We've been running transactional replication with updatable subscribers for
several months now. his morning we are seeing these errors in the LOG and
QUEUE READER logs.
You Receive Error Message: "The replication agent is not registered
properly. Rerun SQL Server setup.
Any ideas?
SQL Server 2000 SP3
Running the following command would likely resolve the issue:
"%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
Although I am curious to know if you have installed\uninstalled software
recently on the box that might have caused the problem in the first place.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
> We've been running transactional replication with updatable subscribers
> for
> several months now. his morning we are seeing these errors in the LOG and
> QUEUE READER logs.
>
> You Receive Error Message: "The replication agent is not registered
> properly. Rerun SQL Server setup.
>
> Any ideas?
> SQL Server 2000 SP3
>
|||Appreciate the info !
We are investigating if changes to either the OS or SQLServer itself are the
root cause of this problem. We are seeing that in addition to the queue
reader agent, these are also experiencing the same errors:
LOG READER agent
SNAPSHOT agent
DISTRIBUTION agent.
Does this means we also need to run the command below to register the above
agents as well or just 'qrdrsvc.exe' as you indicate?
==============
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
> Running the following command would likely resolve the issue:
> "%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
> Although I am curious to know if you have installed\uninstalled software
> recently on the box that might have caused the problem in the first place.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
>
|||This seems really strange, is this a clustered SQL Server instance or was
there a registry restore\repair on the box?
In any case, you can probably resolve the issue that you are seeing by
running the agent executables with the -RegServer parameter:
Snapshot agent - snapshot.exe
Logreader agent - logread.exe
Distribution agent - distrib.exe
If the problem is as extensive as it seems to be you may also need to
re-register the support dlls for the replication agents using regsvr32.exe.
Here is a list off the top of my head:
rinitcom.dll
repldp.dll
rdistcom.dll
-Raymond
"GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
> Appreciate the info !
>
> We are investigating if changes to either the OS or SQLServer itself are
> the root cause of this problem. We are seeing that in addition to the
> queue reader agent, these are also experiencing the same errors:
>
> LOG READER agent
> SNAPSHOT agent
> DISTRIBUTION agent.
>
> Does this means we also need to run the command below to register the
> above agents as well or just 'qrdrsvc.exe' as you indicate?
>
> ==============
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
>
|||This is a 2-node clustered SQLServer environment. Word were are getting is
that an attempt to install a new named instance on the cluster failed
(reason unknown) and had to be uninstalled. We are seeing these errors right
after this happened.
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
> This seems really strange, is this a clustered SQL Server instance or was
> there a registry restore\repair on the box?
> In any case, you can probably resolve the issue that you are seeing by
> running the agent executables with the -RegServer parameter:
> Snapshot agent - snapshot.exe
> Logreader agent - logread.exe
> Distribution agent - distrib.exe
> If the problem is as extensive as it seems to be you may also need to
> re-register the support dlls for the replication agents using
regsvr32.exe.[vbcol=seagreen]
> Here is a list off the top of my head:
> rinitcom.dll
> repldp.dll
> rdistcom.dll
> -Raymond
> "GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
> news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
software[vbcol=seagreen]
subscribers
>
|||It was determined that uninstalling one of the SQL instances on the cluster
caused the replication agents to be unregistered. We executed the commands
below and all went well with the exception of the QUEUE READER agent. When
we attempt to register the queue reader agent with 'qrdrsvc.exe regserver'
we get this error:
===================
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
=======================
Is there something special about registering queue reader agent ?
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> This is a 2-node clustered SQLServer environment. Word were are getting is
> that an attempt to install a new named instance on the cluster failed
> (reason unknown) and had to be uninstalled. We are seeing these errors
right[vbcol=seagreen]
> after this happened.
>
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
was[vbcol=seagreen]
> regsvr32.exe.
are[vbcol=seagreen]
> software
> subscribers
LOG
>
|||That seems kind of strange as I didn't get any messages when I tried the
same on my machine. But if you can start the queue reader agent from
SEM\SQLServerAgent then I wouldn't worry too much about it.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
> It was determined that uninstalling one of the SQL instances on the
> cluster
> caused the replication agents to be unregistered. We executed the commands
> below and all went well with the exception of the QUEUE READER agent.
> When
> we attempt to register the queue reader agent with
> 'qrdrsvc.exe -regserver'
> we get this error:
> ===================
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
> 2000 Microsoft Corporation
> Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
> exist or access denied.
> Unable to connect to Local Distributor
> Queue Reader aborting
> =======================
> Is there something special about registering queue reader agent ?
>
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> right
> was
> are
> LOG
>
|||I'm sorry. Can you please elaborate more on what you mean with
SEM\SQLServerAgent ? We are trying to start the queue reader agent from
Enterprise Manager and keep getting the error:
"The replication agent is not registered properly. Rerun SQL Server setup"
===================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> That seems kind of strange as I didn't get any messages when I tried the
> same on my machine. But if you can start the queue reader agent from
> SEM\SQLServerAgent then I wouldn't worry too much about it.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
commands[vbcol=seagreen]
(c)[vbcol=seagreen]
by[vbcol=seagreen]
to[vbcol=seagreen]
itself[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
Server\80\COM\qrdrsvc.exe" -RegServer[vbcol=seagreen]
first[vbcol=seagreen]
registered
>
|||Hi Mark,
When a replication agent is started through a SQL Server Agent job (which is
the same as starting a replication agent from SEM), SQL Server Agent will
activate the replication agent as a COM exe server rather than running it as
a regular executable. That is why I suspect that the COM registration
information for the replication agents was broken when you first reported
the problem. Now from what you have described, your SQL Server installation
was broken due to a clustered instance uninstall so a better course of
action is probably for you to reinstall SQL server rather than trying to fix
bits and pieces of it since nobody knows exactly what pieces are broken.
That said, it is still strange that running 'qrdrsvc.exe -regserver' didn't
return without errors for you (you would want to make sure that Word didn't
mangle the - for you...).
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
> I'm sorry. Can you please elaborate more on what you mean with
> SEM\SQLServerAgent ? We are trying to start the queue reader agent from
> Enterprise Manager and keep getting the error:
> "The replication agent is not registered properly. Rerun SQL Server setup"
> ===================
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...
> commands
> (c)
> by
> to
> itself
> the
> the
> Server\80\COM\qrdrsvc.exe" -RegServer
> first
> registered
>
|||In fact, this is what we are getting when running 'qrdrsvc.exe -regserver'
as a server administrator (with System Administrator role on the SQL server)
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
The process finished. Use CTRL+C to close this window.
=========================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23USLY0nAGHA.516@.TK2MSFTNGP15.phx.gbl...
> Hi Mark,
> When a replication agent is started through a SQL Server Agent job (which
is
> the same as starting a replication agent from SEM), SQL Server Agent will
> activate the replication agent as a COM exe server rather than running it
as
> a regular executable. That is why I suspect that the COM registration
> information for the replication agents was broken when you first reported
> the problem. Now from what you have described, your SQL Server
installation
> was broken due to a clustered instance uninstall so a better course of
> action is probably for you to reinstall SQL server rather than trying to
fix
> bits and pieces of it since nobody knows exactly what pieces are broken.
> That said, it is still strange that running 'qrdrsvc.exe -regserver'
didn't
> return without errors for you (you would want to make sure that Word
didn't[vbcol=seagreen]
> mangle the - for you...).
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
setup"[vbcol=seagreen]
the[vbcol=seagreen]
Copyright[vbcol=seagreen]
not[vbcol=seagreen]
failed[vbcol=seagreen]
errors[vbcol=seagreen]
seeing[vbcol=seagreen]
need[vbcol=seagreen]
to[vbcol=seagreen]
register[vbcol=seagreen]
message
>
Showing posts with label replication. Show all posts
Showing posts with label replication. Show all posts
Thursday, March 29, 2012
Tuesday, March 27, 2012
Error Pull replication
I have two Win2000 that are in a domain. SQL1(SQL server) acts as the
distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push merge
replication is running well.
I want to PULL the db from SQL1 to the db on SQL2, failed :The process could
not connect to Distributor. Cannot generate SSPI context.
I changed Merge Agent location from Subsciber to Distributor, message :
Server 'SQLTEST1" is not prepared to run the offloaded agent
Error Unable to activate the agent on the specified remote server because of
security restrictions. Use dcomcnfg on the remote server to allow the local
SQL Server Agent account to activate the agent
1. Where the best location for the Merge Agent
2. What I have to do next
the SSPI error should be addressed first - consult these kb articles for
more info on it.
http://support.microsoft.com/search/...alse&x=11&y=14
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> I have two Win2000 that are in a domain. SQL1(SQL server) acts as the
> distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push
merge
> replication is running well.
> I want to PULL the db from SQL1 to the db on SQL2, failed :The process
could
> not connect to Distributor. Cannot generate SSPI context.
> I changed Merge Agent location from Subsciber to Distributor, message :
> Server 'SQLTEST1" is not prepared to run the offloaded agent
> Error Unable to activate the agent on the specified remote server because
of
> security restrictions. Use dcomcnfg on the remote server to allow the
local
> SQL Server Agent account to activate the agent
> 1. Where the best location for the Merge Agent
> 2. What I have to do next
>
|||Thank you for the reply. Now it is running well.
One more question. I want to use dinamic filter, different database name for
each subscriber:
... WHERE CityCode = DB_NAME()
but no record in the subscriber table. Plese advice.
"Hilary Cotter" wrote:
> the SSPI error should be addressed first - consult these kb articles for
> more info on it.
> http://support.microsoft.com/search/...alse&x=11&y=14
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> merge
> could
> of
> local
>
>
|||I think that db_name will always resolve to msdb - as that is the database
that the job is run in. In this case I think you will need to change your
filtering criteria.
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> Thank you for the reply. Now it is running well.
> One more question. I want to use dinamic filter, different database name
for[vbcol=seagreen]
> each subscriber:
> ... WHERE CityCode = DB_NAME()
> but no record in the subscriber table. Plese advice.
>
> "Hilary Cotter" wrote:
http://support.microsoft.com/search/...alse&x=11&y=14[vbcol=seagreen]
Push[vbcol=seagreen]
:[vbcol=seagreen]
because[vbcol=seagreen]
|||what should be the filter?
Please advise.
Thank you.
"Hilary Cotter" wrote:
> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>
|||I would like to use instance name as the filtering criteria, it is posible ?
Please advice.
Thank you.
"Hilary Cotter" wrote:
> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>
distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push merge
replication is running well.
I want to PULL the db from SQL1 to the db on SQL2, failed :The process could
not connect to Distributor. Cannot generate SSPI context.
I changed Merge Agent location from Subsciber to Distributor, message :
Server 'SQLTEST1" is not prepared to run the offloaded agent
Error Unable to activate the agent on the specified remote server because of
security restrictions. Use dcomcnfg on the remote server to allow the local
SQL Server Agent account to activate the agent
1. Where the best location for the Merge Agent
2. What I have to do next
the SSPI error should be addressed first - consult these kb articles for
more info on it.
http://support.microsoft.com/search/...alse&x=11&y=14
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> I have two Win2000 that are in a domain. SQL1(SQL server) acts as the
> distributor and publisher. SQL2(MSDE2000) acts as the subscriber. Push
merge
> replication is running well.
> I want to PULL the db from SQL1 to the db on SQL2, failed :The process
could
> not connect to Distributor. Cannot generate SSPI context.
> I changed Merge Agent location from Subsciber to Distributor, message :
> Server 'SQLTEST1" is not prepared to run the offloaded agent
> Error Unable to activate the agent on the specified remote server because
of
> security restrictions. Use dcomcnfg on the remote server to allow the
local
> SQL Server Agent account to activate the agent
> 1. Where the best location for the Merge Agent
> 2. What I have to do next
>
|||Thank you for the reply. Now it is running well.
One more question. I want to use dinamic filter, different database name for
each subscriber:
... WHERE CityCode = DB_NAME()
but no record in the subscriber table. Plese advice.
"Hilary Cotter" wrote:
> the SSPI error should be addressed first - consult these kb articles for
> more info on it.
> http://support.microsoft.com/search/...alse&x=11&y=14
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:CA8EB6A7-F554-4A18-B817-6CE8F3B9A2C6@.microsoft.com...
> merge
> could
> of
> local
>
>
|||I think that db_name will always resolve to msdb - as that is the database
that the job is run in. In this case I think you will need to change your
filtering criteria.
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
"Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> Thank you for the reply. Now it is running well.
> One more question. I want to use dinamic filter, different database name
for[vbcol=seagreen]
> each subscriber:
> ... WHERE CityCode = DB_NAME()
> but no record in the subscriber table. Plese advice.
>
> "Hilary Cotter" wrote:
http://support.microsoft.com/search/...alse&x=11&y=14[vbcol=seagreen]
Push[vbcol=seagreen]
:[vbcol=seagreen]
because[vbcol=seagreen]
|||what should be the filter?
Please advise.
Thank you.
"Hilary Cotter" wrote:
> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>
|||I would like to use instance name as the filtering criteria, it is posible ?
Please advice.
Thank you.
"Hilary Cotter" wrote:
> I think that db_name will always resolve to msdb - as that is the database
> that the job is run in. In this case I think you will need to change your
> filtering criteria.
> --
> 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
> "Thang Long" <ThangLong@.discussions.microsoft.com> wrote in message
> news:75905A3F-F21F-4131-9FDA-79D6628B79BB@.microsoft.com...
> for
> http://support.microsoft.com/search/...alse&x=11&y=14
> Push
> :
> because
>
>
Friday, March 23, 2012
Error on updatable subscription
After a lot of troubles I make working the Transaction Replication between 2
pc.
The replication is transaction with updatable subriber with update
subscription and queue update on failover.
While it works well if the connection between the two pc is ok, if I
disconnect the subscriber from the network and try to make a update on a
table I receive this message:
SQL Server Enterprise Manager
Another user has modified the contents of this table or view; the database
row you are modifying no longer exists in the database.
Database error: '[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
provider returned message: Connection failure]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d01c].
[Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be
performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
distributed transaction.'
The table has a primary key which is of type identity, both on the publisher
and subcriber, then there is a column of type guid for replication.
I don't need to do insert on the subscription but only update.
Thanks in advance.
Were any of the tables owned by different object owners and did you change
the object owners at any point in time?
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
"Sam" <z.sam-No-Spam-@.libero.it> wrote in message
news:%232Ap103lFHA.3656@.TK2MSFTNGP09.phx.gbl...
> After a lot of troubles I make working the Transaction Replication between
2
> pc.
> The replication is transaction with updatable subriber with update
> subscription and queue update on failover.
> While it works well if the connection between the two pc is ok, if I
> disconnect the subscriber from the network and try to make a update on a
> table I receive this message:
> --
> SQL Server Enterprise Manager
> --
> Another user has modified the contents of this table or view; the database
> row you are modifying no longer exists in the database.
> Database error: '[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
> provider returned message: Connection failure]
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d01c].
> [Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be
> performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
> distributed transaction.'
>
> The table has a primary key which is of type identity, both on the
publisher
> and subcriber, then there is a column of type guid for replication.
> I don't need to do insert on the subscription but only update.
> Thanks in advance.
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uGyJz84lFHA.3568@.TK2MSFTNGP10.phx.gbl...
> Were any of the tables owned by different object owners and did you change
> the object owners at any point in time?
>
No, the owner is olways dbo ad it not change.
Initially I used sql server autentication, but there was problem, as you can
see from my post of 29/07 then I changed into Windows autentication using a
login from a domain and go all until I unplug the network cable at the
subscriber.
Thanks
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uGyJz84lFHA.3568@.TK2MSFTNGP10.phx.gbl...
> Were any of the tables owned by different object owners and did you change
> the object owners at any point in time?
>
I think to have found the solution: I should run the sp_setreplfailovermode
setting the failover_mode to queued.
I noticed that if I leave failover_mode to queued it works well too.
There may be any problem doing so?
Thanks.
pc.
The replication is transaction with updatable subriber with update
subscription and queue update on failover.
While it works well if the connection between the two pc is ok, if I
disconnect the subscriber from the network and try to make a update on a
table I receive this message:
SQL Server Enterprise Manager
Another user has modified the contents of this table or view; the database
row you are modifying no longer exists in the database.
Database error: '[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
provider returned message: Connection failure]
[Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d01c].
[Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be
performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
distributed transaction.'
The table has a primary key which is of type identity, both on the publisher
and subcriber, then there is a column of type guid for replication.
I don't need to do insert on the subscription but only update.
Thanks in advance.
Were any of the tables owned by different object owners and did you change
the object owners at any point in time?
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
"Sam" <z.sam-No-Spam-@.libero.it> wrote in message
news:%232Ap103lFHA.3656@.TK2MSFTNGP09.phx.gbl...
> After a lot of troubles I make working the Transaction Replication between
2
> pc.
> The replication is transaction with updatable subriber with update
> subscription and queue update on failover.
> While it works well if the connection between the two pc is ok, if I
> disconnect the subscriber from the network and try to make a update on a
> table I receive this message:
> --
> SQL Server Enterprise Manager
> --
> Another user has modified the contents of this table or view; the database
> row you are modifying no longer exists in the database.
> Database error: '[Microsoft][ODBC SQL Server Driver][SQL Server][OLE/DB
> provider returned message: Connection failure]
> [Microsoft][ODBC SQL Server Driver][SQL Server]OLE DB error trace [OLE/DB
> Provider 'SQLOLEDB' ITransactionJoi JoinTransaction returned 0x8004d01c].
> [Microsoft][ODBC SQL Server Driver][SQL Server]The operation could not be
> performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
> distributed transaction.'
>
> The table has a primary key which is of type identity, both on the
publisher
> and subcriber, then there is a column of type guid for replication.
> I don't need to do insert on the subscription but only update.
> Thanks in advance.
>
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uGyJz84lFHA.3568@.TK2MSFTNGP10.phx.gbl...
> Were any of the tables owned by different object owners and did you change
> the object owners at any point in time?
>
No, the owner is olways dbo ad it not change.
Initially I used sql server autentication, but there was problem, as you can
see from my post of 29/07 then I changed into Windows autentication using a
login from a domain and go all until I unplug the network cable at the
subscriber.
Thanks
|||"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uGyJz84lFHA.3568@.TK2MSFTNGP10.phx.gbl...
> Were any of the tables owned by different object owners and did you change
> the object owners at any point in time?
>
I think to have found the solution: I should run the sp_setreplfailovermode
setting the failover_mode to queued.
I noticed that if I leave failover_mode to queued it works well too.
There may be any problem doing so?
Thanks.
Error on SQL 2005 replication
Hi,
Can someone provide some troubleshooting for the following error I have during the replication setup on SQL 2005?
Thanks,
Frank
System Engineer
===================================
Cannot connect to LASC06.
===================================
Failed to connect to server LASC06. (Microsoft.SqlServer.ConnectionInfo)
Program Location:
at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
at Microsoft.SqlServer.Management.UI.ReplicationSqlConnection.ValidateConnection(UIConnectionInfo connInfo, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
===================================
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 0 - No process is on the other end of the pipe.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=233&LinkId=20476
Server Name: LASC06
Error Number: 233
Severity: 20
State: 0
Program Location:
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ThrowExceptionAndWarning()
at System.Data.SqlClient.TdsParserStateObject.WriteSni()
at System.Data.SqlClient.TdsParserStateObject.WritePacket(Byte flushMode)
at System.Data.SqlClient.TdsParser.SendPreLoginHandshake(Byte[] instanceName, Boolean encrypt)
at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
Can you remotely connect to the machine via SQL Server Management Studio? If not, you may be hitting an issue where the remote connection protocols are disabled on the remote server. If you are trying to connect to SQL Server 2005 DEV SKU or SQLEXPRESS SKU, then by default the remote connection protocols are disabled. You have to use SQL Server Surface Area Configuration tool to change this.
Tom
This posting is provided "AS IS" with no warranties, and confers no rights.
Error on Snapshot Apply
I'm setting up trasactional replication and am encountering an error I've
never seen before...
On certain articles I receive a "CANNOT USE EMPTY OBJECT OR COLUMN NAMES"
error.
What exactly is that? I've been looking through the groups and can't seem to
fins anything on this.
Any help would be greatly appreciated.
Thank You!
I've never seen it either, can you post your schema and publication creation
scripts here?
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
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:B9416619-67DA-4F25-9259-6E637F447213@.microsoft.com...
> I'm setting up trasactional replication and am encountering an error I've
> never seen before...
> On certain articles I receive a "CANNOT USE EMPTY OBJECT OR COLUMN NAMES"
> error.
> What exactly is that? I've been looking through the groups and can't seem
to
> fins anything on this.
> Any help would be greatly appreciated.
> Thank You!
|||Sorry Hilary:
I ended up recreating the subscription and lost the old scripts. The
snapshot is applying as we speak so we'll see if it occurs again.
I do have one question, however. The client that I'm at right now tends to
implement quite a few database changes and quite often. I've told them that
the only two ways to properly apply these changes is to either do it through
the gui or utilize the system stored procedures.
They are wondering if there's a prettier way to address this, either through
a tool or for the subscriber to somehow "pick up" on changes made at the
publisher. They've tossed the idea aound of applying ALTER table statements
at both publisher and subscriber and that should be good enough. I've told
them that's not gonna cut it.
I guess I'm just looking for confirmation that there is no "easy" way around
this issue...
Thanks!!
"Hilary Cotter" wrote:
> I've never seen it either, can you post your schema and publication creation
> scripts here?
> --
> 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
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:B9416619-67DA-4F25-9259-6E637F447213@.microsoft.com...
> to
>
>
never seen before...
On certain articles I receive a "CANNOT USE EMPTY OBJECT OR COLUMN NAMES"
error.
What exactly is that? I've been looking through the groups and can't seem to
fins anything on this.
Any help would be greatly appreciated.
Thank You!
I've never seen it either, can you post your schema and publication creation
scripts here?
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
"A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
news:B9416619-67DA-4F25-9259-6E637F447213@.microsoft.com...
> I'm setting up trasactional replication and am encountering an error I've
> never seen before...
> On certain articles I receive a "CANNOT USE EMPTY OBJECT OR COLUMN NAMES"
> error.
> What exactly is that? I've been looking through the groups and can't seem
to
> fins anything on this.
> Any help would be greatly appreciated.
> Thank You!
|||Sorry Hilary:
I ended up recreating the subscription and lost the old scripts. The
snapshot is applying as we speak so we'll see if it occurs again.
I do have one question, however. The client that I'm at right now tends to
implement quite a few database changes and quite often. I've told them that
the only two ways to properly apply these changes is to either do it through
the gui or utilize the system stored procedures.
They are wondering if there's a prettier way to address this, either through
a tool or for the subscriber to somehow "pick up" on changes made at the
publisher. They've tossed the idea aound of applying ALTER table statements
at both publisher and subscriber and that should be good enough. I've told
them that's not gonna cut it.
I guess I'm just looking for confirmation that there is no "easy" way around
this issue...
Thanks!!
"Hilary Cotter" wrote:
> I've never seen it either, can you post your schema and publication creation
> scripts here?
> --
> 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
> "A. Robinson" <ARobinson@.discussions.microsoft.com> wrote in message
> news:B9416619-67DA-4F25-9259-6E637F447213@.microsoft.com...
> to
>
>
Thursday, March 22, 2012
Error on replication
Hi,
when i try to run an push-replication on MS SQL 2000
i get the error "Log file is full" on the subscriber.
I tried to make this grow VERY much, but it doesnt help.
The table that fails has over 75000 posts, so maybe that is an issue.
The error occurs when i for the first time tries to sync it...
Any ideas?
// PeterTry breaking your task into smaller units of work.
You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.
Good Luck,|||Well, the thing is... i only want to replicate this to a server, and not
run any scripts. Shouldnt MS-SQL handle this?
I tried the push-operation without the LARGE-table (75000 posts)
and it worked. So it has something to do with that.
Any more suggestions?
Please?!!
// Peter
Originally posted by Bruce A. Baasch
Try breaking your task into smaller units of work.
You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.
Good Luck,sql
when i try to run an push-replication on MS SQL 2000
i get the error "Log file is full" on the subscriber.
I tried to make this grow VERY much, but it doesnt help.
The table that fails has over 75000 posts, so maybe that is an issue.
The error occurs when i for the first time tries to sync it...
Any ideas?
// PeterTry breaking your task into smaller units of work.
You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.
Good Luck,|||Well, the thing is... i only want to replicate this to a server, and not
run any scripts. Shouldnt MS-SQL handle this?
I tried the push-operation without the LARGE-table (75000 posts)
and it worked. So it has something to do with that.
Any more suggestions?
Please?!!
// Peter
Originally posted by Bruce A. Baasch
Try breaking your task into smaller units of work.
You would normally be using "BeginTrans" and "CommitTrans" to free up the log space in a program after a unit of work has been completed.
Good Luck,sql
Monday, March 12, 2012
Error number: 37000
All,
I've been configuring Transactional replication in accordance with the
'High Availability' standards, and it seems the initial snapshots have been
transferred but when looking at my distribution agent I can see this error:
Last Command:
{CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group ('ALA')}
Transaction sequence number and command ID of last execution batch are
0x0001A7C400002F8C000900000000 and 1.
Error Details:
Syntax error or access violation
(Source: MOSS-KIPPER (ODBC); Error number: 37000)
Anyone have a rough idea of what to look at?
James McM
sounds like your table name has some characters in it which are causing
problems.
What is the underlying table name?
You can work around this by right clicking on your publication, selecting
properties, articles, and then click on the browse button (the three
ellipses to the right of your table name), and click on the command tab.
Enter a proc name that looks like this:
sp_MSdel_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Do this for the update and insert procs as well, so they look like this:
sp_MSupd_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
sp_MSins_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Now regenerate and redistribute your snapshot.
You also have the option of doing a no sync subscription, and then doing
validations to determine which tables are out of sync and manually sync
them.
To do a nosync subscription you will need to generate the procs.
To do this change the proc names as illustrated above and then on your
publisher in your publication database.
sp_addpublication 'dummy'
sp_addarticle 'dummy','tablename','tablename'
sp_scriptpublicationcustomprocs 'dummy' and in your results pane you will
find the procs. Copy these procs and run them in your subscription database.
"James McMorrough" <james.mcmorrough@.getrid.sqlpersonnel.com> wrote in
message news:OxNFmtOwEHA.3320@.TK2MSFTNGP14.phx.gbl...
> All,
> I've been configuring Transactional replication in accordance with the
> 'High Availability' standards, and it seems the initial snapshots have
> been
> transferred but when looking at my distribution agent I can see this
> error:
> Last Command:
> {CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group
> ('ALA')}
> Transaction sequence number and command ID of last execution batch are
> 0x0001A7C400002F8C000900000000 and 1.
> Error Details:
> Syntax error or access violation
> (Source: MOSS-KIPPER (ODBC); Error number: 37000)
>
> Anyone have a rough idea of what to look at?
> James McM
>
I've been configuring Transactional replication in accordance with the
'High Availability' standards, and it seems the initial snapshots have been
transferred but when looking at my distribution agent I can see this error:
Last Command:
{CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group ('ALA')}
Transaction sequence number and command ID of last execution batch are
0x0001A7C400002F8C000900000000 and 1.
Error Details:
Syntax error or access violation
(Source: MOSS-KIPPER (ODBC); Error number: 37000)
Anyone have a rough idea of what to look at?
James McM
sounds like your table name has some characters in it which are causing
problems.
What is the underlying table name?
You can work around this by right clicking on your publication, selecting
properties, articles, and then click on the browse button (the three
ellipses to the right of your table name), and click on the command tab.
Enter a proc name that looks like this:
sp_MSdel_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Do this for the update and insert procs as well, so they look like this:
sp_MSupd_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
sp_MSins_Alliance_UniChem_Norge_RBO_Customer_Posti ng_Group
Now regenerate and redistribute your snapshot.
You also have the option of doing a no sync subscription, and then doing
validations to determine which tables are out of sync and manually sync
them.
To do a nosync subscription you will need to generate the procs.
To do this change the proc names as illustrated above and then on your
publisher in your publication database.
sp_addpublication 'dummy'
sp_addarticle 'dummy','tablename','tablename'
sp_scriptpublicationcustomprocs 'dummy' and in your results pane you will
find the procs. Copy these procs and run them in your subscription database.
"James McMorrough" <james.mcmorrough@.getrid.sqlpersonnel.com> wrote in
message news:OxNFmtOwEHA.3320@.TK2MSFTNGP14.phx.gbl...
> All,
> I've been configuring Transactional replication in accordance with the
> 'High Availability' standards, and it seems the initial snapshots have
> been
> transferred but when looking at my distribution agent I can see this
> error:
> Last Command:
> {CALL sp_MSdel_Alliance UniChem Norge (RBO)$Customer Posting Group
> ('ALA')}
> Transaction sequence number and command ID of last execution batch are
> 0x0001A7C400002F8C000900000000 and 1.
> Error Details:
> Syntax error or access violation
> (Source: MOSS-KIPPER (ODBC); Error number: 37000)
>
> Anyone have a rough idea of what to look at?
> James McM
>
Error number: 2812 - Transaction Replication
Hi,
I am trying transactional replication between two servers with a remote
distributor. I am getting following error each time I run the distribution
agent
Last Command : {CALL sp_MSupd_Customers (NULL,N'Alfreds Futterkiste -
test',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,N'ALFKI',0x0200)}
Transaction sequence number and command ID of last execution batch are
0x0000001A00000082000900000000 and 1.
Error Message :Could not find stored procedure 'sp_MSupd_Customers'.
Error details : Could not find stored procedure 'sp_MSupd_Customers'.
(Source: L000646\AA03 (Data source); Error number: 2812)
Can some one help please
If you have used @.sync_type = None in sp_addsubscription or in the
subscription wizard, Initialize subscription page, you select 'no, the
subscriber already has the schema and data' you may get this error. The
system tables for replication will be created on the subscriber in either
case but you'll need to manually create the stored procedures on the
subscriber if you use this option otherwise you'll have the above error when
you change a row on the publisher. Use sp_scriptpublicationcustomprocs
(assuming you have >= sp1) to create a script which creates the procedures
and run this script on the subscriber.
HTH,
Paul Ibison
|||Thanks for that Paul. It is all working now.
regards
"Paul Ibison" wrote:
> If you have used @.sync_type = None in sp_addsubscription or in the
> subscription wizard, Initialize subscription page, you select 'no, the
> subscriber already has the schema and data' you may get this error. The
> system tables for replication will be created on the subscriber in either
> case but you'll need to manually create the stored procedures on the
> subscriber if you use this option otherwise you'll have the above error when
> you change a row on the publisher. Use sp_scriptpublicationcustomprocs
> (assuming you have >= sp1) to create a script which creates the procedures
> and run this script on the subscriber.
> HTH,
> Paul Ibison
>
>
I am trying transactional replication between two servers with a remote
distributor. I am getting following error each time I run the distribution
agent
Last Command : {CALL sp_MSupd_Customers (NULL,N'Alfreds Futterkiste -
test',NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL,NULL ,N'ALFKI',0x0200)}
Transaction sequence number and command ID of last execution batch are
0x0000001A00000082000900000000 and 1.
Error Message :Could not find stored procedure 'sp_MSupd_Customers'.
Error details : Could not find stored procedure 'sp_MSupd_Customers'.
(Source: L000646\AA03 (Data source); Error number: 2812)
Can some one help please
If you have used @.sync_type = None in sp_addsubscription or in the
subscription wizard, Initialize subscription page, you select 'no, the
subscriber already has the schema and data' you may get this error. The
system tables for replication will be created on the subscriber in either
case but you'll need to manually create the stored procedures on the
subscriber if you use this option otherwise you'll have the above error when
you change a row on the publisher. Use sp_scriptpublicationcustomprocs
(assuming you have >= sp1) to create a script which creates the procedures
and run this script on the subscriber.
HTH,
Paul Ibison
|||Thanks for that Paul. It is all working now.
regards
"Paul Ibison" wrote:
> If you have used @.sync_type = None in sp_addsubscription or in the
> subscription wizard, Initialize subscription page, you select 'no, the
> subscriber already has the schema and data' you may get this error. The
> system tables for replication will be created on the subscriber in either
> case but you'll need to manually create the stored procedures on the
> subscriber if you use this option otherwise you'll have the above error when
> you change a row on the publisher. Use sp_scriptpublicationcustomprocs
> (assuming you have >= sp1) to create a script which creates the procedures
> and run this script on the subscriber.
> HTH,
> Paul Ibison
>
>
Sunday, February 26, 2012
Error message when creating replication with generated SQL scripts
Hi all SQL Replication experts :)
I have created my production server as a distributor and a publication on that server. On my backup server I have created a pull subscription. After that I have generated SQL scripts on my backup server so I can create the pull subscription anytime.
To test my script I used sp_removedbreplication 'dbname' to remove replication on the backup server. I then used the generated SQL script to create the pull subscription again. I got this error message
Job 'ProdServName_DBName-BackServName-DBName401A48AE-D8DC-4F29-A610-13916370CD0B' started successfully.
Server: Msg 208, Level 16, State 1, Procedure sp_addsubscription, Line 135
Invalid object name 'syspublications'.
What does this Error message mean and what can I do about it?
Grateful for all answers
Best,
/M
Friday, February 24, 2012
error message on publisher
SQL 2005 sp1 merge replication. 1 publisher/distributor. 20 SQL
Express(SP1) subscriptions.
Working OK since we set up about 7 weeks ago, today we recieved the
following error when attempting an update on the publisher. The table
is bidirectional, auto identity range mgmt, column level tracking.
Error Executing Database Query. [Macromedia][SQLServer JDBC
Driver][SQLServer]UPDATECOLVBM: The parameter 'colv' is not valid.
The error occurred on line 311.
Can anyone shed any light on this? Where to begin looking? Hopefully
there is a way to correct without losing data at the existing
subscriptions.
TIA,
John G.
Can you enable logging so we can determine which proc this is failing on?
Here is a kbarticle which describes how to do this.
http://support.microsoft.com/default.aspx/kb/312292
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
<jgmeinder@.gmail.com> wrote in message
news:1169493886.403936.320150@.38g2000cwa.googlegro ups.com...
> SQL 2005 sp1 merge replication. 1 publisher/distributor. 20 SQL
> Express(SP1) subscriptions.
> Working OK since we set up about 7 weeks ago, today we recieved the
> following error when attempting an update on the publisher. The table
> is bidirectional, auto identity range mgmt, column level tracking.
> Error Executing Database Query. [Macromedia][SQLServer JDBC
> Driver][SQLServer]UPDATECOLVBM: The parameter 'colv' is not valid.
> The error occurred on line 311.
> Can anyone shed any light on this? Where to begin looking? Hopefully
> there is a way to correct without losing data at the existing
> subscriptions.
> TIA,
> John G.
>
|||Sorry, I wasn't very clear, the error occurs when running a T-SQL
update statement on the publisher database, not when an agent is
running. I executed the SQL outside of our app and got the following
error from the merge upd trigger.
Msg 18750, Level 16, State 1, Procedure
MSmerge_upd_6F87E78AF9BA4EC881AD11085DED1A80, Line 100
UPDATECOLVBM: The parameter 'colv' is not valid.
Msg 3621, Level 16, State 1, Procedure
MSmerge_upd_6F87E78AF9BA4EC881AD11085DED1A80, Line 100
The statement has been terminated.
The SQL:
UPDATE tblAlaska_Facility_Manager SET [organization_establishment] =
'Absolute Fresh Seafoods Inc'
WHERE facilityID = 2732
In the app they updated more columns, but otherwise is exactly the
same.
I can see the line it is referring to in the trigger, but do not
understand the syntax.
Also, I have found rows that the update completes correctly, and some
that error with the same exact error. I am going to try see if there
is anything common between the rows that error and the rows that do
not.
Thanks,
jg
Hilary Cotter wrote:[vbcol=seagreen]
> Can you enable logging so we can determine which proc this is failing on?
> Here is a kbarticle which describes how to do this.
> http://support.microsoft.com/default.aspx/kb/312292
> --
> 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
>
> <jgmeinder@.gmail.com> wrote in message
> news:1169493886.403936.320150@.38g2000cwa.googlegro ups.com...
|||I could not discover any commonalities between the rows that returned
the error. So we did a simple update at a subscriber, and it worked,
while the same update at the publisher would error. We then did a
sync, and the rows at the publisher 'freed up', so that updates to the
rows work now.
We see this behavior once in a while, and until this time we would drop
the article and re-create it. But in this case our customers with
subscribers could not afford to lose any data that changed at any
subscription.
At least we have a work around, but I wouldn't mind getting an
understanding of what is causing this behavior.
Thanks,
jg
Express(SP1) subscriptions.
Working OK since we set up about 7 weeks ago, today we recieved the
following error when attempting an update on the publisher. The table
is bidirectional, auto identity range mgmt, column level tracking.
Error Executing Database Query. [Macromedia][SQLServer JDBC
Driver][SQLServer]UPDATECOLVBM: The parameter 'colv' is not valid.
The error occurred on line 311.
Can anyone shed any light on this? Where to begin looking? Hopefully
there is a way to correct without losing data at the existing
subscriptions.
TIA,
John G.
Can you enable logging so we can determine which proc this is failing on?
Here is a kbarticle which describes how to do this.
http://support.microsoft.com/default.aspx/kb/312292
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
<jgmeinder@.gmail.com> wrote in message
news:1169493886.403936.320150@.38g2000cwa.googlegro ups.com...
> SQL 2005 sp1 merge replication. 1 publisher/distributor. 20 SQL
> Express(SP1) subscriptions.
> Working OK since we set up about 7 weeks ago, today we recieved the
> following error when attempting an update on the publisher. The table
> is bidirectional, auto identity range mgmt, column level tracking.
> Error Executing Database Query. [Macromedia][SQLServer JDBC
> Driver][SQLServer]UPDATECOLVBM: The parameter 'colv' is not valid.
> The error occurred on line 311.
> Can anyone shed any light on this? Where to begin looking? Hopefully
> there is a way to correct without losing data at the existing
> subscriptions.
> TIA,
> John G.
>
|||Sorry, I wasn't very clear, the error occurs when running a T-SQL
update statement on the publisher database, not when an agent is
running. I executed the SQL outside of our app and got the following
error from the merge upd trigger.
Msg 18750, Level 16, State 1, Procedure
MSmerge_upd_6F87E78AF9BA4EC881AD11085DED1A80, Line 100
UPDATECOLVBM: The parameter 'colv' is not valid.
Msg 3621, Level 16, State 1, Procedure
MSmerge_upd_6F87E78AF9BA4EC881AD11085DED1A80, Line 100
The statement has been terminated.
The SQL:
UPDATE tblAlaska_Facility_Manager SET [organization_establishment] =
'Absolute Fresh Seafoods Inc'
WHERE facilityID = 2732
In the app they updated more columns, but otherwise is exactly the
same.
I can see the line it is referring to in the trigger, but do not
understand the syntax.
Also, I have found rows that the update completes correctly, and some
that error with the same exact error. I am going to try see if there
is anything common between the rows that error and the rows that do
not.
Thanks,
jg
Hilary Cotter wrote:[vbcol=seagreen]
> Can you enable logging so we can determine which proc this is failing on?
> Here is a kbarticle which describes how to do this.
> http://support.microsoft.com/default.aspx/kb/312292
> --
> 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
>
> <jgmeinder@.gmail.com> wrote in message
> news:1169493886.403936.320150@.38g2000cwa.googlegro ups.com...
|||I could not discover any commonalities between the rows that returned
the error. So we did a simple update at a subscriber, and it worked,
while the same update at the publisher would error. We then did a
sync, and the rows at the publisher 'freed up', so that updates to the
rows work now.
We see this behavior once in a while, and until this time we would drop
the article and re-create it. But in this case our customers with
subscribers could not afford to lose any data that changed at any
subscription.
At least we have a work around, but I wouldn't mind getting an
understanding of what is causing this behavior.
Thanks,
jg
Sunday, February 19, 2012
error message initializing merge replication
i've got the following error message, can anybody help me
The merge process could not initialize the subscription.
(Source: Merge Replication Provider (Agent); Error number: -2147201011)
------
Ongeldige cursorstatus
(Source: MWO-SERVER (Data source); Error number: 0)
------
Bruno
@.Assist
Bruno,
can you try increasing the -QueryTimeOut parameter, and also enable logging
to see if we can get a bit more info.
http://support.microsoft.com/?id=312292
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i'v done that, output is about the same. Has it to do with the snapshot ?
The replication is over the internet and has run for serveral week. I had to
change the design of some tables, so i broke the replication, made the change
but when i tried to recreate the the push subscription i get these error.
this is the last part of the log file
[17-4-2005 21:01:20]MWO-SERVER.assist-b2b: {call sp_MSgetversion }
Percent Complete: 2
Connecting to Subscriber 'MWO-SERVER'
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 0
Applying the snapshot to the Subscriber
The merge process could not initialize the subscription.
Percent Complete: 0
The merge process could not initialize the subscription.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201011
Message: The merge process could not initialize the subscription.
Percent Complete: 0
Category:SQLSERVER
Source: MWO-SERVER
Number: 0
Message: Ongeldige cursorstatus
Disconnecting from Subscriber 'MWO-SERVER'
Disconnecting from Publisher 'ANNA'
Disconnecting from Publisher 'ANNA'
Disconnecting from Distributor 'ANNA'
Rgds,
Bruno
"Paul Ibison" schreef:
> Bruno,
> can you try increasing the -QueryTimeOut parameter, and also enable logging
> to see if we can get a bit more info.
> http://support.microsoft.com/?id=312292
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||I'd check to see that there isn't something more fundamental wrong here. Can
you create a new merge publication of a test table with a couple of rows in
it and see if this'll initialize. Also, please can you confirm your service
pack / patch level.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||microsoft windows 2003
sql server developer edition
version 8.00.760 (sp3)
When i create an new push subscription to another internal sql server, it's
works fine.
"Paul Ibison" schreef:
> I'd check to see that there isn't something more fundamental wrong here. Can
> you create a new merge publication of a test table with a couple of rows in
> it and see if this'll initialize. Also, please can you confirm your service
> pack / patch level.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||Mmmm. Not too sure here. If you have increased -QueryTimeOut then one other
idea I had was blocking. Can you drop all connections to the subscriber
database before initializing to see if this is the issue.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i've created a new database and that also won't work. But the is working the
other way around. i enabled the subscriber as the publisher/distributor and
the original distributor as subscriber and that worked. It's not ideal but
for now its working. I think that some old configuration is still left in the
master database. Can't that be the problem ?
"Paul Ibison" schreef:
> Mmmm. Not too sure here. If you have increased -QueryTimeOut then one other
> idea I had was blocking. Can you drop all connections to the subscriber
> database before initializing to see if this is the issue.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
>
|||I think it might be some incompatibility between builds, which is one thing
I forgot to ask about, but anyway, I'm glad you have things up and going.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
The merge process could not initialize the subscription.
(Source: Merge Replication Provider (Agent); Error number: -2147201011)
------
Ongeldige cursorstatus
(Source: MWO-SERVER (Data source); Error number: 0)
------
Bruno
@.Assist
Bruno,
can you try increasing the -QueryTimeOut parameter, and also enable logging
to see if we can get a bit more info.
http://support.microsoft.com/?id=312292
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i'v done that, output is about the same. Has it to do with the snapshot ?
The replication is over the internet and has run for serveral week. I had to
change the design of some tables, so i broke the replication, made the change
but when i tried to recreate the the push subscription i get these error.
this is the last part of the log file
[17-4-2005 21:01:20]MWO-SERVER.assist-b2b: {call sp_MSgetversion }
Percent Complete: 2
Connecting to Subscriber 'MWO-SERVER'
Percent Complete: 3
Retrieving publication information
Percent Complete: 4
Retrieving subscription information
Percent Complete: 0
Applying the snapshot to the Subscriber
The merge process could not initialize the subscription.
Percent Complete: 0
The merge process could not initialize the subscription.
Percent Complete: 0
Category:NULL
Source: Merge Replication Provider
Number: -2147201011
Message: The merge process could not initialize the subscription.
Percent Complete: 0
Category:SQLSERVER
Source: MWO-SERVER
Number: 0
Message: Ongeldige cursorstatus
Disconnecting from Subscriber 'MWO-SERVER'
Disconnecting from Publisher 'ANNA'
Disconnecting from Publisher 'ANNA'
Disconnecting from Distributor 'ANNA'
Rgds,
Bruno
"Paul Ibison" schreef:
> Bruno,
> can you try increasing the -QueryTimeOut parameter, and also enable logging
> to see if we can get a bit more info.
> http://support.microsoft.com/?id=312292
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||I'd check to see that there isn't something more fundamental wrong here. Can
you create a new merge publication of a test table with a couple of rows in
it and see if this'll initialize. Also, please can you confirm your service
pack / patch level.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||microsoft windows 2003
sql server developer edition
version 8.00.760 (sp3)
When i create an new push subscription to another internal sql server, it's
works fine.
"Paul Ibison" schreef:
> I'd check to see that there isn't something more fundamental wrong here. Can
> you create a new merge publication of a test table with a couple of rows in
> it and see if this'll initialize. Also, please can you confirm your service
> pack / patch level.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
|||Mmmm. Not too sure here. If you have increased -QueryTimeOut then one other
idea I had was blocking. Can you drop all connections to the subscriber
database before initializing to see if this is the issue.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||i've created a new database and that also won't work. But the is working the
other way around. i enabled the subscriber as the publisher/distributor and
the original distributor as subscriber and that worked. It's not ideal but
for now its working. I think that some old configuration is still left in the
master database. Can't that be the problem ?
"Paul Ibison" schreef:
> Mmmm. Not too sure here. If you have increased -QueryTimeOut then one other
> idea I had was blocking. Can you drop all connections to the subscriber
> database before initializing to see if this is the issue.
> Rgds,
> Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
>
>
|||I think it might be some incompatibility between builds, which is one thing
I forgot to ask about, but anyway, I'm glad you have things up and going.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Error message from server: The log file is full. Backup transactio
Hi,
I am working on a Access Sql system where I need to put a new release for a
system. This system involves transactional replication. Most of new screens
and code relate to client side sql server and the main server. When I am
trying to test some functionality on the server (main) side I am getting the
above error. Right now the main database file is 1. GB while the transaction
file is 76 GB. The problem is I cannot backup this database on the server as
it tells the log file is full. So I am not sure how to handle this situation
without having the ability to have a backup. Any help is appreciated. ThanksOn Mar 25, 10:12 am, Jack <J...@.discussions.microsoft.com> wrote:
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
try using DBCC SHRINKFILE to shrink the log file in conjunction with
the BACKUP LOG command, use sp_helpfile to find the log files logical
name, something like the following
SP_HELPFILE
this will return the logical name of the log file
DBCC SHRINKFILE (<LogicalName>)
I believe this moves all the data to the start of the file
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
this then does the actual shrink. you may need to repeat commands 2 a
3 a couple of times until the filesize stops shrinking.
google or BOL the commands to make sure I have them right, I don't
have a DB handy to check.|||You should learn the basics about backup and restore and based on that set the recovery model for
your database properly. In your case, it seems you have full recover model but you don't perform log
backups. This means that the log is never emptied so the ldf file keeps growing and growing. You can
empty the log file by either setting recover model to simple or by doing:
BACKUP LOG dbname WITH NO_LOG
And then shrink the ldf file (keeping an eye on virtual log file layout, according to
http://www.karaszi.com/SQLServer/info_dont_shrink.asp), to a reasonable size.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:9038A77D-EE8E-4E41-9FEB-335DB2D62834@.microsoft.com...
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
I am working on a Access Sql system where I need to put a new release for a
system. This system involves transactional replication. Most of new screens
and code relate to client side sql server and the main server. When I am
trying to test some functionality on the server (main) side I am getting the
above error. Right now the main database file is 1. GB while the transaction
file is 76 GB. The problem is I cannot backup this database on the server as
it tells the log file is full. So I am not sure how to handle this situation
without having the ability to have a backup. Any help is appreciated. ThanksOn Mar 25, 10:12 am, Jack <J...@.discussions.microsoft.com> wrote:
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
try using DBCC SHRINKFILE to shrink the log file in conjunction with
the BACKUP LOG command, use sp_helpfile to find the log files logical
name, something like the following
SP_HELPFILE
this will return the logical name of the log file
DBCC SHRINKFILE (<LogicalName>)
I believe this moves all the data to the start of the file
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
this then does the actual shrink. you may need to repeat commands 2 a
3 a couple of times until the filesize stops shrinking.
google or BOL the commands to make sure I have them right, I don't
have a DB handy to check.|||You should learn the basics about backup and restore and based on that set the recovery model for
your database properly. In your case, it seems you have full recover model but you don't perform log
backups. This means that the log is never emptied so the ldf file keeps growing and growing. You can
empty the log file by either setting recover model to simple or by doing:
BACKUP LOG dbname WITH NO_LOG
And then shrink the ldf file (keeping an eye on virtual log file layout, according to
http://www.karaszi.com/SQLServer/info_dont_shrink.asp), to a reasonable size.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Jack" <Jack@.discussions.microsoft.com> wrote in message
news:9038A77D-EE8E-4E41-9FEB-335DB2D62834@.microsoft.com...
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
Error message from server: The log file is full. Backup transactio
Hi,
I am working on a Access Sql system where I need to put a new release for a
system. This system involves transactional replication. Most of new screens
and code relate to client side sql server and the main server. When I am
trying to test some functionality on the server (main) side I am getting the
above error. Right now the main database file is 1. GB while the transaction
file is 76 GB. The problem is I cannot backup this database on the server as
it tells the log file is full. So I am not sure how to handle this situation
without having the ability to have a backup. Any help is appreciated. Thanks
On Mar 25, 10:12 am, Jack <J...@.discussions.microsoft.com> wrote:
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
try using DBCC SHRINKFILE to shrink the log file in conjunction with
the BACKUP LOG command, use sp_helpfile to find the log files logical
name, something like the following
SP_HELPFILE
this will return the logical name of the log file
DBCC SHRINKFILE (<LogicalName>)
I believe this moves all the data to the start of the file
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
this then does the actual shrink. you may need to repeat commands 2 a
3 a couple of times until the filesize stops shrinking.
google or BOL the commands to make sure I have them right, I don't
have a DB handy to check.
I am working on a Access Sql system where I need to put a new release for a
system. This system involves transactional replication. Most of new screens
and code relate to client side sql server and the main server. When I am
trying to test some functionality on the server (main) side I am getting the
above error. Right now the main database file is 1. GB while the transaction
file is 76 GB. The problem is I cannot backup this database on the server as
it tells the log file is full. So I am not sure how to handle this situation
without having the ability to have a backup. Any help is appreciated. Thanks
On Mar 25, 10:12 am, Jack <J...@.discussions.microsoft.com> wrote:
> Hi,
> I am working on a Access Sql system where I need to put a new release for a
> system. This system involves transactional replication. Most of new screens
> and code relate to client side sql server and the main server. When I am
> trying to test some functionality on the server (main) side I am getting the
> above error. Right now the main database file is 1. GB while the transaction
> file is 76 GB. The problem is I cannot backup this database on the server as
> it tells the log file is full. So I am not sure how to handle this situation
> without having the ability to have a backup. Any help is appreciated. Thanks
try using DBCC SHRINKFILE to shrink the log file in conjunction with
the BACKUP LOG command, use sp_helpfile to find the log files logical
name, something like the following
SP_HELPFILE
this will return the logical name of the log file
DBCC SHRINKFILE (<LogicalName>)
I believe this moves all the data to the start of the file
BACKUP LOG <dbname> WITH TRUNCATE_ONLY
this then does the actual shrink. you may need to repeat commands 2 a
3 a couple of times until the filesize stops shrinking.
google or BOL the commands to make sure I have them right, I don't
have a DB handy to check.
Friday, February 17, 2012
Error Message 8144 on Transaction Push Replication
Don,
have you changed the schema on the publisher and
subscriber - please can you check the table definitions.
Perhaps this was a nosync initialization and you created
the procedures by hand and they are now out of sync as
you've altered the columns on the publisher? Depending on
the problem it may be possible to run
sp_scriptpublicationcustomprocs to generate new
procedures and then recreate them on the subscriber if
this is the case. I'd only do this if the schemas are
identical.
HTH,
Paul Ibison
(The ONLY sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul,
Thank you so much. The developers were upgrading the publication and got the
error message that Dirc Khan-Evans just posted.
Trying to run ALTER TABLE ... get the error message:
Server: Msg 4929, Level 16, State 1, Line 1
Cannot alter the table 'blah' because it is being published for replication.
I had no choice but to delete the publication. I recreated it and pushed a
new subscription and it ran successfully. However, the schema changes did not
carry over to the subscriber. The subsriber table does not have the new
fields. That is why I am getting this error. Should I delete the table on
the subscriber and push a new subscription? Thanks.
Don
the "Paul Ibison" wrote:
> Don,
> have you changed the schema on the publisher and
> subscriber - please can you check the table definitions.
> Perhaps this was a nosync initialization and you created
> the procedures by hand and they are now out of sync as
> you've altered the columns on the publisher? Depending on
> the problem it may be possible to run
> sp_scriptpublicationcustomprocs to generate new
> procedures and then recreate them on the subscriber if
> this is the case. I'd only do this if the schemas are
> identical.
> HTH,
> Paul Ibison
> (The ONLY sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Don,
I'd reinitialize, but first double-check something in the
publication properties. On the article properties
elipsis, snapshot tab, for name conflicts check that it
says 'DROP the existing table'. When you subscribe, be
sure to leave the default which is to initialize. Then it
should all go fine.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
>
|||Paul,
Just to let you know how the story ended. I tried to reinitialize, but that
also did not work. I ended up droping the tables on the subscriber that had
schemas different from the publisher. I scripted the tables from the
publisher and recreated them on the subscriber. I then had to recreate the
publications and push the subscriptions. It now seems to be running fine.
Just one thought... the publisher is on SQL 2000 sp2 and the subsciber is on
2000 sp3. I don't know if this was a bug. Thanks for all your help.
Don Saluga
Vector Security Inc.
"Paul Ibison" wrote:
> Don,
> I'd reinitialize, but first double-check something in the
> publication properties. On the article properties
> elipsis, snapshot tab, for name conflicts check that it
> says 'DROP the existing table'. When you subscribe, be
> sure to leave the default which is to initialize. Then it
> should all go fine.
> HTH,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Thanks for the update Don - it's always helpful.
Regards,
Paul
"Don" <Don@.discussions.microsoft.com> wrote in message
news:A1286950-DC8C-4DB3-97CC-1C6E06E90565@.microsoft.com...
> Paul,
> Just to let you know how the story ended. I tried to reinitialize, but
that
> also did not work. I ended up droping the tables on the subscriber that
had
> schemas different from the publisher. I scripted the tables from the
> publisher and recreated them on the subscriber. I then had to recreate
the
> publications and push the subscriptions. It now seems to be running fine.
> Just one thought... the publisher is on SQL 2000 sp2 and the subsciber is
on[vbcol=seagreen]
> 2000 sp3. I don't know if this was a bug. Thanks for all your help.
> Don Saluga
> Vector Security Inc.
> "Paul Ibison" wrote:
have you changed the schema on the publisher and
subscriber - please can you check the table definitions.
Perhaps this was a nosync initialization and you created
the procedures by hand and they are now out of sync as
you've altered the columns on the publisher? Depending on
the problem it may be possible to run
sp_scriptpublicationcustomprocs to generate new
procedures and then recreate them on the subscriber if
this is the case. I'd only do this if the schemas are
identical.
HTH,
Paul Ibison
(The ONLY sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Paul,
Thank you so much. The developers were upgrading the publication and got the
error message that Dirc Khan-Evans just posted.
Trying to run ALTER TABLE ... get the error message:
Server: Msg 4929, Level 16, State 1, Line 1
Cannot alter the table 'blah' because it is being published for replication.
I had no choice but to delete the publication. I recreated it and pushed a
new subscription and it ran successfully. However, the schema changes did not
carry over to the subscriber. The subsriber table does not have the new
fields. That is why I am getting this error. Should I delete the table on
the subscriber and push a new subscription? Thanks.
Don
the "Paul Ibison" wrote:
> Don,
> have you changed the schema on the publisher and
> subscriber - please can you check the table definitions.
> Perhaps this was a nosync initialization and you created
> the procedures by hand and they are now out of sync as
> you've altered the columns on the publisher? Depending on
> the problem it may be possible to run
> sp_scriptpublicationcustomprocs to generate new
> procedures and then recreate them on the subscriber if
> this is the case. I'd only do this if the schemas are
> identical.
> HTH,
> Paul Ibison
> (The ONLY sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Don,
I'd reinitialize, but first double-check something in the
publication properties. On the article properties
elipsis, snapshot tab, for name conflicts check that it
says 'DROP the existing table'. When you subscribe, be
sure to leave the default which is to initialize. Then it
should all go fine.
HTH,
Paul Ibison
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
>
|||Paul,
Just to let you know how the story ended. I tried to reinitialize, but that
also did not work. I ended up droping the tables on the subscriber that had
schemas different from the publisher. I scripted the tables from the
publisher and recreated them on the subscriber. I then had to recreate the
publications and push the subscriptions. It now seems to be running fine.
Just one thought... the publisher is on SQL 2000 sp2 and the subsciber is on
2000 sp3. I don't know if this was a bug. Thanks for all your help.
Don Saluga
Vector Security Inc.
"Paul Ibison" wrote:
> Don,
> I'd reinitialize, but first double-check something in the
> publication properties. On the article properties
> elipsis, snapshot tab, for name conflicts check that it
> says 'DROP the existing table'. When you subscribe, be
> sure to leave the default which is to initialize. Then it
> should all go fine.
> HTH,
> Paul Ibison
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Thanks for the update Don - it's always helpful.
Regards,
Paul
"Don" <Don@.discussions.microsoft.com> wrote in message
news:A1286950-DC8C-4DB3-97CC-1C6E06E90565@.microsoft.com...
> Paul,
> Just to let you know how the story ended. I tried to reinitialize, but
that
> also did not work. I ended up droping the tables on the subscriber that
had
> schemas different from the publisher. I scripted the tables from the
> publisher and recreated them on the subscriber. I then had to recreate
the
> publications and push the subscriptions. It now seems to be running fine.
> Just one thought... the publisher is on SQL 2000 sp2 and the subsciber is
on[vbcol=seagreen]
> 2000 sp3. I don't know if this was a bug. Thanks for all your help.
> Don Saluga
> Vector Security Inc.
> "Paul Ibison" wrote:
Subscribe to:
Posts (Atom)