Symptom
The system had already been previously renamed to a new SID and now it is renamed again, back to the first SID
During this second system rename operation using SWPM, the tool incorrectly prompts for the target system's Default profile directory instead of the source system´s default profile.
The error in sapinst_dev.log is similar to this:
TRACE XXXXXX (YYYYYYY) (startInstallation) [Installer Callback]
NW.fromProfilepath() done: <disk>:/usr/sap/<SID target>/SYS/profile doesn't exist. throwing
TRACE XXXXXX (YYYYYYY) (startInstallation) [Installer Callback]
NWException thrown: nw.invalidProfilePathNotExists:
Cannot determine SAP system ID from profile directory <disk>:/usr/sap/<SID target>/SYS/profile: directory does not exist.
Read more...
Environment
System rename of SAP NetWeaver based AS ABAP or AS Java system in all release version using SWPM Tool
Product
Keywords
swpm, system rename, default profile directory, directory structure, sapinst_dev.log, profile path error, rename operation, system id error. , KBA , BC-INS-SRN , System Rename Utility , BC-OP-NT , Windows , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview