SCH3300 The DN or Position ID is invalid / Opt.11

[AsokTheIntern]

Dear All,

I have the following problem:

One of our users phones was dead this morning. The TN suddenly appears to be "free" in the system, but the DN not. I can assign a different DN but I need to give the user back his old DN.

I would be very grateful is anyone could help me with this.
Kind regards Sebastian

CHECKING THAT THE TN IS FREE
REQ: luvu
TYPE: 2000
TN
TYPE 2000 TN 013 0 00 01 8D VCE

TRYING TO SETUP THE DN ON THE TN AGAIN: FAILS
REQ: cpy 1
TYPE: 3904
CFTN 11 14
DES M3904
*** MAKE PRINTER READY ***
TN 13 1
DN 9828
SCH3300
DN

CHECKING THE ERROR
>err sch3300
>SCH3300
The DN or Position ID is invalid, it must be unique.
Severity: Info

CHECKING THE DN
OVL000
>ld 20
REQ: prt
TYPE: dnb
CUST 0
DN 9828
DATE
PAGE
DES
NO ACT SINCE NO DATE

TRYING TO SETUP DIFFERENT DN ON TN: WORKS
REQ: cpy 1
TYPE: 3904
CFTN 11 14
DES M3904

*** MAKE PRINTER READY ***
TN 13 1
DN 9803

NEW 3904 TN 013 0 00 01 DN 9803

 

[hawks]

Build it with the new DN then go in and change it to the DN you want. Let us know what happens, have you tried to do a print with just 982 as the extension?

 

[AsokTheIntern]

Hawks,

thx for the tip. Unfortunately I tried it already without success, here the result:
REQ: cpy 1
TYPE: 3904
CFTN 11 14
DES M3904
*** MAKE PRINTER READY ***
TN 13 1
DN 9803
NEW 3904 TN 013 0 00 01 DN 9803

REQ: chg
TYPE: 3904
TN 13 1
ECHG yes
ITEM key 0 scr 9828
SCH0011
>err sch0011
SCH0011
TN in DNBLOCK fails TNTRANS.
Severity: Info

 

[PERRYPJ]

TRY DOING A PRINT ON DNB 982 AND SEE WHAT PRINTS OUT

OLD ROLMEN WORKING ON NORTELS

 

[AsokTheIntern]

Printed DNB: 982
There is no 9828 showing up:
DN 9827
CPND
CPND_LANG ROMAN
NAME John Doe 1
XPLN 13
DISPLAY_FMT FIRST,LAST
TYPE SL1
TN 006 0 00 02 KEY 00 MARP DES M3904 6 APR 2006
(3904)
TN 006 0 00 01 KEY 34 DES 001 25 JUN 2007
(3904)
TN 007 0 00 07 KEY 34 DES 001 25 JUN 2007
(3904)

DN 9829
CPND
CPND_LANG ROMAN
NAME John Doe 2
XPLN 13
DISPLAY_FMT FIRST,LAST
TYPE SL1
TN 006 0 00 12 KEY 00 H MARP DES M3904 9 MAY 2007
(3904)
TN 011 0 00 12 KEY 33 DES YES 25 JUN 2007

 

[TAnselm]

TN in DNBLOCK fails TNTRANS.
Severity: Info

This points to corruption. You basically have 2 options.
1. Call Nortel and get charged an Arm and a leg for them to fix it through PDT.

2. INI the switch. This may or may not get rid of the corruption. If it does your all set if not, you are no worse off and can still call Nortel or possibley try a SYSLOAD.

 

[MagnaRGP]

Try a LD 1 (low traffic period).

That has helped me in the past.

 

[MERIDIAN11C]

Do this on PDT and reboot

PDT> C:/U/DB ENTER


PDT> RENAME CONFIG.REC CONFIG.OLD
PDT> RENAME CONFIG.BAK CONFIG.REC
PDT> RENAME DATABASE.REC DATABASE.OLD
PDT> RENAME DATABASE.BAK DATABASE.REC