Good morning Forum -
I'm sorry if i show up with a question related to the one i had yesterday again. I still get sporadic error messages during setting up YaF. When I start the configuration, I can enter password etc, my database connection test is ok, i sometimes (!) can Initialize/Upgrade Database, and end up with the error messages below when I try Create Board...
Has no one ever encountered an error like that during setup?
Any help is appreciated!
Thanks - Peter

[SqlException (0x80131904): {...}
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +4846887
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +194
System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +4860189
System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +90
System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +376
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +221
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +189
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +185
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +31
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +433
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +499
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +65
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +117
System.Data.SqlClient.SqlConnection.Open() +122
YAF.Classes.Data.YafDBConnManager.get_OpenDBConnection() +39
YAF.Classes.Data.YafDBAccess.GetDatasetBasic(SqlCommand cmd, Boolean transaction) +64
YAF.Classes.Data.YafDBAccess.GetData(SqlCommand cmd, Boolean transaction) +70
YAF.Classes.Data.YafDBAccess.GetData(SqlCommand cmd) +6

ok i found what had happened...
first, the "via" protocol was still enabled for the server connection; seems that this leads to problems frequently.
second, for some reasons two connection strings are listed in db.config - and the first, though not the second, held the correct connection data. seems that the first is used for testing and up to a certain point - whereas the second is used from then on.
anyway, the forum is up and running now.
thanks for reading this issue, and maybe this solution helps in future cases.

the thread can be closed now...
regards, peter