DRAFT: version 1.0 Jump to content English
hp.com home
HP Systems Insight Manager  |  Troubleshooting  |  Login Problems

Troubleshooting
Login Problems

» HP Systems Insight Manager

»Table of Contents
»Index
»Product Overview
»Getting Started
»Monitoring Systems, Events, and Clusters
»Using Tasks
»Using Default Tools
»Reporting
»Administering the Software
»Troubleshooting
»HP Systems Insight Manager Problems
»Installation Problems
Login Problems
»Microsoft Internet Explorer Problems
»Security Problems
»IP Address Problems
»System, Cluster, and Event Problems
»Operating System Problems
»SQL and MSDE Problems
»Agent Problems
»Command Line Interface Problems
»CMS Problems
»Tool Problems
»List Problems
»Task Problems
»Reporting Problems
»Log Problems
»Windows Event Log
»Miscellaneous Problems
»Service and Support
»Glossary
»Using Help
Content starts here

I am unable to log in to HP Systems Insight Manager on Windows XP using a blank password.

Solution 1: Use a non-blank password, which provides better security. Have an administrator re-configure the Windows User Account(s) to specify a non-blank password.

Solution 2: If you must use a blank password, disable the following Security Policy on the Windows XP machine: Accounts: Limit local account use of blank passwords to console login only.

Disabling this policy will allow remote logins over the network using accounts that have no passwords.

To limit local account use of blank passwords to console login only, complete the following:

  1. Open Local Security Settings MMC Application by selecting ProgramsAdministratiave ToolsLocal Security Policy.

  2. Open the Local Security Policies folder, then open the Security Options sub-folder.

  3. Disable the policy.

Unable to login to HP Systems Insight Manager on Windows XP.

Solution: If using a blank password, refer to the problem above, otherwise, change the following Local Security Policy on the Windows XP machine: Network Access: Sharing and security model for local accounts from Guest Only to Classic.

This setting does not affect remote logins using domain accounts. Modifying this policy will allow remote logins over the network using any local account configured to do so, not just the Guest account; ensure all local accounts have appropriate passwords.

To change the setting, perform the following:

  1. Open Local Security Settings MMC Application by selecting ProgramsAdministrative ToolsLocal Security Policy.

  2. Open the Local Security Policies folder, and then open the Security Options sub-folder.

  3. Change the setting from Guest Only to Classic.

If Guest Only is the preferred policy setting, perform the steps above, login to HP Systems Insight Manager, and then add either domain accounts (not local accounts) or the local Guest account, as accounts to HP Systems Insight Manager. Restore the local policy setting back to Classic when done.

Single Login fails on Cluster systems.

Solution: Single Login will not work on a Virtual Cluster system. It will work on the physical systems that comprise the Cluster.

By using a proxy server, users may inadvertently or intentionally bypass IP address login restrictions configured for the user.

Solution: It is possible that a proxy server may be used to bypass specific IP Exclusions, if, the proxy server IP address is not included in the IP Exclusion Range. Likewise, the possibility that a valid proxy server is included in the IP Exclusion Range, would prevent a valid user from logging in through that particular proxy server.

Ensure valid proxy servers are within a valid Inclusion Range and make the Inclusion Range as small as possible. Using IP Inclusion Ranges is more effective than using IP Exclusion Ranges since Inclusion Ranges exclude all addresses not specified in the IP Inclusion Range.

Unable to login to HP Systems Insight Manager or to managed systems browsing from HP Systems Insight Manager using Internet Explorer 6.0.

Reason 1: Internet Explorer has a problem with underscores in system names, which prevents the authentication cookie from working properly.

Solution 1A: For HP Systems Insight Manager, if you are using Internet Explorer 6.0 and your HP Systems Insight Manager server has an underscore in the name, use the IP address of the HP Systems Insight Manager server instead of the name in the Internet Explorer address field.

Solution 1B: For managed systems, if the names of the systems have an underscore, use the IP address of the system. You can configure HP Systems Insight Manager to create links to the system using the IP address instead of the name by:

  1. Browse and login to HP Systems Insight Manager.

  2. Click OptionsSecuritySystem Link Configuraiton. The System Link Configuration page is displayed

  3. Select Use the system IP address.

  4. Click [OK].

Note: By using IP addresses instead of names, you may encounter Security Alerts, if the name in the managed system certificate does not match the name in the link. The default certificate for managed systems uses the system name, not the IP address.

