QlikView extractor tasks failing

[Susmit]

Dear Team,

We are recently facing a issue from the last week our extractor jobs are failing in QMC and server and sometimes it gets executed, we are concerned of this inconsistent behaviour.The error which we get is below:

File not found error

Cannot open file: '\\ww005.XXXX.net\meddfsroot\2_HQ\CRM_Analytics\PriMa\VALIDATION_(TEMP)\Debugging_Step1.csv'
System error: Create directory \ failed: Create directory \ failed: boost::filesystem::create_directory: A device attached to the system is not functioning: "\\ww005.XXX.net\meddfsroot\2_HQ\CRM_Analytics\PriMa\VALIDATION_(TEMP)": too many links

We are just extracting data over a network path, from .xlsx .csv and qvd files

Please help on this at the earliest as this is in production and we not able to distribute the reports to the users.

Regards,

Susmit

[marcus_sommer]

It looked that the specified files aren't available at the time of the access. This means the files aren't really there, they might be locked through any other process, any security tool/rule prevents the access and/or any network issues make the path temporary not accessible or leads to too slow responses respectively timeouts (in this regard you should also look for any proxies and load-balancers within your environment).

- Marcus

[Susmit]

Hi Marcus,

Thanks for the reply.

Proxies/firewall seems to be working fine, also the network team reported there are no drops in connections,can you update which security updates/rules can be causing this issue in the servers.Also is there any workaround for this or any thing we can do scriptwise to make it solved.

Are there any settings we can check that should enabled for this opertaion in server/app.

Regards,

Susmit

[marcus_sommer]

I don't think that there are any missing/wrong server settings causing the issue because if so it shouldn't be work at all. Therefore it are probably rather temporary disturbances which could be quite hard to detect.

Helpful would in each case be to look on the various log-files from Qlik and OS (at first I would look within the event-log) and all the network-parts to find any pattern and maybe also to use a network-sniffer like wireshark.

Another approach would be to check the exists of a file before you tries to load it. Maybe with something like filesize() within a loop with n iterations and by each FALSE result you sleep a second and in the end you may branch into any alternative action to avoid an error. Such measure might be also extended to find the reason behind it by checking if the folder/drives above exists and which access rights are there and so on. Per EXECUTE statements you may fire various batches for it. If the cause is really rather temporary the suggestion should solve your issue.

- Marcus