Comments
Sort by recent activity
Thanks for the quick response.
No error from SQBServerSetup / comments
Thanks for the quick response.
No error from SQBServerSetup
You're right. Attach to process not only works but it also avoids restarting IIS. That means that I don't have to wait for the compilation step and I don't have to start the trace at the beginning of the session. I can trace just the page I am interested in.
I still don't know why it stopped working but I suppose I won't worry too much about that.
Thanks for your help. / comments
You're right. Attach to process not only works but it also avoids restarting IIS. That means that I don't have to wait for the compilation step and I don't have to start the trace at the beginnin...
That did it.
That CLSID was to another profiler that had been uninstalled quite a while ago, but apparently it did not uninstall cleanly.
I removed all of the references to that CLSID in the registry and that seems to have worked.
Many thanks / comments
That did it.
That CLSID was to another profiler that had been uninstalled quite a while ago, but apparently it did not uninstall cleanly.
I removed all of the references to that CLSID in the regist...
Thanks Jessica. I hoped that would help too but alas...
The registry keys did not exist.
I re-installed the VC++ runtime. Nothing changed.
I made sure there were no other users logged on to the host
I did get slightly different errors this time plus an additional error that may be a better clue.
Error 1)
.NET Runtime version 4.0.30319.1008 - Loading profiler failed during CoCreateInstance. Profiler CLSID: '{31535964-564b-462a-bf57-f80c986ebe25}'. HRESULT: 0x8007007e. Process ID (decimal): 2184. Message ID: [0x2504].
Error 2)
Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected.
Error 3)
.NET Runtime version 2.0.50727.5472 - Failed to CoCreate profiler.
Does the WMI error shed any additional light on this problem? / comments
Thanks Jessica. I hoped that would help too but alas...
The registry keys did not exist.
I re-installed the VC++ runtime. Nothing changed.
I made sure there were no other users logged on to the h...
When I start the profiler without ASP.NET settings specified, the status is "Connected" When I specify the ASP.NET settings, it stays "Launching 'Internet Explorer'"
I have 2 errors in the Windows application log (sorry, didn't think to look there).
1) .NET Runtime version 4.0.30319.1008 - Loading profiler failed. The profiler COM object was instantiated, but the profiler failed during its initialization callback. Profiler CLSID: '{31535964-564b-462a-bf57-f80c986ebe25}'. HRESULT: 0x80004005. Process ID (decimal): 6312. Message ID: [0x2505].
2) .NET Runtime version 2.0.50727.5472 - Failed to CoCreate profiler.
The domain user is an administrator on that box but I verified that administrators have full control on both those files.
Thanks for getting back to me. I hope that error message helps. / comments
When I start the profiler without ASP.NET settings specified, the status is "Connected" When I specify the ASP.NET settings, it stays "Launching 'Internet Explorer'"
I have 2 errors in the Windows...
I have gotten the same error a couple of times as well. There is only 1 backup job running at a given time. / comments
I have gotten the same error a couple of times as well. There is only 1 backup job running at a given time.