Bug 1435

PB2017 R2 Compilation fails after rebuild complete 31 October, 2018

Chris Tillman
16 July, 2018
Product: PowerBuilder Category: Installation
Version: 2017 R2 Build:
Classification: Issue Publishing: Public
Priority: P3
Status: Closed Reason: FIXED
Mark Lee @Appeon 20 August, 2018
#15
Hi Chris,

For the fake_machine_info issue, since we’ve discussed this before, we’ll skip it this time.
For getting crashes after Git commits issue, could you please provide us a simple PB test case that can reproduce it for further analysis?

Please understand this is important for us as without a reproducible test case, we may not be able to move forward.

Please open a new ticket when you provide us the simple PB test case so we can properly receive and track things.
 
Please try not to reply a closed ticket as this is not convenient for us to manage tickets and replies to a closed ticket would probably not be responded in time. 
Thanks for your understanding.
 
Regards,
Mark Lee
Chris Tillman 19 August, 2018
#14
Just wanted to let you know this message is still occurring on full builds under 2017 R3.

$ grep fake .DESKTOP-GU15HUD.tofft.log.ERROR.log*
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180813-201623.1000:E0813 20:16:23.286103  2056 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180814-193031.10696:E0814 19:30:31.557487 17128 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180814-194025.4188:E0814 19:40:25.865309   248 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180814-195937.11660:E0814 19:59:37.953909 14900 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180814-213840.4548:E0814 21:38:40.840759  5024 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180815-143446.1600:E0815 14:34:46.669929 12488 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180815-144819.17068:E0815 14:48:19.245767 15020 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180815-150332.13404:E0815 15:03:32.367619  7060 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180815-153638.11744:E0815 15:36:38.704140  7444 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
.DESKTOP-GU15HUD.tofft.log.ERROR.log20180819-094406.18160:E0819 09:44:06.672294 11092 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info

I'm also still getting crashes after Git commits, about one out of 3 times. I haven't figured out how to make it reproducible. The error messages above are associated with builds, not Git commit crashes.
Mark Lee @Appeon 17 July, 2018
#13
Hi Chris,

Thanks for you confirmation.
Glad to hear that.
We will close this ticket.
If you have any further question, please open a new ticket.

Regards,
Mark Lee
Chris Tillman 17 July, 2018
#12
1. This is a real machine rather than a VM. Since moving the targets into separate workspaces, all seems well. The fake_machine_info error now occurs when opening Powerbuilder or closing it down, even without referencing any workspaces (my option is set to open nothing on launch). So it must have been that dialog during installation, possibly related to the signing errors, but seems totally insignificant to usage as long as I use pbc170.exe to build, which I prefer anyway. 

2. With this new information, it looks like the error is associated with the Powerbuilder GUI. That might explain why it crashes on deploy after rebuild is complete, while pbc170.exe succeeds.

Happy to have this ticket closed, and thank you for your prompt support.
Mark Lee @Appeon 17 July, 2018
#11
Hi Chris,

Thanks for you quick update!
I am glad that you can successfully compile with pbc170.

1.      The fake_machine_data issue may due to some permission issue when you use PB on a virtual machine which result in a failure in creating this file.
As mentioned before, this issue doesn’t affect your normal use of PB.

2.      As pbc170 can create the executable, PowerBuilder IDE should also be able to create the executable.

It may requires that you create new PBLs for exporting and importing the objects from all the old PBLs and then do a full build of the workspace before you can successfully create the executable.
 
If you are fine with this solution, please let us know and we will close this ticket. If you have any further question, please open a new ticket.

Regards,
Mark Lee
Chris Tillman 17 July, 2018
#10
I created a new workspace and imported the objects from the old app pbl into the new application pbl, and referenced all the subsidiary pbls in-place. The pbc170.exe build succeeded without any command line error, although it still shows the original fake_machine_data error in the user/Appdata/Local/Temp folder. 

When I go back to the original workspace with pbc170.exe, the executable error still occurs on the command line:

Create of executable file failed
Creation of executable failed with a link error

Back on the new workspace, if I deploy from Powerbuilder it creates all the PBDs but still crashes trying to create the executable.

So I think I'll stick with the new workspace, retire this target from the original workspace, and build with pbc170.exe. There's probably no need to do an interactive session; it looks like this will be a good workaround assuming the funny error is not significant.
Mark Lee @Appeon 17 July, 2018
#9
Hi Chris,

