CODEWITHSUNDEEP
c#scheduled-taskswindows-server-2008-r2outlook-redemption
Shax
Shax

Reputation: 4307

how to solve this error MAPI_E_FAILONEPROVIDER when using Redemption

Hi I have a strange problem and am unable to find out the root cause. We build and deployed our application using Redemption things were working fine but suddenly the installation on UAT server has stopped working. But the same is working in production(Thank God).

Our application is of console based and written using .NET 3.5 its not totally down, it is working but when we try to run the same application via scheduler task it didn't work, but when we double click the exe file it works properly, successfully connect to Exchange reads and download the files as per our business logic but not executing when we try to run under scheduler task.

below is small error info might be helpful for you..

2012-06-15 16:05:06,724 EmailProcess.Program - message = Error in IMAPISession::OpenMsgStore: MAPI_E_FAILONEPROVIDER ulVersion: 0 Error: Microsoft Exchange is not available. Either there are network problems or the Exchange computer is down for maintenance. Component: Microsoft Exchange Information Store ulLowLevelError: 2147746069 ulContext: 1318

Please suggest

Edit 1: More info Windows 2008 Server, a user named SpecialTasksUser is configured on the server to login and has admin rights. Outlook is installed and profile is configured for different user name OutlookSpecialUser, when we login using SpecialTasksUser user and launch the outlook it loads and shows the inbox and private folders...so far so good.

We created the scheduled task and configured to run under user name SpecialTasksUser because this user has admin rights and this is where it gives error. On the other hand, when we go to installation directory and double click the *.exe file the application works and redemption successuflly reads the email and does what it is suppose to do...please help I hope this information would be helpful .....

Upvotes: 1

Views: 5406

Answers (1)

Dmitry Streblechenko
Dmitry Streblechenko

Reputation: 66215

Most likely you are using a wrong parent identity of your process - scheduler runs under its own account by default. Make sure you specify the right Windows account.

Upvotes: 1

Related Questions