VMware vSphere

 View Only
  • 1.  No access to VIC

    Posted Dec 07, 2007 02:58 PM

    Connection to VIC is refused with the message

    "Cannot connect to host ..: No connection could be made because the target machine actively refused it".

    I am using

    VIC 2.0.1 Build 32042

    ESX Server 3.0.1 Build 42829

    Looking at the virual center server i found the following problems:

    . The service "VirualCenter Server" does not start - it automatically stops again (other services are OK)

    . Event log does show event id 1000 starting and stopping again

    . vpxd log shows:

    Log for VMware VirtualCenter, pid=1724, version=2.0.1, build=build-32042, option=Release, section=2

    Current working directory: C:\WINDOWS\system32

    Initializing SSL context

    Vmacore::InitSSL: doVersionCheck = true, handshakeTimeoutUs = 120000000

    NFC connection accept timeout: 180000 milliseconds

    NFC request timeout: 180000 milliseconds

    NFC read timeout: 60000 milliseconds

    NFC write timeout: 600000 milliseconds

    Starting VMware VirtualCenter 2.0.1 build-32042

    Account name: SYSTEM

    Enabled low-frag process heap.

    Enabled low-frag crt heap.

    32 max LROs

    6 reserved internal LROs

    6 reserved blocker LROs

    6 reserved short LROs

    2 reserved long LROs

    600-second task lifetime

    ODBC error: (28000) - [ODBC SQL Server Driver][SQL Server]Login failed for user 'VMESX'.

    Failed to intialize VMware VirtualCenter. Shutting down...

    Shutting down VMware VirtualCenter now

    SetServiceStatus failed: The handle is invalid

    . Testing the DB connection in ODBC was tested OK.

    The ESX systems worked fine for ever since we had it (about a year) with no problems!

    This problem was caused because the external SQL database changed:

    . the database was moved to a new server

    . the servers SQL now uses SQL 2005 (SP?) - old SQL was 2000 i think

    . the password to access the SQL database was changed

    I changed the servername and password in ODBC and as i mentioned the test in ODBC was OK.

    Now the question:

    Could someone help to fix the access to VirtualCenter without loosing any data/templates...?

    Is HA still working without Virtual center?

    Does this problem have any impact on the license server?

    I believe an upgrade to VC 2.0.2 does not help as the current version is not working correctly?

    Thank you in advance



  • 2.  RE: No access to VIC

    Posted Dec 07, 2007 03:04 PM

    Check the release notes for VC2.0.1. You may need to update to VC2.0.2?

    "Support for Microsoft SQL Server 2005 (SP1 only) as a database for VirtualCenter. See Requirements for Running VirtualCenter with MS SQL 2005 (KB 6565318) for information on using this database with VirtualCenter."



  • 3.  RE: No access to VIC

    Posted Dec 07, 2007 03:19 PM

    Sorry, i forgot to mention that the DB is running in compatebility mode. I have also tried to change to the old DB on the old server (its still active but currently read only) with NO Success. I suppose the problem is that the Password has changed?



  • 4.  RE: No access to VIC

    Posted Dec 07, 2007 03:24 PM

    Also, to address a few of your other questions:

    - Your HA should be working properly at the moment. This does not need

    VC to continue functioning once configured.

    - The license service should still be running fine - it is not impacted

    by SQL.