In SharePoint 2016, if you try to change the settings of Content Database via PowerShell while using the Pipeline feature in your command, it throws an error.
Here, we are trying to set the content database max site count to 5 and warning site count to 4. We use the following command.
- Get-SPContentDatabase "WSS_content" | Set-SPContentDatabase -MaxSiteCount 5 -WarningSiteCount 4
- PS C:\Users\kfinst> Get-SPContentDatabase "WSS_content" | Set-SPContentDatabase
- -MaxSiteCount 5 -WarningSiteCount 4
Here is the error we get.
"Set-SPContentDatabase - Could not connect to SPContentDatabase Name=WSS_Content using integrated security - Cannot connect to database master at SQL server at SPContentDatabase Name=WSS_Content. The database might not exist, or the current user does not have permission to connect to it. "
- At line:1 char:39
-
- + Get-SPContentDatabase "WSS_content" | Set-SPContentDatabase -MaxSiteCount 5
-
- -War ...
-
- +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
- + CategoryInfo : InvalidData: (Microsoft.Share...ContentDatabase:
-
- SPCmdletSetContentDatabase) [Set-SPContentDatabase], SPException
-
- + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletSetConte
-
- ntDatabase
-
- PS C:\Users\kfinst>
![]()
No matter what method we use in the pipe, it is not working at all.
- Get-SPContentDatabase " 12345678-90ab-cdef-1234-567890abcdef" | Set-SPContentDatabase -MaxSiteCount 5 -WarningSiteCount 4
Or
- Get-SPContentDatabase -webapplciation "http:
And, all the time, we get the same error.
"Set-SPContentDatabase : Could not connect to SPContentDatabase Name=WSS_Content using integrated security: Cannot connect to database master at SQL server at SPContentDatabase Name=WSS_Content. The database might not exist, or the current user does not have permission to connect to it."
Resolution
This is a bug in the command and already reported to Microsoft. Microsoft is currently working on this and hopefully, it will be fixed in future updates. We will update this as soon as Microsoft released the fix. In SharePoint 2010/2013, it is working fine.
Workaround
Currently, there are two workarounds for such situation. You can use PowerShell without using the pipe option in command, or use the Central Admin and change the settings of the Content Database.
PowerShell
In order to change the settings of the Content Database, don't use the pipe line.
- Set-SPContentDatabase –identity "WSS_Content" -MaxSiteCount 5 -WarningSiteCount 4
To confirm the settings, please run the below command.
- $db = Get-SPContentDatabase "WSS_Content"$db.MaxSiteCount$db.WarningSiteCount
![]()
Central Admin
Another method is to use the Central Admin and change the settings of Content Database. Please follow the below steps to change the settings.
- Log on to Central Admin Site with Farm Admin account.
- Go to Application Management >> Manage Content Database.
- On this page, select the correct Web Application.
- Click on the name of Content Database (it will be hyperlink).
- On this page, you can then change the required settings (Status, Remove Content Database, Maximum Site Count, Warning Site Count, preferred Timer Job Server).
Applies to
This applies only to SharePoint Server 2016 (January 2017 Updates).