You may have just upgraded from Simpana 8.x to Simpana 9 SP2 or later and installed the Exchange DA Client on your Windows 7 client (x64) or Windows XP. Outlook is x86 version and Simpana 9.x Outlook Addin (MSI).

The Commvault documentation Install Using AD Group Policies just tell you in the last sentence that you need permission to Galaxy.Ex2KMBDM.CVEAAddin key. That sounds like a bad joke as it does not explain that you cannot set this value with a GPO together with the installation GPO and also not with two GPOs ordered one after the other (what Support suggested). The setup removes all it's registry keys and reinstall them later (also on updates over existing versions). To apply the permissons on the registry keys and folder you need to reboot the machine after the setup has been completed. But the setup does not reboot itself as there have been no files in use that require a reboot. Now, try to explain this reboot requirements to a few hundred users...

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.

If you are running a Cacti EZ 0.6 based on CentOS 4.x inside a Hyper V Virtual Machine you will see that the machines system time runs out of sync, but you have configured NTP correctly.

Symtoms:

  • If Cacti EZ runs for about one hour and you may see a time difference of ~90 seconds to your NTP time.
  • "ntpdate -u ntp.example.com" command shows you differences to the current time whenever you execute it.

Solution:

title CentOS (2.6.9-100.EL.plus.c4smp) root (hd0,0) kernel /vmlinuz-2.6.9-100.EL.plus.c4smp ro root=LABEL=/ clock=pit initrd /initrd-2.6.9-100.EL.plus.c4smp.img

Sometimes you may have issues with the ShoreTel Communicator application and you need to find out what's going wrong behind the scenes. And there is a quick solution to extend the logging level. Please keep in mind the log files folder in %APPDATA%\ShoreWare Client\Logs may grow.

Enable debugging in Communicator is done with the following secret keys strokes:

  1. Focus curser in Enter you name or number field, where you normally enter the numbers for dialing
  2. Hold CTRL down and press F12
  3. A window opens with several debugging options.
  4. Enable what you need and close. Disable after you finished debugging.

We tried to access a remote webservice from a partner and they updated their certificate a few days ago. This request fails with an very unhelpful error message in ColdFusion.

Symptom:

  • ColdFusion CFHTTP is broken if you access a SSL site, but it worked in past.
  • ColdFusion CFDUMP says Connection Failure with I/O Exception: peer not authenticated

Analysis:

The very first idea was - there must be something wrong with the top level certification authority like a missing root certificate in the cacerts store that has not been integrated with Java in past. The root level certificate has been imported manually, but the error was still there. As you may expierenced yourself, ColdFusion is always very unhelpful if it comes to SSL errors. If you need more detailed information you need to go on the Java level. Here is an example code snippet you can run:

If you are installing a CommCell Console GUI on your Administrator PC it normally download and installs all patches from the CommCell Server to the client. You do not need to do anything manually, but with this bug these feature is more or less broken.

Symptoms:

  • CommCell Console GUI before 8.x SP4 is not installing patches on Windows XP at all.
  • CommCell Console GUI with 8.x SP4 installed fails to upgrade to SP5.
  • CommCell Console GUI starts up and update dialog is shown. After you press Yes for installing the patches, nothing at all happens and patches are not installed.

Reason:

  • Proper UAC (User Account Controll) logic implementation seems missing for Windows Vista and Windows 7 in Simpana 8.x and 9.x. By Microsoft certification rules the product is therefore not certified for Vista / Windows 7.
  • Auto-Upgrade often fails to install other required patches

Workarounds:

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:

This issue describes symptoms that occur for ages with HP Data Protector and that may become a critical issue for your if you don't see them. There will be no notification from DP at all if this happens. The main cause of these bugs seems to be very unreliable internally error handling process in Data Protector. I personally see this for many years now and nothing get's really better over time in these product if you don't stress your bugs.

Symptoms:

  • Job is running and cannot killed. You can try to kill it 1000 times and you can wait days for the kill, but it never get's killed.
  • Planned backup jobs with same job name are not running any longer as DP is waiting for the hanging job to finish.
  • Restarting all Data Protector services will not kill a job.

How to identify:

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:

Patch levelPatch description
DPWIN_00455Core Component
DPWIN_00456Cell Manager Component
DPWIN_00478Disk Agent
DPWIN_00460Media Agent
DPWIN_00457User Interface

Client SQL Server patch level: