June 15, 2004 at 11:24 am
Hi everyone, has anyone seen the following message before? I got this in my job history. I wish there was some detailed error message somewhere so that I can find how to fix the problem. And also, what do they mean by "check your network documentation"? What network documentation? I have googled this error and I have searched Microsoft and found nothing. Thanks for your help.
[SQLSTATE 01000] (Message 10055) General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11).
P.S. We are running Win 2000 with latest SP and SQL 2000 Ent.
June 15, 2004 at 11:28 am
BTW, we get a lot of connection errors. How would I troubleshoot connection errors?
June 15, 2004 at 11:38 am
I believe the following are some of the questions which come up.
who is the owner of your job ? If sa, Does the SQL Account have permissions on the remote Server ? Are you using a proxy account ?
For troubleshooting, If it is a package which has been scheduled, i try to execute the package manually to verify that the package is executing fine first.
June 15, 2004 at 12:05 pm
Hi sa24,
The job owner is sa. The job has been running consistently for years...with few interruptions here and there. We are not using a proxy account.
June 15, 2004 at 12:23 pm
Network documentation just means any documentation that your network admin may have created.
Has the SA password been changed?
Has the password for the SQLServerAgent service changed? Is the account a domain admin account or local admin account?
Are there any related error messages in the Windows Event Viewer log files (application, security, system)?
What was the job attempting to do?
Was the network down at the time?
-SQLBill
June 15, 2004 at 12:57 pm
Ah, just saw the System Event Logs and it seems that we may be having a network adapter problem here. I'll update you when I find out more info on this.
March 31, 2005 at 10:17 pm
I know it's been a while but did you ever figure out what the cause was? I'm having similar problems...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2005 at 3:24 am
I'd hazard a guess from the way it tailed off there that he'd seen the Windows Event log and noticed that the Net card was failing.
The usual fix is anywhere from updating the drivers to replacing the card or cables.
Have you got any more info on the status of the net cards on both machines?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply