SOLVED

Error I've been getting 2 days.

Copper Contributor

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=Microsof...

------------------------------
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-err...

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

The specified network name is no longer available

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

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

2 Replies
best response confirmed by RayMilhon (Copper Contributor)
Solution
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

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

1 best response

Accepted Solutions
best response confirmed by RayMilhon (Copper Contributor)
Solution
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

View solution in original post