Solutions to some of the SQL issues when installing ACT! 2011

Re-posted, with permission from Ben Hamilton

This is a set of common issues we have seen when installing SQL 2008 (which is part of Sage ACT! 2011), especially when upgrading a previous version that used SQL 2005

Remove .Net Framework 4.0 before install

The support staff in Sage Business Solutions Melbourne (bless ‘em) gave me a pointer that if “Microsoft .NET Framework 4 Client Profile” is installed it gives troubles. Therefore they suggested uninstalling it prior to commending an SQL 2008 install. I don’t know why or what but this was an important step. Note that just doing this still gave me a failed SQL install. I’d love to know more about the ‘why’ here. I’d also like to have been informed earlier instead of after me jumping up and down and making phone calls. But that’s a topic for another day. For now I’m very happy with their suggestion as it does appear to have contributed to a successful install, which is GOAL NUMBER ONE.

 

SQL Service Account

During the install you get the option to set which account the SQL Server Database Engine uses, instead of setting to NT AUTHORITY\SYSTEM as per Sage KB26994, leave it as the default. After the installation is complete you then go to services.msc and change it to Local System then.

 

Avoid Special characters in the path

As per Microsoft KB955666 you can’t use a ‘number’ or ‘pound’ (#) sign in the path name. Now I did NOT have a pound sign in the path, but there was a space in one of the folder names and a ‘plus’ sign (+). So taking to heart Microsoft's admonition, I copied the installer to a folder C:\SQL2008ExpR2\*.* and ran it from there.

 

Various other issues and resolutions

  • “MsiGetProductInfo failed to retrieve ProductVersion for package with Product Code = ‘{4AB6A079-178B-4144-B21F-4D1AE71666A2}’. Error code: 1608.. ” See here and here.
  • “Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.” See here.
  • “Error: 15209, Severity: 16, State: 1. An error occurred during encryption.” See here.
  • Attempting to open registry subkey Software\Microsoft\PCHealth\ErrorReporting\DW\Inst​alled
    Attempting to get registry value DW0200
    Submitted 1 of 1 failures to the Watson data repository
    Refer here, here and here.

Hope this helps someone short cut the time to resolve their SQL install.

Please add Comments with any other issues and resolutions you might find when installing SQL 2008 (especially when upgrading from SQL 2005)