Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 494
  • Last Modified:

Event ID 1030 & 1058

Added a new DC (remus) to existing domain; orginal DC (argus) is SBS.
Event logs are now quiet with the exception of these two event errors:
--------
1030 windows cannot query for the list of group policy objects
1058 windows cannot access the file gpt.ini for GPO . . .
---------
NetDiag on argus (SBS) shows the follow two issues:
  [FATAL] cannot open an LDAP session
  [Warning] Failed to query SPN registration on DC
NetDiag on remus (new DC) shows:
  [Warning] The DNS entries for this DC are not registered correctly on DNS server "argus"
                   please wait 30 min  'has been showing this for hours

I haven't heard of any user trouble and all systems appear to be functioning properly.  But the event errors on argus are added about every 5 minutes or when i run cmd: gpupdate
I'm stymied on this one.
0
ShawnGray
Asked:
ShawnGray
  • 2
1 Solution
 
Kini pradeepIT Technology Senior ConsultantCommented:
http://support.microsoft.com/kb/259398/

apart from this has the AD replicated ? also can you check the sysvol/domain /policy folder and check whether the policies have replicated. also run net share & check whether the sysvol and netlogon are shared. you could also stop & start the FRS service & check whether the same events are logged ?
0
 
ShawnGrayAuthor Commented:
kprad,

From article, a couple of reg entries were made to the new DC.
AD replication-yes
Sysvol replication-yes
Net share, shared-yes
FRS restarted
after restart'g FRS i get this:
-------
The File Replication Service is having trouble enabling replication from ARGUS  to REMUS for c:\windows\sysvol\domain using the DNS name argus.domain2.local. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 
 [1] FRS can not correctly resolve the DNS name argus.domain2.local from this computer.
 [2] FRS is not running on argus.domain2.local. {Check: This is running}
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
-----------------------
I thought the original event errors were solved but they popped up about 45 minutes later.
0
 
ShawnGrayAuthor Commented:
Ran: "DFSUtil /purgemupcache "
This stopped the error logs until the system restarted.
A "fix" nonetheless.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now