upgrading NINTEX K2 Five from 5.X to 5.6
if you are upgrading NINTEX k2 five from 5.X to 5.6 , and you’ve installed it successfully with new database creation, then you want to Upgrade your old k2 database, and found the following Error, the solution is here.
Identity - Set Virtual Directory Negotiation Failed
Windows - Set Virtual Directory Negotiation Failed
Forms - Set Virtual Directory Negotiation Failed
=================================================
Error Message :
"Error","General","0","ErrorMessage","SourceCode.Hosting.Server.Runtime.HostLoadBalancedServerManager.Poll","0 System.Exception: Error (0) . --->
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 10.10.10.10:5560
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
"Error","System","2001","ServerStartError","SourceCode.Hosting.Server.Runtime.HostServerEngine.StartHostServer",
"2001 Error Starting Host Server: System.NullReferenceException: Object reference not set to an instance of an object.
at SourceCode.Sync.RuntimeMarshal.SecurityLabelConnector.Init(IServiceMarshalling serviceMarshalling, IServerMarshaling serverMarshaling)
at SourceCode.Hosting.Server.Runtime.HostServerEngine.EnrollHostableTypeInstance(IHostableType HostableTypeInstance)
at SourceCode.Hosting.Server.Runtime.HostTypeLoader.InitAndEnrollHostableType(String HostedTypeName, String InterfaceName)
at SourceCode.Hosting.Server.Runtime.HostTypeLoader.InitAndEnrollHostableTypes(String InterfaceName)
at SourceCode.Hosting.Server.Runtime.HostServerEngine.StartHostServer()","system",
"10.10.10.10","K2-Server01:C:\Program Files\K2\Host Server\Bin","6194011","cef0b83e5cd0499b82b6e88fd13116a9",""
=================================================
SOLUTION:
1- The problem is in Table oIdentity]. ClaimIssuer] URI
The URI is still the old URI, Change it to the new URI and Restart the server.
now the k2 server service started and working.
2- The problem is in Table rHostServer].TConfiguration]
VariableToken >> bSTS_ISSUER_URL]
Change it to the new URI and Restart the server.
3- After Pointing to the old Database and run configuration, Modify the above values, Run the configuration Again will make k2 server service work again.
NOTE:
1- Use Alias URI If Possible like https://K2.nintex.com and add it to hosts file
2- when you run configuration DO NOT Select Update URI, Uncheck IT before resume.
STEP: Resolve Security Token Service Issuer(Uncheck Update If U Use Alias URI)
3- Restart The Server to Check if K2 Server Service is Running, and keep in mind it takes a couple of minutes to run.
=================================================
Good Luck K2 Developers, Keep the hard work going.
=================================================
