OrenRozen
asked on
VS project I created using C# crashes on other systems with exception error 80040154
Hi,
I create a small project to open the 'Select Users or Groups' dialog window.
On my system (Windows 7 x64 + VS2010) the project is working with no problems.
On other systems (server2008 x64, server2003 x86) I get an exception error.
Maybe I'm missing(?) some files?
Thanks.
project.zip
I create a small project to open the 'Select Users or Groups' dialog window.
On my system (Windows 7 x64 + VS2010) the project is working with no problems.
On other systems (server2008 x64, server2003 x86) I get an exception error.
Maybe I'm missing(?) some files?
Thanks.
project.zip
Error - I mean error message...
ASKER
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServ ices.COMEx ception (0x80040154): Retrieving the COM class factory for component with CLSID {E064BB22-22CE-4E01-BB63-1 0EF4058CAF 9} failed due to the following error: 80040154.
at SelectUsersOrGroups_CSharp .UsersOrGr oupsFrm.bt nUsersGrou ps_Click(O bject sender, EventArgs e)
at System.Windows.Forms.Contr ol.OnClick (EventArgs e)
at System.Windows.Forms.Butto n.OnClick( EventArgs e)
at System.Windows.Forms.Butto n.OnMouseU p(MouseEve ntArgs mevent)
at System.Windows.Forms.Contr ol.WmMouse Up(Message & m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Contr ol.WndProc (Message& m)
at System.Windows.Forms.Butto nBase.WndP roc(Messag e& m)
at System.Windows.Forms.Butto n.WndProc( Message& m)
at System.Windows.Forms.Contr ol.Control NativeWind ow.OnMessa ge(Message & m)
at System.Windows.Forms.Contr ol.Control NativeWind ow.WndProc (Message& m)
at System.Windows.Forms.Nativ eWindow.Ca llback(Int Ptr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microso ft.NET/Fra mework/v2. 0.50727/ms corlib.dll
-------------------------- ---------- ----
SelectUsersOrGroups_CSharp
Assembly Version: 1.0.3829.34334
Win32 Version: 1.0.3829.34334
CodeBase: file:///D:/SelectUsersOrGr oups_CShar p.exe
-------------------------- ---------- ----
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembl y/GAC_MSIL /System.Wi ndows.Form s/2.0.0.0_ _b77a5c561 934e089/Sy stem.Windo ws.Forms.d ll
-------------------------- ---------- ----
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembl y/GAC_MSIL /System/2. 0.0.0__b77 a5c561934e 089/System .dll
-------------------------- ---------- ----
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembl y/GAC_MSIL /System.Dr awing/2.0. 0.0__b03f5 f7f11d50a3 a/System.D rawing.dll
-------------------------- ---------- ----
Interop.ObjectPickerHelper 2Lib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Interop.ObjectP ickerHelpe r2Lib.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.
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServ
at SelectUsersOrGroups_CSharp
at System.Windows.Forms.Contr
at System.Windows.Forms.Butto
at System.Windows.Forms.Butto
at System.Windows.Forms.Contr
at System.Windows.Forms.Contr
at System.Windows.Forms.Butto
at System.Windows.Forms.Butto
at System.Windows.Forms.Contr
at System.Windows.Forms.Contr
at System.Windows.Forms.Nativ
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/Microso
--------------------------
SelectUsersOrGroups_CSharp
Assembly Version: 1.0.3829.34334
Win32 Version: 1.0.3829.34334
CodeBase: file:///D:/SelectUsersOrGr
--------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembl
--------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembl
--------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembl
--------------------------
Interop.ObjectPickerHelper
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/Interop.ObjectP
--------------------------
************** 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.
vs 2010 is probably using .net frame work 4.0. This would need to be installed on any other computer to run. Did you create an installer for your program, it would grab the required dll's needed to run your program on another machine. Are you using any 3rd party controls? Another way to debug this problem is to use the RegMon utility, available for free at www.sysinternals.com. It shows you how your app uses the registry. Run it on yours and run it on the other machine and compare the two.
My 2 primary suggestions would be .net 4.0 not on the other machine, and make an installer so it grabs the dlls needed to run the app.
My 2 primary suggestions would be .net 4.0 not on the other machine, and make an installer so it grabs the dlls needed to run the app.
ASKER
- .NET 4.0 is not the problem as in Server 2008 R2 it is already installed.
- I created an installer but it didn't solve the problem.
- tried regsvr32 the .dll file but got an error that the "...entry-point DllRegisterServer was not found." BTW, I get the same error if I try to register the file on my machine where the application is working.
- regmon is no longer available and was replaced with ProcessMon. never used it and don't really know what to look for.
- I created an installer but it didn't solve the problem.
- tried regsvr32 the .dll file but got an error that the "...entry-point DllRegisterServer was not found." BTW, I get the same error if I try to register the file on my machine where the application is working.
- regmon is no longer available and was replaced with ProcessMon. never used it and don't really know what to look for.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Could you please show what the error is?