When installing an Azure DevOps organization for Configuration Manager, you might encounter an issue during the installation process: a failure in setting Contributors as administrators for the project library after multiple attempts.
By verifying the membership of the Tenants\Contributors group, properly adding necessary build service accounts, and adjusting security settings within the Pipeline Library, you can typically resolve the issue.
If you encounter this error, follow the step-by-step solutions to overcome the problem.
Error
During the installation of Configuration Manager, the process may proceed as follows:
Initial Step:
“Installing your organization…”
Error Encountered:
“Cannot make Contributors admin for project library after 5 attempts. Please try again.”
The error typically presents itself with additional technical details:
An error has occurred
at u.setContributorsAsAdminForProjectLibrary (https://cm.coreview.com/js/chunk-common.8b548a68.js:1:80930)
at async u.updateProjectPermissions (https://cm.coreview.com/js/chunk-common.8b548a68.js:1:82869)
at async u.installOrg (https://cm.coreview.com/js/chunk-common.8b548a68.js:1:62897)
at async Proxy.i (https://cm.coreview.com/js/613.c9d5fbec.js:1:9092)
{"innerError":null,"isLiteralMessage":false,"message":"Cannot make Contributors admin for project library after 5 attempts. Please try again.","name":"An error has occurred"}This stack trace indicates a failure in setting Contributors as administrators for the project library after multiple attempts.
Solution
To resolve this issue, follow the steps below.
Step 1: verify membership of Tenants\Contributors
First, ensure that the Tenants\Contributors group is correctly configured. It should be a part of your project's membership structure accessible from the Project Settings.
In Project Settings:
- Select “Permissions”
- Select “Contributors”
- Select the “Members” tab
Example of membership structure:
If your setup resembles the above example, proceed to add the build services as listed below:
Step 2: Add Build Services
Click the “Add” button and select:
- “Project Collection Build Service”
- “Tenants Build Service”
Properly assigning build services to the Contributors group can often rectify the issue.
Once you've completed these steps and made the necessary manual changes, attempt to reinstall the organization. If configured correctly, the installation should proceed successfully.
If the issue persists, please proceed as follows.
Step 1: access Library Security
If the problem remains unresolved after following the above steps, proceed with the following actions:
Access the Library:
- Navigate to the Library section within your DevOps project.
- Navigate to the Security section
- Set the Contributors group as administrators.
Project Naming
You might see your Contributors group listed under a different project name, such as [MyFirstProject]\Contributors.Solution.
Instead of [MyFirstProject], look for:
- [Tenants]\Contributors
- or replace Tenants with the actual name of your project if it differs.