Replication Error 14113

I am having some trouble setting up replication on my MSDE 2000 server installation.
When using the set up replication set up wizard, I get through all the screens
correctly, the Distrubution database is created, and then I get error 14113 - Could
not execute c:\...\osql" -E -I60 -t60 -d"distribution" -b -i "..\instdist.sql" -o
"..\instdist.out"

I am using the enterprise manager to enable replication. I have successfully enabled distributor / replication on other installations prior to this one.

I have attached the instdist.out file as a text file.

Any feedback would be appreciated!I'm having the exact same problem. Figure anything out yet?

Originally posted by huntertx
I am having some trouble setting up replication on my MSDE 2000 server installation.
When using the set up replication set up wizard, I get through all the screens
correctly, the Distrubution database is created, and then I get error 14113 - Could
not execute c:\...\osql" -E -I60 -t60 -d"distribution" -b -i "..\instdist.sql" -o
"..\instdist.out"

I am using the enterprise manager to enable replication. I have successfully enabled distributor / replication on other installations prior to this one.

I have attached the instdist.out file as a text file.

Any feedback would be appreciated!|||Yep... Just re-apply SP3 and it should fix the problem. It worked for me!

Replication Configuration Helper (Id buy it!)

Let's face it - setting up SQL 2005 merge pull replication using HTTPS between numerous SQL Server 2005 Express clients and one or more Publishers is an overly complicated exercise.

It should be easy. Why is it so hard?

In a nutshell: The connection chain and security chain is long and when there's a problem the error messages just don't point you to the answer - You have to search for it;re-read the doco; talk to gurus; use logging tools;re-read the error message 100 times; etc. etc.

It should be possible to create a 'Replication Configuration Helper' that steps -step by step - through both the connection chain (App - to SQL Express - to local network components - to the TCP/IP network - to the web server - to the publishers/distributers) and through the security chain (App - to SQL Express authentication - local agents including certificate errors - to ISS server authentication - to Distributer authentication -to Publisher authentication to Article authentication).

Let's face it - the steps occur in sequence and each step can be tested and the appropriate error message raised - TOGETHER WITH INSTRUCTIONS ON HOW TO RESOLVE! (I mean - what's use is an error message when you have to cut and past the error message into a browser and search for ages before you get the instructions on how to resolve the problem?)

So c'mon - someone volenteer to write a 'Replication Configuration Helper'

We are always looking to improve documentation, and we actually have an article in the works with regards to web sync with no release date yet, if you haven't noticed it's a very popular topic on this forum. We'll continue to update msdn, online version of books online, and kb articles on an ongoing basis and as needed. Thanks for your feedback.sql

replication between SQL Server database and linked informix server

I need help setting up replication between my SQL Server (data warehouse) database and a linked informix database.
Does anyone know the best to accomplish this. I can provide any additional information you require to help you, help me ;-)SQL Server support replicate between SQL Server and non-SQL Server Database.
U can choose snapshot replication ,transactional replicate and merge replication.
First U must establish a distributor(a SQL Server which is an agent is responsible for transfering data between two database server)
Then u will make SQL Server as a publisher and using the distributor u created to publish your data.
last, make the informix server as the subscriber to retrieve the data from the distributor.|||Also refer to books online about replication, heterogeneous data sources topic.|||Originally posted by Satya
Also refer to books online about replication, heterogeneous data sources topic.

I would like to use Access as the publisher and SQL as the subscriber. When I check BOL and forums... I am not finding anything that explains how I can accomplish this. Please keep in mind, I want to set up transactional replication between Access and SQL.|||I think after enabling Linked server connection to Access you can use Replication wizard as listed in this [http://www.databasejournal.com/features/mssql/article.php/1438201] article.

HTH

replication between same server

Hi,
I am setting up a DataCenter database on SERVER1. my data is residing in
the different databases on SERVER1 as well. I am intending to do a
replication for each of the databases to DataCenter but i believe replication
cannot be done on the same server.
However, i would like the abilities of Replication to update DataCenter
whenever there's modification and new records automatically from the various
databases. How can i acheive this as there's no unique field in the tables of
these databases to allow me ensure that i am able to copy over all the new
records as well as modified records by using queries.
furthermore , all these databases are also replicated databases from
elsewhere , if i create a insert/modify triggers in these databases will it
work ? i.e during replication a record is inserted and will this be
considered a real insertion that will trigger off the triggers ?
Appreciate any advice
tks & rdgs
Hi
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
> Hi,
> I am setting up a DataCenter database on SERVER1. my data is residing in
> the different databases on SERVER1 as well. I am intending to do a
> replication for each of the databases to DataCenter but i believe
> replication
> cannot be done on the same server.
> However, i would like the abilities of Replication to update DataCenter
> whenever there's modification and new records automatically from the
> various
> databases. How can i acheive this as there's no unique field in the tables
> of
> these databases to allow me ensure that i am able to copy over all the new
> records as well as modified records by using queries.
> furthermore , all these databases are also replicated databases from
> elsewhere , if i create a insert/modify triggers in these databases will
> it
> work ? i.e during replication a record is inserted and will this be
> considered a real insertion that will trigger off the triggers ?
> Appreciate any advice
> tks & rdgs
|||Hi ,
Actually it's not a matter of me not able to set up replication but i
don't think Replication can occur on the same server between 2 different
databases as in my case.
So i am wondering if w/o having to write any queries (as the structure does
not allow me to uniquely identify whether a record is a new or modified one)
, can i have something that as automatic as replication in detecting changes
(such as a modified or new record)
I am thinking of using triggers actually ...
Appreciate any advice
tks & rdgs
"Uri Dimant" wrote:

> Hi
> http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
> Replica (Step by step)
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
>
>

replication between same server

Hi,
I am setting up a DataCenter database on SERVER1. my data is residing in
the different databases on SERVER1 as well. I am intending to do a
replication for each of the databases to DataCenter but i believe replicatio
n
cannot be done on the same server.
However, i would like the abilities of Replication to update DataCenter
whenever there's modification and new records automatically from the various
databases. How can i acheive this as there's no unique field in the tables o
f
these databases to allow me ensure that i am able to copy over all the new
records as well as modified records by using queries.
furthermore , all these databases are also replicated databases from
elsewhere , if i create a insert/modify triggers in these databases will it
work ? i.e during replication a record is inserted and will this be
considered a real insertion that will trigger off the triggers ?
Appreciate any advice
tks & rdgsHi
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
> Hi,
> I am setting up a DataCenter database on SERVER1. my data is residing in
> the different databases on SERVER1 as well. I am intending to do a
> replication for each of the databases to DataCenter but i believe
> replication
> cannot be done on the same server.
> However, i would like the abilities of Replication to update DataCenter
> whenever there's modification and new records automatically from the
> various
> databases. How can i acheive this as there's no unique field in the tables
> of
> these databases to allow me ensure that i am able to copy over all the new
> records as well as modified records by using queries.
> furthermore , all these databases are also replicated databases from
> elsewhere , if i create a insert/modify triggers in these databases will
> it
> work ? i.e during replication a record is inserted and will this be
> considered a real insertion that will trigger off the triggers ?
> Appreciate any advice
> tks & rdgs|||Hi ,
Actually it's not a matter of me not able to set up replication but i
don't think Replication can occur on the same server between 2 different
databases as in my case.
So i am wondering if w/o having to write any queries (as the structure does
not allow me to uniquely identify whether a record is a new or modified one)
, can i have something that as automatic as replication in detecting changes
(such as a modified or new record)
I am thinking of using triggers actually ...
Appreciate any advice
tks & rdgs
"Uri Dimant" wrote:

> Hi
> http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
> Replica (Step by step)
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
>
>

replication between same server

Hi,
I am setting up a DataCenter database on SERVER1. my data is residing in
the different databases on SERVER1 as well. I am intending to do a
replication for each of the databases to DataCenter but i believe replication
cannot be done on the same server.
However, i would like the abilities of Replication to update DataCenter
whenever there's modification and new records automatically from the various
databases. How can i acheive this as there's no unique field in the tables of
these databases to allow me ensure that i am able to copy over all the new
records as well as modified records by using queries.
furthermore , all these databases are also replicated databases from
elsewhere , if i create a insert/modify triggers in these databases will it
work ? i.e during replication a record is inserted and will this be
considered a real insertion that will trigger off the triggers ?
Appreciate any advice
tks & rdgsHi
http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
Replica (Step by step)
"maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
> Hi,
> I am setting up a DataCenter database on SERVER1. my data is residing in
> the different databases on SERVER1 as well. I am intending to do a
> replication for each of the databases to DataCenter but i believe
> replication
> cannot be done on the same server.
> However, i would like the abilities of Replication to update DataCenter
> whenever there's modification and new records automatically from the
> various
> databases. How can i acheive this as there's no unique field in the tables
> of
> these databases to allow me ensure that i am able to copy over all the new
> records as well as modified records by using queries.
> furthermore , all these databases are also replicated databases from
> elsewhere , if i create a insert/modify triggers in these databases will
> it
> work ? i.e during replication a record is inserted and will this be
> considered a real insertion that will trigger off the triggers ?
> Appreciate any advice
> tks & rdgs|||Hi ,
Actually it's not a matter of me not able to set up replication but i
don't think Replication can occur on the same server between 2 different
databases as in my case.
So i am wondering if w/o having to write any queries (as the structure does
not allow me to uniquely identify whether a record is a new or modified one)
, can i have something that as automatic as replication in detecting changes
(such as a modified or new record)
I am thinking of using triggers actually ...
Appreciate any advice
tks & rdgs
"Uri Dimant" wrote:
> Hi
> http://www.mssqlcity.com/Articles/Replic/Replic.htm --Setting All
> Replica (Step by step)
> "maxzsim" <maxzsim@.discussions.microsoft.com> wrote in message
> news:83E7984A-50AC-4FA2-9541-EB2558EB7905@.microsoft.com...
> > Hi,
> >
> > I am setting up a DataCenter database on SERVER1. my data is residing in
> > the different databases on SERVER1 as well. I am intending to do a
> > replication for each of the databases to DataCenter but i believe
> > replication
> > cannot be done on the same server.
> >
> > However, i would like the abilities of Replication to update DataCenter
> > whenever there's modification and new records automatically from the
> > various
> > databases. How can i acheive this as there's no unique field in the tables
> > of
> > these databases to allow me ensure that i am able to copy over all the new
> > records as well as modified records by using queries.
> >
> > furthermore , all these databases are also replicated databases from
> > elsewhere , if i create a insert/modify triggers in these databases will
> > it
> > work ? i.e during replication a record is inserted and will this be
> > considered a real insertion that will trigger off the triggers ?
> >
> > Appreciate any advice
> >
> > tks & rdgs
>
>

Replication and Mirroring

I am setting up transactional replication on a database A with read only subscriber database B (for reporting purpose). I have also setup mirror on database A. I tried to manually failover to mirror...mirroring works fine but transactional replication is interrupted.

I have followed the steps as in article

http://msdn2.microsoft.com/en-us/library/ms151799.aspx

I have also used PublisherFailoverPartner parameter...but replication still complains that it cannot connect to publishing database.

Any ideas or direction is greatly appreciated.

I would trouble shoot the following way:

1) try to connect to the old mirror (which is the new principal after the failover) database from the distributor (for example using osql.exe) and see if connection can be made. This will eliminate the obvious connection issue.

