How To Fix AQ990 - Internal error: System name cannot be identified

SAP Error Message - Details

• Message type: E = Error

• Message class: AQ - Message texts for SAP Query

• Message number: 990

• Message text: Internal error: System name cannot be identified

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message AQ990 - Internal error: System name cannot be identified ?

  The SAP error message AQ990 "Internal error: System name cannot be identified" typically indicates an issue with the system configuration or environment settings. This error can occur in various contexts, such as during the execution of certain transactions or when accessing specific functionalities within SAP.
  Causes:
  
  System Configuration Issues: The system name may not be properly configured in the SAP system settings.
  Network Issues: Problems with network connectivity or DNS resolution can prevent the system from identifying its name.
  Profile Parameters: Incorrect or missing profile parameters related to the system's identification can lead to this error.
  Transport Layer Issues: If there are issues with the transport layer or if the system is not properly registered in the transport directory, this error may occur.
  Database Connection Issues: Problems with the database connection can also lead to this error, especially if the database cannot be reached or identified.
  
  Solutions:
  
  
  Check System Configuration:
  
  Verify the system's configuration in transaction RZ10 or RZ11 to ensure that the system name is correctly set.
  Check the instance profile and ensure that the parameters related to the system name (like SAPSystem) are correctly defined.
  
  
  
  Network Configuration:
  
  Ensure that the network settings are correct and that the system can resolve its own hostname. You can check this by using commands like ping or nslookup from the command line.
  Check the /etc/hosts file (on Unix/Linux systems) or the DNS settings to ensure that the hostname is correctly mapped.
  
  
  
  Review Profile Parameters:
  
  Use transaction RZ10 to review and adjust the instance profile parameters. Look for parameters like rdisp/mshost and rdisp/msserv to ensure they are correctly set.
  
  
  
  Check Transport Directory:
  
  Ensure that the system is properly registered in the transport directory. You can check the transport directory settings in transaction STMS.
  
  
  
  Database Connection:
  
  Verify that the database is running and accessible. Check the database connection settings in the SAP system to ensure they are correct.
  
  
  
  SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error. There may be patches or updates that resolve known issues related to this error.
  
  
  
  System Restart:
  
  In some cases, a simple restart of the SAP system or the application server may resolve transient issues.
  
  
  
  Related Information:
  
  SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. Provide them with detailed logs and the context in which the error occurs.
  Logs: Check the system logs (transaction SM21) and developer traces (transaction ST22) for any additional error messages or clues that may help diagnose the issue.
  
  By following these steps, you should be able to identify and resolve the cause of the AQ990 error in your SAP system.