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

Question

Question

Format of the URI could not be determined.

Workflow
Updated June 1, 2018
asked on May 20, 2016

Workflow has two conditions: 

Workflow doesn't kick off when the file is sent to Supply Request and sends this message in the 

LFNotificationService

 

 

Invalid URI: The format of the URI could not be determined.

Stack Trace:
Caught exception: System.UriFormatException
Message: Invalid URI: The format of the URI could not be determined.
   at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
   at System.Uri..ctor(String uriString)
   at Microsoft.AspNet.SignalR.Client.Http.DefaultHttpClient.Get(String url, Action`1 prepareRequest, Boolean isLongRunning)
   at Microsoft.AspNet.SignalR.Client.Transports.TransportHelper.GetNegotiationResponse(IHttpClient httpClient, IConnection connection, String connectionData)
   at Microsoft.AspNet.SignalR.Client.Transports.AutoTransport.GetNegotiateResponse(IConnection connection, String connectionData)
   at Microsoft.AspNet.SignalR.Client.Transports.AutoTransport.Negotiate(IConnection connection, String connectionData)
   at Microsoft.AspNet.SignalR.Client.Connection.Negotiate(IClientTransport transport)
   at Microsoft.AspNet.SignalR.Client.Connection.Start(IClientTransport transport)
   at Laserfiche.SignalR.Client.LFHubProxy.Connect()
   at Laserfiche.SignalR.Client.Factories.LFHubProxyFactory.Create(HubEndPoint hubEndPoint)
   at Laserfiche.PushNotificationService.Master.Services.RegisterService.Register(PushServiceRegisterRequest registerData)
   at Laserfiche.PushNotificationService.Master.PushNotificationService.Register(PushServiceRegisterRequest registerData)
   at SyncInvokeRegister(Object , Object[] , Object[] )
   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage41(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage4(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage3(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage2(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage11(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage1(MessageRpc& rpc)
   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
 

0 0

Answer

SELECTED ANSWER
replied on May 24, 2016

Glad it's fixed. You probably should still take a look at the Notification Service settings on the Forms Configuration page to clear that "Invalid URI" error up.

2 0

Replies

replied on May 23, 2016

The Notification system is part of Forms, not Workflow. Workflow never touches that service. What do you see in the Subscriber's trace when the event is evaluated?

1 0
replied on May 24, 2016

The Subscriber's trace is completely empty actually.  

0 0
replied on May 24, 2016

Anything of note in the repository tab in the Subscriber Trace? It's probably best you take it to Tech Support at this time since sorting it out will probably involve double-checking configurations and logs.

1 0
replied on May 31, 2018

Hello Miruna,

 

Where are the Subscriber Traces located?

 

Also- How do you accomplish this- You probably should still take a look at the Notification Service settings on the Forms Configuration page to clear that "Invalid URI" error up.

 

Thanks,

Jeff

0 0
replied on June 1, 2018

See the help file for Subscriber Trace

The Notification service can be configured in the configuration page for Forms:

0 0
replied on May 24, 2016

I reran the workflow config for connecting to the subscriber to see if that can rebuild the connection.  I'm getting information through now.  Not sure how it broke connection.  The workflow is working as intended now.

0 0
SELECTED ANSWER
replied on May 24, 2016

Glad it's fixed. You probably should still take a look at the Notification Service settings on the Forms Configuration page to clear that "Invalid URI" error up.

2 0
replied on May 25, 2016

The error happens when I click on a task as a user in forms. It opens the Form in another window and that's when the error happens.  This is within Chrome. And also Explorer.

 

0 0
replied on May 25, 2016

Right, the notification service is responsible for getting counts of tasks and keeping the numbers updated in the Inbox. If it's working, you'd see little numbers next to the "My Tasks"/"Available" tabs. If it's not, you wouldn't see anything (errors would be logged to the browser's dev tools, but not shown to the user).

0 0
replied on May 25, 2016

Reconfigured and checked the Notification Service Settings.  testing it looks like the error is cleaned up after a restart of the service.  Thank you.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...