Symptoms
Getting a lot of Event log errors - event id 1 and 64007 Sourcecode.logging.extension
Diagnoses
Once a week, I would get a large amount of server errors for:
Log Name: Application
Source: SourceCode.Logging.Extension.EventLogExtension
Date: 8/18/2015 3:19:03 PM
Event ID: 1
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: k2.denallix.com
Description:
1 3014 A mismatch between the end user and the connection credentials has been detected. This may be intentional and will only require action if specific problems are currently being encountered. Refer to Kerberos and K2 Pass-Through Authentication settings (currently ClientKerberos) and documentation.
Event Xml:
1
2
0
0x80000000000000
4758474
Application
k2.denallix.com
1 3014 A mismatch between the end user and the connection credentials has been detected. This may be intentional and will only require action if specific problems are currently being encountered. Refer to Kerberos and K2 Pass-Through Authentication settings (currently ClientKerberos) and documentation.
Resolution
This error can be logged "whenever a client (SourceCode.Workflow.Client) wants to use K2 pass-through, but it is not allowed." But as you currently have K2 configured for "ClientKerberos", this may be logged but it should not cause any issues.
http://help.k2.com/onlinehelp/k2blackpearl/icg/current/webframe.html_k2pa_error_and_log_messages.html
Some options includes:
1. Ignoring the logging of this error as it is not currently affecting users/workflows
2. Perhaps hiding this error ID in the event logs or disabling the logging of K2 errors in the Application events log (this will still be logged in the HostServer log located at C:Program Files(x86)K2 blackpearlHost ServerBin)
3. If you wish to perhaps find out where this maybe coming from, we can enable Verbose hostserver log to determine if Sharepoint, Workspace, or other areas of K2 integration is sending a request to the K2 server and requesting pass-through authentication. This can be done setting the following node in the "HostServerLogging.config" file at "C:Program Files(x86)K2 blackpearlHost ServerBin":
<LogLocation Name="FileExtension" Active="True" LogLevel="All" />
Where Active = True and LogLevel = All
A K2 blackpearl service restart is necessary, as such perhaps implement this during after hours. Then we will need to monitor the server until the error is logged again. Perhaps this will tell us what is interacting with K2/requesting K2 passthrough authentication when it is logged.
4. We can also allow K2 pass-though authentication to stop the logging of this error via changing the "DelegationContext" key to "ClientWindows" if you have Kerberos configured and the Provider is set to "Negotiate", it will try Kerberos first before falling back to K2 passthrough. A K2 service restart is also necessary.
