Posts

Showing posts from May, 2023

K2 Trusted LDAP User Manager

When using K2 Trusted LDAP User Manager with LDAP servers that comply with LDAP v3 but aren't Windows-based, you might encounter a specific issue with the "manager" attribute: User searches can fail: If the "manager" attribute isn't mapped correctly or doesn't exist on the LDAP server, user searches might unexpectedly fail. This behavior is different from other non-mapped or non-existent attributes, which typically don't cause search failures. To address this issue, follow these steps: Check for a matching attribute: Verify if the LDAP server has an attribute that corresponds to the "manager" attribute in K2. Map the attribute correctly: If a matching attribute exists, ensure it's mapped accurately in the K2 configuration. Here's an example of a correct mapping: XML < K2LdapMapping K2Name = "Manager" FullOnly = "true" LdapName = "manager" ObjectType = "System.String" SearchQuery = ...

Upgrading from 4.6.10 or earlier

Upgrading K2 from 4.6.10 or Earlier to Latest: Your Roadmap Starting from K2 4.6.10 or earlier requires a two-step upgrade process: Step 1: Upgrade to K2 4.7 Upgrade path: You cannot directly migrate K2 4.6.10 or earlier to Windows Server 2016 or later due to .NET Framework 4.5 limitations. You must upgrade in-place on your current Windows 2008 R2 or Windows 2012 R2 server. Backup options: Take a VM snapshot and database backup of your current server. Alternatively, stand up a dedicated Windows 2008 R2/2012 R2 server for the upgrade. Upgrade sequence: K2 4.6.10 or earlier (Windows 2008 R2/2012 R2, .NET 4.5) Backup (VM snapshot & database) In-place upgrade to K2 4.7 Step 2: Upgrade to the Latest K2 Version (e.g., K2 5.6) Migration options: From Windows 2008 R2/2012 R2 with K2 4.7: Migrate K2 4.7 to your new Windows Server 2016+ and SQL Server environment. From dedicated upgrade server (optional): Migrate K2 4.7 from the temporary server to your...

K2 Service Account Password Special Characters

For K2 installations and upgrades, avoid using these special characters in your K2 service account passwords: Single quote (') Double quote (") Opening angle bracket (<) Closing angle bracket (>) Ampersand (&) Using these characters can potentially lead to compatibility issues or unexpected behavior within the system.

Blocking error during upgrade Grant_AdminUser_Full_RightsOn_Root_ServiceType

Issue During an upgrade (at least 5.6), you may run into the following error: Grant_AdminUser_Full_RightsOn_Root_ServiceType The K2:DOMAIN\DisabledUserInAD could not be found. Cause This is related to K2 5.6 introduction of Service Instance Security: https://help.nintex.com/en-us/k2five/userguide/current/Content/K2-Management-Site/Integration/ServiceInstancesSecurity.htm Where-in the Upgrade process will get users from the [Server].[ServerUser] tables to set as default administrators for Service Instances.  However, if the user is disabled in Active Directory and marked as not enabled in the K2 Identity Cache, then this step will fail. Resolution You can check which entries in the [Server].[ServerUser] is disabled via SQL, and remove these entries from the [Server].[ServerUser] table.  You can use the following to check: SELECT * FROM [Server].[ServerUser] ssu  JOIN [Identity].[Identity] ii  ON ssu.[User] = ii.FQN  WHERE ii.[Enabled] = 0 AND ii.[Type] = 1 AND ii...

Blocking Error during Upgrade GrantObjectsRightsOnClassTypeWhereInheritanceBroken GrantEveryoneCreateRightsOnCategoryObjectClassObjectsWithBrokenInheritance

Issue If you run into the following blocking error during an upgrade: 13:32:45:>> AuthorizationBase.Execute: Finish GrantObjectsRightsOnClassTypeWhereInheritanceBroken 'GrantEveryoneCreateRightsOnCategoryObjectClassObjectsWithBrokenInheritance'. Successful: False  13:32:45:>> Target.Execute: !Completed: GrantEveryoneCreateRightsOnCategoryObjectClassObjectsWithBrokenInheritance, Success: False  13:32:45:>> Component.Execute: Logged Error: Internal error has caused the install to terminate:   13:32:45:>> Executor.ExecuteComponent: Logged Error: Blocking execution exception occurred, install cannot continue: Cause It may be due to a category with no name .  To determine if this the case, run the following SQL query: SELECT * FROM [Category].[System] WHERE [Name] = N''  Resolution If an empty category is identified, you can run the following query to give it a placeholder name, and Recover the Upgrade: UPDATE [Category].[System]  SE...