[bmacaluso]

Wexxx8217;re a small business with 5 current users on our BES. We recently had some calendar syncing issues that I eventually got resolved by searching this forum, thank you very much! The eventual solution involved getting our BES Admin account on the exchange server the correct xxx8220;receive asxxx8221; and xxx8220;send asxxx8221; permissions. Donxxx8217;t know how they got changed, but thatxxx8217;s another story. One other thing I learned during my search here is that the CDO.DLL file on the exchange server should be the same date as is on the BES. Herexxx8217;s where Ixxx8217;m not sure what to do. It appears Ixxx8217;ve got things working again by fixing the permissions issue, calendars are syncing nicely. However I discovered that these two CDO files on the Exchange and BES are different. Is it imperative that they be the same, or should I leave well enough alone?

[gziz]

the version on BES can be higher then exchange but not the other way around

[bmacaluso]

Thanks. I kind of thought that was the case. Right now the CDO file on the BES is 2003, and the CDO on the Exchange Server is 2006. So, technically I should update the CDO on the BES. Can I just copy the newer CDO file from the Exchange server to the BES? Since the CDO is a DLL file, I wasn't sure if it can be copied from one server to another like that.

[gooseberry]

hi

you cannot just copy and paste, first you will need to unregister the cdo.dll then copy and paste and then register the new one.

locatae the cdo.dll to where it resides on the bes server


1.) To unregister cdo.dll in dos promt change root to location of file ie c:\programe files\Exchsrvr\bin>

Then type regsvr32 cdo.dll xxx8211;u to unregister this file.

2.) then copy the new cdo.dll file in the same origanal place and register this by going in dos promt change root to location of file ie c:\programe files\Exchsrvr\bin>

then type regsvr32 cdo.dll .

however if everything is working fine i would leave it as the saying goes if its not broke dont try and fix it.

[bmacaluso]

I think for now I'll leave it alone. If I run into problems in the future, I'll unregister the old file and register the new one. I had no idea that registration process was involved to change the CDO.DLL file. I agree... If it aint broke, don't fix it.

[ladydi]

you don't need to unregister the dll. Just copy it from the two locations on the exch server to the same locations on the BES and register it on the BES. Takes 3 minutes and may save you future headaches to have it correct.

[bmacaluso]

ladydi - When I search my BES I can only find one instance of CDO.DLL. It's in C:\program files\exchsrvr\bin. Your post seemed to imply that there was more than one copy of CDO.DLL on my BES. Should I be looking somewhere else?

[ladydi]

It also exists in %windir%. You can just register the one in exchsrvr\bin

[bmacaluso]

Thanks.

[gziz]

ya you dont need to unregister it, but you should register it after you copy the file.