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

Question

Question

Unable to access Forms from Workflow

asked on October 10, 2016 Show version history

Hello, When attempting to connect to Forms from Workflow -- both version 10.1 -- we are receiving a (401) Unauthorized error. Forms and Workflow are installed on separate machines, and the the event viewer log on the Forms machine lists it as a "HTTP Status Code: 500" error from /Forms/api/BusinessProcess/Listing.

Here is the full event log:

An unexpected error has occurred. [LFF502-UnexpectedError]

Details: URL: /Forms/api/BusinessProcess/Listing

Error: UnexpectedError

Date: 10/10/2016 10:56:53 AM (Eastern Standard Time)

HTTP Status Code: 500

User:

IP: 192.168.11.1

Stack Trace: Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException

Message: An unexpected error has occurred. [LFF502-UnexpectedError]

Inner exception: System.ServiceModel.FaultException Message: Access is denied. at System.ServiceModel.Dispatcher.AuthorizationBehavior.Authorize(MessageRpc& rpc) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc) at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)

The strange thing is that this was working last week, not sure what went wrong but we started receiving this message late on Friday, still unable to resolve it.

This project is not live yet, we're still testing, so a setting must have gotten altered, but we are at a loss as to what it could be.

Any ideas?

 

Thanks

0 0

Answer

SELECTED ANSWER
replied on October 10, 2016

Please check whether the Forms site in IIS has Windows Authentication enabled as this post. Also please confirm from Forms configuration page and check the workflow server on Laserfiche tab are correctly configured.

0 0

Replies

replied on October 11, 2016

Thank you! I had an alternate version of the workflow server name entered in the Forms settings, which apparently was the source of my problem.

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

Sign in to reply to this post.