Could you upload the file '/config/dashboard.config' somewhere please, so I can debug the issue?

Sure, here it is:

https://www.dropbox.com/s/ixmyf55i41jbvtb/Dashboard.config

Thanks, I'll try to look into this soon, but I've got a lot on my hands ATM.

Also have had this error message today on Umbraco 4.11.5

Same error here on 4.7.1. All other componets except Dashboard installed correctly.

Installing the database table: Installed the database table.

Installing the dashboard failed:Object reference notset to an instance of an object.

Checking the Http Module: The Http Module is functional.
Checking if a previous version exists. Previous version checked succesfully.
Previous version not found.

Could you provide the correct Dashboard entries so that I can manually add them?

System: Umbraco Version - 4.7.1 ,Windows Server 2008 – 8gb memory – 4 Zeon 2.27Ghz processors service pack 1 – 64 bit OS , IIS version 7.5.7600.16385, SQL Server 2008 R2, Stacktrace - N/A         

We are really excited about deploying 301 URL tracker, BUT are also frustrated by the bug in the dashboard entires, like all of the users above, that make it impossible to deploy the program.   We look forward to having a correct set of dashboard entries and hope you find the time soon to rectify this situation.

Thanks.

To make it work please do the following step after installation

Make changes in  the following file ~\Config\Dashboard.config

Add inside StartupDashboardSection section tab for url traker. See example bellow.

<section alias="StartupDashboardSection">   
    <tab caption="Url Tracker">
      <control addPanel="true">/Umbraco/UrlTracker/InfoCaster.Umbraco.UrlTracker.UI.UrlTrackerManagerWrapper.ascx</control>
    </tab>
</section>

I did it manually and Url tracker start work.

Darn the e-mail notifications weren't working for a few days, so I didn't notice more people experiencing issues.

Alexey posted the correct contents of the dashboard.config file for the Url Tracker.

I can confirm that Alexey's solution has worked for me.

The package looks really good, I'm looking forward to testing it out!

I can confirm that Alexey's solution has worked for me.

The package looks really good, I'm looking forward to testing it out!

I have uploaded a new version; 2.0.4-beta.
In this version I've added better exception handling because I can't reproduce this issue, so a StackTrace will be included when an error occurs while installing.
Could anyone please install 2.0.4-beta and tell me what the StackTrace looks like? There's no need to remove 2.0.3 :-)

Thanks, looking forward to it!

After installing the Dashboard fix I got the following error when I tried to move a node:

 Invalid object name 'infocaster301'.

Exception Details: System.Data.SqlClient.SqlException: Invalid object name 'infocaster301'.

It appears by looking at the source that it looks for the previous version's database table which if your are installing it with the 2.0 beta does not seem to get installed. I created the table infocaster301 using the previous version 1.5.2 SQL (in the package.xml from the previous version) and then everything works on moves and redirects correctly.

Thanks much.

@Rob I'm afraid the previous version hasn't been uninstalled...

OK good point! Actually tried uninstallingthe previous version and it said it was uninstalled but maybe not. I tried uninstalling the 2.0 beta after the dashboard problem and that would not uninstall. Eventually tried installing and uninstalling a few times so maybe things were out of sync.

Here is the error when I tried to install2.0.4_beta

Installing the dashboard failed: Object reference not set to an instance of an object.

Well, this is awkward... It seems an error has occurred :-(
Please post a topic at the forum, including the message above, some information about your setup and the stacktrace below:

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 158
at InfoCaster.Umbraco.UrlTracker.UI.Installer.UrlTrackerInstallerService.InstallDashboard() in c:\Users\kipusoep\Documents\GitHub\UrlTracker\UrlTracker\UI\Installer\UrlTrackerInstallerService.asmx.cs:line 56
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at System.Web.Script.Services.WebServiceMethodData.CallMethod(Object target, IDictionary`2 parameters)
at System.Web.Script.Services.RestHandler.InvokeMethod(HttpContext context, WebServiceMethodData methodData, IDictionary`2 rawParams)
at System.Web.Script.Services.RestHandler.ExecuteWebServiceCall(HttpContext context, WebServiceMethodData methodData)
at System.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

Thanks Rob, but I'm still not sure what causes the NullReference, so I've added a few more checks and uploaded a replacement version of v2.0.4.

Could you download a fresh copy and install again to see what the output is? Really appreciating your help!

So far everything works great now that the Dashboard is installed. nodes are moved and renamed perfectly. Great package!!

Thanks for the positive feedback :-) It's been a lot of work!

I just can't stand the dashboard installer issue being not resolved yet, so could you please test for me? :-)

Stefan,

I am the Director of Web Development at UCSF and work closely with Rob Mayfield who has been posting above. He's our main developer. Let me say that 301 URL Tracker is a fantastic program and the Umbraco community should be indebted to you for creating it and then supporting it in real time.  I tested it out and its really an essential add-on, one of the best extensions in the community, right up there with Content Dashboard Maintenance in terms of its utlility.

Richard N. Barg, JD, MBA
Director of Web Strategy and Development,
Department of Surgery,
University of California, San Francisco
http://www.surgery.ucsf.edu/

We'll also test your replacement 2.0.4

I do have one suggestion, that is to slightly increase the size of the "Notes" column so the field data ie. "This page was moved" doesn't wrap in a typical browser (resolution 1280x1040) and greater.  We're only talking about 50 pixels or so. For the other columns, it really doesn't matter if they wrap.

Seems the problem is that the "StartupDashboardSection" is not found in the enumeration of the XElement:

XElement startupDashboardSectionElement = dashboardDoc.Element("dashBoard").Elements("section").SingleOrDefault(x => x.Attribute("alias").Value == "StartupDashboardSection");

----------------- here's the latest trace ----------------------

Installing the dashboard failed: Object reference not set to an instance of an object.

Well, this is awkward... It seems an error has occurred :-(
Please post a topic at the forum, including the message above, some information about your setup and the stacktrace below:

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
at InfoCaster.Umbraco.UrlTracker.UI.Installer.UrlTrackerInstallerService.InstallDashboard() in c:\Users\kipusoep\Documents\GitHub\UrlTracker\UrlTracker\UI\Installer\UrlTrackerInstallerService.asmx.cs:line 66
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodBase.Invoke(Object obj, Object[] parameters)
at System.Web.Script.Services.WebServiceMethodData.CallMethod(Object target, IDictionary`2 parameters)
at System.Web.Script.Services.RestHandler.InvokeMethod(HttpContext context, WebServiceMethodData methodData, IDictionary`2 rawParams)
at System.Web.Script.Services.RestHandler.ExecuteWebServiceCall(HttpContext context, WebServiceMethodData methodData)
at System.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)

Nope, it's because there's a section without an 'alias' attribute, so SingleOrDefault(x => x.Attribute("alias").Value) gives a NullRef:

<section>
  <areas>
    <area>developer</area>
  </areas>
  <tab caption="Error Log">
    <control>/usercontrols/ELMAH.ascx</control>
  </tab>
</section>

I'll fix this right away.

I'll download and install 2.1.1 and see how I get on.

Thanks for the support on this!

Robert

2.1.1 installs perfectly and works well, good job!

Robert

Awesome, thanks for reporting :-)

hi guys,

if its any help tp anyone installed version 2.1.1 on umbraco version 6.1.2 and didnt have this problem. i actually moved it myself to the developer section from the content section as i think it belong there and it still works.

Great improvement from version 1.5.2 love the new layout, hi5 to @kipusoep for this package.

@denford

Thanks for the nice words :-)
I don't know where it belongs. I chose the Content section for now, so content editors can access it too (because there is no DataType yet).

I think I'll add a dropdown in the installer so people can choose where to put the dashboard themselves :-) 

@kipusoep Ahh yes that would be awesome because i suppose with some clients they would want to monitor and change that, especialy with the 404's. the only other thing if im being a critic is could do with some pagination but besides that it great, one of my standard default packages on every site i build ;-)

I did add pagination to the GridView, 15 items per page:

<asp:GridView runat="server" ID="gvUrlTracker" CssClass="table table-striped table-bordered table-hover" AutoGenerateColumns="False" DataSourceID="odsUrlTrackerEntries" AllowPaging="True" AllowSorting="true" GridLines="None" CellSpacing="-1" DataKeyNames="Id" PageSize="15" OnSelectedIndexChanged="GridView_SelectedIndexChanged" OnRowDataBound="GridView_RowDataBound">

I guess it ain't working? I'll have a look at it tonight.

@kipusoep Sorry my bad lol it does work just didnt have enough rules to create the pagination. i mainly use the regex you see so that covered most of the old urls from the old site so gues cant fault you from my view, EVEN BETTER lol

@kipusoep  We'll (UCSF) will install the latest version tonight. 

re: the location of the extension, Content  is far preferable for us.  A configuation option sounds great.

 Where you able to widen (slightly) the Notes column?

Thanks.

Sorry I'm not going to discuss other topics than the dashboard installation bug in here, so if you'd like to suggest someting, create a new topic please.

is working on a reply...