Problem with Outlook Automation

Neil · Joined: 04 Oct 2007 Posts: 11

I have some code I use to create a mail message in Outlook 2003 as follows:

Dim objOutlook As Outlook.Application
Set objOutlook = CreateObject("Outlook.Application")
etc....

The code works fine everywhere except on one computer. On that computer, the
user gets Error -2147024770: "Automation error. The specified module could
not be found."

I did some searching online, and I found that most of the time when people
got that message, it was because a DLL wasn't registered. So I looked up the
reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library," and
it referred to msoutl.olb. However, that OLB file can't be registered,
because it's not an OCX or DLL.

So, any thoughts about what needs to be done here?

Thanks!

Neil

Archived from group: microsoft>public>office>developer>automation

Sue Mosher [MVP-Outlook] · Joined: 04 Oct 2007 Posts: 15

Try running Help | Detect and Repair in Outlook. It might also be worth knowing whether you can run any Outlook automation code in Outlook's own VBA environment.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $yx6.1170@newsread2.news.pas.earthlink.net...
>I have some code I use to create a mail message in Outlook 2003 as follows:
>
> Dim objOutlook As Outlook.Application
> Set objOutlook = CreateObject("Outlook.Application")
> etc....
>
> The code works fine everywhere except on one computer. On that computer, the
> user gets Error -2147024770: "Automation error. The specified module could
> not be found."
>
> I did some searching online, and I found that most of the time when people
> got that message, it was because a DLL wasn't registered. So I looked up the
> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library," and
> it referred to msoutl.olb. However, that OLB file can't be registered,
> because it's not an OCX or DLL.
>
> So, any thoughts about what needs to be done here?
>
> Thanks!
>
> Neil
>
>

Neil · Joined: 04 Oct 2007 Posts: 11

Tried Detect and Repair. Didn't find anything.

I don't think there's anything wrong with the DLL; I just think it's not
registered. Unfortunately, I don't know which DLL it is. The file referenced
in Tools | References is msoutl.olb, which, if I understand correctly, is
just a library referencing other files? So I'm not sure which DLL or OCX is
causing the problem here, or else I'd just try Regsvr32 and try and get it
registered.

Neil

"Sue Mosher [MVP-Outlook]" wrote in message @TK2MSFTNGP06.phx.gbl...
Try running Help | Detect and Repair in Outlook. It might also be worth
knowing whether you can run any Outlook automation code in Outlook's own VBA
environment.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $yx6.1170@newsread2.news.pas.earthlink.net...
>I have some code I use to create a mail message in Outlook 2003 as follows:
>
> Dim objOutlook As Outlook.Application
> Set objOutlook = CreateObject("Outlook.Application")
> etc....
>
> The code works fine everywhere except on one computer. On that computer,
> the
> user gets Error -2147024770: "Automation error. The specified module could
> not be found."
>
> I did some searching online, and I found that most of the time when people
> got that message, it was because a DLL wasn't registered. So I looked up
> the
> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library," and
> it referred to msoutl.olb. However, that OLB file can't be registered,
> because it's not an OCX or DLL.
>
> So, any thoughts about what needs to be done here?
>
> Thanks!
>
> Neil
>
>

RobinS · Joined: 04 Oct 2007 Posts: 13

I assume the user has Outlook installed? You could try reinstalling it
if possible and see if it's a problem with the installation.

Otherwise, you have to figure out which call is causing the problem,
and the only way to do that is to put a bunch of msgbox statements
in your code and run it on his computer. Maybe it's not the Outlook
calls causing your problem.

Robin S.
--------------------------------------------
"Neil" wrote in message $pQ3.2889@newsread4.news.pas.earthlink.net...
> Tried Detect and Repair. Didn't find anything.
>
> I don't think there's anything wrong with the DLL; I just think it's
> not registered. Unfortunately, I don't know which DLL it is. The file
> referenced in Tools | References is msoutl.olb, which, if I understand
> correctly, is just a library referencing other files? So I'm not sure
> which DLL or OCX is causing the problem here, or else I'd just try
> Regsvr32 and try and get it registered.
>
> Neil
>
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP06.phx.gbl...
> Try running Help | Detect and Repair in Outlook. It might also be
> worth knowing whether you can run any Outlook automation code in
> Outlook's own VBA environment.
>
> --
> Sue Mosher, Outlook MVP
> Author of Configuring Microsoft Outlook 2003
> http://www.turtleflock.com/olconfig/index.htm
> and Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
> "Neil" wrote in message
> $yx6.1170@newsread2.news.pas.earthlink.net...
>>I have some code I use to create a mail message in Outlook 2003 as
>>follows:
>>
>> Dim objOutlook As Outlook.Application
>> Set objOutlook = CreateObject("Outlook.Application")
>> etc....
>>
>> The code works fine everywhere except on one computer. On that
>> computer, the
>> user gets Error -2147024770: "Automation error. The specified module
>> could
>> not be found."
>>
>> I did some searching online, and I found that most of the time when
>> people
>> got that message, it was because a DLL wasn't registered. So I looked
>> up the
>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object
>> Library," and
>> it referred to msoutl.olb. However, that OLB file can't be
>> registered,
>> because it's not an OCX or DLL.
>>
>> So, any thoughts about what needs to be done here?
>>
>> Thanks!
>>
>> Neil
>>
>>
>
>

Sue Mosher [MVP-Outlook] · Joined: 04 Oct 2007 Posts: 15

Did you check out the other issue I suggested? Repeating:

> It might also be worth
> knowing whether you can run any Outlook automation code in Outlook's own VBA
> environment.

If not, rerun Outlook setup to make sure its VBA component is installed.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $pQ3.2889@newsread4.news.pas.earthlink.net...
> Tried Detect and Repair. Didn't find anything.
>
> I don't think there's anything wrong with the DLL; I just think it's not
> registered. Unfortunately, I don't know which DLL it is. The file referenced
> in Tools | References is msoutl.olb, which, if I understand correctly, is
> just a library referencing other files? So I'm not sure which DLL or OCX is
> causing the problem here, or else I'd just try Regsvr32 and try and get it
> registered.
>
> Neil
>
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP06.phx.gbl...
> Try running Help | Detect and Repair in Outlook. It might also be worth
> knowing whether you can run any Outlook automation code in Outlook's own VBA
> environment.
>
> "Neil" wrote in message
> $yx6.1170@newsread2.news.pas.earthlink.net...
>>I have some code I use to create a mail message in Outlook 2003 as follows:
>>
>> Dim objOutlook As Outlook.Application
>> Set objOutlook = CreateObject("Outlook.Application")
>> etc....
>>
>> The code works fine everywhere except on one computer. On that computer,
>> the
>> user gets Error -2147024770: "Automation error. The specified module could
>> not be found."
>>
>> I did some searching online, and I found that most of the time when people
>> got that message, it was because a DLL wasn't registered. So I looked up
>> the
>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library," and
>> it referred to msoutl.olb. However, that OLB file can't be registered,
>> because it's not an OCX or DLL.
>>
>> So, any thoughts about what needs to be done here?
>>
>> Thanks!
>>
>> Neil
>>
>>
>
>

Neil · Joined: 04 Oct 2007 Posts: 11

Sorry, I thought I had posted it. I guess I forgot.

Yes, when run from within Outlook, the code works. Also, if I use GetObject
to access an open instance of Outlook from another app, it works on this
person's machine. But if Outlook isn't already open, then CreateObject
fails. Interesting.

Someone in the microsoft.public.access.interopoledde newsgroup replied that
this problem has been reported several times with no explanation or
resolution, and suggested GetObject as a workaround.

Neil

"Sue Mosher [MVP-Outlook]" wrote in message @TK2MSFTNGP03.phx.gbl...
Did you check out the other issue I suggested? Repeating:

> It might also be worth
> knowing whether you can run any Outlook automation code in Outlook's own
> VBA
> environment.

If not, rerun Outlook setup to make sure its VBA component is installed.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $pQ3.2889@newsread4.news.pas.earthlink.net...
> Tried Detect and Repair. Didn't find anything.
>
> I don't think there's anything wrong with the DLL; I just think it's not
> registered. Unfortunately, I don't know which DLL it is. The file
> referenced
> in Tools | References is msoutl.olb, which, if I understand correctly, is
> just a library referencing other files? So I'm not sure which DLL or OCX
> is
> causing the problem here, or else I'd just try Regsvr32 and try and get it
> registered.
>
> Neil
>
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP06.phx.gbl...
> Try running Help | Detect and Repair in Outlook. It might also be worth
> knowing whether you can run any Outlook automation code in Outlook's own
> VBA
> environment.
>
> "Neil" wrote in message
> $yx6.1170@newsread2.news.pas.earthlink.net...
>>I have some code I use to create a mail message in Outlook 2003 as
>>follows:
>>
>> Dim objOutlook As Outlook.Application
>> Set objOutlook = CreateObject("Outlook.Application")
>> etc....
>>
>> The code works fine everywhere except on one computer. On that computer,
>> the
>> user gets Error -2147024770: "Automation error. The specified module
>> could
>> not be found."
>>
>> I did some searching online, and I found that most of the time when
>> people
>> got that message, it was because a DLL wasn't registered. So I looked up
>> the
>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library,"
>> and
>> it referred to msoutl.olb. However, that OLB file can't be registered,
>> because it's not an OCX or DLL.
>>
>> So, any thoughts about what needs to be done here?
>>
>> Thanks!
>>
>> Neil
>>
>>
>
>

RobinS · Joined: 04 Oct 2007 Posts: 13

Did you try
objOutlook = New Outlook.Application()
instead of using CreateObject?

I don't know which version of VB you're using. I used this for Excel
with VB2005.

Robin S.
---------------------------------------

"Neil" wrote in message $pQ3.422@newsread4.news.pas.earthlink.net...
> Sorry, I thought I had posted it. I guess I forgot.
>
> Yes, when run from within Outlook, the code works. Also, if I use
> GetObject to access an open instance of Outlook from another app, it
> works on this person's machine. But if Outlook isn't already open,
> then CreateObject fails. Interesting.
>
> Someone in the microsoft.public.access.interopoledde newsgroup replied
> that this problem has been reported several times with no explanation
> or resolution, and suggested GetObject as a workaround.
>
> Neil
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP03.phx.gbl...
> Did you check out the other issue I suggested? Repeating:
>
>> It might also be worth
>> knowing whether you can run any Outlook automation code in Outlook's
>> own VBA
>> environment.
>
> If not, rerun Outlook setup to make sure its VBA component is
> installed.
>
> --
> Sue Mosher, Outlook MVP
> Author of Configuring Microsoft Outlook 2003
> http://www.turtleflock.com/olconfig/index.htm
> and Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
> "Neil" wrote in message
> $pQ3.2889@newsread4.news.pas.earthlink.net...
>> Tried Detect and Repair. Didn't find anything.
>>
>> I don't think there's anything wrong with the DLL; I just think it's
>> not
>> registered. Unfortunately, I don't know which DLL it is. The file
>> referenced
>> in Tools | References is msoutl.olb, which, if I understand
>> correctly, is
>> just a library referencing other files? So I'm not sure which DLL or
>> OCX is
>> causing the problem here, or else I'd just try Regsvr32 and try and
>> get it
>> registered.
>>
>> Neil
>>
>>
>> "Sue Mosher [MVP-Outlook]" wrote in message
>> @TK2MSFTNGP06.phx.gbl...
>> Try running Help | Detect and Repair in Outlook. It might also be
>> worth
>> knowing whether you can run any Outlook automation code in Outlook's
>> own VBA
>> environment.
>>
>> "Neil" wrote in message
>> $yx6.1170@newsread2.news.pas.earthlink.net...
>>>I have some code I use to create a mail message in Outlook 2003 as
>>>follows:
>>>
>>> Dim objOutlook As Outlook.Application
>>> Set objOutlook = CreateObject("Outlook.Application")
>>> etc....
>>>
>>> The code works fine everywhere except on one computer. On that
>>> computer,
>>> the
>>> user gets Error -2147024770: "Automation error. The specified module
>>> could
>>> not be found."
>>>
>>> I did some searching online, and I found that most of the time when
>>> people
>>> got that message, it was because a DLL wasn't registered. So I
>>> looked up
>>> the
>>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object
>>> Library," and
>>> it referred to msoutl.olb. However, that OLB file can't be
>>> registered,
>>> because it's not an OCX or DLL.
>>>
>>> So, any thoughts about what needs to be done here?
>>>
>>> Thanks!
>>>
>>> Neil
>>>
>>>
>>
>>
>
>

Sue Mosher [MVP-Outlook] · Joined: 04 Oct 2007 Posts: 15

