Unsolved

MDTSVR Not Starting Every time

Comments: 4 - Last Comment by rglenn on Jan 4, 2017   Comment Filter:
Posted on Nov 17, 2016
 
 

Hello

In our stage environment, when we go to start MDTSVR it will get as far as the long show below and then turn green. Only thing is that this is not a complete start. In terms of steps, we start Portal first then MDTSVR.  Not all the time but at times it will take us 5 - 10 attempts to stop and restart MDTSVR until we get a full log and it is green  Any thoughts on what is happening in the step below. Here is the log.....

1d30 11-17-16 15:25:47 MAIN: Process Name Set To: I/Mdtsvr
1d30 15:25:47 MAIN: Debug Level Set To: 5
1d30 15:25:47 MAIN: Registry: UEDELTA MODE OFF
1d30 15:25:47 MAIN: Registry: Groups set to "MobileTCOms"
1d30 15:25:47 MAIN: Registry: CmdThreads set to 10
1d30 15:25:47 MAIN: Registry: CmdThreadTimeout set to 300 seconds
1d30 15:25:47 MAIN: Registry: ExitTimeout set to 60 seconds
1d30 15:25:47 MAIN: Registry: SendMsgSuffix set to ""
1d30 15:25:47 MAIN: Registry: ALL UNITS WILL NOT BE BROADCAST
1d30 15:25:47 MAIN: Registry: THE UNIT ID PREFIX '$' WILL BE USED TO DETERMINE IF A CAD UNIT IS SIGNED ON DURING STARTUP
1d30 15:25:47 MAIN: Registry: AlarmNode not found defaulting to 'RNCAlarms'
1d30 15:25:47 MAIN: Registry: Apc set to {7F0238B7-3953-468b-A02D-96C5BDCEF323}
1d30 15:25:47 MAIN: Registry: CommonPlacePrefix set to '@'
1d30 15:25:47 MAIN: Registry: CatalogedAlarmPrefix set to '#'
1d30 15:25:47 MAIN: Registry: WakeupTimeout set to 20 seconds
1d30 15:25:47 MAIN: Registry: RetryTimeout set to 60 seconds
1d30 15:25:47 MAIN: Registry: QueuedMessagesOutputPerMdt set to 10
1d30 15:25:47 MAIN: Registry: ACTIVATE LOGGING IS 0 (OFF)
1d30 15:25:47 MAIN: Registry: MAP COMMANDS BY APC ID OFF
1d30 15:25:47 MAIN: Registry: BROADCAST TABLE WILL BE USED
1d30 15:25:47 MAIN: Registry: CLEANUP OF SWITCH FILE IF STARTUP FAILS, IS OFF
1d30 15:25:47 MAIN: Registry: ListenerFilter set to all
1d30 15:25:47 MAIN: Registry: PURGE SWITCH ON ERROR IS OFF
1d30 15:25:47 MAIN: Registry: NOTIFY REROUTES TO MDT IS OFF
1d30 15:25:47 MAIN: Registry: MAXIMUM NUMBER OF RETRY ATTEMPTS IS 4294967295
1d30 15:25:47 MAIN: Registry: UNLOCK NODE ON ANY INBOUND OFF
1d30 15:25:47 MAIN: Registry: PURGE MESSAGES ON SIGNOFF OFF
1d30 15:25:47 MAIN: Registry: NO AUTHORIZE ON STARTUP ON
1d30 15:25:47 MAIN: Registry: MAX USERS PER CHAT GROUP 10
1d30 15:25:47 MAIN: Registry: MAX PENDING COMMANDS PER UNIT 200
1d30 15:25:47 MAIN: Registry: OMS CONFIG NAME (Only pertinent to UTILITY customers): oms
1d30 15:25:47 MAIN: Registry: OMS INTITIALIZE ROUTER NETWORK(Only pertinent to UTILITY customers): 1
1d30 15:25:47 MAIN: Registry: IOM READ SYNC (Milliseconds) 0
1d30 15:25:47 MAIN: Registry: PERFORMANCE LOG THRESHOLD (Seconds) 0
1d30 15:25:47 MAIN: Registry: SUPPORT MULTIPLE DEVICES OFF
1d30 15:25:47 MAIN: Registry: MAX AUXILIARY DEVICES PER USER 10
1d30 15:25:47 MAIN: Registry: REMOVE UNIT FROM GROUP 0
1d30 15:25:47 MAIN: Registry: QUICK BOOT OFF
1d30 15:25:47 MAIN: Registry: PROCESS ALL PACKETS OFF
1d30 15:25:47 MAIN: Registry: PROCESS UNITS BY CONFIGURATION NAME OFF
1d30 15:25:47 MAIN: Registry: Report\Apc not found; Requests will be written to MESSAGE SWTICH
1d30 15:25:47 MAIN: Registry: Report\FormatPath set to E:\Program Files\Intergraph\Imdt\mobiletcoms\rptformats
1d30 15:25:47 MAIN: Registry: Report\OutputPath set to c:\temp
1d30 15:25:47 MAIN: Registry: CycleTime set to 1000
1d30 15:25:47 MAIN: Registry: RepeatCycle set to 1
1d30 15:25:47 MAIN: Registry: POST REPORT RESULTS TO SWITCH ON
1d30 15:25:47 MAIN: SICInterfaceApp::Initialize
1d30 15:25:47 MAIN: IUCInterfaceApp::OpenRegistry - bSuccess = 0
1d30 15:25:47 MAIN: SICInterfaceApp::LoadFromRegistry - Not opening registry at this level - no reg items to read
[] 11-17-16 15:25:47 - CLLogonNetwork: GetCurrentProcessId 8468
[] 11-17-16 15:25:47 - CLLogonNetwork: GetCurrentProcessId 8468
1d30 15:25:47 MAIN: CEci::ECIinit: eci com version 9.2.0.5
1d30 15:25:47 MAIN: RADOInitEx threadingModel 0x2
[] 11-17-16 15:25:47 - CLLogonNetwork: GetCurrentProcessId 8468

