Paginated Reports not running on Service

[c_schrotberger]

Just like the error that occured 12/8 for fabric customers with Tenants located in the Central US region where there were issues access the service, this error continues to happen on all paginated reports.  Here is a copy of the error.  

There was an error when attempting to create a new session
Could not connect to the server. Please check your network settings and try again later.
Timestamp: 2025-12-09T14:38:36.901Z
Root activity ID: c40e8e22-176d-e49a-acdf-45b6153048b1
Session ID:
Tenant ID: 61cac203-836b-4c0b-897e-21d01836367f
Cluster: https://61cac203836b4c0b897e21d01836367f-api.analysis.windows.net/
Report ID: 3d2d6255-bea0-44a9-a4f8-2ac4d5549dea
Capacity ID: undefined
ReportViewerVersion: 2025.11.3.1953

[d_m_LNK · Accepted solution]

In further digging on our end this was a CORS detection issue in the browser -- turning off CORS detection allowed the report to render succesfully -- in our case our org will be pushing out a group policy fix to correct this issue.  

We were getting repeated errors like this in the browser when turning on developer mode: 

[stringtype · Accepted solution]

I did my best to explain the situation here as well as the various ways to fix it. @c_schrotberger, try pinging the hostname that you're failing to connect to. What IP range is it in? Is it something like 100.64.*.*?

[c_schrotberger]

Thanks @stringtype .  We did figure out that it was an issue with our group policy that our engineers are working on fixing.  It impacted Org Apps as well.  

[c_schrotberger]

Hello!  Thanks @bradsy Our company does not use ZScaler. We're looking at things on our side as well.  

[MSDS_Caitie]

 This has been happening for days and we're having to manually run the paginated reports on desktop to get critical reports to users.

[d_m_LNK]

Experiencing this as well if anyone has any insight.

[bradsy]

Hi folks,

I am not sure it is the same issue, but there was a release of Chromium last week that appears to interact differently with ZScaler cloud security service. If you have latest chrome or edge and your network security includes ZScaler, you can try a temporary work around until your network security team can figure out a long term solution.

In Edge, type edge://flags for your url. This will bring up flags you can turn off or on. They search for 'Network Access'. Network access checks will show up. Our understanding is if you disable this flag, then things should start to work again. This is a temporary workaround, your network security team will need a long term solution.

Please post if this works.

[d_m_LNK · Accepted solution]

In further digging on our end this was a CORS detection issue in the browser -- turning off CORS detection allowed the report to render succesfully -- in our case our org will be pushing out a group policy fix to correct this issue.  

We were getting repeated errors like this in the browser when turning on developer mode: