Argument 'userFqn' may not be null or empty

  • 24 February 2022
  • 0 replies
  • 57 views

Userlevel 5
Badge +20
 

Argument 'userFqn' may not be null or empty

kbt142070

PRODUCT
K2 blackpearl
This article was created in response to a support issue logged with K2. The content may include typographical errors and may be revised at any time without notice. This article is not considered official documentation for K2 software and is provided "as is" with no warranties.
LEGACY/ARCHIVED CONTENT
This article has been archived, and/or refers to legacy products, components or features. The content in this article is offered "as is" and will no longer be updated. Archived content is provided for reference purposes only. This content does not infer that the product, component or feature is supported, or that the product, component or feature will continue to function as described herein.

Issue

A Server Error appears on Runtime:

Argument 'userFqn' may not be null or empty
Parameter name: userFqn

Image

Symptoms

The error only appears on Runtime and not on K2 Designer. Restarting the K2 Blackpearl service temporarily resolves the issue.

Troubleshooting Steps

To resolve this issue:
  1. Compare the K2 Designer and Runtime web.config files located in:
    ...K2 blackpearlK2 smartforms Designerweb.config
    ...K2 blackpearlK2 smartforms Runtimeweb.config
  2. Ensure that lines below exist on both files:
    <authorization>
       <deny users="?" />
    </authorization>
  3. If it is not present on one, place it right below the </authentication> tag.
  4. Save and close the file changed.
  5. Perform an IISRESET.

0 replies

Be the first to reply!

Reply