No filereference returned from Repository for file: 773a4182-6787-4b0c-a9fd-fd9445947378.2018_07_30_10_51_40.868898DABBEC3FBB8D08.log. Unable to send filereference from slave-node to master

[Anonymous]

Dear Friends,

We have a qliksense site in our organization in which we have Central, Schedular and 2 proxy nodes. Since yesterday, all tasks were running fine. All of a sudden we strated getting below error message while running any task in QMC.

"No filereference returned from Repository for file: 773a4182-6787-4b0c-a9fd-fd9445947378.2018_07_30_10_51_40.868898DABBEC3FBB8D08.log. Unable to send filereference from slave-node to master"

We didn't made any changes to the environemnt. neither we have changes service account after first installation, nor the service account password is locked out. I logged in into the database and the app does exists there. The app does exists in root folder either. I searched the issue in qlik knowledge base but couldn't find any solution. If anyone have faced a similar issue in fast, any help would be much appreciated.

Cheers

Bibhu Sharma

[Levi_Turner]

Hey Bibhu,

This may be suggestive of something inconsistent in the underlying Repository Database at a first approximation, so I'd encourage creating a ticket with Qlik Support.

Hope that helps.

[balabhaskarqlik]

Check these:

https://community.qlik.com/thread/250728

https://community.qlik.com/thread/226191

https://community.qlik.com/thread/142797

May be:

Edit the rule ResourcesOnNonCentralNodes in Load balancing rules

from : ((node.iscentral="false" and resource.stream.id!="a70ca8a5-1d59-4cc9-b5fa-6e207978dcaf"))

to : ((node.iscentral="false" ))

Edit the data connections monitor_apps_REST_* 's connection strings to replace

from : localhost

to: servername

And reloads works fine!

https://community.qlik.com/message/1380381#1380381

[Anonymous]

Hi All,

Thanks for your time and input on this issue. This issue is resolved now. The issue was with storage on NAS drive. The storage was almost full and the environment became responsive as soon as we made free space available. This was an unexpected behavior from environment in a situation where root folder storage is exhausted. Rather I should say, error captured in logs are not at all relevant with actual issue.

Thanks for your inputs though.

Regards

Bibhu Sharma