I
intrepid_dw
Hi, all.
We're trying to overcome the infamous Outlook Object Model Guard dialog
that appears during unattended/programmatic accesses to the address
book or during the attempt to send mail. This tools works fine provided
it is used in an interactive environment. We need for it to work more
like a system service. We have numerous processes that require email
notifications to various people.
I have installed ClickYes in the "Run" key of the registry to force it
to start with the system. If I'm logged in, and I verify ClickYes is
running in TaskManager, and I run a test mail-generating script, it
works perfectly. If I set up a scheduled task to automate that email
test, it fails; and my logs show it is failing (hanging, actually) at
execution of the Send method on the MAPI object in my vbscript, which
says that invisible dialog is awaiting a dismissal that never comes
(and ClickYes is supposed to provide). In short, ClickYes isn't working
as an unattended tool. Mind you, this isn't just with the workstation
locked (which ClickYes docs state it cannot handle).
I've also tried installing ClickYes as a service via SrvAny, which
starts the executable just fine, but still will not dismiss the hidden
Outlook dialog.
I really don't have the option to rewrite these utilities with other
tools like Redemption, and I can't "not" use Outlook (corp standard).
In that regard, I'm very constrained. I've seen a suggestion to send
such messages out via SMTP rather than Exchange, but that's not a
terribly practical solution for us either.
I'd greatly appreciate any experience anyone has had with ClickYes in
this scenario; I've got to believe someone else is using it this way as
well, and can just tell me what I've done wrong.
Many thanks in advance,
David
Please reply to group; email posted in message is long since dead.
We're trying to overcome the infamous Outlook Object Model Guard dialog
that appears during unattended/programmatic accesses to the address
book or during the attempt to send mail. This tools works fine provided
it is used in an interactive environment. We need for it to work more
like a system service. We have numerous processes that require email
notifications to various people.
I have installed ClickYes in the "Run" key of the registry to force it
to start with the system. If I'm logged in, and I verify ClickYes is
running in TaskManager, and I run a test mail-generating script, it
works perfectly. If I set up a scheduled task to automate that email
test, it fails; and my logs show it is failing (hanging, actually) at
execution of the Send method on the MAPI object in my vbscript, which
says that invisible dialog is awaiting a dismissal that never comes
(and ClickYes is supposed to provide). In short, ClickYes isn't working
as an unattended tool. Mind you, this isn't just with the workstation
locked (which ClickYes docs state it cannot handle).
I've also tried installing ClickYes as a service via SrvAny, which
starts the executable just fine, but still will not dismiss the hidden
Outlook dialog.
I really don't have the option to rewrite these utilities with other
tools like Redemption, and I can't "not" use Outlook (corp standard).
In that regard, I'm very constrained. I've seen a suggestion to send
such messages out via SMTP rather than Exchange, but that's not a
terribly practical solution for us either.
I'd greatly appreciate any experience anyone has had with ClickYes in
this scenario; I've got to believe someone else is using it this way as
well, and can just tell me what I've done wrong.
Many thanks in advance,
David
Please reply to group; email posted in message is long since dead.