Show TOC Start of Content Area

Background documentation Further Documentation and Troubleshooting  Locate the document in its SAP Library structure

Use

This sections gives you information on the following:

·        Further documentation on the SAP MMC snap-in which is available on SAP Service Marketplace at:

service.sap.com/msplatforms Microsoft  Windows Server

·        Troubleshooting for common errors

Documentation

·        The SAP MMC snap-in uses the new Web service SAPControl interface or the old DCOM interface ISAPControl of the SAP start service sapstartsrv.exe.

SAP Note 142100 lists all known problems and solutions related to the start service.

·        The documentation SAP System Information in Directory Services on SAP Service Marketplace gives a detailed description of how SAP systems are automatically registered in LDAP directories like the directories like the Windows Active Directory.

SAP Note 379691 describes how to enable ITS registration in LDAP directories for SAP release 46B - 46D.

·        The documentation How to Use the ISAPControl Interface on SAP Service Marketplace describes how to use the ISAPControl DCOM interface in your own scripts and programs for system administration.

·        The documentation Configuring the SAP Web AS for Supporting SSL describes how to enable SSL support, which is also valid for the new Web service SAPControl Interface.

·        The documentation How to extend the SAP MMC Snap-In, which is available on SAP Service Marketplace, provides the necessary information for programmers to create extension snap-ins for the SAP MMC snap-in that can, for example, be similar to the various database extension snap-ins. 

Troubleshooting

SAP recommends to check SAP Note 142100 for potential problems first.

·        The most common problem is that the SAP MMC snap-in cannot connect to the Web service or  DCOM interface of the SAP instance. If the SAP MMC snap-in is used to monitor local SAP instances and Always show local SAP instances is enabled, the SAP system or instance may be missing in  the scope pane. If you are monitoring the SAP instances remotely, the affected instances are displayed with a defect icon.

To get a more detailed error description, choose View Start Profile from the instance context menu. If the instance is missing in the scope pane, you have to add it to the list of monitored instances first. The operation fails and displays one of the following error messages:

¡        "Profile parameter mismatch. SAPSYSTEMNAME or SAPSYSTEM doesn't match ...": 

The connect to the Web service or DCOM interface was successful, but the used SAP system name or system number used by the SAP MMC snap-in does not match the profile parameters of the connected SAP instance. Verify the snap-in parameters and the profile parameters of the connected SAP instance.

¡        "Class not registered" (0x80040154):

The connect to the old DCOM interface failed. The snap-in derives the class ID from the SAP system number. Use the Properties context menu for the instance node to verify that the snap-in uses the correct system number for the SAP instance. Also make sure that the service is correctly installed on the SAP instance. You can reinstall the service by starting sapstartsrv.exe from the executables directory of the SAP instance.

¡        "Error loading type library/DLL" (0x80029C4A):

The connect to the old DCOM interface failed. The snap-in requires the type library of the start service sapstartsrv.exe to be installed on the host running the snap-in. The type library is installed in the registry but cannot be loaded, probably because it has been deleted. If the snap-in is running on a host running one or more SAP instances, reinstall the start service. If the snap-in is running on a host without any local SAP instances, copy sapstartsrv.exe to %windir%\system32 and register the type library by running sapstartsrv.exe -t.

¡        "Interface not registered" (0x80040155):

The connect to the old DCOM interface failed. The type library of the start service sapstartsrv.exe is not registered on the host running the snap-in. If the snap-in is running on a host running one or more SAP instances, reinstall the start service. If the snap-in is running on a host without any local SAP instances, copy sapstartsrv.exe to %windir%\system32 and register the type library by running the command sapstartsrv.exe -t

¡        "Access is denied" (0x80070005):

The connect to the old DCOM interface failed. The user running the snap-in is not allowed to connect to the DCOM interface of the start service. The default DCOM configuration requires that the host running the SAP instance must be able to verify the user account running the SAP MMC snap-in. If your user account cannot be verified on the SAP instance (for example, because of a missing domain trust or using a local user account) you cannot use this account for the administration of the SAP instance. You can modify DCOM security settings on the SAP instance host by using dcomcnfg, but you have to be very careful with this expert user tool (for example, you should be very familiar with the DCOM security details).

Note

Moving registered files with the Windows Explorer is dangerous. The Windows Explorer notices that a file (for example, sapstartsrv.exe or sapmmc.dll) is registered in the registry and changes the path information in the registry if the file is moved. For example, if you move (or delete by moving to the recycler) sapstartsrv.exe with the Windows Explorer, DCOM will still use the moved file, even if you copy a new version of sapstartsrv.exe to the executables directory. Even worse, if you delete the moved file later, DCOM can no longer find the file. To overcome this problem you have to reinstall the service. Do not move sapstartsrv.exe with the Windows Explorer!

·        Starting and stopping an SAP instance from the snap-in fails with error "Access is denied" (0x80070005) (DCOM interface), "Invalid Credentials" or "Permission denied" (Web service interface). Nevertheless other actions from the context menu work normally. The start service checks if the calling user who runs the snap-in (DCOM interface) or is entered in snap-in WebService Authentication dialog (Web service interface) has execute permission on the sapstartsrv.exe file of the SAP instance. Verify the following:

¡        Check the file permissions of sapstarstsrv.exe on the SAP instance. Verify that the user account entered in snap-in WebService Authentication dialog (Web service interface) or running the snap-in (DCOM interface) has execute permission.

Note

To change the start and stop permissions for the selected SAP instance, do the following:

    Right-click on the SAP instance node and choose Properties.

    In the Windows Explorer right-click the sapstartsrv.exe file and choose Properties.

¡        Verify that the SAP instance is installed on an NTFS partition. FAT file systems do not support file permissions, so the start service denies all attempts to start or stop the SAP instance.

¡        The start service uses impersonation for the calling user account to check permissions. If the DCOM connection does not allow impersonation, the start service does not allow the SAP instance to be started or stopped.

·        You cannot access the developer traces with the context menu View Developer traces. When using the DCOM interface, the snap-in tries to access the developer traces directly by using the network filesystem via the saploc  or administrative drive letter share of the SAP instance. If the share does not exist or the user account running the snap-in is not allowed to access it, you cannot view the developer traces.

·        Starting the SAP MMC snap-in takes very long or a pop-up of the start service appears. If the option Always show local SAP instances is enabled, the snap-in checks the local registry for registered class IDs of locally installed SAP instances. If an instance was deleted without correctly uninstalling the service and its DCOM interface, the snap-in still tries to connect to the instance, which results in a long timeout. If the service definition was deleted, but the DCOM interface is still registered and available, DCOM starts the service without any parameters so the service installation popup is displayed. In both cases uninstall the service and its DCOM interface correctly by starting sapstartsrv -u. You need to enter the correct system SID and system number to uninstall the correct service and DCOM interface.

 

End of Content Area