1. Gaurang Patel
  2. PowerBuilder
  3. Tuesday, 3 December 2019 19:21 PM

Hello There Again, 

 

 As mentioned earlier, am new to PB ,  and migrating application from PB9.0 to PB19.0. 

  1. With Contractor's help migrated PB9.0 application to PB19.0 version, in development.
  2. Users were able test the application, hardware configuration users PC win10 with shortcut to EXE on  network location on WIN2016 servers.

 

We have segregation between Development and production network.

Production can be accessed via CITRIX.

.) Installed APP on CITRIX server (MS 2016) , and shortcut pointing to network location in production.

Short cut not working and giving following errors on CITRIX server Logs.

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0001c122

Faulting process id: 0x1948

Faulting application start time: 0x01d5a9fccdd4318d

Faulting application path: \\ad\apps\Prod2019\App2019.exe

Faulting module path: unknown

Report Id: 1437b202-3125-4da9-af28-4f6f4a3c9ec6

Faulting package full name:

Faulting package-relative application ID:

 

 

Any help guidance is appreciated.

 

Thank you,

Gaurang

Gaurang Patel Accepted Answer Pending Moderation
  1. Friday, 6 December 2019 18:54 PM
  2. PowerBuilder
  3. # 1
0
Votes
Undo

Hello All,

 

We had  both  32bit  and 64 bit C++  2015 versions  installed on WIN2016 server, however application would not launch.

We compared with 2012 server, and  installed C++ 2010 version, and able to launch applications.

Continuing Testing with 2016 server, considering this is as resolved...

 

Thank You All for your time and suggestions.

Gaurang

Comment
Thanks for sharing the solution.
  1. Armeen Mazda @Appeon
  2. Friday, 6 December 2019 19:24 PM
There are no comments made yet.
Gaurang Patel Accepted Answer Pending Moderation
  1. Wednesday, 4 December 2019 22:30 PM
  2. PowerBuilder
  3. # 2
0
Votes
Undo

We coped  all runtime DLL and EXE that were working fine in Dev network  t Production network.

UNC path and security settings are all OK.

Outside of Citrix, we are able to launch EXE from VDI, WIN10 PC, from 2008 windows server, and 2012 Win serve, except from 2016 server.

 Also created sample test exe , with just one window, could not launch from 2016 WIN server.

Thank You !!

 

 

Attachments (1)
Comment
I just made a small sample application, compiled as exe (32 bit, no dll's no pbd's, machine code).

Copied it to our 2016 server, with ALL dll's from the SHARED folder of PB.

No runtime install.

It simply works !

So my guess is that your missing some runtime DLL.

regards,

MiguelL
  1. Miguel Leeuwe
  2. Thursday, 5 December 2019 03:41 AM
Hi Miguel;

FYI: Yes, W2016 is supported ... https://docs.appeon.com/appeon_online_help/pb2019/release_bulletin_for_pb/ch01.html

Regards ... Chris
  1. Chris Pollach @Appeon
  2. Thursday, 5 December 2019 15:31 PM
Ups! I thought he was on 2017. Thanks!
  1. Miguel Leeuwe
  2. Saturday, 7 December 2019 03:50 AM
There are no comments made yet.
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Wednesday, 4 December 2019 02:27 AM
  2. PowerBuilder
  3. # 3
0
Votes
Undo

Hi,

Does it work when you run the application on the server itself, without being connected remotely with Citrix?

 

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 3 December 2019 19:27 PM
  2. PowerBuilder
  3. # 4
0
Votes
Undo

Hi Gaurang;

   Could this be a Citrix configuration setting regarding UNC address path resolution / execution permission?

Regards ... Chris

Comment
When you say you "installed" the app - what do you mean? Does this mean you built and installed a PB run-time environment installer? How are you deploying your application - file copy, you created and deployed using an installer MSI? Did the admin install anything on Citrix as the current user?
  1. Stuart Macandrew
  2. Wednesday, 4 December 2019 02:25 AM
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.