K2 blackpearl - Articles
Community articles and FAQ's for K2 blackpearl.
cancel
Showing results for 
Search instead for 
Did you mean: 
Sort by:
Symptoms  Windows Event Viewer is flooded with this message:   "The User Manager 127.0.0.1 returned an empty queue."   This issue seems to be related related with K2 roles. 1. How to check the role dependicies when we cannot delete some roles? 2. "Server.DestQueue" table in K2 database shows some entries for users (NOT roles) with "interval" 5 seconds. Diagnoses This issue occurs whenever you have a role or an active directory group that has only one user that is not active or has resigned. I.e. each role and gruop have to contain at least one valid active user. Resolution This issue occurs whenever you have a role or an active directory group that has only one user that is not active or has resigned.   Inside of K2 database DestQueue table contains a mapping between processes and roles and it would not break the platform (current tasks assignment, existing destination rules, etc.) so you can try deleting the suspicious "user" records from the K2HostServer.DestQueue table to see if it resolves the “empty queue”. As a way to describe this issue K2 is considering those accounts as roles, and tries to “resolve” them to users.   Be sure to backup your K2 database before attempting any direct modification on it and in case of any doubts contact K2 supports.
View full article
When editing your SmartObject, and changing the property, after you click  Finish , the following error is shown:   "Conversion failed when converting date and/or time from character string"   Please view the related KB article here.
View full article
After upgrading to K2 4.7, attempting to execute the  Add  SmartObject method based on an Endpoint WCF Service, results in an exception.   The exception states: “Object reference not set to an instance of an object”.   Please view the related KB article here.
View full article
When making use of K2 Connect for SAP, there is a parameter in the K2 Connect Service Instance named "UseCache".   Please view the related KB article here.
View full article
Symptoms CORS header in SmartObject REST service Response Header. Diagnoses K2 does not currently support CORS header in SmartObject REST service Response Header. Resolution CORS settings for the SmartObject REST services are not supported. The reason for this, is that the REST service is hosted in the host server, instead of IIS which means there is no web.config file to configure CORS settings. There is also no config entry that you can set in the K2HostServer.exe.config file to configure CORS. CORS is enforced by browsers. So if you have a site that is in a different domain, one way to get past the CORS limitation is to make the REST call server side with no browser/client interaction, and then pass the results back to the client.
View full article
Symptoms   Unable to access ViewFlow with the following error message:   "System.DirectoryServices.ActiveDirectory.ActiveDirectoryServerDownException: The server is not operational. Name: "..."   We receiving this despite there are multiple domain controllers available. Diagnoses Usually a K2 server machine restart resolves the issue. Resolution Usually K2 server machine restart resolves the issue.   This is how AD handles LDAP requests: The DC Locator Service has been re-designed in Windows Server 2008 and later to include a new mechanism. When a client computer finds a preferred domain controller, it sticks to this domain controller unless that domain controller stops responding or the client computer is restarted. This is generally called Domain Controller Stickiness. If you take this domain controller offline for maintenance purpose or it goes down, the clients that were connected to it will look for another domain controller to shift their connections to new domain controller. But when the domain controller comes online again, these connections are not shifted back because client computers do not refresh themselves to check to see if domain controller is back again. This can cause load-balancing issues because client computers remain connected to same domain controller.   For the cases when multiple DCs available but one of them (to which K2 happens to be connected) fails following is applicable. K2 performs bind with the DirectoryEntry class e.g: new DirectoryEntry(?LDAP://DC=Domain,DC=COM?, ??, ??,AuthenticationTypes.ReadOnly) This process relies on Domain Controller Locator which an algorithm that runs in the context of the Net Logon service. Essentially it is a sort of AD DS client part which is responsible for selecting specific DC for specific domain. Domain Controller Locator has its own cache. The Net Logon service caches the domain controller information so that it is not necessary to repeat the discovery process for subsequent requests. Caching this information encourages the consistent use of the same domain controller and, thus, a consistent view of Active Directory. Refer to the Microsoft documentation for details: Domain Controller Location Process https://technet.microsoft.com/en-us/library/cc978011.aspx Domain Controller Locator https://technet.microsoft.com/en-us/library/cc961830.aspx Sometimes this cache may keep a reference to unavailable DC for specific domain, and the following command can be used to force reset of this cache: nltest /dsgetdc:DomainName /force Note sometimes it is necessary to run this a few times till another DC is selected. To check which DC you are using at the moment for specific K2 server you can use: nltest /dsgetdc:domain_name You may also look into your the following group policy setting "Specify positive periodic DC Cache refresh for non-background callers," according to documentation it determines when a successful DC cache entry is refreshed. This policy setting is applied to caller programs that do not periodically attempt to locate DCs and it is applied before the returning the DC information to the caller program. Default value (when it is not configured) is 30 minutes (1800). I am not sure if it influence K2 or not, but if it does it means that with default settings your K2 issue should be resolved by itself in 30 minutes. It is not recommended to set very low values for this policy, but in case you have this policy configured to a significantly higher values you may revert back to default or even slightly lesser values for it on your K2 servers. As Domain Controller Locator runs in the context of the Net Logon service restart of this service likely clear locator cache too. Note: in link failure scenario when no DCs available for specific domain are available for specific domain (all DCs are behind WAN link which is temporarily failed) there is nothing that can be done from K2 side apart from restoring WAN link or placing locally available DC/RODC to mitigate against this scenario. In such scenario you will likely to get slightly different exception - "A referral was returned from the server"   Current recommendations: 1) Reconfigure K2 to use GC instead of LDAP. The global catalog is a distributed data repository that contains a searchable, partial representation of every object in every domain in a multidomain Active Directory Domain Services (AD DS) forest. So essentially your GC placed in local domain can serve part of the queries which otherwise should go to DCs in another domain, potentially over WAN link. From purely AD DS side GC has the following benefits: - Forest-wide searches. The global catalog provides a resource for searching an AD DS forest. - User logon. In a forest that has more than one domain GC can be used during logon for universal group membership group enumeration (Windows 2000 native DFL or higher) and for resolving UPN name when UPN is used at logon. - Universal Group Membership Caching: In a forest that has more than one domain, in sites that have domain users but no global catalog server, Universal Group Membership Caching can be used to enable caching of logon credentials so that the global catalog does not have to be contacted for subsequent user logons. This feature eliminates the need to retrieve universal group memberships across a WAN link from a global catalog server in a different site. Essentially you may enable this feature to make use of GC even more efficient. To reconfigure K2 to use GC you have to edit RoleInit XML field of HostServer.SecurityLabel table and replace "LDAP://" to "GC://" with subsequent restart of K2 service. From K2 prospective it should improve responsiveness of AD SmartObjects as well as slightly decrease reliance on WAN link/number of queries to DCs outside of local domain. 2) Try to use Domain Locator cache refresh clear up if the same issue will occur again (see details above, nltest /dsgetdc:DomainName /force) - and verify whether it is viable workaround. It should work. You may also leverage "nltest /dsgetdc:DomainName" to confirm which specific DC is being used by K2 server to verify status and availability of this specific DC with your infrastructure team.
View full article
Symptoms Error when navigating to a SharePoint List:   The remote server returned an error: (401) Unauthorized.Failed to initialize the Context: URL: [SHAREPOINT_SITE_URL] Username: Error Details: Method: SharePointService.initializeContext x-ms-diagnostics : 3001000reason="There has been an error authenticating the request."category="invalid_client"   SPRequestGuid : b992789d-200f-f05d-6a8b-4604b4ceb15b   Type: SourceCode.SmartObjects.Client.SmartObjectException Source: SourceCode.SmartObjects.Client Method Base Member Diagnoses 1) Duplicate User Profiles: In the ULS logs we saw the following error:   Error trying to search in the UPA. The exception message is 'Microsoft.Office.Server.UserProfiles.DuplicateEntryException: GetUserProfileByPropertyValue: Multiple User Profiles found with propertyName 'SPS-UserPrincipalName' of specified value   2) ClaimTypeMapping incorrect: Using the K2HostServer Logs we could see the following:   "Error","SmartObjects","10702","Error","SourceCode.SmartObjects.ServiceBroker [ExecuteSmartObject]","10702 An error occurred in the [SHAREPOINT_SITE_NAME] Service Instance. The remote server returned an error: (401) Unauthorized.Failed to initialize the Context   Just before the error I saw the following:   "Debug","General","0","DebugMessage","SourceCode.Security.OAuth.Service.OAuthService.GetOAuthToken","0 Decoded OAuth Token for Resource='SHAREPOINT_SITE_NAME' ResourceAudience='RESOURCE_AUDIENCE' CredentialID='CREDENTIAL_GUID'   The credentials we used was an ADFS credential, so we mapped the Credential GUID back to the SecurityProvider that was set to "SourceCode.Hosting.SecurityProviders.SSPI" So this means that the user being returned is: K2:[USERNAME] (Windows Account) Resolution 1) We removed the duplicate UserProfile 2) We updated the ClaimTypeMapping and set the ADFS type mapping from 'K2' to 'K2ADFS'  
View full article
Symptoms There are at least 2 user accounts that do not return any data when we try to pull user detail information using the AD service. For instance, i recently created a form with two views, on view lists all users from A/D and when you click any of them the secod view displays all the groups they are a member of. This works with everyone but the two users, those two users don't return anything. I also notice this error in the Application log, ChrisN is one of the users that is not returning data. 64007 Provider did not return a result for K2:DENALLIX\Bob on GetUser Diagnoses N/A Resolution Issue identified as a known issue on 4.7 where UMUser SMO cannot resolve user when there is a AD object, ie computer object, that have the name as the user object (username). Provided customer with fix by setting TranslateWithDirectoryServices=False to the roleinit > run net stop "K2 blackpearl Server" andand net start "K2 blackpearl Server". Customer resolved the issue by renaming the computer object to something else that doesn't match the username.  
View full article
When executing a  SmartObject method  from a  SharePoint Document Library SmartObject , you may experience the following issue:     Please view the related KB article here.
View full article
After upgrading to K2 blackpearl 4.7, an IOException error occurs when deploying a package containing a Workflow with a Hebrew name.    System.IO.IOException: I/O error occurred.   Please view the related KB article  here .
View full article
When editing Form rules the following error appears:  "Object Not Set to a Reference"   Please view the related KB article  here .
View full article
The  close button  or  "X" icon  that appears in the upper-right hand corner of the Subform or Subview is missing:     Please view the related KB article here.
View full article
When a user executes a SmartObject method and does not have rights to the database, no error message displays.   Please view the related KB article here.
View full article
You cannot inherit the properties and methods of the DocuSign SmartObject dll assembly in a Visual Studio custom project.   The following error is shown: CS0509: ExtendDoc: cannot derive from sealed type Broker   Please view the related KB article here.
View full article
The DAC Transaction feature has a rollback option in case a problem occurs on a transaction, enabling a rollback of the transaction. A rollback can cause the K2 Server to stop unexpectedly at times.     Please view the related KB article here.
View full article
When creating a Document Set with a long name in a folder in SharePoint, an error occurs and the Document Set is not created.   The parameters.LeafName argument is invalid.   Please view the related KB article  here .
View full article
When deploying a package that contains a byRef item with powershell, the byRef (Reference Only) item gets fully deployed as well. These items should not deploy as they are a reference to an existing object.   Please view the related KB article here.
View full article
Given a rule that transfers data from an auto complete control to a data label, at runtime selecting a value in the auto complete control does not populate the data label as it should.   Please view the related KB article here.
View full article
An error appears when starting the K2 Service:   K2HostServer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFB924DAC4B (00007FFB924D0000) with exit code 80131506. Faulting application name: K2HostServer.exe, version: 0.0.0.0, time stamp: 0x54ef076c Faulting module name: clr.dll, version: 4.7.2563.0, time stamp: 0x5a3356b3 Exception code: 0xc0000005 Fault offset: 0x000000000000ac4b Faulting process id: 0x1654 Faulting application start time: 0x01d398e199805675 Faulting application path: C:\Program Files (x86)\K2 blackpearl\Host Server\Bin\K2HostServer.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: d8c7098f-04d4-11e8-810e-000d3ab4eeb0 Faulting package full name: Faulting package-relative application ID:   Please view the related KB article  here .
View full article
When executing a joined SmartObject when the K2 database collation differs from the SQL Server, a SQL error returns.   Cannot resolve the collation conflict between SQL_Latin1_General_CP1_CI_AS and Latin1_General_CI_AS in the equal to operation. Cannot resolve the collation conflict between SQL_Latin1_General_CP1_CI_AS and Latin1_General_CI_AS" in the equal to operation.   Please view the related KB article here.
View full article
Top Contributors