Warning on SPM??

[thephonelady]

I have a customer with a Magix 2.0 using Legend carriers and MLX boards. They recently moved SPM to another computer and when they did this they are now getting the message- WinSPM cannot recognize the ckt pk in slot 1
Quick access will not be avail until this situation is resolved
Note- ATL ckt pks can only be used on Merlin Legend.
The weird thing is that there are no ATL packs in the system.
When I got out there I found this setup
Slot 00- Processor
Slot 01-408 G/S L/S MLX
Slot 02- "
Slot 03- 012 T/R
Slot 04-016 T/R
Slot 05-408 G/S L/S MLX
Slot 06-empty
Slot 07-Empty
Slot 08- Merlin Msg

I'm not sure why 2 slots were empty but when I did an inventory the system saw those slots as empty however when I did a print ext dir there were default exts assigned to the ports of the empty slots. I powered down the system & moved the Messaging to slot 06 & did a board renumber & everything came up ok and I reassigned the vm ports in the calling group. I had no errors but still get those messages. Nothing seems to be affected by this. Any ideas??? Thanks in advance.
Eileen

 

[Pepperz]

WinSPM is horribly quirky, especially with "some" computers, and "some" modems. If you are accessing via modem, try the serial connection to the Admin port, if already using serial, try reinstalling the software.

 

[merlinman]

As Pep said, WINSPM is QUIRKY, but he is being nice.

My theory is that either the 408 Mod in Slot 1 is REALLY OLD or WINSPM doesn't like those empty slots.

What is in slot 2 by the way?

My first word of advice is: DO NOT DO A BOARD RENUMBER at this point.

My second would be to power down, and swap the modules in Slots 1 & 5 and see if that makes a difference in your "WINSPM cannot...." error message.

 

[franke]

hmm, you said they were a magix using merlin carriers...i presume though that the second carrier is the metal magix carrier?

franke

 

[thephonelady]

Slot 2 has a 408 G/S L/S MLX and they are using the Merlin Legend carriers with a Magix processor & Messaging in clamshells. I get the same message whether I am on site or remote.