vCenter Server does not start no more after windows update (KB960715)

[CurtisNewton]

Hello,

since yesterday, VirtualCenter Server does not start no more after a system reboot.

Windows does an automatic update for ActiveX Killbits (KB960715), and system rebooted.

But since this update, the Virtual Center Server does not start automaticly.

But I can start it manually over the windows services, and yes, it is set to automatic there.

The following error messages are logged:

Type: error control

Quelle: MSSQL$SQLEXP_VIM

Kategorie: (4)

Ereigniskennung: 18456

Benutzer: NT-AUTORITÄT/System

Beschreibung: Login-failed for user ‚NT-AUTORITÄT/SYSTEM'.

Daten Bytes (Inhalt): SQLEXP_VIM master

Type: error

Quelle: VMware VirtualCenter Server

Kategorie: Keine

Ereigniskennung: 1000

Benutzer: Nicht zutreffend

Beschreibung: Failed to initialize VMware VirtualCenter. Shutting down...

vpxd-4.log

ODBC error: (28000) – [SQL Native Client][SQL Server]Login failed for user ‘NT-AUTORITäT\SYSTEM’.

Failed to initialize VMware VirtualCenter. Shutting down…

Forcing shutdown of VMware VirtualCenter now

So, it looks like some timing problem or a problem with SQL ... but i did not change anything ... and i did not set any password for the sql ?!

With tipps to the elimination of errors I would be pleased!!!

For your information: i got a second system, with the same installation, but not this windows update and everything works fine, reboot too!

Thanks

cu

CURTIS

Systems:

Windows 2003 Server SP2, Standard Edition

VMware VirtualCenter Server 2.5.0.64228

Microsoft SQL Server 2005

Microsoft SQL Server Native Client 9.00.3042.00

[CurtisNewton]

i tried it with the following:

Cause:

The SQL Server is not available. In this case the SQL Server is installed on the same server as VirtualCenter and has not started by the time the VirtualCenter Server service attempts to start.

Solution:

Add the local SQL Server as a dependency to the VirtualCenter Server service. Perform the following on the VirtualCenter Server.

1) Start Regedit

2) Browse to the following key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vpxd

3) Double Click the DependOnService value name

4) Add the SQL Service key name to the list of services

a. By default this is MSSQL$SQLEXP_VIM

5) Click Ok

6) Restart the computer

it was missing,

but that change nothing in the situation, error remains, vCenter Server not started.

which I do not understand is the error

MSSQL$SQLEXP_VIM

Login failed for user NT-AUTORITY/SYSTEM, CLIENT: local machine

where can i find more information to solve this problem???

cu

CURTIS

[Ciaran Garvey]

There is an article on yellow-bricks about this:

http://www.yellow-bricks.com/2009/02/12/vcenter-and-sql-service-dependencies/

hope this helps,

Cgrvy

[CurtisNewton]

Hello cqrvy,

thanks for your answer, but i tried this before (see my self-answer) and it does not help.

I think the bigger problem is the login failure of sql ...

but in the error message its NT-AUTORITY/SYSTEM and in the service SQL Server (SQLEXP_VIM) its NT-AUTORITY/NetworkService ...

sorry, i am a vmware/sql noob!

cu

CURTIS

[CurtisNewton]

Here is the sql error log:

2009-02-16 11:53:34.03 Server Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)

Nov 24 2008 13:01:59

Copyright (c) 1988-2005 Microsoft Corporation

Express Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2009-02-16 11:53:34.03 Server (c) 2005 Microsoft Corporation.

2009-02-16 11:53:34.03 Server All rights reserved.

2009-02-16 11:53:34.03 Server Server process ID is 1280.

2009-02-16 11:53:34.03 Server Authentication mode is WINDOWS-ONLY.

2009-02-16 11:53:34.03 Server Logging SQL Server messages in file 'C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.

2009-02-16 11:53:34.04 Server This instance of SQL Server last reported using a process ID of 5048 at 16.02.2009 11:50:17 (local) 16.02.2009 10:50:17 (UTC). This is an informational message only; no user action is required.

2009-02-16 11:53:34.04 Server Registry startup parameters:

2009-02-16 11:53:34.04 Server -d C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf

2009-02-16 11:53:34.04 Server -e C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG

2009-02-16 11:53:34.04 Server -l C:\Programme\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf

2009-02-16 11:53:34.15 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.

2009-02-16 11:53:34.15 Server Detected 2 CPUs. This is an informational message; no user action is required.

2009-02-16 11:53:36.26 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.

2009-02-16 11:53:36.74 Server Database mirroring has been enabled on this instance of SQL Server.

2009-02-16 11:53:36.81 spid5s Starting up database 'master'.

2009-02-16 11:53:37.03 spid5s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.

2009-02-16 11:53:37.43 spid5s SQL Trace ID 1 was started by login "sa".

