- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Installing SIM 6.3 on windows 2008 r2 sp1 VM r...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2011 09:45 AM
08-29-2011 09:45 AM
Installing SIM 6.3 on windows 2008 r2 sp1 VM running on VMware Server
When trying to install SIM 6.3 I get to the error after I select Iinstall and use Sql express) I enter my password all other info looks good .
SQL 2008 express R2 installation failed with exit code: -2061893608
I have uninstalled and tried reinstalling a few times now . Any thoughts Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2011 12:59 PM
08-29-2011 12:59 PM
Re: Installing SIM 6.3 on windows 2008 r2 sp1 VM running on VMware Server
What says the Advisor before the installation? Is everything green?
I had once also an error with the installation during SQL and found the solution through the advisor which explained me that my version of the Windows Installer was not recent enough... Another time it had to do with a pending reboot...
Other possibility is to manually install the SQL before the Integrated installer... Browse the ICE DVD, somewhere you will find the directory with the executable to install the SQL...
Kr,
Bart
If my post was useful, clik on my KUDOS! "White Star" !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2011 06:56 AM
08-30-2011 06:56 AM
Re: Installing SIM 6.3 on windows 2008 r2 sp1 VM running on VMware Server
Yes I was going to install SQL express first however I'm wondering if this has anything to do with Domain. I have used the same code and successfully installed on a 2008 R2 VM standalone and a physical server 2008 R2 standalone with no issues installs the first time. The Server I'm having issue with is different only by being in the domain.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2011 08:39 PM
08-30-2011 08:39 PM
Re: Installing SIM 6.3 on windows 2008 r2 sp1 VM running on VMware Server
It is possible that if you are in a Win2k8R2 AD that there may be policy considerations.
I'd double check the pre-reqs with the SIM install guide and release notes also I'd run a checksum against the bits just in case. You can download the Insight Software DVD 1 and run the Software Advisor for HPSIM install only and see what it tells you.
More than likely though if you are at SP1 it is a user access problem, make sure you have UAC off, Windows Firewall and run the installer as administrator. You can also check with your Windows Security folks as it may be a GPO as well.
The bummer is that SQL exit code isn't all that helpful - from what I know of it that is pretty general.