OutlookEX UDF - Help & Support (III)

[water]

Add

#include <debug.au3>
_DebugSetut()
_DebugCOMError()

at the tiop of your script to get more detailed error information.

[water]

Add

#include <debug.au3>
_DebugSetup()
_DebugCOMError()

at the tiop of your script to get more detailed error information.

Edited May 22, 2015 by water

[jormatus]

  On 5/22/2015 at 5:23 PM, water said:

Add

#include <debug.au3>
_DebugSetup()
_DebugCOMError()

at the tiop of your script to get more detailed error information.

  Quote

​@@ DEBUG COM Error encountered is script.exe (-1):

Number = 0x80020006 (-2147352570)

WinDescription = Unknown name

Description =

Source =

HelpFile =

HelpContext =

Last Dll Error = 0

Retcode = 0x00000000

​@@ DEBUG COM Error encountered is script.exe (-1):

Number = 0x80040154 (-2147221164)

WinDescription = Class is not registered

Description =

Source =

HelpFile =

HelpContext =

Last Dll Error = 0

Retcode = 0x00000000

[water]

This means that Outlook is not installed on this machine.

[jormatus]

  On 5/25/2015 at 8:28 AM, water said:

This means that Outlook is not installed on this machine.

​Hmm, it certainly is. Tested on two other comps, same thing.

Other one has Outlook 2013 and other one has 2010. Only works on my dev machine (2010).

Maybe Outlook needs to be re-installed?

[water]

Do you have the full version of Outlook installed on this machines? Not the trial version? Or upgraded from the trial version to the full version?

[cembry90]

Thanks again for an awesome UDF, just experiencing one issue while using it.

 

Our company uses SSO to authenticate users, and has each user's SSO listed in the alias field in Outlook. For most of our users, the SSO resolves, your UDF works flawlessly, and the email is sent. However for all of our users who are setup with a single-letter last name (for users in India this is quite common), it fails every single time with the below error. The same does not occur for those who have single-letter first names however.

 

Here's some very rudimentary code (with the actual alias removed) which produces the above error:

#include <includes\OutlookEx\OutlookEx.au3>
#include <debug.au3>
_DebugSetup()
_DebugCOMError()
Global $oOL = _OL_Open(), $oSSO = "000000000"
Global $oItem = _OL_ItemCreate($oOL, $olMailItem, "*\Drafts", "", "Subject=Test Message", "BodyFormat=" & $olFormatHTML, "HTMLBody=Please disregard.")
_OL_ItemRecipientAdd($oOL, $oItem, Default, $olTo, $oSSO)
_OL_ItemSend($oOL, $oItem)
_OL_Close($oOL)

 

I've troubleshot this with a coworker, and it seems to be isolated to the _OL_ItemSend() function (as preparing the message in the Drafts or Outgoing folders does in fact work). What makes it strange is just that - preparing the message translates the name just fine. If I remove the call to _OL_ItemSend() then the message is in the Drafts folder, with the person's name in the "To" field.

 

Any assistance you could provide would be appreciated.

Edited May 27, 2015 by cembry90

[water]

When you manually create an email and enter the one letter recipient, is Outlook able to resolve it?

[cembry90]

  On 5/26/2015 at 8:09 PM, water said:

When you manually create an email and enter the one letter recipient, is Outlook able to resolve it?

​Yep, sure does! And as I mentioned above - if I remove the call to actually send the email, the email ends up in the Drafts folder with the person's name on the email.

 

I tracked it down to the following:

Func _OL_ItemSend($oOL, $vItem, $sStoreID = Default)

    If Not IsObj($vItem) Then
        If StringStripWS($vItem, 3) = "" Then Return SetError(1, 0, 0)
        $vItem = $oOL.Session.GetItemFromID($vItem, $sStoreID)
        If @error Then Return SetError(1, @error, 0)
    EndIf
    $vItem.Send()
    If @error Then MsgBox(0, '', 'ERROR')
    If @error Then Return SetError(2, @error, 0)
    Return $vItem

EndFunc   ;==>_OL_ItemSend

It's specifically failing on $vItem.Send()

 

Confirmed this using the following code:

#include <includes\OutlookEx\OutlookEx.au3>
#include <debug.au3>
_DebugSetup()
_DebugCOMError()

