A web service interface sapstartsrv needs user verification from customer (MMC, SAP MC, sapcontrol) for saved operation for example starting and stopping SAP. This verification may be failed if specifications are perfect. Windows do not need any type of verification for user/password correction so sapstartsrv may check any user verification. If entries with no user domain name exist then the system seeks for a perfect user account in all certified domain name. If user changes windows-specific DCOM interface to place web service interface then SAP MMC snapin cannot take out unspoken verification by the user.
By this reason MMC need to input a username and password of releasing 7.00 till calling a protected operation. Many of the machines have to introduce on any operating system which can only permit a password correction for some user by root rights.NIS user will be used to avoid problems but confirmation code is to be correct.
It should permit the user to check if there are some problems by PAM configuration on some platforms. If window domain name id used by user for the verification.
Configuring Outgoing Email in SAP Basis Services
If user is dependent on the platform that user uses and troubles the customers and takes out the subsequent steps:
1. If User a selects step which is right and can be confirmed ( example, Windows domain user, NIS user, not a shade password user) then this can be sorted.
2. Configure PAM properly.
3. Configure s-bit in support of the sapuxuserchk value program or install a SAP Host Agent and an appropriate kernel patch to use sapuxuserchk by design from the SAP Host Agent.
4. User can Use “trusted connect" characteristic in sapcontrol.