2) check to see if the server that hosted the mirrored database was configured as publisher using the same distributor

Replication across domains ...

I need information on setting up replication across domains. What kind of
gotchas there are, what kind of trust relationships need to exist. All the
gory details.
Any links to resources would be most helpful.
Thanks,
Bob Castleman
DBA Poseur
use passthrough authentication, i.e. same account names and passwords and it
will work fine.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Bob Castleman" <nomail@.here> wrote in message
news:%23kk9KqOqFHA.3136@.TK2MSFTNGP11.phx.gbl...
>I need information on setting up replication across domains. What kind of
>gotchas there are, what kind of trust relationships need to exist. All the
>gory details.
> Any links to resources would be most helpful.
> Thanks,
> Bob Castleman
> DBA Poseur
>

Replication 255 column limit

Is there a workaround for this limitation? I.E can I just use the
column filters option when setting replication up to get around this?
You could upgrade, for a out-of-the box support. Otherwise what people tend
to do is partition the table and replicate the partitions, related by a
PK-PK join. You could present the tables as the original one to the users by
using a view and an instead-of trigger.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||Hi Rob,
It may also be possible to publish an indexed view containing a subset of
the columns as a logbased article (replicate indexed view as table...) if
you can take the performance hit of having the indexed view hanging around
at the publisher.
-Raymond
<robert@.orisoft.co.uk> wrote in message
news:1161004229.423453.155350@.i42g2000cwa.googlegr oups.com...
> Is there a workaround for this limitation? I.E can I just use the
> column filters option when setting replication up to get around this?
>
|||Sorry - just read Raymond's answer and realised I had misinterpreted the
question. To replicate a subset of the table you could use indexed views or
vertically partition the table in the publication wizard. I'll test this,
but as far as I recall the colid is used to determine the max article size,
and as this might still be > 255 the issues may well remain.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||When you are creating a merge/transactional publication, the wizard
(through advanced options) allows you to specify column filters, if I
only tick upto 255 will that get round it? Its for reporting so we dont
need all the data anyway.
Rob
Paul Ibison wrote:
> Sorry - just read Raymond's answer and realised I had misinterpreted the
> question. To replicate a subset of the table you could use indexed views or
> vertically partition the table in the publication wizard. I'll test this,
> but as far as I recall the colid is used to determine the max article size,
> and as this might still be > 255 the issues may well remain.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com .
|||As far as I recall, this will work only if you haven't already deleted some
columns in the table before the 255 you select, assuming these are the
initial 255 columns in the table ie the colid must always be below 255. I'll
verify this but have a big workload at the moment.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Replication - Snapshots

