The LLU search number section of the Portal is returning a Service error::WO0000000021653
MINOR Closed TTB-Outages
STATUS
Closed
CREATED
Feb 16, 10:20 AM (6¼ years ago)
TYPE
TalkTalk Outage
STARTED
Feb 16, 10:12 AM (6¼ years ago)
CLOSED
Feb 16, 04:50 PM (6¼ years ago)
REFERENCE
28112 / 12363635
INFORMATION
  • INITIAL
    6¼ years ago

    It has been reported by SMC at Soapworks and Partners that the main LLU number search in the Portal is returning an error (Service Error occurred while performing search). This is the main LLU search in the Products & Services section used by TalkTalk Assurance teams and Partners for checking line details, diverts, Sonus information and other diagnostics like TAM tests.
    Ân/a
                              

  • UPDATE
    6¼ years ago

    MIM has scheduled a technical bridge between CGI MIM, CGI OSS Support and Business Applications that is in progress. DBA resource is also being engaged to assist with root cause and permanent fix. Further updates will follow. Â

  • UPDATE
    6¼ years ago

    OSS Support and Business Applications team have reviewed the Portal logs and found that calls from G6 webservices to DB37 are failing to a "Could not open connection to SQL server " error. Logs have been shared with the SQL DBA team for further analysis into the cause of the connection errors. A further update will be provided by 13:00. Â

  • UPDATE
    6¼ years ago

    SQL DBA team have confirmed connectivity to DB37 is available across all four G6 servers. OSS Delivery team have been engaged to confirm the specific stored procedure that is calling the database. Once identified DBA team will run a SQL profiler to identify any errors being returned from the execute commands. A further updated will be provided by 15:15 Â

  • RESOLUTION
    6¼ years ago

    It was reported by the SMC and TTB Partners that the LLU number search with Products & Services in the Portal application (portal.talktalkplc.com) were returning an "Service Error occurred while performing search" for 100% of searches as of approx. 09:30. Following investigations by Business Application, DBA, OSS Support and Delivery teams, linked server connectivity issues between DB37 and DB58 were identified as the cause of this outage. Whilst investigations into the fix were on-going with the DBA team, service was restored without any manual intervention at approx. 15:00. This incident will now be closed with root cause analysis being completed via our Problem Management team. Â

  • Closed