2005 Linked Server Connection failure

  • Hi Guys,

    We have a strange problem since moving our SQL Server 2005 onto a new Windows 2008 box.

    The schduled jobs which use a Linked Server connection outside our domain no longer 'remember' the connection details beyond about 4 minutes. The jobs can be manually kicked off and succeed on the second time of trying.

    If I schdule any of these jobs to run at intervals of less that 5 minutes they work, but beyond that magic time they fail.

    I am just guessing that it is the connection details that are 'being forgotten' as I can't think of anything else.

    Any ideas anyone ???

    Below is the error that is posted in the job history

    Message

    Executed as user: nnnnn\Administrator. Cannot initialize the data source object of OLE DB provider "SQLNCLI" for linked server "hoswebdb01". [SQLSTATE 42000] (Error 7303) OLE DB provider "SQLNCLI" for linked server "hoswebdb01" returned message "Unable to complete login process due to delay in opening server connection". [SQLSTATE 01000] (Error 7412). The step failed.

  • Does this look like your current configuration?

    [A] ->

    [A] - Windows Server 2008 w/ SQL 2005

    - Windows Server 2003 w/ SQL 2005. Target of linked server from and on a different trusted domain.

    Is the network connectivity between the [A] and working normally otherwise?

    Anything in the event logs on [A] or related to TCP/IP?

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

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