All available columns have been added to this index.
Cause:
You tried to add a column to an index when columns are no longer available.
Action:
No action.
Cannot connect to the SPI server, host = <host name>, port = <port number>, error = <error code>.
Cause:
The SPI Server TCP/IP port is not accessible.
Action:
Check the Communication component and network configuration. Verify that the SPI Server is running.
Cannot create field <field name>.
Cause:
When you are not able to define the field in the repository.
Action:
Check for related messages.
Cannot create table <table name>.
Cause:
When you are not able to define the table in the repository.
Action:
Check for related messages.
Cannot initialize Windows Sockets.
Cause:
When you do not configure the Windows network environment.
Action:
Contact the Windows system administrator.
Failed to access config file data, wrong file format.
Cause:
The configuration file is accessible, but the content is not valid.
Action:
Check the configuration file.
Failed to add menu item <item name>.
Cause:
Internal error.
Action:
Contact Informatica Global Customer Support.
Failed to close the session.
Cause:
Internal error.
Action:
Check the environment for a temporary network or operating system failure.
Failed to launch SAS data viewer, error code = <error code>.
Cause:
.NET run time might not be available on your system.
Action:
Install Microsoft .NET runtime environment.
Failed to load config file: <file name>, the file does not exist or it is not valid config file.
Cause:
The configuration file is not accessible.
Action:
Make sure the configuration file exists and is accessible.
Failed to load index information from metadata.
Cause:
An internal error occurred while retrieving index information.
Action:
Contact Informatica Global Customer Support.
Failed to open the help file: <file name>.
Cause:
Help file could not be found or could not be opened.
Action:
Check the client installation.
Failed to retrieve metadata, error code = <error code>.
Cause:
SAS does not start.
Action:
Check the SAS environment. Try to start SAS manually, and check the error messages from SAS.
Failed to retrieve SAS session log, error code = <error code>.
Cause:
When you are not able to retrieve the SAS log file from the SAS machine.
Action:
Check the SPI Server log file for more information.
Failed to retrieve session ID.
Cause:
Internal error.
Action:
Contact Informatica Global Customer Support.
Failed to retrieve the registry key: <key name>.
Cause:
When the installation of PowerCenter do not performed properly.
Action:
Perform the installation of the PowerCenter Client.
Failed to save config file: <file name>.
Cause:
When you are not able to save the configuration file.
Action:
Check the file system.
Index name cannot be empty.
Cause:
You tried to define an index without giving it a name.
Action:
Supply a name for the index.
Library information is not available.
Cause:
The SAS session did not return the expected metadata.
Action:
Check the SAS log for error conditions.
No information available about table <table name>.
Cause:
The SAS session did not return the expected metadata.
Action:
Check the SAS log for error conditions.
No selection has been made.
Cause:
You tried to edit a field attribute before selecting an attribute.
Action:
Make a selection before attempting the edit.
Nothing has been selected for import.
Cause:
When you do not select any items in the table tree.
Action:
Select an item.
Received data has not valid format or the imported table/view has no columns.
Cause:
This must not occur in normal situations.
Action:
Check the SAS environment and the assigned library or table for abnormal conditions.
SAS data viewer requires .NET runtime. It appears that .NET runtime is not installed on this system, continue anyway?
Cause:
.NET runtime might not be available on your system.
Action:
Install Microsoft .NET runtime environment.
Session open request failed, host = <host name>, port = <port number>, error = <error code>.
Cause:
SPI Server cannot initialize a session.
Action:
Check the SPI Server log for more information.
SPI server login failed because of wrong user name or password.
Cause:
Authentication to SPI Server failed.
Action:
Use the correct credentials to connect to SPI Server.
The metadata field <field name> does not correspond to any table field.
Cause:
An internal error occurred while retrieving index information.
Action:
Contact Informatica Global Customer Support.
The specified length of a numeric field is out of range (a valid value for SAS must be in the range from <value> to <value>). It will be set to the default value.
Cause:
The field length is not valid.
Action:
Enter a valid length or accept the default value.
Version mismatch is detected. The client version is not compatible with a server you are trying to connect to.
Cause:
The Client component of PowerExchange for SAS is not of the same version as the Communication component.
Action:
Make sure you install both components from the same version.