Client Crashing on Remote Desktop sessions leaving orphaned PVXWIN32.exe - FIX

Just wanted to share this incident.  We upgraded to Sage 2013 PU2 two months ago virtualized on Server 2008 R2.  The Host server is Server 2012.  We just started seeing this issue over the last few weeks.  The client when connecting through a Remote Desktop server(Server 2008) would crash immediately after the user entered their username and password.  This would leave an orphaned pvxwin32.exe running and not allow them to log in again until we killed the process.  I did all of the usual error checking for access rights and authentication with no luck.

FIX*** The issue was found in the color depth in the RDP client connecting.  After switching this to 24 bit depth the issue cleared up immediately.

  • 0

    Thanks I'm adding that to our internal list of tips - here's another that I've found worked in a similar instance:

    Problem / Description:

    After logging into Sage 100 ERP the error "Sage ERP 100 has stopped working" appears. PVXWIN32 is hung in the background and must be closed manually.

    This was occurring via RDP to Windows 2008 R2 server.

    Resolution:

    Product:

    Sage MAS 90 ERP

    Sage MAS 200 ERP

    Application: Library Master

    Version Reported: 4.30

    Subject:

    "MAS has stopped working" when opening MAS 90/200 on Windows 2008 64-bit Citrix/Terminal Server

    Possible Resolution:

    NOTE: MAS 90/200 Version 4.30 is NOT supported on Windows 2008 64-bit Citrix/Terminal Servers. Check the Support Platform Matrix for supported environments.

    Follow the steps below to prevent Windows from monitoring MAS 90/200 program.

    Right click Computer and select Properties.

    Click Advanced system settings from right panel

    Select Advanced tab.

    Select Data Execution Prevention tab.

    Click Add and browse to the ...mas90\launcher\ folder.

    Select Launch32.exe click Open and Apply settings.

    May need to reboot server for setting to take effect.

  • 0

    Hi, thanks for the tips, they helped but didn't completely clear the problem for me.  I disabled the Information Center Page in Mas90 and finally eliminated the crash issue. Information Center Page loads on the right pane of mas.

    We upgraded to Windows Server 2008 R2 64 bit Terminal Service (RDP) and running Mas90 v4.4

    Problem

    After launching Mas90 and typing in username and password, mas would crash, an error massage would appear "Mas has stopped working" pvxwin32.exe would still run and needed to be ended trough the task manager in order to launch the application again.  I also notice that Mas90 would crash when trying to load the Information Center Page on the right pane.

    Resolution

    Using 32 bit resolution, following instructions for Data Execution Prevention, and disabling Information Center Page

    Disable Information Center Page

    - When logged in to mas90 go to view/skip information center page

    Make sure there is a check mark and you're done.  It's per user, not sure if there's an option in Mas90 to do it globally.  After this every user that had the crash issue hasn't had it again.