• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 997
  • Last Modified:

Cannot view localhost or or the servers TrackIt web service on the local intranet

I did an update to my TrackIt sytem on my windows 2003 server running IIS 6 from 10 to 10.5 and the database updated fine but the web service did not.  This update required installing .NET framework 4 (which I did) but now when I go to the TrackIT web site I get an error message saying, "The incoming request does not match any route" and if I go to another one of the TrackIt pages its a blank page, and if I go to \\localhost\ or \\\ it says, "the page cannot be found".

I tried reinstalling the web program but got the same problem. I never had a problem on any of the other versions.  My gut says maybe it has something to do wtih .NET 4.  I even called TrackIt support and they said they had never seen anything like this before.

Now I don't mind if users can't put in tickets but I still have to fix this.

Any ideas?  Thanks in advance
  • 5
2 Solutions
MsAileenSAuthor Commented:
This is the one error I get

The incoming request does not match any route.
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.Web.HttpException: The incoming request does not match any route.

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:

[HttpException (0x80004005): The incoming request does not match any route.]
   System.Web.Routing.UrlRoutingHandler.ProcessRequest(HttpContextBase httpContext) +2310844
   System.Web.Routing.UrlRoutingHandler.ProcessRequest(HttpContext httpContext) +42
   System.Web.Routing.UrlRoutingHandler.System.Web.IHttpHandler.ProcessRequest(HttpContext context) +10
   Numara.TrackIt.Application.Web.SelfService._Default.Page_Load(Object sender, EventArgs e) +128
   System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) +14
   System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) +35
   System.Web.UI.Control.OnLoad(EventArgs e) +91
   System.Web.UI.Control.LoadRecursive() +74
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2207


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1

1) Step ...

open command prompt and go to below path

cd Windows\Microsoft.NET\Framework\v4.0.30319\

Make sure if your server is 64 bit then you have to select framework64 on above command

after then run  aspnet_regiis.exe -lk  command on command prompt.

It will list websiteID with your application name

check your application has assigned .net framework 4.0 version or not.

if it does not assigned means you have to install it in IIS

so you have to run aspnet_regiis.exe -i command from above same location.

and then open IIS manager --> right click on webapplication and select properties --> goto asp.net tab
and select framework 4.0 for your applicaiton.

if framework 4.0 is already there then check 2 step

2) Step
check your default document. if your default document could not found
in your web dire. then you have to select it and set as default document.

Let us know if it not helps..
MsAileenSAuthor Commented:
I will try the steps as soon as I get to work but I can tell you right now my server is not 64-bit. Are you saying .net 4 can't run on 32-bit?

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

MsAileenSAuthor Commented:
Please disregard, you said IF it is 64-bit.

I will try the following as soon as I get in.
MsAileenSAuthor Commented:
Ok so I did the steps provided and I had already installed .NET 4 so when I followed the steps above it did give an error.  so I proceeded to look at the tabs and as instructed and made sure they were all changed the ASP .NET version to 4.0.30319.  And then I tried to follow step 2 since it did say the default document could not be found but I did not know how to select it as the default document.  

So I then got to thinking....  It can't find the webpage on the local host itself, right?  Well, where did this webpage go?  I went to the home directory tab on the default website properities and checked the local path and then proceeded to Windows Explorer and followed that path and found it to be incomplete.  c:\inetpub\wwwroot; the wwwroot folder was missing (why I don't know, it was always there before).  I added the folder and everything started working!  thank you very much.  Just brainstorming with you got me where I needed to be!
MsAileenSAuthor Commented:
Because although I was pointed in the right direction (hence why I think he should get the points) the real solution was that the wwwroot folder was missing.  Not even the trackit people could figure that out. But many thanks to the person who pointed me to look around there.

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now