January 27, 2017 at 8:37 am
When I try to access SSRS URL externally or from any other server it gives error:
Could not load contents.
Something went wrong.Please try again later.
But it works fine while accessing URL from the server where Reporting Service is installed.
No errors are logged in the log files or in event viewer.
FYI: It is SQL Server 2016 SP1.
January 27, 2017 at 8:49 am
PJ_SQL - Friday, January 27, 2017 8:37 AMWhen I try to access SSRS URL externally or from any other server it gives error:
Could not load contents.
Something went wrong.Please try again later.But it works fine while accessing URL from the server where Reporting Service is installed.
No errors are logged in the log files or in event viewer.
FYI: It is SQL Server 2016 SP1.
DNS issue? Can you ping the SSRS server (by name) from the computers on which the URL does not work?
John
January 27, 2017 at 8:54 am
John Mitchell-245523 - Friday, January 27, 2017 8:49 AMPJ_SQL - Friday, January 27, 2017 8:37 AMWhen I try to access SSRS URL externally or from any other server it gives error:
Could not load contents.
Something went wrong.Please try again later.But it works fine while accessing URL from the server where Reporting Service is installed.
No errors are logged in the log files or in event viewer.
FYI: It is SQL Server 2016 SP1.DNS issue? Can you ping the SSRS server (by name) from the computers on which the URL does not work?
John
Yes , I can.
I don't get the error all the time, it is sporadic.
January 27, 2017 at 9:00 am
PJ_SQL - Friday, January 27, 2017 8:54 AMYes , I can.
I don't get the error all the time, it is sporadic.
Are you sure it works fine on the server - do you try it as often as you do remotely? If it does, then it's probably something between the server and the client. You may need to ask your network admin to look for dropped packets and other such phenomena that stop networks from working properly.
John
January 27, 2017 at 9:12 am
I've been having a Google of the problem, which discusses that the issue is due to having a timezone of greater than UTC +00:00, however, this was "resolved" in CU1, which SP1 includes. This also, however, states that it does log an error in the Reporting Service log along the lines of:
Microsoft.ReportingServices.Portal.WebHost_MM_DD_YYYY_HH_MM_SS.log: OData exception occurred: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentOutOfRangeException: The UTC time represented when the offset is applied must be between year 0 and 10,000.
Are you on a timezone or UTC +01:00 or more?
Although this might not be the problem, I would be very surprised that nothing is in the log. SSRS does a lot of logging, so I would expect to see something there.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 27, 2017 at 10:22 am
Thom A - Friday, January 27, 2017 9:12 AMI've been having a Google of the problem, which discusses that the issue is due to having a timezone of greater than UTC +00:00, however, this was "resolved" in CU1, which SP1 includes. This also, however, states that it does log an error in the Reporting Service log along the lines of:
Microsoft.ReportingServices.Portal.WebHost_MM_DD_YYYY_HH_MM_SS.log: OData exception occurred: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.ArgumentOutOfRangeException: The UTC time represented when the offset is applied must be between year 0 and 10,000.Are you on a timezone or UTC +01:00 or more?
Although this might not be the problem, I would be very surprised that nothing is in the log. SSRS does a lot of logging, so I would expect to see something there.
Yes , we are in (UTC-06:00) Central Time (US & Canada).
And we already have SP1.
The report server logs doesn't provide any information regarding the error.
January 30, 2017 at 10:18 pm
This was removed by the editor as SPAM
January 31, 2017 at 4:19 am
John Mitchell-245523 - Friday, January 27, 2017 9:00 AMPJ_SQL - Friday, January 27, 2017 8:54 AMYes , I can.
I don't get the error all the time, it is sporadic.Are you sure it works fine on the server - do you try it as often as you do remotely? If it does, then it's probably something between the server and the client. You may need to ask your network admin to look for dropped packets and other such phenomena that stop networks from working properly.
John
Look in the SSRS CONFIG files as well. Maybe there are timeouts preventing execution past a certain threshold.
Have you look in the ExecutionLogs in the Report Server database to see if the working times exceed These thresholds?
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply