MSExchange ADAccess Error code=8007077f
Hi,
Anyone know what is causing this? I read some articles and nothing will fix it...
Thanks,
Scott
Log Name: Application
Source: MSExchange ADAccess
Date: 4/12/2012 4:44:58 PM
Event ID: 2604
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: EX10.LewisGroup.Corp
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1652). When updating security for a remote procedure call (RPC) access for the Microsoft Exchange Active Directory Topology service, Exchange could not retrieve the security descriptor for Exchange server object EX10 - Error
code=8007077f.
The Microsoft Exchange Active Directory Topology service will continue starting with limited permissions.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange ADAccess" />
<EventID Qualifiers="49156">2604</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-04-12T20:44:58.000000000Z" />
<EventRecordID>80348</EventRecordID>
<Channel>Application</Channel>
<Computer>EX10.LewisGroup.Corp</Computer>
<Security />
</System>
<EventData>
<Data>MSEXCHANGEADTOPOLOGY</Data>
<Data>1652</Data>
<Data>EX10</Data>
<Data>8007077f</Data>
</EventData>
</Event>Thank You, Scott
April 12th, 2012 4:56pm
Scott,
did you happen to see below?
http://support.microsoft.com/kb/2025528
let me know,
Sandeep
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2012 5:05pm
Site name or domain name? I did see this but was unsure... I have built three networks with Exchange 2010 server and this is the only one with this problem. If SiteName where do I find this in Exchange 2010?
Found it wit ADSI edit.
Right-click SiteName, click Modify, type the name of the
Active Directory Site that the Exchange server belongs to in the
Value data box, and then click OK.
Is the Active Directory Site the FQDN of my internal domain? If not where do I find it?
Thank You, Scott
April 12th, 2012 5:32pm
Hi
Do you have anything update on your issue?
Site name is FQDN of AD which your exchange server belongs to. You can find them on your logon interface. (like dag.com, test.com)
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
tngfb@microsoft.comTerence Yu
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
April 12th, 2012 10:37pm
Hi
Do you have anything update ?Terence Yu
TechNet Community Support
April 16th, 2012 2:30am
Problem not resolved.
Log Name: Application
Source: MSExchange ADAccess
Date: 4/16/2012 8:41:56 AM
Event ID: 2501
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: EX10.LewisGroup.Corp
Description:
Process MSEXCHANGEADTOPOLOGY (PID=1676). The site monitor API was unable to verify the site name for this Exchange computer - Call=DsctxGetContext Error code=8007077f. Make sure that Exchange server is correctly registered on the DNS server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchange ADAccess" />
<EventID Qualifiers="49156">2501</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-04-16T12:41:56.000000000Z" />
<EventRecordID>83768</EventRecordID>
<Channel>Application</Channel>
<Computer>EX10.LewisGroup.Corp</Computer>
<Security />
</System>
<EventData>
<Data>MSEXCHANGEADTOPOLOGY</Data>
<Data>1676</Data>
<Data>DsctxGetContext</Data>
<Data>8007077f</Data>
</EventData>
</Event>Thank You, Scott
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2012 8:44am
You'll need to open Active Directory Sites and Services admin tool and verify that your Exchange Server having this issue is belonging to the correct subnet matched to the correct AD Site. Also, did you receive the correct AD Site name while running NLTEST
/DCGetSite?Jesper Bernle | Microsoft Community Contributor 2011 Awardee
April 16th, 2012 8:55am
Under sites\subnets there are none listed.
C:\Users\Administrator.LEWISGROUP>NLTEST /DSGETSITE
Default-First-Site-Name
The command completed successfully
Can the site name be changed to something more meaningful like LewisGroup?Thank You, Scott
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2012 9:20am
Following this artical stopped mail flow. I had to remove the reg key and reboot.
My AD Site Name is LewisGroup.Corp. My FQDN for exchange 2010 server is EX10.LewisGroup.Corp.
WORKAROUND
To work around this issue, hardcode the Active Directory Site name in the registry. To do this, follow these steps:
Click Start, click Run, type Regedit, and then press
OK.Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
On the Edit menu, click New, and then click
String Value.Type SiteName, and then press Enter.Right-click SiteName, click Modify, type the name of the Active Directory Site that the Exchange server belongs to in the
Value data box, and then click OK. Exit Registry Editor, and then restart the computer to apply the change.
When you hardcode the Active Directory Site name, Windows will return the hardcoded site name in response to the query from Exchange. This behavior enables Exchange server to bypass any site name lookup failures.
My DynamicSiteName is Default-First-Site-Name
Thank You, Scott
April 16th, 2012 12:03pm
Hi
DynamicSiteNameStores the dynamically-determined site name for the domain in which this member server or workstation is located. The
value of this entry is determined by the Net Logon service, not by an administrator or user.
The value of the
SiteName entry always takes precedence over the value of this entry. If
SiteName appears in the registry, this value is not used.
You can set LewisGroup.Corp as site name and post your result.
Terence Yu
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2012 9:56pm
If Lewisgroup.corp is the site name then what is the active directory site the Exchange server belongs too?
Right-click SiteName, click Modify, type the name of the Active Directory Site that the Exchange server belongs to in the
Value data box, and then click OK.
Thank You, Scott
April 16th, 2012 10:26pm
Hi
I am confused by your saying. Maybe I misunderstand your saying.
Can you post your AD FQDN, exchange FQDN,GC FQDN? Terence Yu
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2012 10:52pm
I am not sure what to create in the registry key. What I created yesterday stopped all mail flow... I clearly put in the wrong information.
Right-click "SiteName", click Modify, type the name of the "Active Directory Site" that the Exchange server belongs to in the
Value data box, and then click OK.
SiteName=?
Active Directory Site=?Thank You, Scott
April 17th, 2012 7:20am
It seems you only have one AD Site (Default-First-Site-Name) right?
You stated earlier: "I have built three networks with Exchange 2010 server and this is the only one with this problem" I'm guessing your 3 networks are in the same physical location. If not then you should consider creating one AD Site for each location depending
on the connectivity. If they are all on the same high speed campus network then one AD site might suit you just fine.
Can you elaborate a bit around your Network and AD topology?
Normally one shouldn't have to do manual registry tweaks so I think we need to stop editing the registry and go back a step or two and think about what we actually are doing.Jesper Bernle | Microsoft Community Contributor 2011 Awardee
Free Windows Admin Tool Kit Click here and download it now
April 17th, 2012 7:49am
Hi
I should gather information in the post.
1. Your FQDN for exchange 2010 server is EX10.LewisGroup.Corp
2. You find 2604 and 2501 error in event viewer.
3. You have built three networks with Exchange 2010 server and this is the only one with this problem.
(In fact, I dont know your network setting. Are exchange 2010 and AD server in same subnet?)
4. You modify SiteName as LewisGroup.Corp and reboot server.
Does exchange server stop mail flow?
According to your information, I explain my thoughts.
1,2,4
When Exchange 2010 installed on Windows Server 2008 R2. During a restart of the server, the operating system queries Active Directory to get its AD Site information. On a Windows 2008 R2 server, this will sometimes fail. As the Exchange
services are starting, it also will do a query for its AD Site and that too will fail. Windows will continue to try and determine its AD Site name and will eventually succeed. However, Exchange does not re-try the query and the above errors are logged in the
application log every 15 minutes.
So workaround is to hardcode AD site name. According to your mail server FQDN(EX10.LewisGroup.Corp), I think your AD site is LewisGroup.Corp. I also do test on my lab server. It wont affect your mail flow.
3. You have built three networks with Exchange 2010 server and this is the only one with this problem.
Can you post your subnet setting and router setting?
Terence Yu
TechNet Community Support
April 17th, 2012 10:28pm
I call Microsoft last night. The correct answer to my issue was as follows:
WORKAROUND
To work around this issue, hardcode the Active Directory Site name in the registry. To do this, follow these steps:
Click Start, click Run, type Regedit, and then press
OK.Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
On the Edit menu, click New, and then click
String Value.Type SiteName, and then press Enter.Right-click SiteName, click Modify, type the name of the Active Directory Site that the Exchange server belongs to in the
Value data box, and then click OK. Exit Registry Editor, and then restart the computer to apply the change.
When you hardcode the Active Directory Site name, Windows will return the hardcoded site name in response to the query from Exchange. This behavior enables Exchange server to bypass any site name lookup failures.
SiteName=SiteName
Active Directory Site Name=Default-First-Site-Name
After adding this String Value and rebooting the event log errors stopped.
Thanks to everyone for the help.
Thank You, Scott
Free Windows Admin Tool Kit Click here and download it now
April 18th, 2012 7:20am