ximbuex
asked on
SQL Server 2000 - 'PROCESS_TAGS' job crashes SQL, gives error "General Network Error"
The ecommerce software that we run schedules a job to run at certain intervals (currently set at 5 mins) to send out email notifications for our new customers, and their orders through our website.
Yesterday, at 10:40 the job started failing, and each time it does, the SQL server reboots.
Here's the step of the job that causes the crash:
DECLARE @dbName varchar(255)
SET @dbName = db_name()
EXEC Master.dbo.XPE_PROCESS_TAG
Here's the error it gives for the failure:
Executed as user: OURDOMAIN\Administrator. ConnectionCheckForData (CheckforData()). [SQLSTATE 01000] (Message 4) General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11). The step failed.
The SQL server reboots after the failure, which happens very quickly, but I have 15 users that are constantly connected to the database, so they are getting errors when whatever they are doing happens exactly when SQL is restarting. Not to mention, none of our ecommerce emails are being sent out.
Any help is appreciated, this is a pretty urgent problem, so I am awarding 500 points.
Yesterday, at 10:40 the job started failing, and each time it does, the SQL server reboots.
Here's the step of the job that causes the crash:
DECLARE @dbName varchar(255)
SET @dbName = db_name()
EXEC Master.dbo.XPE_PROCESS_TAG
Here's the error it gives for the failure:
Executed as user: OURDOMAIN\Administrator. ConnectionCheckForData (CheckforData()). [SQLSTATE 01000] (Message 4) General network error. Check your network documentation. [SQLSTATE 08S01] (Error 11). The step failed.
The SQL server reboots after the failure, which happens very quickly, but I have 15 users that are constantly connected to the database, so they are getting errors when whatever they are doing happens exactly when SQL is restarting. Not to mention, none of our ecommerce emails are being sent out.
Any help is appreciated, this is a pretty urgent problem, so I am awarding 500 points.
ispaleny
Are you using dbo.xp_sendmail in Master.dbo.XPE_PROCESS_TAG
ASKER
Master.dbo.XPE_PROCESS_TAG
Also, coincidentally, the same time we started having this problem, our UPS Worldship software had problems reading the database through ODBC.
Also, coincidentally, the same time we started having this problem, our UPS Worldship software had problems reading the database through ODBC.
So the problem is in C++ code of DLL binary including Master.dbo.XPE_PROCESS_TAG
ASKER
No changes have been made to the dll file used by the process, the log files that are in the same folder as the dll display this error:
12/05/2005 11:25:03 TProcessTags.GetRecordSet EVEREST Line 1: Incorrect syntax near '='
12/05/2005 11:25:03 TProcessTags.ProcessCustom
12/05/2005 11:25:03 TProcessTags.TagsProcessin
12/05/2005 11:25:03 TXpProcessTags.Execute for Log Id: 3140 EVEREST Line 1: Incorrect syntax near '='
I'm trying to avoid calling my software vendor's high $$ support line.
12/05/2005 11:25:03 TProcessTags.GetRecordSet EVEREST Line 1: Incorrect syntax near '='
12/05/2005 11:25:03 TProcessTags.ProcessCustom
12/05/2005 11:25:03 TProcessTags.TagsProcessin
12/05/2005 11:25:03 TXpProcessTags.Execute for Log Id: 3140 EVEREST Line 1: Incorrect syntax near '='
I'm trying to avoid calling my software vendor's high $$ support line.
ASKER
One of the email messages in the queue to have its tags processed had some sort of corrupt data in it, once I got rid of that once, the function ran properly. Thanks for your help.
ximbuex post "Thanks for your help." comment, but post "Answered my own question" also.
The problem was identified in XPE_PROCESS_TAGS C++ source code and design (Date: 05/12/2005 05:47PM CEST). There is a bug in his vendor's software.
ximbuex followed my responce, found DLL and its log, found data structures related to DLL and did a workaround for this in the data structures, but he is not able to prevent the error from occuring again.
Sorry, he cannot get better answer on "Microsoft SQL Server" forum.
The problem was identified in XPE_PROCESS_TAGS C++ source code and design (Date: 05/12/2005 05:47PM CEST). There is a bug in his vendor's software.
ximbuex followed my responce, found DLL and its log, found data structures related to DLL and did a workaround for this in the data structures, but he is not able to prevent the error from occuring again.
Sorry, he cannot get better answer on "Microsoft SQL Server" forum.
ASKER
If you feel like I should reward you the points I will, I just didn't think that telling me I had a bug solved the problem. It gave me a clue as what may have caused the problem, but did not offer anything to fix the problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.