SQL Nexus Tool

Commented Unassigned: startup failed with a "domain approbation failure" message [25655]

4lex11s — Tue, 19 Aug 2014 10:16:16 GMT

Hello,

After installation of all dependencies, unfortunately I cannot start your wonderful SQL Nexus Tool.

__"La relation d’approbation entre le domaine principal et le domaine approuvé a échoué."__
a conceivable translation:
__"The trust relationship between this workstation and the primary domain failed"__
I did not launched with runas cmd, I didn't have right for Reset-ComputerMachinePassword

FYI:
* I use a personal domain account with administrator right on workstation .
* Microsoft SQL Server 2014 (or a try with Microsoft SQL Server 2012)
* Microsoft 4.5.1
* Windows 7SP1
* ReportViewer 2014 Runtime

Kind regards
Comments: ** Comment from web user: 4lex11s **

Hello,
Unfortunately, I had the same error with a non-domain admin account ... (consequently SID is different)

Thanks for your reply
Kind regards

Closed Unassigned: SQL Diag utility not executing on Windows 2012 [25610]

amitban — Thu, 14 Aug 2014 10:06:41 GMT

Afternoon.

I am trying to run the SQLDIAG data collector utility on a Windows 2012 server to import into SQLnexus. but get the following error. We have tried everything from a security perspective..still no luck.

Please assist if possible.
Comments: Issue being faced due to lack permissions.

Commented Unassigned: Problem with SqlNexus [25616]

amitban — Thu, 14 Aug 2014 10:05:06 GMT

hi, i from colombia and have a problem with sqlnexus ! https://drive.google.com/file/d/0BzDQ7VwG2c-XTUliVVVudjhLUkU/edit?usp=sharing

and this https://drive.google.com/file/d/0BzDQ7VwG2c-XMmxtdUE3RnlQMmc/edit?usp=sharing

could answer in Spanish if possible, thanks
Comments: ** Comment from web user: amitban **

It looks like you are missing some tables in your SQL Nexus database. Did you import all the data collected by SQLDIAG and were there any errors during the import?

Commented Unassigned: startup failed with a "domain approbation failure" message [25655]

amitban — Thu, 14 Aug 2014 10:01:39 GMT

Are you facing the same issue on other workstations as well? Could you try using the tool with a local windows account (non-domain) which has administrative rights on the machine and report back if you still fail with the same issue. The log file shows the following failure:
System.Security.Principal.NTAccount.TranslateToSids

So want to rule out the domain access here.

Created Unassigned: startup failed with a "domain approbation failure" message [25655]

4lex11s — Fri, 08 Aug 2014 07:21:58 GMT

Reviewed: Release 4.0.0.64 (Jul 31, 2014)

jawili — Thu, 31 Jul 2014 21:09:41 GMT

Rated 5 Stars (out of 5) - Thank you for getting this update out, there were several items that you could tell were partly developed. Excellent release!

Created Unassigned: Problem with SqlNexus [25616]

wilcheshell — Wed, 16 Jul 2014 22:02:00 GMT

New Post: Wilcheshell

wilcheshell — Wed, 16 Jul 2014 15:46:34 GMT

Commented Unassigned: SQL Diag utility not executing on Windows 2012 [25610]

amitban — Tue, 15 Jul 2014 17:30:49 GMT

No issues.

You should have permissions to execute an OpenCluster API call. The most common reason for this API call failing is lack of permissions for the account running SQLDIAG to execute the API call successfully.

HTH

Commented Unassigned: SQL Diag utility not executing on Windows 2012 [25610]

WynandCoetzee — Tue, 15 Jul 2014 16:47:15 GMT

Thanks for the feedback and the associated link. I definitely think it is a permissions issue. I used another utility to gather system information on the cluster and the the "passive" node information is not in the rapport. So I believe that somewhere in the SQLDIAG utility it tries and connects to the cluster components and is prohibited.

Apology for logging this issue as SQLNexus problem , for some reason I thought I must do it here :-)

Thanks for helping though.

Commented Unassigned: SQL Diag utility not executing on Windows 2012 [25610]

amitban — Tue, 15 Jul 2014 11:25:28 GMT

This is not a SQL Nexus related issue. SQLDIAG is a tool that ships with SQL Server and is supported by Microsoft Support. You could either post this error on the SQL Server forum or open a support case if the information below does not help you resolve the issue.

I also see that you have pressed CTRL+C. If you don't quit the data collection using CTRL+C, then does it continue to collect the data that you need? If you want you could share the configuration file with the changes that you have made (SQLDiagPerfStats_Detailed_Trace2012.XML) with me using my contact details on my blog (TroubleshootingSQL.com) and I can assist you further.

Also, please check if this applies to you. Instead of 10, it will be 11 for SQL Server 2012.
http://blogs.msdn.com/b/sqlserverfaq/archive/2011/04/06/sqldiag-there-are-no-instances-of-version-10-on-this-computer.aspx

Created Unassigned: SQL Diag utility not executing on Windows 2012 [25610]

WynandCoetzee — Tue, 15 Jul 2014 10:51:07 GMT

Commented Unassigned: SQLNexus is not displaying the reports after import the sql diag data [25593]

amitban — Mon, 14 Jul 2014 06:13:28 GMT

Hi,

I could not see the reports in reports section [i.e left side of the sql nexus tool screen] after importing the sql diag data.

I am using SqlNexus4.0.0.64 tool to import the SQL 2008 R2 captured scripts.

The reports section is displaying only [Instructions] and [SQL Perf Main] reports.

Appreciate your help.

Thanks
Raj Kumar
Comments: ** Comment from web user: amitban **

Capture a profiler trace to see if the stored procedures are being executed to return the results for the report. Also what is the size of your SQL Nexus database? The bottleneck analysis and wait statistics report rely on the *_SQL_200x_Perf_Stats_Startup.OUT file.

Commented Unassigned: SQLNexus is not displaying the reports after import the sql diag data [25593]

SPRaj — Thu, 10 Jul 2014 04:49:30 GMT

Hi Amit,

Appreciate your help.

Is there any workaround on above issue to display the reports.

Thanks
Raj Kumar

Commented Unassigned: SQLNexus is not displaying the reports after import the sql diag data [25593]

SPRaj — Tue, 08 Jul 2014 07:49:56 GMT

Thank you Amitban for quick response.

I can see the reports by category in when I click on [sql perf main] in reports section. The reports are appearing on right side of the screen with blue color but when i click on the report e.g. bottleneck analysis nothing is happening. When I mouse over the report in blue color, the link is not changing to hand and when I click nothing is happening.

Please refer the attached screen shot.

Thanks
Raj Kumar

Closed Unassigned: ReadTrace Crash(Allocation state of block is not valid) [25536]

amitban — Tue, 08 Jul 2014 02:21:45 GMT

Hello

* Used TraceCaptureDef.sql to generate my server-side trace. This is part of RML utilities.
* Attempted run of readTrace via SQLNexus (and the shell) to convert my .trc files into .rml files for replay.
* I receive the same error regarding simplememorycache regardless of which machine I use, regardless of processor architecture.

Help hugely appreciated.

