User specific settings not being saved

Hi,
Which data source type do you use (SQL Server, DVLS, Cloud)?

Regards

Hi, we use Devolutions server with a MS SQL server database backend.

What DVLS version do you use?

Hmm, v3.0.2.0 it looks like. Seems like 3.1.0.0 may have a fix for this issue according to the release notes, so we'll try upgrading. :)

http://server.devolutions.net/Home/ChangeHistory

Actually, my IT guy says he tried to install 3.2.0 the other week and ran into a problem with AD authentication afterwards, and had to roll back. We are looking for the 3.1.0 download but it looks like the page http://server.devolutions.net/Home/PreviousVersion is not maintained with previous releases?

Hello,

Please contact us at support@devolutions.net to book a remote session.


Best regards,

Hi, we get the following error in the event viewer on DVLS version 3.2.0.0 - no users are able to authenticate. We don't get this with 3.1.0 so we'll stick with this for now and worry about this one later. Might be we just have to RTFM... :)


Exception information:
Exception type: TargetInvocationException
Exception message: Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Owin.Loader.DefaultLoader.<>c__DisplayClass12.<MakeDelegate>b__b(IAppBuilder builder)
at Owin.Loader.DefaultLoader.<>c__DisplayClass1.<LoadImplementation>b__0(IAppBuilder builder)
at Microsoft.Owin.Host.SystemWeb.OwinAppContext.Initialize(Action`1 startup)
at Microsoft.Owin.Host.SystemWeb.OwinBuilder.Build(Action`1 startup)
at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
at System.Threading.LazyInitializer.EnsureInitializedCore[T](T& target, Boolean& initialized, Object& syncLock, Func`1 valueFactory)
at Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication context)
at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

Could not load file or assembly 'Microsoft.Owin, Version=2.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
at Owin.WebApiAppBuilderExtensions.UseMessageHandler(IAppBuilder builder, HttpMessageHandlerOptions options)
at Owin.WebApiAppBuilderExtensions.UseWebApi(IAppBuilder builder, HttpConfiguration configuration)

Hello,

Have you followed these instructions from our Online Help about Upgrading to Devolutions Server version 3.2?

Like I wrote previously, could you please contact us at support@devolutions.net? We want to offer you a remote support session to troubleshoot this issue.

Best regards,

Hello,

We appreciate the offer, but we'll likely figure this out by reading the documentation properly. We'll let you know if we are completely unable to sort it out, though. :)

Hi, FYI we were able to fix the authentication issue. Here's the problem we were seeing, which wasn't clearly stated in the update documentation, you may want to update that specific section based on the information below:

While all users had their 'AuthenticationType' column value set to NULL in the database, they could not authenticate. This falls into the second cause at http://helpserver.devolutions.net/index.html?upgrade_dvls32.htm - what is not mentioned in the documentation is that if you only have one authentication type selected on your data source, the dropdown for changing the type as indicated in the upgrade steps is not available (which kind of makes sense when you only have one type selected in the DS settings anyway). To address this, temporarily enable one of the other authentication types (DVLS custom, local, or database) to enable the dropdown, which allows saving the user accounts. Or just set the AuthenticationType column in the DB to 3 for all domain accounts, which we ended up doing.

Also, we found that we had to prefix the domain accounts in the database with the domain NETBIOS name - the UPN (user@domain.loc) was not recognized and the account auto-provision would create NETBIOS\user regardless of our selection, causing mismatch between the UserSecurity and UserProfile tables. After setting the domain name to the NETBIOS name on the DS, and updating all users as NETBIOS\user in the database, everything is working fine. :)

Thank you very much for this post. We ran into this issue as well, and this helped us resolve the problem quickly.