Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi all !
My today's question is about the Reload tab in QEMC. Into Document / User Documents / Reload, we can schedule some Reload task for documents.
When a document have a section access and i want to reload it each days, should i fill the section access part or not ? What is the purpose of this part ?
I'm Using QVS 9 SR5 (without publisher licence).
Thansk all !
Hello,
Those fields are used in case you want a different user than the one is running the service to reload the document. Although you have a section access in your document, you don't need to set this up to reload the document normally.
Regards.
Ok... It's what I'm thinking about..
So we don't fill this part.
But we notice that a document with section access finish with a failure status contrary to document without section access.
We don't undertand why...
You have two options when server reloading a section access document
There are other approaches, but I have tried both of these. Although I would recommend the first.
Remember that the user name should have ADMIN access.
Hope this helps
Jonathan
Hi,
Try checking the log (if it's not enabled, do it in your settings menu, document properties, general, it will be created in the same directory you have your document stored).
Try a manual reload to see whether that helps.
Manually the document has no pb to reload.
That's right, I finally realized that obviously is always going to work, since you has previously logged into your document with a user allowed to reload. I suggest Jonathan Dienst's solution posted above.
Hello Jonathan,
I agree with most, but I'd create a new user for reloading. I guess that ADMIN access depends on the security document configuration, as a user may be allowed to reload. Of course it may be disabled so only an admin user would be allowed.
Regards.
We will try the first one.
For the second, we already try to fill it with an ADMIN user of the section access. The result is failure.
Miguel
My 2c worth on this:
We use a dedicated windows service account for the QV server. This account has a strong, but unchanging password in active directory. It is included in a common section access script (which is in the hidden script) with ADMIN access. The users are athenticated using the NTNAME field. The common access script picks up the user names from a spreadsheet located in an access protected folder.
In our case, the reloads for the production models are not performed by the users. Of course, this does not apply to models created by the users that have not been moved to production, but then these are not reloaded by the server.
I don't really like username/password combinations as the passwords have to be stored somewhere in plain text, there is no enforcement of password policies and they need to be centrally administered.
Regards
Jonathan