SSH after update is displaying stats blocking my view
Thanks. I was struggling to find this setting just now. Glad I found the thread by browsing the forum as I was having trouble describing the issue via search. I initially thought echo was broken until I noticed a new status bar had appeared!
Unable to save the user in the database
Hi Stefane,
Thanks for your work on this. I have finally had a chance to look into it properly. I still get the error even with the latest version. However, I suspect this is because I haven't followed your instructions exactly as I'm a bit confused with what is going on.
What I have done however is to start from scratch and have been able to create a fully working SQL Azure instance by doing the following. By logging onto the Azure SQL server master database via the web portal with the initial 'account creation' SQL login I:
- Created a new login for the Azure SQL server
- Created a user from that login for the Azure SQL server master database
- Created a new database on the Azure SQL server to hold the RDM entries
- Created a user from the login created earlier for this new database
- Granted that user the db_owner role for this database
- Created a new connection in Remote Desktop Manager entering the Azure server name, the server login created in the first step and the name of the database created in step 3
- On the upgrade tab clicked the 'Update Database' button to create the RDM tables
After doing the above I was able to connect to the Azure instance and start creating and removing entries.
I did a bit more testing and have noticed that you can't re-use an existing SQL server login with a new database. For example, I followed the steps above but instead of creating a new login in step 1 I re-used the existing one I created. If I don't create a new login I get the following error:
'Unable to save the user the database!'
'Invalid object name 'sys.sql_login'
Any reason for this?
Also, is there any advantage to letting RDM create the database for you in the Connection Manager window? I notice that if I let RDM create the database it uses the old 'Web/Business' tiers types instead of the new 'Basic/Standard/Premium' tiers.
Finally, is granting the 'db_owner' role giving too many permissions to the RDM database user and would read/write permissions be sufficient?
edited by nickterry on 12/29/2014
Unable to save the user in the database
Thanks
Unable to save the user in the database
Hi Stefane,
I have sent you the application logs.
Thanks.
Unable to save the user in the database
I'm trying to connect to a SQL Azure data source. I'm able to successfully test both the server and database and the RDM database has been created. However, when I click ok and try and use the data source I get the following message:
'Unable to save the user in the database!
Reference to database and/or server name in 'master.dbo.syslogins' is not supported in this version of SQL server.'
What could be the problem? I'm fairly sure the SQL permissions have been configured correctly.
RDM Freezing with SSH Entries
Sure. Unfortunately I experienced a freeze today with the new beta using some SSH sessions I haven't yet migrated over to the new settings so you may want to hold off updating.
RDM Freezing with SSH Entries
Thanks David. I've now installed the latest beta and will see how it goes. Good to hear SecureCRT integration is on the to do list.
RDM Freezing with SSH Entries
Yep, that seems to have done the trick! However, it would be nice to know whether the SecureCRT option I've mentioned is possible....David?
RDM Freezing with SSH Entries
I'm still experiencing freezing with 'Keep tab page opened on disconnect' checked. However, I'll give unchecking 'Close window on disconnect' a go; that should hopefully be the winning combination!
RDM Freezing with SSH Entries
Thanks foxtrot. I think I've found it: 'Keep tab page opened on disconnect'. I'll give it a try.
RDM Freezing with SSH Entries
Not sure if anyone else experiences this but I find, regardless of the version of RDM, that entries using the SSH Shell tend to lock up RDM causing me to end the program and re-launch. It tends to happen when connecting to devices over slower WAN links which have the tendency to drop packets although I've also experienced it on decent links too. I've started to switch (back) to SecureCRT for these connections if I'm using them frequently which doesn't have this issue. Am I right in saying that the SSH Shell is something external to RDM and therefore can't be fixed in the RDM code? If so, are there any alternative methods to use SSH in RDM? I haven't tried it but there's the SSH option but this appears to come with less settings (what's the difference between this and the SSH Shell by the way?). There's also Putty which I imagine would be more reliable. However, if going down that route I'd rather get RDM to launch SecureCRT than Putty as I prefer the former. Is it possible to create entries in RDM and get them to launch in SecureCRT much like the Web browser 'External' option? Or could SecureCRT open as an embedded session in RDM (this would be ideal)?
Why Purchase RDM Server?
Thanks Patrick. I can see the benefits of the 'proxy' nature of RDMS to the data source. With regards to the only other benefit of RDMS (correct me if this statement is wrong) am I right in saying that domain logons to the (MS SQL) advanced datasource are therefore controlled by ACLs in SQL server but if you have Remote Desktop Manager Server you can control logons directly in Active Directory (using AD groups)? But what if you created an AD group then gave that permissions to the database; wouldn't that achieve the same effect? Also, are we just talking about logons here or does it extend to more granular permissions (i.e. only allowing access to a certain part of the session list, for example)?
Why Purchase RDM Server?
I'm looking to purchase some RDM Enterprise licenses to use within our team. My question is, why would I also purchase Remote Desktop Manager Server along with these licenses? What benefits would I gain over just pointing Remote Desktop Manager directly to a SQL instance on a database server?