3
Explorer.exe und Cscript hängen sich auf
Hallo,
ich hab folgendes Problem mit meinem Server,
vor einigen Wochen fing er an VBScripts nicht mehr auszuführen, wenn ich sie per Doppelklick starte (Open with Command Prompt), liefen aber einwandfrei, wenn ich sie mit "open" starte. Seit einigen Tagen fing dann Explorer.exe an unregelmässig einzufrieren, wenn ich Dateien oder Ordner ausgewählt oder gestartet habe, aber ein beenden via Task-Manager und manuell starten (Neuer Task: Explorer.exe) hat das für ein paar Stunden gehandhabt. Seit gestern hilft aber das auch nicht mehr, und die Scripts lassen sich entweder gar nicht mehr starten, oder wenn ich die "open" methode nehme, kann es sein, dass er mit einer Verzögerung von etwa 10 Minuten es doch ausführt, aber auch nur, wenn ich nichts mache.
Ich habe aus anderen Beiträgen erfahren, dass es IE-Fehler sowas verursachen könnte, aber der hat bisher noch nie ein Problem gemacht. Ich hab den IE 6 mit SP1.
Hier noch ein paar Daten zu meinem System.
Windows Server 2003 R2 mit SP1, läuft auf einem Dell PowerEdge 1800 mit einem Intel Xeon 2x 3GHz (falls das irgendwie hilft)
Server läuft als "File Server, Application Server, Domain Controller (Active Directory), DNS Server, DHCP Server".
Als Virenscanner und Real-Time Protector läuft Panda Antivirus.
Mein tatsächliches Problem ist, dass ich das System nicht neuinstallieren oder sonstwie großmächtig verändern darf, da ich das System erst vor kurzem übernommen habe, und die ganzen Einstellungen noch nicht weiss. Das einzige was ich habe sind die Win2003 Installations CDs.
Ich hoffe, dass jemand eine Idee dazu hat.
Danke schon einmal im Voraus.
ich hab folgendes Problem mit meinem Server,
vor einigen Wochen fing er an VBScripts nicht mehr auszuführen, wenn ich sie per Doppelklick starte (Open with Command Prompt), liefen aber einwandfrei, wenn ich sie mit "open" starte. Seit einigen Tagen fing dann Explorer.exe an unregelmässig einzufrieren, wenn ich Dateien oder Ordner ausgewählt oder gestartet habe, aber ein beenden via Task-Manager und manuell starten (Neuer Task: Explorer.exe) hat das für ein paar Stunden gehandhabt. Seit gestern hilft aber das auch nicht mehr, und die Scripts lassen sich entweder gar nicht mehr starten, oder wenn ich die "open" methode nehme, kann es sein, dass er mit einer Verzögerung von etwa 10 Minuten es doch ausführt, aber auch nur, wenn ich nichts mache.
Ich habe aus anderen Beiträgen erfahren, dass es IE-Fehler sowas verursachen könnte, aber der hat bisher noch nie ein Problem gemacht. Ich hab den IE 6 mit SP1.
Hier noch ein paar Daten zu meinem System.
Windows Server 2003 R2 mit SP1, läuft auf einem Dell PowerEdge 1800 mit einem Intel Xeon 2x 3GHz (falls das irgendwie hilft)
Server läuft als "File Server, Application Server, Domain Controller (Active Directory), DNS Server, DHCP Server".
Als Virenscanner und Real-Time Protector läuft Panda Antivirus.
Mein tatsächliches Problem ist, dass ich das System nicht neuinstallieren oder sonstwie großmächtig verändern darf, da ich das System erst vor kurzem übernommen habe, und die ganzen Einstellungen noch nicht weiss. Das einzige was ich habe sind die Win2003 Installations CDs.
Ich hoffe, dass jemand eine Idee dazu hat.
Danke schon einmal im Voraus.
Auf Facebook teilen
Auf Twitter teilen
Auf Reddit teilen
Auf Linkedin teilenBitte markiere auch die Kommentare, die zur Lösung des Beitrags beigetragen haben
Content-ID: 64873
Url: https://administrator.de/contentid/64873
Ausgedruckt am: 23.11.2024 um 08:11 Uhr
3 Kommentare
Neuester Kommentar
Hi!
lad dir mal den CCleaner herunter.
Hat schon wunder bewirkt.
Danach bzw. davor schaust du mal ins Ereignisprotokoll und schaust nach Fehlern und Problemen. (Start --> Ausführen --> compmgmt.msc)
Danach bitte noch mal hier melden...
Gruß
Markus
lad dir mal den CCleaner herunter.
Hat schon wunder bewirkt.
Danach bzw. davor schaust du mal ins Ereignisprotokoll und schaust nach Fehlern und Problemen. (Start --> Ausführen --> compmgmt.msc)
Danach bitte noch mal hier melden...
Gruß
Markus
Also nach dem der CCleaner sein Werk getan hatte, lief es etwas stabiler, aber ich muss manchmal immernoch 5-8 Minuten warten, bis er was macht.
Hier jetzt mal alle Warnungen und Fehlermeldungen derl letzten 2-3 Tage von unserem Hauptserver:
Error: The Template Persistent Cache initialization failed for Application Pool 'DefaultAppPool' because of the following error: Could not create a Disk Cache Sub-directory for the Application Pool. The data may have additional error codes..
SuperSocket info: (SpnRegister) : Error 8344.
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: %1
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: d:\nt\com\complus\dtc\dtc\adme\uiname.cpp:9280, Pid: 1820
No Callstack,
CmdLine: C:\WINDOWS\system32\msdtc.exe
The DSRestore Filter failed to connect to local SAM server. Error returned is <id:997>.
--
Das wiederholt sich immer wieder
--
Active Directory could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
Source domain controller:
BRLNSVR02
Failing DNS host name:
d4236802-452c-4d49-8c25-86bab29076d3._msdcs.brln.netz
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1:
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
User Action:
1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.
2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".
3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns
dcdiag /test:dns
4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:
dcdiag /test:dns
5) For further analysis of DNS error failures see KB 824449:
http://support.microsoft.com/?kbid=824449
Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type was found.
--
Das ist der einzige fehler, der kommt nur gelgentlich vor
--
The SQLSERVERAGENT service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Timeout (30000 milliseconds) waiting for the SQLSERVERAGENT service to connect.
The master browser has received a server announcement from the computer BRLNSVR02 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{151A94A3-FE78-49D6. The master browser is stopping or an election is being forced.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-00805F2CD064}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.
The server service was unable to map error code 998.
The Panda IManager Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Timeout (30000 milliseconds) waiting for the Panda IManager Service service to connect.
--
Selbes mit Panda AdminSecure Scheduler service, Panda AdminSecure Communications Agent service, The Panda Software Controller service, The OmniHTTPd Professional service, und nochmal der SQLSERVERAGENT service.
--
The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This is not a recommended security configuration. Credentials for Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the DHCP Administrative tool.
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-00805F2CD064}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.
The master browser has received a server announcement from the computer BRLNPC33 that believes that it is the master browser for the domain on transport NwlnkNb. The master browser is stopping or an election is being forced.
The master browser has received a server announcement from the computer BRLNSVR02 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{151A94A3-FE78-49D6. The master browser is stopping or an election is being forced.
--
Alle Meldungen bis hier (in "System") wiederholen sich recht oft.
--
The server could not bind to the transport \Device\NwlnkIpx.
The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was swolf and lookup type 0x0.
The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was swolf@BRLN and lookup type 0x20.
The DHCP service encountered the following error while cleaning up the database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
The DHCP service encountered the following error when backing up the database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
The following problem occurred with the Jet database -1032: Jet database read or write operations failed. If the computer or database has just been upgraded, then this message can be safely ignored. If this message appears frequently, either there is not enough disk space to complete the operation or the database or backup database may be corrupt. To correct this problem, either free additional space on your hard disk or restore the database. After you restore the database, ensure that conflict detection is enabled in DHCP server properties. For information about restoring the database, see Help and Support Center. Additional Debug Information: JetBackup.
The redirector failed to determine the connection type.
Printer Driver Dell Laser Printer 5210n for Windows NT x86 Version-3 was added or updated. Files:- DKAAT2DD.DLL, DKAAT2DA.DLL, DKAAT2P1.XML, DKAAT2DA.HLP, DKAAT2P1.RES, DKAAT2B1.DLL, DKAAT2BJ.DLL, DKAAT2BT.DLL, DKAAT2DA.ALL, DKAAT2DU.DLL, DKAAT2ED.DLL, DKAAT2LU.DLL, DKAAT2PI.EXE, DKAAT2TD.DLL, DKAAT2TE.DLL, DKAAT2DA.CHM, DKAAT2DL.DLL, DKAAT2F0.DFM, DKAAT2PU.DLL, DKAAT2SE.DLL, DKAAT2TF.DLL, DKAAT2TH.HLP, DKAAT2D$.INI, DKAAT2UZ.ZIP, DKAAT2DA.CNT, DKAAT2UI.DLL, DKAAT2UI.JS, gencoin.dll, softcoin.dll, DKAAT2TH.HLP, DKAAT2BJ.DLL, gencoin.dll, softcoin.dll.
No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Das sind die Meldungen des Hauptservers (BRLNSVR01), bei dem die Probleme sind.
Ich habe hier auch noch die Meldungen des "Hilfsservers" (BRLNSVR02):
"AVR Boost Active"
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2007-03-29 14:00:05
Invocation ID of source:
05fdf6c8-f6b8-05fd-0100-000000000000
Name of source:
c1019cdb-59c3-46c6-b4ad-7b121526796c._msdcs.brln.netz
Tombstone lifetime (days):
60
The replication operation has failed.
User Action:
Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:
1. Demote or reinstall the machine(s) that were disconnected.
2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner
The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was unsuccessful.
A full synchronization of the security accounts manager (SAM) database to domain controllers running Windows NT 4.0 and earlier might take place if the PDC emulator master role is transferred to the local domain controller before the next successful checkpoint.
The checkpoint process will be tried again in four hours.
Additional Data
Error value:
8614 The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
Duplicate event log entries were suppressed.
See the previous event log entry for details. An entry is considered a duplicate if the event code and all of its insertion parameters are identical. The time period for this run of duplicates is from the time of the previous event to the time of this event.
Event Code:
c00007fa
Number of duplicate entries:
15
--
Diese Meldungen, oder ähnliche von deerselben Quelle (NTDS Replication) wiederholen sich immer wieder.
--
Temperature sensor detected a warning value
Sensor location: BMC Ambient Temp
Chassis location: Main System Chassis
Previous state was: OK (Normal)
Temperature sensor value (in Degrees Celsius): 30.0
(um 6:00 morgens ^^)
--
kam ein paar mal vor (zwischen 6:00 und 10:00 morgens, bis ich kam und die klimaanlage wieder hochgedreht habe)
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
So, ich hoffe, damit kann man was anfangen.
Ich werde daraus nicht wirklich schlau... das einzige was ich verstehe ist, dass es anscheinend Probleme mit unserem Netzwerk gibt.
Hier jetzt mal alle Warnungen und Fehlermeldungen derl letzten 2-3 Tage von unserem Hauptserver:
Application:
Source: Active Server Pages
Type: Error
Error: The Template Persistent Cache initialization failed for Application Pool 'DefaultAppPool' because of the following error: Could not create a Disk Cache Sub-directory for the Application Pool. The data may have additional error codes..
Source: MSSQLSERVER
Type: Warning
SuperSocket info: (SpnRegister) : Error 8344.
Source: MSDTC
Type: Warning
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: %1
Source: MSDTC
Type: Warning
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: d:\nt\com\complus\dtc\dtc\adme\uiname.cpp:9280, Pid: 1820
No Callstack,
CmdLine: C:\WINDOWS\system32\msdtc.exe
Source: dsrestor
Type: Error
The DSRestore Filter failed to connect to local SAM server. Error returned is <id:997>.
--
Das wiederholt sich immer wieder
--
Directory Service:
Source: NTDS Replication
Type: Error
Active Directory could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources.
Source domain controller:
BRLNSVR02
Failing DNS host name:
d4236802-452c-4d49-8c25-86bab29076d3._msdcs.brln.netz
NOTE: By default, only up to 10 DNS failures are shown for any given 12 hour period, even if more than 10 failures occur. To log all individual failure events, set the following diagnostics registry value to 1:
Registry Path:
HKLM\System\CurrentControlSet\Services\NTDS\Diagnostics\22 DS RPC Client
User Action:
1) If the source domain controller is no longer functioning or its operating system has been reinstalled with a different computer name or NTDSDSA object GUID, remove the source domain controller's metadata with ntdsutil.exe, using the steps outlined in MSKB article 216498.
2) Confirm that the source domain controller is running Active directory and is accessible on the network by typing "net view \\<source DC name>" or "ping <source DC name>".
3) Verify that the source domain controller is using a valid DNS server for DNS services, and that the source domain controller's host record and CNAME record are correctly registered, using the DNS Enhanced version of DCDIAG.EXE available on http://www.microsoft.com/dns
dcdiag /test:dns
4) Verify that that this destination domain controller is using a valid DNS server for DNS services, by running the DNS Enhanced version of DCDIAG.EXE command on the console of the destination domain controller, as follows:
dcdiag /test:dns
5) For further analysis of DNS error failures see KB 824449:
http://support.microsoft.com/?kbid=824449
Additional Data
Error value:
11004 The requested name is valid, but no data of the requested type was found.
--
Das ist der einzige fehler, der kommt nur gelgentlich vor
--
System:
Source: Service Control Manager
Type: Error
The SQLSERVERAGENT service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Source: Service Control Manager
Type: Error
Timeout (30000 milliseconds) waiting for the SQLSERVERAGENT service to connect.
Source: MRxSmb
Type: Error
The master browser has received a server announcement from the computer BRLNSVR02 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{151A94A3-FE78-49D6. The master browser is stopping or an election is being forced.
Source: DCOM
Type: Error
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-00805F2CD064}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.
Source: Server
Type: Warning
The server service was unable to map error code 998.
Source: Service Control Manager
Type: Error
The Panda IManager Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Source: Service Control Manager
Type: Error
Timeout (30000 milliseconds) waiting for the Panda IManager Service service to connect.
--
Selbes mit Panda AdminSecure Scheduler service, Panda AdminSecure Communications Agent service, The Panda Software Controller service, The OmniHTTPd Professional service, und nochmal der SQLSERVERAGENT service.
--
Source: DhcpServer
Type: Warning
The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This is not a recommended security configuration. Credentials for Dynamic DNS registrations may be configured using the command line "netsh dhcp server set dnscredentials" or via the DHCP Administrative tool.
Source: W32Time
Type: Warning
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
Source: DCOM
Type: Error
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-00805F2CD064}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.
Source: MRxSmb
Type: Error
The master browser has received a server announcement from the computer BRLNPC33 that believes that it is the master browser for the domain on transport NwlnkNb. The master browser is stopping or an election is being forced.
Source: MRxSmb
Type: Error
The master browser has received a server announcement from the computer BRLNSVR02 that believes that it is the master browser for the domain on transport NetBT_Tcpip_{151A94A3-FE78-49D6. The master browser is stopping or an election is being forced.
--
Alle Meldungen bis hier (in "System") wiederholen sich recht oft.
--
Source: Server
Type: Warning
The server could not bind to the transport \Device\NwlnkIpx.
Source: KDC
Type: Error
The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was swolf and lookup type 0x0.
Source: KDC
Type: Error
The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was swolf@BRLN and lookup type 0x20.
Source: DhcpServer
Type: Error
The DHCP service encountered the following error while cleaning up the database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
Source: DhcpServer
Type: Error
The DHCP service encountered the following error when backing up the database:
An error occurred while accessing the DHCP database. Look at the
DHCP server event log for more information on this error.
Source: DhcpServer
Type: Error
The following problem occurred with the Jet database -1032: Jet database read or write operations failed. If the computer or database has just been upgraded, then this message can be safely ignored. If this message appears frequently, either there is not enough disk space to complete the operation or the database or backup database may be corrupt. To correct this problem, either free additional space on your hard disk or restore the database. After you restore the database, ensure that conflict detection is enabled in DHCP server properties. For information about restoring the database, see Help and Support Center. Additional Debug Information: JetBackup.
Source: MRxSmb
Type: Warning
The redirector failed to determine the connection type.
Source: Print
Type: Warning
Printer Driver Dell Laser Printer 5210n for Windows NT x86 Version-3 was added or updated. Files:- DKAAT2DD.DLL, DKAAT2DA.DLL, DKAAT2P1.XML, DKAAT2DA.HLP, DKAAT2P1.RES, DKAAT2B1.DLL, DKAAT2BJ.DLL, DKAAT2BT.DLL, DKAAT2DA.ALL, DKAAT2DU.DLL, DKAAT2ED.DLL, DKAAT2LU.DLL, DKAAT2PI.EXE, DKAAT2TD.DLL, DKAAT2TE.DLL, DKAAT2DA.CHM, DKAAT2DL.DLL, DKAAT2F0.DFM, DKAAT2PU.DLL, DKAAT2SE.DLL, DKAAT2TF.DLL, DKAAT2TH.HLP, DKAAT2D$.INI, DKAAT2UZ.ZIP, DKAAT2DA.CNT, DKAAT2UI.DLL, DKAAT2UI.JS, gencoin.dll, softcoin.dll, DKAAT2TH.HLP, DKAAT2BJ.DLL, gencoin.dll, softcoin.dll.
Source: Schannel
Type: Warning
No suitable default server credential exists on this system. This will prevent server applications that expect to make use of the system default credentials from accepting SSL connections. An example of such an application is the directory server. Applications that manage their own credentials, such as the internet information server, are not affected by this.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Das sind die Meldungen des Hauptservers (BRLNSVR01), bei dem die Probleme sind.
Ich habe hier auch noch die Meldungen des "Hilfsservers" (BRLNSVR02):
Application:
Source: APCPBEAgent
Type: Warning
"AVR Boost Active"
Directory Service:
Source: NTDS Replication
Type: Error
It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source.
The reason that replication is not allowed to continue is that the two machine's views of deleted objects may now be different. The source machine may still have copies of objects that have been deleted (and garbage collected) on this machine. If they were allowed to replicate, the source machine might return objects which have already been deleted.
Time of last successful replication:
2007-03-29 14:00:05
Invocation ID of source:
05fdf6c8-f6b8-05fd-0100-000000000000
Name of source:
c1019cdb-59c3-46c6-b4ad-7b121526796c._msdcs.brln.netz
Tombstone lifetime (days):
60
The replication operation has failed.
User Action:
Determine which of the two machines was disconnected from the forest and is now out of date. You have three options:
1. Demote or reinstall the machine(s) that were disconnected.
2. Use the "repadmin /removelingeringobjects" tool to remove inconsistent deleted objects and then resume replication.
3. Resume replication. Inconsistent deleted objects may be introduced. You can continue replication by using the following registry key. Once the systems replicate once, it is recommended that you remove the key to reinstate the protection.
Registry Key:
HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Allow Replication With Divergent and Corrupt Partner
Source: NTDS Replication
Type: Error
The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was unsuccessful.
A full synchronization of the security accounts manager (SAM) database to domain controllers running Windows NT 4.0 and earlier might take place if the PDC emulator master role is transferred to the local domain controller before the next successful checkpoint.
The checkpoint process will be tried again in four hours.
Additional Data
Error value:
8614 The Active Directory cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime.
Source: NTDS Replication
Type: Information
Duplicate event log entries were suppressed.
See the previous event log entry for details. An entry is considered a duplicate if the event code and all of its insertion parameters are identical. The time period for this run of duplicates is from the time of the previous event to the time of this event.
Event Code:
c00007fa
Number of duplicate entries:
15
--
Diese Meldungen, oder ähnliche von deerselben Quelle (NTDS Replication) wiederholen sich immer wieder.
--
System:
Source: Server Administrator
Type: Warning
Temperature sensor detected a warning value
Sensor location: BMC Ambient Temp
Chassis location: Main System Chassis
Previous state was: OK (Normal)
Temperature sensor value (in Degrees Celsius): 30.0
(um 6:00 morgens ^^)
--
kam ein paar mal vor (zwischen 6:00 und 10:00 morgens, bis ich kam und die klimaanlage wieder hochgedreht habe)
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
So, ich hoffe, damit kann man was anfangen.
Ich werde daraus nicht wirklich schlau... das einzige was ich verstehe ist, dass es anscheinend Probleme mit unserem Netzwerk gibt.
Hi,
da hast du wohl recht! Einige Probleme und Fehler...
Also ich würde dir empfehlen, dass Du das Problem an einen Dienstleister abtrittst oder einen anderen Admin mal fragst.
Auf die einzelnen Fehler einzugehen ist wirklich zu viel des Guten.
Was ich evtl. noch empfehlen könnte:
Schau dir die Prozessliste im Taskmanager an und dann versuch den Prozess heruaszufinden, der die meiste Prozesszeit zum Zeitpunkt des "Einfrierens" verursacht!
Ggf. würde ich noch den Processexplorer von Sysinternals empfehlen und Diskview.
Gruß und noch viel Erfolg
Markus
da hast du wohl recht! Einige Probleme und Fehler...
Also ich würde dir empfehlen, dass Du das Problem an einen Dienstleister abtrittst oder einen anderen Admin mal fragst.
Auf die einzelnen Fehler einzugehen ist wirklich zu viel des Guten.
Was ich evtl. noch empfehlen könnte:
Schau dir die Prozessliste im Taskmanager an und dann versuch den Prozess heruaszufinden, der die meiste Prozesszeit zum Zeitpunkt des "Einfrierens" verursacht!
Ggf. würde ich noch den Processexplorer von Sysinternals empfehlen und Diskview.
Gruß und noch viel Erfolg
Markus
