Showing posts with label vmware. Show all posts
Showing posts with label vmware. Show all posts

Thursday, 10 July 2014

VMware Horizon View - Error occurred during vCenter operation.

Came across an annoying message and only possible fix I found was to recreate the pool. Thinking that is a bit extreme. When I edit other VMware View 5 Horizon pools no error messages. Rebooted vCenter and the View Connection server with no resolution and no errors in the event logs.

Nothing has changed on vCenter, datastores etc.. for months. The Parent VM and snapshots were all there.

Error Message (Editing a Pool):
"Error Occurred during vCenter operation."












Error Message (Save Pool Settings):
"Could not find the parent VM or snapshot"














Solution:

Select the affected pool, click EDIT, vCenter Settings tab.
For each of the Browse... options click browse and select the same object.
Once you have gone through all the steps click OK and now you can go back and edit the pool.























P.S. If you had to rebuild vCenter Server just refresh the pool and it will all be back to normal.

Friday, 9 May 2014

The Microsoft Exchange Information Store service terminated with service-specific error %%-2147221213.

Problem:

Exchange 2010 DAG has a very high copy queue length.

Non-active node can not start Microsoft Exchange Information Store Service or System Attendant Service.

System Event log error message:

The Microsoft Exchange Information Store service terminated with service-specific error %%-2147221213.
Event ID: 7024












Solution:

1. Make sure your Windows Time Service is running (optional)
2. Note the time difference between your current local clock and domain clock.
2. Run: cmd -> "net time /set" this will pull time from your local ADC site.
3. Shutdown the VM, do not power on.
4. Check the hypervisor clock to make sure it's correct and make sure that the guest VM does not sync time with the host.
5. Wait for the time to pass noted in step 2 and power on the VM.
6. Check Microsoft Exchange Information Store and System Attendant service should be running now.