Unable to synchronize the write cache with the medium

The technical support forum for Firestreamer (the virtual tape library).
Locked
hpetitjean
Posts: 4
Joined: 18 Nov 2011, 06:52

Post by hpetitjean »

jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Post by jsf »

C000020C is STATUS_CONNECTION_DISCONNECTED ("The transport connection is now disconnected"), which can also translate to ERROR_NETNAME_DELETED ("The specified network name is no longer available"). This error is reported by Windows, relates to your network share and has nothing to do with Firestreamer. See E002 for more info.
Best regards,
John Smith
Cristalink Support
hpetitjean
Posts: 4
Joined: 18 Nov 2011, 06:52

Post by hpetitjean »

Thanks for your fast reply.

Here is the thing, alf of the job ( 4 in total ) run great on the same support on lan ( Buffalo W raid ) also this pointed jobs runs great until .... we'v got this message.
All connection are green and the Buffalo is online with no connection erro at all.

how come it works for few days and then suddenly 2 jobs on 4 get this messages ..
jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Post by jsf »

Buffallo may have rebooted or reset the connection, or some Windows bug showed up, but the error came from Windows when Firestreamer attempted to write to or close the file. We can do nothing about it, sorry. You may want to google for "buffalo raid specified network name is no longer available" to see if somebody has an answer...
Best regards,
John Smith
Cristalink Support
hpetitjean
Posts: 4
Joined: 18 Nov 2011, 06:52

Post by hpetitjean »

jsf
Cristalink Support
Posts: 300
Joined: 29 Aug 2010, 09:03

Post by jsf »

I can assure you the error has nothing to do with Firestreamer or DPM, and "rebuilding libraries" won't help. Firestreamer makes no difference between local and network files and uses the same standard Windows API to access both. The error is returned by Windows and may be caused by the local hardware or network drivers, the remote machine that provides the network share, or the network infrastructure in between. It’s extremely hard to find the root cause without the internal knowledge of Windows. Only Microsoft can relatively easily tell what exactly caused that error code to appear. Even if you knew the exact cause of the error, and it was something like "the expected network packet wasn't received", then it'd only mean you'd have to dig further down. It may be easier to start replacing the related components one by one until the issue is resolved (I'd start with the NAS device). I am sorry, we cannot be more helpful.
Best regards,
John Smith
Cristalink Support
Locked