I have been having a problem when I try starting the SQL Profiler. I am running the SQL Server 2005 - Developer edition. I get a message box from Microsoft .NET Framework saying:
Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.
Could not load file or assembly 'ConnectionDlg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its
The details listed under the Details button are:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'ConnectionDlg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
File name: 'ConnectionDlg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
at Microsoft.SqlServer.Management.UI.Profiler.SplashScreen.OptimizeLoadTime()
at Microsoft.SqlServer.Management.UI.Profiler.SplashScreen.splashTimer_Elapsed(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
PROFILER90
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase: file:///C:/PROGRA~1/MICROS~4/90/Tools/Binn/PROFIL~1.EXE
-
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.91
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.91_x-ww_0de56c07/msvcm80.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
pfui90
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/PROGRA~1/MICROS~4/90/Tools/Binn/pfui90.DLL
-
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
******
I have tried uninstalling SQL Server completely as well as .NET2 and then reinstalling them. There is still no change. The rest of the program appears to function fine. Only the Profiler is affected.
Any help would be greatly appreciated.
Thank you for your time.
Terry.
verify this file exists...
C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ConnectionDlg.dll
The namespace of this assembly is Microsoft.SqlServer.Management.UI.ConnectionDlg and I do NOT see this assembly in my GAC, so just ensure its there.
|||Greetings,I have checked and yes, the file does exist. It is version 9.0.1399.0 (Assembly Version: 9.0.242.0) and file size is: 981,720 bytes.|||then I am assuming that onLoad of Profiler it is looking in the wrong binn directory for the assemblies it uses. No clue at this point dude.|||
No problem. At least you did try so for that I do thank you. Besides, for most problems, it's the simple or obvious answer that solves it. This one so far has been the rarity.
|||Greetings,I had found out the problem with the Profiler. It turned out that the problem was a bad link file. I would click on the link to start the Profiler, but it would not set the path environment correctly. So, the Profiler was not able to find the needed files. I had deleted the link and made a new one and it worked fine after that. Definitely a strange cause to the problem.
Thanks for the help.
