5 troubleshooting, Powershell script fails – HP ProLiant DL980 G7 Server User Manual

Page 79

Advertising
background image

5 Troubleshooting

The following sections describe tips for troubleshooting problems that might arise while using HP
ESO.

HP ESO is not found on the SMH page and HP Enterprise SQL Optimizer
is in Disabled state in the service list

Problem description:

After uninstalling and then reinstalling HP ESO, HP ESO is not seen on the HP SMH homepage.
The HP Enterprise SQL Optimizer in the OS service list is Disabled. This occurs when multiple users
are connecting to the system during the reinstallation or upgrade process.

Resolving the problem:

Make sure you are the only user connecting to the system. Then uninstall and reinstall HP ESO
again.

Access to SQL Server or Analysis Services instance is denied

Problem description:

When attempting to log in to an instance from the SQL Login page login fails: the Login Status field

in the fifth column displays the

symbol, and the Latest Login Log field near the top of the page

indicates either of the following two problems:

The specified account is not assigned sufficient server roles in the SQL Server, as required for
access to the indicated SQL Server instance.

The specified account is not a member of the Server Administrators group, as required for
access to the indicated Analysis Services instance..

Resolving the problem:

This problem indicates that the affected user account was not configured properly to access the
indicated instance. To ensure access to SQL Server instances, follow the instructions given in

“Set

user account privileges in Database Engine security” (page 15)

. To ensure access to Analysis

Services instances, follow the instructions given in

“Set user account privileges in Analysis Services

security” (page 16)

.

PowerShell script fails

Problem description:

On attempting to run a PowerShell script, an error message indicates that the script cannot be
loaded because running scripts is disabled on the system. The likely cause of this problem is that
the systemwide PowerShell policy is not set. The policy must be set when running any PowerShell
script (not only HP ESO scripts) on a Windows system.

Resolving the problem:

Make sure the execution policy is set before running any PowerShell Script. Instructions for setting
the policy are included in

“Using a PowerShell script to apply all recommended optimization values

of settable parameters and to initialize software discovery” (page 75)

.

HP ESO is not found on the SMH page and HP Enterprise SQL Optimizer is in Disabled state in the service list

79

Advertising