Description
The archiving of a PCS 7 project with SIMATIC Manager aborts with a message although the project is closed and no other applications are accessing it.

Fig. 01  Warning when archiving a project

This behavior is due to the fact that there is still a WinCC database connected in the SQL Server.

Instructions
Please contact Siemens Industry Technical Support. The access channels to Technical Support are here.

Additional Keywords
Delete project, Reorganize, SQL Server Configuration Manager, SQL Server (WinCC), Service

Description
The instructions below are for installing and using the User Mode Process Dumper in WinCC and PCS 7. You can use this tool to create a memory image of a process in the event of a fault. This memory image can be useful for detailed diagnostics.

Contents
1 Installing and Using the "User Mode Process Dumper"
    1.1 Manual Starting of the "User Mode Process Dumper"
    1.2 Installing the "User Mode Process Dumper" for Automatic Monitoring
            of a Process
    1.3 Installing the "User Mode Process Dumper" with Hotkey
    1.4 Uninstalling the "User Mode Process Dumper"
2 Enabling and Using the "gflags" Tool
    2.1 Enabling the "gflags" Tool

Download

User_Mode_Process_Dumper_en.pdf ( 626 KB )

Keywords
Userdump tool, gflags, Memory overwrite, Memory swell, Memory overflow, Crash, Memory dump, dump WinCC, dumpen
 

Description:  
In order to have the Technical Support answer a service request, a precise description of the issue concerned is necessary. 

This entry provides a compilation of frequently asked questions about SIMATIC PCS 7 and a list of information required by the Technical Support.

1. General information required
2. License error message
3. Communication problems
4. Compilation problems
5. PLC faults
6. Time synchronization
7. Error messages from PCS 7 components/processes or operating system error messages
8. Additional information for Technical Support

In the case of PCS 7 V6 or higher, also refer to the manual "Process Control System PCS 7 - Service Support and Diagnostics V6.0" in Entry ID 15236128 or on the SIMATIC PCS 7 Manual Collection DVD.

1. General information required
The following information is essential for ensuring that your inquiry can be processed quickly:

• The exact wording of any error messages that are displayed.
• Configuration or topology of the system (server, clients, PLC). If Technical Support needs the precise system configuration in NetPro, then please proceed as described in Point 8.
  Procedure: Open the project / multiproject in the SIMATIC Manager. In Component View, expand all levels. Make a screenshot of the left window pane. (Use multiple screenshots if the configuration does not fit on one screen.)

The following information needs to be obtained from each computer involved with the support request (for example, if the issue involves loading the OS server from the ES, the following information is needed from both computers):

• Versions of PCS 7 and all SIMATIC software installed.
  Procedure: Select START > SIMATIC > Information > Installed Software > Products tab. Use the "Export" button to save the information in a CSV file.
• Details about the operating system (version, service pack).
  Procedure: Right-click MyComputer and select "Properties".
• Details about the Internet Explorer (version, service pack).
  Procedure: Open Internet Explorer and select Help > About Internet Explorer.
• Details about additional software installed (non-SIEMENS software).
  Procedure: Select "Start > Settings > Control Panel > Software". Create a list of all the programs installed along with their versions (without SIMATIC and Windows programs).

2. License error message
In rare situations it is possible that the system does not correctly identify an installed license. If the license error message relates to a component whose authorization/license is installed, the authorization/license in question should be copied back to the authorization/license disk or USB stick first and then be transferred back to the hard drive.
If this doesn't work, the following information is required in order to diagnose the cause.

    2.1. For all license errors

• List of all SIMATIC licenses installed on the computer in question.
  Procedure: Open the License Manager under "Start > SIMATIC > License Management > Automation License Manager". Open "File > Export... and create a .CSV file.

    2.2. License errors in WinCC

• Copy the files "License.log", "License_Info.log" (PCS7 V7.0 or higher) and "License.bak" files (if present) from the "...Siemens\WinCC\Diagnostics" folder.

    2.3 License errors in SIMATIC PDM

• Check the number of devices actually configured.
  Procedure: In the SIMATIC Manager, you open the Process Devices Plant View and count the number of devices.

