Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

766

March 28th, 2006 12:00

Fetch Aborted w/status 4352

While reviewing the DX logs, I found several occurances of the following message:
...(5960) Fetch for file ... was aborted with status 4352.

I'm able to bring up the files ok, and verified they were sucessfully copied to the centera. The error lookup mentions ERROR_REMOTE_STORAGE_MEDIA_ERROR. How can I tell what might have caused this?

Thanks!!

397 Posts

March 29th, 2006 20:00

The DX box may have intermittent issues talking to the centera. Try to enable logging to isolate the issue. I've pasted a kb article below:

Subject: How to Enable the EMC Centera SDK Trace logs
Symptom: How to enable the EMC Centera SDK tracing
Fix: EMC Centera has SDK logging that can show all communications and activity on an EMC Centera from an Application server like DiskXtender. This information may be useful to diagnose an issue on the Centera.

There are two levels of logging that can be enabled, Debug and Error. The Debug logs are verbose and can grow in size very quickly. The Error logs only have error messages and will not be as significant in size.

The SDK logging can be initialized by adding the following System Variable from within a Windows Application server:

Start-->Control Panel-->System-->Advance Tab-->Environment Variables):
Variable name:FPLIBRARY_LOG_FILE_DEBUG
Variable value:c:\test.log
Or
Start-->Control Panel-->System-->Advance Tab-->Environment Variables):
Variable name:FPLIBRARY_LOG_FILE_ERROR
Variable value:c:\test.log

Set the variable value to a path that has sufficient space to store the SDK log.
Restart the application services to activate the logging. You'll notice the test.log file growing in size while the application is running.

Do not leave the logging enabled or it may consume all of the free drive space in the path that is set. To disable it, remove the configured system variable shown above and restart the application services.
No Events found!

Top