-
Notifications
You must be signed in to change notification settings - Fork 730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SP 2016 deployment failing to deploy, 1805 #351
Comments
@amazaheri can you send me the list of all items in the resource group and their deployment status? I assume this is related to an issue provisioning one of the SQL Server components. Thanks |
|
Same exact problem here: The user does not exist or is not unique. I wonder if this has anything to do with the fact that Sharepoint Setup User is the same as admin-user? Edit: I have no idea, SQL srv seems to have been set up just fine, but after delving a bit more in the errors it seems the problem lies there. |
From Get-DscConfigurationStatus
|
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'ConfigureSPServer'. Error message: DSC Configuration 'InstallAndConfigureSharePointServer' completed with error(s). Following are the first few: The user does not exist or is not unique. Object reference not set to an instance of an object. Cannot perform security configuration because the configuration database does not exist. You must create or join to a configuration database before doing security configuration."\r\n }\r\n ]\r\n }\r\n}"}]}
The text was updated successfully, but these errors were encountered: