rdigernes

Hello,

I noticed (as the curious technician I am :p) the most recent changelog stating "added multi-domains support". However, I cannot seem to find any updated information or documentation about it. We currently use AD-authentification with our own domain users.

Sounds very interesting as we are currently working on separate internal domains for tightening security.

Any light to shed? :)

I can confirm that this was an issue also for our setup. Whether or not this is an RDM issue, or related to how Windows Server 2012 R2 initially manages this service - I cannot say.

hi,

i installed a new 2012r2-server for new DVLS and got a few problems.

one was that asp-service was not set to automatically -> it has to be changed to automatically by me.

by default asp-service is set to manually.

can you check/set this in your setup-routine or describe it on your installation-help-page?

regards

markus

Latest version (2.5.2.0) now successfully downloaded and installed with no errors. Thanks for Your help!

After running the fix, the upgrade worked successfully. As for our production instance, just to be safe, I'll wait until the next release is available. Will then run an upgrade on our staging source first.

Thank you for solving the matter quickly!

I'll let you know the result as soon as I'm back at work (It's evening over here, and international labor day tomorrow). Thanks for the quick responses so far!

Thanks! Out of the blue, two things come to mind:

We are using a custom user on this server only, just for the purpose of RDM. So far it has worked splendidly, as the same user name and password is used for windows server login, admin rdm-login (for the rdm client on the server), and also sql sysadm as well as iis context, which is also on the same server. We did this to simplify troubleshooting for any eventual events like this. The user has, naturally, administrator rights on the server, but not the whole domain.

Secondly, as we're stationed in Norway we use the danish/norwegian charset on the sql-server.

Still, doesent seem related to the problem at hand. Just fyi.

Thanks for your swift reply!

We've had a fully working solution on the previous Version of RDMS for months, with all documentation and requirements checked and double checked - I haven't seen any documentation stating any new requirements for 2.5.0.0 compared to 2.2.21.0?

Or am I missing something? We are, as you assumed correctly, on 2012 R2.

Hello,

I'm having a hard time upgrading my data Sources from 2.2.21.0 (RDMS) to 2.5.0.0 (Devolutions Server). I started With updating the RDM-Client installed on the server (With IIS and SQL also on the same server), successfully to 10.5.4.0. When upgrading the data Sources (through the now called 'Devolutions Server - Console') the only options is through a recently downloaded .zip-file (as the web-Upgrade doesen't seem to fetch anything other than 2.2.21.0).

Luckily, we have two data Sources where as one of these is our test instance - this is what i first attempted to Upgrade. Our Production data Source is still working for Our users at Version 2.2.21.0.

The following output is showed when trying to Upgrade:

*****

Starting upgrade...

Backing up the configuration...Done!

Backing up files...Done!

Unzipping content...Done!

Removing previous content...Done!

Installing content...Done!

Upgrading database for data source 'RDM - Testmiljo' with version 185

ERROR:System.Data.SqlClient.SqlException (0x80131904): XML parsing: line 1, character 26, end tag does not match start tag

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.ExecuteNonQuery(String sql, IDbConnection dbConnection, IDbDataParameter[] parameters, Int32 commandTimeout)

at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.ExecuteScript(String script, IDbConnection connection)

at Devolutions.RemoteDesktopManager.Business.DatabaseUpgradeAction.Execute(DatabaseConnectionDataSource dataSource)

at Devolutions.RemoteDesktopManager.Business.DataSources.DatabaseConnectionDataSource.Upgrade(Boolean silent, LogMessageDelegate logMessage)

ClientConnectionId:8ffc2197-f73b-4eb4-ad02-692fa3ee2d1a

Error Number:9436,State:1,Class:16

Upgrading database...Error!

Restoring the configuration...Done!

Restoring the custom folder...Done!

Upgrade completed [1 error(s)]!

*****

After a reboot of the server, I can, in fact, Connect to the newly upgraded data Source, but subsequent update attempts result in the same error which I'm not very comfortable With.

Any idea on where to start?

In the datasource an option is available to use Integrated Security but you will still have to add these users to RDM.

When adding the users to RDM you will have to choose Integrated Security also and you can choose to create the SQL Server login and user as well but you may be able to opt out when the users already exist (for example via a Windows Group. Opting out of creating the SQL Server logins and users is something we still have to test - the rest I've implemented succesfully.

Unfortunately, Integrated Security doesen't exist for RDMS - only SQL :|

OK Maurice, it would simplify things greatly for us. I understand I can use %username% at least in the 'Username' field on the data source, so at least that's taken care of.

Hello,

I have been trying to search the forum for related topics, but I cannot find anything conclusive on this matter. We are in the process of configuring our RDMS/RDM system, and would like the RDM Client (locally installed or otherwise) to use local Windows credentials to authenticate the RDMS data Source. Isn't this possible?

Since we're using AD-credentials to authenticate, it seems like unnessecary work to type the currently used credentials every time the client connects to the data source. As a security precaution, we would at the same time like to force users to only be able to supply their own currently cached windows-credentials.

Any hints or tips?