The cause may be an anti-virus program on your computer that has a feature to block Outlook scripting. The solution is to turn off the script blocking feature. You may need to contact technical support for your anti-virus program to find out how to do that.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $pQ3.422@newsread4.news.pas.earthlink.net...
> Sorry, I thought I had posted it. I guess I forgot.
>
> Yes, when run from within Outlook, the code works. Also, if I use GetObject
> to access an open instance of Outlook from another app, it works on this
> person's machine. But if Outlook isn't already open, then CreateObject
> fails. Interesting.
>
> Someone in the microsoft.public.access.interopoledde newsgroup replied that
> this problem has been reported several times with no explanation or
> resolution, and suggested GetObject as a workaround.
>
> Neil
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP03.phx.gbl...
> Did you check out the other issue I suggested? Repeating:
>
>> It might also be worth
>> knowing whether you can run any Outlook automation code in Outlook's own
>> VBA
>> environment.
>
> If not, rerun Outlook setup to make sure its VBA component is installed.

>
> "Neil" wrote in message
> $pQ3.2889@newsread4.news.pas.earthlink.net...
>> Tried Detect and Repair. Didn't find anything.
>>
>> I don't think there's anything wrong with the DLL; I just think it's not
>> registered. Unfortunately, I don't know which DLL it is. The file
>> referenced
>> in Tools | References is msoutl.olb, which, if I understand correctly, is
>> just a library referencing other files? So I'm not sure which DLL or OCX
>> is
>> causing the problem here, or else I'd just try Regsvr32 and try and get it
>> registered.
>>
>> Neil
>>
>>
>> "Sue Mosher [MVP-Outlook]" wrote in message
>> @TK2MSFTNGP06.phx.gbl...
>> Try running Help | Detect and Repair in Outlook. It might also be worth
>> knowing whether you can run any Outlook automation code in Outlook's own
>> VBA
>> environment.
>>
>> "Neil" wrote in message
>> $yx6.1170@newsread2.news.pas.earthlink.net...
>>>I have some code I use to create a mail message in Outlook 2003 as
>>>follows:
>>>
>>> Dim objOutlook As Outlook.Application
>>> Set objOutlook = CreateObject("Outlook.Application")
>>> etc....
>>>
>>> The code works fine everywhere except on one computer. On that computer,
>>> the
>>> user gets Error -2147024770: "Automation error. The specified module
>>> could
>>> not be found."
>>>
>>> I did some searching online, and I found that most of the time when
>>> people
>>> got that message, it was because a DLL wasn't registered. So I looked up
>>> the
>>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library,"
>>> and
>>> it referred to msoutl.olb. However, that OLB file can't be registered,
>>> because it's not an OCX or DLL.
>>>
>>> So, any thoughts about what needs to be done here?
>>>
>>> Thanks!
>>>
>>> Neil
>>>
>>>
>>
>>
>
>

Neil · Joined: 04 Oct 2007 Posts: 11

No, that's not it. As stated, it works with GetObject and is able to create
the e-mail. Script blocking would block that as well.

But, it turns out, the fellow in the other forum stumbled upon a solution
that resolved it. Using CreateObject while specifying the host allowed the
command to go through. Don't ask me why (not that you would have anyway
Wink

). But when the following is used:

Set objOutlook = CreateObject("Outlook.Application", "LocalHost")

the problem is resolved. Again, this is only needed on one computer. On all
the others, the second parameter isn't needed. But on this one, CreateObject
only works with the host specified. Strange.

Neil

"Sue Mosher [MVP-Outlook]" wrote in message @TK2MSFTNGP06.phx.gbl...
The cause may be an anti-virus program on your computer that has a feature
to block Outlook scripting. The solution is to turn off the script blocking
feature. You may need to contact technical support for your anti-virus
program to find out how to do that.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $pQ3.422@newsread4.news.pas.earthlink.net...
> Sorry, I thought I had posted it. I guess I forgot.
>
> Yes, when run from within Outlook, the code works. Also, if I use
> GetObject
> to access an open instance of Outlook from another app, it works on this
> person's machine. But if Outlook isn't already open, then CreateObject
> fails. Interesting.
>
> Someone in the microsoft.public.access.interopoledde newsgroup replied
> that
> this problem has been reported several times with no explanation or
> resolution, and suggested GetObject as a workaround.
>
> Neil
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP03.phx.gbl...
> Did you check out the other issue I suggested? Repeating:
>
>> It might also be worth
>> knowing whether you can run any Outlook automation code in Outlook's own
>> VBA
>> environment.
>
> If not, rerun Outlook setup to make sure its VBA component is installed.

