From: anil <an...@xs...> - 2012-07-31 16:49:48
|
Hi all, I'm having issues with a very simple program that I'm trying to compile using py2exe. Setup: XP machine, 32 bits with python 2.7.1 and py2exe-0.6.9.win32-py2.7 I've set IE as my default browser. My program is nothing more than the following: $ cat foobar.py import os os.startfile("http://www.google.com") # or some other valid webpage # alternatively: import webbrowser; webbrowser.open("...") will also fail as described below. setup.py is as simple as: $ cat setup.py from distutils.core import setup import py2exe setup(console=['foobar.py']) The compilation goes file, but when I execute my program, I get an "WindowsError: [ Error 5] Access Denied" The silly thing is that if I select e.g. Chrome as my default browser, it will kick off Chrome just fine. If I already have an IE running, it will open the webpage as a separate tab, if I try to e.g. start notepad.exe: that works, or even start a batch file that start IE: all works, I just can't seem to be starting IE by itself. Of course, just running foobar.py through the python interpreter also works as expected. I just get this error with when starting IE from a compiled version of my program. I'm out of clues, so any help is much appreciated! Rgds, Anil (an...@xs...) |
From: Mark H. <ski...@gm...> - 2012-07-31 23:02:39
|
Totally random idea - if the compiled version lives in "\Program Files", maybe try setting the process's cwd to somewhere else (eg, to the temp dir) before attempting to start IE? Mark On 1/08/2012 2:49 AM, anil wrote: > Hi all, > > I'm having issues with a very simple program that I'm trying to compile > using py2exe. > > Setup: > XP machine, 32 bits with python 2.7.1 and > py2exe-0.6.9.win32-py2.7 > I've set IE as my default browser. > > My program is nothing more than the following: > > $ cat foobar.py > import os > os.startfile("http://www.google.com") # or some other valid webpage > # alternatively: import webbrowser; webbrowser.open("...") will also > fail as described below. > > setup.py is as simple as: > $ cat setup.py > from distutils.core import setup > import py2exe > > setup(console=['foobar.py']) > > The compilation goes file, but when I execute my program, I get an > "WindowsError: [ Error 5] Access Denied" > The silly thing is that if I select e.g. Chrome as my default browser, > it will kick off Chrome just fine. If I already have an IE running, it > will open the webpage as a separate tab, if I try to e.g. start > notepad.exe: that works, or even start a batch file that start IE: all > works, I just can't seem to be starting IE by itself. > > Of course, just running foobar.py through the python interpreter also > works as expected. I just get this error with when starting IE from a > compiled version of my program. > > I'm out of clues, so any help is much appreciated! > > Rgds, > Anil (an...@xs...) > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users > |
From: anil <an...@xs...> - 2012-08-01 08:00:20
|
G'day Mark, Thanks for the quick response. It's a locally compiled and lives in a local directory. I did try to os.chdir to c:\temp, but that didn't work. I even tried to copy the complete IE folder from c:\program files to a local dir and execute that (just to make sure there we're no files created that I didn't have rights for). No luck :( I did find out that if I try this executable on a Win7 PC, it does work (even without the change to the cwd). So seems to be related to XP (or the setup that I have), in combination with py2exe. rgds, Anil On 2012-08-01 01:02, Mark Hammond wrote: > Totally random idea - if the compiled version lives in "\Program > Files", maybe try setting the process's cwd to somewhere else (eg, to > the temp dir) before attempting to start IE? > > Mark > > On 1/08/2012 2:49 AM, anil wrote: >> Hi all, >> >> I'm having issues with a very simple program that I'm trying to >> compile >> using py2exe. >> >> Setup: >> XP machine, 32 bits with python 2.7.1 and >> py2exe-0.6.9.win32-py2.7 >> I've set IE as my default browser. >> >> My program is nothing more than the following: >> >> $ cat foobar.py >> import os >> os.startfile("http://www.google.com") # or some other valid webpage >> # alternatively: import webbrowser; webbrowser.open("...") will also >> fail as described below. >> >> setup.py is as simple as: >> $ cat setup.py >> from distutils.core import setup >> import py2exe >> >> setup(console=['foobar.py']) >> >> The compilation goes file, but when I execute my program, I get an >> "WindowsError: [ Error 5] Access Denied" >> The silly thing is that if I select e.g. Chrome as my default >> browser, >> it will kick off Chrome just fine. If I already have an IE running, >> it >> will open the webpage as a separate tab, if I try to e.g. start >> notepad.exe: that works, or even start a batch file that start IE: >> all >> works, I just can't seem to be starting IE by itself. >> >> Of course, just running foobar.py through the python interpreter >> also >> works as expected. I just get this error with when starting IE from >> a >> compiled version of my program. >> >> I'm out of clues, so any help is much appreciated! >> >> Rgds, >> Anil (an...@xs...) >> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >> Discussions >> will include endpoint security, mobile security and the latest in >> malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Py2exe-users mailing list >> Py2...@li... >> https://lists.sourceforge.net/lists/listinfo/py2exe-users >> |
From: Mark H. <ski...@gm...> - 2012-08-01 08:58:08
|
On 1/08/2012 6:00 PM, anil wrote: > I did find out that if I try this executable on a Win7 PC, it does work > (even without the change to the cwd). So seems to be related to XP (or > the setup that I have), in combination with py2exe. Was it also built on Win7? If so, check the built directory for extra DLLs that you don't recognize or aren't certain you need - py2exe will sometimes pick up ones from the OS and when they load on xp "random" things go wrong... Cheers, Mark |
From: anil <an...@xs...> - 2012-08-01 10:18:34
|
Hi Mark, No it was built on XP, but does not run on XP. However the same XP build does run on Win7. I'm going to try the exec() the IE from a C program and see if it results in the same. If so, we can rule out py2exe and it probably is a policy setting Rgds, Anil On 2012-08-01 10:58, Mark Hammond wrote: > On 1/08/2012 6:00 PM, anil wrote: >> I did find out that if I try this executable on a Win7 PC, it does >> work >> (even without the change to the cwd). So seems to be related to XP >> (or >> the setup that I have), in combination with py2exe. > > Was it also built on Win7? If so, check the built directory for > extra DLLs that you don't recognize or aren't certain you need - > py2exe will sometimes pick up ones from the OS and when they load on > xp "random" things go wrong... > > Cheers, > > Mark |
From: Mark H. <mha...@sk...> - 2012-08-02 00:01:28
|
On 1/08/2012 8:18 PM, anil wrote: > Hi Mark, > > No it was built on XP, but does not run on XP. However the same XP build > does run on Win7. > I'm going to try the exec() the IE from a C program and see if it > results in the same. > > If so, we can rule out py2exe and it probably is a policy setting Well - if it runs from python.exe but does not run from py2exe on the exact same machine, then it wouldn't seem a policy setting to me. If it is a *different* XP machine that it fails to run on, I'd still be looking for extra DLLs that are being copied. But apart from that, I'm out of ideas :( Cheers, Mark > > Rgds, > Anil > > On 2012-08-01 10:58, Mark Hammond wrote: >> On 1/08/2012 6:00 PM, anil wrote: >>> I did find out that if I try this executable on a Win7 PC, it does work >>> (even without the change to the cwd). So seems to be related to XP (or >>> the setup that I have), in combination with py2exe. >> >> Was it also built on Win7? If so, check the built directory for >> extra DLLs that you don't recognize or aren't certain you need - >> py2exe will sometimes pick up ones from the OS and when they load on >> xp "random" things go wrong... >> >> Cheers, >> >> Mark > |
From: anil <an...@xs...> - 2012-08-02 07:22:04
|
Hey Mark, Thanks for thkinking along. You have a point re: the policy. No, it's the same XP machine it's compiled on and then fails to run on. I asked someone else to compile it (even though he has a Win7 machine). Runs on his, but not on my xp or any other xp box. Same with the program I compiled on my XP box: does not run on my XP box or any other XP box, but does so on Win7. Where should I be looking for extra dlls? I see a libray.zip in the dist folder and a python2.7.dll but nothing else. I even tried this with python 2.5 and 2.6, but no luck. rgds, Anil On 2012-08-02 01:45, Mark Hammond wrote: > On 1/08/2012 8:18 PM, anil wrote: >> Hi Mark, >> >> No it was built on XP, but does not run on XP. However the same XP >> build >> does run on Win7. >> I'm going to try the exec() the IE from a C program and see if it >> results in the same. >> >> If so, we can rule out py2exe and it probably is a policy setting > > Well - if it runs from python.exe but does not run from py2exe on the > exact same machine, then it wouldn't seem a policy setting to me. > > If it is a *different* XP machine that it fails to run on, I'd still > be looking for extra DLLs that are being copied. But apart from > that, > I'm out of ideas :( > > Cheers, > > Mark > >> >> Rgds, >> Anil >> >> On 2012-08-01 10:58, Mark Hammond wrote: >>> On 1/08/2012 6:00 PM, anil wrote: >>>> I did find out that if I try this executable on a Win7 PC, it does >>>> work >>>> (even without the change to the cwd). So seems to be related to XP >>>> (or >>>> the setup that I have), in combination with py2exe. >>> >>> Was it also built on Win7? If so, check the built directory for >>> extra DLLs that you don't recognize or aren't certain you need - >>> py2exe will sometimes pick up ones from the OS and when they load >>> on >>> xp "random" things go wrong... >>> >>> Cheers, >>> >>> Mark >> |
From: Mark H. <ski...@gm...> - 2012-08-02 07:28:30
|
On 2/08/2012 5:21 PM, anil wrote: > Hey Mark, > > Thanks for thkinking along. You have a point re: the policy. > > No, it's the same XP machine it's compiled on and then fails to run on. > I asked someone else to compile it (even though he has a Win7 machine). > Runs on his, but not on my xp or any other xp box. Same with the program > I compiled on my XP box: does not run on my XP box or any other XP box, > but does so on Win7. > > Where should I be looking for extra dlls? I see a libray.zip in the > dist folder and a python2.7.dll but nothing else. In the "dist" directory - I guess you mean python27.dll and there is also the .exe itself. My only other idea is to try playing with the bundle_files option - set it to 3 and see what then ends up in the dist directory... Cheers, Mark > > I even tried this with python 2.5 and 2.6, but no luck. > > rgds, > Anil > > On 2012-08-02 01:45, Mark Hammond wrote: >> On 1/08/2012 8:18 PM, anil wrote: >>> Hi Mark, >>> >>> No it was built on XP, but does not run on XP. However the same XP >>> build >>> does run on Win7. >>> I'm going to try the exec() the IE from a C program and see if it >>> results in the same. >>> >>> If so, we can rule out py2exe and it probably is a policy setting >> >> Well - if it runs from python.exe but does not run from py2exe on the >> exact same machine, then it wouldn't seem a policy setting to me. >> >> If it is a *different* XP machine that it fails to run on, I'd still >> be looking for extra DLLs that are being copied. But apart from >> that, >> I'm out of ideas :( >> >> Cheers, >> >> Mark >> >>> >>> Rgds, >>> Anil >>> >>> On 2012-08-01 10:58, Mark Hammond wrote: >>>> On 1/08/2012 6:00 PM, anil wrote: >>>>> I did find out that if I try this executable on a Win7 PC, it does >>>>> work >>>>> (even without the change to the cwd). So seems to be related to XP >>>>> (or >>>>> the setup that I have), in combination with py2exe. >>>> >>>> Was it also built on Win7? If so, check the built directory for >>>> extra DLLs that you don't recognize or aren't certain you need - >>>> py2exe will sometimes pick up ones from the OS and when they load >>>> on >>>> xp "random" things go wrong... >>>> >>>> Cheers, >>>> >>>> Mark >>> > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users > |
From: anil <an...@xs...> - 2012-11-07 09:39:31
|
Hi guys, Just wanted to provide a follow up on the problem (doing an os.startfile() raised an Access Denied error if IE is your default browser). Unfortunately we never found the root cause. I created a workaround in which IE was started by a batch file, but after a couple of weeks it turned out that the problem did not manifest itself anymore. So it had nothing to do with py2exe, it's just a policy/OS setting that was changed during regular maintenance. Unfortunately, again, I don't know the rootcause :( Rgds, Anil On 2012-08-02 08:28, Mark Hammond wrote: > On 2/08/2012 5:21 PM, anil wrote: >> Hey Mark, >> >> Thanks for thkinking along. You have a point re: the policy. >> >> No, it's the same XP machine it's compiled on and then fails to run >> on. >> I asked someone else to compile it (even though he has a Win7 >> machine). >> Runs on his, but not on my xp or any other xp box. Same with the >> program >> I compiled on my XP box: does not run on my XP box or any other XP >> box, >> but does so on Win7. >> >> Where should I be looking for extra dlls? I see a libray.zip in the >> dist folder and a python2.7.dll but nothing else. > > In the "dist" directory - I guess you mean python27.dll and there is > also the .exe itself. > > My only other idea is to try playing with the bundle_files option - > set it to 3 and see what then ends up in the dist directory... > > Cheers, > > Mark > >> >> I even tried this with python 2.5 and 2.6, but no luck. >> >> rgds, >> Anil >> >> On 2012-08-02 01:45, Mark Hammond wrote: >>> On 1/08/2012 8:18 PM, anil wrote: >>>> Hi Mark, >>>> >>>> No it was built on XP, but does not run on XP. However the same XP >>>> build >>>> does run on Win7. >>>> I'm going to try the exec() the IE from a C program and see if it >>>> results in the same. >>>> >>>> If so, we can rule out py2exe and it probably is a policy setting >>> >>> Well - if it runs from python.exe but does not run from py2exe on >>> the >>> exact same machine, then it wouldn't seem a policy setting to me. >>> >>> If it is a *different* XP machine that it fails to run on, I'd >>> still >>> be looking for extra DLLs that are being copied. But apart from >>> that, >>> I'm out of ideas :( >>> >>> Cheers, >>> >>> Mark >>> >>>> >>>> Rgds, >>>> Anil >>>> >>>> On 2012-08-01 10:58, Mark Hammond wrote: >>>>> On 1/08/2012 6:00 PM, anil wrote: >>>>>> I did find out that if I try this executable on a Win7 PC, it >>>>>> does >>>>>> work >>>>>> (even without the change to the cwd). So seems to be related to >>>>>> XP >>>>>> (or >>>>>> the setup that I have), in combination with py2exe. >>>>> >>>>> Was it also built on Win7? If so, check the built directory for >>>>> extra DLLs that you don't recognize or aren't certain you need - >>>>> py2exe will sometimes pick up ones from the OS and when they load >>>>> on >>>>> xp "random" things go wrong... >>>>> >>>>> Cheers, >>>>> >>>>> Mark >>>> >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. >> Discussions >> will include endpoint security, mobile security and the latest in >> malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Py2exe-users mailing list >> Py2...@li... >> https://lists.sourceforge.net/lists/listinfo/py2exe-users >> |