I’m working on re-creating a SmartForms application for a client — which was already in progress when I took over for another engineer — when I bumped into the exception described in the the title. This application was deployed from another environment.

Where’s the problem?

Continue reading

One of my client’s users came to me with an unusual situation — he could reach the SharePoint pages that host the SmartForms application, but none of the SmartForms would appear. Instead, this MacBook user saw messages that read, “The webpage at {URL} might be temporarily down or it may have moved permanently to a new web address.”

The user works in a remote office, and uses the application infrequently, as needed.

What gives?

Continue reading

This was a really weird one. A client’s application suddenly suffered from this error in all environments simultaneously. The root cause had nothing at all to do with K2 blackpearl, but it affected the service keys of the instance of a service, which brought down the service and caused the exception.

Continue reading

Things just BLEW UP the other night. I connected to the development server, opened my solution in K2 Studio, started to edit, and BLAMMO! Everything went black.

Administrators had to rebuild my blown profile on the server. Once I was able to get into the desktop again, I figured I should have been able to drop shortcuts to K2 Studio and Visual Studio onto my desktop. No big deal, right?

I was able to open K2 Studio, load my solution, but was surprised to see that the solution was not connected to the (local) development environment.

I was even more surprised when anything I tried to do that was related to the server (like open an IPC, for example) yielded a nasty “Primary Credentials Not Authenticated” exception that threw me out of K2 Studio completely.

Continue reading

A user is unable to open the InfoPath form associated with a workflow task. The exception reads:

You have insufficient rights to access the task. Ensure that you have contribute rights on the site before attempting to open the task.

It’s a SharePoint permissions problem. Fortunately, it’s an easy fix.

Continue reading


When attempting an initial workflow deployment to, OR during initial exploration of the K2 Workspace in, a new development environment, the following exception is received:

Please create a master key in the database or open the master key in the session before performing this operation. The key ‘SCSSOKey’ is not open. Please open the key before using it.

Continue reading