Fail

If you shutdown a VM and you cannot restart it again this might be caused by Read Only Domain Controller (RODC).

If you may seen an error message that a VM cannot start with error code 0x80070569 check if the site the VM is running on has an RODC only. If this is the case you may missed to add the new VM to the "Allowed RODC Password Replication Group" of this site. The error 0x80070569 point to a Logon Failure per https://learn.microsoft.com/en-us/troubleshoot/windows-server/virtualization/starting-or-live-migrating-hyper-v-vms-fails.

Search on the Hyper-V host for System Eventlog for ID 5723 and you may see the VM machine name is not trusted by the local RODC server. Also search Hyper-V-VMMS > Admin eventlogs for event ID 15500 to find error code 0x80070569.

Now add the VM machine name into your "Allowed RODC Password Replication Group" and reboot the RODC and VM. When it comes up again the machine account will be cached locally on RODC and you can start/stop the virtual machine successfully.

We just installed Windows 2016 CORE. As recommened you typically should install all available Windows Updates before you move forward and install other software.

When we started to install Commvault File Agent and Virtual Server Agent setup failed with errors in eventlog and never completed. If you search Application event log you will find two errors logged:

Log Name: Application
Source: .NET Runtime
Date: 8/3/2017 3:59:44 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HOST1.example.local
Description:
Application: setup.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception

If you are running Simpana 9.0 SP2a and you backup Windows 2003 servers they are no longer backed up after you have installed SP2a. There is no notice or warning at all. You will not get an email if the job has failed to backup your data. Hopefully you have no data loss before you came aware of this bug...

Symtoms:

• Windows 2003 machines are not backed up. Windows 2008 or Windows R2 is not affected.
• Alert system does not notify you about the data backup failure.
• It does not matter if you use VSS or not.
• It does not matter if you have selected some files or all files for backup.
• Only the Commvault Jobs folder and SystemState is backed up.

Solution:

If you's like to install software via Active Directory it may fail with Error: %%1274.

Symtoms:

• You can reboot as often as you'd like and your deployed Software always fails with Error %%1274
• Eventlog entry:
  • Source: Application Management Group Policy
  • Event ID 101
  • Description: Die Zuweisung der Anwendung ShoreTel Communicator 16.23.5631.0 der Richtlinie ShoreTel Communicator ist fehlgeschlagen. Fehler: %%1274
  • Description: The assignment of application ShoreTel Communicator 16.23.5631.0 from policy ShoreTel Communicator failed. The error was : %%1274

Workaround:

• Explicitly set the policy Startup policy processing wait time: Activated Amount of time to wait (in seconds): 120s. This is normally not required if FastLogonOptimization is disabled, but Windows 7 seems to have a bug here.

History:

• 04/09/2011: Exists in Windows 7 RTM and SP1
• 13/04/2011: Implemented Activated Amount of time to wait workaround.

Mid January 2011 we found a bug in Commvault's Exchange Public Folder Archiver. This bug prevented us from restoring items that have been archived in past. It was a bit random, but my feeling was it is related to mails with attachments. As always supposed, it was not an issue of the MAPI connection configuration or other issues on our side. This is a Commvault bug and nothing else.

Required:

• Commvault Simpana 8.x
• Commvault Simpana 9.x

Symtoms:

• Archived public folder items cannot restored.
• Mails with attachments have mostly failed.
• User received very unspecific error message from Commvault Archiver Add-on in Outlook.

Solution:

If you are one of the HP DataProtector 6.11 customers and you have scheduled MsSQL transaction log and full backup to start simultaneously you will experience the below issue. We found this after an upgrade to latest 6.11 in November 2010 and a hotfix was build for us on 19. November 2010. We are running with this patch for 8 weeks successfully.

Cell Manager patch level:

Client SQL Server patch level: