Forum Discussion

RayMilhon's avatar
RayMilhon
Copper Contributor
Feb 05, 2024
Solved

Error I've been getting 2 days.

I'm getting this error on a couple of SQL Server agent jobs that have been running for years.  To the best of my knowledge nothing on the network has changed.  Any idea what I can check for.  The queries in the steps work fine.

 

 

 

 

TITLE: Microsoft.SqlServer.Smo
------------------------------

Start failed for Job 'PHI_Pharmacy_monthy_for_Kathy_Green'.

For help, click: https://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=16.100.47021.0&Evtsrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Start+Job&LinkId=20476

------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

------------------------------

A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (Microsoft SQL Server, Error: 64)

For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-64-database-engine-error

------------------------------

The specified network name is no longer available

------------------------------
BUTTONS:

OK
------------------------------

  • You should dig into the SQL Job and find out the code that it is executed. Probably it has a linked server call and the destination server wasn't available at the time

    Regards
    Javier

2 Replies

  • You should dig into the SQL Job and find out the code that it is executed. Probably it has a linked server call and the destination server wasn't available at the time

    Regards
    Javier
    • RayMilhon's avatar
      RayMilhon
      Copper Contributor

      Apparently.   It's working now through no effort of mine. 

Resources