Godaddy hosting troubles

Last post 03-17-2008 1:29 PM by smaddaloni. 4 replies.

Sort Posts:

  • Godaddy hosting troubles

    03-15-2008, 12:09 AM
    • Member
      point Member
    • smaddaloni
    • Member since 03-14-2008, 11:46 PM
    • Posts 17

    Hey people,

        I just recently started developing websites (really just 3 weeks) so please excuse me if my terminology for different things isn't correct. I have developed the website using visual web delevoper 2005 and the server-side I am using is ASP.NET 2.0. In VWD I used the login controls they made available and by using those it created a ASPNETDB.mdf. I also created my own database using VWD called Customers.mdf. Everything works perfect when I am testing it locally but when I FTP'd it that when things went bad. I have been having problems here and there but his one I am at a loss. I am very new to this so sometimes I have a hard time of seeing how different things work together. Here is the error after I turned the customerrors=Off:

    Server Error in '/' Application.

    An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

    Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

    Source Error:

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

    Stack Trace:

    [SqlException (0x80131904): An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]
       System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739123
       System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
       System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +685966
       System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +109
       System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +383
       System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181
       System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
       System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130
       System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
       System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424
       System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
       System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496
       System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
       System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
       System.Data.SqlClient.SqlConnection.Open() +111
       System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84
       System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197
       System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Boolean updateLastLoginActivityDate, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved, DateTime& lastLoginDate, DateTime& lastActivityDate) +1121
       System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +105
       System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42
       System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +83
       System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +160
       System.Web.UI.WebControls.Login.AttemptLogin() +105
       System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +99
       System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35
       System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115
       System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163
       System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
       System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
       System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33
       System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102

     

     

    I thought it might be the connection string in the web.config file. but everything looks fine. Here is the strings I am using:

    <add name="ConnectionString" connectionString="Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=OCService; User ID='user'; Password='password' Integrated Security=True; User Instance=True"

    providerName="System.Data.SqlClient" />

    <add name="ASPNETDBConnectionString1" connectionString="Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=APServices; User ID='user'; Password='password'; Integrated Security=True; User Instance=True"

    providerName="System.Data.SqlClient" />

     I have also used the strings above without the:

    Integrated Security=True; User Instance=True

    on the end.

     

    Here is what godaddy gives me to use as a string along with other options which I have tried the last one:

    • ODBC:
    • Driver={SQL Server}; Server=p3swhsql-v14.shr.phx3.secureserver.net; Database=APServices; Uid=APServices; Pwd='your password';
    • OLE DB, OleDbConnection (.NET):
    • Provider=sqloledb; Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=APServices; User ID=APServices; Password='your password';
    • SqlConnection (.NET):
    • Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=APServices; User ID=APServices; Password='your password';

    If someone could help me out with this problem I would be forever in their debt. Thanks SteveO

  • Re: Godaddy hosting troubles

    03-15-2008, 5:35 PM
    • Member
      point Member
    • smaddaloni
    • Member since 03-14-2008, 11:46 PM
    • Posts 17

    Just checking back to see if anyone new anything about this. I also forgot to add that I only get this message when I am trying to login, create a new account, or anything that has to do with connecting to the database. The default page and public access pages I added work fine. Godaddy has told me it is my problem and that I need to figure it out but I don't see how that is when I have used their connection string that they gave me and it works fine on my local machine. I also used the database publishing wizard to move my databases over. That seemed to work fine all the tables and rows I created are there. Anyway if anyone could help I would appreciate it. Thanks

  • Re: Godaddy hosting troubles

    03-15-2008, 8:21 PM
    • Member
      point Member
    • smaddaloni
    • Member since 03-14-2008, 11:46 PM
    • Posts 17

    Nevermind I found the answer to my own question after some digging. Anyways, thanks me !

  • Re: Godaddy hosting troubles

    03-17-2008, 6:31 AM

    Hi

    It would be very helpful if you can post your solution here. your experience can be beneficial to other community members reading the thread. Thanks for your kind support

    Best Regards
    XiaoYong Dai
    Microsoft Online Community Support

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
  • Re: Godaddy hosting troubles

    03-17-2008, 1:29 PM
    Answer
    • Member
      point Member
    • smaddaloni
    • Member since 03-14-2008, 11:46 PM
    • Posts 17

    Sorry about that. I was going to and completely forgot. B y the way I have to databases that I am accessing that is why there are two. Godaddy doesn't tell you this but you have to set up the connection string like this:

    <connectionStrings>

    <add name="ConnectionString" connectionString="Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=Database1 User ID='userid1'; Password='password1'; Trusted_Connection=False"

    providerName="System.Data.SqlClient" />

    <remove name="LocalSqlServer"/>

    <add name="LocalSqlServer" connectionString="Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=Database1; User ID='userid1'; Password='password1'; Trusted_Connection=False"

    providerName="System.Data.SqlClient" />

    <add name="ASPNETDBConnectionString1" connectionString="Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=Database2; User ID='userid2'; Password='password2'; Trusted_Connection=False"

    providerName="System.Data.SqlClient" />

    <remove name="LocalSqlServer"/>

    <add name="LocalSqlServer" connectionString="Data Source=p3swhsql-v14.shr.phx3.secureserver.net; Initial Catalog=Database2; User ID='userid2'; Password='password2'; Trusted_Connection=False"

    providerName="System.Data.SqlClient" />

    </connectionStrings>

Page 1 of 1 (5 items)