DeliveryNow() method

[Mathasu78]

Hello,
I've a inconvenience with cdo.dll Service Pack 4.

I've used the method "oSession.DeliveryNow()" in a procedure.

This line of code was correct for cdo.dll Service Pack 1,
but now
I've copy the procedure in a Windows 2000 Server with
cdo.dll Service Pack 4.

Now this line get error !

Please help me!
Good bye!

 

[Ken Slovak - [MVP - Outlook]]

What error message are you getting when you call Session.DeliverNow?
Is this the client side CDO.DLL from Office that is installed on the
server and is Outlook from the same version of Office installed on the
same server? The server isn't an Exchange server is it?

 

[Mathasu78]

What error message are you getting when you call Session.DeliverNow?

"OLE IDispatch exception code 17389 from Collaboration Data Objects:
unexpected error. [MAPI 1.0 - [E_FAIL(80004005)]]........"

(This is a Visual Fox Pro 6.0 error, 'cause my procedure run into this
language)

Is this the client side CDO.DLL from Office that is installed on the
server and is Outlook from the same version of Office installed on the
same server?

I have wrong in describing the problem:
the error is from a client when my VFP procedure compile a message
and try to deliver it automatically ( with Session.DeliverNow() ).
There isn't a server of Outlook.
In my client is installed:
- Windows 2000 (5.00.2195) Service Pack 3;
- Outlook 2000 (9.0.0.6627) Service Pack 3;
- CDO 1.21s for Windows NT Service Pack 4 (5.5.2652.65).

The server isn't an Exchange server is it?

No, the server isn't an Exchange server.

Help me, please!!!
Thanks

 

[Ken Slovak - [MVP - Outlook]]

If it's CDO 1.21s (CDO.DLL) then DeliverNow is restricted with Outlook
2003 SP3. It's part of the security model so virus code can't send
Outlook emails. Also, DeliverNow never did work correctly with Outlook
2000 Internet only mode. It would have to be a version of Outlook 2000
prior to SP2 (release version or SR1) to be able to use DeliverNow
without errors, and Outlook would have to be in corporate/workgroup
mode (checked in Help, About Microsoft Outlook).

You might have to use Redemption's DeliverNow instead of CDO,
Redemption was developed to avoid the security limitations. You can
find out about Redemption at www.dimastr.com/redemption

What error message are you getting when you call

Session.DeliverNow?

"OLE IDispatch exception code 17389 from Collaboration Data Objects:
unexpected error. [MAPI 1.0 - [E_FAIL(80004005)]]........"

(This is a Visual Fox Pro 6.0 error, 'cause my procedure run into this
language)

Is this the client side CDO.DLL from Office that is installed on the
server and is Outlook from the same version of Office installed on the
same server?

I have wrong in describing the problem:
the error is from a client when my VFP procedure compile a message
and try to deliver it automatically ( with Session.DeliverNow() ).
There isn't a server of Outlook.
In my client is installed:
- Windows 2000 (5.00.2195) Service Pack 3;
- Outlook 2000 (9.0.0.6627) Service Pack 3;
- CDO 1.21s for Windows NT Service Pack 4 (5.5.2652.65).

The server isn't an Exchange server is it?

No, the server isn't an Exchange server.

Help me, please!!!
Thanks

 

[Mathasu78]

If it's CDO 1.21s (CDO.DLL) then DeliverNow is restricted with Outlook
2003 SP3. It's part of the security model so virus code can't send
Outlook emails. Also, DeliverNow never did work correctly with Outlook
2000 Internet only mode. It would have to be a version of Outlook 2000
prior to SP2 (release version or SR1) to be able to use DeliverNow
without errors, and Outlook would have to be in corporate/workgroup
mode (checked in Help, About Microsoft Outlook).

You might have to use Redemption's DeliverNow instead of CDO,
Redemption was developed to avoid the security limitations. You can
find out about Redemption at www.dimastr.com/redemption

Thank you very much!
Now I will try to work with Redemption' s DeliverNow instead of CDO,
but, if there will be problems, perhaps I will rewrite....

Good bye....