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
Error message: Authentication Failed - ALM connectivity due to incorrect configuration
Error message: Cannot Open Git-Upload-Pack
Error message: Cannot find the declaration of element 'web:validateSalesforceOrgConnection'
Error message: Failed to initiate deployment. Unexpected end of JSON input.
Error message: Failed to push some refs to [remote]
Error message: GIT Push Result: RemoteRefUpdate
Error: 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
Error message: Invalid Schema during the Merge Prevalidation Process
Error message: Local and remote repositories are not on the same revision
Error message: Not Authorized (to Merge)
Error message: Not Available for deploy for this organization
Error message: OAuth Authentication Failed
Error message: Please check credentials for 'xxx' branch of 'abc' repository
Error message: Pre-receive-hook declined
Error message: Picklist not found
Error message: Refusing to update checked out branch: [branch_name]
Error message: RPC failed; result=XXX, HTTP code = XXX
Error message: REJECTED_NONFASTFORWARD
Error message: Schema is invalid for the file
Error message: SCM Authentication Failed
Error message: src refspec [branch] does not match any
Error message: This test is already in the execution queue
Error message: Tip of your current branch is behind
Error: Unable to delete workspaces
Error message: Unable to fetch Salesforce Org Users
Error message: Uploaded file is not having Workflow Rules
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.
Navigate to Admin > VC repos, select your repository, and perform a test connection. Please verify your repository credentials are not expired or modified.
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.
On your computer, open Chrome.
At the top right, click More.
Click More tools.
Clear browsing data.
At the top, choose a time range. To delete everything, select All time.
Next to Cookies and other site data and Cached images and files, check the boxes.
Click Clear data.
Now, log in to your instances using the new browser tab.
Last updated
Was this helpful?