This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice This article is not considered official documentation for K2 software and is provided “as is” with no warranties.
The Sourcecode.Forms.Runtime.Error log file will rapidly grow in size due to the error below:
[ERR] Source:<SourceCode.Forms.Runtime.ManagementServer.RemoteNotify(string queryString)>
Message= Arguments=<http://OLDURL:81/Runtime/CacheControl.ashx?u=K2:Domain \K2ServiceAccount&m=uv&_t=636970722796134642&i=SourceCode.Forms.Runtime.ManagementServer, -1, null, null> System.Net.WebException: Unable to connect to the remote server --->
System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 127.0.0.1:81
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) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at SourceCode.Forms.Runtime.ManagementServer.<>c__DisplayClass219_1.b__1(IAsyncResult result)
The Sourcecode.Forms.Runtime.Error file in the (C:\Program Files\K2\Host Server\Bin) will be grow to a large size and could cause disk space allocation problems on the K2 Server.
This error will start to occur after migrating to a new environment and it seems that the old servers URL are referenced.
The following query can be used to determine if there are old URLs in the environment:
SELECT * FROM [Form].[Peer]
If old entries exist direct database modification will be required. Please log a K2 Support Ticket on the K2 Customer Portal for assistance in resolving the issue.
Please Note that direct K2 database modification is not allowed as it might leave the environment in an unsupported state.
This must only be done with the assistance of, or when instructed to do so by K2 Support.