>
> "Neil" wrote in message
> $pQ3.2889@newsread4.news.pas.earthlink.net...
>> Tried Detect and Repair. Didn't find anything.
>>
>> I don't think there's anything wrong with the DLL; I just think it's not
>> registered. Unfortunately, I don't know which DLL it is. The file
>> referenced
>> in Tools | References is msoutl.olb, which, if I understand correctly, is
>> just a library referencing other files? So I'm not sure which DLL or OCX
>> is
>> causing the problem here, or else I'd just try Regsvr32 and try and get
>> it
>> registered.
>>
>> Neil
>>
>>
>> "Sue Mosher [MVP-Outlook]" wrote in message
>> @TK2MSFTNGP06.phx.gbl...
>> Try running Help | Detect and Repair in Outlook. It might also be worth
>> knowing whether you can run any Outlook automation code in Outlook's own
>> VBA
>> environment.
>>
>> "Neil" wrote in message
>> $yx6.1170@newsread2.news.pas.earthlink.net...
>>>I have some code I use to create a mail message in Outlook 2003 as
>>>follows:
>>>
>>> Dim objOutlook As Outlook.Application
>>> Set objOutlook = CreateObject("Outlook.Application")
>>> etc....
>>>
>>> The code works fine everywhere except on one computer. On that computer,
>>> the
>>> user gets Error -2147024770: "Automation error. The specified module
>>> could
>>> not be found."
>>>
>>> I did some searching online, and I found that most of the time when
>>> people
>>> got that message, it was because a DLL wasn't registered. So I looked up
>>> the
>>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library,"
>>> and
>>> it referred to msoutl.olb. However, that OLB file can't be registered,
>>> because it's not an OCX or DLL.
>>>
>>> So, any thoughts about what needs to be done here?
>>>
>>> Thanks!
>>>
>>> Neil
>>>
>>>
>>
>>
>
>

Neil · Joined: 04 Oct 2007 Posts: 11

Yes.

"RobinS" wrote in message @comcast.com...
> Did you try
> objOutlook = New Outlook.Application()
> instead of using CreateObject?
>
> I don't know which version of VB you're using. I used this for Excel with
> VB2005.
>
> Robin S.
> ---------------------------------------
>
> "Neil" wrote in message
> $pQ3.422@newsread4.news.pas.earthlink.net...
>> Sorry, I thought I had posted it. I guess I forgot.
>>
>> Yes, when run from within Outlook, the code works. Also, if I use
>> GetObject to access an open instance of Outlook from another app, it
>> works on this person's machine. But if Outlook isn't already open, then
>> CreateObject fails. Interesting.
>>
>> Someone in the microsoft.public.access.interopoledde newsgroup replied
>> that this problem has been reported several times with no explanation or
>> resolution, and suggested GetObject as a workaround.
>>
>> Neil
>>
>> "Sue Mosher [MVP-Outlook]" wrote in message
>> @TK2MSFTNGP03.phx.gbl...
>> Did you check out the other issue I suggested? Repeating:
>>
>>> It might also be worth
>>> knowing whether you can run any Outlook automation code in Outlook's own
>>> VBA
>>> environment.
>>
>> If not, rerun Outlook setup to make sure its VBA component is installed.
>>
>> --
>> Sue Mosher, Outlook MVP
>> Author of Configuring Microsoft Outlook 2003
>> http://www.turtleflock.com/olconfig/index.htm
>> and Microsoft Outlook Programming - Jumpstart for
>> Administrators, Power Users, and Developers
>> http://www.outlookcode.com/jumpstart.aspx
>>
>> "Neil" wrote in message
>> $pQ3.2889@newsread4.news.pas.earthlink.net...
>>> Tried Detect and Repair. Didn't find anything.
>>>
>>> I don't think there's anything wrong with the DLL; I just think it's not
>>> registered. Unfortunately, I don't know which DLL it is. The file
>>> referenced
>>> in Tools | References is msoutl.olb, which, if I understand correctly,
>>> is
>>> just a library referencing other files? So I'm not sure which DLL or OCX
>>> is
>>> causing the problem here, or else I'd just try Regsvr32 and try and get
>>> it
>>> registered.
>>>
>>> Neil
>>>
>>>
>>> "Sue Mosher [MVP-Outlook]" wrote in message
>>> @TK2MSFTNGP06.phx.gbl...
>>> Try running Help | Detect and Repair in Outlook. It might also be worth
>>> knowing whether you can run any Outlook automation code in Outlook's own
>>> VBA
>>> environment.
>>>
>>> "Neil" wrote in message
>>> $yx6.1170@newsread2.news.pas.earthlink.net...
>>>>I have some code I use to create a mail message in Outlook 2003 as
>>>>follows:
>>>>
>>>> Dim objOutlook As Outlook.Application
>>>> Set objOutlook = CreateObject("Outlook.Application")
>>>> etc....
>>>>
>>>> The code works fine everywhere except on one computer. On that
>>>> computer,
>>>> the
>>>> user gets Error -2147024770: "Automation error. The specified module
>>>> could
>>>> not be found."
>>>>
>>>> I did some searching online, and I found that most of the time when
>>>> people
>>>> got that message, it was because a DLL wasn't registered. So I looked
>>>> up
>>>> the
>>>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library,"
>>>> and
>>>> it referred to msoutl.olb. However, that OLB file can't be registered,
>>>> because it's not an OCX or DLL.
>>>>
>>>> So, any thoughts about what needs to be done here?
>>>>
>>>> Thanks!
>>>>
>>>> Neil
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Sue Mosher [MVP-Outlook] · Joined: 04 Oct 2007 Posts: 15

