Troubleshooting K2 Setup Manager: JavaScript Service Provider Logon Failure

Updating service account passwords in Nintex Automation (K2) is a standard maintenance task, typically handled by running the K2 Setup Manager and selecting the Configure option. However, a known bug can sometimes stall this process, specifically when the installer attempts to restart the K2 JavaScript Service Provider.

The Symptom

During the configuration process, the Setup Manager may fail with a System.InvalidOperationException. If you inspect the installation logs, you will see an error similar to this:

The service did not start due to a logon failure Target failed to execute: Start K2 JavaScript Service Provider

This happens because the Setup Manager attempts to start the service before the new credentials have been fully propagated to the Windows Service host, or it fails to override the old cached credentials during the automated start-up sequence.

The Workaround

If you encounter this error, don't worry—you don't need to roll back your entire installation. You can bypass the bug by manually synchronizing the credentials. Follow these steps:

1. Manually Update the Service Credentials

Before re-running the installer, you need to fix the "Logon" property for the specific service mentioned in the error.

  • Open Services.msc on your K2 Host Server.

  • Locate the K2 JavaScript Service Provider.

  • Right-click and select Properties, then navigate to the Log On tab.

  • Update the password for the service account and click Apply.

2. Start the Service

Once the credentials are saved, manually start the service.

  • Right-click the K2 JavaScript Service Provider and select Start.

  • Ensure the status changes to Running and stays that way for at least 30 seconds.

3. Run Setup Manager in 'Recover' Mode

With the service now running on the correct credentials, go back to your installation media.

  • Run the K2 Setup Manager (Setup.exe).

  • Instead of 'Configure', select the Recover option.

  • The Setup Manager will now verify the environment and complete the configuration without getting stuck on the service start-up phase.

Comments

Post a Comment

Popular posts from this blog

Blocking Error during K2 5.6 Server migration

  Error Encountered: Error during K2 5.6 migration to a new machine, keeping the SQL server unchanged. Error message:                       20:49:59:>> Certificates.FindCertificate: Found 1 certificates                       20:49:59:>> RegisterShard.Execute: Adding additonal connection string parameters to config service shard                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional connection string parameter value: empty                       20:49:59:>> AdditionalConnectionStringParameters.AmendSQLConnectionString: Additional ConnectionString Parameters is empty                       20:50:04:>> AnalyzableAction.PopulateValidate...
Read more

Client Credentials flow with K2 Cloud with Odata, Workflow REST or SCIM

Image
This guide outlines the steps to using the Client Credentials Flow for accessing Nintex K2 Cloud's OData, Workflow REST, or SCIM APIs. Before you begin: Ensure your environment is eligible for Client Credentials Flow by contacting Nintex support ( https://customer.nintex.com/cases/Pages/default.aspx ). Have a SHA256 hash of the client secret of your choosing ready. Steps: Onboarding: Open a support ticket with Nintex requesting the onboarding of the Client Credentials Flow for your environment. Provide the SHA256 hash of your the client secret. https://help.nintex.com/en-US/k2cloud/userguide/current/Content/IdProviders/ClientCredentials.htm You can Generate the secret hash from a Client Secret value in a .NET console application. The onboarding team does not need the actual secret value, only the hash of it. Use the following steps and code example to generate the hash: Add the  IdentityModel  NuGet package. Add the  IdentityModel  library reference in the ...
Read more

Blocking error RegisterServiceInstanceObjects when upgrading to K2 5.6/5.7

K2 5.7 Upgrade Error: Blocking Issue with Orphaned Service Instances Error Message:             07:30:39:>> AuthorizationBase.RegisterServiceInstanceObjects: Current ServiceType and ServiceInstance details: ServiceType.Guid = GUIDValue1. ServiceInstance.Guid = GUIDValue2 . ServiceInstance.Name = ServiceInstanceName             07:30:39:>> ConnectionHelper.GetServerInstance: Create 'AuthorizationClient' instance using ConnectionContext             07:30:39:>> AuthorizationBase.RegisterObject: Validate Parent             07:30:39:>> AuthorizationBase.Execute: Logged Error: Failed: System.Exception: Item 'GUIDValue1' does not exist    at SourceCode.Install.Package.Actions.Authorization.AuthorizationBase.RegisterObject(String name, Guid id, Guid parentID, Guid classID, String className, Boolean inherit, Boolean propagate, IIdentityReferenc...
Read more