You can get around this popup box in XP with this "fix"
Actually it's a security setting that says that x user is allowed to run
programatically You'll need Exchange Admin rights to install it in a
Public Folder. So, this may or may not help you.
It's actually a security risk to enable this, but so is running an old
release, so choose your poison
;EN-US;290499
/W98NT42KMe/EN-US/ADMPACK.EXE
I set it up once so I could help again if needed, but it's been a long
long time
Steven
Message
From: perl-win32-users-bounces (AT) listserv (DOT) ActiveState.com
[@listserv.ActiveState.com] Behalf
Foo Ji-Haw
Sent: Tuesday, January 03, 2006 7:46 PM
To: LeFevre, Ken
Cc: perl-win32-users (AT) listserv (DOT) ActiveState.com
Subject: Re: Win32:: (MAPI) and Win2K scheduler
LeFevre, Ken wrote:
I created a program using ActiveState's perl 5.8.4, compiled it using
perlapp 5.3.0 and ran it on Windows 2000 Professional SP4 against
2000 SR-1 (9.0.0.3821). It runs properly both from a command
prompt and as a scheduled task. I released it into production on
Windows 2000 server SP4 using the identical version of 2000.
Again, it runs great from a command prompt. When I run it as a
scheduled task, however, it dies because it's not able to get the
Application.
Hi there,
I'm afraid I have no solution to your problem, but if you've found help,
please share with me, as I code to access as well.
of the (unrelated) issues that I deal with, is that with the
latest , the user is prompted to grant access to the Perl
application, when the application starts. Some kind of security measure
on Microsoft's part, but it does not happen for 2000.
Here's the relevant code:
Win32::LE->Initialize(Win32::LE::CINITLEINITIALIZE);
die Win32::LE->LastError(),"\n" if Win32::LE->LastError( );
eval { $ =
Win32::LE->GetA('Application') };
die " is not installed" if $@;
unless (defined $) {
$ = Win32::LE->new('Application', sub
{$_[0]->Quit;});
or die ", cannot start ";
< dies here under Win2k srvr as a scheduled
task
As best I can tell, is registered the same on both machines.
The same dlls exist on both. I even set up the scheduled task to run
under the same userid I used when logging on to the server to run the
program from the command prompt. My theory is that there is some sort
of permissions issue or a difference in the scheduled task environment
between the two versions of the Win2k S, but I'm not succeeded at
finding the problem and how to resolve it.
I would greatly appreciate any insight or assistance in getting this
to run in the new environment.
Thanks,
Ken
>
>
>-
>
>
>Perl-Win32-Users mailing list
>Perl-Win32-Users (AT) listserv (DOT) ActiveState.com
>To unsubscribe:
Perl-Win32-Users mailing list
Perl-Win32-Users (AT) listserv (DOT) ActiveState.com
To unsubscribe:
Perl-Win32-Users mailing list
Perl-Win32-Users (AT) listserv (DOT) ActiveState.com
To unsubscribe: