Installing Mobile Server

asked on November 3, 2020

when loading main web page: http://localhost/mobile/configuration.aspx

Invalid URI: The format of the URI could not be determined.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UriFormatException: Invalid URI: The format of the URI could not be determined.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:



[UriFormatException: Invalid URI: The format of the URI could not be determined.]
   System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) +261
   Laserfiche.WebAccessMobile.Formex.get_HostName() +39

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) +0
   System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) +122
   System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) +231
   System.Web.SecurityUtils.MethodInfoInvoke(MethodInfo method, Object target, Object[] args) +194
   System.Web.Script.Serialization.JavaScriptSerializer.SerializeCustomObject(Object o, StringBuilder sb, Int32 depth, Hashtable objectsInUse, SerializationFormat serializationFormat) +636
   System.Web.Script.Serialization.JavaScriptSerializer.SerializeValueInternal(Object o, StringBuilder sb, Int32 depth, Hashtable objectsInUse, SerializationFormat serializationFormat, MemberInfo currentMember) +1837
   System.Web.Script.Serialization.JavaScriptSerializer.SerializeValue(Object o, StringBuilder sb, Int32 depth, Hashtable objectsInUse, SerializationFormat serializationFormat, MemberInfo currentMember) +262
   System.Web.Script.Serialization.JavaScriptSerializer.SerializeEnumerable(IEnumerable enumerable, StringBuilder sb, Int32 depth, Hashtable objectsInUse, SerializationFormat serializationFormat) +199
   System.Web.Script.Serialization.JavaScriptSerializer.SerializeValueInternal(Object o, StringBuilder sb, Int32 depth, Hashtable objectsInUse, SerializationFormat serializationFormat, MemberInfo currentMember) +1674
   System.Web.Script.Serialization.JavaScriptSerializer.SerializeValue(Object o, StringBuilder sb, Int32 depth, Hashtable objectsInUse, SerializationFormat serializationFormat, MemberInfo currentMember) +262
   System.Web.Script.Serialization.JavaScriptSerializer.Serialize(Object obj, StringBuilder output, SerializationFormat serializationFormat) +46
   System.Web.Script.Serialization.JavaScriptSerializer.Serialize(Object obj, SerializationFormat serializationFormat) +106
   Laserfiche.WebAccessMobile.ConfigurationPageService.GetFormlist() +807
   ASP.configuration_aspx.__Render__control2(HtmlTextWriter __w, Control parameterContainer) +1628
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +117
   System.Web.UI.HtmlControls.HtmlHead.RenderChildren(HtmlTextWriter writer) +27
   System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +47
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +132
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +168
   ASP.configuration_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) +108
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +117
   System.Web.UI.Page.Render(HtmlTextWriter writer) +39
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) +132
   System.Web.UI.Control.RenderControl(HtmlTextWriter writer, ControlAdapter adapter) +168
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +9490

0 0

replied on February 11, 2021

Have encountered this before as well. Is a nasty error I've found when the domain for the Forms server is incorrectly written on initial configuration step. The page will produce a 'working on it' placeholder bar, but won't complete and doesn't reach a timeout. If the page is closed and the Laserfiche Mobile Configuration shortcut link is attempted again, the " Invalid URI: The format of the URI could not be determined " unhandled exception error page is displayed, and will persist even after a Laserfiche Mobile Server uninstall.

Replacing the 'web.config' file in the Program Files\Laserfiche\Mobile\Web Files with the one in the 'ReleaseConfig' folder will remove the error page, but produces a login loop for 'localhost' login request to the page after that.

Beyond that, checking a range of settings buried in IIS, Configuration files, registries etc are perhaps a little bit much of a task for unfamiliar users. As mentioned, it doesn't fix itself on Laserfiche Mobile Uninstall/Reinstall or Repair. Occurring in version of Mobile Server 10.4 used from Avante 10.4.3.

0 0

replied on November 12, 2021 • Show version history

I actually had to remove the entire <FormServer> element as removing just the attribute values still gave me the error. Once I performed an IIS reset everything started to work again.

Also I have noticed that it worked correctly when I added https:// or http:// in the server URL section instead of just the domain name.

Question

Question

Replies

Sign in to reply to this post.