I don't think this particular error was related the prior requirement to open it first in Classic for it to appear in Standard. I think Sage has fixed that in a prior PU.
I do notice that when I am in Standard that the MAS_Reports error doesn't appear. NO data shows either --- meaning was still not working and also not providing me with an error message when viewed in Standard.
Ultimately this particular error seemed to arise from running Sage 100 in compatibility mode ( specifically XP SP3).
If you are ever in a situation where IT forces you to use VDI ( which means they tightly control all the desktops ) you should insist as part of the setup that they provide one VM that connects to the server but does not use VDI.
Having a non-VDI desktop is helpful for debugging whether the problem is somewhere in their VDI configurations. The main issue with VDI is you're probably not going to have access to the configuration so you have to rely on IT to make the changes you suggest. They are often reluctant so having a separate VM that runs without issue is VERY helpful at convincing the IT department ( or CTO ) that the issue likely is within VDI.
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------
Original Message:
Sent: 05-07-2020 16:41
From: Alnoor Cassim
Subject: Login failed for user 'MAS_Reports' with BI Explorer on v2019 Premium
I would not have guessed that! It makes a lot of sense, actually. I'm sure BI Explorer is using a .NET method for login with Mas_Reports that is not compatible with Windows XP SP3 mode and so you get the error. For that matter, now that you fixed it, the Standard Desktop will probably work as well (you mentioned earlier only Classic was working).
------------------------------
Alnoor Cassim
Accounting Systems, Inc. (ASI)
Email: alnoor@asifocus.com
Orange County, CA
------------------------------
Original Message:
Sent: 05-07-2020 13:55
From: Wayne Schulz
Subject: Login failed for user 'MAS_Reports' with BI Explorer on v2019 Premium
What eventually seemed to work:
The icon that we were starting Sage 100 Premium had checked off "run in Windows XP SP3" compatibility mode. Once we removed that checkmark everything worked just fine.
I cannot say for 100% if this was the root cause but it was the only solution that we could reproduce the issue and fix it at will by changing.
Toying with the registry did not seem to have an impact
This was in a VDI environment where all of the c:\ and registry comes back with each reboot no matter what the user does to change it. The only ability to save changed items was to the desktop which is why it sort of makes sense that the desktop shortcut could have been at issue and why one user may have experienced the issue and another didn't.
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
Original Message:
Sent: 04-09-2020 08:21
From: Wayne Schulz
Subject: Login failed for user 'MAS_Reports' with BI Explorer on v2019 Premium
Update to this ongoing issue:
First, this is in VDI which is a virtual desktop environment the company uses to manage its remote users. They have tight security in place so user rights are always a concern in debugging.
Sage had me look at these registry keys
------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990