Error uploading from VS 2003

[bruce]

Framework 1.1 is enabled on all our servers.

Do you have customerror enabled w/ Web.config in the root directory?

[b]quote:Originally posted by KPayne

I receive the following error message when attempting to use the Copy Project wizard to upload a ASP.NET application:

Visual Studio .NET has detected that the specified Web server is not running ASP.NET version 1.1. You will be unable to run ASP.NET Web applications or services.

Has .NET Framework 1.1 been rolled out, and if so, what should I do to get the Copy Project wizard to recognize it?

Keith Payne
Technical Marketing Solutions
</blockquote id="quote"></font id="quote">

[KPayne]

Bruce,

I am receiving the error in a messagebox when I click OK to begin copying the project files to the Web server. Does web.config affect that process? I do have CustomErrors enabled in the root of the application, which is a subweb. I do not have an application in the root web of my account.

Keith Payne
Technical Marketing Solutions

[KPayne]

I receive the following error message when attempting to use the Copy Project wizard to upload a ASP.NET application:

Visual Studio .NET has detected that the specified Web server is not running ASP.NET version 1.1. You will be unable to run ASP.NET Web applications or services.

Has .NET Framework 1.1 been rolled out, and if so, what should I do to get the Copy Project wizard to recognize it?

Keith Payne
Technical Marketing Solutions

[KPayne]

Thank you Bruce. I removed the custom error paths from the root web with the IIS Manager control panel tool and it worked.

Does this mean I cannot have custom errors enabled from now on?

Keith Payne
Technical Marketing Solutions

[bruce]

Point the custom error to an aspx page and it should work.

[b]quote:Originally posted by KPayne

Thank you Bruce. I removed the custom error paths from the root web with the IIS Manager control panel tool and it worked.

Does this mean I cannot have custom errors enabled from now on?

Keith Payne
Technical Marketing Solutions
</blockquote id="quote"></font id="quote">

[bruce]

>Does web.config affect that process?

It does matter.

When uploading or creating a project, VS.net 2003 makes an http call to a non existing page, get_aspx_ver.aspx, to get the http header. VS.net 2003 uses this as a mechanism to determine the version of the framework. See http://bluebones.net/news/default.asp?action=view_story&story_id=50

If the CustomError is enabled with web.config to direct all errors to an HTML page (or any page that are not mapped to ASP.net ISAPI), VS.net 2003 will not be able to determine the version of the framework and thus disallow the upload process.

Hope this helps/

[b]quote:Originally posted by KPayne

Bruce,

I am receiving the error in a messagebox when I click OK to begin copying the project files to the Web server. Does web.config affect that process? I do have CustomErrors enabled in the root of the application, which is a subweb. I do not have an application in the root web of my account.

Keith Payne
Technical Marketing Solutions
</blockquote id="quote"></font id="quote">

[jdoe2005]

Try this:

I tried ALL the solutions given by everyone. None of them worked. Finally I tried this and it has worked:

1. shut down ALL applications
2. Uninstall IIS 5.1
3. Reboot
4. Install IIS 5.1
5. Reboot
6. Find Microsft Knowledge Base Article - 306005
- follow the instructions as given.
7. Reboot
8. VS .net 2003 works for ASP and Web Services application.

The multiple Reboots is simply for safety.....and because it was easy that way and since it is Microsoft!

hope this helps.





[b]quote:Originally posted by KPayne

I receive the following error message when attempting to use the Copy Project wizard to upload a ASP.NET application:

Visual Studio .NET has detected that the specified Web server is not running ASP.NET version 1.1. You will be unable to run ASP.NET Web applications or services.

Has .NET Framework 1.1 been rolled out, and if so, what should I do to get the Copy Project wizard to recognize it?

Keith Payne
Technical Marketing Solutions
</blockquote id="quote"></font id="quote">

[bruce]

You can still have custom error, just point it to an aspx page (just not to a HTML, asp or other pages)

[b]quote:Originally posted by KPayne

Thank you Bruce. I removed the custom error paths from the root web with the IIS Manager control panel tool and it worked.

Does this mean I cannot have custom errors enabled from now on?

Keith Payne
Technical Marketing Solutions
</blockquote id="quote"></font id="quote">

[KPayne]

Bruce,

Thank you for following up on this thread. I apologize for not posting a final "Thank you, it worked.". So...

Thank you, it worked! [:D]

Keith Payne
Technical Marketing Solutions

[wuzhong]

Hello All,
I found this link is very helpful so solve our problems with running .aspx on IIS 5.1:

http://support.microsoft.com/default.aspx?kbid=306005&product=aspnet

I encountered this issue which annoyed me for days, and finally solved it by that link. Thank to someone who posted on another site.
Just bring it in hopefully someone can get help from it.

Zhong



[b]quote:Originally posted by KPayne

Bruce,

Thank you for following up on this thread. I apologize for not posting a final "Thank you, it worked.". So...

Thank you, it worked! [:D]

Keith Payne
Technical Marketing Solutions
</blockquote id="quote"></font id="quote">

[Remulac]

What worked for me was to uninstall both IIS 5.0 (running in 2000 professional) and the .NET 1.1 Framework. I then reinstalled IIS 5.0 from a Service Pak 4 disc, and then downloaded the .NET Framework from Microsoft's web site. I had already exhausted most options mentioned in this thread.


It looks like there are many different factors regarding this issue, and different things might work for different people in different situations (it would be nice to know what those factors are). Anyway, my two cents. Good luck!

[nigor]

Stop IIS. Run 'aspnet_regiis.exe - i' in yor 'C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322' or whatever else directory. Start IIS.