Symptoms
K2 workspace sporadically would error displaying the message below. My temp fix now is to recycle Workspace folder permission.
The server is not operational.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Runtime.InteropServices.COMException: The server is not operational.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
>COMException (0x8007203a): The server is not operational.
]
System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail) 557
System.DirectoryServices.DirectoryEntry.Bind() 44
System.DirectoryServices.DirectoryEntry.get_AdsObject() 42
System.DirectoryServices.DirectorySearcher.FindAll(Boolean findMoreThanOne) 98
System.DirectoryServices.DirectorySearcher.FindOne() 49
System.Web.Security.ActiveDirectoryMembershipProvider.FindUser(DirectoryEntry containerEntry, String filter, SearchScope searchScope, Boolean retrieveSAMAccountName, DirectoryEntryand userEntry, Booleanand resetBadPasswordAnswerAttributes, Stringand sAMAccountName) 665
System.Web.Security.ActiveDirectoryMembershipProvider.GetUser(String username, Boolean userIsOnline) 3157474
System.Web.Security.Membership.GetUser(String username, Boolean userIsOnline) 102
Worklist.Page_Load(Object sender, EventArgs e) 3757
System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e) 25
System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e) 42
System.Web.UI.Control.OnLoad(EventArgs e) 132
System.Web.UI.Control.LoadRecursive() 66
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 2428
________________________________________
Version Information: Microsoft .NET Framework Version:2.0.50727.8009 ASP.NET Version:2.0.50727.8015
Diagnoses
The issue was caused by not specifying port in LDAP connection string.
Resolution
Adding port 389 to the LDAP connection string in Workspace Web.config resolved the issue.
