Problem with email generated from VB.NET using Outlook

[Siv]

Hi,
A little while ago I asked if anyone could help me with how to create an
email using MS Outlook that contained an embedded picture file.
Thanks to Jay Harlow I was able to get this working using a code example
from http://www.outlookcode.com/d/code/htmlimg.htm that details the
procedure and with a bit of tweaking I managed to get it working really
well.

I now find that there is a new user on a laptop that always gets an error at
the point where the code creates an Outlook object. I have included all the
interop DLLs with the application and for all users, the code works, except
this one.

The code snippet that is having the problem is:

' Outlook objects
Dim objApp as Outlook.Applica tion
Dim l_Msg As MailItem
Dim colAttach As Outlook.Attachm ents
Dim l_Attach As Outlook.Attachm ent
Dim oSession As MAPI.Session

' CDO objects
Dim oMsg As MAPI.Message
Dim oAttachs As MAPI.Attachment s
Dim oAttach As MAPI.Attachment
Dim colFields As MAPI.Fields
Dim oField As MAPI.Field

Dim strEntryID As String

' create new Outlook MailItem
Set objApp = CreateObject("O utlook.Applicat ion","") '<== PROBLEM OCCURS
HERE!!
Set l_Msg = objApp.CreateIt em(olMailItem)
' add graphic as attachment to Outlook message
' change path to graphic as needed
Set colAttach = l_Msg.Attachmen ts
Set l_Attach = colAttach.Add(" c:\test\graphic .jpg")
l_Msg.Close olSave
strEntryID = l_Msg.EntryID
Set l_Msg = Nothing
etc ...

The user has the same DLLs installed in the application folder as all the
other users, the difference is that they all had MS Office 2000 and then
upgraded to Outlook 2003 as part of the Small Business Server 2003
installation, where the new user only ever had Outlook 2003.

I am using the following DLLs:
=============== =============== =
DLL Version
Interop.MAPI.dl l 1.21.0.0
Interop.Microso ft.Office.Core. dll 2.3.0.0
Interop.Outlook .dll 9.2.0.0
=============== =============== ==

Can anyone explain why the CreateObject command is failing on that one
machine? It's driving me nuts!

--
Siv
Martley, Near Worcester, UK.

[William LaMartin]

I have read that the script blockers in Antivirus programs may block calls
to CreateObject("O utlook.Applicat *ion"). I know Norton Antivirus has such a
script blocker, for example. I did a quick Google search on
CreateObject("O utlook.Applicat *ion") and antivirus that produced some
interesting messages.

Perhaps that is the problem.
"Siv" <ms**********@r emoveme.sivill. com> wrote in message
news:e%******** *******@TK2MSFT NGP11.phx.gbl.. .

Hi,
A little while ago I asked if anyone could help me with how to create an
email using MS Outlook that contained an embedded picture file.
Thanks to Jay Harlow I was able to get this working using a code example
from http://www.outlookcode.com/d/code/htmlimg.htm that details the
procedure and with a bit of tweaking I managed to get it working really
well.

I now find that there is a new user on a laptop that always gets an error
at the point where the code creates an Outlook object. I have included
all the interop DLLs with the application and for all users, the code
works, except this one.

The code snippet that is having the problem is:

' Outlook objects
Dim objApp as Outlook.Applica tion
Dim l_Msg As MailItem
Dim colAttach As Outlook.Attachm ents
Dim l_Attach As Outlook.Attachm ent
Dim oSession As MAPI.Session

' CDO objects
Dim oMsg As MAPI.Message
Dim oAttachs As MAPI.Attachment s
Dim oAttach As MAPI.Attachment
Dim colFields As MAPI.Fields
Dim oField As MAPI.Field

Dim strEntryID As String

' create new Outlook MailItem
Set objApp = CreateObject("O utlook.Applicat ion","") '<== PROBLEM OCCURS
HERE!!
Set l_Msg = objApp.CreateIt em(olMailItem)
' add graphic as attachment to Outlook message
' change path to graphic as needed
Set colAttach = l_Msg.Attachmen ts
Set l_Attach = colAttach.Add(" c:\test\graphic .jpg")
l_Msg.Close olSave
strEntryID = l_Msg.EntryID
Set l_Msg = Nothing
etc ...

The user has the same DLLs installed in the application folder as all the
other users, the difference is that they all had MS Office 2000 and then
upgraded to Outlook 2003 as part of the Small Business Server 2003
installation, where the new user only ever had Outlook 2003.

I am using the following DLLs:
=============== =============== =
DLL Version
Interop.MAPI.dl l 1.21.0.0
Interop.Microso ft.Office.Core. dll 2.3.0.0
Interop.Outlook .dll 9.2.0.0
=============== =============== ==

Can anyone explain why the CreateObject command is failing on that one
machine? It's driving me nuts!

--
Siv
Martley, Near Worcester, UK.

[Siv]

William,
That's something I wouldn't have thought of. The user has McAfee antivirus
on her machine, and the other users have Sophos Antivirus, she also runs MS
Antispyware beta which they don't either as the Sophos suite we have
installed on the desktop machines covers both antivirus and spyware threats.

Have you heard that McAfee does this??

Is it just the script blocking part or some other aspect of McAfee?

Thanks for your help, it gives me an avenue to pursue.
--
Siv
Martley, Near Worcester, UK.
"William LaMartin" <la******@tampa bay.rr.com> wrote in message
news:eq******** *******@TK2MSFT NGP14.phx.gbl.. .

I have read that the script blockers in Antivirus programs may block calls
to CreateObject("O utlook.Applicat *ion"). I know Norton Antivirus has such
a script blocker, for example. I did a quick Google search on
CreateObject(" Outlook.Applica t*ion") and antivirus that produced some
interesting messages.

Perhaps that is the problem.
"Siv" <ms**********@r emoveme.sivill. com> wrote in message
news:e%******** *******@TK2MSFT NGP11.phx.gbl.. .

Hi,
A little while ago I asked if anyone could help me with how to create an
email using MS Outlook that contained an embedded picture file.
Thanks to Jay Harlow I was able to get this working using a code example
from http://www.outlookcode.com/d/code/htmlimg.htm that details the
procedure and with a bit of tweaking I managed to get it working really
well.

I now find that there is a new user on a laptop that always gets an error
at the point where the code creates an Outlook object. I have included
all the interop DLLs with the application and for all users, the code
works, except this one.

The code snippet that is having the problem is:

' Outlook objects
Dim objApp as Outlook.Applica tion
Dim l_Msg As MailItem
Dim colAttach As Outlook.Attachm ents
Dim l_Attach As Outlook.Attachm ent
Dim oSession As MAPI.Session

' CDO objects
Dim oMsg As MAPI.Message
Dim oAttachs As MAPI.Attachment s
Dim oAttach As MAPI.Attachment
Dim colFields As MAPI.Fields
Dim oField As MAPI.Field

Dim strEntryID As String

' create new Outlook MailItem
Set objApp = CreateObject("O utlook.Applicat ion","") '<== PROBLEM OCCURS
HERE!!
Set l_Msg = objApp.CreateIt em(olMailItem)
' add graphic as attachment to Outlook message
' change path to graphic as needed
Set colAttach = l_Msg.Attachmen ts
Set l_Attach = colAttach.Add(" c:\test\graphic .jpg")
l_Msg.Close olSave
strEntryID = l_Msg.EntryID
Set l_Msg = Nothing
etc ...

The user has the same DLLs installed in the application folder as all the
other users, the difference is that they all had MS Office 2000 and then
upgraded to Outlook 2003 as part of the Small Business Server 2003
installation, where the new user only ever had Outlook 2003.

I am using the following DLLs:
=============== =============== =
DLL Version
Interop.MAPI.dl l 1.21.0.0
Interop.Microso ft.Office.Core. dll 2.3.0.0
Interop.Outlook .dll 9.2.0.0
=============== =============== ==

Can anyone explain why the CreateObject command is failing on that one
machine? It's driving me nuts!

--
Siv
Martley, Near Worcester, UK.

[William LaMartin]

I haven't used McAfee in years. I am only familiar with Norton Antivirus.
I personally had to disable the script blocking in it to get various things
in Microsoft Word to work, possibly also to get Microsoft Document Imaging
to work. It has been several years, and I can't remember the specifics.

Strange things happen. I recall once discovering that all of a sudden I
could no longer create a data link. I finally traced it to the installation
of a new mouse. Once I substituted the Microsoft driver for the Logitech
driver, everything returned to normal. Now what does a mouse driver have to
do with data links? I think script blocking possibly has more to do with
CreateObject("O utlook.Applicat *ion") than mouse drivers have to do with data
links. I think you can use the CreateObject method in VBScript.

"Siv" <ms**********@r emoveme.sivill. com> wrote in message
news:e0******** *****@TK2MSFTNG P11.phx.gbl...

William,
That's something I wouldn't have thought of. The user has McAfee
antivirus on her machine, and the other users have Sophos Antivirus, she
also runs MS Antispyware beta which they don't either as the Sophos suite
we have installed on the desktop machines covers both antivirus and
spyware threats.

Have you heard that McAfee does this??

Is it just the script blocking part or some other aspect of McAfee?

Thanks for your help, it gives me an avenue to pursue.
--
Siv
Martley, Near Worcester, UK.
"William LaMartin" <la******@tampa bay.rr.com> wrote in message
news:eq******** *******@TK2MSFT NGP14.phx.gbl.. .

