Sage 100

The Version of the application could not be determined. The setup will now terminate. Nothing in the knowledgebase that i found but I remember this was brought up by another dealer in the past but I couldn't find a solution. Trying to reinstall Sage 100 4.4. The status.flp file and SY_Company look fine.

Harold, that may have been me that brought it up. I fought with it recently. the one I had issues with was on a 2012 server. I could not find an easy was to fix it though. I was trying to add a new module to an existing installation I called Sage support and they could not find anything short of uninstalling and re-installing. This had the SWK add-on and they seemed to think that was the cause although I'm not convinced. I think it has something to do with common files and having multiple versions installed on the same server. I copied the entire MAS90 directory off to another location and uninstalled and re-installed along with my new unlocking keys and the module I was adding. then I re-installed the POS add on. After all that I then migrated the data from my copied installation. a real PIA compared to just adding a module.

Not sure of what you were doing or where you were in what you were doing but... I believe this means that the setup can not find in the registry the ProductGuid. Prior to 2013 you will find in the uninstall directory for each install of Sage 100 the ProductGuid. This must match your setup.ini on the install CD for it to update or install to the same instance. Other reason could be that pvxcom is trying to start to read data from the folder you selected and it isn't starting so it can not return data it needs to complete.

@DavidOverholt The registry that I noted in my post would have fixed your issue. If the setup.ini on the CD doesn't match the registry ProductGuid it will think you are doing a clean install and not allow an upgrade. If this was 2013 then it wouldn't have been the case since they changed the method they use for installs.

Thanks Todd, so we need to edit the registry? Can you point us to where that is located in the registry? I'm not sure if I will ever run into it again, but would be nice to have if I do

The registry depends if you are 64 bit or 32 bit but it would be hklm\software\<wow6432node>\microsoft\windows\currentversion\uninstall\<instance>. The productGuid should match what is in the setup.ini on the root of the CD. If they don't then you are trying to install a different product or version(MAS90, MAS200, SQL or 4.4, 4.3, etc ). If it is missing the ProductGuid in the registry just add it and use the ID from the setup.ini (making sure it is the same version and prodcut).

I'm making notes on this so am interested in the resolution as well. Seems like the type of thing that could cause major aggravation if someone runs into it in 6 months.

Excellent - thanks