Sage 100

Customer on Sage 100 ERP Standard v4.3 - able to get the prompt to login but it goes no further. I know this has been discussed on here before and I'm about to begin the unpleasant task of searching Socialcast but before I start on that three hour tour I thought it wise to also post an inquiry to see if anyone remembers what the likely culprit was.

go to \mas90\home click pvxwin32 and I get the Providex:Initialization square dialog box but when I click OK it does not open to the command box we would normally see. I was able to get into this once - not sure if this is some type of AV or other issue blocking

One workstation or all?

Apparently all - I've gotten so far as to get the login prompt. It appears to flash the Sage 100 menu briefly then goes away. Looking at task manager the PVXWIN32 is NOT still hanging around post-crash.

Looks as if I was mistaken about PVXWIN32 not bringing up a window - it brought it up minimized

Customer complaint from yesterday about slow speed of Sage. They rebooted the server and that's all she wrote. Now if any user tries to login they get a login prompt to Sage (so far so good) then you can login - it appears to authenticate you then the Sage 100 screen briefly flashes and goes away. What's odd about this is task manager does not show PVXWIN32 as hanging around post crash as a stray service as it typically does with a crash. Has me suspicious that some type of AV or MALWARE scanner got an update and is somehow shutting down or stopping PVXWIN from full startup. Of course it could also be one of a bunch of key files that got somehow hosed - menu, security, sy0ctl. Problem is there's no simple want to get to the root cause without a lot of time consuming trial and error.

From SAGE knowledgebase: The Sage MAS 90 or 200 launcher starts minimized when launched Entry Type: Informational Product: Sage MAS 90 ERP, Sage MAS 200 ERP, Sage MAS 200 ERP - SQL Server Edition Application: Library Master Version Reported: 3.71 Subject: The Sage MAS 90 or 200 launcher starts minimized when launched. Possible Resolution: If the Launcher is not visible, locate the Sage MAS 90 icon in the system tray (lower right corner). Double-click the icon and the Launcher should display. From the Launcher, select View and verify that the Start Minimized option is not checked. If it is checked, select the option to disable. Restart Sage MAS 90 or 200 for changes to take effect.

Nice idea but it's starting and apparently exiting. When I look at Task manager there is no PVXWIN32 whatsoever in services listing. However I am not completely hosed because I do get a login prompt and it briefly flashes Sage 100 so it seems to be authenticating

How about this one from the Knowledgebase: 110-515911 - Launcher opens then immediately closes with no error Entry Type: Informational Product: Sage MAS 90 ERP, Sage MAS 200 ERP Application: Library Master Version Reported: 4.30 Subject: Launcher opens then immediately closes with no error Possible Resolution: Someone broadcasted a system shut down from Master Console and has not terminated the shutdown. Any one of the follow will resolve this issue. Find the workstation where the shut down was broadcast from and press the 'ok' button. Using a different MAS 90 or 200 system (if available) open the mas90\mas_system\SY_SYSTEM and set field number 45 BroadcastShutdown$ to 'N' Pull the mas90\mas_system\SY_SYSTEM from back up from before the event occurred.

Hmm - checking

Are either the workstations or server doing real-time scans of the MAS files? See any lock files? Will it run on the server? Are MAS files still open on the server even though no one is in MAS? If so, close them. Grabbing at straws after a short night.

problem solved - thanks to @MichaelMcDonald - i'm not sure if this is 4.3 specific (and has been fixed on future versions) but in essence it seems someone went into Master Console - clicked shutdown all and that choice was left in limbo. I'm not sure if it's a bug or whether the station that did the shutdown just exited improperly. Very odd ""error"" because none of the typical symptoms of PVXWIN32 hanging out in task manager were present.