Sage 100

Any thoughts on the cause of this. MAS 200 v4.4 install. System was running without issue. Server was rebooted (routinely). Host application is running. Unfortunately, it is now unreachable (even at the server console). Have rebooted the server several times. Nothing. Have verified the host is running. I am thinking the port is now being blocked. Weekend user is running in MAS 90 mode but of course Monday morning there will be 30 users hitting the system. Did IT tweak the firewall? Of course, THEY aren't reachable on Saturday either................

My bet would be on the firewall settings. Maybe Windows Updates is responsible.

Glad we are thinking similarly.

I would check windows firewall on the server itself. I agree that it sounds like the port is being blocked. Alternatively, has the port been changed in MAS?

Had a very similar if not exact error happen last week. Symantec was updated by IT and by default blocked the port. My error message wasn't as colorful as your though.

Good call Harold, I have seen that as well with Symantec Endpoint Protection. New rules were added to the firewall and clobbered MAS200 on the server.

Can anyone elaborate on where to look next for the endpoint issues. Just spent the past hour with client IT support. The windows firewall on the server is off. The telnet command is not getting any feed back from the MAS port. When clicking on the MAS host application icon in the program tray, the error below pops up. While the application appears to be launching, it doesn't seem to be finishing the process. Thoughts? Is it time for Sage to earn their stripes?

One of the App Server data files it sounds like probably the sessions.pvk Start Up in MAS 90 style then DFDM all the pvk files in the Appserv folder. See which one you get an Error 106 on. It makes sense that this error is preventing App Server from listening properly and cause of your original error. If it's sessions.pvk you can rename it then start App Server Config and goto Sessions tab to recreate it.

Thanks

Well, I opened every PVK file in dfdm. Not a one bombed. I'll try renaming the session pvk to see if that has any impact. Unfortunately, for some reason, as Administrator, I don't have permissions to rename it. So I'll try rebooting the server to clear the cobwebs.

Whack any lingering pvxwin32.exe tasks in Task Manager

Would logging in and running as local administrator (NOT domain) administrator cause these issues?

Well, Alnoor gets the award for troubleshooter of the day. Renamed sessions.pvk and all is well in User land..........