I'm having difficulty sending auto generated e-mails via SSRS. I'm getting a vague error that states "An error has occurred during report processing.". I've detailed the full error below. Does anyone know some of the possible reasons why I would be getting this error?
Here are examples of the Shared Dataset Properties:
Here's the error I'm getting:
library!WindowsService_9!14c0!07/11/2019-10:18:01:: i INFO: Schedule 3d1ac939-3fb6-4313-9e04-bce6353a6825 executed at 07/11/2019 10:18:01.
schedule!WindowsService_9!14c0!07/11/2019-10:18:01:: Creating Time based subscription notification for subscription: a9d6e90a-84fc-439d-b715-49f7479cf69d
library!WindowsService_9!14c0!07/11/2019-10:18:01:: i INFO: Schedule 3d1ac939-3fb6-4313-9e04-bce6353a6825 execution completed at 07/11/2019 10:18:01.
library!WindowsService_9!14c0!07/11/2019-10:18:01:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 1722, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
processing!WindowsService_9!14c0!07/11/2019-10:18:01:: e ERROR: An exception has occurred in data set 'DS_Example'. Details: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
processing!WindowsService_9!14c0!07/11/2019-10:18:01:: i INFO: DataPrefetch abort handler called for Report with ID=. Aborting data sources ...
processing!WindowsService_9!14c0!07/11/2019-10:18:01:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: , Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
--- End of inner exception stack trace ---;
processing!WindowsService_9!14c0!07/11/2019-10:18:01:: w WARN: Data source ' Data source for shared dataset': Report processing has been aborted.
processing!WindowsService_9!14c0!07/11/2019-10:18:01:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: , Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
--- End of inner exception stack trace ---;
library!WindowsService_9!14c0!07/11/2019-10:18:01:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
notification!WindowsService_9!14c0!07/11/2019-10:18:01:: e ERROR: Error occured processing subscription a9d6e90a-84fc-439d-b715-49f7479cf69d: An error has occurred during report processing.
I ran the procedure that the data set reference. The data generates without any issues. I've created subscriptions for existing reports and they all executed without error. I've also check the connections to confirm that it wasn't a credential issue but it connected without error.
The subscription should generate a daily report to specified users.
The Win32 error 1722 is the key to this error message. It's an RPC server not available error. Microsoft has a KB article addressing this exact issue:
https://support.microsoft.com/en-us/help/842423/a-call-to-the-authzinitializecontextfromsid-api-function-fails-during
So it looks like the permissions needed to be granted for the service account database and table. The issue has been resolved!
Related
In SSIS (version 15, created through Visual Studio 2017), I am trying to connect to a Sharepoint list ("Deficiencies") with an HTTPS URL. I get this error:
Error: 0xC020801F at Deficiencies, Get Deficiencies Data [2]: Cannot
acquire a managed connection from the run-time connection manager.
Error: 0xC0047017 at Deficiencies, SSIS.Pipeline: Get Deficiencies
Data failed validation and returned error code 0xC020801F. Error:
0xC004700C at Deficiencies, SSIS.Pipeline: One or more component
failed validation. Error: 0xC0024107 at Deficiencies: There were
errors during task validation.
I am using an OData Source. The Connection Manager returns a "test successful" and previews the list data. However, when I run the package in VS, it returns the above error. It does the same whether I use Windows Authentication or use the service SQL account.
I'm including /_vti_bin/listdata.svc at the end of the URL.
[Load_Row table [9928]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "DB_NAME" failed with error code 0xC0202009.
There may be error messages posted before this with more information on why the AcquireConnection method call failed.
[SSIS.Pipeline] Error: component "Load_Row table" (9928) failed validation and returned error code 0xC020801C.
[Connection manager "Raven_MSSQL"] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D.
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 10.0" Hresult: 0x80040E4D Description: "Login failed for user '****'."
I am getting above error for 10-12 packages in my pre-prod environment .
But Couple of week before, It was fine and loaded the data.
I have checked the config files and could see no changes happened and everything looks same.But when I downloaded the same package from server and executed, i got the same error.After google, I changed the protection level and executed, it got succeeded.
Do I want to change the protection level and re-deploy ?
Please put your suggestion which helps me to overcome this issue.
Thanks in advance
I'm junior DBA, well actually i'm more of a sysadmin than a DBA.
I'm struggling with a reccuring problem in one of my SQL 2012 Dev reporting server. We've reports snapshot generated by dynamics CRM 2013 on the dev reporting server.
I've been ask to send those reports to a specific email address on which would be attached the generated report in pdf.
I'm able to scheddule a subscription to run for example every day at the certain time and the plan did execute well.
My problem is that the action is it supposed to trigger (sending an email) is not giving me the result i'm expecting.
I found in the report server LogFiles some intriging entries that, despite googling them around, haven't been able to resolved. The Log entries look like this:
schedule!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Handling Event TimedSubscription with data cf25ffaa-99c8-404f-bbf8-00c10ecbbe9b.
library!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Schedule f81461ea-5067- 4d14-b2ad-6930ce8ad3d8 executed at 06/20/2014 14:35:01.
schedule!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Creating Time based subscription notification for subscription: cf25ffaa-99c8-404f-bbf8-00c10ecbbe9b
library!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Schedule f81461ea-5067- 4d14-b2ad-6930ce8ad3d8 execution completed at 06/20/2014 14:35:01.
library!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
notification!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Handling subscription cf25ffaa-99c8-404f-bbf8-00c10ecbbe9b to report {f48fd9a9-4df8-e311-a000- 00155d060421}, owner: DOMAIN\Username, delivery extension: Report Server Email.
library!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: RenderForNewSession('/DEV_MSCRM/CustomReports/{f48fd9a9-4df8-e311-a000-00155d060421}')
library!WindowsService_203!1764!06/20/2014-14:35:01:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: AuthzInitializeContextFromSid: Win32 error: 5; possible reason - service account doesn't have rights to check domain user SIDs., Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ;
library!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Initializing EnableExecutionLogging to 'True' as specified in Server system properties.
emailextension!WindowsService_203!1764!06/20/2014-14:35:01:: e ERROR: Error sending email. Exception: Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The report server has encountered a configuration error. ---> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error.
notification!WindowsService_203!1764!06/20/2014-14:35:01:: i INFO: Notification 4718cbfe-0fef-481b-b0dd-60fae64c4271 completed. Success: True, Status: Failure sending mail: The report server has encountered a configuration error. Mail will not be resent., DeliveryExtension: Report Server Email, Report: {f48fd9a9-4df8-e311-a000-00155d060421}, Attempt 0
Can any one of you guys, faced such a problem? Would you mind pointing me out to the direction that i could follow to get the email sending working?
Thanks again for you time.
I'm trying to implement the SSIS package failure handler. I've added onError Event handler on whole package and failure operation the task where i'm expecting an error in the control flow.
The main task of the package is to pick up some data from the db,
the error handler is Send Mail Task sending email message with error description.
Now, I'm trying to emulate a common error: I make some changes in the SQL query (for example, set incorrect name for one of the columns) and try to run the package.
What i see is that package fails on validation stage and does not even proceed to execution, saying
Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occured. Error Code 0x80040E14. An OLE DB record is available. Source "Microsoft SQL Server Native Client 11.0"
Hresult 0x80040E14 Description "Statement(s) could not be prepared"
Description "The multipart identifier "MyTable.SomeWrongField" could not be bound".
Error: "OLE DB Source" failed validation and returned validation status "VS_BROKEN".
It doesn't even procceed to execution, failing right after validation.
How to set the error handle so it handles EVERY error, even the issue like this (incorrect sql request)?
Thanks.
A Validation error is the SSIS equivalent of a syntax error. There is no opportunity for recovery as the execution is dead in the water. OnTaskFailed and OnError won't catch this type of error (which is one of the reasons we no longer implement error notification from within our packages themselves)
Message
Executed as user: UKDBT91DB05V\SYSTEM. Microsoft (R) SQL Server
Execute Package Utility Version 10.50.2500.0 for 64-bit Copyright
(C) Microsoft Corporation 2010. All rights reserved. Started:
14:58:34 Error: 2013-04-01 14:58:34.45 Code: 0xC0016016
Source: Description: Failed to decrypt protected XML node
"DTS:Property" with error 0x8009000B "Key not valid for use in
specified state.". You may not be authorized to access this
information. This error occurs when there is a cryptographic error.
Verify that the correct key is available. End Error Error:
2013-04-01 14:58:34.76 Code: 0xC001000E Source:
ReceiveDGDinformation Description: The connection "stock" is not
found. This error is thrown by Connections collection when the
specific connection element is not found. End Error Error:
2013-04-01 14:58:34.80 Code: 0xC0202009 Source:
ReceiveDGDinformation Connection manager "Stock" Description: SSIS
Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error
code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft
SQL Server Native Client 10.0" Hresult: 0x80040E4D Description:
"Login failed for user 'DOTCOM\UKDBT91DB05V$'.". End Error Error:
2013-04-01 14:58:34.80 Code: 0xC020801C Source: Populate
Staginng Table Populate DGD Staging table [34] Description: SSIS
Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The
AcquireConnection method call to the connection manager "Stock" failed
with error code 0xC0202009. There may be error messages posted before
this with more information on why the AcquireConnection method call
failed. End Error Error: 2013-04-01 14:58:34.80 Code: 0xC0047017
Source: Populate Staginng Table SSIS.Pipeline Description:
component "Populate DGD Staging table" (34) failed validation and
returned error code 0xC020801C. End Error Error: 2013-04-01
14:58:34.80 Code: 0xC004700C Source: Populate Staginng Table
SSIS.Pipeline Description: One or more component failed
validation. End Error Error: 2013-04-01 14:58:34.80 Code:
0xC0024107 Source: Populate Staginng Table Description: There
were errors during task validation. End Error DTExec: The package
execution returned DTSER_FAILURE (1). Started: 14:58:34 Finished:
14:58:34 Elapsed: 0.624 seconds. The package execution failed. The
step failed.
Meaningful bits of the error message
Failed to decrypt protected XML node "DTS:Property" with error 0x8009000B "Key not valid for use in specified state.". You may not be authorized to access this information. This error occurs when there is a cryptographic error
Login failed for user 'DOTCOM\UKDBT91DB05V$'
This is probably a problem with your ProtectionLevel setting and how you are configuring the job.
If ProtectionLevel is at the default "EncryptSensitiveWithUserKey" setting, then the development environment is encrypting things like your connection string database password using a key that depends on the user who is doing the development. After you deploy it to the production server and schedule a SQL Server Agent job, it will most likely run under a different user account, and then it will be unable to decrypt the database password. You will get this error.
One possibility would be to make sure the development user and the job execution user are the same user account, but this is not a good idea. Usually you want your production user accounts to be separate from your development user accounts.
Instead, you should set ProtectionLevel to "DontSaveSensitive". Then the password won't get saved with the SSIS package at all. You create a configuration file for the connection string, but the password won't get saved to the configuration file either. You will have to edit the configuration file manually if you want it to include a password. But the best way to do this is to configure the password when you schedule the job that executes the SSIS package. That keeps the password in a safe place, and it isn't floating around all over the place with the SSIS package.
Some useful links here and here.
Good luck!