Difference between revisions of "Virtual Centre"

Line 317:

* Caused by the SQL service being unavailable, therefore investigate why this is so.

If SQL is running on the same server, and the service failed after a reboot, its likely that its starting too quickly and SQL isn't ready. ~~Either,~~ make the service ~~automatically restart after X mins (good practise anyway)~~, ~~and/or~~ make the service ~~depend on SQL~~.

If SQL is running on the same server, and the service failed after a reboot, its likely that its starting too quickly and SQL isn't ready. For starters make the service depend on SQL and SQL Agent services, failing that, make the vCentre service start in a delayed fashion.

To make the VirtualCentre Server service depend on the SQL service

# Find the name of the SQL service

#* Find the MSSQL ~~key~~ in the following hive ~~(will probably be MSSQL, MSSQL$SQLEXPRESS, etc)~~

#* Find the MSSQL and SQLAgent keys in the following hive

#* <code> HKLM\System\CurrentControlSet\Services </code>

#* Could be be MSSQL, MSSQL$SQLEXPRESS, or if you've used a named instance, something like MSSQL$VIM

# Make VC service dependant on it

#* Browse to <code> HKLM\System\CurrentControlSet\Services\vpxd </code>

#* Add the name of the SQL service to the <code> DependOnService </code> value (there must be a blank line at the end still)

Interaction between vCentre and SQL can be quite poor when it comes to its start-up behaviour...

* SQL tends to report itself as started, despite the fact that it hasn't made its database instances available yet.

* vCentre will try to connect to SQL, then fail if it can't get in straight away

...meaning that you end up being reliant the vCentre service restarting in order for it to be able to connect and start up - which is far from ideal for normal operation.

=== Virtual Machine won't export ===

@@ Line 317: / Line 317: @@
 * Caused by the SQL service being unavailable, therefore investigate why this is so.
-If SQL is running on the same server, and the service failed after a reboot, its likely that its starting too quickly and SQL isn't ready.  Either, make the service automatically restart after X mins (good practise anyway), and/or make the service depend on SQL.
+If SQL is running on the same server, and the service failed after a reboot, its likely that its starting too quickly and SQL isn't ready.  For starters make the service depend on SQL and SQL Agent services, failing that, make the vCentre service start in a delayed fashion.
 To make the VirtualCentre Server service depend on the SQL service
 # Find the name of the SQL service
-#* Find the MSSQL key in the following hive (will probably be MSSQL, MSSQL$SQLEXPRESS, etc)
+#* Find the MSSQL and SQLAgent keys in the following hive
 #* <code> HKLM\System\CurrentControlSet\Services </code>
+#* Could be be MSSQL, MSSQL$SQLEXPRESS, or if you've used a named instance, something like MSSQL$VIM
 # Make VC service dependant on it
 #* Browse to <code> HKLM\System\CurrentControlSet\Services\vpxd </code>
 #* Add the name of the SQL service to the <code> DependOnService </code> value (there must be a blank line at the end still)
+Interaction between vCentre and SQL can be quite poor when it comes to its start-up behaviour...
+* SQL tends to report itself as started, despite the fact that it hasn't made its database instances available yet.
+* vCentre will try to connect to SQL, then fail if it can't get in straight away
+...meaning that you end up being reliant the vCentre service restarting in order for it to be able to connect and start up - which is far from ideal for normal operation.
 === Virtual Machine won't export ===

Difference between revisions of "Virtual Centre"

Navigation menu

Search