Hi,
We need to change the name of the report builder from netbios to fqdn (now it is http://reportbuilder/reports it should be https://reportbuilder.domain.com).
Due to the shortname we have issues building reports (error os exactly the same as this http://ammarhasayen.com/2015/02/25/configuration-manager-2012-r2-reporting-services-and-ssl-trusting-and-binding-issues/ but root cause is that SSL is linked to fqdn not
netbios name.
Please advise howto change.
Did you know that you can create your own data source and use that. When you upload the RDL you can then change the DS to the CM12 DS?
http://www.enhansoft.com/blog/how-to-upload-a-ssrs-report-and-change-its-data-source
Are you sure, we're talking about the same thing? Current http://netbios/reports should be httpS://fqdn/reports
Ok, I'm not an SQL guy and totally lost now. The article doesn't help me.
Please advise.
You don't need to change the name to the fqdn, to create reports. That was the whole point of my reply.
I don't understand your statement about not being a SQL guy, if you are editing reports.
Not an sql guy, we have sql guys but I'm trying to figure it out myself and learning howto built those reports.
Thanks but that option is not valid to me. It should work without any wokaround.
Not an sql guy, we have sql guys but I'm trying to figure it out myself and learning howto built those reports.
What I'm suggestion IS NOT a workaround, it is native to both CM12 and SSRS.
To clarify: please see screenshot in my post above.
Open Reporting Server Configuration Manager. Click on "Web Service URL" option. Click on Advanced and Change the host name.
Repeat the same process for "Report Manager URL". The URL will then change to the FQDN from netbios.
Added the host header as an extra entry (besides the ip address) and that works. However, didn't solve my problem. Found this but didn't work for me either.
Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?
Since no one has answer this post, I recommend opening a support case with Microsoft Customer Support Services (CSS) as they can work with you to solve this problem.