The following error is written in the K2Error.txt file when trying to start K2 Server service and using integrated security:
"K2Sql.OpenConnection: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection".

This would typically happen when the K2 databases are on a different server.

A possible cause might be that the user account designated to start the service, does not have neccasary rights on the SQL machine. Make sure that the "Access this computer from the network" policy is set on the SQL machine (or machines if it's a cluster). You can set this policy by doing the following on the SQL machine(s):

• Click on

"Start", "Programs", select "Administrative Tools" and click on "Local Security Policy".

• Select the

"User Rights Assignment" node.

• Double click the

"Access this computer from the network" and click on "Add User or Group". Search for the "Authenticated Users" group and add to the list.

• Click

"OK". If prompted with a warning, click "OK" again.

A last thing to check is to verify that the user account that starts the service has applicable rights on the K2 and K2Log databases.