SQLNexus 3.0 will not StartUp

Mar 16, 2011 at 10:03 PM

I was attempting to load a trace file using SQLNexus 3.0 and it exited with error code -21.  I decided to download the latest version of RMLUtilities and now it will not start up.  When I double click sqlnexus.exe the login screen flashes and the with windows disappears and nothing happens.  I am unable to find anything in the log files.

Workstation running Windows XP, SQL Server 2005 for the repository if I can get connected.

Any ideas would be welcome.

Coordinator
Mar 23, 2011 at 8:17 PM

Could you try and import the profiler trace using ReadTrace.exe and post the output of the ReadTrace log file for me to look at?

Mar 24, 2011 at 8:07 PM

Below is the output file but my other question is why SQLNexus flashes the connect screen and then disappears is cloud of smoke?


03/24/11 15:01:44.621 [0X00001730] Readtrace a SQL Server trace processing utility.
Version 9.01.0109 built for x86.
Copyright (c) Microsoft Corporation 1997-2008. All rights reserved.
03/24/11 15:01:44.652 [0X00001730] Number of processors: 2
03/24/11 15:01:44.652 [0X00001730]     Active proc mask: 0x00000003
03/24/11 15:01:44.652 [0X00001730]         Architecture: 0
03/24/11 15:01:44.652 [0X00001730]            Page size: 4096
03/24/11 15:01:44.652 [0X00001730]         Highest node: 0
03/24/11 15:01:44.652 [0X00001730]         Processor(s): 0x00000001 Function units: Separated
03/24/11 15:01:44.652 [0X00001730]         Package mask: 0x00000003
03/24/11 15:01:44.652 [0X00001730]         Processor(s): 0x00000002 Function units: Separated
03/24/11 15:01:44.652 [0X00001730]           Processors: 0x00000003 assigned to Numa node: 0
03/24/11 15:01:44.652 [0X00001730] -Ic:\temp\mkdb2_trace\sqlnexus.trc
03/24/11 15:01:44.652 [0X00001730] -oc:\temp\mkdb2_trace\output.txt
03/24/11 15:01:44.652 [0X00001730] -f
03/24/11 15:01:44.652 [0X00001730] -Smck790L4086\sql2k8
03/24/11 15:01:44.652 [0X00001730] Using language id (LCID): 1024 [English_United States.1252] for character formatting
03/24/11 15:01:44.652 [0X00001730] Attempting to cleanup existing RML files from previous execution
03/24/11 15:01:44.668 [0X00001730] Using extended RowsetFastload synchronization
03/24/11 15:01:44.668 [0X00001730] Establishing initial database connection:
03/24/11 15:01:44.668 [0X00001730] Server: (local)
03/24/11 15:01:44.668 [0X00001730] Database: PerfAnalysis
03/24/11 15:01:44.668 [0X00001730] Authentication: Windows
03/24/11 15:01:44.809 [0X00001730] Using SQL Client version 10
03/24/11 15:01:44.809 [0X00001730] Creating or clearing the performance database
03/24/11 15:01:45.605 [0X00001730] Processing file: c:\Temp\trace\sqlnexus.trc (SQL 2000)
03/24/11 15:01:45.605 [0X00001730] Validating core events exist
03/24/11 15:01:45.605 [0X00001730] Validating necessary events exist for analysis
03/24/11 15:01:45.605 [0X00001730] WARNING: Statement level analysis is disabled because the SP:StmtStarting/SP:StmtCompleted event(s) do not contain the following required columns: OBJID, NESTLEVEL
03/24/11 15:01:45.605 [0X00001730] WARNING: Event 45 (SP_STMT_END_EVENT_CLASS) does not contain the following recommended column(s): INTDATA
03/24/11 15:01:45.605 [0X00001730] WARNING: The quality of the performance analysis may be substantially affected due to the lack of recommended columns.  Consult the help file for the recommended set of trace events and columns.
03/24/11 15:01:45.762 [0X00001730] Events Read: 1000 Queued: 1000 Processed/sec: 0
03/24/11 15:01:45.777 [0X00001730] Events Read: 2000 Queued: 1998 Processed/sec: 2
03/24/11 15:01:45.793 [0X00001730] Events Read: 3000 Queued: 2998 Processed/sec: 2
03/24/11 15:01:46.262 [0X00001730] Processing file: c:\Temp\trace\sqlnexus_1.trc (SQL 2000)
03/24/11 15:01:46.277 [0X00001730] Events Read: 4000 Queued: 3885 Processed/sec: 115
03/24/11 15:01:46.309 [0X00001730] Events Read: 5000 Queued: 4885 Processed/sec: 115
03/24/11 15:01:46.324 [0X00001730] Events Read: 6000 Queued: 5885 Processed/sec: 115
03/24/11 15:01:46.512 [0X00001730] Processing file: c:\Temp\trace\sqlnexus_2.trc (SQL 2000)
03/24/11 15:01:46.590 [0X00001730] Events Read: 7000 Queued: 6880 Processed/sec: 120
03/24/11 15:01:46.621 [0X00001730] Events Read: 8000 Queued: 7880 Processed/sec: 120
03/24/11 15:01:46.668 [0X00001730] Events Read: 9000 Queued: 8858 Processed/sec: 142
03/24/11 15:01:47.184 [0X00001730] Processing file: c:\Temp\trace\sqlnexus_3.trc (SQL 2000)
03/24/11 15:01:47.605 [0X00001730] Processing file: c:\Temp\trace\sqlnexus_4.trc (SQL 2000)
03/24/11 15:01:47.824 [0X00001730] WARNING: PROFILER_MESSAGE_CLASS - Some trace events have not been reported to SQL Profiler because the server has reached its maximum amount of available memory for the process.
03/24/11 15:01:47.824 [0X00001730] Treating as STOP event
03/24/11 15:01:47.824 [0X00001730] Reads completed - Global Error Status 0xffffffeb
03/24/11 15:01:47.840 [0X00001730] Shutting down the worker thread message queues.
03/24/11 15:01:47.840 [0X00001730] Waiting for the worker threads to complete final actions.
03/24/11 15:01:48.027 [0X00001730] Performing general cleanup actions.
03/24/11 15:01:48.027 [0X00001730] Total Events Processed: 15714
03/24/11 15:01:48.027 [0X00001730]  Total Events Filtered: 0
03/24/11 15:01:48.027 [0X00001730] Parse errors: 0
03/24/11 15:01:48.027 [0X00001730] *******************************************************************************
* ReadTrace encountered one or more ERRORS. An error condition typically      *
* stops processing early and the ReadTrace output may be unusable.            *
* Review the log file for details.                                            *
*******************************************************************************
03/24/11 15:01:48.027 [0X00001730] ***** ReadTrace exit code: -21

 

Coordinator
Mar 29, 2011 at 5:03 PM

Can you import the trace using fn_trace_gettable function? If yes, are other trace files failing to import as well?

Looks like the profiler trace had some dropped events due to load on the server instance from which the data was being collected.

I have not encountered the login screen disappearing like that. Could you reinstall SQL Nexus 3.0 and check if the issue persists? If yes, please attache the SQL Nexus log file.

Mar 29, 2011 at 7:38 PM

Not sure what has happened.  It is working now.  Thanks for the assistance and the tool.

Coordinator
Mar 29, 2011 at 10:11 PM

Good to know that it is working.

May 3, 2011 at 9:56 PM

The issue I tracked down was between SQLNexus and an app I run called RocketDock.  If RocketDock is running there is a slim chance that SQLNexus will start.  With RocketDock closed SQLNexus starts every time.  I'm not sure of the conflict but closing out of RocketDock fixes the issue.

Thanks for SQLNexus it is very handy.