FILE SYSTEM NOT AVAILABLE

Using (or providing) components based on the "Win32" framework

FILE SYSTEM NOT AVAILABLE

Postby quant36 on Thu Apr 13, 2017 5:11 pm

We are running Windows and three weeks ago we replaced our main network drive with a new one. Ever since we did that, our virtual server whose job is to kicks off a few APL processes after hours, started running into "FILE SYSTEM NOT AVAILABLE" error several times a week as it reads/writes to our new network storage. The after-hours network traffic in our office is very light and we eliminated all anti-virus/backup operations during the server's APL jobs, but the problem still persists.

According to Daylog APL Version 13.1 User Guide (page 286), "In a PC network, or in a single-processor Unix environment, if the FSCB file is missing or inaccessible (restricted access permissions) the report FILE SYSTEM NOT AVAILABLE (Error code 28) will be given. The same error will occur under NFS if the aplfscb "daemon" is not running.”

Has anyone encountered this error before and could share solutions?
Any links that would shed some light on what aplfscb daemon is?
Actually, any thoughts are welcomed at this point since standard monitoring tools haven't shown anything unusual.

Thanks,

Andrew Chou
Jennison Associates LLC
quant36
 
Posts: 1
Joined: Fri Feb 26, 2010 6:25 pm

Re: FILE SYSTEM NOT AVAILABLE

Postby Vince|Dyalog on Tue Apr 18, 2017 12:33 pm

We are corresponding with Andrew via email as well.

I have moved this topic to the Windows forum.

Regards,

Vince
Vince|Dyalog
 
Posts: 236
Joined: Wed Oct 01, 2008 9:39 am


Return to Windows: GUI, COM/OLE/ActiveX

Who is online

Users browsing this forum: No registered users and 0 guests