topic Re: Task Failure - The specified network name is no longer available in QlikView

Task Failure - The specified network name is no longer available

bhelms — Mon, 26 Jan 2026 18:19:17 GMT

I need help to troubleshoot a failure we are getting randomly on our production server. Jobs will randomly fail and give the below error message. We don't see any errors in Event Viewer on the server other than what QlikView is providing. I don't beleive we are losing network connectivitiy to our NAS because other jobs run fine at the same time that some will fail. Immediately after the job fails it will run fine if we reload it, but can't always be watching the QEMC.

Email Error:

The task "" failed. Part of the log file follows:

7/22/2013 4:42:02 PM Error Exception=System.IO.IOException: The specified network name is no longer available.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count)

at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count)

at System.IO.StreamReader.ReadBuffer()

at System.IO.StreamReader.get_EndOfStream()

at QVBWrapper.Document.ReadDocumentLogThread(ILogBucket i_LogBucket, DateTime i_ReloadStartTime)

7/22/2013 4:42:02 PM Error Aborting Reload. Error=QDSMain.TaskResult

7/22/2013 5:01:21 PM Error Reload failed.

7/22/2013 5:01:21 PM Warning Document was forcibly closed. Clean close was not possible.

7/22/2013 5:01:21 PM Error Reload failed. Distribution skipped.

7/22/2013 5:01:21 PM Error The task "" failed. ErrorCount=4

Event Viewer Log:

Exception=System.IO.IOException: The specified network name is no longer available. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.ReadCore(Byte[] buffer, Int32 offset, Int32 count) at System.IO.FileStream.Read(Byte[] array, Int32 offset, Int32 count) at System.IO.StreamReader.ReadBuffer() at System.IO.StreamReader.get_EndOfStream() at QVBWrapper.Document.ReadDocumentLogThread(ILogBucket i_LogBucket, DateTime i_ReloadStartTime)

Re: Task Failure - The specified network name is no longer available

Bill_Britt — Tue, 23 Jul 2013 16:01:38 GMT

Hi,

To start QlikView does not support NAS storage devices. With that said, need ot look at you OS System and application event logs for errors and warning outside of QlikView. This would be caused my an DNS issue.

Bill

Re: Task Failure - The specified network name is no longer available

bhelms — Tue, 23 Jul 2013 16:12:00 GMT

I do not see any errors or warnings in the Event Viewer other than what QlikView is producing. I also assumed I would see something that would help me troubleshoot, but don't see anything.

This is not the first time that I have heard that QlikView doesn't support NAS/SAN drives. It does surprise me however. I can't immagine not using a NAS/SAN drive to hold the published documents. In a clustered environment, it is a fairly standard practice to not use local drives to ensure document uptime. Is there a solution that QlikView does recommend other than local drives?

Re: Task Failure - The specified network name is no longer available

Bill_Britt — Tue, 23 Jul 2013 16:28:25 GMT

Hi,

SAN's are supported, but not NAS.

Bill

Re: Task Failure - The specified network name is no longer available

Mon, 05 Aug 2013 09:15:25 GMT

Hi,

I'm Facing the same issue, and I'm also very surprised by the "NAS not supported" answer as all "local" Qlikteck guys we talked with, from "Consulting Services Director" to "Experts" exposed us the NAS solution as the only way to create distribution clusters.

What is the officially supported way to create a QDS Cluster and a Server cluster ?

Is there a keynote or something that states that NAS is not supported, so I could debate with those who have driven us to the NAS use ?

Thanks

Manu

Re: Task Failure - The specified network name is no longer available

Mon, 05 Aug 2013 11:31:45 GMT

Shared network storage is required for storage of QlikView applications that are needed in the cluster. It is recommended to host the storage of documents (

.qvw files) and .meta data on a Windows-based file share. QlikView Publisher supports a SAN (NetApp, EMC, etc.) that is mounted to a Windows Server 2003 (or later) and then shared from that server. Storage presented to a server via a SAN must appear as locally attached storage. If SAN storage is used for Publisher, any distributed data that is accessed by QlikView Server should not reside on the SAN storage.

