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.
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.
- 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 that the K2Workspace database is running on.
- Please review log files for more information.
In this case the issue was caused by a permissions issue on the database.
With a simple test, create a UDL file as per this article.
Using the Workspace user account to connect to the DB confirmed that it did not have the correct access on one of the nodes explaining why this occurred intermittently.
The Workspace user account had been given insufficient permissions on the DB.
Giving the correct permissions to access the K2 DB resolved the issue.