The very first requirement for solving potential problems, which can appear during configuration/operation of CMWServer, is clear understanding or terms. Keeping this in mind, all possible problems can be classified into main catefgories described in the next sections.
CMWServer component includes several panels for manager configuration, operations with configuration file and diagnostics. However:
The CMWServer manager is designed to be able to start always, even if there are some errors in configuration and/or environment which prevent from successful start of CMW server. The main reasons why the manager itself can't be started are:
In either case, WinCC OA log shall contain error message, describing the reason why CMWServer manager was not able to start.
When CMWServer manager has started successfuly, it immediately tries to create and start CMW server according to configuration. If by any reason CMW server can't be created and/or started, the message with detailed description of reason is written to WinCC OA log, but CMWServer manager keeps running.
Such state of manager must be clearly indicated in different panels of CMWServer component, for example, the manager state will be IDLE in different panels where the 'overall' state is displayed. In the list of managers such state is indicated by STOP state in CMW column in table:
In either case, WinCC OA log shall contain message with clear (hopefully) description of what is wrong in configuration. Here are some examples of messages which can appear; exhaustive list of possible errors is too long, but all of them must be descriptive enough.
Example 1: DPE, mentioned in configuration file, does not exist:
Example 2: Empty name for 'data' tag in configuration:
It can happen potentially that CMW server was started successfully, but 'does not work as expected', for example: DPE value changes do not reach CMW clients who subscribed to corresponding properties; or SET requests from CMW clients do not really update DPE value.
In principle, there can be many reasons for such problems, including:
The first type of problem can be detected using corresponding diagnostics panels and properly configured UNICOS system integrity for CMWServer.
Other types of problems should normally result in some message in WinCC OA log, provided that problem occured inside CMWServer process. One example of such 'unexpected' message:
This particular error was explained in diagnostics chapter, as well as measures to solve such problem. It is shown here to stress once more: WinCC OA log is a main tool for troubleshooting.
Of course, by design CMWServer manager shall not crash under any rcircumstances. Should this happen, and especially if this can be reproduced, the only solution is to contact support Iceco, providing enough relevant information. ntro ls.Su ppor t@cer n.ch