Event ID 20426

[07281973]

This error message is coming up a few times a day in the event log on our Blackberry Server. About a different user every time.

Have you seen this message?

Event Type: Warning
Event Source: Server Name
Event Category: None
Event ID: 20426
Date: 9/29/2004
Time: 9:18:19 AM
User: N/A
Computer: Server Name
Description:
{UserName@Domain.com} GetAndCreateFolderInfo Could not save Folder State. FolderID=-174.

Any help would be great

 

[greenW]

Looks like a rights issue at first glance...

Make sure the besadmin account has the following rights:


Exchange view only administrator delegation rights on the highest level of the Exchange server.

Specific rights:
• Read
• Execute
• Read Permissions
• List Contents
• Read Properties
• List Object
• Administer Information Store
• View Information Store Status
• Receive As
• Send As

 

[07281973]

I've verified that all permissions are correct.

Is anyone aot there having the same problem?

Please help

Everything works fine, but I don't like the idea of getting this message every other 5 minutes.

Thanks

Event Type: Warning
Event Source: Server Name
Event Category: None
Event ID: 20426
Date: 11/23/2004
Time: 10:42:16 AM
User: N/A
Computer: Server Name
Description:
{user.name@company.com} GetAndCreateFolderInfo Could not save Folder State. FolderID=-39.

 

[greenW]

Time for a second glance then


I'll check out my logs to see if this has ever occured on my BES.

 

[gershman]

These types of errors occur about once every two days on our BES server (3.6 SP3 w/Hot Fix 1+2 running on Win2k3). The user account that is referenced in the logs is usually different each time. I'd be very interested in understanding what it causing the errors and if they are merely informational or more serious in nature.

 

[greenW]

Google couldn't return any links about the following search strings either: "GetAndCreateFolderInfo Could not save Folder State"...

http://www.blackberry.com/knowledge...hat_Affect_Service.pdf?nodeid=736848&vernum=1

did not list this error as one which could affect service, so I dug deeper as I also have that event showing up in all my logs.

Funny what escapes your attention when you're not looking for it.

Here is a possible workaround (similar problem):

http://www.blackberry.com/knowledge..._list_for_EntryID.html?nodeid=728063&vernum=2