Microsoft SQL 2008 Agent not starts
I was playing around with VMware vSphere ESXi 4.1 & vCenter 4.1 together with Microsoft Windows Server 2008 & Microsoft SQL 2008. I can login to my vCenter and everything seems to be work perfectly. Due to certain reason, I have rebooted the Windows server and the incident happen. The VMware Virtual Center service and SQL Agent do not start. The VMware vCenter service is highly depending on SQL Services before it can startup.
The SQL agent event log show as example below:
Log Name: Application
Source: SQLAgent$SQL2008
Date: 10/9/2008 11:22:57 AM
Event ID: 103
Task Category: Service Control
Level: Error
Keywords: Classic
User: N/A
Computer: WIN2K8.local.planetmy.com
Description:
SQLServerAgent could not be started (reason: Unable to connect to server ‘WIN2K8\VCSQL2008′; SQLServerAgent cannot start).
Read more
Possibly Related Posts:
- How to add Dell PERC Drivers into VMware Converter Cold Clone ISO
- Top 10 Free Anti Virus
- VMware Workstation 7 Serial Key
- WP Contact Form III – You do not have sufficient permissions to access this page Error
- WP Cache Error “semget() failed: Permission denied” Solved
Basic vmware-cmd VM Management tips
Sometimes using a command line is much more faster than using GUI. Personally I found VMware Virtual Center always have bugs. The following article will guide you how to use vmware-cmd VM management tool for some basic VMware administrative tasks.
The figure below illustrates states, transitions, and state changing commands for virtual machines.
List path and names of registered VM guest vmx files on the present host
For an example:
# vmware-cmd -l
/vmfs/volumes/473ddda7-2a53d446-x25b-001aa0288d45/SLES9/SLES9.vmx
/vmfs/volumes/473ddd52-a6f731ac-3125-001aa0288d45/SLES10/SLES10.vmx
/vmfs/volumes/473dde07-d8a0f854-rqqa-001aa0288d45/WIN2K3-01/WIN2K3-01.vmx
/vmfs/volumes/473dde07-d8a0f854-eqqa-001aa0288d45/WIN2K3-02/WIN2K3-02.vmx
/vmfs/volumes/47f0819a-9f092588-548c-0015174a435a/WIN2K8-01/WIN2K8-01.vmx
/vmfs/volumes/473daqws-2a53d446-625x-001aa0288d45/WINXP-01/WINXP-01.vmx
VMware ESX provide basic power state options include:
Power on — Powers up the virtual machine and boots the guest operating system if the guest operating system is installed. How to power on VM guest using command line:
#/usr/bin/vmware-cmd /vmfs/volumes/473dde07-d8a0f854-rqqa-001aa0288d45/WIN2K3-01/WIN2K3-01.vmx start
Power off — Powers down the virtual machine. The virtual machine does not attempt to gracefully shut down the guest operating system. How to power off VM guest using command line:
#/usr/bin/vmware-cmd /vmfs/volumes/473dde07-d8a0f854-rqqa-001aa0288d45/WIN2K3-01/WIN2K3-01.vmx stop
Suspend — Pauses the virtual machine activity. All transactions are frozen until you issue a Resume command. How to suspend VM guest using command line:
#/usr/bin/vmware-cmd /vmfs/volumes/473ddda7-2a53d446-x25b-001aa0288d45/SLES9/SLES9.vmx suspend
Resume — Allows virtual machine activity to continue, and releases the Suspended state. How to resume VM guest using command line:
#/usr/bin/vmware-cmd /vmfs/volumes/473ddda7-2a53d446-x25b-001aa0288d45/SLES9/SLES9.vmx resume
Reset —Powers down the virtual machine and restarts it. How to reset VM guest using command line:
#/usr/bin/vmware-cmd /vmfs/volumes/473dde07-d8a0f854-rqqa-001aa0288d45/WIN2K3-01/WIN2K3-01.vmx reset
How to check VM guest power state
#/usr/bin/vmware-cmd /vmfs/volumes/473dde07-d8a0f854-rqqa-001aa0288d45/WIN2K3-01/WIN2K3-01.vmx getstate
Read more
Possibly Related Posts:
- How to add Dell PERC Drivers into VMware Converter Cold Clone ISO
- Top 10 Free Anti Virus
- How to Install Webmin on OpenFiler
- Microsoft SQL 2008 Agent not starts
- VMware Workstation 7 Serial Key
Thanks to VMware ESX 3.5 Update 2 Bug
I would like to thanks to VMware ESX 3.5 Update 2 BUG, it’s really make it busy today. Thanks god, it’s only happen to few of my VM guest and most of them are not mission critical machine.
Anyway, an official letter from VMware CEO Paul Maritz said about 2 failed.
- Not disabling the code in the final release of Update 2; and
- Not catching it in our quality assurance process.
I guess the person in charges have to responsible and probably someone may terminate. This is really a big mistake and we know how’s is the VMware quality control work.
Possibly Related Posts:
- How to add Dell PERC Drivers into VMware Converter Cold Clone ISO
- Microsoft SQL 2008 Agent not starts
- Basic vmware-cmd VM Management tips
- Veeam Backup 2.0 has been released
- VMware Infrastructure 3.5 Update 2 have been released
Veeam Backup 2.0 has been released
Less than five months after the first release, Veeam Backup 2.0 has been released!
The interesting features like:
- Real-time statistics and reports
- Support for VMware ESXi (free of charge)
- Support for Microsoft Volume Shadow Service (VSS) in Windows guest OSes backup
- Support for 3rd party tape backup devices
- Backup and replication combined
- Fast file-level recovery
- Database-consistent backup
Possibly Related Posts:
- How to add Dell PERC Drivers into VMware Converter Cold Clone ISO
- Microsoft SQL 2008 Agent not starts
- Basic vmware-cmd VM Management tips
- Thanks to VMware ESX 3.5 Update 2 Bug
- VMware Infrastructure 3.5 Update 2 have been released
VMware Infrastructure 3.5 Update 2 have been released
VMware have been released the Update 2 for ESX (build 103908) and VirtualCenter (104215).
This new version brings a number of important features including:
- Cross-processors VMotion (auto-configuration of AMD-V Extended Migration and Intel FlexMigration)
- Virtual machines live snapshot through Microsoft Volume Shadow Service (VSS) (only Windows 2003 and 2008 guest OSes)
- Virtual machines live cloning
- Virtual disks hot-extension (only for flat disks without snapshots in persistent mode)
- VMware HA support for individual virtual machines
- VirtualCenter alarms for physical servers health (single components supported)
- Manual computers addition in Guided Consolidation (by hostname or IP)
- Single Sign-On (SSO) on VirtualCenter client (capability to pass-through Windows authentication credentials, with support for smartcards and digital certificates)
- Support for Microsoft Windows Server 2008, Sun Solaris 10 U5, Novell SLES 10 SP2 and Ubuntu 8.04 guest OSes
- Support for 8GB Fibre Channel HBAs
- Support for NFS and iSCSI over 10Gbit Ethernet
- Support for Remote Command Line Interface (CLI) (no more experimental)
- 192 vCPUs per host – VMware now supports increasing the maximum number of vCPUs per host 192 given that the maximum number of Virtual Machines per host is 170 and that no more than 3 virtual floppy devices or virtual CDROM devices are configured on the host at any given time. This support is extended on ESX 3.5 Update 1 as well.
Possibly Related Posts:
- How to add Dell PERC Drivers into VMware Converter Cold Clone ISO
- Microsoft SQL 2008 Agent not starts
- Basic vmware-cmd VM Management tips
- Thanks to VMware ESX 3.5 Update 2 Bug
- Veeam Backup 2.0 has been released