When one of your MATH statements bombs out you can typically see it in either sysinternals' Debug View or in the System Message Monitor on the navigator bar (It appears that SDE 10 no longer puts this link on the navbar by default). The thing is it just gives you the error message not the actual statement that was run against the database.
Make a backup of any edited files before editing.
- Open C:\Program Files (x86)\BMC\Service Desk Express\Application Server\csbr_xml_generator2.aspx in a text editor. The location might be slightly different for you depending on where you installed SDE and if your running a 32 bit versus a 64 bit OS.
- Do a find for string sSQL = "";
- We need to move the definition of this variable higher up in the page so that it will be available in the error handling portion of the page.
- Go ahead and comment out line by putting // in front of it.You may want to put a comment above it to tell why it was commented out. You code should look something like the following.
//David Sullivan Commented out the next line as we are moving outside the TRY block.
//string sSQL = ""; - Now search upwards for the following text.
System.Data.IDataReader oDR = null; //#52224
try
{ - We need to put the definition of out sSQL there. So put a new line before the word try and edit it to look like the following.
System.Data.IDataReader oDR = null; //#52224
//David Sullivan moved the definition of sSQL outside the try block so that it can be used inside the catch block.
string sSQL = "";
try
{ - Now we need to actually append the sSQL to our error output so that we can see it better in Debug.
- Search back downwards and find the following.
GenerateErrorMessage(ruleName, "Math", ex.Message + " " + sSQL, string.Empty, string.Empty); - Go ahead and edit that section to read like the following.
//David Sullivan We need to add the sSQL to the the error message.
//GenerateErrorMessage(ruleName, "Math", ex.Message, string.Empty, string.Empty);
GenerateErrorMessage(ruleName, "Math", ex.Message + " " + sSQL, string.Empty, string.Empty); - Now just save your changes and from now on the errors will have the actual SQL statement appended after the error message.