The QlikView Distribution Services (QDSs) must have a shared application data directory and possibly a shared source document directory as well (hence the requirement for a shared network storage). All configured Publisher services must have reliable network access to the shared storage.

Re: Task Failure - The specified network name is no longer available

Alejandro_Hernández — Tue, 27 Aug 2013 11:35:44 GMT

Brian, were you able to solve this issue?

Re: Task Failure - The specified network name is no longer available

Wed, 04 Sep 2013 13:35:45 GMT

Hi Andreas,

Could you eloborate your quote a little? I don't see the point.

"If SAN storage is used for Publisher, any distributed data that is accessed by QlikView Server should not reside on the SAN storage."

Our Puplisher's do have its QVWs and QVDs stored on the very sam SAN-LUN-Windows-Share, that is used for the Server Cluster Document Root and even Accesspoint.

Why do you would you recommend otherwise? And how?

Re: Task Failure - The specified network name is no longer available

bhelms — Tue, 25 Feb 2014 18:47:37 GMT

I was never able to solve this issue and it has now begun appearing again. I can't figure out if it is an actual network/windows issue, or a QlikView issue. I can't find any logs in the event viewer that show a network disappearance and our network team assures us that there is no degradation from the network drive. If anyone has any new experiences with this, please let us know.

Re: Task Failure - The specified network name is no longer available

Wed, 28 May 2014 14:50:15 GMT

Hi Brian,

We are running into the same issue with the same error, we are on QlikView 11.2 SR2, with clustered environment, data is on clustered managed SAN space,

we opened a case with QlikTech.

so far, not any progress yet.

Re: Task Failure - The specified network name is no longer available

Bill_Britt — Wed, 28 May 2014 14:56:21 GMT

I would guess from what I have seen in the past, the share is not there when Qlik tries to locate it. This can be caused by a number of issues. All would be network related like DNS not responding with IP for host or wrong IP.

Bill

Re: Task Failure - The specified network name is no longer available

Tue, 17 Jun 2014 06:19:45 GMT

Any luck with this issue , we are facing similar issue since over a month now.

No network related reasons found.

Re: Task Failure - The specified network name is no longer available

Tue, 17 Jun 2014 06:23:15 GMT

Hello All,

Even we ran into same issue. QlikView 11.2 SR6, with clustered environment data is on clustered managed NAS.

No network related reasons found.

Thx,

Nisha

Re: Task Failure - The specified network name is no longer available

Bill_Britt — Tue, 17 Jun 2014 11:38:14 GMT

Hi,

NAS are not supported by Qlik.

Bill

Re: Task Failure - The specified network name is no longer available

Tue, 17 Jun 2014 14:38:59 GMT

Hello Bill,

We have a consultant from Qlik working on this and we have repeatedly raised this question about NAS being supported. But NAS is not an issue was the reply.

Thanks,

Nisha

Re: Task Failure - The specified network name is no longer available

Bill_Britt — Tue, 17 Jun 2014 15:43:15 GMT

Hi,

The below is a response from Product Management.

No, NAS is not supported from QDS (same as for QVS). This comes directly from Qlik Product Management and is applicable to QlikView 10, 11, and 11.2

Bill

Re: Task Failure - The specified network name is no longer available

Wed, 18 Jun 2014 07:01:14 GMT

Many thanks Bill.

I will check with our team.

Nisha

Re: Task Failure - The specified network name is no longer available

Wed, 18 Jun 2014 08:07:09 GMT

Hello Bill,

We have a windows server in between and not a direct HNAS setup. This issue is also weird as this error occurs at specific time of day between early morning 03:00 to 4:00 am load. The same loads run at 11:00 am and 07:00 pm the jobs run fine entire day.

Thanks,

Nisha

Re: Task Failure - The specified network name is no longer available

Bill_Britt — Wed, 18 Jun 2014 10:53:14 GMT

Hi,

Can you post you Task and Document logs for this task?

Re: Re: Task Failure - The specified network name is no longer available

Thu, 19 Jun 2014 05:14:21 GMT

Hello Bill,

Please find the Task log & Management Service Log. The Document log does not have any thing. It just stops at the point of this error.

Regards,

Nisha