Problem Description:-
This is created while creating a manual instance of WMSDE using the
following command :
c:program filesmicrosoft sql server sp4wmsdesetupsqlrun16.msi
DISABLENETWORKPROTOCOLS=1 DISABLEAGENTSTARTUP=1 DISABLETHROTTLE=1 SAPWD=2194032892
INSTANCENAME=SharePoint DATADIR="C:Program FilesMicrosoft SQL Server" /l*v
C:wsmde.log
When we try to create a instance of MSDE manually , we may get the following error:-
Setup failed to configure the server. Refer to the server error logs and setup
error logs for more information.
If we check the error log created during the same command ( i,e c:wmsde.log ) we
see the following errors :-
MSI (c) (FC:54) [13:07:13:328]: Font created. Charset: Req=0, Ret=0, Font: Req=MS
Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and setup
error logs for more information.
MSI (s) (BC!E8) [13:08:06:171]: Product: Microsoft SQL Server Desktop Engine —
Setup failed to configure the server. Refer to the server error logs and setup
error logs for more information.
Error the following data files were found in data directory:
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamsdbdata.mdf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamsdblog.ldf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamaster.mdf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamastlog.ldf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamodel.mdf
C:Program FilesMicrosoft SQL ServerMSSQL$SHAREPOINTDatamodellog.ldf
Setup has detected existing data/log files. Please make sure to delete/move the
files before re-running setup
Ending custom action DetectExistingData
Action ended 13:08:06: DetectExistingData.2D02443E_7002_4C0B_ABC9_EAB2C064397B.
Return value 3.
Action ended 13:08:06: INSTALL. Return value 3.
Resolution:-
This would generally happen if a previously installed version of the similar
instance is present either in files or in registry.the log file will tell us where to look for.
Open the log file and scroll to the bottom.Then search for "failed" upwards.
the first occurrence of this error will generally be followed by the reason of
failure.This can either be instances of the instance in the registry , or files on the NTFS
partition.The above log was a failure on the NTFS partition.
Renaming the MSSQL$Sharepoint folder under C:Program FilesMicrosoft SQL Server
might resolve the issue.
In another case there are instances of the GUID in registry that indicate a
previously installed instance.
TO make sure we dont have old instances in registry , look for those GUIDs :
1] Make sure the instance is removed from this location :
HKLM software microsoft microsoft sql server Installed Instances
2] Make sure you do not have any failed attempts under :
HKLM software microsoft microsoft sql server Component Set
3] The same GUID that you see above will be seen as an incomplete GUID under this
key :-
HKLM software microsoft microsoft sql server setup { …GUID…}
Removing the faulty registry GUIDs after a backup should enable us to install a
clean instance of WMSDE.
susguperf 