It seems there's an invalid entry for the OldUrl column in the infocaster301 table... Maybe you can have a look for yourself to see if there are 'special/weird' entries?
My guess is that this is the line where the exception occurs:
Uri oldUri = new Uri(string.Concat(!oldUrl.StartsWith("http") ? "http://www.example.org" : string.Empty, !oldUrl.StartsWith("/") ? "/" : string.Empty, oldUrl));
It is taken into account that the OldUrl can be relative or absolute, so that shouldn't be a problem...
Maybe you can post the OldUrl's here so I can have a look with you? Or mail them to me; stefan [at] infocaster [dot] net if that feels better.
Error migrating data from V1 to V2
I'm getting this error when installing the new package and attempting to migrate data from V1:
Migrating data failed: Invalid URI: The format of the URI could not be determined. | Stacktrace: at InfoCaster.Umbraco.UrlTracker.UI.Installer.UrlTrackerInstallerService.HandleException(Exception ex) in c:\Users\kipusoep\Documents\GitHub\UrlTracker\UrlTracker\UI\Installer\UrlTrackerInstallerService.asmx.cs:line 168<br /> at InfoCaster.Umbraco.UrlTracker.UI.Installer.UrlTrackerInstallerService.MigrateData() in c:\Users\kipusoep\Documents\GitHub\UrlTracker\UrlTracker\UI\Installer\UrlTrackerInstallerService.asmx.cs:line 154<br /> at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)<br /> at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)<br /> at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)<br /> at System.Web.Script.Services.WebServiceMethodData.CallMethod(Object target, IDictionary`2 parameters)<br /> at System.Web.Script.Services.WebServiceMethodData.CallMethodFromRawParams(Object target, IDictionary`2 parameters)<br /> at System.Web.Script.Services.RestHandler.InvokeMethod(HttpContext context, WebServiceMethodData methodData, IDictionary`2 rawParams)<br /> at System.Web.Script.Services.RestHandler.ExecuteWebServiceCall(HttpContext context, WebServiceMethodData methodData)<br /> at System.Web.Script.Services.RestHandler.ProcessRequest(HttpContext context)<br /> at System.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)<br /> at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()<br /> at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)<br /> at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)<br /> at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)<br /> at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)<br /> at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)<br /> at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)<br /> at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)<br /> at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)<br /> at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)<br />
It seems there's an invalid entry for the OldUrl column in the infocaster301 table... Maybe you can have a look for yourself to see if there are 'special/weird' entries?
There were some entries which were just #. I have deleted these but problem still occurs.
There are some entries without a hostname and some on localhost. Would these make a difference?
My guess is that this is the line where the exception occurs:
It is taken into account that the OldUrl can be relative or absolute, so that shouldn't be a problem... Maybe you can post the OldUrl's here so I can have a look with you? Or mail them to me; stefan [at] infocaster [dot] net if that feels better.
There are nearly 1000 of them. I have emailed them to you.
Thanks
Dan
Thanks Dan, I found the bug and fixed it in v2.1.4, which I released just now.
That's fixed it! Thanks!.
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.