look at the dbmon log, not the ccm log. you are reading errors the server is having trying to deploy the client.
On Mon, May 2, 2016 at 11:21 AM, <stefaniebur...@verizon.net> wrote: > Hello our primary site can not longer connect with the Database. I see > this error. Any ideas? > > ~ DoingAccount Cleanup Operation > .... SMS_CLIENT_CONFIG_MANAGER 4/27/2016 2:18:36 AM > 12832(0x3220) > > ~Processing > domainPROD SMS_CLIENT_CONFIG_MANAGER 4/27/2016 2:18:36 > AM 12832(0x3220) > > ~Trying each entry in the SMS Client Remote Installation > accountlist SMS_CLIENT_CONFIG_MANAGER 4/27/2016 > 2:18:36 AM 12832 (0x3220) > > ~ Attempting to connect toadministrative share > '\\\\SSSService' SMS_CLIENT_CONFIG_MANAGER 4/27/2016 > 2:18:36 AM 12832 (0x3220) > > ~ WNetAddConnection2 failed(LOGON32_LOGON_NEW_CREDENTIALS) using account > SSS\SSSService' (000004b3)SMS_CLIENT_CONFIG_MANAGER 4/27/2016 > 2:18:36 AM 12832 (0x3220) > > ~ LogonUser failed(LOGON32_LOGON_INTERACTIVE) using account > prod\SSSService'(00000775) SMS_CLIENT_CONFIG_MANAGER > 4/27/2016 > 2:18:36 AM 12832 (0x3220) > > ~Attempting to connect to administrative share '\\\admin$' using > machineaccount. SMS_CLIENT_CONFIG_MANAGER 4/27/2016 > 2:18:36 AM 12832 (0x3220) > > ~Failed to connect to \\\admin$ using > machineaccount(1203) SMS_CLIENT_CONFIG_MANAGER > 4/27/2016 > 2:18:36 AM 12832 (0x3220) > > ~ERROR: Failed to connect to the \\\admin$ shareusing account > 'MachineAccount' SMS_CLIENT_CONFIG_MANAGER 4/27/2016 > 2:18:36 AM 12832 (0x3220) > > ~Failed to connect to Server. Error > 1203SMS_CLIENT_CONFIG_MANAGER 4/27/2016 2:18:36 AM > 12832(0x3220) > > ~Processing > domainSSSS SMS_CLIENT_CONFIG_MANAGER 4/27/2016 2:18:36 > AM 12832(0x3220) > >
