R/3 System on Windows NT: Problem Analysis (SAP Library - Computing Center Management System (BC-CCM))

R/3 System on Windows NT: Problem Analysis

Use

If problems occur when the R/3 System is started or stopped, you have a number of analysis options.

Procedure

You can start the MMC and use the available features for system analysis to find out the problem. Alternatively, try the following:

Select Programs ® Administrative Tools (Common) ® Event Viewer to access the Windows NT event log. In the menu bar, select Log ® Application. You are shown a list of errors, warnings, and information generated by the application software. You can display detailed information by clicking on a particular log.

Check that the R/3 service ( SAP<SAPSID>_<Instance number> , e.g. SAPC11_00 ) was started.

To do this, go to the window Services (Control Panel ® Services) and check the status of the R/3 service. The service has been started if it has the Status Started. If this is not the case, select Start to start the service.

Check the start log in the MMC. To do this, select the instance involved and from the context menu choose Task ® View Developer Traces.

Check the error files stderr<n> ( n is the number of one of the programs in the Windows NT start profile: Start_Program_<0n>... ). You can find the files in USR\SAP\<SAPSID>\<Instance number>\work .

The files can also be accessed from the MMC. To do this, select the instance involved and from the context menu choose Task ® View Developer Traces.

Check the trace files of the individual R/3 processes:

dev_ms : Developer trace of message server

dev_disp : Developer trace of dispatcher

dev_w<m> ( m number of work process): Developer trace of work processes