Hi there,
I am looking at setting up a solution that relies on replication of data to
many publications. I believe what I need is merge replication. In this
scenario, many companies will receive data from the master publication but
each company should ONLY receive information for their concern. How do I get
the replication of these 250 companies to "configurably" only receive the
data they need.
Thanks in advance
what you are describing is a filtered publication.
You have two options create a publication which filters rows based on some
hardcoded value, is SalesID=123213, or using a dynamic filter where the
publication detects some property about the subscriber and only sends rows
to that subscriber, ie hostname() or @.@.servername. Dynamic filters work best
with pull subscriptions.
The technology is called horizontal partitioning, as you are creating your
publication you will get to a dialog called Customize the Properties of the
Publication. Select Yes, and then select Horizontally, by filtering the rows
of published data. Enter a filter clause that will filter the rows so that
only the rows you want to end up on the subscriber land there.
It also sounds like what you need is transactional replication
"Murray Foxcroft" <murray.foxcroft@.ast.co.za> wrote in message
news:OplWrAzFEHA.2980@.TK2MSFTNGP09.phx.gbl...
> Hi there,
> I am looking at setting up a solution that relies on replication of data
to
> many publications. I believe what I need is merge replication. In this
> scenario, many companies will receive data from the master publication but
> each company should ONLY receive information for their concern. How do I
get
> the replication of these 250 companies to "configurably" only receive the
> data they need.
> Thanks in advance
>