3. Communication problems
The following information is required:

    3.1. Communication problems in WinCC

• If Lifebeat Monitoring / ASSET Management is configured, the status of all connections.
• Under Siemens\WinCC\Diagnostics, the diagnostic files from each computer involved with this issue (if possible, compress the files before sending, e.g. as *.zip archive).
• The Event Viewer of Windows (for procedure refer to Entry ID 15386411).

    3.1.1 Communication problems between PLC and OS

• The status of the connections in WinCC under Start > SIMATIC > WinCC > Tools > Channel Diagnosis.

    3.1.2 Communication problems between OS servers and clients

• The status of the connections in WinCC Explorer under "Tools > Status of Server/Client Connections".

    3.2. Communication problems in PDM
In case of communication queries related to the SIMATIC PDM software package, additional information is required on the points listed below.

• Checking the connection with the station using Lifelist or Longaddr (routing cannot be used here).
• Turn on communication protocol logging and repeat the communications test.
  Procedure: In the PDM, mark the communications log under "Tools > Settings... > Log as Debug Log. You can view the log under Tools > Open log.
• The Event Viewer of Windows (for procedure refer to Entry ID 15386411).

    3.3. Communication problems in the PLC

• Which LEDs are flashing or lit on the CPU and CP443-1.
• The diagnostics buffer of CP443-1.
• The diagnostics buffer of the CPU.
• The Event Viewer of Windows (for procedure refer to Entry ID 15386411).

4. Compilation problems

    4.1 CFC chart compiling problems

• Save the compilation log.
  Procedure: In the CFC Editor, select Options > Logs... and open the Log function. Select the "Compile" tab and then select "No filter" under "Filter" and save the log to a file via the "Save..." button.

    4.2 OS compiling problems

• Save the transfer.log file from your project path.

5. PLC faults

    5.1 CPU fault

• Save the diagnostics buffer in *.txt and *HEX.txt formats under "PLC > Diagnostics/Settings > Module Status".
  Procedure: Go online and select the CPU concerned in the SIMATIC Manager. Under PLC > Diagnostics/Settings > Module Status, you select the "Diagnostics Buffer" tab. Select "Save As..." and save the entries as a *.TXT file. Select "Settings...", mark the box for "Output event information in hexadecimal format", and confirm with "OK". Select "Save As..." and save the entries as a *HEX.TXT file.
• Precise details about when the fault occurred or whether a specific action was performed at that time (e.g. PLC > Load).
• If you have a redundant H system, and the CPU fault is due to a synchronization issue, save the diagnostics buffer of both CPUs.

    5.2 CP fault

• Save information from the CP's diagnostics buffer or from the CP's special diagnostics.
  Procedure: Go online and select the CP concerned in the SIMATIC Manager. Under PLC > Diagnostics/Settings > Module Status, you select the "Diagnostics Buffer" tab. Select "Save As..." and save the entries as a *.TXT file. Select "Settings...", mark the box for "Output event information in hexadecimal format", and confirm with "OK". Select "Save As..." and save the entries as a *HEX.TXT file.
• Precise details about when the fault occurred or whether a specific action was performed at that time (e.g. PLC > Load).

    5.3 IM153 fault

• Screenshot of the IM153 DP Slave Diagnostics
  Procedure: In "HW Config", go online and select the IM153 in the HW Config. Under PLC > Module Status > DP Slave Diagnostics, you open the diagnostics file. Create a screenshot.
• Precise details about when the fault occurred or whether a specific action was performed at that time (e.g. PLC > Load).

6. Time synchronization
On the subject of time synchronization in PCS 7, please also refer to the FAQs in Entry ID 22866327.

• Is time synchronization configured on all stations in the PCS 7 system?
• What is configured as the time master?
• Which bus is being used for time synchronization?
• Is PCS 7 being used in a Windows domain?

7. Error messages from PCS 7 components/processes or operating system error messages
If an error occurs in a PCS 7 application or a process, initially a precise description of the error behavior or wording (or screenshot) of the error message is of particular interest. The files listed below are required for more detailed analysis.

