show the entry list

WinCC -- Setting up development environments -- Installing and upgrading software 
What are the possible causes of an unsuccessful Microsoft SQL Server 2005 Express installation or why is creating or opening a WinCC flexible 2008 project aborted? 
Why do I receive errors during the upgrade installation to WinCC version V7.0 SP2? 
Why should you not install the Microsoft security patches KB2467174, KB2467175, KB2465361 and KB2465367 in WinCC, PCS 7 and WinCC Professional V11? 
Which Microsoft Patches ("Security Patches" and "Critical Patches") have been tested for compatibility with SIMATIC WinCC? 
How can you switch the Microsoft SQL Server Management Studio Express to English on the bundle PC IPC 477C with WinCC V7.0 SP1? 
Why does the installation of Microsoft SQL Server 2005 abort? 
Why can't you install the SQL server from WinCC V6.2 or WinCC V6.2 SP2 after installing WinCC flexible 2008? 
How do you install WinCC V7.0 on a MUI operating system if the language set in Windows is not English? 
What can you do if installation of Security Patch KB929046 fails in the Windows Server 2003 R2 SP2? 
Why is it not possible to activate the subcomponent "Common" while installing the "Microsoft Message Queuing" component? 
How can you install WinCC while the computer is logged on to a domain? 
Why does installation of the "Microsoft Message Queuing Services" abort with an error message? 
What is the difference between an upgrade and an update? 
How do you upgrade the WinCC Options V6.1? 
How do you upgrade WinCC V6.0 to WinCC V6.0 SP3? 
How do you migrate WinCC V4.x projects to WinCC V6.x and WinCC V7.x? 
How can you regularly receive updates to the latest versions of WinCC? 
Which settings do you have to make to set up a redundant single-user station in Microsoft Windows XP SP2? 
How can you analyze errors when installing WinCC? 
Why is the Setup of SIMATIC WinCC aborted at the ACE component (Active Communication Environment)? 
How should you proceed if installation of the Microsoft SQL server fails? 
Missing SQLUNIRL.dll when Installing SIMATIC WinCC V6 
Why does the SQL server 2000 SP3 not appear as present during the installation of WinCC V6.0 SP3, even though it is installed? 

What are the possible causes of an unsuccessful Microsoft SQL Server 2005 Express installation or why is creating or opening a WinCC flexible 2008 project aborted?Go to beginning
Part number:

Description
WinCC flexible 2008 uses the Microsoft SQL Server 2005 Express Edition as an integrated database. It is installed by default with WinCC flexible 2008 ES.

There are many possible causes for a defective or damaged database installation.

If installation or configuration of the Microsoft SQL Server 2005 Express Edition was unsuccessful or damaged (such as by another installation), then usually all you need to do is reinstall/reconfigure the Microsoft SQL Server 2005 Express Edition.

Contents

  1. Installation problems with MS SQL-Server 2005 Express

    1.1 Installation of the SQL Server for WinCC V7.0 not possible
    1.2 Installation of the SQL Server for WinCC V6.2 not possible
    1.3 Re-installing of the SQL Server
    1.4 Problems installing Microsoft SQL Server 2005 Express with WinCC flexible 2008
       
  2. Known problems with MS SQL-Server 2005 Express with WinCC flexible

    2.1 Abort when creating or opening a WinCC flexible project
    2.2 Abort when creating or opening a WinCC flexible project
          via the Remote Desktop connection

1. Installation problems with the Microsoft SQL Server 2005 Express
 
No. Procedure
1.1 Installation of the SQL Server of WinCC V7.0 not possible

Description
The WinCC V7.0 SQL Server cannot be installed.

Possible cause
WinCC flexible Start Center is enabled.

Remedy
You can only install the WinCC V7.0 SQL Server if the WinCC flexible Start Center is disabled.

Procedure

  • Right-click the icon in the taskbar Notification Area, the "tray" area of the taskbar.
  • Then click "SIMATIC WinCC flexible Auto Start > Disable."

Note
What you should watch out for when operating Microsoft SQL Server 2005 on a PC with multiple processors or cores is explainedin Entry ID: 59703368.

1.2 Installation of the SQL Server of WinCC V6.2 not possible

Description
The WinCC V6.2 SQL Server cannot be installed.

Possible cause
For example, the influence of other SQL instances.

Remedy
You can only install the WinCC V6.2 SQL Server if
the WinCC flexible Instance of the Microsoft SQL Server 2005 Express Edition has been uninstalled.

Procedure
More information and notes on procedure are available in Entry ID: 30576253.

Note
What you should watch out for when operating Microsoft SQL Server 2005 on a PC with multiple processors or cores is explainedin Entry ID: 59703368.

1.3 Re-installing the SQL Server

Description
The SQL Server must carry out a re-installation.

Possible cause
For example, the influence of other SQL instances.

Remedy
Carry out re-installation.

Procedure

  • Insert the product DVD.
  • Start the "setup.exe" file in the CD_1 directory.
  • Carry out the installation.
  • Accept the license agreement - but do not change the presetting in the other dialogs.
  • Reboot the PC after installation.
1.4 Problems installing Microsoft SQL Server 2005 Express with WinCC flexible 2008

Description
Uninstallation of the SQL Server and re-installation of the SQL Server by way of the WinCC flexible Setup.  

Possible cause
The user data of Microsoft SQL Server 2005 Express might be damaged.

Remedy
Uninstallation of the SQL Server and re-installation of the SQL Server.  

Procedure

  • Uninstall the entries below by way of "Control Panel" > "Software"
    "Microsoft SQL Server 2005 Express Edition (WINCCFLEXEPRESS)"
    "Microsoft SQL Server Native Client"
    "Microsoft SQL VSS Writer"
    "Microsoft SQL Server Setup Support Files (English)"
  • Start the repair installation of WinCC flexible by way of "Control Panel" > "Software" >"WinCC flexible 2008" "Change" >"Repair program".
    The Setup recognizes that the SQL Server is missing and re-installs the SQL Server.
  • Now restart your operating system.
  • Start WinCC flexible and create a new project.

Note
If WinCC V11(TIA Portal) is installed, you must do a repair installation here as well, because the uninstallation described above also removes the instance of the SQL Server from WinCC V11.

2. Known problems of the MS SQL Server 2005 Express with WinCC flexible
 
No. Procedure
2.1 Abort when creating or opening a WinCC flexible project

Description
Creating or opening a project is aborted with an error message.

Note
See also 2.2 in the case of a Remote Desktop connection!

Possible cause
The Microsoft SQL Server 2005 Express Edition user data is possibly damaged or no longer matches the installed instance.

Remedy
Delete the folders with the user data of the WINCCFLEXEXPRESS instance.

Procedure

  • Close WinCC flexible 2008.
  • Right-click the icon in the taskbar
    "Notification Area", the "tray" area of the taskbar.
  • Then click "SIMATIC WinCC flexible Auto Start > Close."
  • Open the Windows Explorer.
  • In the Windows Explorer address bar, enter the path below including system variable and delete the entire "WINCCFLEXEXPRESS" folder:

    Windows XP
    %USERPROFILE%\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\WINCCFLEXEXPRESS

    or

    %USERPROFILE%\Local Settings\Application Data\Microsoft\Microsoft SQL Server Data\WINCCFLEXEXPRESS

    Windows Vista
    %USERPROFILE%\AppData\Local\Microsoft\Microsoft SQL Server Data\WINCCFLEXEXPRESS


    Fig. 01 - Environment-Variable + Path

    Windows 7
    %USERPROFILE%\AppData\Local\Microsoft\Microsoft SQL Server Data\WINCCFLEXEXPRESS

    Note
    With the system variable "%USERPROFILE%" the directory of the logged-on user is opened dynamically.
2.2 Abort when creating or opening a WinCC flexible project via the Remote Desktop connection

Description
Creating or opening a project is aborted with an error message.

Note
See also 2.1!

Possible cause
The Microsoft SQL Server 2005 Express Edition is installed on a Windows XP SP2-based computer. The user tries to gain access over Remote. The connection fails.

Remedy
Install the relevant Microsoft Hotfix for your operating system.

Procedure
This error was cleared with the Microsoft Hotfix "KB896613", which can be downloaded at this link:

English: http://support.microsoft.com/kb/896613/en-us
German: http://support.microsoft.com/kb/896613/de

Additional Keywords
SQL Express

Why do I receive errors during the upgrade installation to WinCC version V7.0 SP2?Go to beginning
Part number:

Description
If the upgrade installation to WinCC version V7.0 SP2 fails, this may be because you omitted to uninstall the WinCC options before installing the upgrade. You can find the upgrade installation procedure on your DVD under "Install_and_Release-Notes > Language > InstallNotes.pdf". It states in point 2 of the section on "Procedure", section 7.3 of this document, that the WinCC options have to be uninstalled before an upgrade is installed.

Remedy
If you have begun to install an upgrade, you have to perform a complete new installation even though a WinCC option, such as the Web Navigator, has been installed. You can find a description of this in the afore-mentioned document in section 5.3.

Keywords
Upgrade, Update, Service pack

Why should you not install the Microsoft security patches KB2467174, KB2467175, KB2465361 and KB2465367 in WinCC, PCS 7 and WinCC Professional V11?Go to beginning
Part number:

Description
Installation of one of the Microsoft security patches KB2467174, KB2467175, KB2465361 or KB2465367 causes a massive drain on resources (increase in handles) in WinCC Runtime (OS Runtime, WinCC Runtime Professional V11). This consumption of resources can lead to a standstill of WinCC Runtime.
It is strongly recommended not to install any of the Microsoft security patches KB2467174, KB2467175, KB2465361 or KB2465367.

Detailed information about these Microsoft security patches is available at these links:

A remedy is given in the entries below under the corresponding KB numbers.

Note
Refer also to
"Which Microsoft Security Patches have been tested for compatibility with SIMATIC WinCC?" in Entry ID: 18752994 and
"Which Microsoft Security Patches have been tested for compatibility with SIMATIC PCS 7?" in Entry ID: 18490004.

Which Microsoft Patches ("Security Patches" and "Critical Patches") have been tested for compatibility with SIMATIC WinCC?Go to beginning
Part number:

Instructions
Microsoft regularly rectifies security gaps in its products and makes these fixes available to its customers in the form of official patches. This usually happens every second Tuesday in the month, on so-called "Patch Tuesday". Microsoft divides up the updates into numerous different classifications
(http://support.microsoft.com/kb/824684/EN-US/
and
http://support.microsoft.com/kb/824684/de).

However, you only have to install "Security Patches" and "Critical Patches" to ensure that SIMATIC WinCC operation is secure and stable. For this reason, a WinCC test configuration has been set up in order to test the compatibility of the WinCC software with the above-mentioned patch classifications ("Security Patches" and "Critical Patches"). This system always features the very latest of the released versions of WinCC and Microsoft products released for operating these versions of WinCC. Keeping pace with the updates published by Microsoft, compatibility tests with the latest released versions of WinCC are performed on the test system.
The attached table in xls format provides precise information about the Microsoft "Security Patches" and "Critical Patches" which are tested for compatibility. As far as possible, this is updated within two weeks after publication of the latest updates of the classification designated.
If reflects the Microsoft products installed in the WinCC test configuration. Therefore, a discrepancy between this list and the products installed in the project cannot be excluded. If a system requires more updates than contained in the published list, these updates are requested according to the additional installed products / software components. In this case, it is up to the user to install these updates.
We recommend installing all the available updates of both the named classifications to ensure that the system is protected.
However, we cannot say anything about the compatibility of such updates that we have not tested. Therefore, we recommend installing all the updates in separate project-specific test environment prior to rolling out the updates in the productive environment.

Download
 
Description Download
Excel file Security_Patches.xls ( 704 KB )
Packed XML and model files Security_Patches_XML.zip ( 60 KB )
Table 01

In rare cases an update might have a negative effect on our software in our tests. This is noted in the "Comment" field in the list above. Furthermore, we inform you as fast as possible by newsletter of any indications and the resulting remedies.

Recommended procedure for patch management with the Microsoft Windows Server Update Service (WSUS)
These instructions assume that you have a WSUS installed for your WinCC system. How to proceed with the WSUS is described in Entry ID: 38621083.
 
No. Procedure
1 WSUS configuration:
In the "Products and Classifications" dialog you select the "Products" tab and then all the Microsoft products relevant for the system.
2 WSUS configuration:
In the "Products and Classifications" dialog you select the "Classifications" tab and then "Definition Updates", "Security Updates" and "Critical Updates".


Fig. 01

3 WSUS configuration:
Create the project-specific groups for distribution of the updates in the system.
4 Download the "Security_Patches.xls" Excel table above onto your computer.
5 Open the table and set the filter to "Failed" in the "Test Result" column.
6 Check the "Comments" column to see whether these updates have been replaced.
7 WSUS administration:
Select all the available updates in the "Critical Updates" and "Security Updates" categories and then deselect the non-released patches as in the list above. Release the patches for installation in the groups created.
8 Log in on the clients connected to the WSUS using an administrative account (the clients were configured to receive the updates from the WSUS).
9 Execute the updates offered.
Table 02

You can find more precise information about Industrial Security in connection with WinCC software in the WinCC Security Concept in Entry ID: 60119725.
For more detailed explanations about Microsoft Updates and the WSUS visit the following Microsoft sites.

Notes

  • To find out which Microsoft Patches are installed on the PC, refer to Entry ID: 48844294.
  • This guideline applies only as from WinCC V6.0 SP4.

Warning
The procedure described above does not apply for new Microsoft Service Packs which still require an explicit release for use. If the patches require a higher version of the Microsoft software, then refer to the "WinCC Install Notes" or Entry ID 21927773 to check whether these higher versions of the software or Service Packs are released for SIMATIC WinCC.

Additional Keywords
Windows Update Service, Security Patch
 

How can you switch the Microsoft SQL Server Management Studio Express to English on the bundle PC IPC 477C with WinCC V7.0 SP1?Go to beginning
Part number:

Description:
In the preinstallation of the bundle HMI IPC 477C with WinCC V7.0 SP1, the German version of Microsoft SQL Server Management Studio Express Service Pack 2 (SSMSE SP2) was installed.
There are familiar mechanisms you can use to change the language (German and English) of the Windows XP embedded operating system and WinCC. If you wish to work directly in the SQL database, the "SSMSE SP2" is only available in German.
If you need the "SSMSE SP2" in English, you can uninstall the German version and install the English version. You can procure the English version free of charge from the following Microsoft link: "Microsoft SQL Server Management Studio Express" .
Download the SQLServer2005_SSMSEE.msi file and not the SQLServer2005_SSMSEE_x64.msi file.

Instructions:
 
No. Procedure
1 Uninstall the German version of Microsoft SQL Server Management Studio Express on your IPC 477C under "Start > Settings > Control Panel > Software".
2 Install the English version of Microsoft SQL Server Management Studio Express that you have procured from the link specified above.

Why does the installation of Microsoft SQL Server 2005 abort?Go to beginning
Part number:

Description:
The security patch KB 954459 (SP2 for MSXML 6.0) is installed on the Windows XP SP2 operating system via Windows Update. Then SP3 is installed on this system.
Now, if you install the Microsoft SQL Server 2005 on this system, the Setup is aborted when installing MSXML. This file is protected by the KB installed and can no longer be removed in Windows XP SP3.
This makes it impossible to install the SQL server on this system.

Remedy
Open the Microsoft Article 968749 at the link below:
http://support.microsoft.com/kb/968749/ and follow the instructions in the "Remedy" section.
Then restart WinCC Setup and the installation.

Why can't you install the SQL server from WinCC V6.2 or WinCC V6.2 SP2 after installing WinCC flexible 2008?Go to beginning
Part number:

Fault description:
WinCC flexible 2008 is already installed and the WinCC V6.2 and WinCC V6.2 SP2 SQL server cannot be installed.

Cause:
A possible cause is the influence of the different SQL instances that are installed product-specifically with the installation of WinCC flexible or WinCC.

It is imperative that you keep to the following installation sequence when you install WinCC V6.2 or WinCC V6.2 SP2 and WinCC flexible 2008:

  1. WinCC V6.2 or WinCC V6.2 SP2
  2. WinCC flexible 2008

If you have already installed WinCC flexible 2008, consider the following procedure.

Remedy:
You can only install the SQL server from WinCC V6.2 or WinCC V6.2 SP2 if the WinCC flexible instance of the Microsoft SQL Server 2005 Express Edition was deinstalled. WinCC flexible 2008 does not have to be deinstalled.

Procedure:
The table below describes the deinstallation of the WinCC flexible instance of the Microsoft SQL Server 2005 Express Edition:
 
No. Procedure
1 Deinstalling SQL instance
A complete deinstallation of WinCC flexible 2008 is not required.
  • Open the "Control Panel" of your operating system.
  • In the "Control Panel" click on "Software".
  • Select "Microsoft SQL Server 2005" and click on "Remove".


Fig. 01 - Remove program

2 Selecting Desktop Engine
  • Select "WINCCFLEXEXPRESS" in the opened dialog.
  • Click on "Next".


Fig. 02 - Select SQL-Instance

3 Finishing deinstallation
  • Click "Finish".
  • Reboot the PC after finishing the deinstallation.


Fig. 03 - Deinstallation of teh SQL-Instance

4 Installing WinCC and the SQL instance
  • Install WinCC V6.2 or WinCC V6.2 SP2
  • Start the "Setup.exe" file on the product DVD of WinCC flexible 2008 and execute the installation.
  • Accept the license agreements.
  • Click on "Next" and do not change the presettings in the following dialogs of the installation - see also Fig.04.

    Note:
    If the presettings are not changed only the WinCC flexible Instance of the Microsoft SQL Server 2005 Express Edition is installed.
     
  • Reboot the PC after installing the SQL instance for WinCC flexible 2008 again.


Fig. 04 - Installing SQL-Instance

Keywords:
Microsoft SQL Server 2005 SP1, Microsoft SQL Server 2005 SP2, Microsoft SQL Server 2005 Express

How do you install WinCC V7.0 on a MUI operating system if the language set in Windows is not English?Go to beginning
Part number:

Introduction
You receive the message described below only if "English" is not used as installation language with MUI. The FAQ describes this taking the example of "Deutsch" (German) as the installation language (which is why the figures are in German).

Installation
You install WinCC V7.0 on an MUI operating system and use "Deutsch" as the installation language. The installation is made, but is aborted just before completion, because the hotfix "Windows XP SP2 KB319740" cannot be installed.


Fig. 01

This message is issued because during installation of WinCC V7.0 an attempt is made to install the hotfix for German. However, the MUI operating system is based on English, so the hotfix for Windows must also be installed in the English version.

Solution
The following options are open for installing WinCC V7.0 without errors.

  • You install WinCC V7.0 using the English language interface.
  • You install the English hotfix "Windows XP SP2 KB319740" before the installation and then you can use the German language interface for installing WinCC V7.0.

Manual installation of the hotfix "Windows XP SP2 KB319740"
Follow the instructions below to install the hotfix beforehand.
 
No. Procedure
1 Open the CD-ROM contents
Open the WinCC V7.0 Installation CD-ROM by right-clicking on your drive. Now select the "Open" option.


Fig. 02
2

Open path for hotfix
Open the path in which the hotfix is located.
The path is: WinCC V7.0 > InstData > KB 319740 > english


Fig. 03

3 Install the hotfix 
Double-click the file "WindowsXP-KB319740-v5-x86-ENU.exe" to start installation of the hotfix.


Fig. 04

Now follow the instructions until installation of the hotfix is completed.

Then you have the hotfix "Windows XP SP2 KB319740" installed and can start with the installation of WinCC V7.0. Now that the hotfix has been installed manually, you can now also use the German language interface for the installation.

Keywords:
Installation abortion, Installation error, Multi User Interface

What can you do if installation of Security Patch KB929046 fails in the Windows Server 2003 R2 SP2?Go to beginning
Part number:

Description:
The requirement for installing WinCC V6.2 is that Security Patch KB929046 is installed from the "Microsoft Service Packs & Tools" DVD supplied. The following error might occur sometimes when installing the patch in Windows Server 2003 R2 SP2:


Fig. 01

In this case you reinstall SP2 for Windows Server 2003 from the "Microsoft Service Packs & Tools" DVD supplied without uninstalling the SP2 already installed. Then you can install the Security Patch and WinCC.

Why is it not possible to activate the subcomponent "Common" while installing the "Microsoft Message Queuing" component?Go to beginning
Part number:

Instructions:
To install the "Microsoft Message Queuing" component for SIMATIC WinCC, you proceeded as follows.

  • (WinCC V6.0) "WinCC Information System > Installation of WinCC > Microsoft Message Queuing > Procedure for Windows XP > Item 5".
  • (WinCC V6.2 / WinCC V7.0) "WinCC Information System > Installation Notes > Installation of WinCC > How to Install Microsoft Message Queuing > Procedure for Windows XP > Item 5".

Please choose here the subcomponent "General" which corresponds to the subcomponent "Common" in the German Microsoft Windows XP system. The further installation steps are correctly described in the "WinCC Information System". 

How can you install WinCC while the computer is logged on to a domain?Go to beginning
Part number:

Description:
In SIMATIC WinCC, it is not possible to do an installation of WinCC while the computer is logged on to a domain.

Instructions:

  • Log on locally with administrator rights to the computer in question. An installation under the Microsoft Windows operating system requires administrator rights.
  • Refer to the requirements for installation in the SIMATIC WinCC Installation Notes or in the relevant section of the WinCC Information System. 
  • Once the installation is finished, you can log on to the domain again as usual.

Note:
More information regarding the use of WinCC systems on a domain is available in the WinCC Information System under the keyword "Domain".
Information on the installation of WinCC can be found in the WinCC Information System under "Installation Notes > Requirements for Installation".

Why does installation of the "Microsoft Message Queuing Services" abort with an error message?Go to beginning
Part number:

Instructions:
The reason why the installation aborts is that "File and printer release for Microsoft networks" is missing in the operating system.

  • Windows XP/2003/2000
    Go to "Network environment > Properties > LAN Connection > Properties" and check whether "File and printer release for Microsoft networks" is installed. If this service is not activated, activate it.
  • Windows Vista
    Go to "Start > Networks > Networks and Release Center > Manage network connections" and check whether "File and printer release for Microsoft networks" is installed.
    If this service is not activated, activate it.

Note:
For this process you need to have the Microsoft Windows Installation CD at hand.

Then you can install "Microsoft Message Queuing Services" as described in "WinCC Information System".

What is the difference between an upgrade and an update?Go to beginning
Part number:

Configuration Notes:
An upgrade is an upgrade to a new version usually with additional functions. In this case one speaks of a new "major release". This upgrade package is usually billable and also includes a new license. An upgrade is from WinCC V5 to V6, for example.

An update is a further development within a program version (e.g. from WinCC V6.0 SP3 to SP4). Updates are always free of charge and provide no or only minor additional functions.

How do you upgrade the WinCC Options V6.1?Go to beginning
Part number:


Instructions:
Proceed as follows to upgrade the "new" WinCC Options V6.1:
No. Procedure
1 Deinstall your current WinCC Option(s) by going to "Start > Control Panel > Software", select the option and remove it.
2 Boot your computer.
3 Install WinCC V6.0 SP3.
4 Reboot your computer.
5 Install your WinCC Option V6.1.

Now your system is installed correctly.

How do you upgrade WinCC V6.0 to WinCC V6.0 SP3?Go to beginning
Part number:


Instructions:
To upgrade WinCC V6.0 to WinCC V6.0 SP3 it is mandatory to deinstall all WinCC V6.0 options beforehand.
Otherwise there might be errors and abortion of the SP3 upgrade process.

The WinCC options that WinCC V6.0 uses cannot be used for WinCC V6.0 SP3. There are new versions of the WinCC Option that are released for WinCC V6.0 SP3. You should install these after the WinCC V6.0 SP3 upgrade.

How do you migrate WinCC V4.x projects to WinCC V6.x and WinCC V7.x?Go to beginning
Part number:

Instructions:
WinCC V4 projects cannot be migrated directly to WinCC V6, this can only be done via WinCC V5.1.

Migrate your WinCC V4.x project to WinCC V5.1 first of all. Then migrate the WinCC V5.1 project to WinCC V6.x.

You can find information about the migration in the "Release Notes" in WinCC V5; they are stored on your WinCC installation under "...\Siemens\WinCC\Documents\English\ReleaseNotes.chm".

This information can also be downloaded via the following link:

Migration aid from WinCC V4.x to WinCC V5.1 ( 116 KB )

Ordering information for WinCC V5.1 is available in Entry ID 10087200 in Attachment 1, and the ordering information for WinCC V6.0 is available in Entry ID 15195529.

Further information:

  • You can find notes about migration to WinCC V6.2 in the WinCC information system under: "Initial Information > Migration".
  • You can find notes about migration to WinCC V7.x in the WinCC information system under: "Getting Started > Migration".
  • WinCC manuals are available at:  https://support.automation.siemens.com/WW/view/de/10805584/133300

Keywords:
Upgrade, Update

How can you regularly receive updates to the latest versions of WinCC?Go to beginning
Part number:

Description:
WinCC offers a Software Update Service (SUS) as component of its Comprehensive Support package.
The complete package includes the latest updates/upgrades for WinCC including options.
To start with, the WinCC user receives a contract and replacement deliveries are made automatically over a period of 12 months. The contract is extended automatically by one year unless canceled 12 weeks before expiry.
WinCC Comprehensive Support must be procured per WinCC system (single-user, server, client). Prerequisite is possession of the current version of the software. Packages with 3 and 10 licenses are available in addition to the single-license package, which provide corresponding discounts for the cost-effective installation of WinCC Comprehensive Support for multiple systems.
 
Software product Order number
WinCC Comprehensive Support
1 license
6AV6 381-1AA00-0AX5
WinCC Comprehensive Support
3 licenses
6AV6 381-1AA00-0BX5 .
WinCC Comprehensive Support
10 licenses
6AV6 381-1AA00-0CX5

More information on updates for WinCC is available via the following Link.

Which settings do you have to make to set up a redundant single-user station in Microsoft Windows XP SP2?Go to beginning
Part number:

Configuration Notes:
If you wish to implement redundant single-station projects from WinCC V6.0 SP3  onwards up to and including WinCC V6.0 SP4 in Windows XP SP2, you must make the following DCOM settings because of the changes in the operating system. From WinCC V6.2 onwards the DCOM settings are made by default at the end of the installation of WinCC in the dialog "SIMATIC Security Control".
 
No. Procedure
1 Select the menu command "Start > Run...". Enter "dcomcnfg"  in the input field. Press <ENTER>.
2 In the tree structure you select "Component Services > Computer > Workstation".
3 In the pop-up menu you select "Properties" > "COM Security" tab.
4 In the "Access permissions" field you click on the "Edit limits..." button.
5 For the user group "ANONYMOUS LOGON" you activate the option "Permit" for the following permissions:
  • "Local access"
  • "Remote access"
6 Click the "OK" button. The access permissions are configured.
7 Click the "OK" button.

Note:
If the "ANONYMOUS LOGON" group is not available, then add it to the list via the "Add..." button (enter "ANONYMOUS LOGON" and use "Check name").
More information on the DCOM settings is available under "Start > SIMATIC > SIMATIC NET > Commissioning PC stations" or in Entry ID 13542666.  Once you have made all the necessary settings, restart the PC station in order to make the settings effective.

Keywords:
Redundancy, Security settings

How can you analyze errors when installing WinCC?Go to beginning
Part number:

Instructions:
Upon installation of WinCC different log files are created in the Windows directory, e.g. "C:\WINDOWS\". If installation problems occur, you can go through these log files to find error entries and thus determine a possible cause of the problem. Below is a list of some of the log files with path specifications.

Files up to and including WinCC V7.0:
 
citamis.str C:\WINDOWS
HMI_*.log 1) C:\WINDOWS
HMI_*.TXT 2) C:\WINDOWS
RASetup*.LOG C:\
WinCCInstallation.log C:\WINDOWS
sqlsp.log  
sqlstp.log  
1) For example: HMI_CCInit_Master.log, HMI_WebNavigatorServer.log, HMI_WinCCSmartTools.log, HMI_RemotePublisher.log
2) For example: HMI_SC_ACE_LOG.TXT, HMI_SQLServerData.txt, HMI_SSC_ComArch_LOG.TXT

Files as from WinCC V7.0 SP1: 

XP / 2003
 
citamis.str C:\WINDOWS
HMI_SQLStarter.txt C:\Documents and Settings\All Users\Application Data\Siemens\Automation\Logfiles\Setup
RASetup*.LOG C:\
WinCC_Configuration_Log.txt C:\WINDOWS
WinCC_Runtime_Log.txt C:\WINDOWS

Vista:
 
citamis.str C:\ProgramData\Siemens\Automation\Logfiles\Setup
HMI_SQLStarter.txt C:\ProgramData\Siemens\Automation\Logfiles\Setup
RASetup*.LOG C:\ProgramData\Siemens\Automation\Logfiles\Setup
WinCC_Configuration_Log.txt C:\ProgramData\Siemens\Automation\Logfiles\Setup
WinCC_Runtime_Log.txt C:\ProgramData\Siemens\Automation\Logfiles\Setup

Note:
You can quickly find the error entries by using specific full-text searches, e.g. a search for the character string "ERROR". Taking the time stamp, you can compare the entries with any entries in the Windows event display and thus establish further connections.

Why is the Setup of SIMATIC WinCC aborted at the ACE component (Active Communication Environment)?Go to beginning
Part number:

Description:
During Setup of SIMATIC WinCC you receive the following message:


Fig. 01

The cause of this error message is the "path variable" of the Microsoft Windows operating system. The access paths for the programs installed are entered in this tag. This variable is limited by the operating system to 1024 characters. All the programs enter your access paths here upon installation, so there might be multiple entries of the access paths. Since when you uninstall programs, these path entries are not deleted, there might still be entries present that you no longer need.

Notes:

  • The error message above is displayed in Windows XP. In Windows 2000 and Server 2003 the following error message is displayed: "String variable not large enough. Check the string declaration. Error 401".
  • Refer also to the entries in the diagnostics files on installing WinCC in Entry ID 23069304.

Check and clear these entries according to the procedure given below.
 
No. Procedure
1 Under "Start > Settings > Control Panel > System > Advanced > Environment Variables" you open the relevant pop-up menu (Fig. 02).


Fig. 02

Find the "Path" variable under "System variables". Double-click that variable. Copy the entry under "Value" and save this entry in a text file. Copy this text file. Open this copy.

2 Check for duplicate entries and entries that are no longer needed (from uninstall programs) and remove them as necessary. Then sort the order of the entries. Set all the entries that start with "%systemroot%"; the other entries should follow.

Note:
You can also sort the remaining entries according to the frequency of the programs used. The system uses this path variable when searching for programs. The entries of this variable are processed sequentially. The relevant order optimizes your system. Back up the cleared file.
3 Copy the cleared entry into the "Values" field (see above).
4 Check whether there is also a "Path" variable under "User variables". If so, proceed in the same way as with the "Path" variable under "System variables" (as described above).
5 Close all the windows with "OK" and restart your computer.

Run the WinCC Setup again.

Keywords:
Abortion, Install, Installation, Error message

How should you proceed if installation of the Microsoft SQL server fails?Go to beginning
Part number:

Instructions:
Make sure that you proceed according to the installation instructions and the notes in the "Readme" file. Make sure in particular that:

  • You are logged in locally.
  • Have administrator rights.
  • The Windows firewall and virus scanner are disabled.
  • The target folder for installation isn't compressed.

The following instructions do not claim to be able to clear all possible installation problems in any event. The instructions can help to provide a solution to installation problems in many cases.
 
No. Procedure
1 Repeat installation of the SQL server
A possible cause for abortion of the SQL server installation might be that certain files (DLL) should be replaced. This might mean that you have to restart the computer. This is why you should first try to repeat the installation. If this aborts, leave the SQL server CD in the drive and restart your computer. Once the computer has been restarted, the installation should be continued.

If installation problems continue to occur, proceed with the next step.
2 Analyze log files
It is advisable to devaluate the log files or error entries created during installation. The following files are created in the Windows directory:
  • sqlsp.log (error entries include the character string "failed")
  • sqlstp.log (error entries include the character string "failed")
  • HMI_SQLServerData.txt (error entries include the character string "error")
3 Update Microsoft Data Access Components (MDAC)
Often the problem occurs with unsuccessful installation of the ODBC components that are part of the Microsoft Data Access Components (MDAC).
Install the latest MDAC information on this that is available in Entry ID 19354858.
4 Uninstall SQL server
If available, uninstall the SQL server via "Settings > Control Panel > Software".
After successful uninstallation, you call the registration editor with "Run > regedit". Then delete the following codes if there:
  • Under "HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\Windows\CurrentVersion\Uninstall" the entry "SQL Server2000 (WINCC)"
     (this removes the entry in the Control Panel)
  • Under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft" the folder "MSSQLServer"
  • Under "HKEY_LOCAL_MACHINE\Software \Microsoft" the folder "Microsoft SQL Server"
  • Under "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Uninstall" the folder "Microsoft SQL Server 2000 (WinCC)"

