EXBPA 2.6 says it cannot determine PDC FSMO and RID FSMO   

But when I check Operations Master in AD, Domains and Trusts, etc.  they are 
all correct showing DC2 as the master.  DC2 is not showing any errors.

This showed up right after I upgraded to 2.6

date: Mon, 5 Jun 2006 10:29:06 -0700   author:   Anthony

Re: EXBPA 2.6 says it cannot determine PDC FSMO and RID FSMO   

Hi Anthony,

If you look at the "Run-time Log" in ExBPA (Other Reports section), does it 
show any access denied errors for directory objects? If not, feel free to 
zip and send me the output XML file and I'll investigate this for you. 
pbowden @ microsoft . com

Cheers,
-- 
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/analyzers

This posting is provided "AS IS" with no warranties, and confers no rights.

"Anthony"  wrote in message 
news:F5F864A2-3E92-4EA5-971C-6084C4236F44@microsoft.com...
> But when I check Operations Master in AD, Domains and Trusts, etc.  they 
> are
> all correct showing DC2 as the master.  DC2 is not showing any errors.
>
> This showed up right after I upgraded to 2.6

date: Mon, 5 Jun 2006 13:37:25 -0700   author:   Paul Bowden [MSFT]

RE: EXBPA 2.6 says it cannot determine PDC FSMO and RID FSMO   

Hi,

Did you get this fixed?
I am seeing exactly the same errors on our server.
In the run time log I have the following messages relating to these roles.
"09:50:20.431: Error (No mapping between account names and security IDs was 
done) attempting to search for object LDAP://GPLPATTY412/DC=gpl,DC=local--, 
skipping object."
"09:50:20.431: Error (No mapping between account names and security IDs was 
done) attempting to search for object LDAP://GPLPATTY412/cn=RID 
Manager$,cn=System,DC=gpl,DC=local--, skipping object."
"09:50:20.431: Error (No mapping between account names and security IDs was 
done) attempting to search for object 
LDAP://GPLPATTY412/cn=Infrastructure,DC=gpl,DC=local--, skipping object."

"Anthony" wrote:

> But when I check Operations Master in AD, Domains and Trusts, etc.  they are 
> all correct showing DC2 as the master.  DC2 is not showing any errors.
> 
> This showed up right after I upgraded to 2.6

date: Tue, 13 Jun 2006 02:19:02 -0700   author:   Duncan

Re: EXBPA 2.6 says it cannot determine PDC FSMO and RID FSMO   

This issue is still under investigation. Nothing actually changed on the 
ExBPA side, but it's strange that suddenly a few people have started seeing 
the same error (you're the third person to see this). I'm going to relocate 
the ExBPA rules so that we don't fire a false-positive, but it doesn't 
change the fact that a simple LDAP query at the domain level appears to be 
failing. Can I ask if anything changed in your environment recently? I'm 
just wondering if some other hotfix or update has broken our LDAP queries.

If you're proficient with the LDP.EXE tool, it would be interesting to 
enumerate the same container to see if it reports the same problem as ExBPA.

Cheers,
-- 
Paul Bowden
Program Manager
Exchange Server Best Practices Analyzer
http://www.microsoft.com/exchange/analyzers

This posting is provided "AS IS" with no warranties, and confers no rights.

"Duncan"  wrote in message 
news:DA01C5E6-512D-4228-984B-E56C0F919800@microsoft.com...
> Hi,
>
> Did you get this fixed?
> I am seeing exactly the same errors on our server.
> In the run time log I have the following messages relating to these roles.
> "09:50:20.431: Error (No mapping between account names and security IDs 
> was
> done) attempting to search for object 
> LDAP://GPLPATTY412/DC=gpl,DC=local--,
> skipping object."
> "09:50:20.431: Error (No mapping between account names and security IDs 
> was
> done) attempting to search for object LDAP://GPLPATTY412/cn=RID
> Manager$,cn=System,DC=gpl,DC=local--, skipping object."
> "09:50:20.431: Error (No mapping between account names and security IDs 
> was
> done) attempting to search for object
> LDAP://GPLPATTY412/cn=Infrastructure,DC=gpl,DC=local--, skipping object."
>
> "Anthony" wrote:
>
>> But when I check Operations Master in AD, Domains and Trusts, etc.  they 
>> are
>> all correct showing DC2 as the master.  DC2 is not showing any errors.
>>
>> This showed up right after I upgraded to 2.6
>

date: Tue, 13 Jun 2006 09:30:04 -0700   author:   Paul Bowden [MSFT]