• Send all the files from the "Siemens\WinCC\Diagnostics" folder.
• If there are communications problems between OS clients and OS servers, send all the files from the "Siemens\Common\ace\bin\Diagnosis" folder.
• If errors occur on the Central Archive Server (PCS 7 V6.1), send the appropriate XML files from the "Siemens\StoragePlus\logs" path.
• The Event Viewer of Windows (for procedure refer to Entry ID 15386411) as *.EVT file.
• As precise a description as possible of the fault.

8. Additional information for Technical Support

    8.1 Export the system configuration from NetPro

If Technical Support needs the precise system configuration in NetPro, then please proceed as follows:

• In the SIMATIC Manager open the Component View of your project.
• Open NetPro in the SIMATIC Manager under Tools > Configure Network.
• Select Edit > Export.
• Select all the stations and all the options as well as an export path.
• If this is a multiproject, repeat this procedure for each project in the multiproject.

Fig. 01

   8.2 Export the complete PC system information

For some computer related issues, a detailed list of system information from the computer may be needed. Proceed as follows.

• Open the computer system information via "Start > Programs > Accessories > System Programs > System Information".
• Select File > Export... and save the information in a text file.

 8.3 Dr. Watson Log

If a Dr. Watson error occurs, a log file and a crash dump are created in the predefined paths. You can find the defined paths as follows:

• Open Dr. Watson under START > Run > Open > drwtsn32

When the Dr. Watson configuration dialog opens, make the following settings:

• Crash Dump Type: "Full" -- "Mini" is selected as default.
• Visual Notification -- this is not a default setting.

Fig. 02

Note:
Fig. 02 was created with Microsoft Windows XP SP 2. The Crash Dump Type setting might not be available in older operating systems and is automatically set correctly.

If no changes were made to the system, the files are located under C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson. The files are:

• drwtsn32.log
• user.dmp

For exchanging files with Technical Support please also refer to Entry ID: 18194667.

Keywords:
Technical Support, Hotline, Information, Help, Problem, Customer Support, Requirements, PCS 7, Dr. Watson, Diagnostics, System crash

Initial situation
Every time WinCC Runtime is deactivated on an operator station, the process control message "Failure Connection ID16#x" is generated by the CONEC block (FB88). The "x" in this message stands for the connection ID configured in the SIMATIC Manager.
This connection ID is inserted into the message as a process-associated value and is output on the operator stations that are still in runtime. If the runtime of the last of the operator station still in runtime is terminated, this process-associated value can no longer be transferred and "connection ID16#0" is displayed (up to PCS 7 V7.0) or "connection ID16#??" is displayed (as from PCS 7.1).
The same situation occurs during configuring on the Engineering Station if an OS project's runtime is started (OS simulation) and terminated again after the test. Here, too, no other WinCC runtime is started, so "connection ID16#0" (up to PCS 7 V7.0) or "connection ID16#??" (as from PCS 7.1) is also displayed and the message is displayed as struck through (see screenshot below).

Fig. 01

Description
The manual "SIMATIC Process Control System PCS 7 V7.0 SP1 Engineering System" (27002802), section 8.10.4 "How to configure a connection between a PC and a SIMATIC 400 station", contains the following information on how to prevent this message.

Notes from the documentation
To avoid the automation system generating messages during operation when the OS simulation starts or is terminated on the Engineering Station, the connection ID you select for the Engineering Station should be higher than 16#C00.

This is advisable while you remain in the configuration phase, as described above, and, for example, you start the OS projects in the OS simulation. You can also continue to use connection IDs higher than 16#C00 during the normal operating phase, although this means that no message will be generated either if this connection fails. You can change the connection ID by assigning a value greater than C00 in the "Local ID" column (see screenshot below).

Fig. 02

Creation environment
The pictures and downloads in this FAQ were created with PCS 7 version V7.0 SP1.

Description:
After upgrading of an older PCS 7 project to PCS 7 V7.0, it might happen that the setting of the chart installation pointer in CFC is lost.

If this setting is missing, you get the message "Object attribute not found" for the following actions:

• Opening of CFC charts "System error (1739:60451)"
• Deleting blocks from CFC charts "System error (1739:60451)"
• Creating new CFC charts "Insert CFC (1739:60451)"
• Complete compilation of AS with module driver "Create module driver (1739:60451)"

