Sage 100

Customer is leaving MAS200 and the server that MAS200 was running on is being retired. They want to move to Windows Server 2012 R2 and I advised that so long as they only need lookup access just copy MAS200 to the new server and run in MAS90 mode. The Sage 100 version is 4.4 and the new server is Windows Server 2012 R2. I copy the \MAS90 folder and all subfolders to \Sage\v44\ , check permissions and run ""startup.m4p"" only to be met with ""unable to create a session object...."" Have tried the normal suspects - Rename SY_Workstation.m4t - Rename Sessions.pvk and Locate.pvk - Right click PVXWIN32 and run as admin

What I did in this case is guess that maybe their new 2012 server didn't have some of the same pre-requisites installed since I just dragged/dropped \MAS90. Instead I went to a user workstation that already had MAS200 and run the standalone routine and did not receive any ""session object"" messages. This brings up another concern that getting MAS90 mode running on a workstation today is good but in the future when that workstation has to be swapped out they may have issues with missing DLL or components that are normally installed via WKSETUP. Robert/Jim suggest taking a regular MAS90 WKSETUP folder and sticking it onto the server so that in the future people can run wksetup but not be prompted for the server name (which we don't want because we are running MAS200 as MAS90).

Does it make any difference to install the 200 workstation even if 200 is not ""installed""?? Yes, you get the prompts but if you change the icon properties to 90 mode startup, it should run. So the question is will the 200 workstation install? IDK.

Other suggestions from the Sage KB:Create a share on the folder above the MAS90 folder. Adjust the permissions on the share and set to full control; Make sure SYSTEM has full control to the share. .Register Pvxdax.dll by running Regcom.bat in: C:\Program Files\Common Files\Sage\Common Components (for 32-bit operating systems) C:\Program Files (x86)\Common Files\Sage\Common Components (for 64-bit operating systems

Some of those suggestion won't work if you just drag/drop Sage to a new location. I'm betting on PVXDAX or C++ needing to be installed/registered.

Fwiw..I would install the programs then drag and drop over top.

I am working from memory here... but it seems last time I tried this, I had to copy something from the launcher folder on one of the existing workstations to the new Mas90/Launcher folder... can't remember right now what it was, but you might check the two for differences.