Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ADSM\s+database\s+error\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*ADSM\s+database\s+error\s*$/: 4 ]

Total 4 documents matching your query.

1. ADSM database error (score: 1): Author: "Jordan, Chris (ELS)" <c.jordan AT ELSEVIER.CO DOT UK>; Date: Tue, 26 Oct 1999 09:22:00 +0100; 8:30 this morning - ADSM was having no problems.... 8:34 this morning, the following errors appeared: Do we need help?? Do we need to restore from backup?? Restarting the ADSM service allowed it to c; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-10/msg01293.html (11,675 bytes)
2. Re: ADSM database error (score: 1): Author: ADSML <adsml AT YIFAN DOT NET>; Date: Tue, 26 Oct 1999 07:35:00 -0500; This problem can be narrowed to this. Basically, ADSM couldn't read certain pages of your ADSM DB for one reason or another. Now if you were able to get it up again, ADSM was able to recover, albeit; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-10/msg01311.html (10,808 bytes)
3. ADSM database error (score: 1): Author: Jordan, Chris (ELS) <c.jordan AT ELSEVIER.CO DOT UK>; Date: Sun, 04 Oct 2015 17:38:08 -0500; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-10/msg01312.html (12,127 bytes)
4. Re: ADSM database error (score: 1): Author: Richard Sims <rbs AT BU DOT EDU>; Date: Tue, 26 Oct 1999 09:05:42 -0400; Well, better to have diagnostic info come out at error time than just an "*SM failed" message. The now-notorious ANR9999D message is a catch-all emissions point for conditions which should be rare a; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-10/msg01317.html (10,979 bytes)

Current List: 1 - 4
Page: [1]