September 25, 2007 at 1:02 pm
We needed to move a few tables out onto new filegroups over the weekend on our main production DB. No problem. The database is replicated via both replication to report servers and via log shipping to DR and so both must be stopped, the jobs deleted, and then reinitialized once the move is complete (all servers in question are 2000 SP4). Replication was reinitialized with no issues. However, I can't get log shipping back. I reconfigure the job a la the instructions with no problems (I had cancelled log shipping before, deleted the maintenance plan, and restored the new backup) but it won't even do the transaction log backup; the transaction log backup portion keeps failing. This is the error that is showing up in the report file:
Microsoft (R) SQLMaint Utility (Unicode), Version [Microsoft SQL-DMO (ODBC SQLState: 08001)] Error 0: [Microsoft][ODBC SQL Server Driver][Shared Memory]Invalid connection.
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Invalid Instance()).
Can someone tell me what I am missing? Is something buried in a system table? This worked fine for months before we had to stop and try to restart it.
September 25, 2007 at 1:15 pm
:angry:
Never mind. I finally found the issue. Unbelievable:
http://support.microsoft.com/kb/326485
the directory to which we were writing the reports (a new location) had a "-S" in the path....
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply