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).
--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm
"Kukulkan" <(E-Mail Removed)> wrote in message
news:9c519a22-b04b-42e1-918b-(E-Mail Removed)...
> 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