SSRS Subscriptions And Relay Setup - reporting-services

Good day,
I need advice on getting SSRS subscriptions working again at my clients
Scenario 1 - Client upgraded server from Server 2012 with SSRS 2012 to Server 2022 with SSRS 2019 - They use the relay function due to the issue with the Office 365
https://learn.microsoft.com/en-us/answers/questions/670006/try-to-sending-email-not-working-with-suscription.html
I have setup the new server with the relay but now it fails and gives me an MMC error every time
Server Specs & Error
SSRS Subscription Error
Please advice what else I can do regarding this error - I tried to do windows update and it did not work and could not find useful topics to fix this issue
Second scenario - client running windows 10 that is not support with windows relay also using office365 mail server - does not want to upgrade to new server or use an alternative mail server - but they want to use SSRS subscriptions - is there any way forward or alternative way to use SSRS subscriptions with windows 10 or will they need to make the change
https://adamtheautomator.com/iis-smtp-relay/
Thank you in advance

Related

SSRS Data Driven Subscription Option Not Appearing

We have a new 2016 report server. It is supposedly the Enterprise Edition but Data Driven Subscriptions are not available in our PROD database but they are available in our TEST server.
I know that versions lower than the Enterprise Edition do not have Data Driven Subscriptions but our Operations department says that the servers are set up the same.
Unfortunately, I do not have access to check out the server edition (or much else) myself so I can't say for sure that the PROD server is the Enterprise Edition. Our Ops guys haven't done much with SSRS - I had to tell one guy where to set up the e-mail server so the e-mail Destination appeared.
TEST SERVER with data driven subscription:
Is there any reason, other than not having the Enterprise Edition, that could make the Data Driven subscriptions to not appear? Is there a setting or an option that needs to be checked during installation?
There is no setting (as far as I am aware) that would disable the Data Driven Subscription option from appearing on your subscription window by default.
Simple Select ##version in SQL Management Studio against your prod environment and compare it to your test environment.. that should tell you what version straight away.. or connect to the reporting server instance and then look at server properties.. Edition., It's got to be the version!

SQL Server version mismatch

I'm trying to attach a SQL Server .mdf to my Management Studio 2014, but I get the error:
Attach database failed for Server '...\SQLINSTANCE'. (Microsoft.SqlServer.Smo)
Additional information:
An exception occured while executing a Transact-SQL statement or batch.
(Microfost.SqlServer.ConnectionInfo)
The database 'DatabaseName' cannot be opened because it is version 706. This server supports version 663 or earlier. A downgrade path is not supported.
Could not open new database 'DatabaseName'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
The .mdf was created on SQL Server 2012 (which presumably is represented as 'version 706' in the error message).
OK, so I need to upgrade my DB engine to 2012 on my home PC. That means installing 2012 Express from https://www.microsoft.com/en-gb/download/details.aspx?id=29062
A couple of questions though before I do that. By installing 2012, would it be added to Management Studio 2014 automatically? Would I then have both 2008 & 2012 as options for new databases I might want to create, or would 2012 simply replace 2008?
On the download page, it says the supported OSs are "Windows 7, Windows Server 2008 R2, Windows Server 2008 Service Pack 2, Windows Vista Service Pack 2". But I'm using Windows 10. Is this just a case of MS not updating the page or does 2012 really have a problem with Windows 10?
EDIT: It's true that this question is similar to ones previously asked on SO (such as The database cannot be opened because it is version 706), but here I'm not contemplating rolling back the 2012 version of the DB to 2008, but issues pertaining to installing 2012 on my home PC.
So, your SQL Server version is 2008 - you have 2014 management studio and you need to use a database from a server version 2012.
If that is the case; then I hope some of the following will help:
Windows 10 can run SQL Server 2012 fine.
The documentation might just not be updated, but I've not personally seen any issues on multiple instances.
Management Studio 2014 can connect to SQL Server version 2012 as well. You don't need to install it again.
Unless you wish to remove SQL Server 2008, you'll need to install 2012 as a new instance, so you basically have two SQL Servers running. This however, will have affect on how you connect to the databases.
Check out, for example: https://msdn.microsoft.com/en-us/library/ms143531.aspx for more information
So instead of having multiple instances, consider whether you'll still need 2008, so it might be removed if you don't need it at all.
Also - consider whether it might be worth it to upgrade your local instance to newer version - 2014 for example. However this of course might give you the same problem in reverse in the future, if you ever need to make a database on 2014 instance and move it to a 2012 instance.
It all depends on the actual requirements, set-up and development models. Basically because you say it's your home computer, I'd think the newest version might just be the best approach, as you're less likely to use that version as a "creator" rather than a development version.

dynamics ax ssrs deploy error

I've got this error when I tried to deploy SSRS report in Visual Studio.
(DAX 2012 kernel 6.0.1108.6510 app 6.0.1108.670 solution 6.1.1108.670)
Error 1 A call to the Microsoft Dynamics AX SRSFrameworkService service failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 10.43.6.57:8201. C:\Program Files (x86)\MSBuild\Microsoft\DynamicsTools\Microsoft.Dynamics.Framework.Design.Reporting.Modeling.targets 466
10.43.6.57:8201 is old address new should be 10.43.6.91:8201
Where I can change it?
In AX form SSRSServerFarm address is new:(NLDDAXDBS02TR, http://NLDDAXDBS02TR/Reports, 01#NLDDAXDBS02TR)
I run Visual Studio like this "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe" /AxConfig "c:\Users\Username\Desktop\DEV.axc" with correct config file
in axc file I don't have 10.43.6.57 or old dns NLDDAXDBS01T
I scanned and replaced values in registry on client and server machine, checked all files on client and server machine, checked all values in database.
Also restarted AOSes, SSRS service, and client RDP session.
Microsoft Dynamics AX 2012 Configuration and perform a Refresh Configuration didn't help
Full CIL Compilation, Deactivate BIServices, Activate BIServices also didn't help
Running Visual Studio as Admin - same result
nslookup says: NLDDAXDBS01T - 10.43.6.57 NLDDAXDBS02TR - 10.43.6.91
System Administration > Setup > Business intelligence > Report Servers is correct because i tried to deploy from another rdp server and it works fine
Are you certain the default report server is setup correctly in Ax?
Found under:
System Administration > Setup > Business intelligence > Report
Servers
Check your business connector configuration to make sure it's connecting to the right environment, see https://technet.microsoft.com/en-us/library/aa569654.aspx
I think Visual Studio deploys to AX based on that business connector AXC, so if that's pointed to an incorrect environment that has the "old" SSRS setup, it would explain your issue.
I got this problem one time due to multiple AOS and SSRS instance, or you might stop AOS service while user still using.
First, you need to make sure Report servers configuration point correctly to SSRS instance.
Then, stop all AOS service, go to reporting service login with correct instance and check everything again.
Then, perform full compilation using AXbuild.exe , Full CIL.
Start AOS service and check.
Let us know result.

Using the WebForms ReportViewer 10.0 with a Reporting Services 2012 instance

Does anyone know definitively whether the ReportViewer 10.0 webforms control works correctly against a Reporting Services 2012 instance?
Our application uses v10.0 of the webforms ReportViewer control and typically we connect to one of several 2008 SSRS instances. However we have had to setup a new secure environment for one of our clients and have deployed our application to it. We are seeing some strange behavior and I just found out that this new environment runs SQL Server 2012 and therefore SSRS 2012.
The problem we are seeing is that some users of the web application get the following message in the ReportViewer control:
"No connection could be made because the target machine actively refused it."
This doesn't seem like a client specific issue since the connection to the SSRS server is made by the application and the rendered output is sent to the client. Before we go too far into troubleshooting this issue I feel like I need to try and verify whether this combination should work ok, or if there are known incompatibilities.
Unfortunately it's a fairly big effort to just swap out the ReportViewer control we are using to the latest version that aligns with SSRS 2012 and so I'm trying to see if anyone has successfully gotten this to work without issues or not.
Thanks.

"Unable To Load Client Print Control" - SSRS Printing problems again

Please forgive me as my head is spinning. I have tried so many solutions to this issue, that I'm almost not sure where I am at this point.
At this point in time I have these issues in my Production, Test, and Dev environments. For simplicity sake, I will just try to get it working in Dev first. Here is my setup:
Database/Reporting Server (Same server):
Windows Server 2003 SP2
SQL Server 2005 SP3
Development Box:
Windows 7
Visual Studio 2008 SP1
SQL Server 2008 SP1 (not being used in this case, but wanted to include it in case it is relative)
Internet Explorer 8
Details:
* I have a custom ASP.NET application that is using ReportViewer to access reports on my Database/Reporting Server.
* I am able to connect directly to Report Manager and print with no trouble.
* When I view source on the page with ReportViewer, it says I'm am using version 9.0.30729.4402 .
* The classid of the rsclientprint.dll that keeps getting installed to my c:\windows\downloaded program files directory is {41861299-EAB2-4DCC-986C-802AE12AC499}.
* I have tried taking the rsclientprint.cab file from my Database/Reporting Server and installing it directly to my Development Box and had no success. I made sure to unregister the previously installed dll first.
I feel like I have read as many solutions as I can, and so I turn to you for some assistance. Please let me know if I can provide further details that would be helpful.
Thanks
I am cross posting the solution I received on MSDN. I hope it helps someone else.
Hi mamorgan1,
From your description, I notice you
are using Report Viewer with version
9.0.30729.4402, and SQL Server Reporting Serivces 2005 with SP3.
RS Client Print control is an ActiveX
control which uses a ClassID to check
if the ActiveX is installed on the
client. By default, the ClassID for
SQL Server Reporting Services SP3 is
41861299-EAB2-4DCC-986C-802AE12AC499.
However, Report Viewer 9.0.30729.4402
would like the ClassID
0D221D00-A6ED-477C-8A91-41F3B660A832.
RSClientPrint control has been updated
after applying Cumulative Update #8
for SQL Server 2005 Service Pack 3.
So, please apply Cumulative Update #8
for SQL Server 2005 Service Pack 3 to
solve the issue.
For more information about Cumulative
Update #8 for SQL Server 2005 Service
Pack 3, please see:
http://support.microsoft.com/kb/978915/en-us
If you have any more questions, please
feel free to ask.
Thanks, Jin ChenJin Chen - MSFT