# Common Errors and Resolutions he following errors are provided to troubleshoot issues that arise. Please refer to the solutions and resources below for answers to some commonly encountered errors. [Error message: 413: Status Error - Downloading duplicate profile files simultaneously](https://knowledgebase.autorabit.com/~/revisions/3VI0zaSEEP3zDMr0Tue8/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/error-message-413-status-error-downloading-duplicate-profile-files-simultaneously) [Error message: Authentication Failed - ALM connectivity due to incorrect configuration](https://knowledgebase.autorabit.com/~/revisions/ukRudv9dGRUL2q4Awg7g/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/authentication-failed) [Error message: Cannot Open Git-Upload-Pack](https://knowledgebase.autorabit.com/~/revisions/PhrMlDs4KPpBVZk801ve/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/cannot-open-git-upload-pack) [Error message: Cannot find the declaration of element 'web:validateSalesforceOrgConnection'](https://knowledgebase.autorabit.com/~/revisions/EdObJurOGkDws2azAf5L/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/cannot-find-the-declaration-of-element-web-validatesalesforceorgconnection) [Error message: Failed to initiate deployment. Unexpected end of JSON input.](https://knowledgebase.autorabit.com/~/revisions/1MpGiDGwK1B2XQ6cGqOG/product-guides/arm/troubleshoot/arm-faqs/ci-jobs/failed-to-initiate-deployment.-unexpected-end-of-json-input.) [Error message: Failed to push some refs to \[remote\]](https://knowledgebase.autorabit.com/~/revisions/IrtuchPWTlattwGEM6OD/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/failed-to-push-some-refs-to-remote) [Error message: GH006: Protected branch update failed for refs/heads/master. Remote: error: Cannot force-push to a protected branch.](https://knowledgebase.autorabit.com/~/revisions/b1ho43JCpidl0YWBC8yF/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/error-message-gh006-protected-branch-update-failed-for-refs-heads-master.) [Error message: GIT Push Result: RemoteRefUpdate](https://knowledgebase.autorabit.com/~/revisions/lwFT8sv76u9JoeNkeAnx/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/error-message-git-push-result-remoterefupdate) [Error: Installing CodeScan Sonar as a plugin in ARM](https://knowledgebase.autorabit.com/~/revisions/TrXw66IblXlo15giGnBb/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/installing-codescan-sonar-as-a-plugin-in-arm) [Error message: Invalid meta-xml name: lwc/xxx/xxx.css-meta.xml, should end with js-meta.xml](https://knowledgebase.autorabit.com/~/revisions/MpxNH6lUh6Wr71fvOfA2/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/invalid-meta-xml-name-lwc-xxx-xxx.css-meta.xml-should-end-with-js-meta.xml) [Error message: Invalid Schema during the Merge Prevalidation Process](https://knowledgebase.autorabit.com/~/revisions/MpxNH6lUh6Wr71fvOfA2/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/invalid-schema-during-the-merge-prevalidation-process) [Error message: Local and remote repositories are not on the same revision](https://knowledgebase.autorabit.com/~/revisions/9GkIkeaALdJ5Y23XA672/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/local-and-remote-repositories-are-not-on-the-same-revision) [Error message: Not Authorized (to Merge)](https://knowledgebase.autorabit.com/~/revisions/joyFHqtVP2clP8Y8umxN/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/not-authorized-to-merge) [Error message: Not Available for deploy for this organization](https://knowledgebase.autorabit.com/~/revisions/woSPqiPyMz4Dlkp8971h/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/not-available-for-deploy-for-this-organization) [Error message: OAuth Authentication Failed](https://knowledgebase.autorabit.com/~/revisions/woSPqiPyMz4Dlkp8971h/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/oauth-authentication-failed) [Error message: Please check credentials for 'xxx' branch of 'abc' repository](https://knowledgebase.autorabit.com/~/revisions/rYz8WTsiX4uOj026xeRC/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/please-check-credentials-for-xxx-branch-of-abc-repository) [Error message: Pre-receive-hook declined](https://knowledgebase.autorabit.com/~/revisions/Xzn0zbN9NIm96AjmX6Bu/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/pre-receive-hook-declined) [Error message: Picklist not found](https://knowledgebase.autorabit.com/~/revisions/eVHiGs1GS5ibsZILu3Nf/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/picklist-not-found) [Error message: Refusing to update checked out branch: \[branch\_name\]](https://knowledgebase.autorabit.com/~/revisions/3V2gW4eCq06phfVxFPgc/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/refusing-to-update-checked-out-branch-branch_name) [Error message: RPC failed; result=XXX, HTTP code = XXX](https://knowledgebase.autorabit.com/~/revisions/pfTNbBNW4wCntdKKMoiW/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/rpc-failed-result-xxx-http-code-xxx) [Error message: REJECTED\_NONFASTFORWARD](https://knowledgebase.autorabit.com/~/revisions/7Zz9TodeIJRQNq5Pr8lx/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/rejected_nonfastforward) Error message: Schema is invalid for the file [Error: Unable to delete workspaces](https://knowledgebase.autorabit.com/~/revisions/qGbi2kzSAblsa7qu1e7D/product-guides/arm/troubleshoot/arm-faqs/common-errors-and-resolutions/unable-to-delete-workspaces)
Error message: Schema is invalid for the file Users may encounter this error when trying to perform a merge due to invalid characters like (>>>, <<<) symbols used in the file. To resolve, download the merge conflict files and validate the characters present in those XML files.
Error message: SCM Authentication Failed When a commit returns this error, it is either because: * Version control mapped to your Salesforce org user is incorrect. * Your user credentials are incorrectly configured in ARM. 1. Ensure your account is correctly mapped with the version control branch to reflect the commits under your name. 2. Verify your credentials in the **Admin > Credential Manager** section and authenticate the connection again.
Error message: src refspec [branch] does not match any This error occurs when you try to push a branch that doesn't exist locally or has a different name. Ensure that the branch exists and that you have the correct name.
Error message: TF402455: Pushes to this branch are not permitted; you must use a pull request to update this branch This error may be encountered while attempting to commit changes for the production organization to the GitHub master branch. This is expected. When the branch is set with the branch policy, you cannot push it directly and need to create a pull request to update it. Once you remove the branch policy, you should have the ability to push changes to the master branch. Please contact the GitHub Administrator to request push permissions.
Error message: The layout Must Contain an item for the required layout field: IsnonStandard Please refer to this article,
Error message: This test is already in the execution queue When generating a code coverage report for a registered Salesforce org, the test fails with this error if the Apex test execution takes a long time. Go to **TAF > Apex Test Execution** and clear all of the tests in the queue, then run the code coverage report through ARM again.
Error message: Tip of your current branch is behind. This error usually occurs when you try to push a commit to a target branch, but the `HEAD` has been updated by someone else after you started your merge. You need to fetch the latest changes from the remote repository using **git fetch** and then merge them into your local branch using **git merge** before attempting to push again. You **can’t re-push** because: * Your merge commit references an **older state** of the target branch. * Re-pushing would **skip** newer commits, which could cause lost work or conflicts. You need to **re-perform the merge** using the latest version of the target branch.
Error message: Unable to fetch Salesforce Org Users This error may be encountered when a user tries to access the Salesforce Org in the ARM Version Control, CI Jobs, Deployment, and SFDX Modules. This may occur due to an invalid username, password, or security token, if the user is locked out, or if the Salesforce API version is incorrectly configured. Upgrade the API source flow in your Salesforce org to the most recent version and maintain the same Salesforce version in ARM by going to **Admin > My Account > My Salesforce Settings** and updating the API version.
Error message: Uploaded file is not having Workflow Rules This occur may occur when environment provisioning jobs are failing due to using the wrong file format for the **package.xml** file. Upload the correct package.xml file during the creation of environment provisioning jobs.
Error message: Validation checking fails for your repository Users may encounter this error message when a Merge is failed. This occurs when repository credentials are expired or have been modified and not updated in ARM. 1. Navigate to **Admin > VC repos**, select your repository, and perform a test connection. Please verify your repository credentials are not expired or modified. 2. Re-run the CI job after you confirm that the repository connection is successful.
Error message: You are not authorized to push changes to the remote repository This error occurs during the branching baseline operation when version control credentials are insufficient for pushing changes to a branch. This indicates that you have read permissions but not write permissions. After updating your permissions, re-run a new branching baseline operation.
Error message: Your branch is ahead of [remote]/[branch] by X commits This error message indicates that your local branch has commits that haven't been pushed to the remote branch. To resolve this, you can either push your local commits using **git push** or discard your local commits using **git reset** or **git stash**.
Error message: Your connection is private If you are unable to connect to the ARM instance and get this error, it is due to cache and cookies in your system. To resolve this issue, follow the steps below. 1. On your computer, open **Chrome**. 2. At the top right, click **More**. 3. Click **More tools**. 4. Clear **browsing data**. 5. At the top, choose a **time range**. To delete everything, select **All time**. 6. Next to **Cookies and other site data** and **Cached images and files,** check the boxes. 7. Click **Clear data**. 8. Now, log in to your instances using the new browser tab.