Visualizzazione dei risultati da 1 a 6 su 6
  1. #1

    Server Error in '/' Application.

    Ciao.
    come mai da questo errore?

    il sito è su un Hosting di Aruba...

    grazie tante...

    codice:
    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: 
    
    The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
    
    1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
    
      <%@ Page Language="C#" Debug="true" %>
    
    or:
    
    2) Add the following section to the configuration file of your application:
    
    <configuration>
       <system.web>
           <compilation debug="true"/>
       </system.web>
    </configuration>
    
    Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
    
    Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.  
    
    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.SqlRoleProvider.RoleExists(String roleName) +482
       System.Web.Security.Roles.RoleExists(String roleName) +242
       ASP.global_asax.Application_Start(Object sender, EventArgs e) +60
    
     
    
    
    --------------------------------------------------------------------------------
    Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
    La Gratitudine è la prima cosa nella vita...

    Grazie a tutti

  2. #2
    Ciao, anche se con qualche mese di ritardo, sto avendo il tuo stesso problema!!!!
    Come lo hai risolto???
    (non mi dire che hai trsferito il dominio....)

    grazie
    ciao
    Non dire gatto se non ce l'hai nel sacco! ATTIA!

  3. #3
    il problema deriva dal fatto che i domini in hosting aruba non hanno i permessi di connettività verso altri DB MSSQL che non siano quelli messi a disposizione e acquistati presso aruba stessa...

    ho risolto acquistando un server e configurando il mio hosting come DNS.... soluzione drastica, ma necessaria...

    ti auguro buona fortuna... ehehe
    La Gratitudine è la prima cosa nella vita...

    Grazie a tutti

  4. #4
    Questo lo sapevo, ma per le dimensioni di questo sito sto utilizzando un normalissimo db access che ho messo dentro la cartella mdb-database (come sempre).
    Quindi non riesco proprio a capire il problema. Per di più mettendo nella web.config il tag customerror="off" non mi visualizza la specifica dell'errore.

    Non so più cosa fare.

    grazie
    ciao
    Non dire gatto se non ce l'hai nel sacco! ATTIA!

  5. #5
    Utente di HTML.it
    Registrato dal
    Sep 2005
    Messaggi
    336
    Ciao.
    Mi sapresti dire come hai risolto.
    Ho il tuo stesso identico problema...

  6. #6
    non sono riuscito a risolvere.
    mi spiace.
    Non dire gatto se non ce l'hai nel sacco! ATTIA!

Permessi di invio

  • Non puoi inserire discussioni
  • Non puoi inserire repliche
  • Non puoi inserire allegati
  • Non puoi modificare i tuoi messaggi
  •  
Powered by vBulletin® Version 4.2.1
Copyright © 2026 vBulletin Solutions, Inc. All rights reserved.