Skip to content

Troubleshooting - Common Problems#

Host#

Host not starting#

Symptom(s): When trying to start the host service, an error is thrown and the host does not start.

Cause(s): Multiple - require more investigation.

Resolution:

Check the following:

  1. Check that the license key is valid
  2. Check that the port 8080 (default) is not blocked by firewall
  3. User that the host service user (e.g.: "CMFUser") is created at the SQL server database with all the privileges
  4. Check that the database connectionstring in the app.config file is correct

If you are trying to start up the host service and get the message Host Service has stopped working:

  1. Open the folder where the host service is located. (Open the host service in windows services to know the path to host's folder)
  2. Open the Host.log file to see what went wrong.

Host is not available#

Symptom(s): As described in the problem title.

Cause(s): Multiple - require more investigation.

Resolution:

Check the following:

  1. Check the Web server for file Web.config. There is a setting for server hostname or IP address. The default is localhost.
  2. If it happens only in some particular web service interface, check the server trace log file Host_tracelog.svclog to see whether the service is loaded at server startup.

"An error occurred while trying to make a request to URI..."#

Symptom(s): The error means that the host service is not started or not running properly.

Cause(s): The host service is not running.

Resolution: Check if the host service is started:

  1. Click Start, then click Run and type Services.msc.
  2. Search for the Hosting Service service and check the service status.
  3. If the service status is not started right-click on the Service and click on Start.
  4. Else, restart the service.

Warning

While the service is restarting, it will not respond to incoming requests.

Note

If your host service is under an Load Balancing system, the host service status in all the servers where hosts are running must be checked.

Security#

"Unknown error, Invalid Username password"#

Symptom(s): As described in problem title, however the browser shows the correct user at the top-right side

Cause(s): Multiple - require more investigation.

Resolution: Try the following:

  1. Reset MSDTC, (flush data, stop session, start session)
  2. Check the database table [Security].T_User
  3. Check that the service Distributed Transaction Coordinator is running
  4. Check that the Firewall is not blocking the Distributed Transaction Coordinator port, MSDTC (TCP:135)

" ... :9090..., cross domain policy, ..."#

Symptom(s): As described in problem title.

Cause(s): Multiple - require more investigation.

Resolution: Try the following:

  1. Check database table [Services].dbo.T_ServiceProtocol for the port on which the service is listening
  2. Check file Web.Config for port <add key="Host" value="localhost:8080" />
  3. Check whether the port is blocked by firewall
  4. All the above configuration (1., 2. and 3.) must be define the same port number (the default value is 8080 for Critical Manufacturing server)
  5. The Web logon IIS uses the 80 port by default. This cannot be blocked by firewall.

Custom addin (function) does not show after successful logon#

Symptom(s): As described in problem title.

Cause(s): Security access may not be configured.

Resolution: Open configuration page (Admin\Configuration) and check check Guis\Security\Access\<addin>

LBO#

Error loading type Cmf.Presentation.Tool.LightBusinessObject.<xxxClient>#

Symptom(s): As described in problem title.

Cause(s): Framework.BootStrap may be out of date.

Resolution: Rebuild the Framework.BootStrap project.

"There is no binding configuration defined for contract..."#

Symptom(s): As described in problem title.

Cause(s): The file ServiceReference.ClientConfig does not match the LightBusinessObjects.dll when building the Framework.BootStrap project.

Resolution: Correct the ServiceReference.ClientConfig file.

"... binding NgpGuis.Web.dll error ..."#

Symptom(s): As described in problem title.

Cause(s): Client assemblies may be out of date.

Resolution: Delete all client Assemblies and rebuild from Light Business Objects (LBO).

Generic#

How to set the WCF trace log level#

Open the file Cmf.Services.HostConsole.exe.config.xml and change the log level:

<source name="System.ServiceModel.MessageLogging" switchValue="Warning,ActivityTracing">
<source name="System.ServiceModel" switchValue="Warning,ActivityTracing">

Note

The Windows Communication Foundation (WCF) Service Configuration Editor SvcConfigEditor.exe can also be used to edit the file.

How to add more languages (culture) support to the GUI#

In the ApplicationRoster.xml file, it is necessary to add the desired language (cultures) in the SupportedCultures section.

<?xml version="1.0" encoding="utf-8" ?>
<App>
<SupportedCultures>en-US;de-DE;zh-TW;zh-CN</SupportedCultures>
...
</App>

How to enable or disable static model history#

Open the configuration GUI and navigate to the static history configuration settings, there you will find a list of all static model objects. To enable or disable the history select a object and check or uncheck the box to enable or disable the history for that object.