Export Failure Due to Empty SQL Script - Applications Manager

Products

• Automic Applications Manager

Issue/Introduction

An export failure in Automic Applications Manager can lead to downstream issues, such as aborting migration chains. This article provides steps to resolve errors caused by empty configuration files in the SQL directory.

Symptoms

The following error or similar may appear in the export logs:

Creating export file

SSTRIP03 - Cannot open %AW_HOME%\export\####.exp for reading.
"no output from $module"
"N" was unexpected at this time.

Environment

Applications Manager

Cause

The error is typically caused by a required configuration file within the %AW_HOME%\sql\Export2.sql directory being empty (0 bytes). The system requires valid contents in these scripts to execute the export process correctly.

Resolution

To resolve this issue, compare the file sizes in your SQL directory against a known working environment.

1. Navigate to the SQL directory, typically located at: %AW_HOME%\sql.
2. Identify any files that are 0 bytes in size.
3. Compare the file names with the corresponding files in a working environment (e.g., a test or development instance).
4. Copy the contents of the file from the working environment to the affected server.
5. Restart the relevant services or retry the export job.

If needed, the scripts from the sql directory can be found in the installation media at the below file/zip structure:

Applications.Manager_AM.Full.Image_9_6_0+build.1734073930.zip\Applications.Manager_AM.Full.Image\V9\AWFILES.zip\sql\

Additional Information

To speak with a customer representative or a Support Engineer, see Contact Support. Scroll to the bottom of the page and click on your respective region.