Explanation: | The authentication failed for the specified user. |
User Response: | Resolve the issue using the details provided in the error message. |
Explanation: | A user attempted to run a command that accesses the object specified. The command could not be executed because the command line program cannot access the object. |
User Response: | Verify that the user specified in the command has permission on the object. |
Explanation: | Validation failed for an SAP BW Service because no Integration Service references were found. |
User Response: | Configure the Integration Service for the SAP BW Service. |
Explanation: | The Repository Service encountered an error connecting to the repository. |
User Response: | Correct the error indicated in the message. |
Explanation: | The system was unable to locate the domains.infa file required to communicate with the domain. |
User Response: | Internal error. Attempt to start Informatica Services again. If the problem persists, contact Informatica Global Customer Support. |
Explanation: | The command requires that the domain name or host name and port number be entered as a command option. No domain name or host and port number was entered. |
User Response: | Enter the domain name or host name and port number as a command option. |
Explanation: | The PowerCenter Client did not receive a response from a service at the URL. |
User Response: | Correct the error indicated in the message. |
Explanation: | The Service Manager attempted an operation. However, the operation failed because of an error. |
User Response: | Correct the error indicated in the message and retry the operation. |
Explanation: | The domains.infa file is read-only, or there is not enough disk space available. |
User Response: | Make sure the domains.infa file is not read-only and that there is enough disk space available. |
Explanation: | The PowerCenter Client could not connect the domain within the resilience timeout period. |
User Response: | Verify that the domain is running and reconnect to the domain. If the domain is not running, ask the domain administrator to start PowerCenter Services. |
Explanation: | The Service Manager received a response with inconsistent message content. As a result, the operation failed. |
User Response: | Correct the error indicated in the message. |
Explanation: | The command line program was unable to find the domain specified in the command. |
User Response: | Verify that the domain exists and that the domain name was entered correctly. |
Explanation: | The Service Manager attempted an operation. However, the operation failed because of an error. |
User Response: | Correct the error indicated in the message and retry the operation. |
Explanation: | Validation for a linked domain failed as no gateways were specified. |
User Response: | Make sure you specify at least one gateway. |
Explanation: | A value length exceeds the maximum. |
User Response: | Shorten the value to be less than the maximum length. |
Explanation: | The Service Manager has inconsistent data. |
User Response: | Contact Informatica Global Customer Support. |
Explanation: | Internal Error. An unexpected token was encountered while reading an object. |
User Response: | If the problem persists, contact Informatica Global Customer Support. |
Explanation: | You tried to add an incremental key that has already been added. |
User Response: | To enable additional options, use a different incremental key. |
Explanation: | Each license requires one original key. You cannot apply more than one original key to the same license. You must use an incremental key to update an existing license. You use an original key to create a license. |
User Response: | Apply the incremental key to the existing license to update the license. Create a license using the original key. |
Explanation: | Each incremental key must be issued after the original key. |
User Response: | Contact Informatica Global Customer Support to get a valid incremental key. |
Explanation: | The license key file is unreadable. |
User Response: | Contact Informatica Global Customer Support to get a new license key file. |
Explanation: | The key provided was not validated as having proper encryption. |
User Response: | Contact Informatica Global Customer Support to get a new license key file. |
Explanation: | The license is invalid. The Begin Date attribute encountered in the license file is invalid. |
User Response: | Contact Informatica Global Customer Support to get a new license key file. |
Explanation: | The Expiry Date attribute in the license file is invalid. |
User Response: | Contact Informatica Global Customer Support to get a new license key file. |
Explanation: | The Issue Date attribute in the license file is invalid. |
User Response: | Contact Informatica Global Customer Support to get a new license key file. |
Explanation: | The CPUs attribute in the license file is invalid. |
User Response: | Contact Informatica Global Customer Support to get a new license key file. |
Explanation: | The Service Manager failed to validate the license because the number of repositories is invalid. |
User Response: | Contact Informatica Global Customer Support to get a new license key file. |
Explanation: | A client or service attempted to connect to the URL to perform an operation. However, the operation failed because the client or service could not connect to the URL within the resilience timeout. |
User Response: | Verify that the host name and port number for the URL and retry the operation. |
Explanation: | The PowerCenter component could not connect to the Service Manager on the gateway node to look up a service within the resilience timeout for the domain. |
User Response: | Verify that the gateway node is running. |
Explanation: | The service could not complete the operation. This error can occur because the Service Manager is in the process of shutting down. |
User Response: | Restart the node. |
Explanation: | The Log Manager cannot process log events because of the operating system error shown. For example, the shared file system may be unavailable. |
User Response: | Fix the errors listed in the node.log file. The node.log file is located in the server\tomcat\logs directory. |
Explanation: | Too many errors occurred while the Log Manager was processing log events. |
User Response: | Fix the errors listed in the node.log file. The node.log file is located in the server\tomcat\logs directory. |
Explanation: | An application service process could not create the Guaranteed Message Delivery file because of the operating system error shown. For example, the shared file system may be unavailable. |
User Response: | Try to fix the operating system error. |
Explanation: | An application service process could not write log events to the Guaranteed Message Delivery file because of the operating system error shown. For example, the shared file system may be unavailable. |
User Response: | Try to fix the operating system error. |
Explanation: | The incremental key has a different deployment type than the original key that was used to create the license. |
User Response: | Contact Informatica Global Customer Support to get a new incremental license key with the correct deployment type. |
Explanation: | The incremental key is for a different distributor than the original key that was used to create the license. The distributor is the organization that issued the PowerCenter product. |
User Response: | Contact Informatica Global Customer Support to get a new incremental license key with the correct distributor. |
Explanation: | The incremental key is for a different PowerCenter edition than the original key that was used to create the license. |
User Response: | Contact Informatica Global Customer Support to get a new incremental license key with the correct PowerCenter edition. |
Explanation: | The incremental key uses a different serial number than the original key that was used to create the license. |
User Response: | Contact Informatica Global Customer Support to get a new incremental license key with the correct serial number. |
Explanation: | The incremental key is for a different PowerCenter version than the original key that was used to create the license. |
User Response: | Contact Informatica Global Customer Support to get a new incremental license key with the correct PowerCenter version. |
Explanation: | You tried to create a license using an incremental key. |
User Response: | You must use an original key to create a license. |
Explanation: | The Service Manager encountered an error. |
User Response: | Check the additional error message for more information. |
Explanation: | The Upgrade Wizard encountered an error in a Repository Agent to PowerCenter Server configuration file and could not validate the file. |
User Response: | Correct the error indicated in the message and validate the file again. |
Explanation: | The Upgrade Wizard could not determine if the configuration file is a Repository Agent or PowerCenter Server configuration file. A Repository Agent configuration file must contain the <RepositoryName> property. A PowerCenter Server configuration file must contain the <ServerName> property. |
User Response: | Correct the contents of the configuration file and validate the file again. If you created the PowerCenter Server configuration file with the pmserverexportreg utility, the registry for the machine running the PowerCenter Server may contain inconsistent data. |
Explanation: | The Upgrade Wizard could not validate the Repository Agent or PowerCenter Server configuration file because the file is missing one or more of the required properties. |
User Response: | Add the required property or properties to the configuration file and validate the file again. |
Explanation: | You placed a file in the global_repo, local_repo, or PCServer directory in the server/upgrade/cfgfiles directory on a node. However, you can only upgrade Repository Agent or PowerCenter configuration files with the .cfg extension. The Upgrade Wizard cannot validate or upgrade the file. |
User Response: | If the file is a Repository Agent or PowerCenter Server configuration file, rename the file with the correct extension. If the file is not a configuration file, remove the file from the upgrade directory or ignore the error. |
Explanation: | The <RepositoryName> or <ServerName> property in the Repository Agent or PowerCenter Server configuration file matches a Repository Service or Integration Service name in the domain. As a result, the Upgrade Wizard cannot upgrade the configuration file. |
User Response: | If you already upgraded the Repository Agent or PowerCenter Server configuration file, ignore the error and do not upgrade the configuration file. If you want to upgrade the configuration file again, remove the service from the domain and upgrade the file again. |
Explanation: | You selected a node that contains Repository Agent and PowerCenter Server configuration files to upgrade in the Upgrade Wizard. However, the server/upgrade/cfgfiles directory does not exist on the node. The directory was removed after installation. |
User Response: | Create the directory and place Repository Agent and PowerCenter Server configuration files in the appropriate global_repo, local_repo, and PCServer directories under the server/upgrade/cfgfiles directory on the node, and then validate the files again. |
Explanation: | The value for the <RepositoryName> or <ServerName> property in the Repository Agent or PowerCenter Server configuration file matches the same property in another configuration file under the server/upgrade/cfgfiles directory on the node. All configuration files you want to upgrade must contain different values for the <RepositoryName> or <ServerName> properties. There may be duplicate configuration files in the upgrade directory. |
User Response: | Make sure the configuration file have unique values for the <RepositoryName> or <ServerName> properties and validate the files again. |
Explanation: | The PowerCenter Server configuration file contains an associated repository that does not have a corresponding Repository Service in the domain. The Upgrade Wizard requires information from the repository to upgrade the PowerCenter Server. As a result, the Upgrade Wizard cannot upgrade the Powercenter Server. |
User Response: | Upgrade the Repository Agent for the associated repository before you upgrade the PowerCenter Server. |
Explanation: | The PowerCenter Server configuration file contains an associated repository that does not have a corresponding Repository Service in the domain or in any of the Repository Agent configuration files you want to upgrade. The Upgrade Wizard will not be able to upgrade the PowerCenter configuration file without an upgraded Repository Service for the associated repository. |
User Response: | Make sure the domain has an upgraded Repository Service for the associated repository or that the upgrade directory has a Repository Agent configuration file for the associated repository. Otherwise, remove the PowerCenter Server configuration file from the upgrade directory. |
Explanation: | PowerCenter could not create the object because of the database error shown. |
User Response: | Correct the database error. |
Explanation: | The infasetup DefineDomain command was used to create a domain on IBM DB2 and the primary tablespace default page size is too small. |
User Response: | If the domain configuration database type is IBM DB2, make sure that the primary tablespace default page size is at least 16K. |
Explanation: | The Upgrade Wizard cannot decrypt the encrypted password in the Repository Agent or PowerCenter Server configuration file. |
User Response: | Use pmpasswd in the previous version of PowerCenter to encrypt the password. Correct the password in the configuration file, revalidate the configuration file, and upgrade the Repository Agent or PowerCenter Server configuration file again. |
Explanation: | The Repository Agent configuration file is not in the correct directory. |
User Response: | Move the Repository Agent configuration file to the global_repo or local_repo directory. |
Explanation: | A property or properties in a Repository Agent or PowerCenter Server configuration files does not have a corresponding value. |
User Response: | Add a value for the property in the configuration file and validate and upgrade the configuration file again. |
Explanation: | The Repository Agent or PowerCenter Server configuration contains an error and the Upgrade Wizard cannot upgrade the configuration file. |
User Response: | Correct the error indicated in the message and validate and upgrade the configuration file again. |
Explanation: | The permissions of the shared disk was not validated. |
User Response: | Verify the path and directory. The user that starts Informatica Services on the node must have permissions to write to the directory. |
Explanation: | The shared directory cannot be created because it is not valid or user does not have permission. |
User Response: | Verify the path and directory. The user that starts Informatica Services on the node must have permissions to write to the directory. |
Explanation: | The Repository Agent or PowerCenter Server configuration file contains a property without an associated value at a specific line number. |
User Response: | Correct the value for the property at the line number in the configuration file and validate and upgrade the Repository Agent or PowerCenter Server configuration file again. |
Explanation: | The PowerCenter Server configuration file is not in the correct directory. |
User Response: | Move the PowerCenter Server configuration file to the PCServer directory. |
Explanation: | The <RepositoryName> property in the Repository Agent contains a tab character, a trailing space, or one of the following characters: ? " : < > * / \ | . |
User Response: | Back up the repository, restore it using a name that does not contain these characters, and the upgrade the Repository Agent configuration file again. |
Explanation: | In a Repository Agent or PowerCenter Server configuration file, the end block comment string ‘*/’ occurs in the middle of a line, but can only appear at the end of a line. |
User Response: | Correct the configuration file and place the end comment string at the end of the line. Then validate and upgrade the configuration file again. |
Explanation: | You started a comment block that was not ended in a Repository Agent or PowerCenter Server configuration file. |
User Response: | Correct the configuration file and place the end comment string in the file. Then validate and upgrade the configuration file again. |
Explanation: | In the Upgrade Wizard, you chose a Repository Agent configuration file, but selected a PowerCenter Server file type. |
User Response: | Choose a PowerCenter Server configuration file or change the file type. |
Explanation: | In the Upgrade Wizard, you chose a PowerCenter Server configuration file, but selected a Repository Agent file type. |
User Response: | Choose a Repository Agent configuration file or change the file type. |
Explanation: | The PowerCenter Server is not registered to the associated repository in the PowerCenter Server configuration file. |
User Response: | Register the PowerCenter Server to the associated repository in the previous version of PowerCenter. Move the configuration file to the server/upgrade/cfgfiles/PCServer directory on the node and validate and upgrade the PowerCenter Server again. |
Explanation: | Option contains an invalid value. |
User Response: | Use the default value. |
Explanation: | A number option contained invalid numeric format. |
User Response: | Use the default value. |
Explanation: | Domain metadata is invalid with missing required option. |
User Response: | Back up the domain, correct the backup XML file, and restore the domain. |
Explanation: | Domain metadata is invalid with duplicate option. |
User Response: | Back up the domain, correct the backup XML file, and restore the domain. |
Explanation: | Domain metadata is invalid with an unknown option. |
User Response: | Back up the domain, correct the backup XML file, and restore the domain. |
Explanation: | Domain metadata is invalid with wrong option group name. |
User Response: | Back up the domain, correct the backup XML file, and restore the domain. |
Explanation: | Domain metadata is invalid with empty option. |
User Response: | Back up the domain, correct the backup XML file, and restore the domain. |
Explanation: | Domain metadata is invalid with invalid email address. |
User Response: | Back up the domain, correct the backup XML file, and restore the domain. |
Explanation: | An unknown value was encountered in an object. |
User Response: | If the problem persists, contact Informatica Global Customer Support. |
Explanation: | Loading the list of codepages failed when fetching from locale manager. |
User Response: | If the problem persists, contact Informatica Global Customer Support |
Explanation: | A value contains invalid spaces. |
User Response: | Remove all spaces from the value. |
Explanation: | Attempting to communicate with a linked domain not in domain metadata. |
User Response: | Add appropriate linked domain then try again. |
Explanation: | Database connection could not delete the domain. |
User Response: | Make sure the database is running. |
Explanation: | The node is starting on an unsupported platform. |
User Response: | Run PowerCenter only on supported platforms. |
Explanation: | A minimum option value is greater than a maximum option value. |
User Response: | Make sure the minimum value is less than or equal to the maximum. |
Explanation: | A number option contained invalid memory size format. |
User Response: | Enter a valid memory size format. |
Explanation: | You specified both database service name and database connection string. |
User Response: | Use the -DatabaseServiceName or -DatabaseConnectionString option, not both. |
Explanation: | You specified both database service name and database connection string. |
User Response: | Use the -DatabaseServiceName or -DatabaseConnectionString option, not both. |
Explanation: | You specified both database service name and database connection string. |
User Response: | Use the -DatabaseServiceName or -DatabaseConnectionString option, not both. |
Explanation: | The $WorkflowLogDir and $PMStorageDir do not have absolute paths defined in the Integration Service Process properties. |
User Response: | Define absolute paths for $WorkflowLogDir and $PMStorageDir in the Integration Service Process properties before you use operating system profiles. |
Explanation: | Integration Services can use operating system profiles on UNIX nodes. The Integration Service cannot use operating system profiles on Windows nodes. |
User Response: | Enable operating system profiles for an Integration Service that runs on UNIX nodes. Disable operating system profiles for the Integration Service. |
Explanation: | The database type you specified does not support tablespaces. |
User Response: | Omit the -tablespace option from the command. |
Explanation: | The Service Manager cannot read the values for the PowerCenter installation directory and PowerCenter version in nodemeta.xml. As a result, the Service Manager could not start the node. This error occurs when nodemeta.xml contains inconsistent data. |
User Response: | Back up the domain metadata in the domain configuration database, use infasetup to redefine the node, and restart the node. |
Explanation: | nodemeta.xml for the node does not contain values for the PowerCenter installation directory or PowerCenter version. As a result, the Service Manager could not start the node. This error can occur if you edit nodemeta.xml and do not specify the correct values for the PowerCenter installation directory or PowerCenter version. |
User Response: | Back up the domain metadata in the domain configuration database, use infasetup to redefine the node, and restart the node. |
Explanation: | You cannot run the application service on the node because the version of PowerCenter required to run the service is not installed on the node. In a mixed-version domain, the PowerCenter version for the service must be installed on the node where you want to run the service. |
User Response: | Change the node assignment for the service to a node that contains the required version of PowerCenter. |
Explanation: | You cannot create the service because the current domain does not contain the version of PowerCenter you want to create the service for. |
User Response: | Create an application service of a service version that is supported by the domain. |
Explanation: | You can use the environment variable INFA_DOMAINS_FILE to store the domains.infa path. You will receive an error if the environment variable INFA_DOMAINS_FILE is not set. |
User Response: | Add the environment variable INFA_DOMAINS_FILE, and set the path to the domains.infa file. By default, the domains.infa file resides in the infa_home directory. |
Explanation: | The request exceeded the timeout period due to an invalid connection or domain not running. |
User Response: | Ping the domain using infacmd ping and provide the gateway address. If the connection is invalid, infacmd ping adds or updates domains.infa file. If the domain is not running, ask the domain administrator to start Informatica Services. |
Explanation: | The HTTPS port number was used to connect to the PowerCenter domain from the PowerCenter Client. |
User Response: | Use the HTTP port number to connect to the PowerCenter domain from the PowerCenter Client. |
Explanation: | A PowerCenter component failed to understand the response from a PowerCenter service due to an error. |
User Response: | Correct the error indicated in the message. |
Explanation: | The command line programs require the domain name, which you provide as an option at the command prompt. If you incorrectly type this information, you will receive an error. |
User Response: | Verify that you typed the domain name at the command prompt correctly. Optionally, you can store the domain name as the environment variable INFA_DEFAULT_DOMAIN. If you have more than one domain, choose a default domain. |
Explanation: | The domains.infa file does not contain the information necessary to connect to the domain or the domains.infa does not exist. |
User Response: | Ping the domain using infacmd ping and provide the gateway address. If the connection is invalid, infacmd ping adds or updates domains.infa. If the domain is not running, ask the domain administrator to start Informatica Services. If you attempted to connect to a repository with the PowerCenter Client, remove the repository in the Navigator and add the repository again. |
Explanation: | The Service Manager on the gateway is not running, and cannot accept the request. |
User Response: | Use the infacmd ping to verify that the domain is running and the connection parameters are configured correctly. If the domain is running, infacmd displays the host name and port number of the domain. If the domain is stopped or unavailable, ask the domain administrator to start Informatica Services. Contact Informatica Global Customer Support if the domain is running and you continue to receive an error. |
Explanation: | The request exceeded the timeout period due to an invalid connection or domain not running. |
User Response: | Ping the domain using infacmd ping and provide the gateway address. If the connection is invalid, infacmd ping adds or updates domains.infa file. If the domain is not running, ask the domain administrator to start Informatica Services. |
Explanation: | The HTTPS port number was used to connect to the PowerCenter domain from the PowerCenter Client. |
User Response: | Use the HTTP port number to connect to the PowerCenter domain from the PowerCenter Client. |
Explanation: | You specified the incorrect domain name, gateway host name, or port number from a PowerCenter client application, such as pmcmd or the Designer. |
User Response: | Verify that you use the correct gateway information. If the gateway information is correct, and you continue to receive this error, contact Informatica Global Customer Support. |
Explanation: | The Domain Service could not parse the SOAP message received from a remote client, such as an FTP server. |
User Response: | Review the log for related messages to find out more information. Contact Informatica Global Customer Support. |
Explanation: | The domains.infa file is read-only, or there is not enough disk space available. |
User Response: | Make sure the domains.infa file is not read-only and that there is enough disk space available. |
Explanation: | A client or service attempted to connect to the URL to perform an operation. However, the operation failed because the client or service could not connect to the URL within the resilience timeout. |
User Response: | Verify that the host name and port number for the URL and retry the operation. |
Explanation: | The PowerCenter component could not connect to the Service Manager on the gateway node to look up a service within the resilience timeout for the domain. |
User Response: | Verify that the gateway node is running. |
Explanation: | Internal Error. An unexpected token was encountered while reading an object. |
User Response: | If the problem persists, contact Informatica Global Customer Support. |