Forum Discussion
Smartsheet Connector - anyone else been having refresh issues within the last couple of weeks
- Anonymous2 years ago
Hi, RichardJ
According to your screenshot, when you plan to refresh Smartsheet, the refresh fails occasionally and a 500 error is reported. It can be seen from the successful refresh that there is no problem with the planned refresh you configured. According to the RFC2616 document, the reasons for the 500 error are as follows:
- If the server encounters an unexpected situation and cannot run normally, a 500 error will be reported.
- When the server acts as a gateway or proxy and does not receive a response from the specified upstream server in time or the DNS search times out, a 500 error will be returned.
- A 500 error may occur when the server is temporarily overloaded or undergoing maintenance. This is only a temporary situation and will be alleviated and restored later.
- There is a problem with the data source. If lines are added, the structure is changed, or certain necessary structures are deleted, a 500 error will be reported. I've provided links to posts with similar errors below.
I think that the 500 error you encountered is most likely caused by errors reported at points 3 and 4. Did you change the data source before refreshing? If not, then this is a temporary internal error of the server. Additionally, if you have other scheduled refreshes happening at the same time, it may overload the server.
Datasource 500 error URL: https://community.fabric.microsoft.com/t5/Desktop/DataSource-Error-Web-Contents-failed-to-get-data-from-500/m-p/392703
RFC2616 document: https://www.ietf.org/rfc/rfc2616.txt
If the above suggestions are helpful to you, that would be great.
How to Get Your Question Answered Quickly
If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi, RichardJ
According to your screenshot, when you plan to refresh Smartsheet, the refresh fails occasionally and a 500 error is reported. It can be seen from the successful refresh that there is no problem with the planned refresh you configured. According to the RFC2616 document, the reasons for the 500 error are as follows:
- If the server encounters an unexpected situation and cannot run normally, a 500 error will be reported.
- When the server acts as a gateway or proxy and does not receive a response from the specified upstream server in time or the DNS search times out, a 500 error will be returned.
- A 500 error may occur when the server is temporarily overloaded or undergoing maintenance. This is only a temporary situation and will be alleviated and restored later.
- There is a problem with the data source. If lines are added, the structure is changed, or certain necessary structures are deleted, a 500 error will be reported. I've provided links to posts with similar errors below.
I think that the 500 error you encountered is most likely caused by errors reported at points 3 and 4. Did you change the data source before refreshing? If not, then this is a temporary internal error of the server. Additionally, if you have other scheduled refreshes happening at the same time, it may overload the server.
Datasource 500 error URL: https://community.fabric.microsoft.com/t5/Desktop/DataSource-Error-Web-Contents-failed-to-get-data-from-500/m-p/392703
RFC2616 document: https://www.ietf.org/rfc/rfc2616.txt
If the above suggestions are helpful to you, that would be great.
How to Get Your Question Answered Quickly
If it does not help, please provide more details with your desired output and pbix file without privacy information (or some sample data) .
Best Regards
Jianpeng Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Anonymous Many thanks for the comprehensive response and the link to the RFC2616 document.
None of the data has changed so am confident this issue 3 in the list provided.
Hopefully it's only temporary and will improve.
Thanks,
Richard