 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Other Technologies / Replication / September 2006'INITCOLVS' is not a recognized built-in function name
I'm using a replicated SQL Server 2005 database on my server and a SQL Server Everywhere CTP (v3.1) database as my client app. Everything works fine (including sync) until I add a row to a table on the subscriber (client). Upon the next synchronization I get the following error: 'INITCOLVS' is not a recognized built-in function name. This error also tells me that the problem occurred while applying the new row to the publisher, not the subscriber. Any ideas??? Thanks in advance!  SignatureHilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 > I'm using a replicated SQL Server 2005 database on my server and a SQL > Server Everywhere CTP (v3.1) database as my client app. Everything works [quoted text clipped - 9 lines] > > Thanks in advance! What is the compatibility mode on the subscriber? It should be 80 or above. SignatureHilary Cotter Director of Text Mining and Database Strategy RelevantNOISE.Com - Dedicated to mining blogs for business intelligence. This posting is my own and doesn't necessarily represent RelevantNoise's positions, strategies or opinions. 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 > I'm using a replicated SQL Server 2005 database on my server and a SQL > Server Everywhere CTP (v3.1) database as my client app. Everything works [quoted text clipped - 9 lines] > > Thanks in advance! Hilary, thanks for your reply. It WAS set to 80, but changing it to 90 seems to have no effect - subsequent sync operations result in the same error. My understanding is that this database was previously hosted by SQL Server 2000 and had only recently been moved to a SQL Server 2005 box. Any other ideas? > What is the compatibility mode on the subscriber? It should be 80 or > above. [quoted text clipped - 12 lines] >> >> Thanks in advance! We eventually figured this out (I think). The original SQL Server 2000 database had been copied to the SQL Server 2005 computer, then attached. We used the Copy Database Wizard to create a new copy of the database, which must have "converted" it to a SQL Server 2005 DB. We then published the new database and all of our problems disappeared. Hope this helps someone in the future. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2009 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.