Publish Failed

[moondaddy]

I have a new VS 2005 web app project which compiles find and publishes fine
to a local directory. when I try to publish it to a remote server, it fails
almost instantly (2 or 3 seconds). So I created a new website on the server
(no files, just a site with a dedicated IP address). then I created a new
vs 2005 web site project (instead of a web app project) with only the
default file in it such as default.aspx. I published it to a local
directory and all went well. I published it to the new remote website and
it failed instantly. I'm not even being prompted for credentials which I
should be.

I'm really surprised in this day and age that MS doesn't provide any data
about the failure. any idea how I can begin to trouble shoot this?
firewalls and anti virus software should not be an issue in this case.

Thanks.

 

[Alex Meleta]

Hi,

I'm really surprised in this day and age that MS doesn't provide any
data about the failure.

See output view. There is a reason of failure.

Regards, Alex
[TechBlog] http://devkids.blogspot.com

 

[moondaddy]

Thanks that was a good tip. It said I needed to install front page server
extentions. So I installed them and I was then able to publish my test site
called TestPublish.

I was recently reading documentation on the new project styles in vs2005 and
one of the changes was that a vs2005 web site project (rather than a web app
project) doesn't need front page server extensions installed any more. this
contradicts the error I received.

does anyone want to comment on that?

now that I succeeded in publishing the site, I get the following error when
attempting to browse the default page. however, I'll start a new thread on
this.

Server Error in '/' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom
error settings for this application prevent the details of the application
error from being viewed remotely (for security reasons). It could, however,
be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable
on remote machines, please create a <customErrors> tag within a "web.config"
configuration file located in the root directory of the current web
application. This <customErrors> tag should then have its "mode" attribute
set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>


Notes: The current error page you are seeing can be replaced by a custom
error page by modifying the "defaultRedirect" attribute of the application's
<customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Hi,

I'm really surprised in this day and age that MS doesn't provide any
data about the failure.

See output view. There is a reason of failure.

Regards, Alex
[TechBlog] http://devkids.blogspot.com

I'm really surprised in this day and age that MS doesn't provide any
data about the failure. any idea how I can begin to trouble shoot
this? firewalls and anti virus software should not be an issue in this
case.

Thanks.

 

[Walter Wang [MSFT]]

Hi,

The web site mode only alters the way you author and debug the web
site/project, I don't think it alters the way we publish it. Could you
please point me to the document says so?

For the other issue, I've seen that you've solved that in the other thread.

Please feel free to let me know if you need anything else. Thanks.


Regards,
Walter Wang ([email protected], remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.