Contents x
Common Issues and Solutions
  • 07 Oct 2022
  • 7 Minutes to read
  • Contributors
  • Dark
    Light
Contents

Common Issues and Solutions

  • Updated on 07 Oct 2022
  • 7 Minutes to read
  • Contributors
  • Dark
    Light

Error Message: "Unable to fetch Salesforce Org Users"

Error InformationSteps 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:
  1. INVALID LOGIN: Invalid username, password, security token; or user locked out.
  2. Salesforce API Version is wrongly configured.

The following is some helpful information that will assist you in resolving the issues mentioned above:

  1. Upgrade the API source flow in your Salesforce org to the most recent version and maintain the same Salesforce version in ARM. 
  2. To do so, go to Admin > My Account > My Salesforce Settings and update the API version.


Error Message: "Transformed test case failed to compile"

Error InformationSteps 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:
  1. XPath values in the test file were incorrect
  2. The test case failed right after login into Salesforce.

The following is some helpful information that will assist you in resolving the issues mentioned above:

  1. Replace the XPath values in the test file and run it again; it should now function. 
  2. Right after entering into Salesforce, add the wait seconds.


Error Message: "Job too long after 1 hour of analysis"

Error InformationSteps 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: 

  1. Click Project Settings > General Settings in your Project Overview. 
  2. Click the CodeScan tab on the left and modify the timeout under the Unit Test Timeout once you're in General Settings.

Additional Info:

For detailed information on how to change the timeouts, click HERE.


Error Message: "Your connection is private"

Error InformationSteps 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. 
  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.


Error Message: "Not authorized"

Error InformationSteps for Resolution
Descriptions:
When I perform a merge, I get the following error: "Not authorized"

Causes:
  1. You are experiencing this issue because your credentials were not properly mapped in the ARM application.
  1. In Azure, create a new token.
  2. In ARM, go to Admin > Credential and create a new credential.
  3. Re-test the connection after mapping the credential to your version control branch (in the Profile section). 

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 InformationSteps for Resolution
Descriptions:
How do I fix a commit with an "SCM Authentication Failed" error?

Causes:
  1. Version control mapped to your Salesforce org user is incorrect.
  2. Your user credentials are wrongly configured in the ARM application.
  1. Make sure your account is correctly mapped with the version control branch in order to reflect the commits under your name.
  2. Verify your credentials in the Admin > Credential Manager section and authenticate the connection again.


Error Message: "You are not authorized to push changes to remote repository"

Error InformationSteps 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 InformationSteps 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 InformationSteps 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 InformationSteps for Resolution
Descriptions:
ARM throws the following error: "cannot open git-upload-pack", when trying to register the Bitbucket repository?

Causes:
  1. Your Bitbucket account is locked.
  2. When registering the Bitbucket repository, you used the wrong credentials.
  3. It is also possible that your IT/Network team has whitelisted ARM's IP address. 
  1. Try recreating a new credential, and updating the credentials under the Admin > Credential section.  
  2. Re-register your bitbucket repository once again in ARM. (LEARN MORE).


Error Message: "Authentication Failed"

Error InformationSteps for Resolution
Descriptions:
When selecting an ALM on the EZ-Commit screen, ARM displays the error: "Authentication Failed"

Causes:
  1. VPN connectivity appears to be the source of intermittent ALM connectivity issues.
  2. ALM is wrongly configured
  1. On the My Account screen, look for the ALM configuration. To reauthenticate your ALM configuration, click the Test Connection icon to verify your credentials.
  2. If the steps above do not work, create a new credential and link it to your ALM account.


Error Message: "OAuth Authentication Failed"

Error InformationSteps 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. 

  1. Use My Domain URL while registering a Salesforce org inside AutoRABIT.


Error Message: "Uploaded file is not having WorkflowRules"

Error InformationSteps 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.
  1. Upload the correct package.xml file during the creation of environment provisioning jobs.


Error Message: "Please check credentials for 'xxx' branch of 'abc' repository"

Error InformationSteps 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.
  1. Check the permissions you have on your Bitbucket repository with the repository owner/administrator.
  2. Request the permissions that the other users have if you don't have enough permission.


Error Code: "413"

Error InformationSteps 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.
  1. If you download one profile file at a time, you should be able to do it without a problem.


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 InformationSteps 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.
  1. Download the merge conflict files and validate the characters present in those XML files.


Error Message: "validation Checking failed Repository”

Error InformationSteps 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
  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.


Was this article helpful?
Copyright © 2023 AutoRABIT Holding Inc. All Rights Reserved.

The information herein is the property of AutoRABIT Holdings Inc., and any misuse or abuse will result in economic loss. All product and company names mentioned herein may be trademarks or registered trademarks of AutoRABIT Holdings Inc. or their respective owners.

Cookie consent

We use our own and third-party cookies to understand how you interact with our knowledge base. This helps us show you more relevant content and ads based on your browsing and navigation history.