I used VS2005 to modify the "Club Website Starter Kit" changing only the text and ascetics.  It works and looks great on my own computer but when I upload it the GoDaddy, It won't run.  I get this:

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>

I am new and my research into this problem has provided no solution, and GoDaddys tech support is of no help... anyone know what I need to do?  Any help would be appreciated.

Thanks

Hi,

change the web.config on the server like stated in the error message (set the mode="Off" in the <customErrors> element). This gives you the real error message of what's going on.and gives you more insight of what the exact problem is.

Grz, Kris.

It is off, but still says the same thing.  here is my web.config:

<?xml version="1.0"?>

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

<location path="events_edit.aspx" >

<system.web>

<authorization >

<allow roles="Administrators"/>

<deny users="*"/>

</authorization>

</system.web>

</location>

<location path="locations_edit.aspx" >

<system.web>

<authorization >

<allow roles="Administrators"/>

<deny users="*"/>

</authorization>

</system.web>

</location>

<location path="news_edit.aspx" >

<system.web>

<authorization >

<allow roles="Administrators"/>

<deny users="*"/>

</authorization>

</system.web>

</location>

<location path="photoalbum_new.aspx" >

<system.web>

<authorization >

<allow roles="Administrators"/>

<deny users="*"/>

</authorization>

</system.web>

</location>

<location path="member_list.aspx" >

<system.web>

<authorization >

<deny users="?" />

</authorization>

</system.web>

</location>

<location path="member_details.aspx" >

<system.web>

<authorization >

<deny users="?"/>

</authorization>

</system.web>

</location>

<connectionStrings>

<add name="ClubSiteDB" connectionString="Data Source=.\SQLExpress;Integrated Security=true;AttachDBFileName=|DataDirectory|clubsite.mdf;User Instance=True" providerName="System.Data.SqlClient"/>

<remove name="LocalSqlServer" />

<add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true" providerName="System.Data.SqlClient" />

</connectionStrings>

<appSettings>

<!--

The <appSettings> section is used to configure application-specific configuration

settings. These can be fetched from within apps by calling the

"ConfigurationSettings.AppSettings(key)" property:

<add key="connectionstring" value="server=localhost;trusted_connection=true;database=pubs"/>

-->

</appSettings>

<system.web>

<!--

DYNAMIC DEBUG COMPILATION

Set compilation debug="true" to insert debugging symbols (.pdb information)

into the compiled page. Because this creates a larger file that executes

more slowly, you should set this value to true only when debugging and to

false at all other times. For more information, refer to the documentation about

debugging ASP.NET files.

-->

<roleManager enabled="true"/>

<authentication mode="Forms"/>

<compilation debug="false" strict="true">

<assemblies>

<add assembly="System.Xml, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>

<add assembly="System.Messaging, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

<add assembly="System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>

</assemblies>

</compilation>

<membership defaultProvider="AspNetSqlMembershipProvider" />

<siteMap defaultProvider="AspNetXmlSiteMapProvider" enabled="true">

<providers>

<remove name="AspNetXmlSiteMapProvider" />

<add name="AspNetXmlSiteMapProvider"

description="SiteMap provider which reads in .sitemap XML files."

type="System.Web.XmlSiteMapProvider"

securityTrimmingEnabled="true"

siteMapFile="Web.sitemap" />

</providers>

</siteMap>

<!--

The <sessionState> section is used to configure session state for the application.

It supports four modes: "Off", "InProc", "StateServer", and "SqlServer". The

later two modes enable session state to be stored off the web server machine -

allowing failure redundancy and web farm session state scenarios.

<sessionState mode="InProc"

stateConnectionString="tcpip=127.0.0.1:42424"

sqlConnectionString="data source=127.0.0.1;trusted_connection=true"

cookieless="false"

timeout="20" />

-->

<!--

The <customErrors> section enables configuration of what to do if/when an

unhandled error occurs during the execution of a request. Specifically, it

enables developers to configure html error pages to be displayed in place of

a error stack trace:

-->

<customErrors mode="Off" />

<!--

The <authentication> section enables configuration of the security authentication

mode used by ASP.NET to identify an incoming user. It supports a "mode"

attribute with four valid values: "Windows", "Forms", "Passport" and "None".

The <forms> section is a sub-section of the <authentication> section,

and supports configuring the authentication values used when Forms

authentication is enabled above:

<authentication mode="Windows">

<forms name=".ASPXAUTH"

loginUrl="login.aspx"

protection="Validation"

timeout="999999" />

</authentication>

-->

<!--

The <authorization> section enables developers/administrators to configure

whether a user or role has access to a particular page or resource. This is

accomplished by adding "<allow>" and "<deny>" sub-tags beneath the <authorization>

section - specifically detailing the users/roles allowed or denied access.

Note: The "?" character indicates "anonymous" users (ie: non authenticated users).

The "*" character indicates "all" users.

<authorization>

<allow users="joeuser" />

<allow roles="Admins" />

<deny users="*" />

</authorization>

-->

<!-- GLOBALIZATION

This section sets the globalization settings of the application.

-->

<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>

</system.web>

</configuration>

I have exactly the same problem,I did also set the customerror mode to"off" But still the same error !!
I by chance you solved the problem pleas email me the solution at okone@mdc.edu
or post it here so I could see it .Thank you. I think it has to be a better step by step guide to installing the Start kit !! This is too frustrating !
Thank you !

go daddy does not have framework v2.0 on their system

I ran into the same problem and just posted a question looking for answers too.  If you make the change to the web.config file like the error message suggests, you'll see (or at least in my case) a detailed error message indicating that there is a problem with SQL connecting.  Look for my post.  Hofully someone will respond to it and we'll both have working web sites.  This is the way I modified my web.config file:

<!--customErrors mode="RemoteOnly" defaultRedirect="ErrorPage.htm" /-->

<customErrors mode="Off" />

acc999 wrote:

Look for my post.  Hofully someone will respond to it and we'll both have working web sites.

It would be nice if you included the url to that particular post.

Grz, Kris.

They recently added it.

At the time I replied to this one it had not been  accepted by the moderator.  But, it now has so here is the link: 

http://forums.asp.net/1105411/ShowPost.aspx

Godaddy do not allow remote access, i have the same problem with the Classified Starter Kit,

I am on try-and-error mode with differents Web.Config.

Godday message for any problem with Sql Server connection =  

""Thank you for contacting customer support. The error relates to the fact that we do not provide the ability to use remote connections to our database servers. Sorry for any confusion.""

 

For more information on Medium trust level, see the MSDN article How To: Use Medium Trust in ASP.NET 2.0.

I went to the part in the aspx page that has

ConnectionString="<%$ ConnectionStrings:ConnectionString %>"

and changed it to

ConnectionString="Server=whsql-v05.prod.mesa1.secureserver.net;uid=myusername;pwd=******;database=DB_123456"

I'm not suggesting that this is the 'final answer'.  I'm still working to try and make it work with the ConnectionString (instead of the surgical bypass written above), but I've had no luck so far, even though GoDaddy supplies code to write in that I would have thought should have worked easily.

I'm looking for other GoDaddy newbies (ASP.NET / VWD 2005 EE / SQL Server) to collaborate with as we work on these sort of things.

-Larry

 

posting experience here with godaddy.

Trying to get the the small business starter kit running. On godaddy with ASP.NET 1.1 i get the need to turn the customError="Off" message but my web.config says it is "Off" (capital Oh). With ASP.NET 2.0 i get Server unavailable. Got a response from godaddy.com and they said that the site is crashing the ASP.NEt application pool as it is exceeding the allocated resources per site. This is ridiculous as the site itself to include images is 700 kilobytes!!.. Less than a damn floppy and they can allocate resources for that?..... sorry I am shopping for another vendor at this point as I got numerous servers to include an ARCHAIC PII400 with 512 MB of ram and it works fast on that!!

 

<-- not happy with godaddy at this point.

Without knowing what you've done so far it's kind of hard to pinpoint the problem, but I will try to help.

1-Did you make sure site would build on your local server before copying any files?  2- Did you create all the DB tables and Procedures?  3-Did you upload the data?  (I'm assuming you're using VisualStudio/VisualWebDeveloper)

I was going nuts trying to get my ClubSite going and ZOwen was great and clued me in to a wonderful tool for creating the scripts needed to create the tables, procedures and write the data.  All the problems I was having stemed from DB issues.  If you don't already have it - go get it- SQL Server Hosting Toolkit http://www.codeplex.com/Wiki/View.aspx?ProjectName=sqlhost

Once you've made sure you're site is working on your local host, create a brand new (MS SQL) DB. Ensure that you select the 2.0ASP shema.

Then use the script to run against YOUR working .mdf file.  Create 2 separate scripts - 1 for