Online Tutorials & Training Materials | STechies.com
Register Login

What to do if the System does not start, due to missing environment variable.

|| 0

What to do if the System does not start, due to missing environment variable.
Stechies

Situation of sapsweep or system stop

It is neither possible to restart the SAP Application Server nor to execute individual functions after the program sapsweep.exe was executed to delete the SAPGui installation.

sapsweep was executed with the default settings. At present, these settings also cause the Windows NT Registry key
HKEY_LOCAL_MACHINESoftwareSAP
including all sub-entries to be deleted. This also includes the information on the environment variable that needs to be set for all Apllication Servers that are installed on this host.

What to do if System stop

Do not use sapsweep.exe on servers, which have an SAP R/3 Application Server installed.
If you have to use sapsweep for some reason on such a server, you must not select the function
               Delete Registry Entries.

If you have already deleted the sapgui installation with sapsweep and if the function 'Delete Registry Entries' was active, proceed as follows:

Execute the following steps on each Application Server that was installed on the computer you want to repair:

R/3 Systems up to and including Release 4.0B:

Log on as <sid>adm user to the NT desktop that you usually use for system administration. This user should still have the correct environment. Start the program ntenv2reg.exe and select the corresponding instance for which you want to transfer the environment into the Registry. DO NOT start (!) ntreg2env.exe PRIOR TO executing ntenv2reg.exe.
You can use this procedure if you entered or changed the environment variables via Control Panel -> System and if you synchronized the SAP environment via the program ntenv2reg.exe. If you maintained the environment directly in the Registry (against our recommendation) and if you did not maintain or synchronize the user environment of the <SID>adm user in parallel, an automatic repair is not possible. In this case, open an OSS message so we can help you to re-configure your environment.

R/3 Systems as of and including Release 4.5B:

Log on as <sid>adm user to the NT desktop that you usually use for the R/3 System administration. First, determine the user environment you are using. To do this, open a command prompt and enter the following command:
  set U
As a result, you should at least obtain information on the environment variables USERNAME and USERDOMAIN.
Now, start the Registry Editor (regedit.exe) and first create the key HKEY_LOCAL_MACHINESoftwareSAP<SID> if it does not yet exist. Under the key HKEY_LOCAL_MACHINESoftwareSAP<SID> create a string value named AdmUser and the value <USERDOMAIN><USERNAME> (right-click on HKEY_LOCAL_MACHINESoftwareSAP<SID>, select New -> String Value. In the righthand dialog box right-click on 'New Value #1', select Rename and rename the value to AdmUser. Then right-click on 'AdmUser' and select Modify and set the value to <USERDOMAIN><USERNAME>.) For <USERDOMAIN> and <USERNAME> enter the values which were determined with 'set U'.
You can check the setup of the environment variable in the R/3 System as follows:
Start the SAP R/3 MMC console: Right-click on the host name of the Application Server 'All Tasks->View environment' and check the entries for the 'SAP Registry Environment' in the following dialog. These entries must be identical to the entries in Control Panel -> System-> User Environment Variables of the <sid>adm user.