Change name of report builder server to fqdn (now netbios)?

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.

April 16th, 2015 6:07am

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

Free Windows Admin Tool Kit Click here and download it now
April 16th, 2015 6:53am

Thanks but that's for SQL 2010, don't find these options in 2008.
Are you sure, we're talking about the same thing? Current http://netbios/reports should be httpS://fqdn/reports
April 16th, 2015 7:37am

No that is all version of SQL since 2005 (at least)
Free Windows Admin Tool Kit Click here and download it now
April 16th, 2015 8:32am

Ok, I'm not an SQL guy and totally lost now. The article doesn't help me.

Please advise.

April 24th, 2015 4:50am

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.

Free Windows Admin Tool Kit Click here and download it now
April 24th, 2015 6:14am

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.
April 24th, 2015 7:40am

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.

Free Windows Admin Tool Kit Click here and download it now
April 24th, 2015 7:57am

Thanks, but how can I make the certificate work in my case?
To clarify: please see screenshot in my post above.
April 27th, 2015 5:11am

Go to SQL Reporting Server Configuration Manager and change the Reporting Manager URL and Web Service URL from netbios name to FQDN. This way you can change the Reporting URL being used by SCCM which you can validate through the screenshot you have attached with this thread. 
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2015 6:00am

Well, actually, that's my question. Howto do that. There is not option for that.
April 27th, 2015 6:13am

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.

Free Windows Admin Tool Kit Click here and download it now
April 28th, 2015 3:36am

Thanks, but identification is on ip address, didn't want to change that. So I could change that to host header without any further impact?
April 28th, 2015 3:44am

It does work but now SCCM cannot connect to the reporting server (!)
Free Windows Admin Tool Kit Click here and download it now
April 28th, 2015 4:25am

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.

https://social.technet.microsoft.com/Forums/en-US/add3e017-6166-4443-b9f2-9898e4e0c843/report-builder-unable-to-connect-to-data-source

 
April 28th, 2015 5:14am

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.

Free Windows Admin Tool Kit Click here and download it now
July 25th, 2015 10:28am

No, actually never did. Workaround was to login directly on the SQL Reporting server and create reports there.
July 25th, 2015 2:15pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics