Installing vCenter 5.5 – Database job was created by another user

Installation, vCentre Comments Off

I’m installing vCenter Server 5.5 on a Windows 2012 R2 server, using a SQL 2012 instance on another server, and have encountered this error:

Database job [Past day stats rollupWebbWorld] was created by another user.  Use the same user to setup your DSN or remove the job.  ODBC Error: [Microsoft][SQL Server Native Client 11.0][SQ Server] The specified @job_name (‘Past Day stats rollupWebbWorld’) does not exist.


After a bit of investigation I managed to locate this job which runs as part of the SQL Server Agent and remove it.  Here is how…

1. Open SQL Management Studio and connect to the appropriate instance

2. Expand the SQL Server Agent node and then expand Jobs

3. Right-click on the offending job and choose Delete


4. Click OK

5. Retry the vCenter Server installation

[BlogBookmark] [Blogsvine] [] [Digg] [Facebook] [Furl] [Google] [LinkedIn] [MySpace] [Reddit] [Slashdot] [StumbleUpon] [Twitter] [Windows Live] [Yahoo!] [Email]

Installing vCenter Server 5.5 – The DB user entered does not have the required permissions

Installation, vCentre Comments Off

I’m installing vCenter Server 5.5 on a Windows 2012R2 server (with SQL 2012 on a different server).  I’ve setup the DSN and now the installation fails with the following error:

The DB user entered does not have the required permissions needed to install and configure vCenter Server with the selected DB. Correct the following error(s):

The database user ‘vc_sql_serv’ does not have the following privileges on the ‘WebbWorld’ database:
EXECUTE sp_add_category
EXECUTE sp_add_job
EXECUTE sp_add_jobschedule
EXECUTE sp_add_jobserver
EXECUTE sp_add_jobstep
EXECUTE sp_delete_job
EXECUTE sp_update_job
SELECT syscategories
SELECT sysjobs
SELECT sysjobsteps


After  lot of playing around with permissions, and banging my head against the desk, I figured out that this message was a bit misleading, and I needed to change the permissions on the msdb database:

1. Open SQL Management Studio and log in to the appropriate instance

2. Expand Security -> Logins

3. Right-click the appropriate user and select Properties

4. On the User Mapping page grant db_owner rights


5. Click OK

6. Retry the vCenter Server installation

[BlogBookmark] [Blogsvine] [] [Digg] [Facebook] [Furl] [Google] [LinkedIn] [MySpace] [Reddit] [Slashdot] [StumbleUpon] [Twitter] [Windows Live] [Yahoo!] [Email]

An error occurred while consolidating disks

ESX, Troubleshooting, vCentre Comments Off

Having received an alert that I need to consolidate disks on a VM I proceeded to do so.  However, after an hour or so the operation failed with this message:

The maximum consolidate retries was exceeded for scsi0:1


I tried several times to consolidate the disks but it kept failing.  A Google search didn’t return many useful results but I did find that the following solution worked for me:

1. Take a snapshot of the VM (don’t snapshot the virtual machine’s memory)

2. Consolidate the disks

3. Remove the snapshot

4. Consolidate the disks

[BlogBookmark] [Blogsvine] [] [Digg] [Facebook] [Furl] [Google] [LinkedIn] [MySpace] [Reddit] [Slashdot] [StumbleUpon] [Twitter] [Windows Live] [Yahoo!] [Email]

Virtual machine disks consolidation is needed

ESX, ESXi, Maintenance, Troubleshooting Comments Off

This morning one of my VMs was reporting that virtual machine disks consolidation is needed, as shown in the screenshot below:


I believe this was caused by a Veeam backup job, as there was also a snapshot size warning, but no snapshot was present.  This was easy to fix:

1. Right-click on the VM, select Snapshot and then Consolidate

2. Click Yes

Depending on the size of the files this may take some time.


[BlogBookmark] [Blogsvine] [] [Digg] [Facebook] [Furl] [Google] [LinkedIn] [MySpace] [Reddit] [Slashdot] [StumbleUpon] [Twitter] [Windows Live] [Yahoo!] [Email]

Veeam Backup & Replication job failed with warning – vmdk size changed

Backups, Storage, Troubleshooting No Comments »

Yesterday I increased the size of a disk on a VM and today the backup job failed with a warning:

Disk [DataStore1] Server1/Server1.vmdk size changed.  Changed block tracking is disabled.

This was because I didn’t rescan the vCenter server within Veeam.  This is straight forward and only takes a few steps…

1. Open Veeam Backup & Replication

2. In the Virtual Machines section expand Infrastructure -> VMware vSphere

3. Right-click on the vCenter server and select Rescan


4. Click Close when the task is complete

[BlogBookmark] [Blogsvine] [] [Digg] [Facebook] [Furl] [Google] [LinkedIn] [MySpace] [Reddit] [Slashdot] [StumbleUpon] [Twitter] [Windows Live] [Yahoo!] [Email]