Cant Upload RDL File to SSRS 2016
-
I've wasted half a day trying to figure out a solution for this issue.
We just stood up a SSRS 2016 server. Everything looks great. We're able to access the site with the URL we created. I can set the permissions and create folders.
However, when I wanted to test out a simple RDL file, which only has a text box, it fails to upload. I get the famous "an error has occurred. Something went wrong. Please try again later."
Just for giggles, I uploaded a simple image file and boom, it uploaded just fine. NO errors whatsoever. But when I go back and try to upload an RDL file, that's when I get the error.
The way I'm trying to upload the RDL file is by going to the web portal and then clicking on the big UPLOAD button. Then I browse to my file and then Open to start the upload. Again, error appears. Not only can I not upload an RDL file, but I cant even create a new Data Source from the web portal. I get the same error. Permissions is not an issue since I'm using an admin account.
Like I said, I've been searching and searching but nothing.
Hoping someone here has experienced this issue and resolved it.
Thanks guys!
- DarthBurrito - Tuesday, October 16, 2018 3:06 PM
That useless error message is often due to configuration issues.
What was in the Reporting Services logs when you got the errors when uploading the rdl, creating a new data source, etc.? That should have more detail related to the issue.Sue
-
This issue happened to me in a dev environment some time ago, for me it was an authentication issue.
first of all, verify you have windows authentication installed on your IIS components:
Second: Open your rsreportserver.config file (located in your installation directory), also make a backup of the file before changing anything, then, locate the <Authentication> tag, and inside it, add the following code if not present already:
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>the final code should look like this:
<Authentication>
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>
<RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel>
<RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
after restarting the service you should be able to add the reports,If this does not solve your issue, check also the web.config file in the same folder, and inside the <system.web> tag, you should see the following code, if not there, add it:
<authentication mode="Windows" />
<identity impersonate="true" />
restart the service and you should be good to go.that must solve your issue, if it persist, then is not related to windows authentication.
MCSE, MCSA SQL Server Database Developer/Administrator
- epivaral - Wednesday, October 17, 2018 3:41 PMThis issue happened to me in a dev environment some time ago, for me it was an authentication issue.
first of all, verify you have windows authentication installed on your IIS components:Second: Open your rsreportserver.config file (located in your installation directory), also make a backup of the file before changing anything, then, locate the <Authentication> tag, and inside it, add the following code if not present already:
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>the final code should look like this:
<Authentication>
<AuthenticationTypes>
<RSWindowsNTLM/>
</AuthenticationTypes>
<RSWindowsExtendedProtectionLevel>Off</RSWindowsExtendedProtectionLevel>
<RSWindowsExtendedProtectionScenario>Proxy</RSWindowsExtendedProtectionScenario>
<EnableAuthPersistence>true</EnableAuthPersistence>
</Authentication>
after restarting the service you should be able to add the reports,If this does not solve your issue, check also the web.config file in the same folder, and inside the <system.web> tag, you should see the following code, if not there, add it:
<authentication mode="Windows" />
<identity impersonate="true" />
restart the service and you should be good to go.that must solve your issue, if it persist, then is not related to windows authentication.
Beginning with SQL Server 2008, Reporting Services uses http.sys rather than using IIS.
Sue
-
Well, that is how i solved it in a windows 2012 with sql 2016 maybe i did extra steps...
MCSE, MCSA SQL Server Database Developer/Administrator
- epivaral - Wednesday, October 17, 2018 4:28 PM
Hopefully, you didn't install IIS on that server for Reporting Services as it wasn't needed.
If you changed the report server config, you may have had authentication set to negotiate and were having kerberos. Nonetheless, there should be more information in the log files and you'd probably want to check those errors before making any changes. Or adding IIS.Sue
-
Everyone, thanks for your input. I tried the IIS solution, but unfortunately, that did not work for me. However, I did get it working and here's what I did.
SSRS Instance #1 - This instance was not working properly. I'm able to create folders and add upload images, but I was not able to upload RDL files nor was I able to create a Data Source. I tried the IIS solution, but nothing. Since this is not working, I'm going to remove this instance.
SSRS Instance #2 - I created an entire new instance of SSRS. Here are my settings.
- Service Account - Used built-in account called Virtual Service Account. (I will update this later with a proper service account, but for now since I have the environment working, I'm leaving it as is.)
- Web Service URL - Left at default settings
- Database - I created a new SSRS report database.
- Web Portal - Left default
- Everything else after Web Portal was left at default.
I did make a backup key just in case. Since this is my DEV environment, I'm not in a rush to change the service accounts.Now I'm able to upload RDL files using the Upload button and create a Data Source.
-
I'm back again. So my second SSRS instance bombed on me also. It must be a permissions issue because when I went back into SSRS Config Manager and added the service account, it bombed out when I tried to upload a report and create a Data Source.
So now I'm on my third SSRS instance and this time, I did not enter any service account info. I'm leaving everything as NT Service. Since this is dev, it's not a huge deal. Leaving everything as default, I'm back in business again and able to upload RDL files and create a Data Source. - DarthBurrito - Thursday, October 18, 2018 1:24 PM
Did you by any chance save the Reporting Services log files? Those are probably the single most valuable tool in troubleshooting SSRS.
Eventually you'll need to figure out where things are going wrong.Sue
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply