LOAD ERROR FOR DATA SUBSYSTEM OF AMO FBTXT EXCEPTION CODE : H'

[Dafidoe]

When i login to my HIPATH 4000 it gives this message.

S3: LOAD ERROR FOR DATA SUBSYSTEM OF AMO FBTXT
EXCEPTION CODE : H'8442

AN INCONSISTENCY IN YOUR CONTRACTED SOFTWARE HAS BEEN DETECTED

ADMINISTRATION OF SWU IS BLOCKED

ALL FEASU FEATURES WILL BE BLOCKED AFTER 00027 DAY(S)

(EMERGENCY OPERATION ONLY)

PLEASE CONTACT YOUR SERVICE CENTER AND QUOTE THIS MESSAGE.

i. what is the solution to this problem.
ii. how to i backup the IDE to an external device.

When check the disk status i get this message with defect to my controller 1.
<Dis-ddsm;
DIS-DDSM;
H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE, LOAD AREA IS: DS:
TYPE: HD SS-NO : <STDH5> SIZE : 3884 MB ( 62158*64KB) GRAN : 512
NON-RMX PARTITIONS:
SYSTEM ID SYSTEM NAME BEGIN / NO OF SECTOR(S) SIZE
H'12 UNIXWARE H' 7995F0 H' 139C5 39 MB ( 627*64KB)
H'63 UNIXWARE H' 7ACFB5 H' 3CF61CB 31212 MB ( 499395*64KB)
H'63 UNIXWARE H' 44A3180 H' 5DE2BF 3004 MB ( 48069*64KB)
AREA: A NAME : A1H1A STATUS : D E F E C T
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 100 MB (1600 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 2047 MB (32767*64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:GLA:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
IAG:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 616 MB (9868 *64KB) A-GRAN: 4096
CONTROLLER: 6
TYPE: HD SS-NO : <CF2G0> SIZE : 1953 MB ( 31263*64KB) GRAN : 512
AREA: A NAME : A1H6A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H6E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H6F STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
ACTIVATED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
AREA-SZ: 100 MB (1600 *64KB) A-GRAN: 4096
AREA: G NAME : A1H6G STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H6H STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H6I STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:MOD-SCR:
ACTIVATED LOGICAL NAMES:
:MOD-SCR:
AREA-SZ: 1183 MB (18940*64KB) A-GRAN: 4096

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;

 

[adibv]

It looks like licence will expire in 27 days.
dis-codew;

Try to reactivate HDD via (commands in german):
AENDERN-DSSM:A1,1;
EINSCHALTEN-DSSM:A1,1;

If still DEFECT on dis-ddsm; try to make a Unix restart (from Assistant) and check again.
Related HDD back-up there are some topics on forum ... use search.

 

[sbcsu]

Is this a system with a SIM card ?

 

[Dafidoe]

Thanks guys for the responses.

1. Please explain how I will do a Unix restart (from Assistant)


2. Is this a system with a SIM card ? NO SIMCARD

here is a message dis-codew
<display-codew;
DISPLAY-CODEW;
H500: AMO CODEW STARTED

SALES UNIT COUNTERS
===================

CODEWORD: CLA45A88WHCJKTCTEZ1HDR72CZGGMZ3FMN4LFH4PGRPG32X1C9P969M
5RNAFN8LUGKKF7HUAMXU5MDDFC7CBVVGA9RTAUMXE5MHYC71
VERSION : ????
SERIAL NUMBER: 0
HARDWARE ID : (DONGLE/SIM CARD NOT YET READY FOR READING OR NOT ATTACHED,
ATTACH DONGLE/SIM CARD AND REPEAT COMMAND)
ENTRY DATE : 06.04.2010
TRIAL MODE : NOT ACTIVATED
CONFIRMATION : 0

+---------------------------------------------+-------+-------+-------+-------+
| | | | | |
| UNIT | CON- | USED | FREE |BLOCKED|
| | TRACT | | | |
+---------------------------------------------+-------+-------+-------+-------+
| COMSCENDO | 0 | 480 | !!!!! | |
| CORDLESS E | 0 | 0 | 0 | |
| PNE | 0 | 0 | 0 | |
| SIGNALING SURVIVABILITY | 0 | 0 | 0 | |
| CC-AP FOR AP EMERGENCY | 0 | 0 | 0 | |
+---------------------------------------------+-------+-------+-------+-------+

AMO-CODEW-111 CODEWORD FOR ADMINISTRATION LOCK IN SWU
DISPLAY COMPLETED;

 

[thepfy]

[highlight #FCE94F]HARDWARE ID : (DONGLE/SIM CARD NOT YET READY FOR READING OR NOT ATTACHED,
ATTACH DONGLE/SIM CARD AND REPEAT COMMAND)[/highlight]

There is a SIM in the system but it cannot read it.

Normally it needs a clean

See last reply in [URL unfurl="true"]https://www.tek-tips.com/viewthread.cfm?qid=1724083[/url]

 

[sbcsu]

thread965-1781246

 

[Dafidoe]

thanks guys I ALL THAT WAS PRESCRIBED. The simcard/CODEWORD issue resolved.
the hdd/cf card are looking ok. but am still not able to backup using EX-UPDAT:BP,ALL; & EX-UPDAT:A1,ALL; IT GIVES
F02: ACCESS ERROR; DMS ERROR CODE 43.

[highlight #FCE94F]EX-UPDAT:BP,ALL;
H500: AMO UPDAT STARTED
F02: ACCESS ERROR; DMS ERROR CODE: 43
AMO-UPDAT-111 UPDATING HARD DISK DATABASE
EXEC NOT COMPLETED;
<EX-UPDAT:A1,ALL;
EX-UPDAT:A1,ALL;
H500: AMO UPDAT STARTED
F02: ACCESS ERROR; DMS ERROR CODE: 43
AMO-UPDAT-111 UPDATING HARD DISK DATABASE
EXEC NOT COMPLETED;[/highlight]

PLEASE ANY NEW IDEAS ON GETTING IT DONE SO THAT ALL CHANGES CAN BE BACKED UP.

HERE IS MY DISK STATUS

DIS-DDSM;
H500: AMO DDSM STARTED
CONTROLLER: 1 IS ACTIVE LOAD DEVICE, LOAD AREA IS: DS:
TYPE: HD SS-NO : <STDH5> SIZE : 3884 MB ( 62158*64KB) GRAN : 512
NON-RMX PARTITIONS:
SYSTEM ID SYSTEM NAME BEGIN / NO OF SECTOR(S) SIZE
H'12 UNIXWARE H' 7995F0 H' 139C5 39 MB ( 627*64KB)
H'63 UNIXWARE H' 7ACFB5 H' 3CF61CB 31212 MB ( 499395*64KB)
H'63 UNIXWARE H' 44A3180 H' 5DE2BF 3004 MB ( 48069*64KB)
AREA: A NAME : A1H1A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
ACTIVATED LOGICAL NAMES:
DS:
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
ACTIVATED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
AREA-SZ: 100 MB (1600 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
ACTIVATED LOGICAL NAMES:
:CGD:
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
ACTIVATED LOGICAL NAMES:
MS:,SY:
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:SCR:
ACTIVATED LOGICAL NAMES:
:SCR:
AREA-SZ: 2047 MB (32767*64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:GLA:
ACTIVATED LOGICAL NAMES:
:GLA:
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
IAG:
ACTIVATED LOGICAL NAMES:
IAG:
AREA-SZ: 616 MB (9868 *64KB) A-GRAN: 4096
CONTROLLER: 6
TYPE: HD SS-NO : <CF2G0> SIZE : 1953 MB ( 31263*64KB) GRAN : 512
AREA: A NAME : A1H6A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H6E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 450 MB (7200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H6F STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 100 MB (1600 *64KB) A-GRAN: 4096
AREA: G NAME : A1H6G STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H6H STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H6I STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:MOD-SCR:
ACTIVATED LOGICAL NAMES:
:MOD-SCR:
AREA-SZ: 1183 MB (18940*64KB) A-GRAN: 4096

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;

 

[Moriendi]

Hard to say what's wrong. Controller 1 is active load device and area E is active.

I would reload the ADP processor and reseat the HDCF plate.

dea-dssm:a1,1,,yes;
Slide out the ADP proc.
Slide out the HD/CF card (this is only to power cycle it)
Insert HD/CF
Insert ADP.

Wait for ADP to boot.
Try again.

Can't remember if it's 2 commas or 3 before that "yes" in dssm. Prompt it's answering is "unixshut" ie, shutdown the unix=yes;

On your first post areas on HD 1 are defect. That is not normal.

If above does not resolve, then you'll have to reload the ADP (not the SWU) from the MO and then make another exec-updat, then at least you will have a copy of the DB stored. You could then try a copy ddrsm frmo 6 to 1, maybe. Try above first.

 

[adibv]

You may try to re-initialize DMS area:

sta-init:a1,a1h1h; .. I think