Uploaded image for project: 'Workterra BenAdmin'
  1. Workterra BenAdmin
  2. WB-281

Server error on Employee plan eligibility report

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Bug Fixed
    • Labels:
    • Environment:
      Stage
    • Categories:
      Report
    • Company:
      Softchoice
    • Reported by:
      Support
    • Level:
      Admin

      Description

      ErrorID : 0
      ErrorSource : ControllerAppTier.SaveAndGetData->BenAdminControllerAppTier.SaveAndGetData->StaticReports.SaveAndGetData->AdminUser.GetData->EligibilityReason.FetchEmployeePlanEligibility->EligibilityReason.FetchEligibleEmployeeForReport
      ErrorMessage: Invalid object name 'AdminUserClass1'.
      StackTrace: at WORKTERRA.BenAdmin.BenAdminControllerAppTier.SaveAndGetData(BenAdminControllerWebTierEntity objBenAdminControllerWebTierEntity)

        Attachments

          Issue Links

            Activity

            Hide
            prasanna Prasanna Karlekar (Inactive) added a comment -

            We will be taking this in Sprint-41 starting from 6-Nov-2017.

            Thank you!

            cc: Gaurav Sodani

            Show
            prasanna Prasanna Karlekar (Inactive) added a comment - We will be taking this in Sprint-41 starting from 6-Nov-2017. Thank you! cc: Gaurav Sodani
            Hide
            prasanna Prasanna Karlekar (Inactive) added a comment -

            We will be working on this issue in Sprint-40, starting from 23-Oct-2017.

            Thank you!

            cc: Gaurav Sodani

            Show
            prasanna Prasanna Karlekar (Inactive) added a comment - We will be working on this issue in Sprint-40, starting from 23-Oct-2017. Thank you! cc: Gaurav Sodani
            Hide
            harshada.borole Harshada Borole (Inactive) added a comment -

            Below are the 3C's:

            Concern:- Server error on Employee plan eligibility report
            Cause:- Incorrect database connection string was formed.
            Connection string was pointing to OnlineEnrollment database instead of Company database.
            Database query for Company Admin included 'AdminUserClass' tables. These tables are present in Company DB. The query was getting executed in OnlineEnrollment and could not find 'AdminUserClass' tables.
            Correction:- Corrected the connection string, pointing to Company Database

            Files affected:-
            EligibilityReason.vb

            Affected Area:-
            Employee Plan Eligibility Report.

            Tested Scenario's:- Tested for Admin login and Company Admin.

            Show
            harshada.borole Harshada Borole (Inactive) added a comment - Below are the 3C's: Concern:- Server error on Employee plan eligibility report Cause:- Incorrect database connection string was formed. Connection string was pointing to OnlineEnrollment database instead of Company database. Database query for Company Admin included 'AdminUserClass' tables. These tables are present in Company DB. The query was getting executed in OnlineEnrollment and could not find 'AdminUserClass' tables. Correction:- Corrected the connection string, pointing to Company Database Files affected:- EligibilityReason.vb Affected Area:- Employee Plan Eligibility Report. Tested Scenario's:- Tested for Admin login and Company Admin.
            Hide
            meghana.joshi Meghana Joshi (Inactive) added a comment -

            Verified above issue on LB through Admin and Partner Login with combination of Some Classes , Some Benefit Type and Plan and All Classes , All Benefit Types.

            Working Fine

            CC - Sachin Hingole

            Show
            meghana.joshi Meghana Joshi (Inactive) added a comment - Verified above issue on LB through Admin and Partner Login with combination of Some Classes , Some Benefit Type and Plan and All Classes , All Benefit Types. Working Fine CC - Sachin Hingole
            Hide
            nidhi.kaul Nidhi Kaul (Inactive) added a comment -

            Harshada Borole
            IS this fixed in new UI as well?

            Show
            nidhi.kaul Nidhi Kaul (Inactive) added a comment - Harshada Borole IS this fixed in new UI as well?
            Hide
            harshada.borole Harshada Borole (Inactive) added a comment -

            Hi Nidhi Kaul,

            We haven't deployed the changes in new UI as it is on LB Hold.
            We will deploy it once it is ready for stage.

            cc: Jyoti Agrawal,Prasanna Karlekar

            Show
            harshada.borole Harshada Borole (Inactive) added a comment - Hi Nidhi Kaul , We haven't deployed the changes in new UI as it is on LB Hold. We will deploy it once it is ready for stage. cc: Jyoti Agrawal , Prasanna Karlekar
            Hide
            nidhi.kaul Nidhi Kaul (Inactive) added a comment -

            Rakesh Roy
            I guess this issue was raised by UAT group while testing UI refresh. Shouldn't it be created in NF?

            Nidhi.

            Show
            nidhi.kaul Nidhi Kaul (Inactive) added a comment - Rakesh Roy I guess this issue was raised by UAT group while testing UI refresh. Shouldn't it be created in NF? Nidhi.
            Hide
            rakeshr Rakesh Roy (Inactive) added a comment - - edited

            Nidhi Kaul This issue was on stage as well, that's why created WT ticket.

            Show
            rakeshr Rakesh Roy (Inactive) added a comment - - edited Nidhi Kaul This issue was on stage as well, that's why created WT ticket.
            Hide
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment -

            This is fixed on production.

            Show
            hrishikesh.deshpande Hrishikesh Deshpande (Inactive) added a comment - This is fixed on production.

              People

              Assignee:
              rashmita.dudhe Rashmita Dudhe (Inactive)
              Reporter:
              rakeshr Rakesh Roy (Inactive)
              Developer:
              Harshada Borole (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Dev Due Date:
                Pre-Prod Due Date:

                  Time Tracking

                  Estimated:
                  Original Estimate - 21h
                  21h
                  Remaining:
                  Time Spent - 10.25h Remaining Estimate - 10.75h
                  10.75h
                  Logged:
                  Time Spent - 10.25h Remaining Estimate - 10.75h
                  10.25h