Sage 100

Have a client on 2017 Standard whose IT renamed the server Sage is installed on. I modified their icon and Sage runs fine. HOWEVER, when I tried to license Sage Intelligence on one of the workstations, the workstation install started running and eventually crapped out because it couldn't find the old path. So I thought I'd uninstall the workstation completely and reinstall using the new path. NO. The uninstall ALSO craps out because it can't find the old path. I also can't do a repair, because even though I am running it from the new path, somewhere in the inital chugging, Sage looks back to the old path. WTH? How do I get the danged thing off the workstation?

Search the registry for the old path. You can either change the path or backup and delete the record.

The path to the data is also in Company Maintenance, Preferences. Once you get back in, you might want to check the data location there.

@JaneCavanaugh - that's a really good point, which makes me wonder why Sage appears to be running just fine, with the data intact.

@MichelleTaylor1 - OMG, the path is out there all over the place. This should be fun.

Has been my experience (standard) that MAS90 care about the server when running. Name just matters when applying PU's or when screwing with the registry.

Beth - Make a backup of the registry just in case. Also the 2 fields in Sy_Company for data location are normally blank (which is why it's running fine). When you use actual Alternate Directories then it will have something in there.

@Alnoor - Phew! I guess IT is planning on moving Sage to another server (too bad they didn't get this all done before I installed Sage only a few months ago...), so I will wait until that's done before digging into the registry. Or, maybe I can persude them to change the name back long enough I can uninstall. Argh.