Application Delivery Management

Troubleshooting

March 11, 2024

Contributed by:

R C

When you run the migration script for the first time, it checks for the prerequisites and proceeds with the migration. If all prerequisites are met, the migration completes without any errors. If any prerequisite fails, the script displays error messages with reasons. After fixing the errors, you must rerun the script again.

Note

If you see an error message that displays “already exists”, it means that:

You might have run the migration script for more than one time and some configurations are already migrated to ADM service.

You might have manually created the same configuration in ADM service, before running the migration script.

Refer to some of the following error messages:

Manual profile added to ADM service

Workaround: If you have created admin profiles in NetScaler ADM service before running the migration script, ensure to delete those profiles and rerun the migration script.

NetScaler device added to ADM service

Manual ADC device addition

Workaround: In on-premises ADM, ensure the instance status and see if you can access the instance without any issues. If any issue persists, fix the issue, and rerun the migration script.

StyleBook custom templates import to ADM service

Manual StyleBook addition

Workaround: This error message is an example for the already migrated StyleBook. You can also see this error if you have manually created a StyleBook with the same name, version, and namespace, in NetScaler ADM service before running the migration script.

Configuration Jobs added to ADM service

Configuration jobs manual addition

Workaround: This error occurs if you have subscribed to Express Account and have more than two configuration jobs. You must obtain a valid subscription to have all your configuration jobs to be migrated.

IP blocks added to ADM service

IP blocks manual addition

Workaround: Delete the IP block that is manually created in ADM service and rerun the migration script.

Network dashboard report addition status

Network dashboard manual addition

Workaround: Delete the dashboard that is manually created in ADM service and rerun the migration script.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Troubleshooting

March 11, 2024

Contributed by:

R C

March 11, 2024

Contributed by:

R C

Troubleshooting

Manual profile added to ADM service

NetScaler device added to ADM service

StyleBook custom templates import to ADM service

Configuration Jobs added to ADM service

IP blocks added to ADM service

Network dashboard report addition status

In this article