0 votes

We have several webservices that interact with Adaxes through the ADSI interface. They have been configured and working with the 2013.2 version for several months. We just upgraded our Dev environment to 2014.1 and now we are unable to interact with the ADSI interface. We have updated our DLLs to 3.7.10510 (Softerra.Adaxes and Softerra.Adaxes.Adsi). The exception we are getting is thrown from the following code (that worked in the 2013.2 version):

IAdmNamespace ns = new AdmNamespace();
Service = ns.GetServiceDirectly(this.Host); //Host = our dev adaxes domain

and the exception is: Operation is not valid due to the current state of the object.
File name: 'Softerra.Adaxes.Adsi, Version=3.6.10109.0, Culture=neutral, PublicKeyToken=43a637781bd9a3c2'
at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean forIntrospection)
at System.Reflection.RuntimeAssembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.Load(String assemblyString)
at System.Runtime.Remoting.RemotingConfigHandler.RemotingConfigInfo.LoadType(String typeName, String assemblyName)
at System.Runtime.Remoting.RemotingConfigHandler.CreateChannelSinkProvider(SinkProviderEntry entry, Boolean bServer)
at System.Runtime.Remoting.RemotingConfigHandler.CreateClientChannelSinkProviderChain(ArrayList entries)
at System.Runtime.Remoting.RemotingConfigHandler.CreateChannelFromConfigEntry(ChannelEntry entry)
at System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData configData, Boolean ensureSecurity)
at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at IActiveDirectoryAccess.GetUserByLoginName(String loginName)
at ActiveDirectoryAccessClient.GetUserByLoginName(String loginName)

by (140 points)

1 Answer

0 votes
by (140 points)

Disregard this question. I had to update the dll version in the Softerra.Adaxes.Adsi.dll.config file also.

Related questions

0 votes
1 answer

Hello, after upgrading to 2014.1 the web interface is throwing lots warnings pertaining to groups: Failed to build a list of groups, in which user 'Some.Person@domain.local ... very noisy with these warnings. :) Has anyone else experienced this? Any ideas?

asked Aug 29, 2014 by EgotisticalGiraffe (350 points)
0 votes
1 answer

I'm moving from 2013.1 (on Server 2008 R2) to 2014.1 (on Server 2012 R2) and am going from a single server to 2 new servers and will shut down the 2013 ... be updated properly if their target object is moved or renamed. Would another reboot fix this possibly?

asked Aug 26, 2014 by danftasc (440 points)
0 votes
1 answer

Hi, I installed a new adaxes 2014.1 server and restore web interfaces from another server in 2013.2 When I uncheck Operations in Customize Operations windows, there is no ... fine on my 2 others Adaxes servers (in 2013.2) Thanks in advance Regards Sebastien

asked May 7, 2014 by smasset (730 points)
0 votes
1 answer

Hello, I think I might have found a regression. Starting 2014.1 it is impossible to change the reply address for a user having an Exchange 2003 mailbox. The button "Set ... related to my authorizations; I did test various configuration (admin, ...). Regards,

asked May 2, 2014 by Pierre (750 points)
0 votes
1 answer

Hello! I've just upgraded our installation of Adaxes to 2014.1, and I'm looking forward to utilising the new features, particularly the O365 Cloud management features. However ... switch (will wait for some feedback), would be greatly welcome. Many thanks, Jay

asked Apr 11, 2014 by jaypaterson (90 points)
2,740 questions
2,474 answers
1,373,433 users