You are viewing limited content. For full access, please sign in.

Question

Question

qf agent with error 9013

Quick Fields
Updated October 29, 2014
asked on October 17, 2014

HI, QF session ,when run via QF Agent ,processes/ stores documents in LF but ends with error 9013( permission denied). When QF session is manually processed via QF 9.0.0.460, all is ok ( no 9013 error).

QF Agent service has LOCAL SYSTEM as the service account and this account has full control of where the documents are processed from and where the documents are to be moved.

We did a procmon but only access denied is for regedit keys. There is nothing in Event Viewer ( applog/security/system).

I have attached the log from QF Agent ( logging was set at diagnostics-verbose).

 

ps: what is the protocol if there is similiar reported entry to LF Answers ?? Do I add to that or do I open a new question, like now?

 

Thanks Valerie


 

0 0

Answer

APPROVED ANSWER SELECTED ANSWER
replied on October 29, 2014

The issue was that in the Quick Fields session, the configuration for unidentified documents was still using Windows Authentication. After that was changed to Laserfiche Authentication, then the session ran fine in Quick Fields Agent.

0 0

Replies

replied on October 17, 2014 • Show version history

9013 is a Laserfiche error code so the "permission denied" message applies to Laserfiche security. What account is the Quick Fields session configured to use when storing documents into the repository? If it's using Windows Authentication, then when you run the session manually in Quick Fields, it's just using the account that you're logged into the PC as. However, in Quick Fields Agent, it would be using the service account, so Local System wouldn't have rights to the repository. You can try changing the Quick Fields Agent service account to a domain account that has rights to the repository.

1 0
replied on October 17, 2014

HI Alex, thanks for your quick reply.

I checked -all of the sessions are run under a Laserfiche Admin account created specifically for Quickfields. We use Laserfiche Authentication for this account and it has full admin priviledges

 

0 0
replied on October 17, 2014

Please open a support case so the matter can be more thoroughly investigated.
 

0 0
APPROVED ANSWER SELECTED ANSWER
replied on October 29, 2014

The issue was that in the Quick Fields session, the configuration for unidentified documents was still using Windows Authentication. After that was changed to Laserfiche Authentication, then the session ran fine in Quick Fields Agent.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...