Troubleshooting Url Master Installations
Jul
18
Written by:
Friday, July 18, 2008 11:15 AM
Debugging Url Master Problems
With the growing number of installations of the Url Master module, the types of support requests I receive continue to surprise me - some people use the module in way I had not expected. That's great news, of course, as talented end-users come up with ways to make the software work for situations it wasn't necessarily designed for.
I'm happy about it, of course, because it validates the deliberate strategy of leaving a wide array of configuration options, which tends to mean no two installations are ever alike. However, the wide variety of requests highlighted the need for a way to remotely diagnose problems on installations. This isn't always possible, of course, because a lot of testing of the module takes place on 'localhost' installations.
This blog post is about how you (as the end-user) can debug and diagnose problems in your Url Master setup. The best place to look for answers remains the Url Master support forum, but think of this post as a guide to installating and troubleshooting.
Some DotNetNuke Url Theory
Before diving into the details, I'd like to cover some theory first. This is important to define terms so the rest is understandable. Here's the list of functions that the Url Master module actually does. This is to eliminate confusion as to what the functionality is.
- A Url Rewriting module : it takes virtual (as in they don't map to a physical file) Urls, and rewrites them so that the rest of the DNN code (including third party modules) sees the Url in the format that we would traditionally expect : /default.aspx?tabid=36&ctl=login
- A Url Redirecting module : it accepts Urls for locations and then forwards those requests to a new location. This is both done automatically for 'unfriendly' urls (forwarded to 'Friendly' urls) and for custom redirects (accepting a Url for a location no longer supported and forwarding the request to a new location)
- A Friendly Url Provider : Once installed, the module replaces the standard DNN Friendly Url Provider, and it generates Urls in the most humand and search friendly format possible. This includes putting a separator between words, allowing the end-user to specify whatever they like for page names, ensuring urls are all in lower case - anything to do with making presntable Urls.
- A DNN Rewriting HttpModule : this sounds like a duplicate of the first point, but it's important : the standard DNN Url Rewriter does more than just rewrite Urls, it also determines which request is for which portal, and sets important request context items, such as the 'PortalSettings' and 'OriginalUrl' values.
With those definitions out of the way, it's important to recognise in which area does your problem fall into
- Problems with 404 or 500 status codes, or from Third Party Modules not working correctly are probably Rewriting errors.
- Problems with 301 or 302 status codes, or from getting the wrong page for the Url requested, are probably Redirecting errors.
- Problems with Urls not looking like you would expect, such as including the 'Tabid' path when you didn't want it, are probably Friendly Url Provider errors.
- Problems such as 'PortalSettings is null' or other 'null reference' type errors in other parts of your DNN install may be to do with the failure of the DNN rewriting functions.
Note that I say 'probably' and 'maybe' because there are no hard and fast rules, and problems could be a combination of several of the above factors, working together.
Debugging Your Problems
Performing Http Tracing to Diagnose Problems Correctly
Install Microsoft Fiddler
The first thing I recommend is the downloading and installation of the Microsoft Fiddler tool. This is a Http traffic sniffing application that will show you the request/response for the Http traffic going to/from your website. You can download the Fiddler tool from here : Fiddler Download Page
Once you've got Fiddler installed, you'll be presented with a UI that doesn't make it obvious where to start. Here's what you want to do :
- Start Fiddler, and check that the 'File'->'Capture Traffic' option is ticked.
- Open up your site to debug in Internet Explorer (yes, Firefox users, it won't kill you)
- Watch as the Http traffic between IE and your website is listed in Fiddler. If you don't get a Fiddler-screen full of http traces, then refer to the Fiddler help until you can get it sniffing your Http traffic.
Figure 1 : Microsoft Fiddler Session Trace Detail
As you can see in the above image (which is a Fiddler trace of ifinity.com.au), there is one line for each request (or 'hit') made to the ifinity.com.au server. Incidentally, this is why you don't refer to 'hits' when talking about web page statistics - there are 26 hits here for one single page view. Each of these lines represent a resource that was downloaded from the server. There a couple of other rogue requests in there as well, such as the Google Toolbar request (see, I told you they were watching you) and the Internet Explorer 7.0 phishing filter request (urs.microsof.com:443 - see I told you they were watching you also!)
Understanding a Fiddler Trace
Each of these lines are the key to understanding problems with your site. The first thing to inspect is the 'Result' column. A result of '200' means everthing went OK. A result of '404' (such as the ifinity.com.au favicon - which I'll attempt to fix here) means the request did not go OK. A result of 301 or 302 means that the request was forwarded to another location.
If you've got obvious problems with your Url Master install (such as a page request returning a 404) then this is the first place to look. Non-obvious problems might be that the formatting of your page is all wrong, which is likely a stylesheet with a 404, or some type of key functionality does not work because of javascript errors (a 404 on a .js or .axd file).
Forming your own Requests
You don't need to 'sniff' traffic to use Fiddler - you can also use it to craft your own Http requests and submit them. The easiest way to do this is to click on an existing trace, and drag it over to the 'Request Builder' tab. When the tab goes bright green, then drop the item, and the Request will be automatically created for you.
Figure 2 : Microsoft Fiddler Request Detail
In the above example, I have dragged-and-dropped the trace for the 'favicon.ico' request into the Request Builder. I can now click on 'Execute', and Fiddler will repeat that request to the server for me. Because I haven't changed anything, the result comes back exactly the same.
The thing that I am most interested in is the Response headers. These contain information about the response we got back from the server. You access the Response Headers by clicking on the trace session for the request you would like to inspect (on the left hand pane) and then clicking on the 'Headers' button in the lower area of the 'Session Inspector' tab.
HTTP/1.1 404 Not Found
Date: Thu, 17 Jul 2008 23:59:26 GMT
Server: Microsoft-IIS/6.0
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 6748
The above list shows the response headers for the 'favicon.ico' request.
Getting Debug Information From Url Master
The latest versions of Url Master (from 1.0.9 upwards) have built-in debug code that is activated when you add in a request parameter. This allows you to gain more information about what is causing your problem.
To do this, add the following request parameters into your Fiddler request. You do this by clicking in the 'Request Headers' section of the 'Request Builder' tab, and typing in the information as follows :
_umdebug:true
This request parameter should be on a new line in the Request Headers section, so the entire request headers looks a bit like this :
Accept: */*
UA-CPU: x86
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1;)
Host: www.ifinity.com.au
Proxy-Connection: Keep-Alive
_umdebug: true
Submit the request using the 'Execute' button, and then inspect the headers by clicking on the trace, and selecting 'Headers' in the Session Inspector response area.
You will see on the bottom of the list of headers, a value called 'X-UrlMaster-Debug:'. This contains debug information as formatted by the Url Master application. If you don't get this response header, and you included '_umdebug:true' - either of two things has happened. 1) You haven't got a recent enough version of Url Master (1.0.9 upwards), or 2) the error is occuring before the code in the Url Master module is run. The second of these scenarios points to an ASP.NET or IIS problem.
If you do have a Url Master debug response header, it will look something like this:
X-UrlMaster-Debug: http://www.ifinity.com.au/favicon.ico,
, www.ifinity.com.au/favicon.ico, Output404
Note, debug information broken over two lines for formatting
To understand this, here are the 4 sections to the debug header. Each section is separated by a comma, and each can have a value, or no value at all, depending on the response status. Here are the values, in order:
- Original request : the Url, as requested to the server and seen by the Url Master module. Note that in some cases IIS can modify this request value, and it won't be exactly as typed in.
- Redirect Url : if a redirect was requested, the value of the Url that the request is redirect to is shown here. Incidentally, the response status should also show this Url if it is a 301 or 302.
- Rewrite Path : If a rewrite was processed, the value of the rewritten path will be shown here.
- Action : This is an internal encoded value, and indicates what the Url Master module decided to do with the request. It may say 'Continue' which means 'OK', or it may say 'Redirect301' which means it decided to 301 redirect the request.
As you can see with the favicon example, it decided to output a 404 error as the request could not be understood.
As another example, see this debug request as submitted to the /home.aspx value:
X-Redirect-Reason: Site Root Home Requested
X-UrlMaster-Debug: http://www.ifinity.com.au/home.aspx, http://www.iFinity.com.au/
, Default.aspx?tabId=53, Redirect301
Note, debug information broken over two lines for formatting
You can see the original request (with home.aspx), the resulting redirect (the site root), the rewritten path (?tabid=53, the home page) and the action value. In addition, because it was a redirect request, the reason for the redirect is also output. In this case it was becase the home page was requested, and an in-built rule for Url Master is that requests for the home page are forwarded to the site root value.
Troubleshooting Url Master Installations
I feel obliged to mention here that the majority of installations of Url Master work just fine, and the code works as designed. For the other 5% or so where there are complications, here's a good checklist for troubleshooting your problems.
- If you're getting a 404 error, is it from IIS, or ASP.NET, or from Url Master. Url Master 404 pages are different to the IIS 404 page and the ASP.NET 404 page. If you're getting an IIS or ASP.NET 404, chances are the problem lies in an IIS setting like application configuration. A common mistake is to modify the page extension mapping (to wildcard or another value) and then tick the 'verify file exists' check box. This will result in 404's because each of the Urls is virtual, in that it doesn't map to a physical file location.
- Check your DNN Event Log. Some exceptions will result in a 404 so as to not stop the site from working if they are in the main logic path. An example is an invalid Regex filter applied in the settings for the module - the latest versions of Url Master log an exception but don't stop processing. If you can't logon to your site to check the log, query the database directly - it's the dnn_EventLog table you need to look at.
- Understand the debug information if you're using it, and try and work out why you're getting the results you're getting. If you're getting a 404 for something like a .swf, .png, .ico file, and you have 'wildcard' mappings on for your site to run in extension-less mode(as ifinity.com.au does), then you may need to exclude that value using the advanced regex settings.
- Don't forget the test setup. In the 'Friendly Url Settings' page of your Url Master installation, there are test boxes for both Friendly Url Generation and Url Rewriting. You can test out the Urls you're trying, and these boxes will give information as to what happened during processing. This is particularly useful if you're trying to install the module on a live site, and can't leave the Url Master module 'switched on' because some aspect of the site is not working. The 'test' functions will work even when the module is switched off.
If you've come across a module that doesn't seem to work well, it's probably because that module doesn't use the Friendly Url API in the DNN Core to generate Friendly Urls. These modules often do some type of find/replace function on the 'default.aspx' string in the Url, and as such, are outside of the Core Url functionality. It's best to ask the developer of the module to use the core Friendly Url Api to generate the Urls, and you can point them to my blog post on the topic : An open letter to the DotNetNuke developers of the world: Please start using the FriendlyUrlProvider API for custom page names!
Need More?
Of course, if you're stuck and this information hasn't helped at all, you should post your problem to the Url Master Support Forum.
If you've got any other tips to add, please do so via the comments below. Personally, I'm off to locate my lost favicon.ico.
19 comment(s) so far...
Re: Troubleshooting Url Master Installations
Not sure if you're aware or not, but the links in the RSS feeds for your blog are messed up.
Troubleshooting Url Master Installations
If you've installed the Url Master module, and it's not working exactly as you want, here's some things to try to work out where you're going wrong.
http://www.ifinity.com.auhttp/www.iFinity.com.au/Blog/Technical_Blog/EntryID/43/
By John Henley on
Saturday, July 19, 2008 12:29 AM
|
Re: Troubleshooting Url Master Installations
John - I am aware of it - as far as I can tell it is a blog RSS feed error. It's to do with the blog module not checking to see whether the portal alias is attached to the Url when it receives the Url back - it always appends the portal alias to the front of the returned Url. I'm still trying to come up with a fix that doesn't involve modifying the blog code.
thanks for letting me know, though
By Bruce on
Saturday, July 19, 2008 9:21 AM
|
Re: Troubleshooting Url Master Installations
This post should hopefully save some support calls Bruce!
I am pretty sure the blog RSS issue is fixed in later versions of DNN - an upgrade should do the trick...
By Rodney on
Monday, July 21, 2008 2:39 PM
|
Re: Troubleshooting Url Master Installations
I would be happy just to get the module installed. I have tried now on 2 attempts, unsuccessfully. I install the module, make the changes suggested in Host -> Friendly Url Settings, the Apply the changes (effectively making the change in my web.config), then I cannot access my site after that. I get the following error:
500 Server Error
(An error occured during processing)
Exception:
Could not load file or assembly 'DotNetNuke.HttpModules, Version=4.6.2.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
Stack Trace:
at iFinity.DNN.Modules.UrlMaster.RewriteController.IdentifyByRegEx(String absoluteUri, String queryString, String applicationPath, UrlAction result, FriendlyUrlSettings settings) at iFinity.DNN.Modules.UrlMaster.UrlRewriteModule.CheckForRewrite(Uri requestUri, UrlAction result, Boolean useFriendlyUrls, NameValueCollection queryStringCol, FriendlyUrlSettings settings) at iFinity.DNN.Modules.UrlMaster.UrlRewriteModule.ProcessRequest(HttpContext context, HttpRequest request, HttpServerUtility Server, HttpResponse response, Boolean useFriendlyUrls, String requestType, Uri requestUri, UrlAction result, NameValueCollection queryStringCol, FriendlyUrlSettings settings)
What am I missing? BTW, I am trying to get an extensionless URL configuration installed, and yes, I do have full control of my Windows Server 2003 IIS. My site does work after I make the necessary changes in IIS, just not when I apply the web.config changes. TIA for any help!
By Dennis St. John on
Tuesday, August 19, 2008 2:43 AM
|
Re: Troubleshooting Url Master Installations
Dennis, the Url Master module requires DNN 4.6.2 or later.
-Bruce
By bchapman on
Tuesday, August 19, 2008 9:23 AM
|
Re: Troubleshooting Url Master Installations
As a followup - all I had to do to allow the favicon.ico through was put it in the 'ignoreRegex' - I did this by adding |\.ico on the end of the regex filter.
By host on
Tuesday, September 09, 2008 3:34 PM
|
Re: Troubleshooting Url Master Installations
Hi.
We've just adquired a license for yor UrlMaster for DNN module and our problem is than can't install the UrlMaster module in our dnn website. When we try it, the following SQL error occurs:
Start Job Registering DesktopModule
Information Registering Definitions
Information Registering Controls
Fail Exception System.Data.SqlClient.SqlException: Function or procedure AddTab has too much arguments. Instruction ended. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(SqlConnection connection, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, CommandType commandType, String commandText, SqlParameter[] commandParameters) at Microsoft.ApplicationBlocks.Data.SqlHelper.ExecuteScalar(String connectionString, String spName, Object[] parameterValues) at DotNetNuke.Data.SqlDataProvider.AddModuleControl(Int32 ModuleDefId, String ControlKey, String ControlTitle, String ControlSrc, String IconFile, Int32 ControlType, Int32 ViewOrder, String HelpUrl, Boolean SupportsPartialRendering) in C:\Web ASEM\Library\Providers\DataProviders\SqlDataProvider\SqlDataProvider.vb:line 737 at DotNetNuke.Entities.Modules.ModuleControlController.AddModuleControl(ModuleControlInfo objModuleControl) in C:\Web ASEM\Library\Components\Modules\ModuleControlController.vb:line 111 at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.RegisterModules(PaFolder Folder, ArrayList Modules, ArrayList Controls) in C:\Web ASEM\Library\Components\ResourceInstaller\PaDnnInstallerBase.vb:line 427 at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.Install(PaFolderCollection folders) in C:\Web ASEM\Library\Components\ResourceInstaller\PaDnnInstallerBase.vb:line 551 at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install() in C:\Web ASEM\Library\Components\ResourceInstaller\PaInstaller.vb:line 76
In your scripts 01.00.00.SqlDataProvider and 01.10.04.SqlDataProvider (we're using the module version 12 iFinity.UrlMaster_01.12.00_Install.zip), there is a query like this for the stored procedure AddTab:
/*add in a new tab */
exec {objectQualifier}AddTab @portalId, @TabName, @isVIsible, @disableLink, @parentId, @TabIconFile, @title, @Description,@KeyWords
,NULL, @skinSrc, @containerSrc, @TabPath, @startDate, @endDate, @refreshInterval, @pageHeadText, @isSecure
But our procedure definition is the following, where, as can see, there's no definition for the @isSecure parameter:
CREATE procedure dbo.AddTab
@PortalId int,
@TabName nvarchar(50),
@IsVisible bit,
@DisableLink bit,
@ParentId int,
@IconFile nvarchar(100),
@Title nvarchar(200),
@Description nvarchar(500),
@KeyWords nvarchar(500),
@Url nvarchar(255),
@SkinSrc nvarchar(200),
@ContainerSrc nvarchar(200),
@TabPath nvarchar(255),
@StartDate DateTime,
@EndDate DateTime,
@RefreshInterval int,
@PageHeadText nvarchar(500)
as
insert into Tabs (
PortalId,
TabName,
IsVisible,
DisableLink,
ParentId,
IconFile,
Title,
Description,
KeyWords,
IsDeleted,
Url,
SkinSrc,
ContainerSrc,
TabPath,
StartDate,
EndDate,
RefreshInterval,
PageHeadText
)
values (
@PortalId,
@TabName,
@IsVisible,
@DisableLink,
@ParentId,
@IconFile,
@Title,
@Description,
@KeyWords,
0,
@Url,
@SkinSrc,
@ContainerSrc,
@TabPath,
@StartDate,
@EndDate,
@RefreshInterval,
@PageHeadText
)
select SCOPE_IDENTITY()
GO
If we delete the @isSecure parameter in your scripts, the modules installs succesfully, but a new error appears if we make click in the menu option Admin / Page URLs
DotNetNuke Error: - Version 04.05.01
--------------------------------------------------------------------------------
An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: Method not found: 'Boolean DotNetNuke.Entities.Tabs.TabInfo.get_IsSecure()'. ---> System.MissingMethodException: Method not found: 'Boolean DotNetNuke.Entities.Tabs.TabInfo.get_IsSecure()'. at iFinity.DNN.Modules.UrlMaster.Entities.TabInfoEx.Clone(TabInfo tab) at iFinity.DNN.Modules.UrlMaster.Entities.TabInfoEx..ctor(TabInfo tab) at iFinity.DNN.Modules.UrlMaster.Data.SqlDataProvider.GetTabs(Int32 portalId, Boolean includeAdminTabs, Boolean includeHostTabs) at iFinity.DNN.Modules.UrlMaster.UrlMasterController.GetTabs(Int32 portalId, Boolean includeStdUrls, String httpAlias, FriendlyUrlSettings settings) at iFinity.DNN.Modules.UrlMaster.UI.Controls.PageList.GetTabs(Int32 portalId) at iFinity.DNN.Modules.UrlMaster.UI.Controls.PageList.TabsToScreen(Int32 portalId) at iFinity.DNN.Modules.UrlMaster.UI.Controls.PageList.Page_Load(Object sender, EventArgs e) at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) at System.EventHandler.Invoke(Object sender, EventArgs e) at System.Web.UI.Control.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace ---
--------------------------------------------------------------------------------
Return to Site
We're using: Microsoft SQL Server 2000 and DNN Version: 04.05.01
Please, help us.
By Julen Joseba Garrastatxu on
Wednesday, January 14, 2009 1:52 AM
|
Re: Troubleshooting Url Master Installations
Hi Julen
The module requires version DNN 4.6 or higher. You'll need to upgrade your DNN install first. I'd recommend this anyway as later versions run faster and have many security patches.
-Bruce
By Bruce Chapman on
Wednesday, January 14, 2009 7:45 AM
|
Re: Troubleshooting Url Master Installations
Thanks a lot, Bruce.
I wil upgrade to 4.6 version and try it again.
Best regards.
By Julen Joseba Garrastatxu on
Friday, January 16, 2009 7:24 PM
|
Re: Troubleshooting Url Master Installations
... but...
Bruce,
We've used the module version 12 (iFinity.UrlMaster_01.12.00_Install.zip) and not the 13. Does this version not work with dnn 4.05.01?
In the version 13, you specify I need dnn 4.6 so I tried to install version 12.
Best regards (again).
By Julen Joseba Garrastatxu on
Friday, January 16, 2009 7:39 PM
|
Re: Troubleshooting Url Master Installations
Julen
There is no version of the module that works with 4.5. All versions require 4.6 and above. This is because of the change in the way the Url Rewriting modules were packaged starting from version 4.6.
-Bruce
By Bruce Chapman on
Friday, January 16, 2009 10:07 PM
|
Re: Troubleshooting Url Master Installations
Well...for me this blog is completely Greek. The module is NOT intuitive and the apparant strategy is to not include any documentation that makes sense so we can all sign up for the "master support". I'm sick of this. I've got ZERO response from you guys. It must be that the only people reviewing the module work for you.
By genewell on
Saturday, June 06, 2009 6:12 AM
|
Re: Troubleshooting Url Master Installations
@greg Sorry the support times can lag by several hours : this is due to the difference in timezones. I've now responded to your help tickets, there's no need for premium support just to get the module configured as you need. I also welcome any suggestions to improve the documentation that you might have, it's not always easy to write documentation from the point of view of someone who has not seen the module before.
Just to be clear, any review, testimonial or comment that you might see for the module are from genuine paying customers.
By Bruce Chapman on
Saturday, June 06, 2009 8:24 AM
|
Re: Troubleshooting Url Master Installations
Hi Bruce,
We have purchased license for iFinity URL master. I followed each and every step regarding installation of this module, but when I apply the URL master settings, all the pages start giving 404(Page Not Found). I figured out that if I do not use "Replace Spaces in Page Titles? " in configuration then it works fine but as soon as I use hyphen(-) or underscore(_) to replace the spaces I get 404 error. I am using DNN 5.0 and iFinity.UrlMaster_01.13.10 . I used Fiddler to debug this but am not getting any debug information. I checked IIS configuration and that is OK. Please help me to get this problem resolved.
By Sushil Kumar Tripathi on
Tuesday, June 09, 2009 7:36 PM
|
Re: Troubleshooting Url Master Installations
@Sushil I'm not sure what the problem is but will need an example url to check - Please log your support requests in the Support Forums at www.ifinity.com.au/Products/Support_Forums so you will be notified of an answer.
By Bruce Chapman on
Wednesday, June 10, 2009 11:12 AM
|
Re: Troubleshooting Url Master Installations
Installed the module and enabled it, applied changes, uploaded the license file.
I did NOT check the no extensions option at first... tried to navigate any of hte tabs on teh site and get a page not found error page -- but if I type default.aspx after the url in the browser hte page shows up.
So, I went back into the Master URL settings and checked the Never Use extensions setting since it was hiding the extensions, and applied changes. Tried navigating again and it still dosn't work. Page not found on any menu items.
Since this is a production site I tried the revert to host provider button but that didn't change anything; still have no extensions and can't find page errors. Reverted back to using your module with no extensions -- still doesn't work.
Is it because wildcards are not enabled on teh server and will enabling them fix it? I can't do that myself because it's a client's environment but I have to tell them early monday morning when they see the site is down; I do not have access to their web config either.
By Richard Golko on
Sunday, December 06, 2009 12:29 AM
|
Re: Troubleshooting Url Master Installations
Hi I get this error when trying to load URL master trial version
ExceptionSystem.UnauthorizedAccessException: Access to the path 'C:\Inetpub\vhosts\planit73.com\httpdocs\images\Friendly-Urls-icon.gif' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite) at DotNetNuke.Common.Utilities.FileSystemUtils.CopyFile(String sourceFileName, String destFileName) at DotNetNuke.Services.Installer.Util.CopyFile(InstallFile installFile, String basePath, Logger log) at DotNetNuke.Services.Installer.Installers.FileInstaller.InstallFile(InstallFile insFile)
Failure Installation Failed - File
By Scott Mackay on
Saturday, May 21, 2011 2:36 PM
|
Re: Troubleshooting Url Master Installations
@Scott - you need to grant your IIS/ASP.NET user permission to write to the \images path. As a rule, the user that the dnn site runs under should be able read/write/create/delete on all files and directories under the site root.
By Bruce Chapman on
Saturday, May 21, 2011 2:56 PM
|
Re: Troubleshooting Url Master Installations
Hi, This is going to be tough to explain, but here goes.
I have installed Infinity URL on our pre-production site. Have had good success installing and with initial setup, except for two issues.
#1 One page(researchnotes) at times "takes over" and the entire site has been defined under it. For example this is what is displayed: 206.168.225.161/researchnotes/Services when it should be 206.168.225.161/Services. Along with this, at times, the ResearchNOTES page displays the home page and I cant log out, or log back in with out using the login.aspx extension. I have tried deleting the page, renaming the page, etc. But every time I add the page back in it, the paths seem to get lost.
#2 There are 12 pages whose access is thru links on the ResearchNOTES page and their extensions are not changing - they keep the .aspx extention. (originally I had ResearchNOTES as the parent but tried to debug the problem by removing the parent/child connection) This is what is currently displaying: 206.168.225.161/july2010.aspx
I am waiting to install this into a production status for my client until these are resolved. Thanks, Jenny
By Jenny J on
Thursday, May 26, 2011 12:40 AM
|