U4-1744 - Missing DefaultProvider RegEx in providers for UrlRewritingNet

Created by Josh Reid 19 Feb 2013, 21:01:16 Updated by Sebastiaan Janssen 12 Jan 2016, 10:44:10

After upgrading from 4.10 to 4.11.x (and likely further upgrades- reports of it still happening in 6.0RC) there is a random error in back office (often when creating nodes but also on save/publishes)... Shown below. (I've tried including 'defaultProvider="RegEx"' in the first line of UrlRewriting.config like so (to no avail):

'''Server Error in '/' Application.''' '''''Missing the DefaultProvider RegEx in the list of providers for UrlRewritingNet''''' 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.ApplicationException: Missing the DefaultProvider RegEx in the list of providers for UrlRewritingNet

'''Source Error:'''

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

'''Stack Trace:''' [ApplicationException: Missing the DefaultProvider RegEx in the list of providers for UrlRewritingNet] UrlRewritingNet.Web.UrlRewriting.Initialize() +420 UrlRewritingNet.Web.UrlRewriting.CreateRewriteRule(String providerName) +16 UrlRewritingNet.Web.UrlRewriteModule.Init(HttpApplication context) +232 System.Web.HttpApplication.InitModulesCommon() +172 System.Web.HttpApplication.InitModules() +43 System.Web.HttpApplication.InitInternal(HttpContext context, HttpApplicationState state, MethodInfo[] handlers) +828 System.Web.HttpApplicationFactory.GetNormalApplicationInstance(HttpContext context) +304 System.Web.HttpApplicationFactory.GetApplicationInstance(HttpContext context) +107 System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +327

Original Forum post: http://our.umbraco.org/forum/ourumb-dev-forum/bugs/36672-Missing-DefaultProvider-RegEx-in-providers-for-UrlRewritingNet-4111

Comments

Kris Vanlooy 15 May 2013, 12:10:09

I have had this error while installing the Google Maps datatype and the Config tree package via the online package repository in v4.11.8


Peter Slight 22 May 2013, 11:55:10

I seem to experiance this when trying to load the backoffice /umbraco/ on a cold start of the application . So the IIS been reset (or been taken out of memory because it hasn't been used), then the first page requested is http://www.website.com/umbraco/ this then throws the error.

using 6.0.3


Karl Walls 22 May 2013, 13:47:41

Getting this in the 6.0.5 release when trying to publish a tree node with children


Josh Reid 02 Aug 2013, 22:55:21

This is a UrlRewriting.net issue - Use IIS URL Rewrite Module instead.


Peter Slight 04 Sep 2013, 12:53:59

I'm not sure being pointed to use something else is an option for everyone. Some developers are in shared hosting and this might not be possible for them.


Peter Slight 11 Sep 2013, 11:49:10

On one of my installations I've removed the urlRewritingNet and used the IIS URL rewrite module (as @Josh suggested) and all is well. So it is a possible solution - thanks josh. This might not be an option for all though.


Damian Green 28 Jan 2014, 12:50:10

I have ahad it when i have had an app recompile on the server after deploying new DLLS. If i make another request it clears. Could maybe be the fact this is the first module that gets fired.

Also the server it was happeneing was desperate for a reboot and its happening tonight - compile times are terrible at the moment and a reboot normally sorts this out.

Ive not had this error before but be interesting to see if it still happens after the reboot. Will let you know if it does as the only pther thing ive done with this site is upgrade it from v4.7 to 6.1.6.


Damian Green 17 Mar 2014, 17:57:26

I am still getting this on 6.2 beta when uploading a new dll to a site and it has to recompile.


Sebastiaan Janssen 06 Jan 2016, 15:48:19

Almost 3 years later: looks like this is fixed in UrlRewriting.Net - I've asked him to release a new version so we can ship with it! https://github.com/aspnetde/UrlRewritingNet/pull/2


Sebastiaan Janssen 12 Jan 2016, 10:44:10

Updated UrlRewritingNet to a new version that incorporates this change.


Priority: Normal

Type: Bug

State: Fixed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 4.11.0, 4.11.1, 4.11.2, 4.11.3, 4.11.4, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 4.11.8, 6.2.0

Due in version: 7.3.5

Sprint:

Story Points:

Cycle: