Re: Updating CDO.DLL on BlackBerry Server

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Lee Derbyshire [MVP] (a_at_t)
Date: 09/29/04 

Date: Wed, 29 Sep 2004 19:33:21 +0100

"sjohnson" <anonymous@discussions.microsoft.com> wrote in message
news:0b2101c4a571$7948d400$a601280a@phx.gbl...
> Hello-
>
> We have Exchange 5.5 SP4 running on NT4 SP6a under native
> ADS.
>
> After applying the 828429 hotfix to our Exchange server,
> we now have a problem with our Blackberry Enterprise
> Server.
>
> According to Research In Motion (the makers of the
> Blackberry server) the version of CDO.DLL installed on the
> BES must match or exceed that of the CDO.DLL on the
> Exchange server (now 5.5.2657.67.)
>
> I tried to apply the 828489 hotfix to the BES, but got an
> error that it wasn't a valid Exchange installation.
>
> Research In Motion advised I extract the files from the
> 828489 hotfix package using the /x switch and then
> manually copy and register the CDO.DLL from the package to
> the BES. I tried this to no avail, though I may have
> registered the DLL incorrectly - when registered using
> regsvr32.exe, must the DLL file be in the correct location
> or is it okay that I registered it from a temp directory
> and then copied it to the BES's system32 directory?
>
> Otherwise, it would be great if there was a way to install
> this patch to our BES.
>
> Does anybody out there have any ideas?
>
> Am I barking up the wrong tree and need to be looking for
> client versions of this CDO?
>
> Any help is appreciated.
>
> -Shannon

You probably can't copy the new file over the old one while IIS is running
(it will be locked). It doesn't have to be in the same place, though; you
can regsvr32 it in any location, as long as you don't move it afterwards,
because the location that you register it from is also saved as part of the
path to the DLL. You will need to stop/start IIS after registering it so
that the new one is loaded into memory.

I have left a copy of the DLL here if you still need it
www.leederbyshire.com/CDO.DLL.5.5.2657.67

Lee. 

-- 
___________________________________
Outlook Web Access for PDA and WAP:
www.leederbyshire.com
___________________________________

Relevant Pages

  • Re: VB6 Regfree Com
    ... The dll itself is a standard dll and needs no registering. ... It allows you to instantiate objects from COM servers *without* the need to register them. ... The COM server file may be anywhere on disk, not necessarily in the application directory. ... The only difference is that for instantiating you must not use VBs New operator or VBs CreateObject method. ...
    (microsoft.public.vb.general.discussion)
  • Re: VB6 Regfree Com
    ... MSVBVM60.DLL is on the target machine, then I can just include this DLL, the ... The COM server file may be anywhere on disk, ... Register the COM server you want to use *on the development pc*. ...
    (microsoft.public.vb.general.discussion)
  • Re: runtime error 800a0030 when executing vbscript from w2k. Works
    ... The COM server (it is not DLL, but out proc exe) is registered on both ... I forgot to mention more about the enviroment, but basically the COM Server ... > Does the dll register correctly as a COM component? ...
    (microsoft.public.scripting.vbscript)
  • Re: Registering DLL issue.
    ... working fine, with it pointed to the system32 folder, can't explain it ... system32 drive and use regsvr32 to register it. ... are pointing to the dll on the network drive and not the dll i ... All of my source is on our server so it's backed up every night. ...
    (microsoft.public.vb.general.discussion)
  • Re: Help in WMI in ASP.net application
    ... In my option you did the correct thing by creating a COM+ DLL. ... step I see you missing is that you need to register the DLL in COM+. ... The parameters that we pass or the server name (the host ... > well as from a remote machine it is giving the correct result. ...
    (microsoft.public.scripting.wsh)