2051=Std By CPU. wrong message 39 on ne

[moya]

Iam getting these weird messages about the standby cpu and terminals. Here are the messages.
10/01/08 09:34:33 000001S|00/24/-/---|=3:2040=Std By CPU. Bad term type = T_RESU
instead of POS_NUM Msg 32 n_term 20
10/01/08 09:35:39 000001S|00/16/-/---|=3:2040=Std By CPU. Bad term type = T_RESU
instead of POS_NUM Msg 32 n_term 22
and

10/01/08 09:10:31 000001S|--/--/-/---|=3:2051=Std By CPU. wrong message 39 on ne
qt 399 info 20003
10/01/08 09:11:01 000001S|--/--/-/---|=3:2051=Std By CPU. wrong message 39 on ne
qt 399 info 20003

I have done the twin command everything in fine. I have checked the configuration of at least one of the neqt terminal in both main and stanby cpu's. I would be grateful for any suggestions. Thank You.

[knightr1der]

When was the last time a 'mastercopy' was performed?

Perhaps performing a new mastercopy will clear the problem if they are out of synch (which is not impossible).

[moya]

thank you for the reply i will try that. I thought about that but I needed a second opinion Ill schedule that.

[Eliott_DUP]

Database inconsistency on standby.
Bad term type = T_RESU instead of POS_NUM means that the
maincpu has an user at a specific port and the standby nothing.
Enter listerm 0 24 and check position 20 on both CPU's
Enter listerm 0 16 and check position 22 on both CPU's
Then enter traded 399 on both cpu's and compare the results.

Solution:
Disable autostart on standby
Reboot standby
Enter mastercopy twincpu and choose all except linux/chorus data and enable start of telephonic application
Enable autostart

[moya]

many thnks elliot

[frank]

I had the same issue on a couple of sites lately , a cpu duplication did not fix anything.
After 2/3 days, the error came back. I have a ticket open with France, and it looks like there is a patch to come..