J
Jim Mitten
I am sending e-mail through Outlook from my Window program using COM.
- The solution runs fine in all tested versions of Windows and Outlook
except one.
- In Outlook 2007 under Vista with UAC ON and run normally (not as Admin),
the solution will occassionally time-out with no response from Outlook.
- Turn off UAC or run Outlook as Admin, then evetything works fine.
- If Outlook is not loaded and UAC is ON, everything works fine even though
it loads in non-admin mode.
- I can run the program with some exe names and it works fine. If I take the
program that doesn't run and simply rename the exe to a name that previously
works, the program starts working.
- One source told me that Outlook does NOT maintain a list of
blocked/allowed programs but uses a heuristic to determine if Outlook needs
to be elevated to Admin mode. My experience says this is false or the
internal heuristic must have some logic associated with the exe name.
I find no posts that shows how to maintain or affect the heuristic.
- When Outlook 2007 is under Vista with UAC ON and run normally (not admin
mode even with an Admin User), then the Programmatic Access Security is
disabled and the default setting of 0 is selected disabled even if the
Registry items
that affect this setting have changed. (And show with their correct changed
value when run in Admin mode.)
- Outlook 2007 should not time out in this situation. If it thinks the
access is not appropriate, a security message should be displayed that allows
the user to determine if this is an allowable event. However, it just times
out.
It seems to me that this is a defect in Outlook 2007 and not my program. Are
there some registry settings that I can use to affect the situation? Are
there log entries that show what's wrong (I have found none.)
- The solution runs fine in all tested versions of Windows and Outlook
except one.
- In Outlook 2007 under Vista with UAC ON and run normally (not as Admin),
the solution will occassionally time-out with no response from Outlook.
- Turn off UAC or run Outlook as Admin, then evetything works fine.
- If Outlook is not loaded and UAC is ON, everything works fine even though
it loads in non-admin mode.
- I can run the program with some exe names and it works fine. If I take the
program that doesn't run and simply rename the exe to a name that previously
works, the program starts working.
- One source told me that Outlook does NOT maintain a list of
blocked/allowed programs but uses a heuristic to determine if Outlook needs
to be elevated to Admin mode. My experience says this is false or the
internal heuristic must have some logic associated with the exe name.
I find no posts that shows how to maintain or affect the heuristic.
- When Outlook 2007 is under Vista with UAC ON and run normally (not admin
mode even with an Admin User), then the Programmatic Access Security is
disabled and the default setting of 0 is selected disabled even if the
Registry items
that affect this setting have changed. (And show with their correct changed
value when run in Admin mode.)
- Outlook 2007 should not time out in this situation. If it thinks the
access is not appropriate, a security message should be displayed that allows
the user to determine if this is an allowable event. However, it just times
out.
It seems to me that this is a defect in Outlook 2007 and not my program. Are
there some registry settings that I can use to affect the situation? Are
there log entries that show what's wrong (I have found none.)