Link to home
Start Free TrialLog in
Avatar of Rick_Penney
Rick_Penney

asked on

HP SIM Installation

Hi, I am installing HP Systems Insight Manager on a HP Proliant ML350p Gen 8 server with Windows Server 2008 R2 OS.
The server is already configured with SQL express for Symantec Backup Exec 2014.
When I run the HP SIM installation, at the Database configuration screen it pre populates the Instance name with BKUPEXEC.
I guess I need to have a unique name for the HP SIM DB, I have tried MSSQLSERVER plus a random name but neither work.
MSSQLSERVER gives an error of MSSQLSERVER name cannot be used, any other name gives me the error of unable to connect to the specified host.
regards
Rick
ASKER CERTIFIED SOLUTION
Avatar of Milind Koyande
Milind Koyande
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Rick_Penney
Rick_Penney

ASKER

Hi, many thanks for your reply.
Please bear with me as I have no experience with SQL.
I have installed the Management Studio and the Server instance name is <hostname>\bkupexec
If I try to install HP SIM leaving the instance name as "use existing" BKUPEXEC it tries to validate but gives error of unable to connect to the specified host. please check database and port values and be sure the target database is running.
I've gone back into the Management studio and right clicked on Database and created a new database called HP_SIM. When I run the HP SIM installer and change the instance name to HP_SIM I get the same connection error message.
regards
Rick
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Apologize for the delay in reply.. Glad your issue has been resolved.
Reason for also accepting my comment as part of the solution was that the comment Milind Koyande  kindly provided steered me in the right direction but after finding the remainder of the information myself using the SQL server network configuration tool, I was then able to proceed with the installation.