Sage 100

Anyone see MAS 200 change Data location while processing in the company? I have setup a parallel install and while users are in the live system I am in the test system on a client on the server. When I go into a few companies I can print the reports just fine no problem. Then something happens and I get prompted to convert the report or the files can not be found. I look at the data location in company setup and they are pointing to the live data location not the test location that they were pointing to when I started to work on the client. I don't change anything. I exited and then restarted the service and opened the client and the data path is correct and I can function. Process repeats over time. I checked the SOTA.ini and the path is right. Change data location has not been used so it takes the path of the mas90 folder not an override. Only thing I could think of is that users using the live system are triggering a change in the test system. Could it be the cs odbc changing the path in the odbc and is that affecting the path for the client?

I thought it might be reading from ODBC because I've seen this too.

I had this same issue but In my case it was it only happened when I was on the server that was running both the 4.30 MAS200 and the 4.40 MAS200. When I was on the server, the data location on the 4.40 version would switch back to the 4.30 version. Very weird.

Yes seen this a few times and it creeps me out every time --- if you find out the cause please post an update. I'm thinking that either of the above could be a cause. I try to make it a habit to double check the paths in company maintenance because I've seen this occur with some regularity though I wish I could spotlight the cause..

I have checked in company main. That path changes unless you statically set it. Otherwise it will take your path of the ODBC. This is why you may see on the server the path be = to the server drive letter (unless you change the default path when installing to unc). Otherwise the clients see the UNC path only. It almost fools you in seeing the data in maintenance showing the path into believing it is the path for all users. It is not, at least in my experience, it is the path for the current client unless you use the alternate directories which force a static link to another path.

I just had this happen last week, similar to @JimWoodhead (running both 4.30 and 4.40 MAS 200 on the server. I had gone into Company Maint to start the test upg Data Conversion but got a message that said there's data issues that must be fixed first. Well I had already done that during the pre-Migration - so I decided I'll try re-running the migration. But first let me delete the apparent bad company data. Oooof. It started to delete the Live data folders although it couldn't finish completely because users were in 4.30 - but the damage was done. Luckily I had the manual bkup I had first made earlier. Thought it may have had something to do with both Appl Servers running, so decided to run 4.40 MAS 200 ""as MAS 90"" (i.e., pvxwin.exe: run ""startup.m4p""). Definitely gonna keep my eye on it. Seems like this is isolated to MAS 200?

Important safety tip. When upgrading from 4.30 to 4.40 on MAS200 on the same server ALWAYs make sure you have a complete backup of the MAS System.

And actually regardless of the version, ALWAYS have a backup.