Dollar Universe resources and NAS

[Yves Degauquier]

Hi,

We are currently facing some difficulties for using resources.

We have a node running on 6.10.91 on Windows, the server can view a folder on the NAS (\\company.com\folder1\folder2) but when configuring a resource on that folder it is not detecting the file we put on the folder. We checked that user access rights are OK.

We also mounted the NAS as I: drive but without success.

If we set the folder to a local disk, then the resource is ok.

Any experience or advice on dealing with resource on NAS?

Thanks in advance,

Yves

 

[Domenico Cotugno]

Hello @Yves Degauquier,

This is not an uncommon occurrence. It is generally cause by the process that supervises file-type resources, the EEP, not having permissions to the network location. You can change the startup of the Windows EEP service to use a domain user that has rights to the UNC path of your NAS. However, make sure to also make that domain user a local admin account so the EEP can also read local file resources. A limitation of this workaround is that if you have multiple network paths with different user permissions, the EEP can only be set to use 1 username. 

See here for more details:

Condition on file resource is not detected on network disk on Windows

I hope that helps!

Regards,

------------------------------
Domenico Cotugno
Tricise Automation
------------------------------

[Gilles deBuzonniere]

Hello Domenico,

There is a real issue behind this question: why is the resource checked by a single user account? If you consider the fact that the required resource will be used by the conditionned uproc, it would be more logical and simple to check the resource with the submission account of the uproc. The EEP service should ask to the windows service user to check the resource, or submit a check througth the same mechanism as the Launcher submit uprocs.

Regards,

Gilles.