Assertion failed: The installer is started with enabled database environment variables in SWPM

Estimated read time 4 min read

Hi Folks,

I would like to share a knowledge base article regarding the issues while performing Classical Migration using Export/Import method and SWPM tool.

Scenario:

We have an ABAP system for which we have taken export using SWPM on source server and here we are doing an SAP system installation while importing the exported data using SWPM tool (Installation + Migration), it throws below error while import.

Assertion failed: The installer is started with enabled database environment variables, which is not supported

Environment: Windows server 2019

Cause:

This issue occurred because there was already a System on target host with the same SID which was not properly uninstalled and cleaned up, so there were few Sybase database environment variables remained in the target host Registry Editor(regedit) in windows server which was not properly cleaned up during uninstallation.

Solution:

There are two ways in which this issue can be resolved.

The OS level user from which you are running SWPM, if it contains that environment variables and regedit (Registry) entries of old system SID, running SWPM with another user having same privileges fixes the issue.Remove the environment variables and entries of Old SID from regedit and restart SWPM and try again.

Additional Information:

You might come across a situation where your target system is corrupted, or system failure happens and you may loss the important encrypted data which is copied from source.  

While importing the data, SWPM provides you key id and key value which you need to take a note of and keep it in a safer place.

The secure storage will be encrypted with the following key:

 Key ID:

YYYYMMDD_HHMMSS_<SID>_INSTALLER

 Key Value:

***********************************************

Make a backup of above Key ID and 58-character Key Value and keep it in a secure place for disaster recovery.

When you are in the process of system installation and want to use this system as source for a system copy or system rename, you must provide this backup to restore access to the encrypted data in the copied system.

Thanks & Regards,

Tanmay Gupta

SAP

 

 

​ Hi Folks,I would like to share a knowledge base article regarding the issues while performing Classical Migration using Export/Import method and SWPM tool.Scenario:We have an ABAP system for which we have taken export using SWPM on source server and here we are doing an SAP system installation while importing the exported data using SWPM tool (Installation + Migration), it throws below error while import.Assertion failed: The installer is started with enabled database environment variables, which is not supportedEnvironment: Windows server 2019Cause:This issue occurred because there was already a System on target host with the same SID which was not properly uninstalled and cleaned up, so there were few Sybase database environment variables remained in the target host Registry Editor(regedit) in windows server which was not properly cleaned up during uninstallation.Solution:There are two ways in which this issue can be resolved.The OS level user from which you are running SWPM, if it contains that environment variables and regedit (Registry) entries of old system SID, running SWPM with another user having same privileges fixes the issue.Remove the environment variables and entries of Old SID from regedit and restart SWPM and try again.Additional Information:You might come across a situation where your target system is corrupted, or system failure happens and you may loss the important encrypted data which is copied from source.  While importing the data, SWPM provides you key id and key value which you need to take a note of and keep it in a safer place.The secure storage will be encrypted with the following key: Key ID:YYYYMMDD_HHMMSS_<SID>_INSTALLER Key Value:***********************************************Make a backup of above Key ID and 58-character Key Value and keep it in a secure place for disaster recovery.When you are in the process of system installation and want to use this system as source for a system copy or system rename, you must provide this backup to restore access to the encrypted data in the copied system.Thanks & Regards,Tanmay GuptaSAP    Read More Technology Blog Posts by SAP articles 

#SAP

#SAPTechnologyblog

You May Also Like

More From Author