Friday, February 24, 2012

How I resolved "Failure sending mail: The Report Server has encountered a configuration er

Hi
It seems there are various issues that lead to this problem.
If no other postings appear to solve your particular problem check
this...
Are all subscriptions failing or just some of them?
If its just some of them your problem maybe that the failing reports
have a subscription owner of a specific domain user id that has been
removed.
1) Check the subscription to the failing report and see if there is an
"Owner" specified under the "Delivered By" option.
2) If there is, check with your admin that this id still exists.
In my case this was an ex-employee who had been removed.
3) If the id has been deleted, create a clone of the subscription and
delete the failing subscription. Test your new subscription by manually
starting the appropriate job on the report server.
TIP - I identify the correct JobName with this piece of SQL on the
Report Server. You might need to adapt it slightly but it works for me!
SELECT J.name AS JobName
,C.Name AS ReportName
,CASE CHARINDEX('RenderFormat', S.ExtensionSettings)
WHEN 0 THEN 'PATH'
ELSE SUBSTRING(S.ExtensionSettings
,CHARINDEX('RenderFormat', S.ExtensionSettings) + 26
,CHARINDEX('</Value>', S.ExtensionSettings,
CHARINDEX('RenderFormat', S.ExtensionSettings)) -
(CHARINDEX('RenderFormat', S.ExtensionSettings) + 26))
END AS ExportType
,S.DeliveryExtension AS DeliveryMethod
,S.DEscription + '...' AS Recipients
FROM ReportServer.dbo.Catalog C
,ReportServer.dbo.ReportSchedule R
,ReportServer.dbo.Subscriptions S
,msdb.dbo.sysjobs J
WHERE C.ItemID = R.ReportID
AND R.SubscriptionID = S.SubscriptionID
AND J.name = CAST(R.ScheduleID AS VARCHAR(255))
ORDER BY 2
,3I'm running into this as well excep I am the owner of the report...
The one thing that has occured recently is that my PC was switched from one
domain to another. The new domian I am operating on is setup w/ active
directory.
Any ideas?
Thanks,
Ben Sullins
"perrydyball@.hotmail.com" wrote:
> Hi
> It seems there are various issues that lead to this problem.
> If no other postings appear to solve your particular problem check
> this...
> Are all subscriptions failing or just some of them?
> If its just some of them your problem maybe that the failing reports
> have a subscription owner of a specific domain user id that has been
> removed.
> 1) Check the subscription to the failing report and see if there is an
> "Owner" specified under the "Delivered By" option.
> 2) If there is, check with your admin that this id still exists.
> In my case this was an ex-employee who had been removed.
> 3) If the id has been deleted, create a clone of the subscription and
> delete the failing subscription. Test your new subscription by manually
> starting the appropriate job on the report server.
> TIP - I identify the correct JobName with this piece of SQL on the
> Report Server. You might need to adapt it slightly but it works for me!
> SELECT J.name AS JobName
> ,C.Name AS ReportName
> ,CASE CHARINDEX('RenderFormat', S.ExtensionSettings)
> WHEN 0 THEN 'PATH'
> ELSE SUBSTRING(S.ExtensionSettings
> ,CHARINDEX('RenderFormat', S.ExtensionSettings) + 26
> ,CHARINDEX('</Value>', S.ExtensionSettings,
> CHARINDEX('RenderFormat', S.ExtensionSettings)) -
> (CHARINDEX('RenderFormat', S.ExtensionSettings) + 26))
> END AS ExportType
> ,S.DeliveryExtension AS DeliveryMethod
> ,S.DEscription + '...' AS Recipients
> FROM ReportServer.dbo.Catalog C
> ,ReportServer.dbo.ReportSchedule R
> ,ReportServer.dbo.Subscriptions S
> ,msdb.dbo.sysjobs J
> WHERE C.ItemID = R.ReportID
> AND R.SubscriptionID = S.SubscriptionID
> AND J.name = CAST(R.ScheduleID AS VARCHAR(255))
> ORDER BY 2
> ,3
>

No comments:

Post a Comment