David,
It's been three days and no startup errors with RDM not being able to see the SQL DB. Maybe RDM was starting up too fast and SQL had not completed starting its services.
Totally understand about moving session to private and or back to regular session as I only see that to be a one time move since prior to the private vault my connections were business and personal. Now with the PV then I should be able to move my personal connections to the vault and leave them there.
No worries about the printing to PDF as it's not a big deal to do the rename as I already do that with various print to pdf tasks.
Two things that I have recently noticed with the Private vault... I took my personal connections and moved them to the vault. I kept the original connections in place for a few days and then I deleted the original site folder with all connections. Once completed I went over to the vault and all of my connections which had a custom icon were show up up with an exclamation mark inside of a red circle. Only the connections with the default rdp icon were ok. the connections still worked but it lost the association to the custom icon. Once I restored the site, folders, and connections back to the sessions folder, closed RDM, and re-opened the custom icons came back.
second item was that I noticed that adding an expire date placed an extra icon (clock) in lower right of RDM. The Expired Entry List Report should show all sessions that have the expired date enabled and not just the sessions which have actually expired. Changing the report in this manner I believe will be helpful to print out and have. The report should look at production sessions and also have option for private as setting an expired date would be something an admin would setup for private and business sessions.
Now in setting up a test expired session for tomorrow in one of my private sessions it did something strange by taking the site folder and duplicating that but using the original site name and the creating a sub folder and then finally listing the session which now has the expired date.
So my original MSP folder was imported to private, renamed to MSP-2, then inside of the accounts folder I added an expire date to my FedEx session and saved it. Now I have a new MSP folder, a second accounts folder and then the FedEx session with expire date. So in adding the date it created a new main folder which is a site folder, then a sub folder and it basically moved it from MSP-2\ACCOUNTS to MSP\ACCOUNTS.
Felix
In reviewing the icons in the Help menu I ran across the View Application Log and below are the two instances where I had a problem connecting to my SQL Express DB on my PC:
[7/5/2013 4:07:16 AM]ERROR System.Data.SqlClient.SqlException: Cannot open database "RDM-2013" requested by the login. The login failed.
Login failed for user 'sa'.
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.GetData(String sql, IDbDataParameter[] parameters)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.GetDataSourceSettings()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadDataSourceSettingsFromDataSource(BaseConnectionDataSource newDataSource)
****************************** SqlError ******************************
Message:Cannot open database "RDM-2013" requested by the login. The login failed.
****************************** SqlError ******************************
Message:Login failed for user 'sa'.
[7/7/2013 12:56:58 PM]ERROR System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.GetData(String sql, IDbDataParameter[] parameters)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.GetDataSourceSettings()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadDataSourceSettingsFromDataSource(BaseConnectionDataSource newDataSource)
****************************** SqlError ******************************
Message:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
edited by fvigo1128 on 7/12/2013
It's been three days and no startup errors with RDM not being able to see the SQL DB. Maybe RDM was starting up too fast and SQL had not completed starting its services.
Totally understand about moving session to private and or back to regular session as I only see that to be a one time move since prior to the private vault my connections were business and personal. Now with the PV then I should be able to move my personal connections to the vault and leave them there.
No worries about the printing to PDF as it's not a big deal to do the rename as I already do that with various print to pdf tasks.
Two things that I have recently noticed with the Private vault... I took my personal connections and moved them to the vault. I kept the original connections in place for a few days and then I deleted the original site folder with all connections. Once completed I went over to the vault and all of my connections which had a custom icon were show up up with an exclamation mark inside of a red circle. Only the connections with the default rdp icon were ok. the connections still worked but it lost the association to the custom icon. Once I restored the site, folders, and connections back to the sessions folder, closed RDM, and re-opened the custom icons came back.
second item was that I noticed that adding an expire date placed an extra icon (clock) in lower right of RDM. The Expired Entry List Report should show all sessions that have the expired date enabled and not just the sessions which have actually expired. Changing the report in this manner I believe will be helpful to print out and have. The report should look at production sessions and also have option for private as setting an expired date would be something an admin would setup for private and business sessions.
Now in setting up a test expired session for tomorrow in one of my private sessions it did something strange by taking the site folder and duplicating that but using the original site name and the creating a sub folder and then finally listing the session which now has the expired date.
So my original MSP folder was imported to private, renamed to MSP-2, then inside of the accounts folder I added an expire date to my FedEx session and saved it. Now I have a new MSP folder, a second accounts folder and then the FedEx session with expire date. So in adding the date it created a new main folder which is a site folder, then a sub folder and it basically moved it from MSP-2\ACCOUNTS to MSP\ACCOUNTS.
Felix
In reviewing the icons in the Help menu I ran across the View Application Log and below are the two instances where I had a problem connecting to my SQL Express DB on my PC:
[7/5/2013 4:07:16 AM]ERROR System.Data.SqlClient.SqlException: Cannot open database "RDM-2013" requested by the login. The login failed.
Login failed for user 'sa'.
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.GetData(String sql, IDbDataParameter[] parameters)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.GetDataSourceSettings()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadDataSourceSettingsFromDataSource(BaseConnectionDataSource newDataSource)
****************************** SqlError ******************************
Message:Cannot open database "RDM-2013" requested by the login. The login failed.
****************************** SqlError ******************************
Message:Login failed for user 'sa'.
[7/7/2013 12:56:58 PM]ERROR System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.GetData(String sql, IDbDataParameter[] parameters)
at Devolutions.RemoteDesktopManager.Business.DataSources.SQLServerConnectionDataSource.GetDataSourceSettings()
at Devolutions.RemoteDesktopManager.Managers.ConnectionManager.LoadDataSourceSettingsFromDataSource(BaseConnectionDataSource newDataSource)
****************************** SqlError ******************************
Message:A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
edited by fvigo1128 on 7/12/2013