Sage 100

MAS 200 v4.4.2 Application server starts but host is not listening on port 9600 and no one can log on. When you stop the host you get the error 'Unable to Communicate with Server: ""SAGE"". Cannot perform action requested. Have restored MAS_System, Home, Launcher, SOA and SY folders at Sage's request. Still not workin. Any ideas? TIA

You may need to create an inbound rule to open port 9600 on the Windows firewall.

Windows firewall not running on server.

Is there anything else using port 9600?

Nothing listening on port 9600.

Is port 9600 possibly being used by another program? Run netstat from a command prompt.

try port 10000.

I ran netat and nothing was using port 9600.

backup exec is using port 10000

yes, had that issue before. try port 9900 then.

I tried port 9599 and it didn't solve the issue

1. Try another port number 2. Ping a ding ding? 3. DNS issue? Does swapping ip for host name in the workstation file do anything? 4. How do you know host is not listening? (what tests have shown this?) 5. Don't think this is still an issue at 4.4 but can host ping server and server ping host? 6. Duplicate server names?

Full local admin permissions?

Running the host as an app? have you tried it as a service?

Don't think this applies but just in case: Sage 100 Advanced v 4.5 (aka MAS200) running as a service shuts down on server with error similar to: Faulting application name: pvxwin32.EXE, version: 9.30.6.0, time stamp: 0x 4dd2c46d Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0b17fd24 Faulting process id: 0x728 Faulting application start time: 0x01ce312f959c75e3 Faulting application path: C:\Sage\MAS 200 Client\Version4\MAS90\HOME\pvxwin32.EXE Faulting module path: unknown Report Id: 433a5e3e-9d23-11e2-921e-00155d3c9b0a Suggested Fix: Try turning off Data execution prevention for pvxwin32.exe and see if that helps. To configure DEP settings Click Start, click Control Panel, and then double-click System. Click the Advanced tab. Then, under Performance, click Settings. Click the Data Execution Prevention tab. Click Turn on DEP for essential Windows programs and services only to select the OptIn policy. Click Turn on DEP for all programs and services except those I select to select the OptOut policy. If you selected the OptOut policy, click Add and add the applications that you do not want to use DEP with 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/

Running as an app logged in as domain admin Sage tried using IP address instead of server name with no help. Know nothing is listening on port 9600 using netstat command. Would prefer not to run as a service

Right click run as admin - even if logged in as admin?

try service anyway just for kicks. if it works that would eliminate a lot of possibilities.

Thanks all for jumping on this for me. @WayneSchulz ran host clicking and ran as administrator and still same error. Tried ping server and got no errors.

You don't have that box checked to ban logins?

@DougHiggs ran as a service and get same error.

@WayneSchulz where is the ban logins box?

I see the same symptom whether running as a service or as an app that when I run the netstat -a command I don't see the server listening on port 9600.

check he path to the home directory the host is using. is it using a unc path or a mapped drive?

There's a check box to ban logins - it's in the application config somewhere. I forget what the exact wording is but when you check the box nobody can login.

ON the Apps tab I see -DR=C:\Sage 44\mas90\home

Has any new software (esp. anti- virus type ) been installed on the server?

@WayneSchulz I see a Disable Server button and Disable connections button and they are unchecked. @JohnLeonard they've been using Symantec Endpoint Protection. we disabled it but it did not clear the problem.

is user access control enabled?

Just to be sure that the Symantec is not causing a problem I would disable any Symantic related services and the Windows firewall service and reboot the server.

@DougHiggs - uac is enabled @JohnLeonard I tried disabling Symantec but it didn't help. the windows firewall is disabled.

I would turn off uac, reboot the server and try to start the host.

You may also want to exclude the MAS Application Server from Data Execution Protection. Are you getting any errors in the event log? Is the applictation running without listening or is the application just shutting down?

@DougHiggs The problem with turning off uac is that i'm logging on remotely and i can't back on with uac off. @SteveIwanowski MAS is excluded from DEP and the application is running but isn't listening. When it's running as a service i can stop the service without an error. When running as an app i get an error when trying to stop the server that it can't communicate with Sage. i think the error is because the port isn't in use but that's just a guess.

Nate at Sage got the host working this morning. He renamed apps.pvk, locate.pvk, server.pvk and sessions.pvk in the home\_appserver folder. Then he used a pvx command to set the host parameters back to default. Something was corrupt in one of those files. Thanks to all who helped last evening. I appreciate it.

Do you remember what the pvx command was?

Shoot the piece that I missed was that the host files were restored. I think they can be deleted (renamed) and are recreated upon restart. Maybe what happened is corrupted files were being restored.

Sorry @WayneSchulz there were several commands and I did not get them. You're right, seems one of the files that was restored was already corrupt but that's weird because we restored from Tuesday when the system was working fine

Ahhh.... the old corrupt file issue. I would love to start a list of the top 10 reasons consultants give to their clients when asked ""what causes that?"".

I had the same/similar issue yesterday morning. I always recommend searching here before calling Sage. It can save a lot of time and frustration! Its the power of a team!

This helped me resolve a similar issue when the MAS 200 Application would die about 30 seconds after launching. Replace Locate.pvk and Sessions.pvk. Have all users exit Sage MAS 200. Stop the application server, and exit the Application Server Configuration program. On the Sage MAS 200 server, browse to ..\Home\Lib\_appserv\. Rename the following files: Locate.pvk Sessions.pvk Restart the application server. Start the Application Server Configuration program. The Locate.pvk and Sessions.pvk files are automatically recreated, and the original grid is restored.