Publishing Orchard from VS2010

Topics: Troubleshooting
Aug 29, 2011 at 1:55 PM


I'm trying to publish my first Orchard site to a staging environment.  I'm using VS2010 and Orchard.Source.1.2.41

What I did was right click on Orchard.Web to publish, then copied the files to staging.  When I go to the address in the browser, I arrive at a parent directory and when I go into the Orchard directory I get the following Run Time Error.  Any help? 


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 -->

        <customErrors mode="Off"/>

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 -->

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


Aug 29, 2011 at 2:30 PM

I think what I really need is a "How To Publish Your Orchard Site Using VS2010 and Orchard.Source.1.2.41"....

Aug 29, 2011 at 3:39 PM

I now have the real error:


Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:

Line 85:             ASP.NET to identify an incoming user.
Line 86:     -->
Line 87:     <authentication mode="Forms">
Line 88:       <forms loginUrl="~/Users/Account/AccessDenied" timeout="2880"/>
Line 89:     </authentication>

Aug 29, 2011 at 6:49 PM

Is it possible that your target site is not configured to be an IIS application?

Aug 30, 2011 at 1:23 PM

yes it was totally an IIS issue....figured it out - thanks!