Using the Promotion Tools

Troubleshooting the Promotion Tools

The following error messages might appear when you run the Export SAS Package wizard, the Import SAS Package wizard, or the batch import or export tool:

Out of memory error occurred during the import (or export) process.

This error could occur if you export or import a large number of sizable objects, such as information maps or SAS Data Integration Studio jobs. If this error occurs, you can take either of the following actions:

Instead of exporting all of your objects at the same time, perform multiple exports that include a smaller number of objects.
Increase the amount of memory that is allocated to the import or export process. For instructions, see Ensure Adequate Memory.

Duplicate named objects were found within the same folder. These objects will not be exported. View the Details to see the list of objects.

This error could occur in these circumstances:

You use the Include all dependencies option in the Export SAS Package wizard or the -includeDep option with the export batch tool.
The export includes two or more objects that depend on different objects that have the same name and type. For example:
- In the Export SAS Package wizard, you select two information maps: Map A and Map B.
- You select the Include all dependencies option.
- Map A depends on a table called PRODUCT-DIM that is located in /Shared Data/Orion Star Data, and Map B depends on a different table called PRODUCT-DIM that is located in /Shared Data/Company Data.

To resolve the error, export the objects' folders along with the objects, as follows:

If you are using the Export SAS Package wizard:
1. Go back to the previous wizard page.
2. Select a folder that contains both the parent objects and the dependent objects. In the preceding example, you would select the Shared Data folder.
3. Within the folder structure, deselect any objects and folders that you do not want to export. However, make sure that the dependent objects that have duplicate names (for example, the two different PRODUCT-DIM tables) remain selected, as well as the folders that make up these objects' paths.
If you are using the batch export tool, modify the -objects option so that it specifies the dependent objects that have duplicate names (for example, the two different PRODUCT-DIM tables) and their paths.

The export process has failed. No X11 DISPLAY variable was set, but this program performed an operation which requires it. For more information, view the export log file: filename

This error could occur if you submit a batch import or export job on a UNIX machine for which the DISPLAY variable has not been set. To resolve the error, set the DISPLAY variable by entering a command such as the following:

export DISPLAY=machine-name

No extraField1 found.

This error can occur if you try to import a package file whose contents were updated after the package was created. For example, if you open a package file, save any of the files in the package (for example, the export log), and then save the package file, then the package becomes corrupted and cannot be imported.

To resolve the error, perform the export again to re-create the package.

The following resources could not be found in the package file or on the target server. Objects dependent on these resources may not function properly after the import process.

This message means that the objects that you are importing depend on objects that are not present on the target metadata server.

You will need to import the resources that objects depend on, unless those resources already exist in the target environment. For example, in order for a report to function properly, you must import the information map that the report depends on, as well as any stored processes that are associated with the report.

Destination folder has invalid or missing content mapping; cannot import reports.

If this message appears when you try to run the Import SAS Package wizard, click OK to close the message box and click Cancel to stop the import process.

Specify content mapping on the target metadata server (see For Reports, Set Up Content Mapping on the Target Metadata Server), and start the import again.

Could not import "filename.sas" in "path" on application server "server name". Reason: Insufficient authorization to access path.

This message appears in the error log at the end of the import process. It means that the user who ran the import does not have Write permission for the specified directory in the file system of the target machine. Grant the user Write permission to the directory, and run the import again.

Libname library name is not assigned.

This message could appear in the error log if you try to export physical tables along with DBMS table objects while you are logged on as an unrestricted user. Unrestricted users (for example, sasadm) cannot access the servers that are necessary to export physical DBMS tables. Log on as a different user, and start the export process again.

Top of Page