; Open the connection to Outlook
Global $oOL = _OL_Open()

; Create a mail item and set some properties
Global $oItem = _OL_ItemCreate($oOL, $olMailItem, "*\Drafts", "", "Subject=Test Message", "BodyFormat=" & $olFormatHTML, "HTMLBody=Please disregard.")

; Add a recipient and resolve it
_OL_ItemRecipientAdd($oOL, $oItem, Default, $olTo, "000000000")

; Send the mail
;_OL_ItemSend($oOL, $oItem)
$oItem.Send()

; Close the object
_OL_Close($oOL)

 

Thank you.

[water]

What is the value of @error and @extended after _OL_ItemRecipientAdd?

[cembry90]

  Reveal hidden contents

#include <includes\OutlookEx\OutlookEx.au3>
#include <debug.au3>
_DebugSetup()
_DebugCOMError()

; Open the connection to Outlook
Global $oOL = _OL_Open()

; Create a mail item and set some properties
Global $oItem = _OL_ItemCreate($oOL, $olMailItem, "*\Drafts", "", "Subject=Test Message", "BodyFormat=" & $olFormatHTML, "HTMLBody=Please disregard.")

; Add a recipient and resolve it
_OL_ItemRecipientAdd($oOL, $oItem, Default, $olTo, "000000000")
ConsoleWrite(StringReplace(StringFormat("@error: %s\n@extended: %s\n", @error, @extended), "\n", @CRLF))

; Send the mail
;_OL_ItemSend($oOL, $oItem)
$oItem.Send()

; Close the object
_OL_Close($oOL)

@error: 0
@extended: 0

Edited May 27, 2015 by cembry90

[water]

Which version of the UDF do you run? Version info can be found in the header lines of the UDF.

[cembry90]

  On 5/27/2015 at 4:13 PM, water said:

Which version of the UDF do you run? Version info can be found in the header lines of the UDF.

; UDF Version ...: 0.9.0

 

I tried updating (to 1.0.0.0) for good measure, but received the same error.

[water]

Could you please give an example of what $oSSO (in your example set to "000000000") looks like?
Is it "Lastname, Firstname" or something else?
"K, something" as I take from your screenshot is the resolved displayname of the user?

[cembry90]

  On 5/27/2015 at 10:09 PM, water said:

Could you please give an example of what $oSSO (in your example set to "000000000") looks like?
Is it "Lastname, Firstname" or something else?
"K, something" as I take from your screenshot is the resolved displayname of the user?

​It's literally the alias in Outlook. Example:

[water]

But could you please give an example for the CONTENT of such an Alias field for which the send then fails?
So I could then create such an alias here and do more testing.

[cembry90]

  On 5/28/2015 at 4:51 PM, water said:

But could you please give an example for the CONTENT of such an Alias field for which the send then fails?
So I could then create such an alias here and do more testing.

Sorry about that. Ours are nine-digit numbers, which is why I replaced it with nine 0s.

$oSSO = "000000000"

$oSSO = "123456789"

$oSSO = "112233445"

 

Any of those.

Edited May 28, 2015 by cembry90

[water]

I see.

I will create two contacts:
One with a nine digit number as alias and a Last name with only one character.
Another with a nine digit number as alias and a Last name with more than one character.

The first should fail on send.

BTW: Did you tell me which version of Outlook you run?

[water]

Another idea:
I assume your contacts are stored in the Global Address Book.
Could you create a contact in your personal contacts with an Alias an a one-letter Lastname and check if the problem still exists with this contact?

[cembry90]

  On 5/28/2015 at 5:47 PM, water said:

I see.

I will create two contacts:
One with a nine digit number as alias and a Last name with only one character.
Another with a nine digit number as alias and a Last name with more than one character.

The first should fail on send.

BTW: Did you tell me which version of Outlook you run?

​Microsoft Office Professional Plus 2010 - Version: 14.0.7145.5000 (32-bit)

 

  On 5/28/2015 at 6:00 PM, water said:

Another idea:
I assume your contacts are stored in the Global Address Book.
Could you create a contact in your personal contacts with an Alias an a one-letter Lastname and check if the problem still exists with this contact?

Tried to find a way to do this, but it appears it's controlled by an Exchange server and thus you can't give address book contacts an alias.