I'm running
ActiveState Perl version 5.8.4 build 810. PPM used to work great.
Now, when I do a search, it gives the following error
message:
Error: No valid
repositories: Error: This SOAP server does not expose aPPM3-compatible
interface. Specifically, it does not implement
I'm pretty sure you need to provide a password. It would be the password
attached to the Outlook profile.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Yekhande, Seema (MLITS)
Sent: Friday, May 19, 2006 9:12 AM
To: A. Pollock;
Title: Reading mail box.
I've
attached an object that reads the Outlook folder in the mailbox you specify when
you instantiate it. It works under Windows 2K Professional, but not Win2k
Server. It does, however, work under Win2k3 Server. It requires that
you install Microsoft's free
There's also a great command line tool by Mark Russinovich (which is easy to
launch from a perl script) called pskill (you can get it at
www.sysinternals.com).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Jack D.
Sent: Monday, April 17, 2006 10:52 PM
, 2006 5:18 PM
To: LeFevre, Ken; perl-win32-users@listserv.ActiveState.com
Subject: RE: Win32::Ole (MAPI) and Win2K scheduler
Replace :
die Oops, cannot start Outlook;
with
open (FILE,c:\\outlookerror.txt);
print FILE Oops, cannot start Outlook\n.Win32::OLE-LastError();
close (FILE);
die Oops
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 Outlook 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
handle the messages brought
back. The service now works exactly as I had hoped it would.
Ken
-Original Message-
From: Jan Dubois [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 29, 2005 2:15 PM
To: 'Steven Manross'; LeFevre, Ken; [EMAIL PROTECTED]
Subject: RE: OLE problem with Outlook
I'm writing a
program that monitors an Outlook mailbox and processes incoming e-mail in a
given folder with a specified mailbox. When I run the module that does
that actual access in the debugger, it works great. When I run the same
module as a thread, I get the following error:
retrying
Marcus:
Here's some code that will execute your command and
return what would normally go to STDOUT to the array
@lines.
my $path = \\;
my $cmd =
dir$path";my
@lines;open X, "$cmd |"; @lines = X;close
X;
foreach my $line
(@lines){ print "$line\n"; }
Ken
-Original
]
Sent: Monday, October 24, 2005 5:29 PM
To: LeFevre, Ken
Cc: perl-win32-users@listserv.ActiveState.com; $Bill Luebkert
Subject: RE: thread issue?
Are you releasing the threads when done with each? With Windows I
believe the maximum concurrent thread count is 255. If not, please
follow the standard
I have a process
that reads a snippet of code from a database and then executes it using an
eval. When I run it using my test tools, it works great. When I run
it as part of a system that spawns worker threads and these threads do the eval,
the same code fails. Here are my particulars:
11 matches
Mail list logo
