75,730
I just tried to install SQL 2017 for the first time using the version downloaded in PartnerSource. They have separated out the SSRS installation to it own installation package. This package asks for a product ID. When I enter what is provided for SQL it does not work. How do I obtain a valid SSRS product ID?
*This post is locked for comments
The images are for different languages, from what I could see, so I used the English one.
Just copy the registration keys that gets populated into the SQL 2017 install, then use that same key to enter when you're installing Reporting Services, because it doesn't automatically populate when you install SSRS from the image.
Thanks
I install SQL 2017 with SSRS onto brand new image to test and the same PID worked for both. I will try again on the client's server to see if perhaps they were doing something slightly different than I normally do. By the way, for your SQL 2017 installations which of these options would you check? There are several new ones for SQL 2017 and if any of them are useful for GP I would want to include them.
Ok, I installed SQL 2017 using the download you mentioned and see that Reporting Services is now a separate install, for whatever reason.
If you copy the key that was populated when you installed the initial SQL Server 2017 Standard Runtime, you can use it when you install SQL 2017 Reporting Services as well.
docs.microsoft.com/.../find-reporting-services-product-key-ssrs
Let me know if this doesn't work for you. I tested it and it worked for me when I did it.
Thanks
Thank you
Here is the link. The install media has many changes. They had already separated out Management Studio now they have separated out SSRS as well.
Do you have the link on Partnersource for the SQL 2017 / Reporting Services you're installing? Just so I'm testing the exact same thing.
Thanks
Thanks Derek, I was just taken aback yesterday when first I discovered that SSRS was a separate installation and then when the PID did not work we immediately put the brakes on the test upgrade. Please keep us posted.
You're correct in that SQL 2017 is being tested for compatibility with Dynamics GP 2018, which is why you can actually run GP 2018 Utilities on SQL 2017 without getting a version error, but until it's actually on the System Requirements page, it is technically not a supported environment.
I haven't had a chance to look at SSRS and SQL 2017 but I'll make a note to do so and update this if I find anything out as well.
Thanks
Derek, I have information from a very well placed Microsoft contact that SQL 2017 is about to be added to the requirements page. We now have the problem where the PID for SQL does not work with the separate install media of SSRS. Looks like another one of the consequences of someone at Microsoft not thinking this all the way through. I will let everyone know what I find out.
Along with this Dynamics GP forum, this may also be a question to put into a SQL Server / Reporting Services forum as well.
I also wanted to mention that currently, SQL Server 2017 is not compatible nor supported with any version of Dynamics GP, including GP 2018.
Thanks
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (