Hello,
As already said by Egbert Nierop, CDONTS is not supported on Windows Server
2003, and replaced by CDO. So you should consider rewriting the code.
But, if you upgrade a server, the cdonts.dll file will be available, but it
is possible that it is not registred. Try to run:
regsvr32 windir\system32\cdonts.dll
Where windir is the windows folder.
Also see:
<a style='text-decoration: underline;' href="http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/iisdg_dep_tnoc.asp" target="_blank">http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/...loyguid</a>
for more information.
--
Regards,
Kristofer Gafvert
<a style='text-decoration: underline;' href="http://www.ilopia.com" target="_blank">http://www.ilopia.com</a>
"Siegfried Heintze" <siegfried RemoveThis @heintze.com> wrote in message
news:%23SiUmev4EHA.3864@TK2MSFTNGP15.phx.gbl...
> We are moving a perl application from IIS5/Win2000 to IIS6/XP2003. We are
> using CDONTs on the old installation and it works. Perl aborts on the new
> installation when we (er, the perl script) create an instance of the
> CDONTS
> COM object.
>
> (1) How do I determine if CDONTs is installed?
> (2) Is there a way to determine if CDONTs is working correctly (besides
> running my perl script)?
>
> Thanks,
> Siegfried
>
><!-- ~MESSAGE_AFTER~ -->
>> Stay informed about: Is CDONTs installed and working correctly?