Symptoms

While attempting to install the K2 components on SharePoint 2010 servers to integrated K2 with SharePoint 2010, the K2forSharePiont.config file fails to update properly, thus preventing the integration from fully finishing.
 

Diagnoses

During installation on the SharePoint machines, K2 will try to set the value in K2forSharePoint.config for the eWEBDESIGNERCONNECTIONSTRING] variable, and the value looks like this:

Data Source=yourdatabasenameInitial Catalog=yourK2servernameuid=installaccountnamepwd=installaccountpasswordPooling=True

All of this information is then parsed to XML. In several cases, an ampersand sign (symbol appearing as andamp) can be part of a particular password value and then be encoded as "andampamp" instead of just the ampersand symbol itself. This can cause the value of the installaccountpassword to include "andampamp" thus making K2 think it is in invalid when updating the K2forSharePoint.config file.
 

Resolution

After changing the password for the install account to one that did not include an 'andamp' sign in this particular case, and then re-running the K2 blackpearl setup manager on the SharePoint machines, this resolved the issue and allowed the installation to fully complete.

Users must be aware that if the K2 Service Account is being used to install and is the account where the password is then changed, the K2 blackpearl setup manager-Configure option will need to be re-run on both the K2 server and all SharePoint 2010 servers in order to update the K2 installation with the new service account password.