Bryvo01,  The count of "^T " matches can be way higher when the remote repository accessors is used. This exception is not pointed out in the KB explicitly. The "^C " matches gives the number of instances in the repository. The "^T " also gives the number of instances when remote repository accessor is not used. But when the remote repository accessor is used for instances there will be two entries starting with "^T " (one to capture the accessory information and the other to capture the instance attribute information). The "^T " entry is followed by the actual instance name. I took the unique instance specific"^T " entries count, for both the repository provided, and it is (almost) matching the "^C " count. So, both repositories are proper.  Kind Regards, Sean
I read KB 000447456 (easy way to check this in Windows FWIW:  findstr /B /C:" " <.rps file> | find /v "" /c) and ran a check on all of my domains.  ALMOST everything checked out fine; ACM and ESM had numbers for 'T ' that were waaaaaaay off.   The problem is that both ACM and ESM get their topology from other domains.  I can easily rename the existing .rps and let ACM and ESM build a new one, but it comes out the exact same.  Is KB 000447456 not a good check for ACM and ESM?  Do I need to rebuild AM and PM topologies and fix ACM and ESM?  Or is there something totally different that I just missed?
corrupt SMARTS repositories