Hi Sean
With regards to the first error, were any users/groups deleted that are currently being used within your workflow? if so this can lead to the Identity.Identity not being able to resolve for the deleted users/groups.
Secondly how many nodes are currently setup within your environment? It could be that the Identity might be out of sync. Could i ask you to restart the K2 Blackpearl server service and moniter if the issue appears again?
Lastly what versions of Blackpearl and Smartforms are you currently running and could you provide details on the setup of your environment?
Kind Regards,
Yannick
Hi there,
Thank you for the response.
"were any users/groups deleted that are currently being used within your workflow?"
No. There hasn't been any changes to permission groups.
"Secondly how many nodes are currently setup within your environment?"
Not too sure what you mean here? Is this specific to the workflow?
There are +- 40 activities within the workflow.
We currently have one workflow process at this client.
The problem seems to occur infrequently, and not at the same activity.
"Could i ask you to restart the K2 Blackpearl server service and moniter if the issue appears again?"
I've restarted the service and the second error persists. As the first error occurs "randomly" I'm too sure of ruling this problem out just yet.
I'm thinking the first error may just be a once or twice off thing. I'll keep an eye on it though.
I'm more concerned about the second error:
"2014-05-27 01:50:43::120", "Error", "GetUser", "The format of the specified domain name is invalid. Resolving User:NT AUTHORITYANONYMOUS LOGON", " at ADUM.Translate.NameToDN(String Name)
at ADUM.K2UserManager2.GetUser(String Name)", "Additional Information: ", "GetUser(NT AUTHORITYANONYMOUS LOGON)"
"Lastly what versions of Blackpearl and Smartforms are you currently running and could you provide details on the setup of your environment?"
K2 Blackpearl: 4.6.6
K2 Smartforms: 1.0.3
K2 standalone server (includes SQL Server 2008R2, K2 BlackPearl, K2 SmartForms).
3 tier SharePoint environment (Web front end, Application server, SQL Server).
Windows Classic Authentication on both K2 and SharePoint.
Thanks again for the response. Any further questions just shoot!
Sean
Hi Sean,
Thank for supplying the requested information. Firstly are you Exchange or SMTP for your mail service? If you are using SMTP, please make the SMTP connection is correct. Please use the Connection String Editor to update the SMTP connection string and change the TLS to "None" and restart the K2 Service and see the error persists.
Secondly please attach your K2HostServer log to the post so i can look at it also.
Many Thanks,
Yannick
Hi Sean,
With regards to the first error where the "The remote name could not be resolved: 'bconnect'.", this states that remote name cannot be found. Please confirms if this is the correct remote name.
Many Thanks,
Yannick
Hi Sean_Heinen,
I found the following community article on the issue you are having, the error is not 100% on the dot correct however it is the same error.
Error:
64005 Failed to resolve 'SP:SharepointGroupProviderNameSharepointGroupName'
It seems that the resolution is to Re-running the App Registration wizard against the site indicated by the Group Provider url to resolve the issue.
Referencing community post:
http://community.k2.com/t5/tkb/articleprintpage/tkb-id/TKB_blackpearl/article-id/1953
Kind Regards,
Raymond