Reason 2: For managed systems, the privacy policy setting in Internet Explorer 6.0 is blocking the authentication cookies from the managed systems.

Solution 2A: Change the browser's privacy security policy setting. From the browser menu, select ToolsInternet Options, then select the Privacy tab. The privacy setting can be modified in one of the following ways:

  • Set the privacy setting to Accept all Cookies by sliding the slider bar to the bottom. This will allow the browser to accept all cookies for both first-party and third-party sites. When browsing to Insight Manager XE or HP Systems Insight Manager, or directly to a managed system, it is considered a first-party site. When navigating to a managed system through Insight Manager XE or HP Systems Insight Manager, the system is considered a third-party site.

or

  • Customize the handling of cookies by clicking Advanced and enabling Override automatic cookie handling. Then select the appropriate radio buttons for first-party and third-party cookies to either Accept or Prompt. If you select Prompt, the browser will prompt you on how to handle a cookie each time a cookie is received. You can choose to block or allow the cookie each time, or for all times. Enabling Always allow session cookies won’t resolve the problem since the Web Agents do not use session cookies.

or

  • Individually specify the handling of cookies for each system. Click [Edit] in the Websites section and add the address of the system in the specified field. Click [Allow] to always allow cookies to that system. Repeat this for all systems.

Solution 2B: Remove the systems from the Internet Zone. The privacy policy only affects systems in the browser’s Internet Zone, so by removing systems from that zone, you prevent the privacy policy from affecting those systems. This can be accomplished in one of the following ways:

  • Browsing to systems by IP address instead of by name may cause the browser to consider those systems to be in the Internet Zone. Instead, browse by name. You can configure HP Systems Insight Manager to use system names when creating links to systems by going to OptionsSecuritySystem Link Configurationand selecting Use the system name.

  • If your browser is configured to use a proxy server, you can configure your browser to bypass the proxy server for specific systems, which removes those systems from the browser’s Internet Zone. From the browser menu, click ToolsInternet Options, then select the Connections tab. Click LAN Settings, and if you are configured to use a proxy server, click Advanced. In the Exceptions list, you can specify a list of addresses that should bypass the proxy server; these addresses will no longer be in the Internet Zone and will not be affected by the privacy settings policy.

Selecting a link that opens up a new browser window requires another login.

Solution: If you are browsing using the Internet Explorer link from within Windows Explorer, you must instead start Internet Explorer as a separate process. Start Internet Explorer by selecting it from the Windows Start menu or using the desktop icon.

I cannot log into the HP Systems Insight Manager server from Windows NT, Windows 2000, or Windows XP.

Solution: The Windows account(s) used to access HP Systems Insight Manager must have the access this computer from the network right selected.

In Windows NT 4, open the User Manager by clicking StartProgramsAdministrative Tools. In the Policies menu, select User Rights. In the Rights drop-down, select access this computer from network and ensure the HP Systems Insight Manager users are granted full rights.

In Windows 2000 and Windows XP, open the Local Security Policy by clicking StartProgramsAdministrative Tools. Expand the Local Policies tree, and select User Rights Assignment. Ensure the HP Systems Insight Manager users have the access this computer from the network right and that they do not have the Deny access to this computer from the network right selected.

I am receiving the exception org.apache.jasper.JasperException while logging in to HP Systems Insight Manager.

Solution: Delete all the files in the install dir>\www\ui\jsp\compiled directory and log in again.

Your login user name is a valid HP Systems Insight Manager user, but you are no longer considered a valid user. Execution of any HP Systems Insight Manager commands fails with the error: The name ‘?’ does not represent a user in this system.

Verify that you are still a HP-UX or Linux user.

  • Execute the id(1)command. If it returns an empty string for the user name, then your HP-UX or Linux login name has been removed or is no longer accessible.

  • Execute:

    ypcat passwd │ grep login

    or

    grep login /etc/passwd

    If no passwd line is found, you are no longer considered an HP-UX or Linux user.

Solution: If you are using NIS, verify that /etc/passwd still contains the +::0:0::: entry at the end of the file. If not, try restoring this line. Deparaine if this fixes the problem by running the verification commands again.

If your HP-UX user login is missing, log in as root and add the user back using the System Administration Manager tool, SAM. If your Linux user login is missing, log in as root and add the user back using the useradd(8) command.