Sage 100

Sage 100 Advanced v4.5, via terminal server with 28 user licenses. One of the users couldn't login today. In fact the login screen presented was the old MAS 90 screen. On the Sage server we found that the Application Server showed an error; we clicked ""close program"" and all cleared she could then login normally. Event Viewer shows EventID 1000 for pvxwin.exe when the user tried to login (details from the event viewer is in the comment section.). 10 minutes before that event, there were 15 instances of ""DCOM was unable to communicate with the computer 192.168.50.194 using any of the configured protocols""; they occured over a 3-minute span. This happens for the customer occasionally. We don't think it should happen ever -- the terminal server has plenty of resources. We can't figure out what might cause this hiccup. Any suggestions?

Faulting application name: pvxwin32.exe, version: 8.31.5.0, time stamp: 0x4ad765a1 Faulting module name: pvxwin32.exe, version: 8.31.5.0, time stamp: 0x4ad765a1 Exception code: 0xc0000005 Fault offset: 0x0009ab97 Faulting process id: 0x2204 Faulting application start time: 0x01cf858e77cab312 Faulting application path: D:\MAS200\Version4\MAS90\Home\pvxwin32.exe Faulting module path: D:\MAS200\Version4\MAS90\Home\pvxwin32.exe Report Id: 1ea13d32-f182-11e3-a50e-000c29b1ddb8

Standard issue/questions -- running as App generally is more stable than Service - especially above 20 users (YMMV). Also have found that even though no further memory expansion via bush-league type registry changes is SUPPOSED to be required - we have indeed needed to do them for 20+ user system on one occasion. I think this is the KB that we had to use - and , Yup, it's old. https://www.evernote.com/shard/s270/sh/58f4e85e-5007-4d56-81f9-befeb5b6557d/e9b566829594d59ab573b3e3ee17515c

Thanks Wayne. I looked in our KB with different search terms. I also looked under #terminalservices and it didn't come up. Can you add it? I was just about to post here that we did stumble on this: apparently the registry hack we had installed earlier .... disappeared! We'll add it back in and see if things return to ""trouble free"" status.