2009-02-16 11:53:37.46 spid5s Starting up database 'mssqlsystemresource'.

2009-02-16 11:53:37.49 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.

2009-02-16 11:53:37.95 spid8s Starting up database 'model'.

2009-02-16 11:53:37.95 spid5s Server name is 'VMMANAGE01\SQLEXP_VIM'. This is an informational message only. No user action is required.

2009-02-16 11:53:38.15 spid5s Starting up database 'msdb'.

2009-02-16 11:53:38.17 Server A self-generated certificate was successfully loaded for encryption.

2009-02-16 11:53:38.17 Server Server local connection provider is ready to accept connection on http:// \\.\pipe\SQLLocal\SQLEXP_VIM .

2009-02-16 11:53:38.17 Server Server named pipe provider is ready to accept connection on http:// \\.\pipe\MSSQL$SQLEXP_VIM\sql\query .

2009-02-16 11:53:38.18 Server Dedicated administrator connection support was not started because it is not available on this edition of SQL Server. This is an informational message only. No user action is required.

2009-02-16 11:53:38.19 Logon Error: 17187, Severity: 16, State: 1.

2009-02-16 11:53:38.19 Logon SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.

2009-02-16 11:53:38.20 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.

2009-02-16 11:53:38.67 spid8s Clearing tempdb database.

2009-02-16 11:53:38.77 Logon Error: 18456, Severity: 14, State: 16.

2009-02-16 11:53:38.77 Logon Login failed for user 'NT-AUTORITÄT\SYSTEM'.

2009-02-16 11:53:39.41 Logon Error: 18456, Severity: 14, State: 16.

2009-02-16 11:53:39.41 Logon Login failed for user 'NT-AUTORITÄT\SYSTEM'.

2009-02-16 11:53:41.12 spid8s Starting up database 'tempdb'.

2009-02-16 11:53:41.57 spid5s Recovery is complete. This is an informational message only. No user action is required.

2009-02-16 11:53:41.59 spid11s The Service Broker protocol transport is disabled or not configured.

2009-02-16 11:53:41.59 spid11s The Database Mirroring protocol transport is disabled or not configured.

2009-02-16 11:53:41.78 spid11s Service Broker manager has started.

2009-02-16 12:01:28.76 Server SQL Server is terminating because of a system shutdown. This is an informational message only. No user action is required.

2009-02-16 12:01:30.81 spid11s Service Broker manager has shut down.

2009-02-16 12:01:30.82 spid11s Error: 17054, Severity: 16, State: 1.

2009-02-16 12:01:30.82 spid11s The current event was not reported to the Windows Events log. Operating system error = 31(Ein an das System angeschlossenes Gerät funktioniert nicht.). You may need to clear the Windows Events log if it is full.

2009-02-16 12:01:31.18 spid5s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

2009-02-16 12:01:31.32 Server Server resumed execution after being idle 439 seconds: user activity awakened the server. This is an informational message only. No user action is required.

so, this line could be the problem:

2009-02-16 11:53:38.19 Logon SQL Server is not ready to accept new client connections. Wait a few minutes before trying again. If you have access to the error log, look for the informational message that indicates that SQL Server is ready before trying to connect again.

but where can i find more information or configuration?

Nachricht geändert durch CurtisNewton

[CurtisNewton]

funny thing, on the second machine, i did the following:

- checked the SQL pipe, and enabled Named Pipes in the SQL Server Configuration Manager

- changed the host name in big letters

- added the hostname into hosts file

and after reboot the VirtualCenter Server starts! but not on the first machine - see SQL error log above

sorry, i do not understand it ...

... Nachricht geändert durch CurtisNewton ...

[kooltechies]

Hi,

Do you have the SQL server on the same machine as VC , if thats the case then this error will come because the SQL server is still getting initialized when the VC requests for a connectio. You can resolve this by setting the VC service to restart each time its failing.

Steps :

Open the services panel > select Virtual center service > properties > recovery Tab > choose restart the service for each failure.

Second option will be to move your sql server to a remote server rather than local.

Thanks,

Samir

P.S : If you think that the answer is helpful please consider rewarding points.

[CurtisNewton]

Hi kooltechies,

yes, i checked this too, but changed nothing ...

please remember, i have two identical server, with identical installation (W2kSP2,VMware VCserver/License,SQL together), one starts VCserver and the other one not ...

my last hope: harddisk defragmentation

cu

Curtis

[DaveConverySHI]

Curtis -

Maybe the login for vCenter to the SQL Express DB was somehow corrupted. You can install the SQL Express Management Studio and change the account that vCenter uses for logging into SQL.

http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en

Dave

************************

Accomplishing the impossible means only that the boss will add it to your regular duties.

Doug Larson

[DanDaffer]

Try this:

Run ‘svrnetcn.exe’

Add TCP/IP back into the list of enabled protocols and reboot.