Sage 100

2013 advanced - new install service start and immediately stops, application starts and immediately stops, logged on as admin, full rights on the MAS folder, any ideas? Looking at ports on windows firewall now but that doesn't usually cause a problem until we move from the server to the workstation

Try logging in as Administrator and turning off the PEP program.

how do I turn off the PEP program, we're already in as admin - thanks

I'll try loggin in through 90 mode and see if we can turn that off - can't open it up under 200, unless there is a back end way to turn that off

Click on the Sage Product Enhancement Program at the bottom. It will bring up the window where you can deselect the ""Participate in Program"".

You can also double-check if that port is already in use. At a command line, you can use: netstat -aon | find "":10000"" (or whatever port you're using). If you see any results, you'll need to change the port. If nothing shows, then you're in the clear.

netstat doesn't seem to work, turning off the PEP didn't work either - I've tried netstat - ano, netstat - aon, with without spaces - get a message form the cmd line that it's not a recognized command

If I remember correctly from our 200 Install this past weekend on a 2008 Server, it kept shutting down until I added the port to the firewall.

used netstat - o and the port is not in use

I did add the port to windows firewall - in and out, still no luck. strange, I'm not sure what's blocking this from starting up

the Sage port is 9995

I think you need the -a switch to pick up the listening ports.

Backup Exec uses port 10000 also so be sure that is not also installed.

Nothing in the System Event Log? Is Data Execution Protection disabled for the service?

By any chance are any of the disable connections check boxes selected on the server tab of the Application Server Configuration?

no on the app server config check boxes,, I don't see anything under system event log tied to the port and I'm not sure where the data execution protection shows on the service - but I can't find it. They do have Backup exec but I don't think there is a port conflict. Windows firewall has been turned off completely.

Have you tried starting the desktop version of the App Server instead of the service? The real error may reveal itself (e.g. Windows firewall window may appear).

DEP link via DSD - 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/

yep - just opens very quickly and closes immediately

thanks Wayne - looks promising, we'll give that a shot

I used DEP last week. Server would randomly shut down unexpectedly. Made the adjustment and no calls this week (knock on wood).

Add pvxwin32.exe too

Thanks for the info, I'll add that one to our check list.

Add masapsvr.exe too. I prefer just turning down DEP to the low setting of ""essential Windows programs and services only"" and rebooting for it take effect. Eric does it make a difference if Run as Adminsitrator used on App Server Startup shortcut?. Also in App Server Config / Apps tab / MAS 200 / click Details then look at the Startup Directory to make sure it's correct.

Please post solution when known so we can add it to Evernote. This is one of those head scratchers which if we document can save someone else a lot of time down the road.

will do - doesn't appear to be DEP, trying another server reboot but I'll definitely post the solution once we get this fixed.

Alnoor- have tried run as admin with several of the processes, creating the service, running the app starup, etc. We are logged on as administator

I think if it were DEP related, it would have made an entry in the event log. Grasping at straws, could you run Workstation Setup on the server? Run the RegCom.bat file at C:\Program Files (x86)\Common Files\Sage\Common Components? Check what .Net Frameworks are installed on the server... What is the server? 2008 R2?

Client had to step away - we're remote so expect an update this afternoon or tomorrow

@EricAnderson rename sy_workstation and sy_console also.

One or more system files for the Application Server Configuration module are damaged. Application Server Configuration controls the startup path for the service, port number, and other items for Sage MAS 200. This error can also cause runaway pvxwin32 tasks on the server when starting the application. Resolution 1: Replace the LOCATE.PVK and SESSIONS.PVK files. Have all users exit Sage MAS 200. Stop the Application Server, and close Application Server Configuration. On the Sage MAS 200 server, rename the ..\home\lib\_appserv\LOCATE.PVK file. On the Sage MAS 200 server, rename ..\home\lib\_appserv\SESSIONS.PVK file. Restart the Application Server, and open Application Server Configuration. New LOCATE.PVK and SESSION.PVK files are automatically recreated and the original grid restored.

Good tip Jim. This has happened to us a couple of times and your suggestion fixed it for us.

unfortunately, we're not sure what the exact issue was. The client ended up creating a brand new virual server, Sage 100 was installed and everything is working well. We believe there was just something blocking the application or service from starting up on that other server, just not sure exactly what it was.