Error running app in production

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
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
Interop.Outlook
Assembly Version: 9.0.0.0
Win32 Version: 9.0.0.0
CodeBase:
file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Interop.Outlook.DLL
----------------------------------------
Zip
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase:
file:///C:/Program%20Files/Information%20Vision/Events%20Manager%202008/Zip.DLL
----------------------------------------
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1433 (REDBITS.050727-1400)
CodeBase:
file:///C:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
----------------------------------------
Infragistics2.Win.UltraWinGrid.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.UltraWinGrid.v7.3.DLL
----------------------------------------
Infragistics2.Win.UltraWinTabControl.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.UltraWinTabControl.v7.3.DLL
----------------------------------------
Infragistics2.Win.UltraWinEditors.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.UltraWinEditors.v7.3.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.

Mr
Sat Feb 16 20:18:47 CST 2008


"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.

John
Sat Feb 16 20:43:15 CST 2008

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.
>
>
>
>

kimiraikkonen
Sun Feb 17 01:33:25 CST 2008

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
present on your system.

kimiraikkonen
Sun Feb 17 01:35:03 CST 2008

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.

> 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 -

Mr
Sun Feb 17 18:24:09 CST 2008


"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.

Steve
Sun Feb 17 18:37:00 CST 2008

John wrote:

> Thanks. Is there a way to pin point which dll is it that is required?
>

From your original post:

> 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.

MisbahArefin
Sun Feb 17 20:02:00 CST 2008

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.
> >
> >
> >
> >
>
>
>

John
Sun Feb 17 20:43:21 CST 2008

Yes, Outlook 2003 is installed.

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.
>> >
>> >
>> >
>> >
>>
>>
>>

Norman
Sun Feb 17 23:37:40 CST 2008


"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.


>
> 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.
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>
>

Claes
Mon Feb 18 05:13:02 CST 2008

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.
>

John
Mon Feb 18 20:07:31 CST 2008

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.
>>
>
>

Claes
Tue Feb 19 03:30:48 CST 2008

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


"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.
>>>
>>
>>
>
>