VMware vSphere

 View Only
  • 1.  VC Lic Srvr error, wont start service

    Posted May 16, 2007 05:56 PM

    We have a 2003 box that has been our dev VC box. Its fully patched. I am just now getting back to dev testing for our proposed environment. Trying to install new license file but the Lic Service wont start automatically. When I try to start it I get error: "Could not start the VMware License Service on Local Computer. Error 1067: The process terminated unexpectedly."

    BTW, I have the hosts that are connected to this VC running their own licenses, this is different from when I fist had it setup and running.

    I also dont see under help the license adding feature while in VC.

    TIA



  • 2.  RE: VC Lic Srvr error, wont start service

    Posted May 16, 2007 06:12 PM

    OK looks like my default SQL instance wont start up either. A search revealed these realted. Any hints ???



  • 3.  RE: VC Lic Srvr error, wont start service
    Best Answer

    Posted May 16, 2007 06:15 PM

    If SQL is failing to start you'll likely see some errors in the Windows application and system logs. Any specific errors in the system log?



  • 4.  RE: VC Lic Srvr error, wont start service

    Posted May 16, 2007 09:48 PM

    App logs:

    Event ID: 1002, Hanging application sqlmangr.exe, version 2000.80.760.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    Another one is:

    Event ID: 19011, The description for Event ID ( 19011 ) in Source ( MSSQL$MSDE_VC ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: (SpnRegister) : Error 1355.

    I also have for sys log:

    Event ID: 4, AMLI: ACPI BIOS is attempting to read from an illegal IO port address (0x71), which lies in the 0x70 - 0x71 protected address range. This could lead to system instability. Please contact your system vendor for technical assistance.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    This might be starting to look like a HW issue huh... Its old HW that VC is running on. Looking at MS site now.