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.

Issue

A new installation of the K2 blackpearl service is unable to start and the following error appears:

The server [Server]:5555 does not exist.

Symptoms

Upon further investigation the following was found:

1. The [HostServer].[Server] did not have any entries, thus the error.

2. After checking the installer trace file, the Logged Warning and Logged Error was found:

ConfigFunctions.UpdateConfig: 16:39:02:>> Logged Warning: Exception occurred while trying to update node connectionStrings for file: C:\Program Files (x86)\K2 blackpearl\\Host Server\Bin\SourceCode.Forms.Runtime.config Exception Type: XmlException Exception Msg: An error occurred while parsing EntityName. Line 1, position 144. Stacktrace: at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.HandleEntityReference(Boolean isInAttributeValue, EntityExpandType expandType, Int32& charRefEndPos)
at System.Xml.XmlTextReaderImpl.ParseAttributeValueSlow(Int32 curPos, Char quoteChar, NodeData attr)
at System.Xml.XmlTextReaderImpl.ParseAttributes()
at System.Xml.XmlTextReaderImpl.ParseElement()
at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
at System.Xml.XmlLoader.ParsePartialContent(XmlNode parentNode, String innerxmltext, XmlNodeType nt)
at System.Xml.XmlElement.set_InnerXml(String value)
at SourceCode.Install.IO.ConfigFunctions.ConfigFunctions.UpdateConfig(ConfigUpdateSettings cus)
23:24: RetryableAction.ExecuteRetryable: 16:39:02:>> Could not successfully complete the action. Exception: An error occurred while parsing EntityName. Line 1, position 144.
23:24: XmlUpdate.Execute: 16:39:02:>> Logged Error: Could not update C:\Program Files (x86)\K2 blackpearl\\Host Server\Bin\SourceCode.Forms.Runtime.config. Exception: An error occurred while parsing EntityName. Line 1, position 144.

Troubleshooting Steps

1. To resolve this, verify that these characters are not used for the username or password to connect to the K2 database, as these are not valid in XML elements.

"
'
<
>

&

2. If these characters are present, remove them from the username or password and run a repair from the Setup Manager.