Skip to main content
Nintex Community Menu Bar

When running K2 4.7 blackpearl setup manager on the 2nd server node (K2 farm environment), setup manager will be held in a wait state

  • February 16, 2021
  • 0 replies
  • 16 views
  • Translate
MillaZ
Nintex Employee
Forum|alt.badge.img+21
  • MillaZNintex Employee
  • Nintex Employee
  • 667 replies
 

K2 blackpearl setup manager hangs when running on the 2nd server node

KBF200006

PRODUCT
K2 blackpearl 4.7
BASED ON
K2 blackpearl 4.7
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

There is a known issue when running the K2 4.7 blackpearl setup manager on K2 farm environment, it will complete the configuration on 1st server node successfully.  But when you run the setup manager on the 2nd server node, setup manager hangs with an error mesaage like "Distributed install in progress - K2 blackpearl Server on machine: "

 

 

Symptoms

When running the setup manager on 1st K2 server node, it will add a "[SERVER_BUSY]" variable value to the "[HostServer]. [Configuration]" table and it will remain after the configuration is done.

When you try to run the setup manager on the 2nd server node, it hangs because "[SERVER_BUSY]" variable value is still set.

 

Image

 

As the above image displays [SERVER_BUSY] variable value is set after running the setup manager on the 1st K2 server node.

Resolution

  • Re-run the K2 blackpearl setup manger on the 1st server node to remove the variable value
  • Select Configure K2 blackpearl
  • Complete the configuration steps without making any changes 

This will reset the "[SERVER_BUSY]" variable token value. Then you should be able to run the setup manger on the 2nd server node successfully.

 

 

Check out these Nintex University Learning paths: https://community.nintex.com/p/NintexUniversity
    Did this topic help you find an answer to your question?

    0 replies

    Be the first to reply!

    Reply


    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsCookie Settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie Settings