Accessing SafeUser.SMTPAddress crashes Outlook (Redemption)

[Kukulkan]

Hi,

One of our customer has a problem with our AddIn. He uses Windows 7
with OL2003 (latest ServicePacks) connected to Exchange. His Outlook
crashes, if our AddIn (VB6) accesses the data of the current user like
this:

Dim SafeUser As New Redemption.SafeCurrentUser
Dim Address As String
Dim SMTPAddress As String
Address = SafeUser.Address
SMTPAddress = SafeUser.SMTPAddress ' <- crash

This happens on multiple system. Many other customers are running out
AddIn without any problems. Virus-scanner and firewalls have been
temporary disabled. Outlook has been reinstalled. Nothing helps.

Outlook crashes this way (german):
Ereignistyp: Fehler
Ereignisquelle: Microsoft Office 11
Ereigniskategorie: Keine
Ereigniskennung: 1000
Faulting application outlook.exe, version 11.0.8312.0, stamp 4a403990,
faulting module unknown, version 0.0.0.0, stamp 00000000, debug? 0,
fault address 0x00000001.

Any Idea to prevent the crash? Can we do something? It is an important
customer...

Kukulkan

 

[Diane Poremsky [MVP]]

You might want to try this forum for developer questions now that Microsoft
closed their nntp servers:
http://social.msdn.microsoft.com/Forums/en-US/outlookdev/threads

--
Diane Poremsky [MVP - Outlook]

Outlook & Exchange Solutions Center: http://www.slipstick.com/

Outlook Tips by email:
mailto:[email protected]

 

[Ken Slovak]

See what else he's running that integrates with Outlook. If the code works
on other systems but not his there's something different about his system.

 

[Kukulkan]

Hi Ken,

See what else he's running that integrates with Outlook. If the code works
on other systems but not his there's something different about his system.

Thank your for your reply. The customer swears that he does not run
any other Outlook AddIn and his virus scanner has been disabled. There
is no other internet security suite installed. The Outlook
installation in renewed and actualized with the latest service pack.
No difference. It crashes directly by calling the SMTPAddress
property.

Andy other idea about the reason of such a crash? Andy idea what to
test? Exchange options to check? Should I use the dependency walker?
Any SysInternals tool? I am grateful for any additional information...

Kukulkan

 

[Ken Slovak]

If the user has an email account set up they should have an SMTP address for
SafeUser. About all you can do is to add extra error logging and make sure
Redemption is registered and running. I'd check for SafeUser not being null
before trying to access SMTPAddress. I'd then use String.IsNullOrEmpty() on
that string property, it might not even be there.

I've had lots of users swear a lot of things and almost all the time the
error is PEBKAC (problem exists between keyboard and chair).

 

[Kukulkan]

Hi Ken,

the problem is solved. The reason has been a telephony addin by AVAYA
Com4Tel. Is there any chance to fix the problem without the help of
their developers? We currently do not know any other incompatibilities
of our addin with other addins. We care about closing all
references...

I've had lots of users swear a lot of things and almost all the time the
error is PEBKAC (problem exists between keyboard and chair).

how true...

Kukulkan

 

[Ken Slovak]

Hi,

I think you'd either need to work with their developers or to have a FAQ
that lists their application as incompatible. Not much else you can do.