Today I had this problem for the second time. Last time it cost me 3 hours to find the solution. Now I find your article and I fixed it in 30 minutes
My Exact error was (summary.txt):
MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
The workaround resolution involves the following steps:
For a stand-alone installation of SQL Server 2005
Remove the following registry subkeys that store SID settings:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\SQLGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\AGTGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\FTSGroup
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.X\Setup\ASGroup
Note In these registry subkeys, MSSQL.X is a placeholder for the corresponding value on a specific system. You can determine MSSQL.X on a specific system by examining the value of the MSSQLSERVER registry entry under the following registry subkey:
Reinstall the SQL Server 2005 service pack or the SQL Server 2005 hotfix package.
For some reason, the local SIDs had been changed or removed or something and SQL just needed to figure out what was going on.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL\
When you access the reporting services over SSL you can have the problem that the reporting services GUI under IE is very slow.
The solution is quite simple: Login with the servername or domain name. E.g: SERVERNAME\username
This problem exist under IE 8 and IE9 under Server 2008, 2008r2, Vista and Windows 7.
SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')
If you want to use mysqldump to back up the database, you can enter the full path when typing the command, or add the path c:\wamp\bin\mysql\mysql5.0.51b\bin to the System variable PATH in Control Panel – System – Advanced – Environment Variables – System variables.
You can make a backup from the command line or a scheduled task in Windows like this, assuming that myusername and mypassword have access to the database mydatabase:
mysqldump -umyusername -pmypassword mydatabase > mydatabase.sql
You can restore the database using the mysql command from the command line:
mysql -umyusername -pmypassword -D mydatabase < mydatabase.sql
More info from the command line:
mysql –help | more
–* you can get the logical log file name usingthe following command in Query Analizer:
Now execute the following command to shrink the database log to 200MB:
DBCC SHRINKFILE ("logicalLogFileName", 200) BACKUP LOG "databaseName" WITH TRUNCATE_ONLY DBCC SHRINKFILE ("logicalLogFileName", 200)
–if it doesn’t work, run the two commands again.
–When done with that, do a full backup of your db as you will have broken your tlog backup chain.
USE databasename; GO -- Truncate the log by changing the database recovery model to SIMPLE. ALTER DATABASE databasename SET RECOVERY SIMPLE; GO -- Shrink the truncated log file to 1 MB. DBCC SHRINKFILE (2, 1); -- here 2 is the file ID for trasaction log file,you can also mention the log file name (dbname_log) GO -- Reset the database recovery model. ALTER DATABASE databasename SET RECOVERY FULL; GO