Have you tried setting the framework version in IIS, for your site/virtual directory?
Main Topics
Browse All TopicsI believe I'm having a setup issue with a .NET environment.
Here's some potentially useful background info:
- Windows Server 2003 / IIS 6.0
- The following directories exist in the C:\Windows\Microsoft.NET\F
1.) v1.0.3705
2.) v1.1.4322
3.) v2.0.50727
- I have full admin access to the web server in question and I am free to make configuration changes, recycle IIS, etc.
- I have added IUSR_[machineName] and IWAM_[machineName] users to the Administrator group just to make sure permissions weren't the issue here
I am trying (unsuccessfully) to install Microsoft's FlexWiki. I have actually installed the wiki successfully on different servers, so I'm at a loss as to what's wrong in this case.
When I try to view the wiki (localhost/flexWiki/defaul
I found this towards the bottom of the following flexWiki help desk page: http://www.flexwiki.com/de
"Q: I went through the steps in QuickSetup. When I navigate to http://localhost/FlexWiki/
A The problem in my case was that asp.net was not properly installed. I got a tip to run the following command to install it, and this fixed my blank page problems:
C:\WINDOWS\Microsoft.NET\F
I tried the similar command for v2.0.50727, restarted IIS, and I'm still having blank page issues. Does anyone know of a utility I can run or some test I can do to see whether or not the ASP.NET runtime is successfully installed on my server or to further diagnose this issue?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
...you can't get to anything in your flexwiki install?
can you create just a super simple html page, put it into the flexwiki folder, and then see if you can browse to it?
like put this in notepad and save it as "test.htm" and place it in the flexwiki folder, then see if you can browse to it by going to http://localhost/flexWiki/
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtm
<html xmlns="http://www.w3.org/1
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>test page</title>
</head>
<body>Hi!
</body>
</html>
Strangely enough, when I try "http://server:port/defaul
When I try it in Firefox, I get:
XML Parsing Error: no element found
Location: http://server:port/default
Line Number 1, Column 1:
When I navigate to "http://server:port/" in Firefox or IE6, I get blank pages.
Ideas?
ok...so that means the virtual directory is mapped correctly...
now...let's test if a simple aspx page works...put this in a notepad file called test.aspx and put it in the same flexWiki folder and see if you can browse to it...it should just load the time...
...I know it seems like silly tests...but without being there and only using this forum...I don't know of a better way to test things...
if this page loads ok...then we know asp.net 2.0 is running correctly on the server and IIS is setup correctly...and the problem is in the actual flexWiki installation and not server related...
<%@ Page Language="VB" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtm
<script runat="server">
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs)
Me.Label1.Text = Now.ToString
End Sub
</script>
<html xmlns="http://www.w3.org/1
<head runat="server">
<title>Test Page</title>
</head>
<body>
<form id="form1" runat="server">
<div>
<asp:Label ID="Label1" runat="server" Text="Label"></asp:Label>
</div>
</form>
</body>
</html>
Yeah -- I've tried configuring it as its own website in IIS rather than just a virtual directory set as an application root -- same result either way.
Interestingly enough, I can go to something like:
http://server:port/pageDoe
OR:
http://server/appRootName/
And I get a blank page in IE, XML error in Firefox.
Arrrgh!
http://server:port/pageDoe
loads a blank page
and
http://server:port/test.as
doesnt work
but
http://server:port/test.ht
(our first html test page)
works?
i'm back to thinking that it is the asp.net components not being installed properly in IIS.
there isn't a diagnostic tool I know of perse besides aspnet_regiis...but usually running aspnet_regiis almost always clears up these types of problems...
aspnet_regiis has a lot of switches and parameters...and I"m betting one of them will get things going....
http://msdn2.microsoft.com
there are 2 switches that will let you see how asp.net is installed in IIS
"-lk" and "-lv"
maybe running those will give you some insight on whether or not asp.net got installed properly for the app....
Loads blank page in IE6, XML error in Firefox:
http://server:port/pageDoe
http://server:port/test.as
Loads with no issues:
http://server:port/test.ht
Thanks,
Phil
Here are the -lv and -lk results:
<cmd_text>
C:\Windows\Microsoft.NET\F
1.1.4322.0 Valid C:\NW2003\Microsoft.NET\Fr
2.0.50727.0 Valid (Root) C:\NW2003\Microsoft.NET\Fr
</cmd_text>
<cmd_text>
C:\NW2003\Microsoft.NET\Fr
W3SVC/ 2.0.50727.42
W3SVC/1/ROOT/Agency_New/ 2.0.50727.42
W3SVC/1/ROOT/AgentOpp/ 2.0.50727.42
W3SVC/1/ROOT/agy_reports/ 2.0.50727.42
W3SVC/1/ROOT/ALC/ 2.0.50727.42
W3SVC/1/ROOT/MSB/ 2.0.50727.42
W3SVC/1/ROOT/NewRequest/ 2.0.50727.42
W3SVC/1/ROOT/supportWiki/ 2.0.50727.42
W3SVC/1/ROOT/temp/ 2.0.50727.42
W3SVC/1301720292/root/ 2.0.50727.42
W3SVC/521952328/root/ 2.0.50727.42
W3SVC/7254/root/ 2.0.50727.42
</cmd_text>
I also tried -r:
<cmd_text>
C:\NW2003\Microsoft.NET\Fr
Start installing ASP.NET (2.0.50727) and replacing ASP.NET DLL in all Scriptmaps
with current version.
..........................
.....................
Finished installing ASP.NET (2.0.50727) and replacing ASP.NET DLL in all Scriptm
aps with current version.
</cmd_text>
OK -- some additional updates.
When I do -ua, of course it uninstalls all versions of ASP.NET, as promised.
Now the responses seem to be more reasonable:
server:port/page.aspx -- "The request is not supported."
server:port/nonexistentPag
I do -lk and -lv and it tells me that no versions of the ASP.NET framework are detected.
So, then I go to the Microsoft site and download the ASP.NET 1.1 redistributable (http://www.microsoft.com/
At any rate, now I go back in to C:\NW2003\Microsoft.NET\Fr
Then, trying the pages above give me the same errors as before.
Arggh!
I will try again with downloading and reinstalling the ASP.NET 2.0 redistributable: (http://www.microsoft.com/
oops, error in my last statement. I said this:
At any rate, now I go back in to C:\NW2003\Microsoft.NET\Fr
I meant this:
At any rate, now I go back in to C:\NW2003\Microsoft.NET\Fr
Note that I meant -i vs. -c (that's the only difference)
Thanks again.
I put the same test.aspx (from before in this thread) in wwwroot and tried to access it through the default website on port 80:
XML Parsing Error: no element found
Location: http://oh309wal1326/test.a
Line Number 1, Column 1:
Now I'm getting .NET Compact Framework 2.0 Service Pack 1 Redistributable:
http://www.microsoft.com/d
all I can think of is a corrupt IIS metabase...and regardless of what the diagnostics tell you...asp.net is definitely not installing correctly into IIS
and since you've installed flexwiki before without problems...it makes sense that the issue is at the web server (IIS) level and not anything with the installation of flexwiki...
99% of the time i've had problems getting asp.net to run, aspnet_regiis takes care of the problem...that other 1%...
sadly (and don't hate me for this)...I had to un-install IIS completely...ran some registry cleaning tools...and did a re-install of IIS and then ran aspnet_regiis
with all the things you've tried...I"m guessing this isn't a production server...a re-install of IIS is all I can think of ...there are ways to try and repair the IIS install...but it might just be easier to start fresh...
Ok -- so I've tried another server, and I notice when I right-click on an application root or a website in IIS 6 and hit properties, I don't see an ASP.NET tab.
However, I did run aspnet_regiis -i on directory v1.1.4322 on this server and it said that it completed successfully.
Why wouldn't the ASP.NET tab be there?
Thanks,
Phil
it's been a little while, but if I remember correctly, the asp.net tab in IIS wasn't added until 2.0 came out
1.x by itself didn't have this tab...
again...it's been a little while..and I can't find a web server on our network that is running only 1.x to verify...but i'm about 90% sure this tab wasn't there if your web server is running only 1.x
@samtran0331:
I have not pursued this issue any further, mostly because I didn't want to totally rip out IIS and reinstall it on either of these two servers. However, you've been immensely helpful and I really really appreciate it. I am confident that reinstalling IIS would resolve the issue, so I am comfortable awarding points for that recommendation.
Thanks again for all your assistance with this, and I apologize for the delay!
Best,
Phil / peh803
Business Accounts
Answer for Membership
by: samtran0331Posted on 2007-04-26 at 13:05:58ID: 18984725
does the event viewer show any errors?