Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Lumbago
Norsk Yak Master
3271 Posts |
 Posted - 2010-10-15 : 03:02:27
|
Hi fellas,I ran in to a strange problem yesterday that I still haven't resolved. I moved a replicated database from a SQL 2000 server to a 2008 server using backup/restore and when doing the restore I used the restore wizard (didn't have my script library available) and I checked the "preserve replication setting" (WITH KEEP_REPLICATION) checkbox without the distributor being configured first. This was obviously a mistake on my part and nothing worked as I had hoped. I then removed all replication related stuff using the "Disable distribution and publishing"-wizard and everything was removed, including the publications that came with the old database that I restored. As far as I know I was back to a cleen slate.Then I configured the distributor again without a hitch but when I tried to create the publication I got a weird error. I had scripted the creation of the publication and when running the exec sp_addpublication I got the following error:Msg 2812, Level 16, State 62, Procedure sp_MSrepl_addpublication, Line 1357Could not find stored procedure ''. Has anyone seen this before...? I've googled *quite* a bit but can't seem to find anything.- LumbagoMy blog (yes, I have a blog now! just not that much content yet) -> www.thefirstsql.com |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-10-15 : 15:18:59
|
| whats result of these-- at publisherselect * from sys.tables where is_published = 1--at distributorselect * from mspublicationsalso, is original sql 2000 instance still running? or more specifically, is it still publishing?We just did a big migration (using backup/restore) and I dropped all of the publications/subscriptions, then recreated 'em on the new publisher. |
 |
|
|
Lumbago
Norsk Yak Master
3271 Posts |
Posted - 2010-10-18 : 03:35:04
|
| Thanx alot Russel, I managed to "fix" the problem by removing replication altogether by using the system stored procedure "sp_removedbreplication", and then adding it again. It did cause me quite a bit of headache prior to figuring out what the actual problem was though, so the lesson learned is to remove replication before doing migration.- LumbagoMy blog (yes, I have a blog now! just not that much content yet) -> www.thefirstsql.com |
|
|
|
|
|
|
|
|
Could not find stored procedure