1. Ian Ho
  2. PowerBuilder
  3. Wednesday, 1 November 2017 07:58 AM

My migrated project deployed successfully, its stored in "D:\MyApp\" . It runs properly within that folder.

However, when I move the deployed files to "C:\Production" folder, it fails to execute and generates Windows event log application error.

What's wrong?

--------------- Application Error Event Log (Event 1000)  ----------------------------------------------------------

Faulting application name: myapp.exe, version: 1.0.0.1, time stamp: 0x59c46ae9
Faulting module name: PBVM170.dll, version: 17.0.0.1681, time stamp: 0x59c46c13
Exception code: 0xc0000005
Fault offset: 0x001df5f7
Faulting process id: 0x7ec88
Faulting application start time: 0x01d352e43da2b8ea
Faulting application path: C:\Production\myapp.exe
Faulting module path: C:\Production\PBVM170.dll
Report Id: edbfe350-af04-4601-9277-009a3bb71efe
Faulting package full name: 
Faulting package-relative application ID: 

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

Accepted Answer
Marco Meoni Accepted Answer Pending Moderation
  1. Wednesday, 1 November 2017 08:47 AM
  2. PowerBuilder
  3. # Permalink
0
Votes
Undo

Hello,
please provide more info, I tried the same operations on my machine (build the app 32/64 bit, copy .exe and .pbd to a different folder) and had no issue.
- What is your env? My guess is you are running on a 64bit Win10.
- Did you compile myapp.exe in 32 or 64 bit?
- Are you moving the executable to c:\production on the *same* machine?
This error occurs in PBVM170.DLL and might be caused by incompatibility between 32bit app and 64bit O.S. 
I would suggest you move the app to a different box by bundling all dependencies with the Appeon -> PB Runtime packager utility.

Cheers,

Marco

Comment
I think the problem lies on the OLE DB driver you are using to connect to MSSQL.



Once again, you must clarify your env, what version of MSSQL? There are many versions available but drivers change accordingly.



PB 2017 supports the SQL Server (up to 2016) native client (ver 11.0) as well as ODBC.



Please verify the DB connection using one of the above and compile again the project.



Cheers,



Marco 

  1. Marco Meoni
  2. Wednesday, 1 November 2017 20:53 PM
Its a MSSQL 2012 SP3.



I doubt its related to MSSQL driver, as the same executable runs without error on the same machine connecting to the same MSSQL just located on deployed folder. 



Edit: I am sorry I moved those deployed EXE and PBD once again and the application starts successfully today. I didn't change any setting as I recalled. 



 

  1. Ian Ho
  2. Thursday, 2 November 2017 02:10 AM
One possible cause is that there are already existing files in your c:\production folder and the copy was not able to successfully overwrite some of them (especially the exe file when it's running). So there were incompatibilities.

  1. Neil Garcia
  2. Thursday, 2 November 2017 19:20 PM
There are no comments made yet.


There are replies in this question but you are not allowed to view the replies from this question.