Unable to start SCP after upgrading to 10.2

[Legacy User]

Hi All,

 

After upgrading to spectrum r10.2, when i'm opening the SCP on primary MLS it's giving "could not connect to the location server" error. Tried to restart the processd but no luck. Below are the logs from processd_log file.

****************************************

Jan 03 14:49:24  Processd Service has been started.

Jan 03 14:49:33 Failure to connect to Location Service at host:

ABC, port #: 56063.

Will try again until we make a connection.

Jan 03 14:50:03 WILL NOT START AUTORESTARTED PART LOCSERV BECAUSE WE EXCEEDED THE RETRY LIMIT!
Jan 03 14:50:34 Failure to send heartbeat message

*****************************************

Kindly suggest any possible solution. 

 

Regards,

Bijender

[Silvio Okamoto]

Hi Bijender,

 

Did you check the following files:

a) $SPECROOT/LS/LOCSERV.OUT

b) $SPECROOT/LS/.locrc

 

Is the LocServer.exe process up and running?

 

Thanks,

Silvio

[Legacy User]

Hi Silvio,

 

LocServer.exe is not running, tried to start it manually but getting some error massage(screenshot attached).

Entires in .locrc file are fine.

 

 

 

Thanks,

Bijender

[Silvio Okamoto]

Hi Bijender,

 

Is there anything in the LOCSERV.OUT log file?

 

Try enabling the processd in debug mode and then start the LocationServer via Install Ticket.

 

Here are the steps to enable the processd in debug mode:

a) Open a bash shell (bash -login)

b) Navigate to the $SPECROOT/lib/SDPM directory

c) Take note of processd.exe's PID in the Windows Task Manager

d) Run the following command in the bash shell:

./kill -TRAP <PID of processd>

e) Try starting the Location Server via Install Ticket (use TEC1917563)

1. Navigate to the $SPECROOT/bin directory in a bash shell 

2. Run the following syntax:

./launchinstdbapp <hostname> 2 LOCSERV y LOCSERV.OUT

3. Check the processd_log and LOCSERV.OUT log files.

f) To turn off processd debugging, just rerun the command that started it. (./kill -TRAP <PID of processd>)

 

TEC1917563 - How can I start and stop processes that are running under processd in Spectrum?

 

Thanks,

Silvio

[Legacy User]

Hi Silvio,

I got nothing in the LOCSERV.OUT file even after running the processd in debug mode, no contents in the log file..

 

Thanks,

Bijender

[Silvio Okamoto]

Hi Bijender,

 

What did you get in the processd_log file when you enabled processd in debug mode and tried to start the Location Server via Install Ticket?

 

Thanks,

Silvio

[Legacy User]

Hi Silvio,

 

I'm sharing the processd logs captured during debug mode on. kindly have a look in it..

*************************************

Jan 04 11:07:17 DEBUG START
Jan 04 11:08:26
Client Name: install partname startup program
User Name : Administrator( 0 )
Host : spectroserver1( ::1 )
Authorized : Success

Jan 04 11:08:26 STARTED NEW PROCESS

Jan 04 11:08:26 DATE OF THIS REQUEST

ticket function id = 257
ticket cb function id = 256
ticket exchange id = 4
ticket more data = 0
ticket version number = 5
ticket process_pid = 1216
ticket process_ppid = 0
ticket process_gpid = 1216
ticket process_state = 2
ticket how_many_procs = 1
ticket auto_restart = 1
ticket admin privileges = 1
ticket server process = 1
ticket windows service = 0
ticket dont save ticket = 0
ticket state based = 0
ticket user_id = 0
ticket user_name = Administrator
ticket requester user_name = Administrator
ticket group user_id = 0
ticket part_name = LOCSERV
ticket application_name = Location Service
ticket work_pathname = C:/win32app/Spectrum/LS
ticket log_name = C:/win32app/Spectrum/LS/LOCSERV.OUT
ticket output file pos = 0
ticket output_file =
ticket os errno = 0
os errno string =
ticket num of errnos = 1
errnos = 0
ticket retry timeout = 600
ticket retry maximum = 5
ticket retry current = 0
ticket timestamp started = 1483508306
ticket start_priority = 15
argv list = C:/win32app/Spectrum/LS/LocServer.exe
envp list = ALLUSERSPROFILE=C:\ProgramData
envp list = APPDATA=C:\Windows\system32\config\systemprofile\AppData\Roaming
envp list = CLISESSID=1984
envp list = COMMONPROGRAMFILES(X86)=C:\Program Files (x86)\Common Files
envp list = COMMONPROGRAMFILES=C:\Program Files\Common Files
envp list = COMPUTERNAME=SPECTROSERVER1
envp list = COMSPEC=C:\Windows\system32\cmd.exe
envp list = CVS_RSH=/bin/ssh
envp list = CYGPATH=C:\win32app\Spectrum\NT-Tools\SRE
envp list = CYGWIN32=C:/win32app/Spectrum/NT-Tools/SRE
envp list = CYGWIN32PATH=/C/win32app/Spectrum/NT-Tools/SRE
envp list = CYGWIN=nontsec
envp list = FP_NO_HOST_CHECK=NO
envp list = HOME=C:\win32app\Spectrum\NT-Tools\SRE\home\Administrator
envp list = HOMEDRIVE=C:
envp list = HOMEPATH=\Users\Administrator
envp list = HOSTNAME=SpectroServer1
envp list = INFOPATH=/usr/local/info:/usr/share/info:/usr/info:
envp list = LOCALAPPDATA=C:\Windows\system32\config\systemprofile\AppData\Local
envp list = LOGONSERVER=\\SPECTROSERVER1
envp list = MAKE_MODE=unix
envp list = MANPATH=/usr/local/man:/usr/share/man:/usr/man:
envp list = NAMING_SERVICE_PORT=14006
envp list = NUMBER_OF_PROCESSORS=1
envp list = OLDPWD=/c/win32app/Spectrum
envp list = OS=Windows_NT
envp list = PATH=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\win32app\Spectrum\NT-Tools\SRE\bin;C:\win32app\Spectrum\lib;
envp list = PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
envp list = PERLLIB=%PERLLIB%
envp list = PROCESSOR_ARCHITECTURE=x86
envp list = PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 44 Stepping 2, GenuineIntel
envp list = PROCESSOR_LEVEL=6
envp list = PROCESSOR_REVISION=2c02
envp list = PROGRAMDATA=C:\ProgramData
envp list = PROGRAMFILES(X86)=C:\Program Files (x86)
envp list = PROGRAMFILES=C:\Program Files
envp list = PROMPT=$P$G
envp list = PS1=\[\e[44m\e[36m\]\h%\w\[\e[0m\]\n>
envp list = PUBLIC=C:\Users\Public
envp list = PWD=/c/win32app/Spectrum/bin
envp list = SESSIONNAME=Console
envp list = SHELLOPTS=igncr
envp list = SHLVL=1
envp list = SPECPATH=C:\win32app\Spectrum
envp list = SPECROOT=C:/win32app/Spectrum
envp list = SRADROOT=C:\Program Files (x86)\SRAdmin
envp list = SYSTEMDRIVE=C:
envp list = SYSTEMROOT=C:\Windows
envp list = TEMP=C:\Windows\TEMP
envp list = TERM=cygwin
envp list = TMP=C:\Windows\TEMP
envp list = USER=Administrator
envp list = USERDOMAIN=WORKGROUP
envp list = USERNAME=SPECTROSERVER1$
envp list = USERPROFILE=C:\Windows\system32\config\systemprofile
envp list = WINDIR=C:\Windows
envp list = _=./launchinstdbapp.exe
envp list = PERL=C:/win32app/Spectrum/bin/perl
envp list = SPECJAVA=C:/win32app/Spectrum/Java/jre
envp list = BES_LIC_DIR=C:/win32app/Spectrum/bin/VBNS/license
envp list = TOMCAT_ROOT=C:/win32app/Spectrum/tomcat
envp list = HUGE_LANDSCAPE_SUPPORT=0
envp list = CommonProgramFiles=C:\Program Files (x86)\Common Files
envp list = CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
envp list = CommonProgramW6432=C:\Program Files\Common Files
envp list = ComSpec=C:\Windows\system32\cmd.exe
envp list = PROCESSOR_ARCHITEW6432=AMD64
envp list = ProgramData=C:\ProgramData
envp list = ProgramFiles=C:\Program Files (x86)
envp list = ProgramFiles(x86)=C:\Program Files (x86)
envp list = ProgramW6432=C:\Program Files
envp list = SystemDrive=C:
envp list = SystemRoot=C:\Windows
envp list = windir=C:\Windows

 ******************************************************************************************

Thanks,

Bijender

[Silvio Okamoto]

Hi Bijender,

 

What is the version of your Operating System?

I noticed your KERNEL32.DLL file version is 6.0.6001.1800.

 

In my Windows 2012 R2 I have the following entry in the $SPECROOT/SS/support/SpectroSERVER.info file regarding KERNEL32.DLL file:

KERNEL32.DLL                    6.3.9600.17415      1302528         0xbaa10000      C:\Windows\system32\KERNEL32.DLL

 

In my Windows 2008 R2 I have the following in the $SPECROOT/SS/support/SpectroSERVER.info file regarding KERNEL32.DLL file:

kernel32.dll                    6.1.7601.23543      1114112         0x74a70000      C:\Windows\syswow64\kernel32.dll

 

Thanks,

Silvio

[Legacy User]

Hi Silvio,

I am using Windows Server 2008(x64).

Thanks,

[Silvio Okamoto]

Hi Bijender,

 

Kernel32.dll is the 32-bit dynamic link library found in the Windows operating system kernel. It handles memory management, input/output operations, and interrupts.

What do you have in the $SPECROOT/SS/support/SpectroSERVER.info file regarding KERNEL32.DLL?

SP2 has been applied on your Windows Server 2008 (x64)?

 

Thanks,

Silvio

[Legacy User]

Hi

Below is the information in $SPECROOT/SS/support/SpectroSERVER.info regarding KERNEL32.DLL.

 kernel32.dll                   6.0.6001.18000      1224704         0x76cc0000      C:\Windows\system32\kernel32.dll

 

currently server is on SP1, Is it mandatory to make it SP2 for spectrum 10.2 ?

Thanks,

Bijender 

[Silvio Okamoto]

Hi Bijender,

 

Yes. Check the System Requirements section of CA Spectrum 10.2 Installation Guide.

System Requirements for Installing CA Spectrum - CA Spectrum - 10.2 - CA Technologies Documentation 

 

Thanks,

Silvio

[Josh Bovee]

This same thing happened to me after doing the 10.2 upgrade and unfortunately ended up having to do a uninstall/reinstall of Spectrum on the SpectroServers.

[Anon Anon]

The same error by me!  As described  above. 

I update from 10.1.1.0.64 to 10.02.00.00.244, fortunately only on my Test-Machine.

OS = Windows Server 2008 (64) SP2

 

In Windows events:

Fehlerhafte Anwendung LocServer.exe, Version 10.2.0.0, Zeitstempel 0x584efdf0, fehlerhaftes Modul KERNEL32.dll!K32GetProcessMemoryInfo, Version 6.0.6002.19346, Zeitstempel 0x55023e3e, Ausnahmecode 0xc0000139, Fehleroffset 0x00000000000b6f68, Prozess-ID 0xc3c, Anwendungsstartzeit 01d26a7df7d9ee33.

Details:

+ System
  - Provider
   [ Name]  Application Error
  - EventID 1000
   [ Qualifiers]  0
   Level 2
   Task 100
   Keywords 0x80000000000000
  - TimeCreated
   [ SystemTime]  2017-01-09T13:40:40.000Z
   EventRecordID 7421
   Channel Application
   Computer Spectrumtest.stadt.braunschweig.de
   Security

- EventData
   LocServer.exe
   10.2.0.0
   584efdf0
   KERNEL32.dll!K32GetProcessMemoryInfo
   6.0.6002.19346
   55023e3e
   c0000139
   00000000000b6f68
   c3c
   01d26a7df7d9ee33

 

[Silvio Okamoto]

Please open a ticket with CA support.

[Anon Anon]

Here is the answer from CA.

This is a known issue that is currently being investigated by Engineering under defect DE265472.