GoDaddy

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

Re: GoDaddy

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.

Re: GoDaddy

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

<?xml version="1.0"?>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

</connectionStrings>

<!--

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:

-->

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

-->

</assemblies>

</compilation>

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

-->

<!--

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:

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

-->

<!-- GLOBALIZATION

This section sets the globalization settings of the application.

-->

</system.web>

</configuration>

Re: GoDaddy

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 !

Re: GoDaddy

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

Re: GoDaddy

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:

Re: GoDaddy

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

Re: GoDaddy

They recently added it.

Re: GoDaddy

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

Re: GoDaddy

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.

Re: GoDaddy

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

Re: GoDaddy

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.

Re: GoDaddy

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 the tables&procedures and 1 for the data (try not to script the data in the DB for photos - will bring everything to a standstill). Then you have to go thru the entire tables/procedures script and move any GOTO statements up to the row before (this is very important). The copy and paste that entire edited script up to the hosted database using the tool provided. You should not receive any errors when that tool runs. Then copy and paste script for the data into the tool. Then copy all your asp files up to the host. Make sure you have already added yourself as an administrator before the upload - so that you don't have to go thru any additional steps to add yourself or your roles on the hosted db.

Good luck.

http://MarValus-Domains-Hosting.com

ClubSite: http://DisciplesOnDirt.com

I'll be working on the small business starter kit myself in a couple weeks - so if you're still stuck I will try to help you more.

Re: GoDaddy

Good point on #1. I too was getting mighty disappointed trying to get the connection string working with Godaddy.

They finally gave me this little script that proved my connection string was correct:

mysqltest.aspx

<%@ Import Namespace="System.Data.SqlClient" %>
<%
Dim oSQLConn As SqlConnection = New SqlConnection()
oSQLConn.ConnectionString ="Server=whsql-v09.prod.mesa1.secureserver.net;uid=dbasolutions;pwd=*****;database=DB_87972;"
try
oSQLConn.Open()
catch dag as exception
response.write(dag.message)
End try
Response.write("Connection Open!")
%>

When this worked, I finally realized the program was not being recompiled on Godaddy. After recompiling locally, I was able to get it to work. Is there a setting in the config file to allow recompile on the server?

(btw: I am moving away from Godaddy since they are not asp.net friendly.)

Bill

Re: GoDaddy

Hi MarValUS,

I really appreciate the effort you have gone to so far, but I have not had success yet with your instructions. Here is what I have done to date:

Using Visual Studio 2005, SQL Express 2005 locally

1: Built site locally and tested all aspects working fine. Added myself as administrator at this point. I did not modify the content of the site in any way.

2: I am not sure what you mean by "Did you create all the DB tables and Procedures?"

3: Downloaded and ran the SQL Server Database Publishing Wizard and ran this through VS 2005 against my local copy of "Club.mdf"

Settings here were:

Drop existing objects in script = True

Schema qualify = True

Script for target database = SQL Server 2000 (the SQL Database on GoDaddy says it is version 2000)

Types of data to publish = first run through I chose Schema only, and the second time (separate target file) Data only

I can provide the output of these files if it helps. One thing I noted is that there are no GOTO statements in either of these scripts. Plenty of GO statements though.

4: Created a new SQL DB on my GoDaddy account. ASP 2.0 enabled.

5: Copied and pasted the contents of the schema script file into the GoDaddy SQL Server Web Admin tool. I got no errors with either script.

6: Edited the ConnectionStrings section of the web.config file to read:

7: Uploaded all files to GoDaddy. Every page gives me "an application error has occurred".

So far I have got 2 support replies from GoDaddy. #1: "Rename Default.aspx to default.aspx" and #2: "Unfortunately, we will be unable to assist you as this is a scripting error" which is nice since GoDaddy suggests this Clubsite, and Microsoft lists GoDaddy as the #1 host to use for this Clubsite.

If anyone has had success with this Clubsite on GoDaddy, I would love to hear from you.

Re: GoDaddy

I am going to answer myself here [;)]

What I had forgotten to do was to Rebuild the website locally, with the web.config file modified to suit the GoDaddy database information ie:

Server=p3swhsql-v02.shr.phx3.secureserver.net; ....etc

and then upload the files to GoDaddy.

At this point in time - I am quite amazed to say - everything I have checked so far is working except that I cannot login using the administrator role which I created locally earlier.

Re: GoDaddy

After the rebuild do you have to do anything other than ftp the files to Godaddy?

Thank,

Re: GoDaddy

Here is my working web.cong. Here are the steps I followed on Go Daddy

1. First, get a copy of the Go Daddy Walkthrough post on this site
2. Create your DB on Go Daddy using their SQL tool. Note the user name and password you use to create teh DB
3. Using the create scripts in the CSK, create your table, sp's, etc. changing the dbo ownership in the scripts to the ID you used to create your DB on Go Daddy.
4. Use the Go Daddy Walk Through to add your Admin ID
5. Modify your web.config to use the proper Go Daddy server, etc.
6. Post your site. I used VWD and just FTP'd it up.

Here is my working web.config.
<?xml version="1.0"?>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<!--<location path="Files.aspx">

<system.web>

</authorization>

</system.web>

</location> -->

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

<system.web>

</authorization>

</system.web>

</location>

</connectionStrings>

<system.web>

</assemblies>

</compilation>

</providers>

</siteMap>

</system.web>

<system.net>

</defaultProxy>

</system.net>

<system.net>

<network

host="relay-hosting.secureserver.net"

port="25"

defaultCredentials="true"

</smtp>

</mailSettings>

</system.net>

</appSettings>

</configuration>

Re: GoDaddy

I"m having trouble launching my site locally as well as accesing the asp.net applications. here's a copy of my web.config. Does godaddy.com allow remote access or not?

thanks,

jay0555

<add name="ClubSiteDB" providerName="System.Data.SqlClient"

connectionString="server=whsql-v21.prod.mesa1.secureserver.net;

database=DB_146614;

uid=xxxxxx;

pwd=xxxxxx"/>

<add name="LocalSqlServer" providerName="System.Data.SqlClient"

connectionString="server=whsql-v21.prod.mesa1.secureserver.net;

database=DB_146614;

uid=xxxxx;

pwd=xxxxx"/>

</connectionStrings>

Re: GoDaddy

No GoDaddy doesn't allow remote access. To run your site locally you have to change your connection string to connect to your local DB. To look at/ connect to your live DB you have to use their DB manager tool. I wish they would chage to allow remote access, it would be a lot easier but also more chance of the DB getting hacked.