Sage 100

Has anyone done multiple installs of Sage 100 version 2013 on the same machine? I installed 100 standard as a ""sandbox"" when it came out, and now when I try to add another install to upgrade our company Sage 100 it will only let me alter the original install, no option for a new install.

I believe you can only have one 2013 on a given machine. At least, that's what I remember.

I think I remember something about that during summit. I think it have to do with the new Sage advisor and registry entries.

Wasn't it the new install thing via MSI, or something like that (which was needed by Advisor)? But yeah, only one per machine. People made a fuss, but I guess with the new install it's tough cookies.

Well, you can only have one OFFICIAL install, but has anyone just COPIED the official install to another folder and try to run it. My concern would be the ability to point the Sage Advisor updates to the correct folder.

I think jeff is right, you could Install your production and then copy it and use the copy as a pilot.

So now instead of having a VM for each version of Crystal we need one for Sage 100, one for Sage 300 (because installing Sage 100 2013 after installing Sage 300 2012 renders the Sage 300 2012 inoperative) and for developers means a separate VM for each customer with mods, all so Sage can run SPYWARE on its users. FUCUS!!!!!!!!!!!!!!!!!!

It was with the MSI. The work around was to install and make a copy.

Further update on this: You can make copies and they do work. The catch is that the product update installer claims they are not valid and won't update them!

That could be another benefit.

One step forward, one or more backward. Who said progress wasn't a challenge......

What was the step forward?

Stephen Smith of Sage answered again on the Sage Partners, Employees and Alumni Networking Group on LinkedIn, and basically said ""Too bad"" and we should use VMWare. I had commented that I always have 2 installs of the latest version fo Sage 100 on my laptop for demo purposes - standard and JobOps. It looks like I can't do that with 2013. My decision is to just install the JobOps version.

Going to post a possible hack by tomorrow. Something the installer is looking for. I think it will work. But can't test right now myself. If someone can test the theory by doing a 2nd install. Then separate test to see if product update will install too. You may need to that via PU download instead of Sage Advisor update.

If this works do this only on your own laptops (not on clients' until more is known) Delete the following registry key. This is what installer checks to see if 2013 is already installed HKEY_CLASSES_ROOT\Installer\Products\56C1EE7BA1519234C9FEF2C3CAE8205F

Am sure Sage engineers are doing the same hack themselves

Alnoor, I assume this has to be deleted after each install????

Yes or before the next new install. I haven't checked what the PU installer does but am hoping it's looking for the same thing (try to install PU from the website download as I'm not sure what complications the Sage Advisor update brings into the picture).

@AlnoorCassim - I deleted that key and tried the PU installer - same ""does not contain an installation of Sage 100 ERP"" message

So that means the key is needed for the PU installer. Maybe rename the key prior to doing a new installation (so it creates the key) then do the PU install. Then prior to installing the next copy of 2013 rename the key again then do the PU install again. Then when reinstalling a subsequent PU in the future have the appropriate version of the key unrenamed so the appropriate 2013 installation is updated. Sucks but better than nothing.

I did not test doing another install - I just deleted the key and then tried the PU on a ""copy"".

I tested doing a second install and it looks like that part is solved by the registry key removal. However, the product update issue is not.

Doing the 2nd install should've put the key back. If you've renamed the key after you completed the 2nd install, then rename it back and now see if the PU installer picks it up. That key points to an InstallShield GUID which should have the location of the \mas90 folder. I'm theorizing all this of course.

That works, but it means in order to update multiple installs you have to do the registry shuffle, and you can never apply updates to installations made by copying an installed MAS90 folder.

The registry shuffle - well said. That's what I meant above by 'Sucks but better than nothing'. I'll inquire about the PU installer maybe there is some override switch.

Now I can't get this song out of my head.... http://www.youtube.com/watch?v=EHoCOa860B4

@ThereseLogeais Thanks. For a trip down memory lane! Now where did I store that box of old vinyl LP s!

@ThereseLogeais - Nor sure how ""shuffle"" became ""hustle"", but I have a suggested cure: in Pandora or Spotify, type in Emerald Rose

At first I thought it was the Super Bowl Shuffle, but then remembered where she lived.... http://www.youtube.com/watch?v=2B74ii2F0Bw Watching it makes me feel real old.....

I'm not as concerned about my personal machine but for customers upgrading from 2013 to another level this looks like a more serious problem. We don't have a real good way to solve this issue (go ahead and hack their WIN server Registry or Workstation and let me know how their IT reacts the next time there's some type of bug) . I don't see toying with the customer's registry as much of an option but then again I'm much more risk averse. In essence what Sage did is just increase the cost of most upgrades for customers at a point where we were telling them things were settling down. Sage apparently misread the reason why most customers do a test upgrade prior to go live.

Oh snap! @JeffSchwenk that brings back memories.

@WayneSchulz I hadn't even thought of the upgrade parallel install issue.