“Failed to get a SQL Server connection. Either the SQL Server is not running, or all connections have been used.”

I am getting a Status Message ID of 600 for the SMS_DATABASE_NOTIFICATION_MONITOR Component with the following error:

“Failed to get a SQL Server connection. Either the SQL Server is not running, or all connections have been used.”

“SMS Site Component Manager failed to reinstall this component on this site system.”

I have my Site Database and Site Server installed on different servers.

I am unable to backup my Site and if I look under Component Status I see a Status Message ID of 1020 for the SMS_SITE_SQL_BACKUP_ Component stating:
 
SMS Site Component Manager failed to reinstall this component on this site system.
 
Solution: Review the previous status messages to determine the exact reason for the failure. SMS Site Component Manager will automatically retry the reinstallation in 60 minutes. To force SMS Site Component Manager to immediately retry the reinstallation, stop and restart SMS Site Component Manager using the SMS Service Manager.
 
Looking in the Application Log on the SQL Server there was an Event ID 1020 present from SMS Server with the following description:
 
The description for Event ID 1020 from source SMS Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
 
If the event originated on another computer, the display information had to be saved with the event.
 
The following information was included with the event:
 
On 10/01/15 15:15:30, component SMS_SITE_COMPONENT_MANAGER on computer reported: 
60

If I look in sitecomp.log I see:

    Reinstalling component SMS_SITE_SQL_BACKUP…
STATMSG: ID=1018 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_SITE_SQL_BACKUP_” SYS= SITE= PID=2300 TID=5640 GMTDATE=Wed Sep 30 23:12:59.623 2015 ISTR0=”” ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0
      Starting bootstrap operations…
        Component file list item in the install map for component SMS_SITE_SQL_BACKUP does not contain srvboot.exe.
      Bootstrap operations aborted.
LogEvent(): Failed to log Event to NT Event Log (HRESULT=0x6be)!
      The server already contains some of the required files for this component.  A disk space check will not be made.
      Installed file \\\$\SMS_\bin\x64\smssqlbkup.exe.
Disabling Wow64FsRedirection…
Revert Wow64FsRedirection…
      All files installed.
      Starting bootstrap operations…
        Component file list item in the install map for component SMS_SITE_SQL_BACKUP does not contain srvboot.exe.
      Bootstrap operations aborted.
    Reinstallation failed and will be retried in the next polling cycle.
LogEvent(): Successfully logged Event to NT Event Log (1, 77, -1073740804, (null)).
STATMSG: ID=1020 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_SITE_SQL_BACKUP_” SYS= SITE= PID=2300 TID=5640 GMTDATE=Wed Sep 30 23:12:59.810 2015 ISTR0=”60″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0
      Releasing current connection to server.
      Releasing Abstract Network object.
  Finished polling server …
Thread “SiteComp server polling Thread #1” id:5640 terminated normally
 
And then lower down in the log:
 
      ERROR: NAL failed to access NAL path “MSWNET:\\\admin$\”, probably because the machine is down, the network is down, or the Site System Connection Accounts are misconfigured.  NAL INetworkObject::IsAccessible() returned 0x80070079: The operation completed successfully.
STATMSG: ID=1037 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_SITE_COMPONENT_MANAGER” SYS= SITE= PID=2300 TID=5968 GMTDATE=Thu Oct 01 00:13:18.725 2015 ISTR0=”\\” ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0
      Server will be reinstalled in the next polling cycle.
STATMSG: ID=1057 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_SITE_COMPONENT_MANAGER” SYS= SITE= PID=2300 TID=5968 GMTDATE=Thu Oct 01 00:13:18.725 2015 ISTR0=”\\” ISTR1=”60″ ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0
      Component SMS_SITE_SQL_BACKUP flagged for reinstallation.
STATMSG: ID=1017 SEV=I LEV=M SOURCE=”SMS Server” COMP=”SMS_SITE_SQL_BACKUP_” SYS= SITE= PID=2300 TID=5968 GMTDATE=Thu Oct 01 00:13:18.725 2015 ISTR0=”60″ ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0
 
And things just keep looping round from there. 

“SMS Site Backup failed while creating the snapshot using the VSS services. Aborting the backup operation.”

I have ConfigMgr installed with the Site Server and Site Database Server running on different servers.

I’m seeing a Status Message ID 5047 for the SMS_SITE_BACKUP Component stating:

SMS Site Backup failed while creating the snapshot using the VSS services. Aborting the backup operation.

If I look in the smsbkup.log I see:

Component 6 – Backup\SiteDBServer\SMSbkSQLDBsite.dat.
Dependency On SQL Writer , LogicalPath:\\, ComponentName:SMS_
After GatherWriterMetadata SMS Writer status = FAILED_AT_PREPARE_BACKUP.
Error: VSS_E_WRITERERROR_TIMEOUT. Error Code = 0x80,042,3f2.
Starting to clean and prepare the backup location.
Cleanup and/or preparation done.
Info: Sending message to start the SQL Backup…
Starting to create the snapshot set.
Added volume containing :\ to the snapshot set.
Info: Starting Asynchronous PrepareForBackup…
Info: Asynchronous PrepareForBackup finished…
Info: Waiting for SQL to PrepareForBackup.
Sleeping for 5 seconds…

Sleeping for 5 seconds…
Error: Sql Server could not prepare for the Backup.
Aborting the backup process.
 
Error: CreateSnapshotSet failed…
STATMSG: ID=5047 SEV=E LEV=M SOURCE=”SMS Server” COMP=”SMS_SITE_BACKUP” SYS= SITE= PID=64352 TID=64128 GMTDATE= ISTR0=”” ISTR1=”” ISTR2=”” ISTR3=”” ISTR4=”” ISTR5=”” ISTR6=”” ISTR7=”” ISTR8=”” ISTR9=”” NUMATTRS=0
SMS site backup failed. Please see previous errors.

There are no errors in smssqkbkup.log
 

“Failed to copy the database files to the backup location. Please ensure that the SMS_SITE_SQL_BACKUP component has access to the backup location.. Backup operation is not completed”

I’m seeing a Status Message ID 5052 for the SMS_SITE_BACKUP Component stating:

SMS SQL Backup service on the SQL server <a href="http://\\”>\\ failed to backup the SMS database CM_. The error reported by the service is Failed to copy the database files to the backup location. Please ensure that the SMS_SITE_SQL_BACKUP component has access to the backup location.. Backup operation is not completed.

“A .NET Framework error occurred during execution of user-defined routine or aggregate” in StateSys.log and SMS_STATE_SYSTEM component has a “Critical” status

If I look in the ConfigMgr Console the SMS_STATE_SYSTEM Component is showing with a Critical Status.

If I look in the StateSys.log I see:

*** [42000][6522][Microsoft][SQL Server Native Client 11.0][SQL Server]A .NET Framework error occurred during execution of user-defined routine or aggregate “fnReadMDMPolicyCertValidationDuration”: ~~System.Data.SqlTypes.SqlTypeException: Two strings to be compared have different collation.~~
System.Data.SqlTypes.SqlTypeException: ~~
at System.Data.SqlTypes.SqlString.StringCompare(SqlString x, SqlString y)~~
at System.Data.SqlTypes.SqlString.Compare(SqlString x, SqlString y, EComparison ecExpectedResult)~~
at Microsoft.SystemsManagementServer.SQLCLR.CryptoUtility.fnReadMDMPolicyCertValidationDuration(SqlString MessageText)~~.
: sp_UpdateAPNSCertAlertVariable

Why if I make a change to Client Settings that generates a large volume of State/ Status messages does it take longer to process them?

I’ve changed Client communication from HTTPS to HTTP in Client Settings which has generated a large volume of State/ Status messages.

However, I’ve noticed that it’s taking longer to process these than normal.

Why can’t I see the Status Messages I am expecting to see?

I am trying to view all of the Status Messages for all of my Sites but I’m only seeing messages from certain Sites, not all of them.

Why are State messages wrongly marked as Corrupted from Simple Certificate Enrollment Protocol Configuration Items that are targeted to devices and that contain a user entry of SYSTEM?

I’ve noticed that State messages are wrongly marked as corrupted from Simple Certificate Enrollment Protocol Configuration Items that are targeted to devices and that contain a user entry of SYSTEM.

“ERROR: The component item for SMS_STATUS_MANAGER in the master site control file does not contain property list items for a status filter named “SMS_STATUS_MANAGER”, or those property lists are corrupt or badly formatted”

I’ve noticed that Status Manager is not processing changes to built-in Status Filter Rules on localised ConfigMgr installations.

If I look in STATMGR.log I see:

ERROR: The component item for SMS_STATUS_MANAGER in the master site control file does not contain property list items for a status filter named “SMS_STATUS_MANAGER”, or those property lists are corrupt or badly formatted

Why is the “HardwareID” field not unique on Linux when the same VHD is used?

I’ve noticed that if I use the same VHD that the HardwareID field is not unique on Linux.