```
06/06/14 12:29:04.873 [0X000030A0] Events Read: 1000 Queued: 768 Processed/sec: 628
06/06/14 12:29:05.391 [0X000030A0] Events Read: 2000 Queued: 1611 Processed/sec: 438
06/06/14 12:29:05.424 [0X000030A0] Events Read: 3000 Queued: 2557 Processed/sec: 481
06/06/14 12:29:05.632 [0X000030A0] Events Read: 4000 Queued: 3276 Processed/sec: 641
06/06/14 12:29:06.031 [0X000030A0] Events Read: 5000 Queued: 4270 Processed/sec: 478
06/06/14 12:29:06.039 [0X000030A0] Events Read: 6000 Queued: 5270 Processed/sec: 475
06/06/14 12:29:06.041 [0X00003D80] A serious error condition (0x7FB0B07F == pBlock->m_lLastAlloc) has been encountered.
Allocation state of block is not valid
File: c:\sqlee\rml_4_rtw\common\cpp\simplememorycache.cpp
Line: 2651
Return Address: 0x000000013FE978C6
Function: SMCFree
06/06/14 12:29:06.041 [0X00003D80] Default Module: 0x000000013FDC0000 (C:\Program Files\Microsoft Corporation\RMLUtils\readtrace.exe)
06/06/14 12:29:06.042 [0X00003D80] ln 0x000000013FE9ABAF
06/06/14 12:29:06.043 [0X00003D80] ln 0x000000013FE9BE65
06/06/14 12:29:06.044 [0X00003D80] ln 0x000000013FE978C6
06/06/14 12:29:06.045 [0X00003D80] ln 0x000000013FE79B62
06/06/14 12:29:06.046 [0X00003D80] ln 0x000000013FE790D3
06/06/14 12:29:06.048 [0X000030A0] Events Read: 7000 Queued: 6263 Processed/sec: 477
06/06/14 12:29:06.054 [0X00003D80] ln 0x000000013FE7950B
06/06/14 12:29:06.054 [0X00003D80] ln 0x000000013FE95324
06/06/14 12:29:06.055 [0X00003D80] ln 0x000000013FE9FC66
06/06/14 12:29:06.057 [0X00003D80] ln 0x000000013FEA3C8B
06/06/14 12:29:06.058 [0X00003D80] ln 0x000000013FE4D620
06/06/14 12:29:06.058 [0X00003D80] ln 0x000000013FE4377E
06/06/14 12:29:06.058 [0X00003D80] ln 0x000000013FE4AF8D
06/06/14 12:29:06.059 [0X00003D80] ln 0x000000013FE90EAA
06/06/14 12:29:06.061 [0X00003D80] ln 0x000007FECD744F7F
06/06/14 12:29:06.061 [0X00003D80] ln 0x000007FECD745126
06/06/14 12:29:06.062 [0X00003D80] ln 0x00000000779D652D
06/06/14 12:29:06.062 [0X00003D80] ln 0x0000000077C0C541
06/06/14 12:29:06.062 [0X00003D80] Frames: 17 (Return code: 17)
```
Comments: Workaround provided

Commented Unassigned: ReadTrace Crash(Allocation state of block is not valid) [25536]

amitban — Tue, 08 Jul 2014 02:21:22 GMT

Use -T171 parameter to workaround the issue.

Commented Unassigned: SQLNexus is not displaying the reports after import the sql diag data [25593]

amitban — Tue, 08 Jul 2014 02:20:08 GMT

The reports are available by clicking on SQL Perf Main. If the data is available to show the report from the imported data, then a drill through report link will be available on SQL Perf Main report page.

Created Unassigned: SQLNexus is not displaying the reports after import the sql diag data [25593]

SPRaj — Mon, 07 Jul 2014 15:45:04 GMT

New Comment on "Sql2005PerfStatsScript"

HotRats — Thu, 03 Jul 2014 18:29:16 GMT

There are other useful SQLDiag arguments - see http://msdn.microsoft.com/en-us/library/ms162833.aspx. For example, adding /L /E +00:200 /R /Q to your .cmd file registers (/R) sqldiag as a service (that way you don't have to keep the command window open), restarts SQLDIAG every 20 minutes (/L /E +00:20), and quietly (/Q) overwrites the old output (every 20 minutes). The arguments /L /E +00:200 /R /Q are useful when you don't know when the problem will start and/or a system may not have enough disk space (for a SQLDiag that traces). Also consider /N and /C. One thing that a correctly configured pssdiag configuration manager's pssdiag will (that these scripts won't) create is DeleteOldTrcFiles.cmd.