1.      We suggest that you create a new workspace and a new PBL.
Then, export the objects from the original code that has the issue and import them into the new PBL.
2.      After you full-build the workspace, try deploy it and see if PB still crashes.
 
If there is still the issue, let's schedule a remote session to debug it.
We would recommend you to make the remote session during our working time which is 9:00 ~ 17:00 (we are in UTC+8 ) thus we can get the immediate help from the other team if necessary.
Please let us know when you can make the session and which tool you'd like to use for this session.(teamviewer or gotomeeting)

Regards,
Mark Lee
Chris Tillman 17 July, 2018
#8
Interesting, the same error got generated in my Local\Temp folder when PB crashed while deleting an object from a PBL (the one with many objects). So it's not just a build error.
Chris Tillman 17 July, 2018
#7
1.      I'm pretty sure I made "fake_machine_info" up when faced with that dialog. I think that may be true that it doesn't impact things, the only thing is sometimes the executable that's built doesn't work. When I built a 64-bit executable, it complained when attempting to execute, but I switched back to 32-bit and that one works.
2.      That's good.
3.      64-bit Windows 7 English was the first occurrence.
4.      64-bit Window 10 English was the second occurrence. That's why I thought the installation problem might be producing the problem... because I'm seeing the same error on both machines with the same PB installation and PBLs.
5.      I tried building a very simple test application, both 32-bit and 64-bit targets, and the error was not generated. But I tried building a different target in the same workspace with not nearly as many pbls and did get the error again. I'll try copying these pbls over to the test application which doesn't error.
6.      It is an older PB Classic application, dating from version 6 in some parts and last developed 6 years ago under 10.5/12.
7.      Not using any PBX objects.

Regards,
Chris
Mark Lee @Appeon 16 July, 2018
#6
Hi Chris,

1.      The missing fake_machine_info file shouldn’t affect the normal use of PB. This file is only for identifying the machine. It doesn’t matter even if it can’t identify.
2.      The failure of registering Sybase.PowerBuilder.Compiler.dll and WPFToolkit.dll is an known issue, we are fixing this issue.
Normally, the failure of registering them won’t affect the build and deploy functions in PB.
3.      Please let us know which version of the OS you are using on this machine (for example, 32-bit Windows 7 English).
4.      Please verify if you can reproduce the issue on another machine.
5.      Please provide a simple test case for us to reproduce and verify the issue.
6.      If the application you are building a standard application? Is it an .Net WebService application?
7.      If you are using any old version of PBX object in your code, please remove the object and import the corresponding PBX object from PB 2017 Shared folder. (The default path is: C:\Program Files (x86)\Appeon\Shared\PowerBuilder)

Regards,
Mark Lee
Chris Tillman 16 July, 2018
#5
.CHRIS-4540S.user.log.ERROR.log20180601-213319.4780 (0KB)

Attaching .CHRIS-4540S.user.log.ERROR.log20180601-213319.4780 from E:\Users\user\AppData\Local\Temp . I have dozens of these logs that say the same thing ... one for each build. This was the first, shortly after PB2017 installation.
Govinda Lopez @Appeon 16 July, 2018
#4
Hi Chris,

I will transfer it to our Engineering team for further analysis. We will keep you posted of the results here.


Regards,
Chris Tillman 16 July, 2018
#3
PB_2017_Install.txt (4KB)

Adding PB2017_Install.txt from E:\Windows\SysWOW64\AppeonInstallLog
Chris Tillman 16 July, 2018
#2
ngen.log (182KB)

Attaching ngen.log from E:\Windows\Microsoft.NET\Framework\v4.0.30319
Chris Tillman 16 July, 2018
#1
BuildProblem.txt (7KB)

*Phenomenon:
My Powerbuilder builds (both full builds and deploys) are failing with this message appearing in my AppData/Local/Temp folder:

--
E0601 21:33:19.682852  4784 FileTool.cpp:351] GetFileLength failed , file is not exitst; pathC:\Program Files (x86)\Appeon\PowerBuilder 17.0\fake_machine_info
--


*Reproduce Steps:
Select Full Build or Deploy from IDE, or use pbc170.exe on the command line. See attachment for details.

Remark:
My investigation found the PB 2017 R2 1769 installation package doesn't install two DLLs to the GAC.
OS:
Windows 7
Platform:
64-bit
Database Type:
Microsoft SQL Server
Database Version:
2014