Directory Programming .NET

We are getting some 'index out of range' errors on clients trying to login through ADFS (it was working fine previously). I am not sure if it is happening always or only sometimes, but they sent be a very verbose log and I constantly see a pattern of:

2009-04-21T22:54:01 [INFO] UpdateTrustPolicyCallback: The loaded trust policy is old. Ignore.

Do I need a new trust policy? How/Why do I make a new one?

That's all pretty weird.  I'd suggest looking at the trust policy file and the .bak file and ensure that the backup has a version number 1 lower than the current version.  Sometimes if manual edits are made, this can be a problem.  You may need to get Microsoft's help on this too.

If I were going to spend time trying to diagnose this problem, I'd likely try to find out where the string is getting logged by using Reflector and then I'd zoom in on the logic to try to understand what's wrong.

It would also be helpful to know if that's an FS or agent log.  Looks like an FS but I wanted to be sure.

Hi ,
 I too had faced a similiar problem, we have a virtualised infrastructure. After we tested MOSS 2007 on win 2008, we took a snapshot and rolled it back. After the roll back, the new group claims that were added were not visible ( i did look in the logs on both ADFS server and web agent on MOSS)

I'm not sure what the problem is here. If you update the version on the trust policy manually, does the problem go away?