There may be a few reasons for this problem to occur:
- It may be a space in the install directory due to which you might encounter this problem.
- Ensure that you are not using the sa user for configuration.
- Ensure that the password does not contain any special characters.
If the above is ruled out. Check if the checkdb.log has recorded something similar to the following -
10/23 11:00:16.98 server sql_ckeckdb 5896 SEVERE_ERROR sqlclass.c 431 Failed to logon to SQL Server (sa-ca-health1) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=18456 SQL State=42000] Login failed for user 'ServiceDesk'.
10/23 11:04:16.78 server sql_ckeckdb 1616 SEVERE_ERROR sqlclass.c 431 Failed to logon to SQL Server (sa-ca-health1) Reason: [Microsoft OLE DB Provider for SQL Server] [ SQL Code=18456 SQL State=42000] Login failed for user 'ca.user'.
If yes, in that case you might be using a complex password.
In case configure.log carries following error:
10/23 11:00:17.243 INFO MonitorSQLMDB.java 67 Null file passed to MonitorSQLMDB, using default at C:\DOCUME~1\ca.user\Local Settings\Temp\mdb\mdbstatus.log
10/23 11:00:17.384 INFO InstallMSSqlMdbTask.java 180 The syntax of the command is incorrect.
10/23 11:00:17.384 ERROR InstallMSSqlMdbTask.java 192 Configure SQL server returns code 255
10/23 11:00:17.384 WARN TaskMediator.java 210 Configure MS SQL Server: Task failed (Configure MS SQL Server). Continue?
If yes then do the following:
Change the Environment variable path of TEMP and TMP to -
Now run the configure again. It should run without any issues.