Search
 
 
 

FAQ - K2 Runtime
1. While starting server I get “ NoLicenseFileException”
2. While connecting Management Tool to K2 Server I get big list exceptions with message Invalid Host or Port No.
3. During start up server, 'cmd' is not recognised as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'for' : return code '0x1'.
4. Build of examples fails on windows, with the message ‘winsock2.h’, no such file or directory.
5. Running K2 with the “k2daemon.cmd start” fails with just an empty dialog box.
6. How do I setup K2 Server Clusters?


K2 Runtime

1. While starting server I get “ NoLicenseFileException”
 

Please check that you have obtained valid license key and saved it as “License.K2” in k2_ccm_server_1_4/k2 folder, before starting K2 server. This file is sent via mail after successfully downloading K2. If you don’t receive the license key, please contact us at k2.support@iCMGworld.com

2. While connecting Management Tool to K2 Server I get big list exceptions with message Invalid Host or Port No
 

Please make sure that both TAO IFR and K2 server are started successfully prior to connecting management console to server. The specified host and port number must match with HTTP server host & port as specified in k2daemon.cfg file located in k2/bin directory.

3. During start up server, 'cmd' is not recognised as an internal or external command, operable program or batch file. NMAKE : fatal error U1077: 'for' : return code '0x1'.
 

K2 Window runtime expects DOS command console (cmd.exe) to be present in your PATH. The executable is usually located in C:\WINNT\System32 directory.

4. Build of examples fails on windows, with the message ‘winsock2.h’, no such file or directory.
 

Make sure that vcvars32.bat has been executed in the current console window. Run vcvars32.bat in the current console window, and rebuild the examples.
top

5. Running K2 with the “k2daemon.cmd start” fails with just an empty dialog box
 

This problem arises because necessary DLLs are missing from the System Path. In a command console window execute “k2server.exe” to find out the names of the DLLs that are missing. Run <k2install-dir>\supportSoftware\NT4Pdhdll.exe for adding missing DLLs to the System Path.

6. How do I setup K2 Server Clusters?
 

1. Add the hostname for the nodes participating in the k2cluster.cfg files on each K2 Server Installation. (Create one k2cluster.cfg with all the node names and copy it to the participant nodes).

2. Check for multicast address and port number in k2daemon.cfg of the Cluster participant nodes, the following entries needs to be the same on all hosts
k2.cluster.MulticastAddress = <m-cast address>
k2.cluster.MulticastPort = <port>

3. Start K2 Servers on each of the nodes.

Note: On starting the server on the first node in the cluster, the server console will show a FAILED message for the other nodes since they are not currently running. Subsequently, when the other nodes are started it would be recognized, and become part of the Cluster (On viewing the Management Console you will find the new Node in the Cluster Navigator pane on the left-hand side).
Refer to the Quick Start Guide for details.

 
K2 Assembly Tool
Financial Component
Knowledge Base
World Of
CCM Link
 

 
Copyright © 2008 iCMG. All rights reserved.
Site Index | Contact Us | Legal & Privacy Policy