FUJ00173185
FUJ00173185
Peak Incident Management System
Call Reference PC0276698 Call Logger _Customer Call_ -- EDSC
Release Reported In -- HNG-X Rel. Ind. Top Ref INC2186508
Call Type Live Incidents Priority D -- Internal
Contact EDSC Call Status Closed -- Administrative Response
Target Date 22/02/2019 Effort (Man Days) 0
Summary INC2186508 : The VB Application identified by the event source logged this Application
All References Type Value :
TFSNow INC2186508
Jira POA-2978
Collections Name User Date
-SSCAdm Chad Daborn 12-Feb-2019 15:50:58
Progress Narrative
pate:12-Feb-2019 15:42:05 User:_Customer Call_
CALL PCO276698 opened
Details entered are:-
summary: INC2186508 : The VB Application identified by the event source logged this Application
call Type:L
call Priority:
ffarget Release:HNG-X Rel. Ind.
routed to:EDSC - Unassigned_
22-Feb-2019 15:42:04 Uscr: Customer Call,
HNCIDENT MANAGEMENT
Date/Time Raised: Feb 12 2019 3:40PM
Priority: D
contact Name: POA SMC1
contact Phone:
originator: XXXXXX@TFSO1
wiginator's reference: INC2186508
product Serial No:
Product Site:
Service : NA I Platform : Audit Workstation 202, 204 & 206
served below critical alert in SSN V2:
} ‘The VB Application identified by the event source logged this Application AEClient: Thread
1046 Description: Unable to execute command with
7528 ,Logged: Error
Location: AEClientDLL.clsConnection.ExecCommandWithReturn 12/02/2019 15:03:14 1
The VB Application identified by the event source logged this Application AEClient: Thread ID: 8532 , Logged: Error
47467259 Description: [Microsoft] [ODBC SQL Server
unication link failure Location: AEClientDLL.clsRFIQueryRequest. 12/02/2019 15:02:56 2
“} The VB Application identified by the event source logged this Application AEClient: Thread ID: 4448 ,Logged: Error
147467259 Description: [Microsoft] [ODBC SQL Server
DriverICommunication link failure Location: AEClientDLL.clsRFIQueryRequest. 12/02/2019 15:02:56 1
The VB Application identified by the event source logged this Application AEClient: Thread ID: 9936 , Logged: Error
Jaumber: 91 Description: Object variable or With block variable not set Location: AEClientOCX. frmSetAuditPoints.Form Load
12/02/2019 15:33:22 1
KEL: jenningse3617N (related)
aller : POA SMC1
caller Contact :
onfiguration Item =
Locatior
jbate:12-Feb-2019 15:45:07 User:_Customer Call_
2/02/2019 15:44:10 ~ Subhasish Saha (Additional comments)
please advise.
Date:12-Feb-2019 15:51:42 User:Chad Daborn
[Start of Response]
le dont support the Audit machines, routing to to audit dev
[End of Response]
Response code to call type L as Category 40
Response was delivered to Consumer
Pending
Incident Under Investigation
FUJ00173185
FUJ00173185
12-Feb-2019 15:52:01 User:Chad Daborn
Product HNG-X Platforms -- Audit Workstation (AUW) (version unspecified) added.
jDate:12-Feb-2019 15:52:12 User:Ghad Daborn
Ithe Call record has been transferred Lo the team: Audit-Dev
Progress was delivered to Consumer
lbate:43-Feb-2019 13:15:27 User:Gerald Barnes
[fhe Call record has been assigned to the Team Member: Gerald Barnes
progress was delivered to Consumer
[Date:13-Feb-2019 15:40:34 User: Customer Call_
13/02/2019 15:39:30 - SiriTeja Kalagampudi (Additional comments)
lselow similar alerts observed.
mary Last Occurrence Count
The VB Application identified by the event source logged this Application AEClient: Thread ID: 11336 , Logge
=2147467259 Description: [Microsoft] [ODBC SQL Server Driver]Communication link failure Location:
sRFIQueryRequest 13/02/2019 15:26:52 2
The VB Application identified by the event source logged this Application AEClient: Thread ID: 8276 ,Logged: Error
2147467259 Description: [Microsoft] [ODBC SQL Server Driver]Communication link failure Location:
IAECLientDLL.clsRFIQueryRequest. 13/02/2019 15:26:47 1
IRRELI Error
Jaumber
bate:14-Mar-2019 1
[Start of Response]
there has been no report to me from the Prosecution Team about this issue and so it is most likely that the ARQ they were running
failed and when they reran it it succeeded. The errors logged are always put into the close log of the ARQ when the ARQ is
closed. I have had a look at all recent closed ARQ logs and this is a fairly common error. In fact 4% of ARQs looked at (out of
1503) had failed.
7:22 User:Gerald Barnes
so in conclusion it happens but the ARQs almost certainly work on rerun since otherwise the prosecution team would have raised a
PEAK themselves.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
lkesponse was delivered to Consumer
Hours spent since call received: 3 hours
Date: 29-Mar-2019 13:17:59 User: Customer Call_
29/03/2019 13:17:35 - Prakash Santappagari (Additional comments)
served similar critical alert in V2 :
The VB Application identified by the event source logged this Application AEClient: Thread ID: 6748 ,Logged
: -2147217900 Description: [Microsoft] [ODBC SQL Server Driver] [SQL ServerIIncorrect syntax near + Location:
JAEClientDLL.clsRFIQ 29/03/2019 12:19:12 1
[Date:01-May-2019 16:19:06 Uscr:Gerald Barnes
{Start of Response]
I got the incident described in "Date:12-Feb-2019 15:42:04 User: Customer Call_
in development.
jt just ran an audit query to return some files and it happened.
I reran the query from a clean start and it did not.
so it is an intermittent problem which does not occur consistently.
[End of Response]
Response code to call type L as Category 40 -- Pending -- Incident Under Investigation
Response was delivered to Consumer
Jbate:01-May-2019 16:27:18 User:Gerald Barnes
Reference Added: Jira POA-2978
bate:15-dul-2019 11:02:36 User:Aastha Mehrotra
Mehrotra, Aastha
Monday, July 15,
: Barnes, Gerald
: Malayil, HarishKumar <{_-
subject: PC0276698
[Prom
sent.
fr
2019 3:31 PM
$b; Guy, James _ _ b
ified by the event source logged this Application
INC218650
Hi Gerald,
Its there any update that can be recorded on this peak?
[thanks & Regards,
laastha Mehrotra
Project Coordinator
FUJ00173185
FUJ00173185
Date: 29-Nov-2019 12:44:39 User:Gerald Barnes
[Start of Response]
[this does not happen very often and is difficult to reproduce. There is a jira for it. Please close the issue.
[End of Response]
lkesponse code to call type L as Category 40
Response was delivered to Consumer
Incident Under Investigation
Pending
Date:29-Nov-2019 12:45:09 User:Gerald Barnes
fhe Call record has been transferred to the team: EDSC
Progress was delivered to Consumer
Date:29-Nov-2019 13:02:20 User:Mark Wright
[Start of Response]
[this does not happen very often and is difficult to reproduce. There is a jira for it. Please close the issue.
[End of Response]
response code to call type L as Category 68 -- Final -- Administrative Response
outing to Call Logger following Final Progress update.
Service Response was delivered to Consumer
Date:29-Nov-2019 13:02:20 User:Mark Wright
IcALL. PC0276698 closed: Category 68 Type L
jbate:29-Nov-2019 13:02:20 Uscr:Mark Wright
befect cause updated to 41 General - in Procedure
Root Cause General - in Procedure
Logger _Customer Call_ -- EDSC
Subject Product HNG-X Platforms -- Audit Workstation (AUW) (version unspecified)
Assignee _Customer Call_ -- EDSC
Last Progress 29-Nov-2019 13:02 -- Mark Wright