Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (7)

Resolved 64 bit vs 32 bit deploy ..

  1. Issue
0
Votes
Undo
  1. Don Whitehead
    Don Whitehead
  2. PowerBuilder
  3. Monday, 7 February 2022 19:33 PM UTC

Have an issue with an application that we converted from PowerBuilder 8.0.1 to version 2021 build 1311..

the application converted with no issues.

when i run the application via the PowerBuilder IDE the application works fine.

Originally I deployed the application as a 64bit exe (and it built fine and I was able the fire up the .exe).. As it turns out we needed to deploy at a 32 bit .exe.. the .exe gets built but when I try to run it i get the following error, and then the .exe disappears 

"Windows cannot access the specified device, path or file. You may not have the appropriate
permissions to access the item."

I can switch between 64 bit and 32 bit and 64 bit always builds the .exe and I am able to run the application, 32 bit always give the same error and then the .exe disappears.

the folder where the .exe is built has no permission restrictions

I exported the BuildFile for both 32 and 64 bit and this is the only difference between the  files

32 bit code:

"CodeGenerationOptions": {
"Platform": 0,
"//": "0: 32-bit",
"//": "1: 64-bit",
"32Bit": {

64 bit code:

"CodeGenerationOptions": {
"Platform": 1,
"//": "0: 32-bit",
"//": "1: 64-bit",
"32Bit": {

I have googled the error message and none of the Windows solutions pertains..

  1. 32-bit
  2. 64-bit
  3. PowerBuilder
How to Deploy .Net Assembly along with Power Build...
Spring4Shell, is it used?
Responses (7)
Tracy Lamb
Tracy Lamb Accepted Answer Pending Moderation
  1. Saturday, 26 March 2022 17:44 PM UTC
  2. PowerBuilder
  3. # 1

This issue is marked as RESOLVED, but I don't see in the thread what the resolution was... could you please clarify?

 

 

Comment
Load more comments
Tracy Lamb
  1. Tracy Lamb
  2. Saturday, 26 March 2022 17:54 PM UTC
I wish he would mark one of the replies as a solution...looks like Roland Smith provided the solution.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Thursday, 31 March 2022 12:38 PM UTC
Yes, as mentioned by me in my first answer :)
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 31 March 2022 15:03 PM UTC
Oh, I didn't even bother scrolling that far. Credit should go to you. :-)
  1. Helpful
There are no comments made yet.
Don Whitehead
Don Whitehead Accepted Answer Pending Moderation
  1. Tuesday, 8 February 2022 15:12 PM UTC
  2. PowerBuilder
  3. # 2

Thanks all for the help..it in fact was an issue with our Dell anti virus software...

Comment
There are no comments made yet.
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 8 February 2022 01:33 AM UTC
  2. PowerBuilder
  3. # 3

I googled the message and found this:

https://support.microsoft.com/en-us/topic/-windows-cannot-access-the-specified-device-path-or-file-error-when-you-try-to-install-update-or-start-a-program-or-file-46361133-47ed-6967-c13e-e75d3cc29657

If an exe is disappearing by itself, it must be your Anti-Virus deleting it.

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Tuesday, 8 February 2022 02:26 AM UTC
My thought, as I commented already. That would be my first step and if that's not the cause keep looking further. It could even be a corrupted disk :)
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 7 February 2022 20:25 PM UTC
  2. PowerBuilder
  3. # 4

Hi Don;

  FWIW: I have compiled & deployed "tons" of PB Apps in both 32bit & 654bit modes simultaneously with no issues. I use different EXE names though so that I get a clean EXE vs a possible improper replacement EXE (ie: <MyApp>32P.exe  and <MyApp>64P.exe).

  Also, there have been two key MRs (Maintenance Releases) since the GA version of PB2021 that you are using. The PB021 version that I am currently running build 1506. If you can, I would first try and move up to the latest build & try the various bitness compiles again.

  FWIW: Note that the 32bit App may also crash out if the DB Client that it's using to connect to your DBMS is either the wrong bitness, missing bitness or the the DB Client version does not match your DBMS version. Food for thought.

Regards ... Chris

Comment
There are no comments made yet.
Don Whitehead
Don Whitehead Accepted Answer Pending Moderation
  1. Monday, 7 February 2022 19:59 PM UTC
  2. PowerBuilder
  3. # 5

John..this is the path I use for .dlls ..I assume that it contains both 32 and 64 bit..We have other applications that we converted that build in 32 bit fine

Comment
Roland Smith
  1. Roland Smith
  2. Tuesday, 8 February 2022 02:46 AM UTC
The 64bit runtimes are in the x64 subfolder.
  1. Helpful
John Fauss
  1. John Fauss
  2. Tuesday, 8 February 2022 02:57 AM UTC
Roland is correct.

Also, the phrase "the EXE disappears" is potentially misleading. Do you mean: (1) the application stops and is removed from the Windows task bar, or (2) the application EXE file itself is deleted? I'm assuming you mean the former and not the latter. Please clarify.

As a test, have you tried placing the application EXE, PBD's/DLL's, and runtime DLL's all in one folder? Any temp folder will do. When you do this, remove or rename the application XML file created by the deployment process that identifies the location of the runtime DLL's...this XML file is needed only when the runtime DLL's reside in a location other than where the app resides.
  1. Helpful
There are no comments made yet.
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 7 February 2022 19:54 PM UTC
  2. PowerBuilder
  3. # 6

Try deactivating your antivirus and see if the EXE still "disappears".

 

Comment
There are no comments made yet.
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Monday, 7 February 2022 19:52 PM UTC
  2. PowerBuilder
  3. # 7

Hi, Don - 

Each "bitness" (32 or 64) has its own set of runtime DLL's.

When you run the deployed 32-bit app, are you using the 32-bit runtime DLL's? A 32-bit executable will not be able to run using 64-bit runtime DLL's.

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.