Last post Jan 30, 2006 04:59 PM by Baiju
Nov 14, 2005 08:02 PM|FMastro|LINK
I tried to search for this but the search function is very limited.
I'm having websites get this error now. (I own server so I can make needed changes), seems to be ever since I installed .net 2.0, but the it's been awhile since it was last accessed.
This is happening on multiple sites.
I've tried creating a get_ver file or something close in the root folder.
I ran the asp_regiis -i from 1.1 and from 2.0
I checked the mappings in the website and made sure that "verify file" was not checked.
I'm running out of ideas, I've gone down through 50 google searches looking for a solution.
Nov 15, 2005 04:20 PM|Baiju|LINK
Nov 15, 2005 08:16 PM|FMastro|LINK
I wish it was that simple, I really do.
Not only from trying that, once it went away when I restarted IIS after switching site to ASP 2.0 but then was replaced with a
And I've already gone through these links
So I give up, I think I'm gonna have to open a MS Ticket.
Nov 16, 2005 01:04 PM|Baiju|LINK
I have seen this if you have not run aspnet_regiis -i from 1.1 frame work directory.
Nov 19, 2005 09:45 AM|FMastro|LINK
Jan 30, 2006 02:25 PM|Satishr23|LINK
Jan 30, 2006 04:59 PM|Baiju|LINK
The VS2003 expects Asp.Net version 1.1.
Try running aspnet_regiis from Framework 1.1 directory. (normally windows\Microsoft.Net\Framework\1.1.xxx). Please see teh help of aspnet_regiis for parameters.