That is strange. Good tip.

In my experience, GetObject() doesn't seem to be blocked by anti-virus programs, just CreateObject()

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $yx6.1874@newsread2.news.pas.earthlink.net...
> No, that's not it. As stated, it works with GetObject and is able to create
> the e-mail. Script blocking would block that as well.
>
> But, it turns out, the fellow in the other forum stumbled upon a solution
> that resolved it. Using CreateObject while specifying the host allowed the
> command to go through. Don't ask me why (not that you would have anyway
> Wink

). But when the following is used:
>
> Set objOutlook = CreateObject("Outlook.Application", "LocalHost")
>
> the problem is resolved. Again, this is only needed on one computer. On all
> the others, the second parameter isn't needed. But on this one, CreateObject
> only works with the host specified. Strange.
>
> Neil
>
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP06.phx.gbl...
> The cause may be an anti-virus program on your computer that has a feature
> to block Outlook scripting. The solution is to turn off the script blocking
> feature. You may need to contact technical support for your anti-virus
> program to find out how to do that.
>
>
> --
> Sue Mosher, Outlook MVP
> Author of Configuring Microsoft Outlook 2003
> http://www.turtleflock.com/olconfig/index.htm
> and Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
> "Neil" wrote in message
> $pQ3.422@newsread4.news.pas.earthlink.net...
>> Sorry, I thought I had posted it. I guess I forgot.
>>
>> Yes, when run from within Outlook, the code works. Also, if I use
>> GetObject
>> to access an open instance of Outlook from another app, it works on this
>> person's machine. But if Outlook isn't already open, then CreateObject
>> fails. Interesting.
>>
>> Someone in the microsoft.public.access.interopoledde newsgroup replied
>> that
>> this problem has been reported several times with no explanation or
>> resolution, and suggested GetObject as a workaround.
>>
>> Neil
>>
>> "Sue Mosher [MVP-Outlook]" wrote in message
>> @TK2MSFTNGP03.phx.gbl...
>> Did you check out the other issue I suggested? Repeating:
>>
>>> It might also be worth
>>> knowing whether you can run any Outlook automation code in Outlook's own
>>> VBA
>>> environment.
>>
>> If not, rerun Outlook setup to make sure its VBA component is installed.
>
>>
>> "Neil" wrote in message
>> $pQ3.2889@newsread4.news.pas.earthlink.net...
>>> Tried Detect and Repair. Didn't find anything.
>>>
>>> I don't think there's anything wrong with the DLL; I just think it's not
>>> registered. Unfortunately, I don't know which DLL it is. The file
>>> referenced
>>> in Tools | References is msoutl.olb, which, if I understand correctly, is
>>> just a library referencing other files? So I'm not sure which DLL or OCX
>>> is
>>> causing the problem here, or else I'd just try Regsvr32 and try and get
>>> it
>>> registered.
>>>
>>> Neil
>>>
>>>
>>> "Sue Mosher [MVP-Outlook]" wrote in message
>>> @TK2MSFTNGP06.phx.gbl...
>>> Try running Help | Detect and Repair in Outlook. It might also be worth
>>> knowing whether you can run any Outlook automation code in Outlook's own
>>> VBA
>>> environment.
>>>
>>> "Neil" wrote in message
>>> $yx6.1170@newsread2.news.pas.earthlink.net...
>>>>I have some code I use to create a mail message in Outlook 2003 as
>>>>follows:
>>>>
>>>> Dim objOutlook As Outlook.Application
>>>> Set objOutlook = CreateObject("Outlook.Application")
>>>> etc....
>>>>
>>>> The code works fine everywhere except on one computer. On that computer,
>>>> the
>>>> user gets Error -2147024770: "Automation error. The specified module
>>>> could
>>>> not be found."
>>>>
>>>> I did some searching online, and I found that most of the time when
>>>> people
>>>> got that message, it was because a DLL wasn't registered. So I looked up
>>>> the
>>>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library,"
>>>> and
>>>> it referred to msoutl.olb. However, that OLB file can't be registered,
>>>> because it's not an OCX or DLL.
>>>>
>>>> So, any thoughts about what needs to be done here?
>>>>
>>>> Thanks!
>>>>
>>>> Neil
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Neil · Joined: 04 Oct 2007 Posts: 11

That's interesting about GetObject working with anti-virus programs, but not
CreateObject.

In another twist here, the person on whose machine CreateObject didn't work
without "LocalHost" being specified uninstalled and reinstalled Office 2003,
and now it works fine with the original code (without "LocalHost").
Interesting.

Neil

"Sue Mosher [MVP-Outlook]" wrote in message
news:%23GWUJj$LHHA.2232@TK2MSFTNGP02.phx.gbl...
That is strange. Good tip.

In my experience, GetObject() doesn't seem to be blocked by anti-virus
programs, just CreateObject()

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"Neil" wrote in message $yx6.1874@newsread2.news.pas.earthlink.net...
> No, that's not it. As stated, it works with GetObject and is able to
> create
> the e-mail. Script blocking would block that as well.
>
> But, it turns out, the fellow in the other forum stumbled upon a solution
> that resolved it. Using CreateObject while specifying the host allowed the
> command to go through. Don't ask me why (not that you would have anyway
> Wink

). But when the following is used:
>
> Set objOutlook = CreateObject("Outlook.Application", "LocalHost")
>
> the problem is resolved. Again, this is only needed on one computer. On
> all
> the others, the second parameter isn't needed. But on this one,
> CreateObject
> only works with the host specified. Strange.
>
> Neil
>
>
> "Sue Mosher [MVP-Outlook]" wrote in message
> @TK2MSFTNGP06.phx.gbl...
> The cause may be an anti-virus program on your computer that has a feature
> to block Outlook scripting. The solution is to turn off the script
> blocking
> feature. You may need to contact technical support for your anti-virus
> program to find out how to do that.
>
>
> --
> Sue Mosher, Outlook MVP
> Author of Configuring Microsoft Outlook 2003
> http://www.turtleflock.com/olconfig/index.htm
> and Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
> "Neil" wrote in message
> $pQ3.422@newsread4.news.pas.earthlink.net...
>> Sorry, I thought I had posted it. I guess I forgot.
>>
>> Yes, when run from within Outlook, the code works. Also, if I use
>> GetObject
>> to access an open instance of Outlook from another app, it works on this
>> person's machine. But if Outlook isn't already open, then CreateObject
>> fails. Interesting.
>>
>> Someone in the microsoft.public.access.interopoledde newsgroup replied
>> that
>> this problem has been reported several times with no explanation or
>> resolution, and suggested GetObject as a workaround.
>>
>> Neil
>>
>> "Sue Mosher [MVP-Outlook]" wrote in message
>> @TK2MSFTNGP03.phx.gbl...
>> Did you check out the other issue I suggested? Repeating:
>>
>>> It might also be worth
>>> knowing whether you can run any Outlook automation code in Outlook's own
>>> VBA
>>> environment.
>>
>> If not, rerun Outlook setup to make sure its VBA component is installed.
>
>>
>> "Neil" wrote in message
>> $pQ3.2889@newsread4.news.pas.earthlink.net...
>>> Tried Detect and Repair. Didn't find anything.
>>>
>>> I don't think there's anything wrong with the DLL; I just think it's not
>>> registered. Unfortunately, I don't know which DLL it is. The file
>>> referenced
>>> in Tools | References is msoutl.olb, which, if I understand correctly,
>>> is
>>> just a library referencing other files? So I'm not sure which DLL or OCX
>>> is
>>> causing the problem here, or else I'd just try Regsvr32 and try and get
>>> it
>>> registered.
>>>
>>> Neil
>>>
>>>
>>> "Sue Mosher [MVP-Outlook]" wrote in message
>>> @TK2MSFTNGP06.phx.gbl...
>>> Try running Help | Detect and Repair in Outlook. It might also be worth
>>> knowing whether you can run any Outlook automation code in Outlook's own
>>> VBA
>>> environment.
>>>
>>> "Neil" wrote in message
>>> $yx6.1170@newsread2.news.pas.earthlink.net...
>>>>I have some code I use to create a mail message in Outlook 2003 as
>>>>follows:
>>>>
>>>> Dim objOutlook As Outlook.Application
>>>> Set objOutlook = CreateObject("Outlook.Application")
>>>> etc....
>>>>
>>>> The code works fine everywhere except on one computer. On that
>>>> computer,
>>>> the
>>>> user gets Error -2147024770: "Automation error. The specified module
>>>> could
>>>> not be found."
>>>>
>>>> I did some searching online, and I found that most of the time when
>>>> people
>>>> got that message, it was because a DLL wasn't registered. So I looked
>>>> up
>>>> the
>>>> reference (in Access 2003) to "Microsoft Outlook 11.0 Object Library,"
>>>> and
>>>> it referred to msoutl.olb. However, that OLB file can't be registered,
>>>> because it's not an OCX or DLL.
>>>>
>>>> So, any thoughts about what needs to be done here?
>>>>
>>>> Thanks!
>>>>
>>>> Neil
>>>>
>>>>
>>>
>>>
>>
>>
>
>

