Hi,
we've got a NetServer script that works in my local demo environment, but when I add it at the customer it doesn't work. They use single-signon (Windows authentication in IIS).
The logfile contains lots of these kind of errors when the script is supposed to run:
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 SuperOffice.ApplicationDomain.SoRemoteLoader.CallStaticMethod(String typeName, String methodName, Type[] parameterTypes, Object[] methodParams)
at SuperOffice.Scripting.ScriptEngine.SendEvent(String methodName, Boolean async, Object& state, SendEventArguments& arguments)
at SuperOffice.Events.SoEventManager.SendEvent(String methodName, Boolean async, Object& state, SendEventArguments& arguments)
Inner Element:
Message: Invalid token for impersonation - it cannot be duplicated.
Type: System.ArgumentException
Details:
at System.Security.Principal.WindowsIdentity.CreateFromToken(IntPtr userToken)
at System.Security.Principal.WindowsIdentity..ctor(SerializationInfo info)
Is there any problem running NetServer scripts when IIS is set up to use Windows authentication?