CDOSYS AND CDONTS on W2K3 machine

[tshad]

I have both cdosys.dll and cdonts.dll on my W2K3 server.

We have been told by our web authors that their asp code won't work on our
machine and that we don't have CDONTS installed on our machine.

They're getting an error from:

Set objCDOMail = Server.CreateObject("CDONTS.NewMail")

I know that the new format is:

Set objCDOMail = Server.CreateObject("CDO.Message")

Is there something special that we have to have installed to make CDONTS
work?

Thanks,

Tom

 

[tshad]

CDONTS doesn't come with W2k3 so unless you added it you are out of luck.
Either way though it's a dead technology, switch over to CDO.

I agree and have already done that.

Our problem is mostly temporary.

We have a couple of companies doing projects for us and they are using the
same project for others.

We have W2K3 and others have W2K (which has CDONTS on it).

I moved CDONTS.DLL from my other machine to allow their code to work until
they change their code. But we are getting an error. Is this because it
has both .dlls (cdonts.dll and cdosys.dll) on the machine?

Thanks,

Tom

 

[Ray Costanzo [MVP]]

Well, while you ~can~ put the cdonts.dll file on your machine and regsvr32
it, I suggest that you don't do that. Use CDO.Message.

 

[Steven Burn]

http://support.microsoft.com/default.aspx?scid=kb;en-us;315197

--

Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

CDONTS doesn't come with W2k3 so unless you added it you are out of luck.
Either way though it's a dead technology, switch over to CDO.

I agree and have already done that.

Our problem is mostly temporary.

We have a couple of companies doing projects for us and they are using the
same project for others.

We have W2K3 and others have W2K (which has CDONTS on it).

I moved CDONTS.DLL from my other machine to allow their code to work until
they change their code. But we are getting an error. Is this because it
has both .dlls (cdonts.dll and cdosys.dll) on the machine?

Thanks,

Tom

 

[Aaron [SQL Server MVP]]

We have W2K3 and others have W2K (which has CDONTS on it).

Windows 2000 also has CDOsys, so stop using CDONTS.NEWMAIL there, too.

 

[tshad]

Well, while you ~can~ put the cdonts.dll file on your machine and regsvr32
it, I suggest that you don't do that. Use CDO.Message.

I agree.

But if they want to be backward compatible with their other customers, they
may balk at that - at the moment.

But you do have to register it?

How do I look to see if it is already registered?

Is there a conflict problem if I am using both cdosys and cdonts?

Thanks,

Tom

 

[Steven Burn]

But you do have to register it?
</snip>

Yes

How do I look to see if it is already registered?

</snip>

Start > Run, type: regsvr32 <dll_name>

Doesn't really make a difference if it's already registered

Is there a conflict problem if I am using both cdosys and cdonts?

</snip>

No.

--

Regards

Steven Burn
Ur I.T. Mate Group
www.it-mate.co.uk

Keeping it FREE!

Well, while you ~can~ put the cdonts.dll file on your machine and regsvr32
it, I suggest that you don't do that. Use CDO.Message.

I agree.

But if they want to be backward compatible with their other customers, they
may balk at that - at the moment.

But you do have to register it?

How do I look to see if it is already registered?

Is there a conflict problem if I am using both cdosys and cdonts?

Thanks,

Tom

 

[Ray Costanzo [MVP]]

But you do have to register it?

Yes, you do. And with 2003, you may have to go into dcomcnfg
(start--run--dcomcnfg) and verify that your IUSR account has permissions to
execute the component after you register it.

How do I look to see if it is already registered?

I guess if it's in dcomcnfg, it's registered, but it won't hurt anything to
reregister it if it's already registered.

Is there a conflict problem if I am using both cdosys and cdonts?

I don't believe that should be a problem.

Ray at work

 

[tshad]

Windows 2000 also has CDOsys, so stop using CDONTS.NEWMAIL there, too.

Good point.

Hadn't realized that.

Thanks,

Tom

 

[Jeff Cochran]

I agree and have already done that.

Our problem is mostly temporary.

We have a couple of companies doing projects for us and they are using the
same project for others.

We have W2K3 and others have W2K (which has CDONTS on it).

I moved CDONTS.DLL from my other machine to allow their code to work until
they change their code. But we are getting an error. Is this because it
has both .dlls (cdonts.dll and cdosys.dll) on the machine?

Judging from your error I'd say... well... um...

If you have an error you want a resolution to, you need to tell us
what it is.

Jeff

 

[Aaron [SQL Server MVP]]

Judging from your error I'd say... well... um...

If you have an error you want a resolution to, you need to tell us
what it is.

Or be logical. "Gee, I have a 1978 Datsun B210 and a 2005 BMW 645i in the
driveway. The Datsun won't start, can someone help, I really need to go buy
some groceries, and I want to use the Datsun for some weird reason!"

 

[tshad]

Judging from your error I'd say... well... um...

If you have an error you want a resolution to, you need to tell us
what it is.

Server object error 'ASP 0177 : 800401f3'

Server.CreateObject Failed

/EmailEmpReg.asp, line 12

800401f3

 

[Morris]

I moved CDONTS.DLL from my other machine to allow their code to work until
they change their code. But we are getting an error. Is this because it
has both .dlls (cdonts.dll and cdosys.dll) on the machine?

*Moved* it? Do you mean just copied the dll over? Did you register it
on the 2003 box?

Morris

 

[tshad]

*Moved* it? Do you mean just copied the dll over? Did you register it on
the 2003 box?

I don't remember if I registered it or not. I don't have access to the
machine at the moment, but I was going to check that out. I hadn't realized
that I needed to register it until someone else mentioned it earlier.

Tom

 

[Jeff Cochran]

I moved CDONTS.DLL from my other machine to allow their code to work until

Server object error 'ASP 0177 : 800401f3'

Server.CreateObject Failed

/EmailEmpReg.asp, line 12

800401f3

That's typical of not having the CDONTS.DLL on the system, or of not
registering it if you do have it. Either register the DLL and try it,
or switch to CDOSYS which requires no registration of DLLs on your
server.

Jeff

 

[tshad]

That's typical of not having the CDONTS.DLL on the system, or of not
registering it if you do have it. Either register the DLL and try it,
or switch to CDOSYS which requires no registration of DLLs on your
server.

Actually, I am doing both.

Thanks,

Tom