Unable to register 'Oracle Service Instance' - page hangs and doesn't  respond

  • 24 February 2022
  • 0 replies
  • 6 views

Userlevel 5
Badge +20
 

Unable to register 'Oracle Service Instance' - page hangs and doesn't  respond

kbt145016

PRODUCT
K2 blackpearl
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

Unable to register 'Oracle Service Instance' using the Smartobject Service Tester tool, the page hangs and doesn't respond.

Symptoms

After waiting for the register service instance, the following error was found in the K2 host server logs located in "C:Program Files (x86)K2Host ServerBin:

 

""96691534","2018-03-22 22:51:04","Error","System","2025","InternalMarshalError","SourceCode.Hosting.Server.Runtime.

HostServerBroker.InternalMarshal","2025 Error Marshalling SourceCode.SmartObjects.Runtime.SmartObjectManagementServer.RegisterServiceInstance, Timeout expired.

The timeout period elapsed prior to completion of the operation or the server is not responding. InnerException: The wait operation timed out","","","[K2 server name]:D:Program Files (x86)K2 blackpearlHost ServerBin","96691534","a8ae70f29305448bb859a43373b86303","" "96691535","2018-03-22"

 

Depending on the size of the Database, creating a service instance can either be fast or slow. If the message "not responding" appears, just ignore it and let process run.

Troubleshooting Steps

You can resolve this by increasing the CommandTimeout on K2HostServer.exe.config:

 

1. Open K2HostServer.exe.config file which is the default location for K2: "C:Program Files (x86)K2Host ServerBin"

2. Search for the "commandtimeout" keyword. (There should be 2 entries.) 

3. Edit the following line and increase the default value of commandtimeout="30" to "90" or "120" (always start from a smaller value and increase only if necessary.) Save the changes in configuration file.

4. Restart the K2 service.


0 replies

Be the first to reply!

Reply