Troubleshooting ACC 7.1 Setup

You can use the work around mentioned in the procedures below for any of the following problems that occur while using the ACC 7.1:

The computer systems or services in the Resources view show incorrect status.
Authorization exceptions occur while logging into the ACC.
SLD exceptions occur while logging into the ACC.
Permission denied exception occurs when you start, stop, or relocate a service.
Invalid Credentials exception occurs when you start, stop, or relocate a service.
Stopping Instance Agent Fails with HTTP 401 Unauthorized Error.

Procedure

Computer Systems or Services Report an Incorrect Status

When the computer systems do not show a green status, or the status of the services reported is incorrect, you can perform the following checks:

Check the availability of SAP Host Agents.
1. Log on to the computer system data provider test page using the URL http://<host>:<port>/tc~lm~itsam~core~computersys~web/csdp_test.jsp
2. Choose Show availability information (directly from SAP_ITSAMComputerSystems).
  All your AC managed computer systems should appear as available: true in the list.
  
  If there are computer systems that appear as available:false in the list:
  1. Check if the host is reachable from the manager system by opening the URL http://<hostagent_host>:1128/SAPHostControl/?wsdl in a browser on the manager system. You should get the SAP HostAgent wsdl as a result (for example, by pinging the host) and the host agent port (typically ‘1128’) is not blocked.
  2. Check if the host agent is running on the specific host.
Check if the NetWeaver Scheduler is Switched On
1. Log on to the SAP Java EE Config Tool.
2. Navigate to services, and choose the scheduler service configuration.
3. Make sure that the key enableJobExecution has the value true, and the key removeTasksOnSingletonStart has the value false.
4. If you changed the values of the keys in the previous step, then save the changes and restart the Java AS cluster.
Check if Prefetch Jobs are scheduled.
1. Log on to the SchedulerAdministrator using the URL http://<host>:<port>/SchedulerAdministrator.
2. Navigate to Scheduler tasks.
  Make sure that at least four Prefetch Jobs, and one Routing Job is listed.
3. If the jobs are missing, execute the configuration wizard that configures ACC in the SAP NetWeaver Administrator again.
Check if Prefetch Service Data Providers are running without errors.
1. Log on to the SchedulerAdministrator using the URL http://<host>:<port>/SchedulerAdministrator.
2. Navigate to List completed jobs, and open the Log of any currently completed PrefetchJob.
  If the list of completed jobs is empty, the Job Scheduler is switched off. Follow the steps described in the Check if the NetWeaver Scheduler is switched on point.
  
  If there are log messages with severity warning like WARNING Data provider SAP_ITSAMComputerSystemDataProvider was not found, execute the configuration wizard that configures ACC in the SAP NetWeaver Administrator again.
Check if Computer System Data Provider is Working.
1. Log on to the computer system data provider test page using the URL http://<host>:<port>/tc~lm~itsam~core~computersys~web/csdp_test.jsp
2. In the Hostname field, enter the host name of any of your AC managed computer systems and choose Get prefetched computer system data.
  The Prefetch timestamp details are displayed as output. For example, Tue Mar 06 15:39:15 CET 2007.
  
  The Prefetch timestamp must not be older than several minutes, as the data provider is triggered each 60 seconds.
Check if Service Status Data Provider is working
1. Log on to the computer system data provider test page using the URL http://<host>:<port>/tc~lm~itsam~core~acservicestatus~web/statdp_test.jsp
2. Choose get status data for all SAP instances.
  The Prefetch timestamp details are displayed as output. For example, Wed Mar 07 12:54:53 CET 2007.
  
  The application displays the status information of all AC managed instances as it was collected by the prefetch service.
  
  The timestamp must not be older than several minutes, as the data provider is triggered each 60 seconds.

SAP Systems not visible in the ACC Service Configuration

An installed SAP System is not available in the ACC Service Configuration and therefore you can not configure and manage the SAP system. In this case you can:

Check, if the SAP system is registered in the SLD.
1. Log on to the computer system using the URL http://<host>:5<instance #>00/sld.
  1. From the CIM Instances / CIM Classes, select the appropriate SLD class for your SAP system (for example, All in One System or BC System).
  2. Enter the SAP System ID in Filter.
  3. Choose Go.
    Your SAP System should be visible in the CIM Instances table.
If your SAP system is not visible in the SLD, the reasons could be
- The installation failed somehow
- The SAP system has never been started
- The SAP system components did not register correctly in the SLD. Maybe one or several data suppliers have to be patched or configured.
If your SAP system is visible in the SLD, the reasons could be
- The appropriate CTC template for your SAP system has never run or has not finished correctly.
In this case you go to the central NWA system and rerun the CTC template NWA Add Managed System for the missing SAP system.

Authorization Exception Occurs when logging into ACC (Missing Permissions)

Authorization exceptions occur when logging into ACC when the user does not have the required permission. In this case you can:

Log on to the UME, and create a new role (for example, ACC_Admin) and assign the following 10 actions:

Type	Service/Application	Name
UME	tc~lm~aci~engine~app	OperationExceptionHandling
UME	tc~lm~aci~engine~app	ServerEnable
UME	tc~lm~aci~engine~app	Archiving
UME	tc~lm~aci~engine~app	Configuration
UME	tc~lm~aci~engine~app	Operation
UME	tc~lm~aci~engine~app	ServiceEnable
UME	jmx	JmxManageAll
UME	tc~lm~aci~engine~app	Schedule
UME	tc~lm~aci~engine~app	Observing
UME	tc~lm~aci~engine~app	CustomizeLink

Assign this role to the Administrators group, and to all users who work with ACC.

SLD Exception Occurs when logging on to ACC

ACC 7.1 requires an SAP SLD model version 1.5.18 or higher. An SLD exception Failed to find adaptive controller instance. Make sure the sap.com /tc~lm~aci~engine~app application is deployed, running and configured occurs when the model version of the SLD is less than 1.5.18. In this case of SLD exception, perform the following checks:

Check the current SLD model version.
Log on to the SLD Administration UI using the URL http://<host>:<port>/sld
Choose Administration Details .
On the Data tab page, check the model version of namespace sld/active.
This version needs to be 1.5.18 or higher:
If the SLD model version is lesser than 1.5.18, download a newer version from \\rrrdev\lid\landscape\CR_exports\requiredModel\dev
Choose Administration Import .
Select the downloaded model (.zip file) and choose Import....

Permission denied exception occurs

When the user does not have sufficient permissions to execute protected operations (For example, start or stop instance), the Permission denied exception occurs.

The host agent connection user (sapadm) requires the write permissions to the sapstartsrv executable in the executable directory of the host agent (UNIX: /usr/sap/hostcontrol/exe)

Message Code	Severity	Message
... ACC	... Information	... Executing the operation process step with ID'process-723017a-03c4-11dc -8937-0002b3c0b411-step' now. Type of operation" 'Start of an adaptive installed instance via HostAgent'
ACC	Information	Using the follwong argumetns. ServiceID: 'SystemID.NYA.Number.24.InstanceHost. scsnys',Hostname:'aip4224n0',SID:'NYA',StstemNumber:'24',SAPLOCALHOST:' scsnya',USerExit:'false',HostAgentProtocol:'http',HostAgentuser:'sapadm', HostAgentPort:'1128'
ACC	Information	Preparing the nost 'aip4224n0' now (calling'ACOSPrepare()' on host agent).
ACC	Error	RemoteException thrown by HostAgent when executing ACOSPrepare:'Server Exception: Permission denied; nested exception is: javex.xml.rpc.soap.SOAPFaultException: Permission denied'

To resolve this error, perform the following activities:

Ensure that the sapstartsrv executable is owned by the user sapadm and that this user has write permissions.
Connect to the host agent with the sapadm user or any other user who has write access to the sapstartsrv executable.

Invalid Credentials exception occurs

The host agent authenticates the connection user (sapadm) with the help of operating system user authentication facilities (For example, PAM on UNIX). The host agent throws the Invalid Credentials exception if this authentication fails, when you start, stop or relocate a service.

Message Code	Severity	Message
... ACC	... Information	... Using the follwoing arguments. ServiceId: 'SystemID.TRX.Number.02. InstanceHost.vqe2tx', HostnameL'Is2105', SID: 'TRX', SystemNumber: '02', SAPLOCALHOST: 'vqe2tx', UserExit:'false', HostAgentProtocol: 'http', HostAgentUser: 'sapadm', HostAgentPOrt: '1128'
ACC	Information	Executing the stop of instance on host 'Is2105' now (calling 'stopInstance()'on Host Agent).
ACC	Error	Error occurred when trying to stop instance. (RemoteException: 'Server Exception: Invalid Credentials; nested exception is: javax.xml.rpc.soap.SOAP FaultException:Invalid Credentials')

To resolve this, perform the following activities:

Ensure that the connection user is available on the host, and you are using the correct password.
On UNIX, verify your PAM setup.
For more information, refer SAP note 927637.

SAPControl Fails with HTTP 401 Unauthorized Error

When starting or stopping an instance or instance agent an exception occurs.

The host agent uses the sapcontrol program to control an SAP instance. The sapcontrol program can use a trusted connect feature to setup a local connection to an instance agent without providing a user and password. On UNIX, the trusted connect feature is implemented through a UNIX Domain Socket (UDS).

1. Unintentionally, the instance agent removes this UDS when stopping its instance.

2. The UDS file is not owned by the instances <sid>adm user and/or the <sid>adm user has no write permissions to this file.

When starting or stopping an instance or when the instance agent fails, the following messages appear in the Log Details of the ACC Operation Log:

Message Code	Severity	Message
... sapcontr	... Information	... StopService
sapcontr	Information	FAIL: HTTP error, HTTP/1.1 401 Unauthorized
saphostc	Error	Sapcontrol terminated with error
ACC	Error	Error occured when trying to stop instance. (Operation Exception: 'Command Execution failed.' Fault Code: '127')

As a solution:

Upgrade the instance agent. For more information: refer SAP note 877795.
Shutdown the instance agent, delete the UDS file and restart the instance agent that re-creates the UDS file with the correct ownership and permissions. Proceed as follows:
- Log on with the <sid>adm user
- Shutdown the instance agent by executing the following command:
  sapcontrol -nr <NR> -function StopService -user <sid>adm<password>
- Change to the root user and remove the UDS file. The file is located in the /tmp directory and the file name convention is “.sapstream5<NR>13”
- Change back to the <sid>adm user and start the instance agent for example, with the following command:
  sapcontrol -nr <NR> -function StartService <SID>