Hi

Help request -

Environment is -

Windows 2003 Server
Exchange 2003
Bes 4.1
MSDE 2000

I am getting loads of the below warnings on the Bes effecting multiple users -

Event Type: Warning
Event Source: BlackBerry Messaging Agent SVR-BES Agent 1
Event Category: None
Event ID: 20301
Date: 03/10/2006
Time: 16:48:29
User: N/A
Computer: SVR-BES
Description:
Unable to save configuration settings or statistics

Event Type: Warning
Event Source: BlackBerry Messaging Agent SVR-BES Agent 2
Event Category: None
Event ID: 20045
Date: 03/10/2006
Time: 16:50:10
User: N/A
Computer: SVR-BES
Description:
CalICSAgent::Synch: Could not save synchronization state

Event Type: Warning
Event Source: BlackBerry Messaging Agent SVR-BES Agent 2
Event Category: None
Event ID: 20048
Date: 03/10/2006
Time: 16:27:52
User: N/A
Computer: SVR-BES
Description:
CalICSAgent:: - SaveSyncInfo SaveProps for PR_RIM_SYNCH_x(0x80040111) failed

Event Type: Warning
Event Source: BlackBerry Messaging Agent SVR-BES Agent 1
Event Category: None
Event ID: 20035
Date: 03/10/2006
Time: 16:17:42
User: N/A
Computer: SVR-BES
Description:
CDOCalendar::~CDOCalendar() - Exception handled

Any help would be very much apprieciated.

Thanks

Steve

Anyone ????

Have had a search on the site and on the net but cant find anything specific.

People are getting errors when accepting calander events in their blackberry's I assume this is related ?

Could the error relating to the calendar be down to the cdo.dll versions ?

Have seen a few things about this many different views do all versions of cdo.dll have to be the same ie exchange servers and bes server.

Has no one seen any of these errors before ? Does that mean I am special

Anyone I really could do with making some head way on these but I am going round in circles at the mo.

I would definately check your cdo.dll and mapi.dll versions to make sure they are the same on your BES and your exchange server (if you are running exchange). That would be the last error in your log as well as the errors people are seeing.

As to the others in the log, not sure, I have never seen those before.

Do you have enough space on the drive where the logs are located?

Thanks for the replies.

Yes we are running an exchange environment. I have checked the cdo.dll versions and it appears that the version on the exchange boxes is later and the bes server.

Ref space there is plenty of space on the drive free literally Gb's I have logging set so it is only kept for 14 days.

Any other suggests on the other errors that may not be related to the cdo.dll

Try re-registering the cdo.dll file on the BES, restart the synchronization service and observe the Event logs after 5mins.