How To Fix SYCM_APS172 - Could not update project. Old configurations restored

SAP Error Message - Details

• Message type: E = Error

• Message class: SYCM_APS - Custom Code Management App texts

• Message number: 172

• Message text: Could not update project. Old configurations restored

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 SYCM_APS172 - Could not update project. Old configurations restored ?

  The SAP error message SYCM_APS172 indicates that there was an issue updating a project, and as a result, the system has restored the old configurations. This error typically occurs in the context of SAP Project Management or SAP Solution Manager when there are inconsistencies or issues during the project update process.
  Possible Causes:
  
  Configuration Issues: There may be inconsistencies in the project configuration that prevent the update from being applied successfully.
  Authorization Problems: The user attempting to perform the update may not have the necessary authorizations to make changes to the project.
  System Locking: Another user or process may have locked the project or certain objects within it, preventing the update.
  Data Integrity Issues: There may be issues with the underlying data that the project relies on, such as missing or corrupted entries.
  Transport Issues: If the project update involves transport requests, there may be issues with the transport itself, such as missing objects or dependencies.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to update the project. This can be done by reviewing the user's roles and permissions.
  Review Configuration: Check the project configuration for any inconsistencies or errors. This may involve reviewing the project settings and ensuring that all required fields are correctly filled out.
  Unlock Objects: If the project or its components are locked, identify the user or process that has locked them and resolve the locking issue.
  Data Validation: Validate the underlying data for the project to ensure that there are no missing or corrupted entries. This may involve running consistency checks or data validation reports.
  Check Transport Requests: If the update involves transport requests, ensure that all necessary objects are included and that there are no missing dependencies. You may need to re-import the transport request or create a new one.
  Consult Logs: Review the system logs (transaction SLG1) for more detailed error messages or warnings that may provide additional context for the failure.
  
  Related Information:
  
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Documentation: Review the official SAP documentation for Project Management or Solution Manager for best practices and troubleshooting guidelines.
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis or technical support team for further investigation.