-
DarkLight
Error Message: "Unable to fetch Salesforce Org Users"
Error Information | Steps for Resolution |
---|---|
Descriptions: When I try to access the Salesforce Org in the ARM Version Control, CI Jobs, Deployment, and SFDX Modules, it fails and the error message "Unable to fetch Salesforce Org Users" appears. Causes:
| The following is some helpful information that will assist you in resolving the issues mentioned above:
|
Error Message: "Transformed test case failed to compile"
Error Information | Steps for Resolution |
---|---|
Descriptions: When I try to execute the test cases task in the ARM TAF Module, it fails. When running a test case, the error message "Transformed test case failed to compile" appears. Causes:
| The following is some helpful information that will assist you in resolving the issues mentioned above:
|
Error Message: "Job too long after 1 hour of analysis"
Error Information | Steps for Resolution |
---|---|
Descriptions: Why are my analysis status failing and I'm getting the error "Job too long after 1 hour of analysis" when using CodeScan as a code analysis tool? Causes: In CodeScan Cloud, the default setting for unit test timeouts is 1 hour (3600 seconds) for limited Metadata analysis. These timeouts might not be enough if your project has a lot of metadata. This is the reason behind the error message. | Increase the timeouts to avoid problems like these. To increase the timeouts, follow the procedures below:
Additional Info: For detailed information on how to change the timeouts, click HERE. |
Error Message: "Your connection is private"
Error Information | Steps for Resolution |
---|---|
Descriptions: Why I am unable to connect to the ARM instance and sometimes get an error “Your connection is private”? Causes: This is due to cache and cookies in your system. | Follow the steps below to remove the cache and cookies from your system.
|
Error Message: "Not authorized"
Error Information | Steps for Resolution |
---|---|
Descriptions: When I perform a merge, I get the following error: "Not authorized" Causes:
|
Additional Info: If the test connection for the mapped repository and branch fails, we recommend upgrading your password and altering the credential in the credential section, then retrying the connection. |
Error Message: "SCM Authentication Failed"
Error Information | Steps for Resolution |
---|---|
Descriptions: How do I fix a commit with an "SCM Authentication Failed" error? Causes:
|
|
Error Message: "You are not authorized to push changes to remote repository"
Error Information | Steps for Resolution |
---|---|
Descriptions: AutoRABIT throws the following error during the branching baseline operation: "You are not authorized to push changes to remote repository" Causes: Your version control credentials are insufficient for pushing changes to your branch. This indicates that you have read permission but not write permission. | Re-run a new branching baseline operation after updating your permissions |
Error Message: "This test is already in the execution queue."
Error Information | Steps for Resolution |
---|---|
Descriptions: When I try to generate a code coverage report for my registered Salesforce org, the test fails with the following error: "This test is already in the execution queue." Causes: This is most likely to happen if the apex test execution takes a lengthy period. | 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: "Invalid meta-xml name: lwc/xxx/xxx.css-meta.xml, should end with js-meta.xml"
Error Information | Steps for Resolution |
---|---|
Descriptions: The deployment is getting failed with the following error: "Invalid meta-xml name: lwc/xxx/xxx.css-meta.xml, should end with js-meta.xml" Causes: This error usually occurs due to behavior in the Salesforce CLI 7.83 version. When retrieving the lwc components, it retrieves .css-meta.xml rather than .js-meta.xml file which results in deployment to get failed. | Try renaming the .css-meta.xml file to .js-meta.xml and running the deployment again. |
Error Message: "cannot open git-upload-pack"
Error Information | Steps for Resolution |
---|---|
Descriptions: ARM throws the following error: "cannot open git-upload-pack", when trying to register the Bitbucket repository? Causes:
|
|
Error Message: "Authentication Failed"
Error Information | Steps for Resolution |
---|---|
Descriptions: When selecting an ALM on the EZ-Commit screen, ARM displays the error: "Authentication Failed" Causes:
|
|
Error Message: "OAuth Authentication Failed"
Error Information | Steps for Resolution |
---|---|
Descriptions: When I try to register a Salesforce environment in AutoRABIT, I get the error "OAuth Authentication Failed." Causes:This is due to the fact that while adding the Salesforce org to AutoRABIT, you did not use the My domain URL. |
|
Error Message: "Uploaded file is not having WorkflowRules"
Error Information | Steps for Resolution |
---|---|
Descriptions: My environment provisioning jobs are failing and throwing an error “Uploaded file is not having WorkflowRules.” Causes: If you are using the wrong file format for the package.xml file, then the above error occurs. |
|
Error Message: "Please check credentials for 'xxx' branch of 'abc' repository"
Error Information | Steps for Resolution |
---|---|
Descriptions: While trying to connect to the Bitbucket repo, the ARM application throws the error: Please check credentials for 'xxx' branch of 'abc' repository" Causes: This seems to issue with the user permissions. If you are using the wrong file format for the package.xml file, then the above error occurs. |
|
Error Code: "413"
Error Information | Steps for Resolution |
---|---|
Descriptions: I get a 413-status error in the browser console when I try to upload duplicate profile files that have been resolved after downloading from version control. Causes: When you try to download numerous files at one go, you'll see such an issue. |
|
Deployment Issues:
Error Information |
---|
If you are getting the below errors during the deployment in ARM, follow the respective Salesforce article to get resolve the issues:
|
Error Message: "Schema is invalid for the File.”
Error Information | Steps for Resolution |
---|---|
Descriptions: Merge is getting failed with the error message “Schema is invalid for the File.” Causes: This is due to invalid characters like (>>>, <<<) symbols used in the file. |
|
Error Message: "validation Checking failed Repository”
Error Information | Steps for Resolution |
---|---|
Descriptions: Merge is getting failed with the error message “Schema is invalid for the File.” Causes: Your repository credentials are expired or it has been modified and not updated in the ARM application |
|