Remote SP Failure

  • From a job that is kicked off on server(A) I am activating a stored procedure on server(B). This stored procedure restores a database on server(B) using the 'restore database' command.

    The job keeps failing with the following error:-

    OLE DB provider 'STREAM' reported an error. [SQLSTATE 42000] (Error 7399) [SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB Provider 'STREAM' IRowset::GetNextRows returned 0x80004005: ]. [SQLSTATE 01000] (Error 7300). The step failed.

    If I activate the SP actually on server(B) then it does work ok.

    Anyone know what the problem might be?

  • How do you map local login in serverA to remote login in ServerB? Try to set the default database for remote login is 'master'.

  • Its set up as a linked server. The remote login that it links to does have a default database of 'master'. The 'master' database also holds the SP that gets activated.

    I'm not sure that its anything to do with the login because the database does start restoring because you can see it in Enterprise Manager marked as 'Loading'. It just seems to give up!

  • Do you have ideas how long the restoration will take? Any error messages in SQL Server errorlog? Can you post the restoration statement?

  • The restoration should take about 30 minutes. When I look at the job history the Run Duration shows 27 minutes.

    The restoration statement is:-

    restore database pt_live from pt_live_ship with replace, recovery, move 'pt_conv_data' to 'd:\program files\microsoft sql server\mssql\data\pt_live_data.mdf', move 'pt_conv_log' to 'd:\program files\microsoft sql server\mssql\data\pt_live_log.ldf'

  • It seems you are activating a sp that starts a job to restore the database in remote server. Is it? If not, can you describe more details about the whole processes?

    When you saw database was in loading status, it might still in the restoration process. Do you see any error message in SQL Server errorlog?

  • Yep - all its doing is restoring a database on the remote server. There is nothing in the error log.

    I'm wondering if its just getting timed out!

  • I tested with pubs database without any problems. Can you try pubs database too?

  • Pubs also worked ok for me!

    I can work around this problem by just changing some 'jobs' around so I think I'll do that.

    Just would have been nice to know what the problem is but I think its one of those weird ones.

    Thanks.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply