The databases we've installed in those years---counting the various issues encountered during SQLSERVER2008 installation (ongoing updates)

To oneself Ann over sqlServer2008, also give a lot of classmates Ann over sqlServer2008, during the encounter a lot of different people upset problem, in here to tidy up, (involved in part of the method is found on the Internet, some have not tried, just here to tidy up, hereby declare)

Error One : Error creating System.Diagnostics configuration section Handler: This problem will always require a reboot when checking the configuration

failed to load file or assembly "System, version=4.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089" or one of its dependencies.                                               The system cannot find the file specified. (C:\Windows\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 28) error code 0x84b10001.

Workaround: (Win7)
Delete C:\Users\Administrator\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0 \user.aconfig.xml file is available

Error Two : SQL Server 2008 installation occurs when an invoke or BeginInvoke error cannot be invoked on a control

workaround :(i) "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager" found on the registration form and delete the value of "PendingFileRenameOperations" below it. and then perform the installation again.

(ii) A service program for VC 2010 Mscorsvw.exe process invoke invoke causes, end this process, you can.

Error three : Reload SQLServer2008, Tip: Msigetproductinfo cannot retrieve the productversion of the package for Product Code {xxxxx}. Error code: 1605

Workaround : Execute cmd.exe, then open the Register editor regedit.exe, navigate to Hkey_classes_root\installer\upgradecodes,  then search eb28d9c4, the search to the key value of the parent node deleted, OK. It is important to note that EB28D9C4 is the first part of the message that {4c9d82eb-9001-4e59-8f64-0beee5f4a30a} is inverted. Erase it and install it again.

Error Four : "There are validation errors on this page" appears on the server Configuration page

Workaround : This problem is caused by manual configuration of username and password, it is recommended to select "Use same account for all SQL Services", in the popup form, username fill System,password not fill in

error Five : "Invalid user-supplied credentials" appears on the server Configuration page

Workaround : same as the fourth question.

error six : object of type ' Microsoft.SQL.Chainer.Package.PropertiesTypeProperty ' cannot be converted to type ' Microsoft.SQL.Chainer.Package.PropertiesTypeProperty ".

Solution : Small part said not met, online said to unpack the installation package after the installation is good, but I have been using the virtual CD-ROM installed

error Seven : Error 1406: Cannot write value debugger to the Register ... Please make sure you have sufficient access to the registration entry

Workaround: Right-click on the installer (EXE) and execute it as an administrator

error eight : Fatal error 1316

Workaround: can ssceruntime-chs-x86.msi first renamed to Ssceruntime_x86-chs.msi and then put it in the installation source folder under the 2052_chs_lp\x64\setup folder, If you install it again, you can.

error Nine : reboot failed when checking configuration, and failed multiple times, always prompt to restart

Workaround : Delete the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager for the registration form The PendingFileRenameOperations item in the

Error 10 : appears at end of installation: MOF compiler cannot connect to Wmiserver

Workaround :(a) check the system32 under Windows for FrameDyn.dll This system file, assuming that there is no System32 Copy FrameDyn.dll to system32 folder under the WBEM file .

(b) If not, there is a way to first uninstall VS, I have not tried, think it is not as good as the reinstall system, we can Baidu such a method

Error 11 : need to be replenished

The databases we've installed in those years---counting the various issues encountered during SQLSERVER2008 installation (ongoing updates)