< class="prominent-subhead ">

Workspace goes into error: "Initialization failed before PreInit: Membership could not be verified: Timeout expired"

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.
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.


The following error appears:

"Initialization failed before PreInit: Membership could not be verified: Timeout expired."

The timeout period elapsed prior to completion of the operation or the server is not responding.


Possible Causes

- The application pool that workspace is running under, may be incorrect.

- The application pool user may not have sufficient rights to access the SQL Server which hosts K2 database.

- Please review log files for more information.

Troubleshooting Steps

This issue can be caused by the lack of permissions on the database level. As a simple test to verify this, you can create a UDL file as described in the Basics first : "UDL Test" article on MSDN. You can then use the workspace user account to connect to the K2 database to verify whether it  has the access from K2 server (check from all nodes) to the SQL server.

If your workspace user account had been given insufficient permissions on the DB you need to give correct permissions to access the K2 DB to resolve this issue.