Important:
As a general rule, no warranty can be provided for direct changes made to the Registry, because this is the sole responsibility of the user. In any event, you are advised to make a backup of the registry before undertaking the actions described here.

5 Restart the computer
Restart the computer.

Note:
In some cases it might be necessary to boot the system from the Windows CD and then run the "Repair Windows" option.

6 Install the SQL server and Service Pack separately
Execute the SQL server setup and then the setup of the associated service pack. These are on the SQL server CD under:
  • "<CD_SQLSERVER>SQL2000\Products\MSSQLServer2000"
  • "<CD_SQLSERVER>SQL2000\Products\MSSQLServer2000_SPx"
7 Reinstall the SQL server
Execute the "normal" WinCC installation of the SQL server once again, for example by calling the Autorun program from the SQL server CD supplied. This is always absolutely necessary if the original MS Setups have been executed, so that WinCC-specific settings are entered in the SQL server.

If the Setup aborts again, then acknowledge the error message and restart the computer.  For this you leave the SQL server CD in the drive.
After restart, Setup should be continued.

Note:
Refer to the following entry in the Microsoft Support pages if you get an error message when installing the SQL Server 2005/2008 in the operating system WinXP SP3.
http://support.microsoft.com/kb/958897

Missing SQLUNIRL.dll when Installing SIMATIC WinCC V6Go to beginning
Part number:

QUESTION:  
If I install Microsoft SQL Server prior to installing SIMATIC WinCC V6, the following message appears: 

"CNFGSVR.EXE - DLL not found
The dynamic link library SQLUNIRL.dll was not found in the stated path C:\WINNT\system32."

How can I avoid this?

ANSWER:  
In this case the installation of Microsoft Data Access (MDAC) is no longer functionable. Repair this damage of Microsoft Data Access as follows:

  • when using WinCC V6.0 SP1
    Start file mdac_typ.exe from directory "WinCC\Setup\Products\MS_mdac\" of CD WinCC V6.0 SP1.
     
  • when using WinCC V6.0 SP2
    Start file mdac_typ.exe from directory "Tools\MS_mdac\" of CD Microsoft Tools.
     
  • Restart setup of des Microsoft SQL Server.

Note:
If you are using the operating system Windows 2003 Server, you require a more recent version of file mdac_typ.exe. The file you can download in the internet from the following URL:

http://www.microsoft.com/downloads/details.aspx?displaylang=de&FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c (German)

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c (English)

Key Words:  
DataAccess, Error Message


Why does the SQL server 2000 SP3 not appear as present during the installation of WinCC V6.0 SP3, even though it is installed?Go to beginning
Part number:

Description:
SQL Server 2000 SP3 has to be installed in order to install WinCC V6.0 SP3.
The SQL server installation is supplied in WinCC.

There are two different SQL server CDs for WinCC V6.0 and WinCC V6.0 SP3. The CD for WinCC V6.0 is marked "Siemens AG, Copyright 2003" and the CD for WinCC V6.0 SP3 is marked "Siemens AG, Copyright 2004".

In order to install WinCC V6.0 SP3, ensure that you use the SQL server CD marked "Siemens AG, Copyright 2004".


 Entry ID:22127699   Date:2014-04-14 
I regard this article....as helpfulas not helpful                                 






























mySupport
My Documentation Manager 
Newsletter 
CAx-Download-Manager 
Support Request
To this entry
Print
Create PDF 
Send to a friend
QuickLinks
Compatibility tool 
Help
Online Help
Guided Tour