Point your RSS reader here for a feed of the latest messages in this topic
RE: MDTSVR Not Starting Every time
Posted on Dec 16, 2016 in response to: rglenn
 
   
 

Hi Developers are You home.  Could use your help please.

 

Bueller Bueller.

 

Still happening on a consisten basis in our stage environment. Can we install a debug copy of MDSTVR and trobuleshoot.

 

thanks,

rose

RE: MDTSVR Not Starting Every time
Posted on Dec 16, 2016 in response to: rglenn
 
   
 

Adding some more information.  When MDTSVR does start correctly we start to see the following message repeated over and over in the mdtsvr log .

wwwfdomst01 is the server where Mdtsvr is rnning on.

3e0 14:48:34 CL: CMdtsvrApp::OnListenerRead: Entering
3e0 14:48:34 CL: CMdtsvrApp::CImpIMdtApplication::GetUnitIdFromPacket: Packet Type not supported; Packet Type = 10044
3e0 14:48:34 CL: Can't get Unit Id from command message; Msg Type = 10044)
3e0 14:48:34 CL: CMdtsvrApp::OnListenerRead: Leaving; bRet = 1
3e0 14:48:36 CL: SICInterfaceApp::ListenerRead: Qtype <  1> Subtype <10044> #29218 From <wwwfdomst01>
3e0 14:48:36 CL: Unknown CAD MSG Type (10044).
3e0 14:48:36 CL: CMdtsvrApp::OnListenerRead: Entering
3e0 14:48:36 CL: CMdtsvrApp::CImpIMdtApplication::GetUnitIdFromPacket: Packet Type not supported; Packet Type = 10044
3e0 14:48:36 CL: Can't get Unit Id from command message; Msg Type = 10044)
3e0 14:48:36 CL: CMdtsvrApp::OnListenerRead: Leaving; bRet = 1
3e0 14:48:37 CL: SICInterfaceApp::ListenerRead: Qtype <  1> Subtype <10044> #29219 From <wwwfdomst01>
3e0 14:48:37 CL: Unknown CAD MSG Type (10044).
3e0 14:48:37 CL: CMdtsvrApp::OnListenerRead: Entering

RE: MDTSVR Not Starting Every time
Posted on Dec 20, 2016 in response to: rglenn
 
   
 

Hi,

Can you attach your mdtsvr log. we didn't see any exit statement in your message. 

I think you are in inservice 9.2 (as per the message above)

-Mahesh

RE: MDTSVR Not Starting Every time
Posted on Jan 4, 2017 in response to: umkalepa
 
   
 

Hi, Mahesh,

 

Attached is out latest log from our stage environment

What are you looking at is we restared the mobile services. Clean start log and this is after a few days of the services bing up and not being used.

Rick mears also has additioanl videos, log and proc dump files.

 

Thank you for taking a look at this.

rose

MDTSVR01042017.LOG

Add a Comment

Please sign in on the right menu to comment.  If you do not have an account, please Join now.