KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : CA XOsoft File Synchronization scenario yields error "Unable to query the status of the last asynchronous operation. The caller is out of memory or other system resources. (0x8007000e)"

Last Update: 2015-12-15 22:09:54 UTC

 

Document ID:    TEC521340
 
Title:  CA RHA File Synchronization scenario yields error 'Unable to query the status of the last asynchronous operation. The caller is out of memory or other system resources. (0x8007000e)'

Description:

Unable to query the status of the last asynchronous operation. The caller is out of memory or other system resources. (0x8007000e).

Solution:

When running a CA XOsoft scenario using File Synchronization, Microsoft VSS Snapshot technology is leveraged during the initial synchronization process. The advantage to this is that user access to root directories will not be affected when a scenario is started.

If the VSS Snapshot fails during the file synchronization process, XOsoft will revert to a file system scan which will temporarily disable access to any root directories defined within the scenario to protect data integrity.

If you are using File Synchronization and user's are reporting issues accessing the server's shares then most likely there is a problem with VSS.

The following error indicates a lack of system resources are available for a VSS Snapshot to be completed:

Unable to query the status of the last asynchronous operation. The caller is out of memory or other system resources. (0x8007000e)

The applicable real world limit for VSS on a 32 Bit OS is a volume not greater than 5TB.

256MB is the maximum available nonpaged pool memory available for a 32 bit OS with 4GB or memory and no /3GB switch (with /3GB defined this number drops to 128MB).

A 5TB volume consumes 200 MB of nonpaged pool memory during the snapshot creation phase and then drops to using 40 MB after that. Using the 32-bit Operating System, and a 5TB volume, VSS will consume 200 MB of the nonpaged pool memory (even more), and other applications will also consume some of the nonpaged pool memory, which will together exceed the maximum of the nonpaged pool memory limitation of 256MB.

The resolution for this issue would be to create smaller volumes which are less than 5TB, or move to a 64 bit platform where nonpaged pool memory can use up to 128 GB depending on configuration and RAM.

You can also review the following articles from Microsoft articles for more information about how VSS Snapshots scale:

http://technet2.microsoft.com/windowsserver/en/library/2de5c6af-f6a4-4ea0-8b78-df153663f6ed1033.mspx?mfr=true

and

http://msdn.microsoft.com/en-us/library/aa366778%28VS.85%29.aspx.

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments