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

Resolved Program crash on DataWindow PrintPreview?

  1. Issue
0
Votes
Undo
  1. Daniel Vivier
    Daniel Vivier
  2. PowerBuilder
  3. Wednesday, 17 February 2021 23:24 PM UTC

Has anyone else experienced programs crashing in the DW DLL PBDWE190.DLL (with messages like "progname.exe has stopped working") when you put a DW into PrintPreview mode, or if not then, when go to actually print it?

I'm guessing this can be related to printer driver issues but not sure.

We did not encounter this until we started have a version of our programs available on a server accessed by Graphon's remote-control software, which supplies its own printer drivers - usually a "Universal Printer Driver". Something under 5% of our users of this new version are having problems like this. For the rest it's fine!

Thanks.

  1. DataWindow
  2. PowerBuilder (Appeon)
  3. Print
PB IDE Login Error
Application Crashes in some workflow when a third ...
Responses (4)
John Fauss
John Fauss Accepted Answer Pending Moderation
  1. Wednesday, 17 February 2021 23:52 PM UTC
  2. PowerBuilder
  3. # 1

Hi, Dan -

I've not heard of GraphOn GO-Global prior to you asking this question. The DataWindow Engine (DWE) is heavily dependent on the user's default printer (driver) especially in regards to Print Preview functionality, based on what I know, so if this remote-desktop alternative product provides a funky printer driver that is maybe not "well-behaved", I can see how that might give the DWE fits.

Have you inquired with GraphOn's Tech Support if they have knowledge of any issues (particularly this issue) running PB apps on desktops that use their product?

Regards, John

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Thursday, 18 February 2021 00:06 AM UTC
Good suggestion, I'll have our contacts that company running that GraphOn server for us to ask GraphOn about it.



By the way other than this problem, so far we are finding this to be a really nice way to turn our PB apps into what are essentially cloud apps, because all the user has to install is the small GraphOn remote-control client, and there is even a Mac client, and ones for Android and iOS. Some modifications were needed because of the environment but overall it wasn't too difficult.
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 18 February 2021 00:26 AM UTC
  2. PowerBuilder
  3. # 2

Hi John;

   It's probably the same "default printer" issue as in the Citrix environment. My suggestion would be to use the PrintGetPrinter() to check the default printer. If not correct, let the App User select the default printer they want to use using the PrintGetPrinters() command. Then save that in an INI file for example. Upon App restart, reset the default printer at startup using the last saved default printer from the INI using the PrintSetPrinter() command.

Food for thought Dan. ;-)

Regards ... Chris

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Thursday, 18 February 2021 00:34 AM UTC
Good thought, Chris, but that's not how it works in the GraphOn environment. There's an OnDemand Printers application that automatically starts with your local default printer - with the Universal Printer Driver - but you can add further local printers if you have them. You can also change drivers, if there's an installed driver on the server that matches your printer. But we've had users where none of that seemed to help.

Fortunately they also have a default PDF driver, printing to which somehow saves the PDF on your local hard drive and opens your local computer's default PDF application (so, usually Adobe Reader) from which you can print it. Deleting the real printer and using only that PDF driver seems to work as a last resort for all users with this problem, though obviously it's a bit of a pain to have to take extra steps to print.
  1. Helpful
There are no comments made yet.
Brad Mettee
Brad Mettee Accepted Answer Pending Moderation
  1. Thursday, 18 February 2021 15:54 PM UTC
  2. PowerBuilder
  3. # 3

Is it possible that the PB App isn't detecting there's a default printer assigned? I know we've had problems over the years where Windows would temporarily "forget" the active default printer and it would return "" or null instead.

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 18 February 2021 16:28 PM UTC
Hi Brad .. that was my though t as well. See my earlier response about using the PrintGet/SetPrinter() commands. ;-)
  1. Helpful
There are no comments made yet.
Mark Lee @Appeon
Mark Lee @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 10 March 2021 09:44 AM UTC
  2. PowerBuilder
  3. # 4

Hi Dan,

 

Have you resolved this issue?

It seems that this issue is related to the GraphOn tool. Have you consulted GraphOn support and see if there is any solution?

If not, it is suggested you report this problem to our ticket system:https://www.appeon.com/standardsupport/newbug so it can be properly received and tracked. 

Please also provide a VM with the GraphOn tool installed that could reproduce this issue for us to analyze when submitting the ticket. Thanks in advance.

 

Regards,

Comment
Daniel Vivier
  1. Daniel Vivier
  2. Wednesday, 10 March 2021 14:18 PM UTC
No it's not resolved, and some other users have a different behaviour - the headers of the report appear, but the body is blank (no crashing). We have a work-around for those users, which is using Graphon's Preview PDF printer instead, which creates a PDF on the user's computer and opens it in the user's computer's default PDF application, so they can always print from there.

Graphon doesn't really have any other solutions.

And because this is all running on someone else's servers, we can't bundle it up in VM for testing. Besides, it only happens on certain computers / printers, so you wouldn't necessarily be able to replicate it anyways.
  1. Helpful
Mark Lee @Appeon
  1. Mark Lee @Appeon
  2. Thursday, 11 March 2021 02:44 AM UTC
Hi Dan,

Do you mean you have a workaround for those users that have different behavior and there is still no workaround for the crashing issue?

Since it only happens on certain computers / printers, sorry that we can’t help you further without a replicable environment. Hope you can understand.

If possible, we suggest you try using other printer drivers like GhostScript or Microsoft Print to PDF and see if the issue exists?

  1. Helpful
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.