19 Posts

May 3rd, 2011 08:00

It has been my experience that this is a client error.  9 out of 10 times a simple client reboot fixes it.

41 Posts

May 3rd, 2011 08:00

Hi,

Is this error related to networker or the other application on the client machine.

Pratapsimha M P

Data Protection l2

ITO DO India Cluster – Assigned to Pfizer

HP Enterprise Services

Telephone +91 80 2611 2240

Mobile +91 9740 966 855

Email :pratapsimha.mp@hp.com pratapsimha.mp@pfizer.com

HP Avenue, Electronics City, Hosur Road, Bangalore, India

24 x 7 Support Contact Info:

Via Email, please send an E-mail to Group Mailbox: Pfizer.backup@hp.com

Via Phone, please contact Team Mobile : 91-9740-966-855 | Service Desk: 1-877-733-4357

1 Attachment

19 Posts

May 3rd, 2011 08:00

We find that the memory is not availabel, that we cannot touch the registry because it is locked, or that the system disk is full.  The latter creates a similar but different message.  We do not have time to do an in-depth analysis.

If a simple restart of the group does not fix it, we then  move on to checking system disk space, if there is space available we immediately request a reboot in the next maintenace window.

41 Posts

May 3rd, 2011 09:00

Ok thanks for the reply and suggestion will let you know the status

Pratapsimha M P

Data Protection l2

ITO DO India Cluster – Assigned to Pfizer

HP Enterprise Services

Telephone +91 80 2611 2240

Mobile +91 9740 966 855

Email :pratapsimha.mp@hp.com pratapsimha.mp@pfizer.com

HP Avenue, Electronics City, Hosur Road, Bangalore, India

24 x 7 Support Contact Info:

Via Email, please send an E-mail to Group Mailbox: Pfizer.backup@hp.com

Via Phone, please contact Team Mobile : 91-9740-966-855 | Service Desk: 1-877-733-4357

1 Attachment

4 Operator

 • 

14.4K Posts

May 5th, 2011 05:00

It is VSS subsystem which reports this error on the client.  Available memory is not enough to complete snapshot operation.  Restarting group will unlikely address this as usually whatever took memory won't give it back (in other words, there is more chance this is extreme situation than normal).  So, I would go for restarting the client machine.

No Events found!

Top