Sunday, February 26, 2012

File Share Delivery of subscription fails

I have a subscription that will not deliver to a file share. I've ensured
that the windows acct for share access for the subscription has read/write to
the share.
The error I get in report manager is:
Failure writing file <report name>: The Report Server has encountered a
configuration error; more details in the log files
The log file says:
ReportingServicesService!library!10ec!08/08/2005-12:26:05:: i INFO: Call to
RenderFirst( '/My Reports/<report name>)
ReportingServicesService!library!10ec!08/08/2005-12:26:06:: e ERROR:
Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The Report Server has encountered a configuration error; more details in the
log files, AuthzInitializeContextFromSid: Win32 error: 234;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The Report Server has encountered a configuration error; more details in the
log files
ReportingServicesService!library!10ec!08/08/2005-12:26:06:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server system
properties.
ReportingServicesService!subscription!10ec!08/08/2005-12:26:06::
Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The Report
Server has encountered a configuration error; more details in the log files
-->
Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
The Report Server has encountered a configuration error; more details in the
log files
at
Microsoft.ReportingServices.Authorization.Native.GetAuthzContextForUser(IntPtr userSid)
at Microsoft.ReportingServices.Authorization.Native.IsAdmin(String
userName)
at
Microsoft.ReportingServices.Authorization.WindowsAuthorization.IsAdmin(String
userName, IntPtr userToken)
at
Microsoft.ReportingServices.Authorization.WindowsAuthorization.CheckAccess(String
userName, IntPtr userToken, Byte[] secDesc, ReportOperation requiredOperation)
at Microsoft.ReportingServices.Library.Security.CheckAccess(ItemType
catItemType, Byte[] secDesc, ReportOperation rptOper)
at
Microsoft.ReportingServices.Library.RSService._GetReportParameterDefinitionFromCatalog(CatalogItemContext
reportContext, String historyID, Boolean forRendering, Guid& reportID, Int32&
executionOption, String& savedParametersXml, ReportSnapshot&
compiledDefinition, ReportSnapshot& snapshotData, Guid& linkID, DateTime&
historyDate)
at
Microsoft.ReportingServices.Library.RSService._GetReportParameters(String
report, String historyID, Boolean forRendering, NameValueCollection values,
DatasourceCredentialsCollection credentials)
at
Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters)
at
Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
reportContext, ClientRequest session, Warning[]& warnings,
ParameterInfoCollection& effectiveParameters, String[]& secondaryStreamNames)
at Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
-- End of inner exception stack trace --
at
Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
at
Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService
rs, CatalogItemContext reportContext, ClientRequest session, JobTypeEnum
type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters,
String[]& secondaryStreamNames)
at Microsoft.ReportingServices.Library.ReportImpl.Render(String
renderFormat, String deviceInfo)
at
Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.SaveReport(Notification notification, SubscriptionData data)
at
Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.Deliver(Notification notification)
Any ideas?
TIA,
Berry Morgan
JSOAre the user who created the report subscription and the ReportServer in the
same domain (actually the ReportServerService service account). We have seen
this issue in our DEV + QA environments which are in different domains that
are not trusted by our prod domain (but do trust it). We have configured all
our Report Servers to run under prod domain service accounts to get around
this issue (because when testing subscriptions, developers will still be
using their prod accounts and it seems that it is the subscription owner
account that was failing to be resolved)
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Berry at JSO" <6399bwmNOSPAM@.community.nospam> wrote in message
news:D735DEE3-F3E8-4250-9AAA-396D1B3742B2@.microsoft.com...
>I have a subscription that will not deliver to a file share. I've ensured
> that the windows acct for share access for the subscription has read/write
> to
> the share.
> The error I get in report manager is:
> Failure writing file <report name>: The Report Server has encountered a
> configuration error; more details in the log files
>
> The log file says:
> ReportingServicesService!library!10ec!08/08/2005-12:26:05:: i INFO: Call
> to
> RenderFirst( '/My Reports/<report name>)
> ReportingServicesService!library!10ec!08/08/2005-12:26:06:: e ERROR:
> Throwing
> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
> The Report Server has encountered a configuration error; more details in
> the
> log files, AuthzInitializeContextFromSid: Win32 error: 234;
> Info:
> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
> The Report Server has encountered a configuration error; more details in
> the
> log files
> ReportingServicesService!library!10ec!08/08/2005-12:26:06:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
> system
> properties.
> ReportingServicesService!subscription!10ec!08/08/2005-12:26:06::
> Microsoft.ReportingServices.Diagnostics.Utilities.RSException: The Report
> Server has encountered a configuration error; more details in the log
> files
> -->
> Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
> The Report Server has encountered a configuration error; more details in
> the
> log files
> at
> Microsoft.ReportingServices.Authorization.Native.GetAuthzContextForUser(IntPtr
> userSid)
> at Microsoft.ReportingServices.Authorization.Native.IsAdmin(String
> userName)
> at
> Microsoft.ReportingServices.Authorization.WindowsAuthorization.IsAdmin(String
> userName, IntPtr userToken)
> at
> Microsoft.ReportingServices.Authorization.WindowsAuthorization.CheckAccess(String
> userName, IntPtr userToken, Byte[] secDesc, ReportOperation
> requiredOperation)
> at Microsoft.ReportingServices.Library.Security.CheckAccess(ItemType
> catItemType, Byte[] secDesc, ReportOperation rptOper)
> at
> Microsoft.ReportingServices.Library.RSService._GetReportParameterDefinitionFromCatalog(CatalogItemContext
> reportContext, String historyID, Boolean forRendering, Guid& reportID,
> Int32&
> executionOption, String& savedParametersXml, ReportSnapshot&
> compiledDefinition, ReportSnapshot& snapshotData, Guid& linkID, DateTime&
> historyDate)
> at
> Microsoft.ReportingServices.Library.RSService._GetReportParameters(String
> report, String historyID, Boolean forRendering, NameValueCollection
> values,
> DatasourceCredentialsCollection credentials)
> at
> Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(CatalogItemContext
> reportContext, ClientRequest session, Warning[]& warnings,
> ParameterInfoCollection& effectiveParameters)
> at
> Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
> reportContext, ClientRequest session, Warning[]& warnings,
> ParameterInfoCollection& effectiveParameters, String[]&
> secondaryStreamNames)
> at
> Microsoft.ReportingServices.Library.RenderFirstCancelableStep.Execute()
> at
> Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
> -- End of inner exception stack trace --
> at
> Microsoft.ReportingServices.Diagnostics.CancelablePhaseBase.ExecuteWrapper()
> at
> Microsoft.ReportingServices.Library.RenderFirstCancelableStep.RenderFirst(RSService
> rs, CatalogItemContext reportContext, ClientRequest session, JobTypeEnum
> type, Warning[]& warnings, ParameterInfoCollection& effectiveParameters,
> String[]& secondaryStreamNames)
> at Microsoft.ReportingServices.Library.ReportImpl.Render(String
> renderFormat, String deviceInfo)
> at
> Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.SaveReport(Notification
> notification, SubscriptionData data)
> at
> Microsoft.ReportingServices.FileShareDeliveryProvider.FileShareProvider.Deliver(Notification
> notification)
>
> Any ideas?
> TIA,
> Berry Morgan
> JSO|||The subscription creator is a production domain account, but the
ReportServer service identity is NT AUTHORITY\Network Service.
If I change the ReportServer service identity to a domain account, won't
that require reactivation of the reporting server?
Also, email subscriptions currently work: wouldn't changing the service
identity require configuration changes for this subscription type as well?
My hunch is that subscription delivery to file shares is tied in with code
access security settings, but I'm not the MVP. :)
-Berry
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:ewEcpyGnFHA.3304@.tk2msftngp13.phx.gbl...
> Are the user who created the report subscription and the ReportServer in
> the same domain (actually the ReportServerService service account). We
> have seen this issue in our DEV + QA environments which are in different
> domains that are not trusted by our prod domain (but do trust it). We have
> configured all our Report Servers to run under prod domain service
> accounts to get around this issue (because when testing subscriptions,
> developers will still be using their prod accounts and it seems that it is
> the subscription owner account that was failing to be resolved)
>|||Our issue was purely domain related however what I would suggest is that you
contact PSS. They'll be able to provide you with a utility that should help
pinpoint the issue. This is a common problem (the error message you are
seeing) and it's all related to being able to query AD and permissions
related to that (rather than specifically anything SQL related). PSS will be
able to help you track down the specific issue in your environment. Email
subscriptions don't suffer the same issue as far as I'm aware (we haven't
seen it but that doesn't mean it doesn't exist<g>)
--
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Berry Morgan" <6399bwmNOSPAM@.community.nospam> wrote in message
news:uwK78DTnFHA.1372@.TK2MSFTNGP10.phx.gbl...
> The subscription creator is a production domain account, but the
> ReportServer service identity is NT AUTHORITY\Network Service.
> If I change the ReportServer service identity to a domain account, won't
> that require reactivation of the reporting server?
> Also, email subscriptions currently work: wouldn't changing the service
> identity require configuration changes for this subscription type as well?
> My hunch is that subscription delivery to file shares is tied in with code
> access security settings, but I'm not the MVP. :)
> -Berry
> "Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
> news:ewEcpyGnFHA.3304@.tk2msftngp13.phx.gbl...
>> Are the user who created the report subscription and the ReportServer in
>> the same domain (actually the ReportServerService service account). We
>> have seen this issue in our DEV + QA environments which are in different
>> domains that are not trusted by our prod domain (but do trust it). We
>> have configured all our Report Servers to run under prod domain service
>> accounts to get around this issue (because when testing subscriptions,
>> developers will still be using their prod accounts and it seems that it
>> is the subscription owner account that was failing to be resolved)
>

No comments:

Post a Comment