| Groups | Blog | Home |
dotnet interop : Error running app in production
[quoted text, click to view] "John" <John@nospam.infovis.co.uk> wrote in message news:%23N3uAIQcIHA.4072@TK2MSFTNGP02.phx.gbl... > Hi > > I created a setup file of my app and remotely installed it on a clients > machine. The app bombs at start-up with the error; > > Error while initializing application: Retrieving the COM class factory for > component with CLSID {0006F03A-0000-0000-C000-000000000046} failed due to > the following error: 8007007e. > > The application also gave a stack trace which is given below at the end. > What's more there is no JIT debugger on the target system. What is the > problem and how can I proceed from here specially when I have little or > now way to debug the app on the target system. > > Many Thanks > > Regards > > > > Stack Trace > ======== > > See the end of this message for details on invoking > just-in-time (JIT) debugging instead of this dialog box. > > ************** Exception Text ************** > System.NullReferenceException: Object reference not set to an instance of > an object. --------------------------------------- What it means is that you have a Object reference to a DLL, and the DLL is not there on the target machine where the applications is running, so it can't create an Object derived from the DLL that is not there. As opposed to this DLL being on your development machine where the Object can be derived from the reference you had set in the development project to the DLL. Or the DLL is there. but it's dependant upon another DLL that is not there. You need to find out what that DLL is that is not on the client's machine, and you include it in your setup package so that it gets installed with your application. You never assume that a client machine is going to have all components you need for your application to run properly. You must make sure your setup package has all the components that must be installed with the application in the application's setup packet and install them no matter what, even if they are all ready there.
[quoted text, click to view]
On Feb 17, 4:43=A0am, "John" <J...@nospam.infovis.co.uk> wrote: > Thanks. Is there a way to pin point which dll is it that is required? > > Thanks again. > > Regards > > > > > You need to find out what that DLL is that is not on the client's machin= e, > > and you include it in your setup package so that it gets installed with > > your application. You never assume that a client machine is going to hav= e > > all components you need for your application to run properly. You must > > make sure your setup package has all the components that must be install= ed > > with the application in the application's setup packet and install them = no > > matter what, even if they are all ready there.- Hide quoted text - > > - Show quoted text - First you must see which DLLs you have referenced doing: To remove a reference in Visual Basic 1-In Solution Explorer, double-click the My Project node for the project. 2-In the Project Designer, click the References tab. 3-In the References list, locate the library that you referenced. Then post the dll name or search it on the client machine which is
[quoted text, click to view]
On Feb 17, 9:33=A0am, kimiraikkonen <kimiraikkone...@gmail.com> wrote: > On Feb 17, 4:43=A0am, "John" <J...@nospam.infovis.co.uk> wrote: > > > > > > > Thanks. Is there a way to pin point which dll is it that is required? > > > Thanks again. > > > Regards > > > > You need to find out what that DLL is that is not on the client's mach= ine, > > > and you include it in your setup package so that it gets installed wit= h > > > your application. You never assume that a client machine is going to h= ave > > > all components you need for your application to run properly. You must= > > > make sure your setup package has all the components that must be insta= lled > > > with the application in the application's setup packet and install the= m no > > > matter what, even if they are all ready there.- Hide quoted text - > > > - Show quoted text - > First you must see which DLLs you have referenced doing: > > To remove a reference in Visual Basic Correction: Do these steps to see the dll that's refenced, not to remove it. [quoted text, click to view] > 1-In Solution Explorer, double-click the My Project node for the
> project. > > 2-In the Project Designer, click the References tab. > > 3-In the References list, locate the library that you referenced. > > Then post the dll name or search it on the client machine which is > present on your system.- Hide quoted text - > > - Show quoted text -
Hi
I created a setup file of my app and remotely installed it on a clients machine. The app bombs at start-up with the error; Error while initializing application: Retrieving the COM class factory for component with CLSID {0006F03A-0000-0000-C000-000000000046} failed due to the following error: 8007007e. The application also gave a stack trace which is given below at the end. What's more there is no JIT debugger on the target system. What is the problem and how can I proceed from here specially when I have little or now way to debug the app on the target system. Many Thanks Regards Stack Trace ======== See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.NullReferenceException: Object reference not set to an instance of an object. at EMS.frmClients.RefrshDropDowns(Boolean FirstTime) at EMS.frmClients.BindFieldstoDataSource() at EMS.frmClients.frmClients_Load(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.SetVisibleCore(Boolean value) at System.Windows.Forms.Form.SetVisibleCore(Boolean value) at System.Windows.Forms.Control.Show() at EMS.frmMain.OpenForm(String x, Int32 id) at EMS.frmMain.frmMain_Load(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Windows.Forms.Form.OnLoad(EventArgs e) at System.Windows.Forms.Form.OnCreateControl() at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible) at System.Windows.Forms.Control.CreateControl() at System.Windows.Forms.Control.WmShowWindow(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ScrollableControl.WndProc(Message& m) at System.Windows.Forms.ContainerControl.WndProc(Message& m) at System.Windows.Forms.Form.WmShowWindow(Message& m) at System.Windows.Forms.Form.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll ---------------------------------------- IV Assembly Version: 1.0.2968.12064 Win32 Version: 1.0.2968.12064 CodeBase: file:///C:/Program%20Files/IV/Events%20Manager%202008/IV.exe ---------------------------------------- Microsoft.VisualBasic Assembly Version: 8.0.0.0 Win32 Version: 8.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- System.Configuration Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll ---------------------------------------- System.Xml Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll ---------------------------------------- System.Runtime.Remoting Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Runtime.Remoting/2.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll ---------------------------------------- Infragistics2.Win.v7.3 Assembly Version: 7.3.20073.38 Win32 Version: 7.3.20073.38 CodeBase: file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Infragistics2.Win.v7.3.DLL ---------------------------------------- Infragistics2.Shared.v7.3 Assembly Version: 7.3.20073.38 Win32 Version: 7.3.20073.38 CodeBase: file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Infragistics2.Shared.v7.3.DLL ---------------------------------------- Infragistics2.Win.UltraWinToolbars.v7.3 Assembly Version: 7.3.20073.38 Win32 Version: 7.3.20073.38 CodeBase: file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Infragistics2.Win.UltraWinToolbars.v7.3.DLL ---------------------------------------- Infragistics2.Win.UltraWinExplorerBar.v7.3 Assembly Version: 7.3.20073.38 Win32 Version: 7.3.20073.38 CodeBase: file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Infragistics2.Win.UltraWinExplorerBar.v7.3.DLL ---------------------------------------- Infragistics2.Win.UltraWinStatusBar.v7.3 Assembly Version: 7.3.20073.38 Win32 Version: 7.3.20073.38 CodeBase: file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Infragistics2.Win.UltraWinStatusBar.v7.3.DLL ---------------------------------------- Infragistics2.Win.Misc.v7.3 Assembly Version: 7.3.20073.38 Win32 Version: 7.3.20073.38 CodeBase: file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Infragistics2.Win.Misc.v7.3.DLL ---------------------------------------- System.Design Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll ---------------------------------------- Accessibility Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400) CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll ---------------------------------------- System.Data
Thanks. Is there a way to pin point which dll is it that is required?
Thanks again. Regards [quoted text, click to view] > You need to find out what that DLL is that is not on the client's machine, > and you include it in your setup package so that it gets installed with > your application. You never assume that a client machine is going to have > all components you need for your application to run properly. You must > make sure your setup package has all the components that must be installed > with the application in the application's setup packet and install them no > matter what, even if they are all ready there. > > > >
[quoted text, click to view]
John wrote: > Thanks. Is there a way to pin point which dll is it that is required? > From your original post: [quoted text, click to view] > Error while initializing application: Retrieving the COM class > factory for component with CLSID > {0006F03A-0000-0000-C000-000000000046} failed due to the following > error: 8007007e. > ************** Exception Text ************** > System.NullReferenceException: Object reference not set to an > instance of an object. > at EMS.frmClients.RefrshDropDowns(Boolean FirstTime) Presumably RefrshDropdowns(Boolean FirstTime) is a method you wrote, and that's where the error occured. Taking a good look at that method may give you a hint of which object reference was not set, from which you can deduce which dll is missing. It is apparently a COM object, and COM dlls are not always included automatically by install builders for .Net apps.
a little bit of google revealed that's definitely the CLSID for Outlook. The
trivial explanation: do you have Outlook installed on your clients machine? -- Misbah Arefin [quoted text, click to view] "John" wrote:
> Thanks. Is there a way to pin point which dll is it that is required? > > Thanks again. > > Regards > > > You need to find out what that DLL is that is not on the client's machine, > > and you include it in your setup package so that it gets installed with > > your application. You never assume that a client machine is going to have > > all components you need for your application to run properly. You must > > make sure your setup package has all the components that must be installed > > with the application in the application's setup packet and install them no > > matter what, even if they are all ready there. > > > > > > > > > >
[quoted text, click to view] "John" <John@nospam.infovis.co.uk> wrote in message news:e%23$lZ7QcIHA.4684@TK2MSFTNGP06.phx.gbl... > Thanks. Is there a way to pin point which dll is it that is required? > What I would do is go back to development project and look at all the DLL(s) that are being referenced make sure they are included in the setup package. I would also use a DLL dependency checker on each DLL to what other DLL(s) a given DLL is dependant upon and include those DLL(s) in the setup project. One thing you can do in your project is put Try/Catches in your code, and if the Exception.InnerText is not null the display that message, as that message will help you pin point things.
[quoted text, click to view] "John" <John@nospam.infovis.co.uk> wrote in message news:ugHdHgdcIHA.4936@TK2MSFTNGP03.phx.gbl... > Yes, Outlook 2003 is installed. And you are using Outlook200? in your developing box? If it is Outlook2007, then that is where the proble is from. Or is this app a win desktop app run by a logged in user? Does the user have his Outlook profile set up before running your app? Are you automating Outlook from your Win form app? More information will definitely help identify possible problems. [quoted text, click to view] >
> Thanks > > Regards > > "Misbah Arefin" <MisbahArefin@discussions.microsoft.com> wrote in message > news:E71E40B5-0CD0-4CFD-B298-B9A021CA3D3F@microsoft.com... >>a little bit of google revealed that's definitely the CLSID for Outlook. >>The >> trivial explanation: do you have Outlook installed on your clients >> machine? >> >> -- >> Misbah Arefin >> >> >> >> "John" wrote: >> >>> Thanks. Is there a way to pin point which dll is it that is required? >>> >>> Thanks again. >>> >>> Regards >>> >>> > You need to find out what that DLL is that is not on the client's >>> > machine, >>> > and you include it in your setup package so that it gets installed >>> > with >>> > your application. You never assume that a client machine is going to >>> > have >>> > all components you need for your application to run properly. You must >>> > make sure your setup package has all the components that must be >>> > installed >>> > with the application in the application's setup packet and install >>> > them no >>> > matter what, even if they are all ready there. >>> > >>> > >>> > >>> > >>> >>> >>> > >
Yes, Outlook 2003 is installed.
Thanks Regards [quoted text, click to view] "Misbah Arefin" <MisbahArefin@discussions.microsoft.com> wrote in message news:E71E40B5-0CD0-4CFD-B298-B9A021CA3D3F@microsoft.com... >a little bit of google revealed that's definitely the CLSID for Outlook. >The > trivial explanation: do you have Outlook installed on your clients > machine? > > -- > Misbah Arefin > > > > "John" wrote: > >> Thanks. Is there a way to pin point which dll is it that is required? >> >> Thanks again. >> >> Regards >> >> > You need to find out what that DLL is that is not on the client's >> > machine, >> > and you include it in your setup package so that it gets installed with >> > your application. You never assume that a client machine is going to >> > have >> > all components you need for your application to run properly. You must >> > make sure your setup package has all the components that must be >> > installed >> > with the application in the application's setup packet and install them >> > no >> > matter what, even if they are all ready there. >> > >> > >> > >> > >> >> >>
That CLSID is present in Outlook 2003 (I have it on my machine)
The error 0x8007007E is ERROR_MOD_NOT_FOUND ("The specified module could not be found") wrapped in a COM HRESULT Start by checking the registry on the deployment machine to ensure that the COM object is registered correctly. If it's there try using OleView.exe (just copy it from your dev machine) to create an instance of it. In OleView it should be in All Objects under the name "Microsoft Office Outlook" (there might be more than one entry with that name so make sure you try the correct one) /claes [quoted text, click to view] "Norman Yuan" <FakeName@FakeEmail.Not> wrote in message news:en8iiBfcIHA.1168@TK2MSFTNGP02.phx.gbl... > > "John" <John@nospam.infovis.co.uk> wrote in message > news:ugHdHgdcIHA.4936@TK2MSFTNGP03.phx.gbl... >> Yes, Outlook 2003 is installed. > > > And you are using Outlook200? in your developing box? If it is > Outlook2007, then that is where the proble is from. Or is this app a win > desktop app run by a logged in user? Does the user have his Outlook > profile set up before running your app? Are you automating Outlook from > your Win form app? More information will definitely help identify possible > problems. >
Hi
In OleView when I try to expand the Microsoft Outlook 8.0 Object Library node by clicking on the + sign I get the below error; CoGetClassObject failed. The specified module could not be found. Severity: SEVERITY_ERROR, facility: FACILITY_WIN32 ($8007007E) What can I do from here? Thanks Regards [quoted text, click to view] "Claes Bergefall" <claes.bergefall@nospam.nospam> wrote in message news:eWgk78hcIHA.4332@TK2MSFTNGP06.phx.gbl... > That CLSID is present in Outlook 2003 (I have it on my machine) > The error 0x8007007E is ERROR_MOD_NOT_FOUND ("The specified module could > not be found") wrapped in a COM HRESULT > > Start by checking the registry on the deployment machine to ensure that > the COM object is registered correctly. If it's there try using > OleView.exe (just copy it from your dev machine) to create an instance of > it. In OleView it should be in All Objects under the name "Microsoft > Office Outlook" (there might be more than one entry with that name so make > sure you try the correct one) > > /claes > > "Norman Yuan" <FakeName@FakeEmail.Not> wrote in message > news:en8iiBfcIHA.1168@TK2MSFTNGP02.phx.gbl... >> >> "John" <John@nospam.infovis.co.uk> wrote in message >> news:ugHdHgdcIHA.4936@TK2MSFTNGP03.phx.gbl... >>> Yes, Outlook 2003 is installed. >> >> >> And you are using Outlook200? in your developing box? If it is >> Outlook2007, then that is where the proble is from. Or is this app a win >> desktop app run by a logged in user? Does the user have his Outlook >> profile set up before running your app? Are you automating Outlook from >> your Win form app? More information will definitely help identify >> possible problems. >> > >
Are you sure the name is Microsoft Outlook 8.0 Object Library? If you have
Outlook 2003 installed it should be version 11.0, not 8.0. On my machine the name is Microsoft.Office.Outlook. Anyway, it sounds like something is wrong with the installation. Try reinstalling Outlook (uninstall all previous ones first). /claes [quoted text, click to view] "John" <John@nospam.infovis.co.uk> wrote in message news:eMbivwpcIHA.4332@TK2MSFTNGP06.phx.gbl... > Hi > > In OleView when I try to expand the Microsoft Outlook 8.0 Object Library > node by clicking on the + sign I get the below error; > > CoGetClassObject failed. > The specified module could not be found. > Severity: SEVERITY_ERROR, facility: FACILITY_WIN32 ($8007007E) > > What can I do from here? > > Thanks > > Regards > > "Claes Bergefall" <claes.bergefall@nospam.nospam> wrote in message > news:eWgk78hcIHA.4332@TK2MSFTNGP06.phx.gbl... >> That CLSID is present in Outlook 2003 (I have it on my machine) >> The error 0x8007007E is ERROR_MOD_NOT_FOUND ("The specified module could >> not be found") wrapped in a COM HRESULT >> >> Start by checking the registry on the deployment machine to ensure that >> the COM object is registered correctly. If it's there try using >> OleView.exe (just copy it from your dev machine) to create an instance of >> it. In OleView it should be in All Objects under the name "Microsoft >> Office Outlook" (there might be more than one entry with that name so >> make sure you try the correct one) >> >> /claes >> >> "Norman Yuan" <FakeName@FakeEmail.Not> wrote in message >> news:en8iiBfcIHA.1168@TK2MSFTNGP02.phx.gbl... >>> >>> "John" <John@nospam.infovis.co.uk> wrote in message >>> news:ugHdHgdcIHA.4936@TK2MSFTNGP03.phx.gbl... >>>> Yes, Outlook 2003 is installed. >>> >>> >>> And you are using Outlook200? in your developing box? If it is >>> Outlook2007, then that is where the proble is from. Or is this app a win >>> desktop app run by a logged in user? Does the user have his Outlook >>> profile set up before running your app? Are you automating Outlook from >>> your Win form app? More information will definitely help identify >>> possible problems. >>> >> >> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |