Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ODBC Error

Status
Not open for further replies.

YL5956

MIS
Jul 11, 2001
73
US
Hi,

I'm testing our application and I'm running into this error. Has anyone encountered this and how can you resolve it? Thanks



ODBC Error Code = 01000 (General warning)

[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'master'.

The error occurred while processing an element with a general identifier of (CFSTOREDPROC), occupying document position (245:3) to (245:90).
 
This isn't really an error, but more of a "notification". It's probably in response to a statement like "use master" in your query or stored procedure.

I've had issues like this in the past, where you get an ODBC error but the message doesn't describe an actual error. What may be happening is that the SQL Server is passing a number of messages back to the ColdFusion server in response to the query. One of these messages, although not the first message, is an error. ColdFusion dutifully shows the ODBC error page, but erroneously shows the first message it got back from the SQL Server as the text of the error.

This is a tough problem to diagnose, because there's no way that I have found to see all the messages that were passed back in response to the query. You can try to change your query or stored procedure (or the server's configuration) to minimize the number of general messages that are passed back. Next, try running your query from the Query Builder (in ColdFusion Studio) or the Query Analyzer (a tool that's distributed with SQL Server) to see if you can get any more descriptive error messages. What you may have to do, ultimately, is try to figure out what the error is without the benefit of any diagnostic information.
 
This is both, interesting and scary.

I wonder if SQL has a way to log such messages. If so, that would be a solution as far as getting the whole story.

Perhaps, windows' own event viewer is the answer!

What do you think? KNOWLEDGE: Something you can give away enlessly and gain more of it in the process! - Jose Lerebours
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top