TPM Error ID 13 and 516 occuring after some time

Question

Hi all,
on my TP X301 a TPM error occurs always after some up-time. I get error IDs 13 and 516 in the Windows Error Protokolls. This is leading to an unusuable  Client Security Password Manager. Client Security then tells me that the communication with the TPM-chip is blocked...
The Windows online Help for these IDs suggest me to replace the TPM hardware. I do not believe it is a hardware problem since fingerprint reader is working fine....?
Anybody got a suggestion on this?
I got vista x64 running.
The error information in German is:
TPM Error ID 13: "Beim Gerätetreiber für das Trusted Platform Module (TPM) ist ein nicht behebbarer Fehler in der TPM-Hardware aufgetreten, der die Verwendung der TPM-Dienste (z. B. Datenverschlüsselung) verhindert. Wenden Sie sich an den Computerhersteller, um weitere Hilfe zu erhalten."
TBS Error ID 516: "Fehler bei der Kommunikation mit dem TPM. Vom Treiber wurde 0x8007045d zurückgegeben."
ThanX a lot in advance.
St.

Answer 1

Here is an explanation of the failure:
1. Prioritized replication was introduced with DS6.0;
2. When a suffix at a DS6 instance is initialized from a DS5 instance, and then an operation is performed at the DS6 instance that uses prioritized replication, replication fails;
3. By default, password policy uses prioritized replication to propagate auth-failure-lockout state updates (e.g., adding a pwdFailureTime attribute value on a failed bind attempt);
A work-around:
Disable DS6 supplying auth-failure lockout state using prioritized replication. In any password policy having auth-failure-lockout enabled, set
pwdIsLockoutPrioritized:FALSE
Note that DS6 enables prioritized lockout by default, in particular, it enables this feature when migrating a password policy received from a DS5 instance. Hence, for this workaround to be effective, the prioritized lockout feature must be disabled in any DS6 password policy that has auth-failure lockout enabled, which could include:
1. The default password policy at any DS6 instance (cn=password policy,cn=config);
2. Any password policy originating at a DS5 instance, including those in data imported into a DS6 instance, received via replication total update initialization, or added at the DS5 instance subsequent to the DS6 instance initialization;
3. Any password policy added to a DS6 instance.
Additionally, do not set any prioritized replication rules for other attributes.
It is possible the bug can still be triggered in the case of a DS6-only topology that was initialized from DS5 data.
Contact Sun support for the status of a fix for the bug. The CR is 6645742.