Fig. 01

Instructions:
Proceed as follows to set the chart installation pointer anew.
 

No.	Procedure
1	Open CFC Open any CFC chart of your upgraded project. Acknowledge the system message that appears. Switch to the "Runtime sequence" view (Edit > Change runtime sequence). Acknowledge the system message that appears.
2	Set chart installation pointer In the tree structure of the "Runtime sequence" view, you mark the OB into which you wish to insert the blocks by default (e.g. OB32).   Open the OB's pop-up menu and select the "Predecessor for Insert Position" item. Fig. 02   Acknowledge the changes of the chart installation pointer. The position at which the runtime group of the next chart is created is marked green in the tree view.

Creation environment:
The pictures and downloads in this FAQ were created with PCS 7 V7.0 SP1.

Description:
This error message is displayed if you attempt to create the project in a compressed folder. If you then press the "OK" key, a second error message is displayed: "PCS 7 wizard (2772:106) -- Internal error when creating the plant hierarchy".

You cannot use this Windows feature (compressed folder) for project folders in the PCS 7 environment. Refer also to Entry ID 26447221 with regard to error messages during OS compilation.

QUESTION:
I have created a new project. Why, when I insert blocks in a CFC plan, do I get the message "HMI properties could not be created"?

ANSWER:
In the Control Panel under Country Properties you have set "English (USA)" and have made a user-defined setting in the country settings.

In order to stop this message appearing open Country Settings via Start>Settings>Control Panel. There you select the "Numbers" tab and enter a period instead of a comma for the decimal separator character.

QUESTION:
I have incorporated GSD files of another manufacturer into a project. Why do I get an error message when I open HW Config?

ANSWER:
You have opened the hardware configuration from an ES on which it wasn't originally configured. In addition, you have incorporated GSD files from another manufacturer, and have probably not copied them onto the other ES (in S7Data/GSD). This results in the error message "Cannot start HW Config".

If you open the hardware configuration from a project in which GSD files from another manufacturer are incorporated and these are not under "S7DATA/GSD", you get the following error message (STEP7 V3.2 / V4.01):

This refers to the missing GSD file. As a remedy you copy the GSD file(s) of the other manufacturer onto all stations that process the project. In version V4.02 and higher GSD files are contained in the project data. Thus the procedure described above doesn't apply.

Description
One cause could be that you are accessing the block in Debug mode (SCL or STL). Values could still be forced in the CPU.

Remedy

• Terminate forcing and remove the connection cable. This terminates the Debug access.
• If this doesn't clear the problem, do an overall reset for the CPU.
• For test purposes download a DB. In this way you can determine whether the problem is connected specifically to the block displayed or whether no blocks at all can be loaded into the CPU.

ANSWER:  
When installing PCS 7, you did not select the option "TH" (Technology Hierarchy). This means the system cannot make the link to the CFC or SFC chart and the chart is not found. 

Remedy:
Close the project and install the TH from the PCS 7 Installation CD with the existing installation. After completing installation, you can now open and edit the CFC and SFC charts.

Keywords:Installation, Installation problem

ANSWER:
In my SIMATIC PCS 7 project I upgrade the user function blocks contained in it. These function blocks come from a self-created block library. After copying the latest blocks from the library into the block container of my project, I get the following error message when I attempt to run an attribute match:

[Add Function Block (256:107):
"The object "Standard Library\System Function Blocks\ Symbols\Alarm_8P" of the "Symbol" type could not be copied. Continue with procedure?]

The block that you want to update in your project contains an ALARM_8P (SFB 35) call. When you run a block attribute match, the system function block SFB 35 is indeed found in the block container of your project, but not in the library that contains the user function block.

Remedy:
There are two ways of avoiding this error message.

1. Add the SFB 35 to your library.
2. Update your project via the CFC by creating a new chart there and placing the blocks to be update in this new chart. If the CFC detects that instances of this block type are already available, it queries whether updating and an attribute match should be done.
   Note:
   In order to avoid unnecessary use of resources, you should then delete the block and chart.

Keywords:
Configuration, Updates