Comments
Sort by recent activity
Michael Clark wrote: »
Would it be possible to update to the latest version SQL Prompt 9.0.6?
Unfortunately, I do not have the license to do so. However, a colleague of mine found a workaround. Add TrustServerCertificate=True to the Additional Connection Parameters tab in the Connect to Server dialog. / comments
Michael Clark wrote: »
Would it be possible to update to the latest version SQL Prompt 9.0.6?
Unfortunately, I do not have the license to do so. However, a colleague of mine found a workarou...
@Jessica R
No, LineLevelBlacklist doesn't seem to be working. / comments
@Jessica R
No, LineLevelBlacklist doesn't seem to be working.
Yes. I have the PDB. / comments
Yes. I have the PDB.
@Jessica R I think I figured it out. Placing my assembly into LineLevelBlackList.xml was not necessary. Neither was increasing permissions on my assembly in AssemblyInfo.cs I just added HtmlAgilityPack into the file and that did the trick.
The odd thing is that I do not have source code for this assembly. It's an open source library and I was just referencing the DLL.
My LineLevelBlackList.xml now has these entries:
<!-- Assemblies with known issues -->
<assemblyName>Newtonsoft.Json</assemblyName>
<assemblyName>log4net</assemblyName>
<!-- Add your assemblies to blacklist below this line -->
<assemblyName>HtmlAgilityPack</assemblyName>
Perhaps you should add HtmlAgilityPack to the list of assemblies with known issues. / comments
@Jessica R I think I figured it out. Placing my assembly into LineLevelBlackList.xml was not necessary. Neither was increasing permissions on my assembly in AssemblyInfo.cs I just added HtmlAgi...
@Jessica R I meant to get back to this earlier. I am back to the "Operation could destabilize the runtime" error. I've added the assembly, which contains the code in the screenshot lives, to the LineLevelBlacklist.xml and it seems to ignore the file.
I've also downgraded to Ants Profiler 8.6 and it's showing the error there too. And I've added the assembly to %localappdata%\Red Gate\ANTS Performance Profiler 8\LineLevelBlacklist.xml.
Is it possible that runtime destabilization happens somewhere else and the code that's displayed is a red herring? / comments
@Jessica R I meant to get back to this earlier. I am back to the "Operation could destabilize the runtime" error. I've added the assembly, which contains the code in the screenshot lives, to the...
@Jessica R That worked! I added the Security rules attribute and it did the trick. Thank you very much.
w3p.exe still crashes if Enable Inlining is checked, but I don't think I need that . I was also able to turn Async Awareness on.
I'll have to look into that assembly and see what security settings might be going on. Any ideas of what I should be looking at? / comments
@Jessica R That worked! I added the Security rules attribute and it did the trick. Thank you very much.
w3p.exe still crashes if Enable Inlining is checked, but I don't think I need that . I wa...
@Jessica R
So I tried suggestions you made. Unfortunately it didn't help. I disabled "Profile with async awareness" and disabled all options in "Additional profiler options".
Alternatively I got either crashes or "Operation could destabilize the runtime" error. I am not sure what leads to this error.
One thing that does work is line level profiling until the crash (which happens shortly after I press Start Profiling).
So I am at a loss. Any other suggestions? [image] / comments
@Jessica R
So I tried suggestions you made. Unfortunately it didn't help. I disabled "Profile with async awareness" and disabled all options in "Additional profiler options".
Alternatively I got ...
Hi @Jessica R
I cleared out the event log and recreated the crash. Event log had the following entries:
.NET Runtime version 4.0.30319.0 - The profiler was loaded successfully. Profiler CLSID: '{F487E236-8315-45AF-833E-DF0967B1E79A}'. Process ID (decimal): 364. Message ID: [0x2507].
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The configuration information of the performance library "C:\Windows\System32\perfts.dll" for the "TermService" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
Faulting application name: w3wp.exe, version: 10.0.15063.0, time stamp: 0xacce422f
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x3636e10b
Faulting process id: 0x16c
Faulting application start time: 0x01d30fde87182b0a
Faulting application path: C:\WINDOWS\SysWOW64\inetsrv\w3wp.exe
Faulting module path: unknown
Report Id: b7193eb4-f29b-47fa-bf35-5ba0de499542
Faulting package full name:
Faulting package-relative application ID:
I chose to debug the w3p crash using a new copy of Visual Studio and it pinpointed the following line with the Stack Overflow exception:
result = engine.Invoke(outputType, renderOptions.ComponentName, properties).ToString(); [image] / comments
Hi @Jessica R
I cleared out the event log and recreated the crash. Event log had the following entries:
.NET Runtime version 4.0.30319.0 - The profiler was loaded successfully. Profiler CLSID: '{...
Hi @Jessica R
I cleared out the Event Viewer, repeated the test and it crashed again. The Event Viewer had the following things (separated by carriage returns):
.NET Runtime version 4.0.30319.0 - The profiler was loaded successfully. Profiler CLSID: '{F487E236-8315-45AF-833E-DF0967B1E79A}'. Process ID (decimal): 364. Message ID: [0x2507].
The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code.
The configuration information of the performance library "C:\Windows\System32\perfts.dll" for the "TermService" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
Faulting application name: w3wp.exe, version: 10.0.15063.0, time stamp: 0xacce422f
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x3636e10b
Faulting process id: 0x16c
Faulting application start time: 0x01d30fde87182b0a
Faulting application path: C:\WINDOWS\SysWOW64\inetsrv\w3wp.exe
Faulting module path: unknown
Report Id: b7193eb4-f29b-47fa-bf35-5ba0de499542
Faulting package full name:
Faulting package-relative application ID:
I then selected to "debug" the w3p crash using a new copy of Visual Studio and it pinpointed this line of code in our code base:
result = engine.Invoke(outputType, renderOptions.ComponentName, properties).ToString();
The error was Stack Overflow. [image]
As I mentioned before none of these errors happen if I profile without line level stats. / comments
Hi @Jessica R
I cleared out the Event Viewer, repeated the test and it crashed again. The Event Viewer had the following things (separated by carriage returns):
.NET Runtime version 4.0.30319.0 - ...
eddie davis wrote:
Can you please check to see if you have the following SQL Prompt Options enabled?
SQL Prompt 5 ->Options ->Format ->Data statements ->New Lines (to the right) ->Place the following on a new line: ->Join condition and Align join condition with JOIN.
If you have "Join condition" and "Align join condition with JOIN" options enabled, can you please disable these options and recheck to see if your join statement follows the style you have set?
Those items were already disabled. Just for fun, I re-enabled them, then disabled them again - unfortunately no result. / comments
eddie davis wrote:
Can you please check to see if you have the following SQL Prompt Options enabled?
SQL Prompt 5 ->Options ->Format ->Data statements ->New Lines (to the right) ->Place the foll...