Troubleshooting ACC 7.1 Setup 

Use

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

...

       1.      The computer systems or services in the Resources view show incorrect status.

       2.      Authorization exceptions occur while logging into the ACC.

       3.      SLD exceptions occur while logging into the ACC.

       4.      Permission denied exception occurs when you start, stop, or relocate a service.

       5.      Invalid Credentials exception occurs when you start, stop, or relocate a service.

       6.      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:

...

       1.      Check the availability of SAP Host Agents

                            a.      Logon to the computer system data provider test page using the URL http://<host>:<port>/tc~lm~itsam~core~computersys~web/csdp_test.jsp

                            b.      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:

                                                  i.       Check if the host is reachable from the manager system (for example, by pinging the host) and the host agent port (typically ‘1128’) is not blocked.

                                                ii.       Check if the host agent is running on the specific host.

       2.      Check if the NetWeaver Scheduler is Switched On

                            a.      Logon to the SAP Java EE Config Tool.

                            b.      Navigate to services, and choose the scheduler service configuration.

                            c.      Make sure that the key enableJobExecution has the value true, and the key removeTasksOnSingletonStart has the value false.

                            d.      If you changed the values of the keys in the previous step, then save the changes and restart the Java AS cluster.

       3.      Check if Prefetch Jobs are scheduled

                            a.      Logon to the SchedulerAdministrator using the URL http://<host>:<port>/SchedulerAdministrator.

                            b.      Navigate to Scheduler tasks.

Make sure that at least four PrefetchJobs, and one RoutingJob is listed.

                            c.      If the jobs are missing, execute the configuration wizard that configures ACC in the SAP NetWeaver Administrator again.

       4.      Check if Prefetch Service Data Providers are running without errors

                            a.      Logon to the SchedulerAdministrator using the URL http://<host>:<port>/SchedulerAdministrator.

                            b.      Navigate to List completed jobs, and open the Log of any currently completed PrefetchJob.

You should see the following output:

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.

       5.       Check if Computer System Data Provider is Working

                            a.      Logon to the computer system data provider test page using the URL http://<host>:<port>/tc~lm~itsam~core~computersys~web/csdp_test.jsp

                            b.      Enter the host name of any of your AC managed computer systems and choose Get prefetched computer system data.

The timestamp must not be older than several minutes, as the data provider is triggered each 60 seconds.

       6.      Check if Service Status Data Provider is working

...

...

                            a.      Logon to the computer system data provider test page using the URL http://<host>:<port>/tc~lm~itsam~core~acservicestatus~web/statdp_test.jsp

                            b.      Choose get status for all SAP instances.

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.

Authorization Exception Occurs when logging into ACC

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

...

       1.      Logon to the UME, and create a new role (for example, ACC_Admin) and assign the following 10 actions:

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

SLD Exception Occurs when logging in into ACC

ACC 7.1 requires an SAP SLD model version 1.5.18 or higher. An SLD exception occurs when the model version of the SLD is less than 1.5.18. In this case of SLD exception, perform the following checks:

...

       1.      Check the current SLD model version.

                            a.      Logon to the SLD Administration UI using the URL http://<host>:<port>/sld.

                            b.      Choose Administration →Details.

                            c.      On the Data tab page, check the model version of namespace sld/active.

This version needs to be 1.5.18 or higher:

       2.      If the SLD model version is lesser than 1.5.18, download a newer version.

                            a.      Choose Administration → Import.

                            b.      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 Permisission 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).

Perform the following activities:

...

       1.      Ensure that the sapstartsrv executable is owned by the user sapadm and that this user has write permissions.

       2.      Connect to the host agent with the sapadm user or any other user that has write access to the 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.

Perform the following activities:

...

       1.      Ensure that the connection user is available on the host, and you are using the correct password.

       2.      On UNIX, verify your PAM setup.

For more information, refer SAP note 927637.

Stopping Instance Agent Fails with HTTP 401 Unauthorized Error

On Unix, the host agent (the sapcontrol program – which is used by the host agent to control an instance) relies on a unix domain socket to make a trusted connect to the instance agent.

The instance agent removes this socket when stopping the instance. The sapcontrol tries to connect via HTTP to the instance agent and results in the error, when you stop or relocate an instance.

As a solution, upgrade the instance agent.

For more information, refer SAP Note 877795.