Sage 100

Another Applianz issue! Client on v2013 Advanced went live today (unfortunately) and the appliction server seems to be ""holding"" users. Example: with one user in and no one else total user count is 12 with only 4 available. Spent over an hour on the phone with Sage and they seem to feel its an issue with how applianz is handling the sessions. Applianz is no help because they say its a Sage issue. They are having issues today but say that this is unrelated and can't help. Clients continually see user limit exceeded messages and all of the normal routines aren't resolving. Anyone have any ideas? At this point it looks like they are going to have to roll back to v4.3 (not on applianz).

Did they not have this issue during testing?

run as an application or change registry setting

Did not see the issue whrn testing however - not sure if all users were on at the same time while testing. Already tried running as app and registry setting. Also renamed sy_workstation and sy_console. Killed all pvx sessions rebooted server. As soon as server comes back up - 7 clients automatically log in. However no users are actually logging in.

Two thoughts. First, since Applianz is a client/server setup you could run Sage 100 Standard and avoid all MAS 200 issues with the server. Second, here is what I have had to do to get Advanced to run without issue. Cannot run as a service. MAS 200 Server Configurations -On the Application Server Configuration, go to the Server tab, set KeepAlives = Off -On the Application Server Configuration, go to the Clients tab, set Reconnect = None -On the Application Server Configuration, set the Reconnect to Prompted if wanting to track dropped connections. -On the server, rename \MAS_System\SY_Console.M4T -On the server, rename \home\lib\_appserv\Locate.pvk -On the server, rename \home\lib\_appserv\sessions.pvk -Delete the contents of the MAS90\Locks folder -Delete the MAS200 service and run as a Host program. To remove all PVXWIN sessions -Close application server -From Task Manager, click to show processes from all users. -Delete pvxwin32.exe sessions User Maintenance -Go to preferences tab. Check box ""Spawn Tasks from Application Server"" -This eliminates Connection Failure to Host message at workstation.

It's been over a year since I installed on Applianz, but recall an issue where client was dropping session and when reconnecting, a new session was started (instead of the old one resuming). Since a new session began, MAS 90 was not dropping the license for the disconnected session. I believe I worked with Dustin and Nathaniel from Applianz... and they resolved by configuring the client to resume previous session instead of starting new one.

Applianz is modified Citrix. Each time a user logs in a new session is created, and when that user logs out, it is destroyed. If you have a local connection that must be special (eg, a special USB connection in shipping), then Applianz support can create a specific session for you to login to which has all the settings and is not destroyed. Works great, but it does consume one of your concurrent Applianz licenses.

So I was looking around in the Template Configuration and there was a check box marked ""Pre-Launch Application"". I unchecked it applied the changes and now everything is working as expected. Doesn't really make any sense - other Applianz clients of our are set up the same way and they don't experience this issue. All of the users appear to be in and working now.

That's weird. Even if the new session pre-launched Sage 100, you'd still have to log in. How could it pre-launch and actually commit a Sage 100 license without a valid username/password?

The whole thing is bizzare but then again I don't really understand some of the details with Applianz. I literally watched today as MAS sessions were created for 10 users when no one was even attempting to access the system. And because Applianz has been dealing with their other major system issue today - their two people who work in support haven't been able to assist with our issue all that much. I've never seen an issue like this before - very frustrating.