Unsolved
This post is more than 5 years old
46 Posts
0
1245
November 5th, 2009 02:00
A heap of MAPI_E_TIMEOUT events for one profile.
As users were complaining they couldn't resolve any shortcuts, we inspected the eventlog for possible reasons. In the OTG log we noticed a heap of MAPI_E_TIMEOUT events for just one exchange profile.
Restarting the EX services didn't resolve the issue. Hard resetting the server eventually resulted in the correct functioning of the EmailXtender service. This is not desirable, though.
For the future I want to know if I can safely delete the profile for which the time outs are being reported? Or is there another way to resolve this issue?
Hope someone can give me some advice on this.
Kind regards,
Duncan
Restarting the EX services didn't resolve the issue. Hard resetting the server eventually resulted in the correct functioning of the EmailXtender service. This is not desirable, though.
For the future I want to know if I can safely delete the profile for which the time outs are being reported? Or is there another way to resolve this issue?
Hope someone can give me some advice on this.
Kind regards,
Duncan
No Events found!
RKatwal
2 Intern
•
600 Posts
0
November 11th, 2009 21:00
Which version of EX server are you running ? If its below 4.81.1147, first thing I would suggest is to be on 4.81.1147 there were many fixes that went into .655 and .1147 that were related to shortcut retrieval failure and resetting MAPI profiles.
Thanks,
Rajan
minfin
46 Posts
0
November 16th, 2009 01:00
Hi Katwar,
We are using 4.81.564 (this the version most dll's have, adn this is shown in EX Administrator), but when I check in EmailXtract for Exchange the version mentioned is 4.81.619.
I will look into the case of updating our system to the latest version.
However I still want to know if I can safely remove those profiles.
Kind regards,
Duncan
ashaw1
12 Posts
1
December 2nd, 2009 14:00
Hello,
I believe this is a known issue with version 4.81.564, resolved under SDR26049 (See the "Fixed Defects" section(s) of the release notes for the latest patch). I would recommend upgrading to the latest patch which includes the fix for this issue.
Hope this helps!
Andrew