Symptoms
We are getting the below error when deploying a workflow on production server from K2 studio, the system is not usable and the deployment is necessary to fix that issue.
We have already checked the MSDTC service as suggested by K2 on different forums.
"2 Error(s)
(Suggestions) Notification Service: Task Error: System.Exception: System.Xml.XmlException: Root element is missing.
Server stack trace:
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at SourceCode.Categories.Client.CategoryServer.RefreshCategoryManager(CategoryManager categoryManager, Boolean getCategoryData)
at SourceCode.EventBus.EventAdmin.Admin.addEventToCategory(String eventID, String eventName, String categoryConnectionString, Int32 worklistNotificationCategoryID)
at SourceCode.EventBus.EventAdmin.Admin.UpdateCustomEventWithMappings(String connection, CustomEvent customEvent, String user)
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
Exception rethrown at 0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageDataandamp msgData, Int32 type)
at SourceCode.EventBus.EventAdmin.Admin.UpdateCustomEventWithMappings(String connection, CustomEvent customEvent, String user)
at SourceCode.EventBus.Server.ClientServerImplimentation.UpdateCustomEventForNotification(CustomEvent customEvent, String userName)
at SourceCode.EventBus.Server.ClientServerImplimentation.AddWorklistItemNotification(WorklistItemIdentifier worklistItemIdentifier, String eventData, PolicyMapping policyMapping, Boolean externalOwned)
at SourceCode.EventBus.Server.ClientServerImplimentation.AddWorklistItemNotification(WorklistItemIdentifier worklistItemIdentifier, String eventData, PolicyMapping policyMapping, Boolean externalOwned)
at SourceCode.EventBus.Server.ClientServerImplimentation.UpdateWorklistItemNotification(List`1 worklistItemIdentifiers)
(Suggestions) The "SourceCode.DeploymentTasks.NotificationService.NotificationTask" task failed unexpectedly.
System.Exception: System.Exception: System.Xml.XmlException: Root element is missing.
Server stack trace:
at System.Xml.XmlTextReaderImpl.ThrowWithoutLineInfo(String res)
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.LoadXml(String xml)
at SourceCode.Categories.Client.CategoryServer.RefreshCategoryManager(CategoryManager categoryManager, Boolean getCategoryData)
at SourceCode.EventBus.EventAdmin.Admin.addEventToCategory(String eventID, String eventName, String categoryConnectionString, Int32 worklistNotificationCategoryID)
at SourceCode.EventBus.EventAdmin.Admin.UpdateCustomEventWithMappings(String connection, CustomEvent customEvent, String user)
at System.Runtime.Remoting.Messaging.Message.Dispatch(Object target)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
Exception rethrown at 0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageDataandamp msgData, Int32 type)
at SourceCode.EventBus.EventAdmin.Admin.UpdateCustomEventWithMappings(String connection, CustomEvent customEvent, String user)
at SourceCode.EventBus.Server.ClientServerImplimentation.UpdateCustomEventForNotification(CustomEvent customEvent, String userName)
at SourceCode.EventBus.Server.ClientServerImplimentation.AddWorklistItemNotification(WorklistItemIdentifier worklistItemIdentifier, String eventData, PolicyMapping policyMapping, Boolean externalOwned)
at SourceCode.EventBus.Server.ClientServerImplimentation.AddWorklistItemNotification(WorklistItemIdentifier worklistItemIdentifier, String eventData, PolicyMapping policyMapping, Boolean externalOwned)
at SourceCode.EventBus.Server.ClientServerImplimentation.UpdateWorklistItemNotification(List`1 worklistItemIdentifiers)
at SourceCode.Hosting.Client.BaseAPI.BaseAPIConnection.RemoteCall(String TypeName, String MethodName, Objectt] Parameters, Booleann] NullList, MarshalMessageType CallType)
at SourceCode.Hosting.Client.BaseAPI.BaseAPI.RemoteCall(String TypeName, String MethodName, Objectt] Parameters, Booleann] NullList, MarshalMessageType CallType)
at SourceCode.EventBus.ClientAPI.Notification.UpdateWorklistItemNotification(List`1 worklistItemIdentifiers)
at SourceCode.DeploymentTasks.NotificationServic
Diagnoses
The last message sent to customer was:
"
In a previous ticket we discovered that the SQL was on a cluster so the Authentication method should be set to "No authentication required". Checking the SQL Cluster MSDTC and the Servers MSDTC properties we realized that there were ok. The K2 Server MSDTC was set to "Incoming Caller Authentication Required". This is ok if SQL is not in a cluster. We changed it to "No authentication required" but we got an error when applying the changes. After we logged in with a different account and proceed to make the change it let us continue with no errors.
After that we were able to deploy the package.
For reference, here is how the MSDTC must be configured:
http://help.k2.com/onlinehelp/K2blackpearl/ICG/4.6.9/webframe.html#MSDTC.html.
"
Resolution
The last message sent to customer was:
"
In a previous ticket we discovered that the SQL was on a cluster so the Authentication method should be set to "No authentication required". Checking the SQL Cluster MSDTC and the Servers MSDTC properties we realized that there were ok. The K2 Server MSDTC was set to "Incoming Caller Authentication Required". This is ok if SQL is not in a cluster. We changed it to "No authentication required" but we got an error when applying the changes. After we logged in with a different account and proceed to make the change it let us continue with no errors.
After that we were able to deploy the package.
For reference, here is how the MSDTC must be configured:
http://help.k2.com/onlinehelp/K2blackpearl/ICG/4.6.9/webframe.html#MSDTC.html.
"