Re^3: Win32::OLE (Outlook) as a windows service

Limbic~Region:

Here in the salt mines, our security is tied down pretty tightly, so applications attempting to access an Outlook session from a different process invoke a dialog box for the user to key in their password to give the application access to Outlook. Perhaps you're running into something like that? You might be able to test it by RDPing into your computer with a different account and trying to access the Outlook session you already have running. (IIRC, another way you can see if the service account is opening a dialog box is by looking at the Event Viewer | Applications page.)

Other than that, I can't think of anything.

(I'm quite selfishly hoping you'll be successful, as I tried to get an automatic process to load EMail from Outlook into a database so I could search / archive / categorize / graph it more easily. I got access, but the aforementioned security problem stonewalled me. I'll try to think on it some more and/or dig up my OutlookDB project and see if I can come up with something.)

...roboticus

Comment on Re^3: Win32::OLE (Outlook) as a windows service

Replies are listed 'Best First'.
Re^4: Win32::OLE (Outlook) as a windows service by Limbic~Region (Chancellor) on Oct 17, 2008 at 15:36 UTC
roboticus, You may want to have a look at the Advanced Security add-in for Outlook. This allows you to tell Outlook to trust certain applications for certain activities permanently rather than being annoyed by the pop-ups. It doesn't sound like that is exactly what your problem is though. Read on for ideas on that. First, you can run a service as any account you want - it doesn't have to be the system account. This means you can have the service running as the owner of the mailbox and that might solve your problems. If you are using Outlook as your client and Exchange as your server, you can also modify the permissions on the mailbox to allow another user to have full access without prompting for passwords. Of course, this all highly depends on your environment and local policies. None of this happens to help me solve my problem but it might help you with yours. Cheers - L~R	[reply]

Replies are listed 'Best First'.

Re^4: Win32::OLE (Outlook) as a windows service
by Limbic~Region (Chancellor) on Oct 17, 2008 at 15:36 UTC

roboticus

Advanced Security add-in

First, you can run a service as any account you want - it doesn't have to be the system account. This means you can have the service running as the owner of the mailbox and that might solve your problems. If you are using Outlook as your client and Exchange as your server, you can also modify the permissions on the mailbox to allow another user to have full access without prompting for passwords. Of course, this all highly depends on your environment and local policies. None of this happens to help me solve my problem but it might help you with yours.

Cheers - L~R

[reply]