All, Seeing very strange behavior on a Win2003 server onto which I'm trying to install just MDAC9b1 and the 2.0 Framework (from dotnetfx.exe which ships with VS2005 March 2004 Preview). The Dot Net installer takes forever, seeming to hang on the aspnet_regiis.exe
-i step, and when I check the Application Log, I get a few errors which read: The ASP.NET DLL (Path: C:\WINDOWS\Microsoft.NET\Framework\v1.2.30703\aspnet_isapi.dll) (Version:1.2.30703.0) is missing That looks like the old Whidbey path (Oct 2003 codebase),
so I'm wondering if something is corrupted in this server's registry. (The server used to have the Whidbey Framework on it.) If I look in my c:\windows\microsoft.net\framework directory, I see four version directories, including the v1.2.30703 directory, despite
the fact that I've done a proper uninstall of the Whidbey redistributables, and the VS.NET 2005 version of them installs properly. If I try to do a manual aspnet_regiis.exe -i, the process takes a very long time, and it generates an unusual number of periods
(two lines worth). And it produces errors: "Setup has detected some errors during the operation. For details please read the setup log file..." and when I review that file, I get all sorts of interesting errors, some of which pertain to the ASPNET_Admin stuff
(which I know is broken) and some of which appear to pertain to othere problems. (It's a big file, but I can post the "Failure" lines if someone wants them.) Any ideas, folks? Thanks, /s/ James
Check so you don’t have the path to the PDC bits in the Environment variable PATH. Search through the registry for the old version and remove any keys if they don’t have bean removed successfully when you uninstall the PDC bits. I don’t know if this will help
you, but you can give it a try.
Hello All, I have a similar problem installing VS2005 March 2004 Preview. The aspnet_regiis.exe -i step had the following errors in the ASPNETSetup_00000.log file: 2004-04-01 16:32:38 Starting Precompile the web admin tool. 2004-04-01 16:32:41 Starting Error
executing the following command line: aspnet_compiler -m /LM/w3svc/1/Root/aspnet_webadmin/2_0_40301 2004-04-01 16:32:41 Failure Error executing the following command line: aspnet_compiler -m /LM/w3svc/1/Root/aspnet_webadmin/2_0_40301: PrecompileWebAdmin failed
with HRESULT 80004005: 'Unspecified error ' 2004-04-01 16:32:41 Failure Precompile the web admin tool.: PrecompileWebAdmin failed with HRESULT 80004005: 'Unspecified error ' 2004-04-01 16:32:41 Failure Precompile the web admin iis app.: PrecompileWebAdmin
failed with HRESULT 80004005: 'Unspecified error ' 2004-04-01 16:32:41 Failure Setting up web admin application: SetupFiles failed with HRESULT 80004005: 'Unspecified error ' Now I can't bring up the properties dialog for any directory in IIS. Can anyone help?
Many thanks, Paul
>Now I can't bring up the properties dialog for any directory in IIS To resolve this issue Open the registry editor by selecting Run from the Start menu, typing regedit, clicking OK. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET and locate the registry
key with the name 2.0.40301.9 (pd4.040301-0900). Rename this registry key to 2.0.40301.9. Select the registry key named 2.0.40301.9 and locate the sub-key named DllFullPath. Right-click the sub-key named DllFullPath and select Modify. In the Value data: text
box, type the file location of the aspnet_isapi.dll for the .NET Framework version 2.0.40301. For example, C:\WINDOWS\Microsoft.Net\Framework\v.2.0.40301\aspnet.isapi.dll. Note Windows may not be installed in the C:\WINDOWS directory on your server. Be sure
to use the proper path to the Windows installation for your server. Select the registry key named 2.0.40301.9 and locate the sub-key named Path. Right-click the sub-key named Path and select Modify. In the Value data: text box, type the folder location of
the aspnet_isapi.dll for the .NET Framework version 2.0.40301. For example, C:\WINDOWS\Microsoft.Net\Framework\v.2.0.40301. Note Windows may not be installed in the C:\WINDOWS directory on your server. Be sure to use the proper path to the Windows installation
for your server. Close the registry editor.
OK, the ReadMe instructions do fix the IIS MMC problem, but I still can't call aspnet_regiis.exe -i successfully. I keep getting the errors as described by PaulSB whenever I run it manually, and ASP.NET does not respond to any requests for .aspx pages. I've
now tried this on two separate Windows 2003 machines, with the same results. A few more details: 1) I ran the MDAC 9 beta installer first (from the /wcu directory); 2) I ran DotNetFx from the /wcu directory; 3) that's all I did Also, I noticed that there are
actually two different v2.0.x entries in my registry: v.2.0.40301.0 and v.2.0.40301.9; they BOTH display in the IIS MMC snap-in Properties dialog for the website in question. So, has anyone actually been able to run ASP.NET 2.0 without using the VS.NET personal
web server? /s/ James
I can run it with IIS, I use Windows XP. Check if you have "Allowed" ASP.Net application to run in your IIS. Is that doesn't work, run the setup and repair your installation or reinstall it from the setup file. Let it install the MDAC9 and DotNetFx for your
etc.
Well, this is getting stranger by the minute. First, I have now installed VS.NET 2005 on these two Windows 2003 machines, and I can successfully compile and run a web project using the Personal Web Server on the randomly-generated port number that web server
uses. However, if I point IIS at the same directory, I get application errors ("Page not Found"). I still cannot run aspnet_regiis -i without getting an error, but all of those errors pertain to the WebAdmin directory, so I thought based on the ReadMe and
other posts that that problem doesn't stop me from getting IIS to actually run the aspnet_filter.dll and hand requests for .aspx pages off to ASP.NET. However, since I'm still getting "Page not Found" errors, I think I am wrong in this assumption. Second,
Frederik, if you don't mind my asking, can you confirm the following things to me, please: 1) When you do an aspnet_regiis -lv (those letters are 'ell' and 'vee'), you should see a list of versions of ASP.NET you're running. Do you see one v2.0.40301.x or
do you see two? I see two: v2.0.40301.0 and v2.0.40301.9. I don't really understand that (it also appears in my HLKM\... registry entries where I was supposed to fix the full path in order to fix the MMC problem). 2) When I attempted to install VS.NET 2005
(successfully), the installer indicated that Framework 2.0 was installed *TWICE*. I think it figured this out from the Registry, probably from the same HKLM/... hive the ReadMe points to. 3) I noticed that the registry keeys for v2.0.40301.0 are MUCH more
extensive than the v2.0.40301.9 keys; they include things like DefaultDoc and other keys not present in the v2.0.40301.9 hive. Can you confirm whether you have this also, or whether you have only one hive, and if so, how many keys are in there? [I have tried
renaming the v2.0.40301.9 hive and the .0 hive, swapping them, removing one, etc. Nothing seems to work here.] 4) Your recent suggestion was to make sure "ASP.Net is "Allowed" to run in your IIS"--I assume you meant to check that the ISAPI panel of the IIS
config for the website was properly set up to show the "aspnet_filter.dll" Or is there something else I should be doing? Thanks to everyone for help. This is getting truly frustrating! Best, /s/ James
I've made some more progress in tracking this down: I just installed IIS on my XP Pro box, the one from which I've been developing, and even though aspnet_regiis -i returned the same errors as it does on my Windows 2003 machines, when I try to access a website
on my XP Pro machine, I have no problem getting the .aspx files to execute. So maybe we're dealing with a Windows Server 2003-specific problem here?? Other notes: if I look in my XP Pro c:\windows\microsoft.net\framework\ directory, I have these version folders:
v1.0.3705/ v1.1.4322/ v2.0.40226/ <-what's this?! v2.0.40301/ The v2.0.40226 directory is now on the Windows 2003 machines, and this XP box never had the original (Whidbey) toolset on it, so there's no v1.2.x directory. Just to be clear, when I run aspnet_regiis
-i, I'm calling the one in the v2.0.40301 directory. Any further thoughts, folks? Thanks! /s/ James
I haven’t tried to run aspnet_regiis on my machine without using the
ASP.Net switcher. I have two keys in the registry. I don't know what folder v2.0.40226/ is used for, it only contains a registry key settings for the helper. What I meant about “Allow” running ASP.Net on your Win 2003 machine is that there is a setting
where you can for example allow ASP to run on your computer etc. I don’t remember where these settings are located but probably in the IIS settings. I don’t have Win 2003 installed on my computer and I will not get back to work until Tuesday.
Just wanted to say "THANK YOU SO VERY MUCH FOR THIS LOVELY THREAD!!!" I reinstalled xp, reinstalled just about everything, and the properties window in my IIS didn't pop up. I started getting very very angry, and couldn't for the life of me figure out what
was going on. Came to this thread, and the regkeys were exactly on target. *sigh* I almost had a heart attack thinking I had to restore my whole harddrive, and that wasn't making me a happy person. Again, thanks for everyone who contributed to this thread.
jgbeldock
Member
100 Points
20 Posts
regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 07, 2004 02:56 AM|LINK
Fredrik N
All-Star
29674 Points
5334 Posts
MVP
Re: regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 07, 2004 04:29 AM|LINK
MVP, ASPInsider, WCF RIA Services Insider
My Blog
paulsb
Member
40 Points
8 Posts
Re: regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 09, 2004 09:08 PM|LINK
Fredrik N
All-Star
29674 Points
5334 Posts
MVP
Re: regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 09, 2004 09:33 PM|LINK
MVP, ASPInsider, WCF RIA Services Insider
My Blog
jgbeldock
Member
100 Points
20 Posts
Re: regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 09, 2004 11:22 PM|LINK
Fredrik N
All-Star
29674 Points
5334 Posts
MVP
Re: regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 10, 2004 06:48 AM|LINK
MVP, ASPInsider, WCF RIA Services Insider
My Blog
jgbeldock
Member
100 Points
20 Posts
Re: regiis failing after 2.0 installation; errors in App Log looking for FW 1.2?!
Apr 10, 2004 05:45 PM|LINK
jgbeldock
Member
100 Points
20 Posts
This may be a Windows 2003 problem... (was Re: regiis failing after 2.0 installation; errors in A...
Apr 10, 2004 06:40 PM|LINK
Fredrik N
All-Star
29674 Points
5334 Posts
MVP
Re: This may be a Windows 2003 problem... (was Re: regiis failing after 2.0 installation; errors ...
Apr 10, 2004 10:21 PM|LINK
MVP, ASPInsider, WCF RIA Services Insider
My Blog
KraGiE
Star
14567 Points
2926 Posts
Re: This may be a Windows 2003 problem... (was Re: regiis failing after 2.0 installation; errors ...
Apr 11, 2004 09:08 AM|LINK