April 14, 2011 at 12:43 pm
There is a job which is basically executing a DTS package failing everyday sometime between 10:00 PM to 11:00 PM. This job is scheduled to run every 5 minutes. Please find below the error message generated.
Error string: [DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error.
Check your network documentation.Error source: Microsoft OLE DB Provider for SQL Server
I found some links on the internet but wasn't able to get to the root cause. Could you kindly share your thoughts on what exactly might be the issue here. What are the items you may check. By the by, this is
SQL Server 2000.
M&M
April 14, 2011 at 1:12 pm
Just a guess, but I'd be checking the server logs and talking to your network people.
This doesn't look like a SQL Server specific error.
April 15, 2011 at 12:08 am
But only this job fails sometime between 10:00 PM to 11:00 PM.
It is scheduled to run every 5 minutes though.
M&M
April 15, 2011 at 12:18 am
Here is the problem, we can't see from here what you see from there. We have no idea what the job is doing that fails, we have no idea what other jobs are scheduled to run at the same time during this period of time, we can't review the server and sql logs to see what other error(s) may be present in them.
Based on this, please tell me how we are supposed to tell you what is wrong? You haven't provided the detail we really need to be able to tell what may be the problem. I pointed you toward the error logs, have you taken the time to read them to see what else may be going on? Have you checked with the people I suggested to see if they had any ideas as to what may be causing the problem?
Now, if you take the time to tell us more about the problem, provide more information regarding the error(s) that may be occurring, we may be able to provide you with much better answers to your problem.
April 15, 2011 at 2:16 am
mohammed moinudheen (4/15/2011)
But only this job fails sometime between 10:00 PM to 11:00 PM.It is scheduled to run every 5 minutes though.
General network error: Errr, okay. A nice vague windows error.
What happens on the network between 10 and 11?
What's the job do?
What's the network do?
Have you tried to communicate with all the target servers between 10 and 11?
This is a point in time issue... you need to get your hands on said server, with network admin support, during the point in time. A transient error is one of the hardest to troubleshoot. You and the error need to get involved simultaneously, which means hanging around pinging the server at 10 and seeing if you can find where exactly the problem is inside of that one hour.
It won't be fun, it'll take a lot of guesses, and it's going to take (most likely) a lot of time. You're also going to need other resources. I'm sorry there's no easy solution to this but you're just going to have to hammer out what you can. When you have any information other than this generic error, we'll be happy to help you with a bunch of assumptions that might be accurate.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
April 15, 2011 at 2:38 am
Thanks Lynn and Craig, I got a lot of points from your comments.
I didn't mean to trouble you folks though, it is kind of tough to work on these types of errors
as there is no silver bullet for the solution. I kind of got pressurized by the application team
folks for a quick root cause analysis. Anyways, your comments would point me to the right direction.
Thank you 🙂
M&M
April 15, 2011 at 5:15 am
mohammed moinudheen (4/15/2011)
I kind of got pressurized by the application teamfolks for a quick root cause analysis.
Just a quick note. Never let the app team pressure you into a quickie diagnosis. Tell them you understand there is a problem and you are working on tracking down the issue, but don't give them an answer without being sure.
Why do I give this advice?
Because if you give them the quick answer and you are wrong, your reputation will always be tainted by that. Every time you are right about a problem after that, especially if the error is on the application side, they will not listen to you. The response they'll tell their boss is "Oh, he doesn't know what he's talking about."
There are a lot of urgent things in this world, but you need to make it clear to the people-who-want-the-answer-yesterday that you're working as fast as you can but there are a lot of things to look at and giving them a quickie answer might actually slow down the troubleshooting process.
April 15, 2011 at 10:37 am
I agree with you Brandie. Thank you.
M&M
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply