MonoX support board

Start the conversation, ask questions and share tips and solutions with fellow developers.

Non-registered users can only browse through our support boards. Please register now if you want to post your questions. It takes a second and it is completely free. Alternatively, you can log in without registration using your credentials at major sites such as Google, Microsoft Live, OpenId, Facebook, LinkedIn or Yahoo.

Page Not Found erros for groups  (Mono Support )

Viewed 16975 time(s), 5 post(s) 11/9/2010 3:37:54 PMby toddbert
toddbert

toddbert

11/9/2010 3:37:54 PM
Hi,

I have installed the latest monox and the initial pages all work fine. I can see the home and content pages, login to admin etc.

As soon as I attempt to view a groups page it gives a 404 not found error eg
http://localhost/MonoX/MonoX/Pages/SocialNetworking/Groups/GroupView/tTEhT5qOAE-0VZ4pAYNDfA/Aiden/

I'm guessing its something to do with url routing but cant figure out specifically what.

I'm running .Net 3.5 SP1.

Cheers
This content has not been rated yet. 
0 Reputation 3 Total posts
denis

denis

11/9/2010 4:35:05 PM
Hi,
I assume that you are using IIS 5.1 or 6. Since the group part (and many others) are using the "rewritten" URLs - they do not have the .aspx extension - you need to set the "wildcard mapping" in IIS so it could catch all requests, including the ones for "extensionless" resources. This feature is crucial for SEO and many other techniques.

By default, only the .aspx and related files (.ashx, .asmx) are mapped to the ASP.NET runtime. You can change this by following tis procedure:
- right click on the Web site you want to administer, Properties, Home directory tab, Configuration button. Copy the executable path from one of the existing ASP.NET extensions (.asax, for example). Click on the insert button, paste the executable path you copied in the previous step, and uncheck "Verify that file exists". This should fix this problem.
This content has not been rated yet. 
7207 Reputation 956 Total posts
toddbert

toddbert

11/9/2010 8:50:47 PM
Thanks for the quick reply. That fixed the problem.
This content has not been rated yet. 
0 Reputation 3 Total posts
RCrouch

RCrouch

1/7/2011 7:20:43 PM
I am having the exact same issue, but in Windows7... What are the steps for IIS 7.5?
This content has not been rated yet. 
0 Reputation 1 Total posts
denis

denis

1/7/2011 10:51:08 PM
It should work by default on IIS 7 and higher if runAllManagedModulesForAllRequests attribute of the modules node in the system.webServer section is set to True. More info: [url=http://learn.iis.net/page.aspx/508/wildcard-script-mapping-and-iis-7-integrated-pipeline/]http://learn.iis.net/page.aspx/508/wildcard-script-mapping-and-iis-7-integrated-pipeline/[/url]
This content has not been rated yet. 
7207 Reputation 956 Total posts