Suddenly receiving Transport error trying to start jobs

  • I'm trying to start a job on a hosted db. I've connected using SSMS, created the job and try to start it. No such luck and receive the following error every time:

    Msg 64, Level 20, State 0, Line 0

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

    I was able to start jobs previously, but I've been moved to Windows 7 and the problems began. So, I connected to a Windows 2003 server where I received the same errors. I can ping and telnet to the IP/Port; I can do everything but start a job.

    Any ideas? Support for the host site doesn't have any and neither does my team.

  • Is the job enabled? Does the job use any linked servers? Please post the results of view history of this job.

    “If your actions inspire others to dream more, learn more, do more and become more, you are a leader.” -- John Quincy Adams

  • Thanks for your reply. The job is enabled and the support staff for the host can run it successfully. There is no history when I attempt to start it since it never starts. I am sysadmin in SQL and used to be able to start jobs.

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

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