[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

DCDiag Error 457

Hi

I have 5 DC and when I execute the dcdiag, return this error:
      Starting test: systemlog
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 11/06/2008   13:28:13
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 11/06/2008   13:28:13
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 11/06/2008   13:28:14
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 11/06/2008   13:28:14
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 11/06/2008   13:28:15
            (Event String could not be retrieved)
         An Error Event occured.  EventID: 0x00000457
            Time Generated: 11/06/2008   13:28:15
            (Event String could not be retrieved)
         ......................... RTM-CORREO failed test systemlog
      Starting test: VerifyReferences
0
agustipons
Asked:
agustipons
  • 4
  • 3
  • 3
1 Solution
 
Hedley PhillipsCommented:
0
 
sliiconmanCommented:
When I have seen this it is printers. Like the link above states it just reads the event logs. Remove your printers, save the system log file off and rerun. If the errors do not come back add 1 printer at a time until they do unless of course the driver is listed in the system log like the above link posts. If the error in the system log is somthing other than printers please post it here for us.
0
 
agustiponsAuthor Commented:
I have remote printers, but i need for printing
0
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.

 
agustiponsAuthor Commented:
On of the DC, has installed no printer, and the error when execute dcdiag is the same

0
 
sliiconmanCommented:
Are you logging on via RDP? Printers may try to load. Can you shoot us the errors in the event log?

Problem may be with the printer, even if you need it, that may be what we need to fix.  Send us the event log errors and we will know more.
0
 
agustiponsAuthor Commented:
I am logging on via  Terminal Server, I have Ip printers and remote printers, if it was necessary i can unistall all the printers, but: only the remote or the Ip printers or the local printers?
But later?, i need this printers fopr my users

The obly error Ican see is with the dcdiag (457)..
0
 
sliiconmanCommented:
There are no errors in the event log that you can copy and past? Gives source etc.
 
OK so if printers are hard to troubleshoot now use replmon to check for replication problems.

check the logs for last succesful replication. See if you get any warnings about latency and tombstone lifetimes.
0
 
Hedley PhillipsCommented:
As sliiconman said and my original link, we need to see the System log errors please. Set up a filter and export it.
0
 
agustiponsAuthor Commented:
Hello

I an see the problem is withs the drivers of the printers.

When i logon on with my computer (vista) to the DC (win2k3), in the event viewer (system), i can see various errors. I deleted in my pc, all the old printers , now in my computer have only one printer, and in every DC,  i have on error in the event viewer (111). source =TermServDevices

The printer is an IP printer (HP 4700), but the system says that no have a driver, but it isn't true, i can print!!!!!

I reinstall the drivers?

0
 
Hedley PhillipsCommented:
"This warning occurs because, by default, the Remote Desktop client will try to share your local printers, to enable printing to a local printer from the remote computer. The warning is completely harmless, present only to make you aware of the fact that you've attempted to share a printer that the remote computer doesn't have a driver for, and therefore won't be able to print to."

To disable this when you're connecting to your home server:

    * Start the Remote Desktop client on your PC, but don't log in to your server.
    * Click the Options>> button.
    * Click the Local Resources tab.
    * Remove the check mark next to Printers.

You can now log on to your server without that completely harmless warning message. If you want to have that option off by default, save a connection profile for your server with it off.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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