Mike · Joined: 04 Oct 2007 Posts: 15

"Neil" wrote:

>> Set objOutlook = CreateObject("Outlook.Application", "LocalHost")

Are there any downsides to specifically using "LocalHost" as the
server name?

I am asking because I am thinking of adding this as a preemptive fix
to the automation error. Whenever I get a bug report for "Error
-2147024770: Automation error. The specified module could not be
found.", I always raise the possibility of script blocking anti virus
software, but this would be a great if it could eliminate most of
those support calls.

-mike

Neil · Joined: 04 Oct 2007 Posts: 11

I don't see any, personally, as long as Outlook's installed locally. But
this isn't my code anyway. You might want to post your question in the forum
I referenced earlier in this thread, where the person who came up with this
posted it.

"Mike" wrote in message @4ax.com...
> "Neil" wrote:
>
>>> Set objOutlook = CreateObject("Outlook.Application", "LocalHost")
>
> Are there any downsides to specifically using "LocalHost" as the
> server name?
>
> I am asking because I am thinking of adding this as a preemptive fix
> to the automation error. Whenever I get a bug report for "Error
> -2147024770: Automation error. The specified module could not be
> found.", I always raise the possibility of script blocking anti virus
> software, but this would be a great if it could eliminate most of
> those support calls.
>
> -mike

Outlook Automation: Permissions Problem We have VB6 app which creates an Outlook Application instance and interacts with various Outlook Some of our users, who are always Outlook clients on corporate laptops (setup up with various permissions by the corporate IT department), are

Outlook automation from vb6 I am using MAPI to send e-mails from vb6 through Outlook 2003. A security message appears for every e-mail sent. (A program is trying to access e-mail I have used a product called ClickYes, but I want to control this through my vb6 applica

Automation outlook Bonjour, Je voudrais recuperer par ole automation, les adresses des contacts dans outlous, si les contacts contiennes des liste de distributions recuperer aussi les contacts de ces listes par categories Avez-vous une idée ou pouvez vous m'aider Soit en VB

Help on Outlook 2000 automation HI, Our application (frontend - VB) is using Outlook to send emails and is trapping the Close event and doing some processing before closing the mailitem. It was working well will MS Outolook Object 8.0 Library and Outlook 97. But now the customer is upgr

Problem opening Excel app via automation Hello, I have a VB6 exe front end that opens an Excel VBA app via automation. I am running it under a Virtual PC Win 2k Office 2K testbed. I have previously run it without problem on my host Win XP Pro Office 2003 system. The Excel VBA portion opens witho