SECC 4.2 services not starting 3

[atascoman]

I have a new SECC 4.2 server that I am having a problem with. The VSM, ASM and TFE service are stuck in the starting mode when viewing them from the SMon viewer. The ELAN comes up on the PBX, but when you stat it in LD48 it shows:

SERVER TASK: ENABLED
ELAN #: 16 DES: elan16
APPL_IP_ID: 10 .194 .91 .12 LYR7: ACTIVE EMPTY APPL ACTIVE
ELAN #: 17 DES: test
APPL_IP_ID: 10 .194 .91 .30 LYR7: ACTIVE EMPTY APPL
DISABLE


Elan 16 is the Call Pilot, 17 is the SECC. My ELAN and VSID are programmed as:

VAS
VSID 16
DLOP
ELAN 16
SECU NO
INTL 0001
MCNT 9999

VSID 17
DLOP
ELAN 17
SECU YES
INTL 0001
MCNT 9999


REQ prt
TYPE adan ELAN

ADAN ELAN 16
CTYP ELAN
DES elan16
N1 512
ADAN ELAN 17
CTYP ELAN
DES test
N1 512

Does the ELAN have to be 16 for Symposium?

I also have the co-resident client installed on the server if that matters. The server is on SU13 as well. I can ping the PBX from the server and the server from the PBX.
Any ideas?

 

[sandyml]

Make sure that your PBX host name and switch ID as you have in the SECC are identical to the PBX. Meaning, make sure that your switch ID has been entered with caps for letters and that it matches the PBX switch ID. Go to LD 117 and PRT ELNK. The active host name that it prints out needs to match what you have in the SECC, case sensitive.

 

[turtle916]

I agree with sandyml, double-check that everything in the SECC has been entered correctly. I once had this problem and it turned out that I had typed in the wrong IP address for the PBX when I went through the Server Setup Config.

Also, make sure that you are logging into windows with the NGenSys account. Many of the services are tied to this account and may not start up if you log on as a different user.

 

[atascoman]

I checked everything. The Switch name in the SECC setup matches the active ELNK host name and the IP address is correct. I am logging in as ngensys as well.

 

[TheWorkingMan]

If the switch serial number has a letter in it such as "D" make sure that it is in CAPS in the server setup and configuration. If the letter is lowercase it will cause this issue!!

TWM

 

[atascoman]

This server is not actually licensed for the PBX I am using to test it on. It's a new server that I am setting up for one of our customers in another city. if the serial number on the keycode that is entered during the setup process is not the same as the PBX it's connecting to will this cause this problem. I remember being able to get one to work this way before, but who knows I may be full of crap on that. it's been a while.

 

[TheWorkingMan]

Yea, you will not be able to get ASM, VSM and TFE up if the serial numbers don't match. You will see application disabled in the ELAN STAT. The only way to get it to work is to change the serial number on the PBX. But we don't know how to do that!! Or do we???

TWM