vCenter

 View Only
  • 1.  Issue after install

    Posted Sep 28, 2009 06:42 AM
    I have a feeling that this is an issue that happens to everyone, and I'm going to get flamed but I've had a look around and can't really find what I'm looking for.

    We are running Server 2003 and have installed HQ.

    When logging into the dashboard we get the error message "The HQ Server is still starting"

    This still appears ~ an hour after starting the service.

    I went digging through the logs and found an error in the Server log.

    I have stopped and restarted the services multiple times, rebooted the server and reinstalled twice and I get the same error.

    We have never had HQ working before, but we wish to try it out.

    Attached is my log - I am using all the default settings re: database and ports.

    Any help would be awesome.

    Thanks.


  • 2.  RE: Issue after install

    Posted Sep 28, 2009 09:56 PM
    These errors are rather fatal and point to a incorrect or incomplete database installation. Are you using the embedded database or external PostgreSQL? Where there errors during installation? Find the hq-install.log and hq-install.log.debug logs for more info.


  • 3.  RE: Issue after install

    Posted Sep 29, 2009 01:42 AM
    Hi Marty,

    Thanks for your response.

    I'm using the default built in database, all logs say it's successful - I have attached them here, in case I'm missing something.

    I must say I'm relieved this isn't blindingly simple!

    I didn't get any errors while installing. I installed via the msi file.

    During my multiple installs I tried using all the default settings and again where i set my own admin user name and password - same result each time.


  • 4.  RE: Issue after install

    Posted Sep 29, 2009 05:42 AM
    Well I think I've managed to fix it!

    I installed it on my XP workstation, and it worked fine, so what I did was copy the entire server folder overwrite it on the server, stopped and started the service and hey presto! it works.

    That being said I'm not sure why re installs didn't fix the issue, but it seems to be working now.

    Thanks Marty.