This section discusses how to troubleshoot any issue occurred during Identity Server Code Promotion.
Error message: Configuration Import Failed
While importing the configuration data, the Import Configuration wizard displays this message.
See the details of the failure Administration Console tomcat logs at the following location:
Linux: /opt/novell/nam/adminconsole/logs/catalina.out
Windows: \Program Files (x86)\Novell\Tomcat\logs\stdout.log
Windows: \Program Files (x86)\Novell\Tomcat\logs\stderr.log
Collect the error details and contact the Technical Support team.
To restore your system, go to the Dashboard and click the drop-down menu in the upper right corner > Code Promotion. You will find the backup file that was created as part of import. Download the file and then click Import Configuration on the same page. Re-import this backup configuration to restore to the previous configuration.
This section discusses how to troubleshoot any issue occurred during Access Gateway Code Promotion.
Error message: Configuration Import Failed
While importing the configuration data, the Import Configuration wizard displays this message.
See the details of the failure Administration Console tomcat logs at the following location:
Linux: /opt/novell/nam/adminconsole/logs/catalina.out
Windows: \Program Files (x86)\Novell\Tomcat\logs\stdout.log
Windows: \Program Files (x86)\Novell\Tomcat\logs\stderr.log
Collect the error details and contact the Technical Support team.
You can restore Access Gateway configuration by using the backup file if you have backed up the configuration by using the ambackup file.
Error message: Policy configuration locked by another user
If an administrator is making changes to policies and you try to import the configuration by using Code Promotion simultaneously, then import fails.
Ensure that while importing, no other administrator is making changes to configuration. If it is already locked, click Please unlock to override.
You also need to check which policy containers are locked and then unlock them from the Policy user interface.
Error message: Access Gateway configuration locked by another user
If an administrator is making changes to Access Gateway configuration and you try to import the configuration by using Code Promotion simultaneously, then import fails.
Ensure that while importing, no other administrator is making changes to configuration. If it is already locked, click Please unlock to override. Unlock Access Gateway cluster in Access Gateway user interface for which you are importing the configuration data.
Error message: Could not generate Access Gateway import overview
Ensure that you associate Access Gateway cluster with an Identity Server cluster before importing protected resources that have Identity Server dependencies such as contracts and custom attributes.
Error message: Proxy service name not unique
If the name of a proxy service is same on the source and target systems, but their type does not match, then the import does not happen. For example, a proxy service is Path Based Multi-Homing on the source setup and a proxy service with the same name is Domain Based Multi-Homing on the target system.
Update the type of the proxy service on the source setup or target setup and then import.
Error message: Invalid input
Type Mismatch Error: Cannot import policy <name of the policy> of container <name of the container>. The type of this policy is <type of policy> in the source setup and <type of policy> in the target setup.
If the name of a policy is same on the source and target systems, but their type does not match, then the import does not happen. For example, a policy is defined as authorization policy in the source setup and a policy with the same name is defined as identity injection in the target setup.
Update the type of the policy on the source setup or target setup and then import.
Error message: Invalid input
Cannot import the new virtual proxy service in (name of reverse proxy) > (name of proxy service) from source Access Gateway cluster <name of the cluster> because SSL is enabled in the reverse proxy <name of the reverse proxy on the target system> in the target Access Gateway cluster.
Import of virtual proxy services to a SSL enabled proxy service in the target system is not allowed.In such cases, ensure that you exclude virtual proxy services during import.
Error message: Domain-Based Multi-Homing requires the Published Domain Name of proxy service <name of the proxy service being imported> to be in the Cookie Domain of the first Proxy Service under Reverse Proxy
Master proxy service's cookie domain does not match with the imported Domain Based Proxy Service's DNS name.
Update the published DNS name for the specified proxy service while importing it.
Error message: Invalid input
Cannot import the SSL enable proxy service in (name of reverse proxy) > (name of proxy service) from the source Access Gateway cluster because SSL is not enabled in the reverse proxy in the target Access Gateway cluster
You cannot import SSL enabled proxy service to non SSL enabled reverse proxy. Before importing, enable SSL for the target reverse proxy or disable SSL for source proxy service.
Error message: Invalid input
Cannot import master proxy service from the source Access Gateway cluster as another master proxy service with a different name already exists in the target Access Gateway cluster.
Name of the master proxy service must be same on the source and target systems. Update the name on the source or target setup before importing it.
Error message: Invalid input
Reverse Proxy does not exist in the target Access Gateway cluster
For importing a proxy service or protected resource, if the corresponding reverse proxy or master proxy service does not exist, then you must create reverse proxy and master proxy service on the target system before starting the Code Promotion import.
Error message: Invalid input
Proxy Service does not exist in the target Access Gateway cluster
Importing only selected protected resources for a domain-based proxy service that does not exist in the target setup fails. You must also import the related domain-based proxy service in such cases.
Error message: Published DNS Name is not unique under Reverse Proxy in the target setup.
DNS name must be unique under a reverse proxy. Specify a unique name in the Published DNS Name field for the proxy service during import.
In case of any error during the import process, system tries to revert to the previous configuration. If any error occurs during this revert process, then Code Promotion displays a message specifying the component for which the revert process failed. Components include Access Gateway configuration and dependent policies and policy extensions. In this case, you need to restore the pre-import configuration manually by using ambackup. You should take a backup by using the ambackup file before importing the configuration data.
This section discusses how to troubleshoot any issue occurred during device customization Code Promotion.
Ensure that the custom files are available in the source setup and paths are correct.
Verify the following Administration Console log file of the source setup after export. This log file contains information about files that are not exported.
Linux: /opt/novell/nam/adminconsole/logs/catalina.out
Windows: \Program Files (x86)\Novell\Tomcat\logs\stdout.log