log shipping restore failure

I don't understand, have sql 2000 on a win2000server. I set the sqlserver to
startup using the ./administrator account.
I use Windows XP on my destkop and use desktop connection to get to the
server. I log on as the administrator account.
I created a log shipping maintenance plan. As long as I am logged on to the
server, and use the SA account to register the servers in in Ent Manager.
The jobs ALL run fine. Until I log off. Once off, the jobs all go to hell..
The restores all start to fail. The backups still work, but the restores
fail. This happens every time I recreate the jobs. I get the following
erron on the restore
.....Executed as user: CHLSNT010\Administrator. sqlmaint.exe failed.
[SQLSTATE 42000] (Error 22029). The step failed.
I can't find anything on error 22029.
Can anyone help with this.
Thanks
Gordon
You'll find more details when you right click on the plan and view history
or details ..
"gordon" <gordon@.discussions.microsoft.com> wrote in message
news:EBFCF72E-CE7A-4660-9C4C-812BEE4336E6@.microsoft.com...
> I don't understand, have sql 2000 on a win2000server. I set the sqlserver
to
> startup using the ./administrator account.
> I use Windows XP on my destkop and use desktop connection to get to the
> server. I log on as the administrator account.
> I created a log shipping maintenance plan. As long as I am logged on to
the
> server, and use the SA account to register the servers in in Ent Manager.
> The jobs ALL run fine. Until I log off. Once off, the jobs all go to
hell..
> The restores all start to fail. The backups still work, but the restores
> fail. This happens every time I recreate the jobs. I get the following
> erron on the restore
> ....Executed as user: CHLSNT010\Administrator. sqlmaint.exe failed.
> [SQLSTATE 42000] (Error 22029). The step failed.
> I can't find anything on error 22029.
> Can anyone help with this.
> Thanks
> Gordon
|||Yes, there is no failure there. Only as below. Any ideas why?
"Hassan" wrote:

> You'll find more details when you right click on the plan and view history
> or details ..
> "gordon" <gordon@.discussions.microsoft.com> wrote in message
> news:EBFCF72E-CE7A-4660-9C4C-812BEE4336E6@.microsoft.com...
> to
> the
> hell..
>
>

Log shipping recover

I have changed the roles of primary and secondary servers due to server failure.
Can anyone advise how to revert back to previous main server? Are these any links available?See BOL topic:
How to set up and perform a log shipping role change (Transact-SQL)

In couple words - you have to set up log shipping again (move last backup from secondary to primary with stopping any activity of course on first one).|||If I set up log shipping with the old server, it becomes secondary. But I want to make my old server primary again.

Would I need to copy the db from current primary to old primary server, switch off the current server and switch on the old one?

log shipping load failure

Hi guys,
In my lodg shipping setup i selected the option terminate
users in database. but if the database is open the restore
is failing with following error.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
[Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
access could not be obtained because the database is in
use.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating abnormally.
is it normal?
as fars as i know with the above option selected it should
terminate the users and restore succesfully.
thanks
Biju
Why do you have connections open to the read-only DB?
What connections are open when this happens?
"biju george" wrote:

> Hi guys,
> In my lodg shipping setup i selected the option terminate
> users in database. but if the database is open the restore
> is failing with following error.
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
> access could not be obtained because the database is in
> use.
> [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
> is terminating abnormally.
> is it normal?
> as fars as i know with the above option selected it should
> terminate the users and restore succesfully.
> thanks
> Biju
>
|||yes i have opened sql query analyser
[vbcol=seagreen]
>--Original Message--
>Why do you have connections open to the read-only DB?
>What connections are open when this happens?
>
>"biju george" wrote:
terminate[vbcol=seagreen]
restore[vbcol=seagreen]
Exclusive[vbcol=seagreen]
LOG[vbcol=seagreen]
should
>.
>

log shipping load failure

Hi guys,
In my lodg shipping setup i selected the option terminate
users in database. but if the database is open the restore
is failing with following error.
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3101:
[Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive
access could not be obtained because the database is in
use.
[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE LOG
is terminating abnormally.
is it normal?
as fars as i know with the above option selected it should
terminate the users and restore succesfully.
thanks
Biju
..
Biju,
no, this is not normal. Can you double check that the option was enabled by
editing the maintenance plan. If it definitely is, then have a look at the
current activity window (locked objects, TSQL etc) on the standby server to
see which process is locking the database and what exactly it is doing. This
should give some ideas as to what the issue is.
Regards,
Paul Ibison
|||Hi paul,
yes i checked the option it is enabled.
>--Original Message--
>Biju,
>no, this is not normal. Can you double check that the
option was enabled by
>editing the maintenance plan. If it definitely is, then
have a look at the
>current activity window (locked objects, TSQL etc) on the
standby server to
>see which process is locking the database and what
exactly it is doing. This
>should give some ideas as to what the issue is.
>Regards,
>Paul Ibison
>
>.
>
|||Biju,
OK - have a look at the processes locking the database in the current
activity window (or sp_who, sp_who2, sp_lock etc).
If necessary do a trace.
Regards,
Paul Ibison

Log Shipping Issue

I had log shipping set up from serverA to serverB. One day, I start getting the automated SQL Server job failure messages.

JOB RUN: 'Log Shipping Restore for ServerA.db_nm_logshipping' was run on 10/19/2007 at 10:15:46 AM
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. Unable to retrieve steps for job Log Shipping Restore for ServerA.db_nm_logshipping.

After a few troubleshooting steps, I eventually removed and remade the maintenance plan and all associated log shipping jobs (or so I thought). For some reason, even though the new log shipping job is working properly, I'm still getting error messages from an old job.

I've ran a number of queries trying to find rogue entries still in system tables that could possibly still be trying to execute this job:

select * from dbo.log_shipping_databases where database_name = 'db_nm'
select * from dbo.log_shipping_monitor
select * from dbo.log_shipping_plan_databases where source_database = 'db_nm'
select * from dbo.log_shipping_plan_history where source_database = 'db_nm'
select * from dbo.log_shipping_plans where plan_name like '%db_nm%'
select * from dbo.log_shipping_primaries where primary_database_name = 'db_nm'
select * from dbo.log_shipping_secondaries where secondary_database_name = 'db_nm'
select * from dbo.sysdbmaintplan_databases where database_name = 'db_nm'
select * from dbo.sysdbmaintplan_jobs
select * from dbo.sysdbmaintplans where plan_name like '%db_nm%'
select * from dbo.sysjobs where name like '%db_nm%'

I couldn't find anything!

Does anyone have any idea what could be transpiring here? Any assistance would be GREATLY appreciated.

Thanks in advance!

-JoeAs a follow-up:

I ended up restarting SQL Agent. That somehow cleared out the issue.