Create Jobstep failed due to tcp provider error

Question

Create Jobstep failed due to tcp provider error

Hollyz

SSCommitted

Points: 1763
More actions
February 20, 2008 at 9:22 am

#182354

Hi I am getting this type of error when I try to create a job step. I created this on the sql server box itself and I also try to create the job step through remotely. Either way, I am getting the same strange error:
'Create failed for Jobstep 'Query sys'
An exception occured while executing a Transact-sql statement or batch.
(Microsoft.SQLServer.ConnectionInfo)
A transport-level error has occurred when sending the request to the server. (provider: TCP provider, error: 0 - An establishe connection was aborted by the software in your host machine.) (Microsoft SQL Server, Error: 10053)
It is SQL Serve 2005 x64 Edition with SP2 on Windows Serveer 2003 R2.
I believe it is clustered.

Viewing 5 posts - 1 through 4 (of 4 total)

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

Jack Corbett SSC Guru Points: 184394 More actions · Answer 1

Have you checked the Error Logs (Sql Server and Windows)? If it is clustered (you should know this), is it an Active-Active or Active-Passive cluster?

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Hollyz SSCommitted Points: 1763 More actions · Answer 2

It is Active- Passive. Do you have any idea why I 'm getting that type of error message. And on top of that, the steps on the jobs get deleted automatically once I get that error.

So the Job will have empty steps.

Jack Corbett SSC Guru Points: 184394 More actions · Answer 3

I have only seen this error when connecting to remote SQL Servers and there have been network issues. If you are getting this error when on the SQL Server console I would wonder if there is some kind of issue with the shared disk array for the cluster.

You really need to look at the SQL Error logs and the Windows Event log to see if you are getting any other errors.

Another idea is to run Profiler when you are creating/modifying the job to see what's happening.

Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question

Hollyz SSCommitted Points: 1763 More actions · Answer 4

Thanks for suggestions. I would definetely pass those information to the network team to let them look at the clustering configurations. I also have used the sql profiler to track the problem, but nothing came up that seems to be causeing it.