Hi Jamie!

Are you using PDK 7.1 or later (ideally 7.3 now) for your tests?  There was a bug in the -dy
ndll code that could trip the DEP (data
execution prevention) mechanism in Windows 2003.  This has been fixed in PDK 7.1 and later.

I have no idea how running an app just once as a dependent app should make a difference.  I 
would suggest you try the following:

.         Check if DEP is enabled (go to your computer properties, select the "Advanced" tab
, then select the "Performance Options"
dialog and switch to the "Data Execution Prevention" tab.

If it is enabled, disable it and see if that fixes the problem. Just re-enable it after the 
test; any problems with PerlApp under
DEP should be considered bugs in PerlApp.

If this fixes the problem, then disabling the -dyndll option may be a workaround for you.



.         If the problem seems to be unrelated to DEP, try running ProcessMonitor from Sysin
ternals (now part of Microsoft) to
collect all activities from your program. Setup a filter first to only collect events from t
his one process, otherwise you will be
overwhelmed by the amount of information collected.

If the information from ProcessMonitor don't help you further, feel free to send them to me 
(not to the list).

Please also provide more information about your setup: exact versions of both PDK and Active
Perl that you are using, maybe output of
`perlapp -version -verbose` plus service pack level of your 2003 server.

Cheers,
-Jan

From: pdk-bounces@[...].com [mailto:pdk-bounces@[...].com] On Behalf Of Jamie Harris
Sent: October 10, 2008 11:01 AM
To: pdk@[...].com
Subject: Perl app program won't run on Windows 2003 server.

 

 

I have several Perlapp executables which will not run on Windows 2003 server.  We have two s
ervers and it runs fine on one but won't
run at all on the other.   

 

I've written the typical "Hello World!" application and tried that and it won't run.  

 

Nothing happens, no error message, no event log entries, no nothing.   What is strange is th
at I've fixed my problem by making a
"dependent" executable and installing ActivePerl.  When I did that, the compiled program run
s fine.   Even weirder, I re-compiled
without the 'dependent' option and it *still* runs fine, and I've even uninstalled ActivePer
l and my program continues to work as
it's supposed to.  So it's like my dependent version set something up (registry?  permission
s?) and now that that's done I can have
a non-dependent version and it's fine as long as it's got the same name.  

 

I have several programs that do not work, and the one I compiled as a dependent and ran work
s fine now, but the others still do not.
So I have to reinstall ActivePerl, compile them as 'dependent' and run them one time, then f
rom that point forward I don't need them
to be dependent.   

 

I'm using PDK 7 (trial) at the moment but this problem existed in PDK 6 as well (I was hopin
g PDK 7 would fix this problem).   

 

The command line I usually use is: 

perlapp  --norunlib --force --clean --dyndll --verbose --perl C:\Perl\bin\perl.exe program.p
l

 

Program is:

#!/usr/bin/perl

 

print "Hi!\n";
$ignore = <STDIN> ;

 

 

 

 

 

 

-----------------------------------------------------
James Harris
Enterprise Application Analyst/Programmer
Information Technology Division
Frederick Community College 

-----------------------------------------------------