We currently have K2 deployed on our production server. However, we are seeing the following errors in the K2 Server's event log:
Insight into how to fix this problem would be greatly appreciated.
05:12:25","Error","Unknown","8060","ProcessPacketError","SourceCode.Hosting.Server.Services.TCPClientSocket.ProcessPacket","8060 ProcessPacket Error, Authentication With Server Failed : Logon failure: unknown user name or bad password","system","167.191.127.101","PDTCSHPK201:e:\Program Files (x86)\K2 blackpearl\Host Server\Bin","21452042","b3b2b5c615e9418986b461cfb9f82570","""21452565","2011-06-10
"21452566","2011-06-10 05:13:25","Error","EnvironmentServer","15109","EditStringTableEntry","SourceCode.Workflow.Runtime.Management [EditStringTableEntry [string[] names]]","15109 Error occurred on EditStringTableEntry, ERROR: Authentication With Server Failed : Logon failure: unknown user name or bad password","anonymous","0.0.0.0","PDTCSHPK201:e:\Program Files (x86)\K2 blackpearl\Host Server\Bin","21452566","32a86a797ba14e02940e2608cf67a53c",""
05:13:25","Error","System","2025","InternalMarshalError","SourceCode.Hosting.Server.Services.TCPClientSocket.InternalMarshal","2025 Error Marshalling SourceCode.Workflow.Runtime.Management.WorkflowManagementHostServer.GetProcessInstances, Authentication With Server Failed : Logon failure: unknown user name or bad password","system","167.191.127.101","PDTCSHPK201:e:\Program Files (x86)\K2 blackpearl\Host Server\Bin","21452570","9eba18073cbf44faa11d179a993f3bcf",""
We have the following database connections set up in the Strings table in our K2 Workspace.(See end of post)
I have already confirmed that the account specified in the database connection string can RDP into the sql server, Open the SemService database, and run queries on some of the tables in the database.
Database Connection:Data Source=pdtcsql13;Initial Catalog=SEMService;Persist Security Info=True;User ID=<user>;Password=<pwd>Workflow Management Server: Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=k2workflow.fremont.lamrc.net;Port=5555Workflow Server:Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=k2workflow.fremont.lamrc.net;Port=5252Service Object Server:Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=k2workflow.fremont.lamrc.net;Port=5555Category Server:Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=k2workflow.fremont.lamrc.net;Port=5555
Our K2 Blackpearl service and our K2 Process Error Notification Service run under a specific domain account.
Regards,
Mihir Chokshi
Hi Mihir,
the resolution is in the error message itself. Have you changed the password of the service account recently or did the password expire? Run the Setup manager from the start menu and key in the service account details again and complete the setup.
The statements and opinions made in my postings are my own, and do not reflect the opinions of SourceCode Technology Holdings, Inc. or its subsidiaries. All information is provided as is with no warranties, express or implied, and grants no rights or licenses.
Thank you for your feedback. I ran the K2 setup manager with the "Configure K2 Blackpearl" option selected, but that did not help. In the configuration wizard, I came across a screen with all the connection settings to each of the K2 databases. I pressed the "Test" button for each connection setting, and they all showed a "successful" connection message. The configuration wizard completed successfully. However, the errors still showed up in the application event log. On our K2 server, we also have the K2 Blackpearl Process Error Notification service deployed. On the bottom of this post, I have attached the configuration settings we have set up for this service.
Here are the configuration settings we have set up in the Strings Table, in K2 Workspace:
Workflow Server: Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=UAT-k2workflow;Port=5252
SmartObject Server: Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=UAT-k2workflow;Port=5555
Workflow Management Server: Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=UAT-k2workflow;Port=5555
Category Server: Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=UAT-k2workflow;Port=5555
Service Object Broker: Integrated=True;IsPrimaryLogin=True;Authenticate=True;EncryptedPassword=False;Host=UAT-k2workflow;Port=5555
SEMService Connection String: Data Source=qdtcsql11;Initial Catalog=SEMService;Persist Security Info=True;User ID=SEMServiceUser;Password=S3Mf(0wM3S
Note: We have a number of other configuration settings set up. However, the ones listed above, are the only ones that show connection strings. Is there anyway to validate whether or not the connection strings above, are working to establish connectivity??
Here are the configuration settings we have set up for the K2 Process Error Notification Service:
<add key="ServiceName" value="K2 Process Error Notification" /> <add key="SMTPServer" value="<our smtp server>" /> <add key="EmailFromAddress" value="user@domain.com" /> <add key="EmailRecipients" value="user@domain.com" /> <add key="EmailSubject" value="K2 Process Error Notification" /> <add key="LogName" value="Application" /> <add key="LoggingEnabled" value="true" /> <add key="ScheduleInMinutes" value="1" /> <add key="ClientSettingsProvider.ServiceUri" value="" /> <add key="WorkflowServer" value="qdtcshpk202" /> <add key="WorkflowManagementServer.Port" value="5555" /> <add key="WorkflowManagementServer.SecurityLabelName" value="K2" /> <add key="WorkflowManagementServer.WindowsDomain" value="<domain>" /> <add key="WorkflowManagementServer.UserID" value="<domain account>" /> <add key="WorkflowManagementServer.Password" value="<pwd>" /> <add key="ProcessErrorStatusNumber" value="0"/>
Here are the errors we are currently seeing on the K2 server event log, repeatedly:
8060 ProcessPacket Error, Authentication With Server Failed : Logon failure: unknown user name or bad password
2025 Error Marshalling SourceCode.Workflow.Runtime.Management.WorkflowManagementHostServer.GetProcessInstances, Authentication With Server Failed : Logon failure: unknown user name or bad password
15109 Error occurred on EditStringTableEntry, ERROR: Authentication With Server Failed : Logon failure: unknown user name or bad password
Any insight you can provide would be greatly appreciated.
Hi There,
If you look in the windows event log in the security log on the machines involved do you see any authentication failures which might help you track which account it having the problem.
I am seeing the following authentication failure messages in the security log. I think it is related to my errors, I have posted above. How do I fix these errors?? MIhir Chokshi An account failed to log on. Subject: Security ID: FREMONT\a-choksmi Account Name: a-choksmi Account Domain: FREMONT Logon ID: 0x4ef06dbb Logon Type: 3 Account For Which Logon Failed: Security ID: NULL SID Account Name: a-choksmi Account Domain: a-choksmi Failure Information: Failure Reason: Unknown user name or bad password. Status: 0xc000006d Sub Status: 0xc0000064 Process Information: Caller Process ID: 0x1b18 Caller Process Name: E:\Program Files (x86)\K2 blackpearl\Host Server\Bin\K2HostServer.exe Network Information: Workstation Name: QDTCSHPK202 Source Network Address: - Source Port: - Detailed Authentication Information: Logon Process: Advapi Authentication Package: Negotiate Transited Services: - Package Name (NTLM only): - Key Length: 0 This event is generated when a logon request fails. It is generated on the computer where access was attempted. The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe. The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network). The Process Information fields indicate which account and process on the system requested the logon. The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases. The authentication information fields provide detailed information about this specific logon request. - Transited services indicate which intermediate services have participated in this logon request. - Package name indicates which sub-protocol was used among the NTLM protocols. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
I am seeing the following authentication failure messages in the security log. I think it is related to my errors, I have posted above. How do I fix these errors??
MIhir Chokshi
An account failed to log on.
Subject:
Security ID: FREMONT\a-choksmi
Account Name: a-choksmi
Account Domain: FREMONT
Logon ID: 0x4ef06dbb
Logon Type: 3
Account For Which Logon Failed:
Security ID: NULL SID
Account Domain: a-choksmi
Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064
Process Information:
Caller Process ID: 0x1b18
Caller Process Name: E:\Program Files (x86)\K2 blackpearl\Host Server\Bin\K2HostServer.exe
Network Information:
Workstation Name: QDTCSHPK202
Source Network Address: -
Source Port: -
Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Is this account FREMONT\a-choksmi one of the K2 users? or a service account? Try and see if this accounts details have been cached by K2 and are now invalid?, login to the workspace and have a look in the management console under user settings single sign on.
Also do you know if you have K2 pass through authentication configured? have a read of the white paper at the address below.
http://help.k2.com/en/displaycontent.aspx?id=3533
HTH
Fremont\a-choksmi is one of the K2 Users. I added this account in, just for troubleshooting purposes. Under regular circumstances, the K2 service runs under a service account. Regardless, the errors in the event log continue to occur if the service runs under myself or the K2 service account.
The following errors occur in our eventlog every minute, and we dont know why??
2025 Error Marshalling SourceCode.Workflow.Runtime.Management.WorkflowManagementHostServer.GetProcessInstances, Authentication With Server Failed : Logon failure: unknown user name or bad password I have logged into the machine where k2 is running, using the service account credentials, and that seems to work. I have also reentered the K2 service account credentials into the K2 service, and the service starts up successfully. Besides having the K2 service running, we also have the K2 Process Error Notification service running. when we stop either of these services, we no longer get the error messages, in the event log. I have looked under single sign on, and we have 1 entry, there for SalesForce. Here are the settings we have for the K2 Process Error Notification Service: <add key="ServiceName" value="K2 Process Error Notification" /> <add key="SMTPServer" value="mail.lamrc.com" /> <add key="EmailFromAddress" value="" /> <add key="EmailRecipients" value="" /> <add key="EmailSubject" value="K2 Process Error Notification" /> <add key="LogName" value="Application" /> <add key="LoggingEnabled" value="true" /> <add key="ScheduleInMinutes" value="1" /> <add key="ClientSettingsProvider.ServiceUri" value="" /> <add key="WorkflowServer" value="UAT-K2Workflow.fremont.lamrc.net" /> <add key="WorkflowManagementServer.Port" value="5555" /> <add key="WorkflowManagementServer.SecurityLabelName" value="K2" /> <add key="WorkflowManagementServer.WindowsDomain" value="Fremont" /> <add key="WorkflowManagementServer.UserID" value="FREMONT\<service account user>" /> <add key="WorkflowManagementServer.Password" value="<pwd>" /> <add key="ProcessErrorStatusNumber" value="0"/> WE STILL CONTINUE TO EXPERIENCE A BUILD UP OF ERRORS IN THE EVENT LOG AND DONT KNOW WHY THE ABOVE 3 ERRORS KEEP OCCURRING?? Mihir Chokshi
I have logged into the machine where k2 is running, using the service account credentials, and that seems to work. I have also reentered the K2 service account credentials into the K2 service, and the service starts up successfully. Besides having the K2 service running, we also have the K2 Process Error Notification service running. when we stop either of these services, we no longer get the error messages, in the event log.
I have looked under single sign on, and we have 1 entry, there for SalesForce.
Here are the settings we have for the K2 Process Error Notification Service:
<add key="ServiceName" value="K2 Process Error Notification" /> <add key="SMTPServer" value="mail.lamrc.com" /> <add key="EmailFromAddress" value="" /> <add key="EmailRecipients" value="" /> <add key="EmailSubject" value="K2 Process Error Notification" /> <add key="LogName" value="Application" /> <add key="LoggingEnabled" value="true" /> <add key="ScheduleInMinutes" value="1" /> <add key="ClientSettingsProvider.ServiceUri" value="" /> <add key="WorkflowServer" value="UAT-K2Workflow.fremont.lamrc.net" /> <add key="WorkflowManagementServer.Port" value="5555" /> <add key="WorkflowManagementServer.SecurityLabelName" value="K2" /> <add key="WorkflowManagementServer.WindowsDomain" value="Fremont" /> <add key="WorkflowManagementServer.UserID" value="FREMONT\<service account user>" /> <add key="WorkflowManagementServer.Password" value="<pwd>" /> <add key="ProcessErrorStatusNumber" value="0"/>
WE STILL CONTINUE TO EXPERIENCE A BUILD UP OF ERRORS IN THE EVENT LOG AND DONT KNOW WHY THE ABOVE 3 ERRORS KEEP OCCURRING??
I am guessing there are stored credentials on the server that is causing these error messages. Login to the server as Fremont\a-choksmi and go to ControlPanel-->Credential Manager-->Manage Windows Credential. Delete all stored login details. Log off and Log back in as K2 service account and do the same procedure again. You wont be able to see the cached credentials of an other AD user unless you login as that user. After this, restart the K2 service and check if you still get the error logged
Run the Setup manager from the start menu and key in the service account details again and complete the setup.