Sumeet.Kolge Please update Error log which will help Dev team to identify root cause easily.

Hi Rakesh Roy,

Checked and discussed this issue, no error log is generated. Thanks!

---------------------------------------
CC: Mandar Kulkarni, Satya, Hrishikesh Deshpande, Sachin Hingole, Prasad Patil

Harshada Borole
Please take this on priority.

Prasanna Karlekar
Nidhi.

Below are the 3C's:
Concern:
Error while processing reports.

Cause:
On Report server, for this company's datasource, incorrect connection string was stored.
Due to this, dataset error was appearing.

Correction:
Have deleted the old datasource and new one is created with connection string referring to this company on Pre-prod environment.

Harshada Borole
Why is this still showing in development?

Prasanna Karlekar
Thanks,
Nidhi.

Hi Nidhi Kaul,

We will make this LB deployed after we scan data on Pre Prod for incorrect connection string.
You can expect this to be done no latter than 28-Dec-2017.

Thank you!

cc: Harshada Borole

Okay. I thought the status to be incorrect since this is assigned to Sumeet. But if you are working on this, why is it assigned to Sumeet?

Please update the dev due date as well

Hi Nidhi Kaul,

While discussing this issue, we had discussed following 2 points:
1. Scan data to check the discrepancy between company ID and connection string. - Complete
We scanned report server data for already created reports in Pre Production environment. There were following 5 companies for which reports are created :

All of them have proper connection string defined. No issues for existing data.

2. To check, if anytime Online enrollment connection string is getting created from code. - Root cause found. Code fix pending.
Thank you! for asking us to check this. We did found a scenario when Online Enrollment connection string can get created while executing a company level report. We will be fixing this issue. Have extended dev due date to 02-Jan-2017.

[~parmeshwar.jumbade] -
Please take this on priority tomorrow 28-Dec-2017.

Thank you!

That's a good news that we got the root cause. As long as issue is fixed for now, we should be okay to extend the date.

Thanks,
Nidhi.

3Cs:
Concern: Error while processing reports
Cause: When we execute standard system utilization report as first report for a company, connection string with OnlineEnrollment was getting created for respective company's datasource. This issue was only when, system utilization was the first report to be executed for a company. No other report had such issue.
Correction: Now we have removed code which was used to generate report datasource with Online Enrollment connection string for company level report. Due to this it will create datasource with company specific connection string for standard/dynamic reports.

Affected Files: App\BusinessLogic\Reports\RDLGenerator.vb

Affected Areas: Reports (All types and All levels)

Tested Scenarios:
1. Verified multiple types of report and it's datasource
2. Verified company level, Global level reports

CC: Prasanna Karlekar Gaurav Sodani

Environment: Codemap
Company: or QA Kindercare for hspl
Login: Partner

Reports are checked for the serevr error. No server error found during testing. So, making jira ready for Pre-pro.

Sachin Hingole Hrishikesh Deshpande

Testing done on Codemap.

Verified all report on Random basis. Report working as expected.