Error Msg: 7221 | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Error Msg: 7221

Dear All,
I am not entirely new to SQL Server log shipping. I have successfully implemented log shipping at one of my sites. However I am having problems on this one. Anytime I run the DB restore job from the primary server the ff happens Step 1. Backup DB runs successfully
Step 2. Copy Backup runs successfully
Step 3. Executes restore sp on secondary server fails
(Error Server: Msg 7221, Level 18 State 2 Line 1)Could not relay the results of the procedure restore_SUNDB from remote server, OLE/DB provider returned message: Timeout expired) I suspect a network problem but the server replies to ping and also the backup file can easily be copied from the production server to the secondary.I have tested to see that the linked server is working. What is happening?
Hope to get your usual feedback. Regards
Kwame
Confirm the level of service pack on SQL for both the SQL Servers.
Refer to event viewer for any information. I suspect the network issues between the servers is contributing this error. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
Satya,
Both serves have service pack 6. Event viewer does not provide much info. It only says Job failed …. last step to run was step3 which means first two steps run alright. Infact, if I run the sp (say resore_db) using query analyser on the secondary server, it runs perfectly and restores the db but if I issue a remote command Exec SecondaryServer.master.dbo.restore_db from the primary server, it fails returning error 7221 as described earlier. Regards
SP6 relates to Windows NT and my question related to Service pack on SQL Servers. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
No SQL service packs on both servers. I will be suprised if that contributes to the error since a similar configurations at another site is working fine.
Yes the SQL server must be updated with latest service pack SP3a which will fix the issue. Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>