Sage 100

Major Issue. I just upgraded a customer from v2016 Standard to v2017 Advanced. The system now crashes multiple times per day. Sage is aware of this issue - there are other customers with the same problem - and currently THERE IS NO FIX. Sage is working on it. The client is having to run in MAS90 mode, which helps, but it still crashes. Sage created a BAT file to clear all the processes on the server when this happens so they can return to work. I recommend NOT upgrading until this is resolved.

Thanks for the heads up !! is this specific to a version of Windows server ? Running as a service or application ?

I don't believe it is specific to Windows version. In this case it's 2012 R2, and running as a service with admin login.

have you tried running as an application ?

We are running in MAS 90 mode now.

MAS 90 mode where users execute the PVXWIN32.exe file? Or as an application running on the Server Desktop?

The first one. I set up standard mode icons on each desktop. ""X:\MAS90\Home\ Pvxwin32.exe"" ..\Launcher\Sota.ini ..\SOA\Startup.m4p

Is this just inherent to version 2017 or is it because you upgraded from standard to Advanced?

I believe it is related to going from v2016 Standard to v2017 Advanced from what I am hearing. But that could be one of Sage's CYA statements.

Total user count?

10

Could it be related to data execution - here's a post that Jim did some years ago - http://dsdtips.com/how-do-you-resolve-mas90-or-mas200-force-close-errors-when-you-are-running-mas-on-a-terminal-server-on-a-win-2008-r2-64-bit-server/

Also, some basics - probably not related but fyi - http://www.s-consult.com/2008/10/08/tips-how-to-set-up-an-application-server-in-sage-mas-200-version-4x/

At 10 users it's typically not the usual Advanced instability. I have a user where we struggled with this (about 45 users) and had to expand memory allowance on the server via regedit. Doesn't sound like the same issue here.

Again, Sage is aware of this issue and is working on a fix. This is not a setup or configuration problem.

Sorry to hear you are on the bleeding edge. Did Sage give an ETA for the fix?

Thanks for the heads up - reaffirms our decision to NOT roll out 2017 until next year.

Jon, Sorry to hear that. I guess this is specific to 2017 Advanced. I upgraded 2 customers to 2017 Standard about 10 days ago and no problems reported yet.

Just did one this morning and stuck to 2016. Wasn't sure it was the right call, but feeling relieved now. My usual policy is to wait for the first PU to be released.

How is it they add virtually no new features but managed to break the program?

It's a special talent Sage has.

Please keep us posted on anything further you hear from Sage.

Jon, sorry to pipe in late, did you check DEP settings, Check off on the Sage 100 Configurator keep alives, and what do you have for each users' settings for spawn tasks set at? The other issue is the number of processes being able to be run as a service on the server, I thing Wage alluded to this , SS3003_ABC.pdf discuss this issue.

Hey Jon, any update from Sage yet? Do you know if there's a KB entry on it?

Hi - is there any update from Sage on this ??? we are holding back on a large system upgrade.... thanks Jeff

The client, who contacted Sage directly, is still waiting for notification from Sage that there is a fix for this. I would expect it to be part of SP1 whenever that is released. In the meantime, Sage says the problem should not occur if everyone runs the Classic desktop. However, we prefer to wait for a proper fix which has not yet happened.

I would like to add that I have everyone at my client running in ""MAS 90"" aka Standard mode through special icons I created. And this is working until a fix is obtained. So I believe if you are going to v2017 Standard, you should be OK.

Sage says the problem should not occur if everyone runs the Classic desktop.... And yet, we continue to convert users to 100c so they can take ""advantage"" of the many ""enhancements"" offered by this NEW interface.....

I've been under the impression that this is not the 100c new vs classic desktop crash (related to a hidden date prompt), since the original post doesn't mention 100c...

Update from Scott Brady at Sage: In regards case# 800xxxxxxx - Sage 100 freezing in Standard mode, our Engineering Team has come up with a workaround to replace some files stored in the launcher folder. The actual fix will not be included in updates because it requires an interpreter update which needs to be installed with the initial installation. Because of this, it will only be included on Sage 100 2018 version. The workaround fix will only be available with a signed Pre-release agreement. If you would like the workaround, I can obtain the Pre-release agreement for xxxxx. The workaround involves replacing files in the Launcher folder on both the Server and the workstations. My only issue is the problem occurs in Advanced mode. Using Standard mode as a work-around - which appears to work ok now that ALL users are doing it. Not sure what my client will opt for.

Do you think Scott meant Standard UI and not standard version of 100?

Also, is this related? I feel like maybe two (possibly more) different issues were brought into this discussion (all of which were high value to me and I've made note) -- https://goo.gl/0TGVcK

Jon, is this happening with remote users using Terminal Server, which client on a TS has to use the classic desktop. I just did and upgrade to V2017, Advance, all remote uses are using the classic, all internal are using the standard desktop. We will see how it goes went live today.

Why not publish a new installer for customers who haven't switched to 2017 yet? Just when we were getting folks used to upgrading and the idea that a current version could be stable... this makes me want to delay any Advanced/Premiums upgrades for an extra year.