Error Messeage - "object reference not set to an instance of an object."

[Anonymous User]

Original User: patrick.murphy

I could use some help clarifying an issue with the error message, "object reference not set to an instance of an object."

I was building a report in Jtx 931 that apparently was to much for jtx to handle as it froze. It was a report detailing history for about twenty five jobs. While it was processing, Jtx became non responsive. I pulled up task manager and Ended Task.

After it closed, I attempted to reopen the JTX app (giving up on creating the report) and now it is coming up with the error message: "object reference not set to an instance of an object." When I try to open JTX Configuration manager I get a similiar error, "Error initialinzing JTX Admin Tool.object reference not set to an instance of an object"

Please advise on how to correct this error.

[Anonymous User · Accepted solution]

Original User: bdemers

Hi,

The error message you saw is displayed when JTX/WMX encounters an unexpected error.  It's not particularly helpful by itself, but in light of what else you wrote, there are a few things you may want to try:

Check the JTX log files.  First, make sure that the JTX Application and Config Manager are closed.  Then, in your JTX installation directory (ex., "C:\Program Files\JTX") under the "bin" directory, you should see a file named "JTXAdvancedSettings.exe".  Running this file will launch a configuration dialog similar to the screenshot attached below.  JTX's log files are stored in the "Log Folder" directory shown by this tool.  The log files recorded during/since the failure may provide a clue about what exactly is causing the error.  If not, you can also try setting the "Log Level" to "5" (verbose logging), applying your changes, restarting JTX, running until you get the error, then closing JTX and checking the latest log files for new information.

Manually clear the JTX_REPORTS and/or JTX_REPORT_QUERIES tables.  If the log files don't help, then since you were editing a report when the application crashed, it stands to reason that the problem lies with one of the tables associated with JTX reports.  You could try inspecting these tables' contents in ArcMap and removing all rows from them (...or any "suspect" rows, if anything jumps out at you).  However, I would highly recommend that you make a backup copy of both tables before going this route in case it doesn't help or makes things worse.

Restore your JTX database from a known-good backup.  This is probably safest overall, though obviously may not be ideal.

I hope some of this helps; good luck...

Brian D.

[Anonymous User]

Original User: patrick.murphy

Brian,

Your last suggestion proved to be the correct one. My supervisor suggested the same course of action and we found that inside of those two exact tables (REPORTS, and REPORT QUERIES) was a field that had been started but not completey filled out. All the values are populated with NULL. The report being generated crashed but was able to start the field. We deleted the one NULL row from each of the tables in our database. That was the fix! Thanks for your help.

[BrianDemers]

Great, that's good to hear!  If you decide to recreate the report and see the same failure again, please reply to this thread if you can.