The log file shows success in testing DB connection. The error is with CoreDButil.exe
log below is the error...
2016-12-29 10:56:48 INFO: Executing: D:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe /buildcomponents /DDON /xml="D:\Program Files\LANDesk\ManagementSuite\datamart.xml" /logpath="C:\ProgramData\LANDESK\ManagementSuite\Install\10.1\Log" (Launcher.ExecuteXmlCommand()) 2016-12-29 10:57:54 ERROR: Execution of CoreDBUtilDatamart completed. Return code: 1, State: Failure (SetupController.ExecuteNextCommand())
And the CoreDButil.log is
12/29/2016 13:43:53 INFO 4680:1 RollingLog : Argument: /logpath=C:\ProgramData\LANDESK\ManagementSuite\Install\10.1\Log
12/29/2016 13:43:54 ERROR 4680:1 DataServices.OleDbHelper : Initialize(); exception: ex = Login failed for user %user%
Well - this part is pretty indicative ...
Login failed for user %user%
... you may have fat-fingered the password and/or username?
Double-check the events on the SQL Server side -- that'll help make sure whether you fat-fingered the username (that part it should show in the event) or the password (if the username is correct, then this is the only option).
Hope that helps?
Well yes it does appear so!
But the database connection test using same credentials prior goes through perfectly. The account on SQL side is not locked out.
Are you saying the database connection test only checks for the existence of a DB rather than testing the credentials?
Also this is the same credentials as our existing production 9.5 DB...
so it's not that straight forward. if i check the configuration tool the password section is blank.. and i get the same error if i click the inventory tab..
if the SQL side was fat fingered I am confused as to how we get a test success prior.... checking SQL side now...
Ok this account logs on fine to SQL. It is the same credentials added to the Test connection at start of install. if anything fat fingered its in the code passing the credentials entered across... to add to this and complicate further its the same account that we use on our 9.5 prod DB... which is working fine... however there are login failed results on the SQL side... which makes no sense if we can log in manually..
this is strange i know. I have a ticket open with support too. is there anything else it could be?
Ok so we decided to retry using a new account - we used a similar password but with a few less characters
When we re ran after reverting back to a fresh snapshot the install passed the datamart config -
So all we can see is that for some reason LANDesk 2016 did not like the password - like i said the manual login worked fine and its the same user / password as our prod 9.5 DB!
Not sure what to make of this...
So it was confirmed some special characters were not liked by the LANDesk 2016 DB. If this happens to you take one or two characters out.
I hope belowd docs help: