Unable to Create a New Scheduled Refresh

[gbosman]

Hi Everyone

I am using the May 2021 15.0.1106.169 version (Latest) of Power BI Report Server. When I try to create a new scheduled refresh for any report on the server, I get the following error:

"An error has occured. Something went wrong. Please try again later."

The page will then get stuck with the  "Loading" message showing

Has anyone experienced this before or started experiencing this after updating to the latest version?

[Icey]

Hi @gbosman ,

It works well on my side. Please refer to @FarhanAhmed's suggestion and try it again.😊 Hope it works for you.

Best Regards,

Icey

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[gbosman]

Thanks for replying @FarhanAhmed and @Icey 

We did some more investigating and it looks like the issue might be part of a bigger issue. At the moment our server hosts two Report Servers one using TCP (HTTP) and one using SSL (HTTPS). We are able to connect to both Report Servers and browse the files, but when try to connect to the locals hosts it gives us an error. 

HTTP Server URL:
http://[servername]/Reports/browse (Working)

http://[servername]/Reportserver (Not Working)

HTTPS Server URL:

https://[servername]/Reports/browse (Working)

https://[servername]/Reportserver (Not Working)

When we try to access the localhosts we get the following error:
"HTTP Error 503. The service is unavailable"

Troubleshooting inculdes (Normal Error 503 steps has been tested):
* Updating all accosiated account credentials

* Checking and restarting of accosiated services

* Add and re-adding of Web Services via Repport Server Config Manager
* Comparing URL Reservations to that of our Production Report Servers

* Add and re-adding of URL Reservations

The only option we have not done is the re-install as suggested. We would want to find out if there is another way for resolution before taking the re-install route.

[FarhanAhmed]

You probably need to re-install the PBIRS again.

We encountered this issue once, we did reinstallation and it worked well for us.

We did our little investigation of why this happened and we realized that we updated the server without stopping services which somehow causes issues. But after that we did multiple upgrades using the strategy of stopping the services and update the PBIRS and haven't encountered this issue again {or as of now 🙂 }