Unable to connect to the database
Since the update to the new version we got a connection problem to the database sometimes..
this happens when domain accounts are used to use the integrated secruity option of the database (credential passthrough)
with normal sql accounts, the problem doesnt appear
i dont get any useful information out of the logs..
no windows logs or sql logs are generated to this event.
i can normally connect with the sql management studio on the server itself, firewall isnt a problem, because its not active
any help?
All Comments (7)
Hello,
Can you check in the logs of the SQL Instance to see if you have more information?
Thank you,
Maurice
I've checked the logs. The logs are not useful.. I've restarted the database and now i can connect.. but i dont know how long it takes until we get the next disconnect.
i can send you the SQL Logs for analysis if you want.
Hello,
Have you seen http://support.microsoft.com/kb/811889
Seems a bit involved, but may be the only thing we can try to help identify the issue.
Best regards,
Maurice
nothing has changed since weeks in our environment, so i guess thats not the problem. the only thing we did was the update to 10.1.3
Hi
Does the MSSQL happen to be member in a different domain?
Is there any way you could try inside a VM maybe, to run same RDM binary/portable version and with a older RDM binary/portable version and set RDM debugging level to full first. Is there any changes?
http://download.devolutions.net/Devolutions.RemoteDesktopManager.Bin.10.1.2.0.zip
http://download.devolutions.net/Devolutions.RemoteDesktopManager.Bin.10.1.3.0.zip
//Brandur
//Brandur
What version did you have before?
Maurice
I've checked both versions from Brandur, both got the same issue, sometimes it connects somtimes not.
For testing purposes i've installed the old version: 10.0.4.0
Its running fine without any issue.
@edit logs from a 10.1.3.0 version
System.Data.SqlClient.SqlException (0x80131904): Der Prinzipalname des Ziels ist nicht korrekt. Der SSPI-Kontext kann nicht generiert werden.
bei System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)
bei System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)
bei System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)
bei System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
bei System.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)
bei System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)
bei System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)
bei System.Data.SqlClient.SqlConnection.Open()
bei Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.GetData(String sql, IDbDataParameter[] parameters)
bei Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.GetDataSourceSettings()
bei Devolutions.RemoteDesktopManager.Managers.ConnectionManager.c29fbd34504079a3525ca4c390d5d4074(BaseConnectionDataSource cf40b69955d088020784eb92737f0a505)
ClientConnectionId:d4b09abf-920a-44c1-87b4-bb984ba8bc0e
edited by stein-it on 1/12/2015