dbo.VPX_HOST_VM_CONFIG_OPTION & ‘VIM_VCDB’ because the ‘PRIMARY’ filegroup is full


Error:
Vcenter service stops frequently or Unable to login through VIClient.

Event-ID: 1105

Could not allocate space for object ‘dbo.VPX_HOST_VM_CONFIG_OPTION’.’PK_VPX_HOST_VM_CONFIG_OPTION’ in database ‘VIM_VCDB’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

RootCause: This error due to limitation size in log file growth in SQL and we need to clear unwanted files in the log file to reduce the size.

Solution:

1.Download and install the Microsft SQL Server Management Studio Express.

2. Connect to ServernameSQLEXP_VIM and login with Windows Authentication.

sqlserver-authentication

 

 

 

 

 

 

3. Expand databases > Expand VIM_VCDB > Expand Tables > Open table dbo.VPX_PARAMETER:

2-vimcdb-vm-table-modify

 

 

 

 

 

 

4. Modify event.maxAge to a be 30 > Modify event.maxAgeEnabled to value of true

4-vm-table-event-max-true-setting

 

 

 

 

 

 

5. Modify task.maxAge to be 30 > Modify task.maxAgeEnabled to a value of true

2-vimcdb-vm-table-modify-taskmax-aged-current

 

 

 

 

 

 

5-task-max-enabled-true

 

 

 

 

 

 

6. Then run the built in stored procedure: from the VCDB > Programmability > Stored Procedures

Right Click dbo.cleanup_events_tasks_proc and click “Execute Stored Procedure”

6-execute-cleanup-from-table

 

 

 

 

 

 

7. This will purge the data from tables: vpx_event, vpx_event_arg and vpx_task based on the date specified for maxAge.

executeprocedure

 

 

 

 

 

 

 

 

8. When this has sucessfully completed, close the SQL Management Studio down > Then start the VMware Virtual Centre Server service

9. If you are getting error on the Step 7 (“Right Click dbo.cleanup_events_tasks_proc and click “Execute Stored Procedure””)

7-sql-log-file-full

 

 

 

 

 

 

10. Increase the log file size as mentioned in the below screen shot

a. Right click on the VIM_VCDB and go to properties

8-sql-log-full-solution-1-properties

 

 

 

 

 

 

 

 

 

b. Select the log “File type” option as highlighted

8-extend-log-file-growth

 

 

 

 

c. Extend the log file growth as mentioned

9-extend-sql-log-file-growth-2gb

 

 

 

 

 

d. Now the solved Output of the Step7. “”Right Click dbo.cleanup_events_tasks_proc and click “Execute Stored Procedure””

 

10-table-cleanup-solved

 

 

 

 

 

 

Ref article: http://www.petenetlive.com/KB/Article/0000479

 

 

 

Advertisements

Disk Consolidation Needed – Unable to access file since it is locked


If any backup running on your VM it will create a snapshot and after completion the snapshot will get removed. Sometimes it requires disk consolidation for the VM.

When we try to do disk consolidation of the VMDKs manually by right clicking on the VM and selecting Snapshot –> Consolidate.

However the consolidate operation may fail again, if the issue which caused the snapshot deletion operation to fail disk consolidation previously has not been cleared and shows an error “Unable to access file since it is locked”

VM-Consolidation1

 

 

VM-Consolidation-error1

 

I manually tried the scenarios like create another snapshot by switching off the VM and delete the snapshot manually for consolidation of VM disk and remove the VM from inventory and reregister the VM in the Vcenter which is also weird.

 

Solution:-

  1. From the VM summary identified the ESXI and do SSH login.

2. Ran the command “vmkfstools -D /vmfs/volumes/yourvolume/yourVM/yourlockedVM.vmdk

3. I could see the owner of the vmdk file which had the lock with MAC address ending “008ed

# vmkfstools -D /vmfs/volumes/VM_BLOCK_LUN0_VNX5200/VM server Folder/VM-

flat.vmdk