I have read that the script blockers in Antivirus programs may block calls
to CreateObject("O utlook.Applicat *ion"). I know Norton Antivirus has such
a script blocker, for example. I did a quick Google search on
CreateObject( "Outlook.Applic at*ion") and antivirus that produced some
interesting messages.

[Siv]

William
I got the user to turn off "scriptstop per" in McAfee to see if the problem
went away, but it didn't. She also runs MS Anti Spyware so I turned that
off as well and still no good. (Wasn't too keen to have these things turned
off anyway so in some ways I am glad that they weren't the cause of the
problem!).

So the problem must be software and DLL related??
Unless anyone else knows what could be the problem.
--
Siv
Martley, Near Worcester, UK.
"William LaMartin" <la******@tampa bay.rr.com> wrote in message
news:ed******** ******@TK2MSFTN GP14.phx.gbl...

I haven't used McAfee in years. I am only familiar with Norton Antivirus.
I personally had to disable the script blocking in it to get various things
in Microsoft Word to work, possibly also to get Microsoft Document Imaging
to work. It has been several years, and I can't remember the specifics.

Strange things happen. I recall once discovering that all of a sudden I
could no longer create a data link. I finally traced it to the
installation of a new mouse. Once I substituted the Microsoft driver for
the Logitech driver, everything returned to normal. Now what does a mouse
driver have to do with data links? I think script blocking possibly has
more to do with CreateObject("O utlook.Applicat *ion") than mouse drivers
have to do with data links. I think you can use the CreateObject method in
VBScript.

"Siv" <ms**********@r emoveme.sivill. com> wrote in message
news:e0******** *****@TK2MSFTNG P11.phx.gbl...

William,
That's something I wouldn't have thought of. The user has McAfee
antivirus on her machine, and the other users have Sophos Antivirus, she
also runs MS Antispyware beta which they don't either as the Sophos suite
we have installed on the desktop machines covers both antivirus and
spyware threats.

Have you heard that McAfee does this??

Is it just the script blocking part or some other aspect of McAfee?

Thanks for your help, it gives me an avenue to pursue.
--
Siv
Martley, Near Worcester, UK.
"William LaMartin" <la******@tampa bay.rr.com> wrote in message
news:eq******** *******@TK2MSFT NGP14.phx.gbl.. .

I have read that the script blockers in Antivirus programs may block
calls to CreateObject("O utlook.Applicat *ion"). I know Norton Antivirus
has such a script blocker, for example. I did a quick Google search on
CreateObject ("Outlook.Appli cat*ion") and antivirus that produced some
interestin g messages.

[Siv]

William
I got the user to turn off "scriptstop per" in McAfee to see if the problem
went away, but it didn't. She also runs MS Anti Spyware so I turned that
off as well and still no good. (Wasn't too keen to have these things turned
off anyway so in some ways I am glad that they weren't the cause of the
problem!).

So the problem must be software and DLL related??
Unless anyone else knows what could be the problem.
--
Siv
Martley, Near Worcester, UK.
"William LaMartin" <la******@tampa bay.rr.com> wrote in message
news:ed******** ******@TK2MSFTN GP14.phx.gbl...

I haven't used McAfee in years. I am only familiar with Norton Antivirus.
I personally had to disable the script blocking in it to get various things
in Microsoft Word to work, possibly also to get Microsoft Document Imaging
to work. It has been several years, and I can't remember the specifics.

Strange things happen. I recall once discovering that all of a sudden I
could no longer create a data link. I finally traced it to the
installation of a new mouse. Once I substituted the Microsoft driver for
the Logitech driver, everything returned to normal. Now what does a mouse
driver have to do with data links? I think script blocking possibly has
more to do with CreateObject("O utlook.Applicat *ion") than mouse drivers
have to do with data links. I think you can use the CreateObject method in
VBScript.

"Siv" <ms**********@r emoveme.sivill. com> wrote in message
news:e0******** *****@TK2MSFTNG P11.phx.gbl...

William,
That's something I wouldn't have thought of. The user has McAfee
antivirus on her machine, and the other users have Sophos Antivirus, she
also runs MS Antispyware beta which they don't either as the Sophos suite
we have installed on the desktop machines covers both antivirus and
spyware threats.

Have you heard that McAfee does this??

Is it just the script blocking part or some other aspect of McAfee?

Thanks for your help, it gives me an avenue to pursue.
--
Siv
Martley, Near Worcester, UK.
"William LaMartin" <la******@tampa bay.rr.com> wrote in message
news:eq******** *******@TK2MSFT NGP14.phx.gbl.. .

I have read that the script blockers in Antivirus programs may block
calls to CreateObject("O utlook.Applicat *ion"). I know Norton Antivirus
has such a script blocker, for example. I did a quick Google search on
CreateObject ("Outlook.Appli cat*ion") and antivirus that produced some
interestin g messages.