Overview:

Sage 50 Error Code 1608 is otherwise called the "Installation Error. It is a great deal like that of Sage 50 Error Code 1605. The Sage 50 Error 1608 typically happens at the hour of the establishment of the Sage 50 bookkeeping programming and furthermore has similarities with a couple of other Installation Error Codes like 1605. 

The Sage 50 Installation Error code 1608 by and large happens on the Windows working framework (OS) and furthermore while introducing a portion of different projects like ACT7 SQL Server 2008R2

What are the causes of Sage 50 Installation Error 1608? 

Sage 50 Error 1608 is an Installation Error that occurs due to: 

• This Error could likewise happen when you are attempting to endeavor to introduce ACT7 SQL Server 2008R2. 
• At the point when this mistake happens, you will get to see the accompanying message springing up on your screen:

"MsiGetProductInfo neglected to recover Product Version for bundle with Product Code = '{GUID}'. Mistake Code: 1608."

• The Sage Install Error Code 1608 happens significantly because of errors with or in the OS. 
• The two primary drivers that stand apart as the most probable reason for this error and furthermore that it is viewed as the most widely recognized model. 
• You could experience this mistake likewise when you are presumably not signed in as a director of your framework or when your Windows vault or the Install Shield can't work really.

We will now go through the different Arrangements that can help solve the Sage 50 Installation Error 1608

Now we shall discuss the different arrangements that can be implemented to fix the Sage 50 Installation Error 1608 in Detail: 

Arrangement 1: Appeon Setup.Ex

• You are expected to run the introduce driver for IDriver.exe and Idriver2.exe, that is situated in the C:\ drive
• Then, you really want to run "Appeon setup.exe" record

Arrangement 2: Set the File

• You want to open the Control Panel
• Once done, you want to tap on Systems Advanced Performance Virtual Memory
• From that point onward, you want to make changes under the suggestion that is referenced with respect to that of the size and initials
• By and by, you want to go to the Control Panel System Advanced Performance Virtual Memory
• Then, you should make changes in introductory alongside most extreme size upto 0
• Once done, you want to restart the framework
• You can hinder the record to its ideal size
• This cycle, in turn, compels it to reproduce a page record.

Arrangement 3: Idriver

• You really want to see regardless of whether the IDriver has been introduced appropriately
• From that point onward, search for the accompanying record situated in your C:\ drive: "index C:\Program Files\Common Files\InstallShield\Driver\8\Intel 32".dllexe
• Whenever you have found them, you really want to run "regsvr32" on each of the documents notwithstanding, "_ISRES1033.dll and Idriver.exe" and afterward run "idriver/regserver"

Arrangement 4:UpgradeCodes

• You really want to choose the "Windows Start" choice
• From that point onward, click on "Run"
• At the point when you can see the Run order box has showed up, go to the Search field and type "regedit"
• You will see the "Windows Registry" window has showed up on your screen
• Go to the area "HKEY_Classes_Root\Installer\UpgradeCodes" then, at that point, left click on the "UpgradeCodes"
• Trade the "UpgradeCodes" envelope with the choice of "File\Export" through Selected Branch send out range
• You are expected to rename the "UpgradeCodes" organizer to "UpgradeCodesOld"
• Physically introduce Microsoft SQL Server 2008 R2
• Import the sent out "UpgradeCodes" with the choice of "File\Import"
• At last, send off the Sage ACT! establishment process 

Arrangement 5: OS Windows

• In the event that your OS is Windows 98, you want to introduce Microsoft DCOM 98 preceding reinstalling your OS.
• MS Windows incidentally experiences the Sage error code 1608 and for this, it offers the choice to analyze and resolve the issue of course, set up to uninstall and reinstall the program.
• At the point when you pick that choice, it will fix the harmed or contaminated library keys on 64 cycle OS as well as those that deal with the update information.

Arrangement 6: Install Shield

• Continue towards uninstalling Install Shield from your framework; erase the organizer containing the Install Shield program documents and afterward make the envelope again by running the program arrangement. 
• Re-run the arrangement once the establishment is finished. 
• Tidy up your arrangement of all Temp grinds and close down whatever other application that might be running in your framework. Then, re-run the Install Shield arrangement.

Final Comment: 

At this point, your mistake has been disposed of and you can run your Sage 50 bookkeeping programming effectively. In any case, still the issue suffers; you fundamentally need to call the Sage live chat to assist you with repairing the slip message so you can work usefully on your Sage bookkeeping programming.