Prev: Check 'instdist.out' in the install directory.
Next: sp_removeDbReplication error
From: yarddawg27 on 29 Nov 2006 11:15
SQL Server 2005 SP1, Windows 2003 Enterprise SP1

Yesterday, we lost two drives off of our production database server
Raid-5 array and had to rebuild. We were able to recover most of our
MDF and LDF files and they worked perfectly, but one database we had to
restore from tape and rool the logs forward. This particular database
had a daily snapshot replication job running against it for Reporting.
Now, we cannot resych the Publication. The publication shows up under
the Replication monitor but it will not execute. It shows the message
: Invalid object name 'dbo.syspublications'

I have tried to recreated and/or drop the publication(the puiblication
only shows up in the REPL Monitor-nowhere else) and I get a sereies of
messages like:
Msg 208, Level 16, State 1, Procedure sp_MSrepl_dropsubscription, Line
103
Invalid object name 'dbo.syssubscriptions'.
Msg 266, Level 16, State 2, Procedure sp_MSrepl_dropsubscription, Line
103
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
TRANSACTION statement is missing. Previous count = 0, current count =
1.
Msg 266, Level 16, State 2, Procedure sp_dropsubscription, Line 0
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
TRANSACTION statement is missing. Previous count = 0, current count =
1.
Msg 266, Level 16, State 2, Procedure sp_MSpublishdb, Line 0
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
TRANSACTION statement is missing. Previous count = 0, current count =
1.
Msg 266, Level 16, State 2, Procedure sp_replicationdboption, Line 0
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
TRANSACTION statement is missing. Previous count = 0, current count =
1.

We have a merge replication that is going to a thrid party vendor, so I
really do not want to stop all districbution and reconfigure. Any
ideas on how to easily remove the references to the old Snapshot
replication so I can create a new one?

From: Panos Stavroulis. on 11 Dec 2006 12:46
By the way, this is on 2005. Can I also consider database mirroring in this
case? Thanks.

"yarddawg27(a)gmail.com" wrote:

> SQL Server 2005 SP1, Windows 2003 Enterprise SP1
>
> Yesterday, we lost two drives off of our production database server
> Raid-5 array and had to rebuild. We were able to recover most of our
> MDF and LDF files and they worked perfectly, but one database we had to
> restore from tape and rool the logs forward. This particular database
> had a daily snapshot replication job running against it for Reporting.
> Now, we cannot resych the Publication. The publication shows up under
> the Replication monitor but it will not execute. It shows the message
> : Invalid object name 'dbo.syspublications'
>
> I have tried to recreated and/or drop the publication(the puiblication
> only shows up in the REPL Monitor-nowhere else) and I get a sereies of
> messages like:
> Msg 208, Level 16, State 1, Procedure sp_MSrepl_dropsubscription, Line
> 103
> Invalid object name 'dbo.syssubscriptions'.
> Msg 266, Level 16, State 2, Procedure sp_MSrepl_dropsubscription, Line
> 103
> Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
> TRANSACTION statement is missing. Previous count = 0, current count =
> 1.
> Msg 266, Level 16, State 2, Procedure sp_dropsubscription, Line 0
> Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
> TRANSACTION statement is missing. Previous count = 0, current count =
> 1.
> Msg 266, Level 16, State 2, Procedure sp_MSpublishdb, Line 0
> Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
> TRANSACTION statement is missing. Previous count = 0, current count =
> 1.
> Msg 266, Level 16, State 2, Procedure sp_replicationdboption, Line 0
> Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK
> TRANSACTION statement is missing. Previous count = 0, current count =
> 1.
>
> We have a merge replication that is going to a thrid party vendor, so I
> really do not want to stop all districbution and reconfigure. Any
> ideas on how to easily remove the references to the old Snapshot
> replication so I can create a new one?
>
>
 | 
Pages: 1
Prev: Check 'instdist.out' in the install directory.
Next: sp_removeDbReplication error