ACTDIAG: Fehlerprotokoll - wie reparieren?

Probleme und Tips in der Anwendung von ACT!

Moderatoren: Ingrid Weigoldt, Schlesselmann, Robert Schellmann

Antworten
mt333
Beiträge: 8
Registriert: Freitag 1. August 2003, 11:21

ACTDIAG: Fehlerprotokoll - wie reparieren?

Beitrag von mt333 »

Hallo zusammen,

ich habe mit ACTDIAG folgendes Fehlerprotokoll generiert. Zum Lösen dieser Probleme habe ich alle Kontakt und Gruppendaten in eine neue Datenbank importiert. Das Importieren war erfolgreich - leider war nach dem Import auch die neue Datenbank fehlerhaft.

Actdiag hat die Fehler nicht korrigiert. Wie kann ich diese manuell korrigieren? Gibt es da Möglichkeiten?

Ach ja, beim Qick check wird "invalid File Size" ausgegeben. Das Arbeiten mit der Datenbank funktioniert eigentlich, leider gibt es aber ca. 20 Abstürze pro Tag!

Vielen Dank
Michael


ADB Rec # 792 had no REL match
ADB Rec # 2770 had no REL match
ADB Rec # 3043 had no REL match
ADB Rec # 3130 had no REL match
ADB Rec # 3140 had no REL match



REL Rec # 147 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 595 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 610 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 935 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 1409 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 1447 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 1488 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 1492 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 2112 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 2681 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3120 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3315 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3365 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3568 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3820 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3908 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3928 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3934 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3942 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3943 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 3960 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 4074 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 4332 ID: $5!# I#T \ had no GDB match and was removed
REL Rec # 4347 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 4361 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 4362 ID: $5!# I#T \ had no GDB match and was removed
REL Rec # 4423 ID: $5!# I#T \ had no GDB match and was removed
REL Rec # 4430 ID: $5!# I#T \ had no GDB match and was removed
REL Rec # 4531 ID: $5!# I#T \ had no GDB match and was removed
REL Rec # 4544 ID: $5!# I#T \ had no GDB match and was removed
REL Rec # 4572 ID: $5!# I#T \ had no GDB match and was removed
REL Rec # 4666 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 4845 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 4957 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 4964 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 5048 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 5261 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 5342 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 5389 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 5801 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 6378 ID: ?3= 81["Z had no GDB match and was removed
REL Rec # 7477 ID: ?3= 81["Z had no GDB match and was removed



HDB Record 2499 had no associated contact and was reassigned to ACTDiag
HDB Record 2500 had no associated contact and was reassigned to ACTDiag
HDB Record 3352 had no associated contact and was reassigned to ACTDiag



SDB Record 207 had an incorrect group link
SDB Record 221 had an incorrect group link
SDB Record 596 had an incorrect group link
SDB Record 602 had an incorrect group link
SDB Record 603 had an incorrect group link
SDB Record 604 had an incorrect group link
SDB Record 630 had an incorrect group link
SDB Record 701 had an incorrect group link
SDB Record 828 had an incorrect group link
SDB Record 842 had an incorrect group link
SDB Record 941 had an incorrect group link
SDB Record 969 had an incorrect group link
SDB Record 976 had an incorrect group link
SDB Record 978 had an incorrect group link
SDB Record 982 had an incorrect group link
SDB Record 984 had an incorrect group link
SDB Record 985 had an incorrect group link
SDB Record 989 had an incorrect group link
SDB Record 1064 had an incorrect group link
SDB Record 1095 had an incorrect group link
SDB Record 1209 had an incorrect group link
SDB Record 1210 had an incorrect group link
SDB Record 1233 had an incorrect group link
SDB Record 1281 had an incorrect group link
SDB Record 1283 had an incorrect group link
SDB Record 1284 had an incorrect group link
SDB Record 1285 had an incorrect group link
SDB Record 1286 had an incorrect group link
SDB Record 1296 had an incorrect group link


ACTDiag Repair - Ended at 01.01.2006 16:41:16
Ingrid Weigoldt
Beiträge: 3027
Registriert: Donnerstag 24. April 2003, 02:00
Wohnort: Viernheim

Beitrag von Ingrid Weigoldt »

Hallo mt33,

wie kommen Sie zu der Annahme, ACTDiag hätte die protokollierten Fehler nicht beseitigt?
Sie werden wahrscheinlich in der behandelten Datenbank einen Datensatz finden über Firma = ACTDIAG, in dem zumindest die nicht zuordenbaren Einträge aus HDB zu finden sind. Alles andere kann ACTDiag nur löschen.

Beim QuickCheck "Invalid Size" zu sehen, das habe ich auch - und meine Datenbank funktioniert trotzdem Klasse.

Natürlich ist bei 20 Abstürzen am Tag die Datenbank schnell wieder instabil. Ist auf Ihrem PC Opportunistik Locking = False (also richtig) gesetzt? Ist die Datenbank lokal oder auf einem Server? Wenn Server, ist auch dort OpLocks ok? Wenn Server, welches Betriebssystem?
Welches ACT überhaupt?

Wann treten die Abstürze auf? Schon mal hier im Forum nach CB.DAL gesucht?
Schöne Grüße aus Viernheim
Ingrid Weigoldt
mt333
Beiträge: 8
Registriert: Freitag 1. August 2003, 11:21

Beitrag von mt333 »

Hallo Frau Weigold,

vielen Dank für Ihre Antwort.

Ich habe mir gerade das Update von ACTDIAG auf 6.0.3.953 installiert. Mit dieser Version werden die Fehler behoben. Invalid File Size wird immer noch angezeigt (ist aber wohl doch kein Problem).

Ich werde ACT 6.0 nun neu installieren und dann die Datenbank noch einmal testen.

Hoffentlich läuft dann die DB stabiler. Ich werde in ein paar Tagen das Ergebnis posten.

Viele Grüsse
mt333

PS: Die Opportunistik Locking Einstellungen sind in Ordnung.
Ingrid Weigoldt
Beiträge: 3027
Registriert: Donnerstag 24. April 2003, 02:00
Wohnort: Viernheim

Beitrag von Ingrid Weigoldt »

Hallo mt333,

Ihr ACT!6 hat doch hoffentlich die Version 6.0.3.994? Wenn nicht, unbedingt Update downloaden (Melville-Schellmann, Downloadbereich). Und patch4 nicht vergessen. Bestandteil von ACT 6.0.3.994 ist die ACTDiag 6.0.3.951, und die kanns auch.
Schöne Grüße aus Viernheim
Ingrid Weigoldt
mt333
Beiträge: 8
Registriert: Freitag 1. August 2003, 11:21

Beitrag von mt333 »

Hallo Frau Weigold,

ich hatte ACTDiag 6.0.3.951 installiert. Mit dieser Version wurde kein Fehler behoben. Lediglich das Fehlerprotokoll aus meinem ersten Post wurde generiert.

Gruss
mt333
Antworten