Lock [type 10c00001 offset 49518592 v 15, hb offset 3276800

gen 9, mode 1, owner 561795d7-66ffccd8-782c-b82a72d008ed mtime 797087

num 0 gblnum 0 gblgen 0 gblbrk 0]

Addr <4, 54, 3>, gen 4, links 1, type reg, flags 0, uid 0, gid 0, mode 600

len 107374182400, nb 102400 tbz 44371, cow 0, newSinceEpoch 102400, zla 3, bs 1048576

 

  1.  This is the ESXi server which has the lock on the VMDK file.
  2.  Next locate which ESXi host has a network adaptor with that MAC address.

 

  1.  Once confirmed I placed the host in maintenance mode, DRS vMotioned all VMs to another host in the cluster and restarted the hostd service or restart the server.

Syntax: #/etc/init.d/hostd restart

7. After restarting the host I can able to do consolidation of disk successfully and also storage migration.

“The VMRC console has disconnected…attempting to reconnect”


Error: “The VMRC console has disconnected…attempting to reconnect” unable to do open console for the VM.

vmrcconsoleissue

 

 

 

 

 

 

 

 

Solution:

  1. Exit your vsphere client
  2. Open your Task Manager (many ways to do this)
    1. Ctrl-Alt-Del -> Choose “Start Task Manager”
    2. Start -> Run -> Cmd and type “taskmgr.exe”
      or
    3. Right-click the clock, in the pop up menu choose “Start Task Manager”
  3. Look for any vmware-vmrc.exe process(es). Select it, then click “End Process”
  4. Restart vsphere client

 

vmrcconsoleissue-vmware-vmrc-taskmgr

An error was detected on device \Device\Harddisk1\DR1 during a paging operation.


Error in VM:

Event log error-id: 51

Error message “An error was detected on device \Device\Harddisk1\DR1 during a paging operation.”

In the backup error log “It was not possible to create volume snapshot for ‘E:\’. System error: ‘QueryStatus() failed’.”

 

Cause: Microsoft provides hot fix for the VSS issue for windows 7 and Windows2008r2 which was not installed.

Solution: Install the two hotfix provided by Microsoft

1.       Windows6.1-KB975688-x64.msu

2.       Windows6.1-KB976099-x64.msu

Patch download url : https://www.dropbox.com/sh/m3lca0905tnt5fe/GbJ5bOZ1cz

http://support.microsoft.com/kb/975688/en-us

http://support.microsoft.com/kb/976099/en-us

This solves the problem.

Unable to source /lib/lsb/init-functions cannot proceed vcloud director vmware


Error: Unable to source /lib/lsb/init-functions cannot proceed vcloud director vmware

Cause: Prerequisite library files not installed on Linux os.

Solution: Install redhat-lsb application; (eg.) # yum install redhat-lsb –y

Ref: http://help.digipower.vn/questions/296/install+vCloud

One more prerequisite of vcloud installation is apache service should be stopped or not to be installed on the Linux OS; other wise even after the successful installation of Vcloud director the webpage will not be displayed due to vmware-vcd service not binding to port 80.

While taking snapshot it gives an error another task is already in progress.


Error: Unable to migrate one host to another host and while taking snapshot it gives an error another task is already in progress.

Cause: VM Tools task is running on a particular VM which is not successfully completed.

Resolution: Identify the VM and kill the VMTools installation or upgradation process as shown in the figure below.
This solves the problem.

vmtools-blog

 

call datacenter.queryconnectioninfo for object test on vcenter server


Error: When you delete a cluster  in vCenter with out removing host you will be face an error “Call “Datacenter.QueryConnectionInfo” for object “Datacenter Name” on vCenter Server “vCenter server name” failed.

Cause: We should not remove cluster abruptly while hosts are configured to cluster.

Solution:

1. Enter the host in maintenance mode which are not connected to vcenter server.

2. Then add the host in the vcenter server.

3. Exit the maintenance mode.

4. Then reconfigure cluster, if you abruptly removed or check with your requirements for cluster to those hosts.