Installation of Non-MS Fonts cause .NET errors during SQL server 2005 setup

Setup is ideally supposed to be an easy process, but more often than not we are fraught with a multitude of errors. This blog is intended to make life a little easier when it comes to SQL server setup.

When we run SQL 2005 setup we get the following error:

SERVERNAME: Setup has detected a problem with Microsoft .Net Framework installation and cannot proceed. Microsoft .Net Framework 2.0 is either not installed on this system or is corrupt.

This is a seemingly ambiguous error which does not directly deal with the underlying .NET being corrupt

Cause

Installation of Non-standard Microsoft fonts cause errors during SQL server 2005 setup

Resolution

· From the core (local) log obtained this error:

<Func Name='PerformDetections'>

0

<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>

<Func Name='DisplaySCCWizard'>

CSetupBootstrapWizard - unknown error 0x80070057

<EndFunc Name='DisplaySCCWizard' Return='-2147024809' GetLastError='183'>

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Failed to load the Wizard UI. There is either a problem with .Net framework installation or it is not installed. : -2147024809

Message displayed to user

                Setup has detected a problem with Microsoft .Net Framework installation and cannot proceed. Microsoft .Net Framework 2.0 is either not installed on this system or is corrupt.

· Conventional methods to tackle the .NET error did not resolve the issue

· We tried multiple reinstallation attempts of the .NET framework 2.0

· We had encountered previous issues where issues were caused by the Non-standard Microsoft fonts and on uninstallation of these and subsequent restart we were able to run the SQL setup successfully

How did we arrive here?

 

· We went ahead to obtain a memory dump of the SQL Server setup and found an exception

Exception message:

Font 'Albertus Extra Bold (W1)' does not support style 'Regular'

· We went ahead and removed the 'Albertus Extra Bold (W1)' font

      (Refer : https://support.microsoft.com/kb/314960 )

· After a server reboot when we ran setup again we were successful.

· We have encountered similar issues with following non-standard Microsoft fonts as well :

· Bitstream Vera Mono Bold Italic (VeraMoBI.ttf)

· Bitstream Vera Mono (VeraMono.ttf)

· Bitstream Vera Mono bold (VeraMoBd.ttf)

· Bitstream Vera Mono Italic (VeraMoIt.ttf)

 

Amrutha Varshini J

Support Engineer, Microsoft SQL Server.

Reviewed By

Amit Banerjee
Technical Lead, Microsoft SQL Server