show the entry list
ES - SIMATIC Manager -- Product information -- Checking compatibility
Compatibility Tool for Automation and Drive Technology
What are the basic requirements for data exchange between COMOS and SIMATIC PCS 7?
Why should you not install the Microsoft security patches KB2467174, KB2467175, KB2465361 and KB2465367 in WinCC, PCS 7 and WinCC Professional V11?
How can you find out which Microsoft Patches are installed on the PC?
Why can different versions of PCS 7 not be operated in mixed mode?
Which modules and their firmware versions are released for PCS 7 and how can you upgrade them?
With what are SIMATIC PCS 7 V8.x, V7.x, V 6.x, V5.x and V4.x compatible?
Why can't you use Service Packs for Microsoft Windows, the MS SQL Server or the Internet Explorer if they do not originate from the CDs/DVD provided with the PCS 7 software?
What support does Microsoft provide for Microsoft products (operating systems and Internet Explorer) implemented with PCS 7?
Which Microsoft Patches ("Security Patches" and "Critical Patches") have been tested for compatibility with SIMATIC PCS 7?
Important note on Microsoft Patches KB 943459 and KB 971468
Important note when using Microsoft's automatic update service in PCS 7.
Additional information on the compatibility of PCS 7 V6.x and Microsoft products
WinCC -- Product information -- Checking compatibility
Compatibility Tool for Automation and Drive Technology
Important note on Microsoft Patches KB 943459 and KB 971468
Which licenses do you need to upgrade from WinCC flexible 2008 or WinCC V7 to WinCC V11 and in WinCC V11?
Why should you not install the Microsoft security patches KB2467174, KB2467175, KB2465361 and KB2465367 in WinCC, PCS 7 and WinCC Professional V11?
With what are SIMATIC WinCC V7.x, V 6.x and V5.x compatible?
Which Microsoft Patches ("Security Patches" and "Critical Patches") have been tested for compatibility with SIMATIC WinCC?
How can you find out which Microsoft Patches are installed on the PC?
Further information on the Catalog ST80 with regard to WinCC Communication
Which operating system and software do you require for the SIMATIC WinCC Web Navigator V1.x, V6.x and V7.x?
With which Microsoft Windows operating systems is SIMATIC WinCC/ProAgent compatible?
Which security patch do you need for installing SIMATIC WinCC V6.0?
Drivers on the SIMATIC NET CD 07/2001 and WinCC
Notes on using WinCC V5.1 with "SIMATIC NET 7/2001 SP4"
Microsoft Windows language versions released for SIMATIC WinCC V5.1
Important note on Microsoft Patches KB 943459 and KB 971468
Part number:

Description
When using Microsoft operating system Windows Server 2003 SP1 or SP2, there can be rare cases of blocking on the OS clients if two clients (one after another) access the same runtime screen (*.pdl). Operation of the OS client is disrupted (hour glass) during this blocking.
The error that leads to this behavior is in the Kerberos ticket handling of the Microsoft operating system Windows Server 2003.

KB 943459 has been updated by Microsoft for Windows Server 2003 SP2 with KB 971468 (also available via WSUS).

More detailed information about Microsoft Patches is available in the entries below.

  • "Which Microsoft Security Patches have been tested for compatibility with SIMATIC WinCC?" in Entry ID: 18752994
  • "Which Microsoft Security Patches have been tested for compatibility with SIMATIC PCS 7?" in Entry ID: 18490004

A correction is provided by Microsoft in KB 943459 and KB 971468 at the following links.

We therefore recommend that you install Microsoft Patch KB 943459 or KB971468 as soon as possible.

German Link
http://support.microsoft.com/kb/943459/de

http://support.microsoft.com/kb/971468/de

English link
http://support.microsoft.com/kb/943459/en-us

http://support.microsoft.com/kb/971468/en-us

Installation notes
You have to restart the computer after installing this hotfix.
Close all SIMATIC applications beforehand.

Note
Patch KB 943459 modifies the following code in the Registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters OplockBreakWait. Do not change the default time of 35 seconds set in the parameter OplockBreakWait. 

 Entry ID:30827420   Date:2012-05-25 
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