Scenerio:
RS2000. Subscription delivers email with PDF attachment.
When the email is opened in Outlook client, the attachment is there and
working as expected.
Problem:
When the email is opened in the Outlook Web client (OWA), the paperclip is
there identifying the attachment, but when the email is opened, there is no
attachment.
It seems to be happening only with attachment coming from reporting
services. I can send an email with another PDF file and open it fine. The
PDF files are small in size so I do not think it is a size proble.I just tried this and also was not able to see the .pdf file. This appears
to be a bug to me. I would contact customer support to help get this issue
resolved.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
news:B4C39492-DC1A-4FA0-8198-F1727A020B34@.microsoft.com...
> Scenerio:
> RS2000. Subscription delivers email with PDF attachment.
> When the email is opened in Outlook client, the attachment is there and
> working as expected.
> Problem:
> When the email is opened in the Outlook Web client (OWA), the paperclip is
> there identifying the attachment, but when the email is opened, there is
> no
> attachment.
> It seems to be happening only with attachment coming from reporting
> services. I can send an email with another PDF file and open it fine.
> The
> PDF files are small in size so I do not think it is a size proble.|||Daniel,
Thank you for the response.
"Daniel Reib [MSFT]" wrote:
> I just tried this and also was not able to see the .pdf file. This appears
> to be a bug to me. I would contact customer support to help get this issue
> resolved.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "chicagoclone" <chicagoclone@.discussions.microsoft.com> wrote in message
> news:B4C39492-DC1A-4FA0-8198-F1727A020B34@.microsoft.com...
> >
> > Scenerio:
> > RS2000. Subscription delivers email with PDF attachment.
> > When the email is opened in Outlook client, the attachment is there and
> > working as expected.
> >
> > Problem:
> > When the email is opened in the Outlook Web client (OWA), the paperclip is
> > there identifying the attachment, but when the email is opened, there is
> > no
> > attachment.
> >
> > It seems to be happening only with attachment coming from reporting
> > services. I can send an email with another PDF file and open it fine.
> > The
> > PDF files are small in size so I do not think it is a size proble.
>
>
Showing posts with label subscription. Show all posts
Showing posts with label subscription. Show all posts
Thursday, March 22, 2012
Tuesday, March 20, 2012
bug: data-driven subscription generates deadlock in ReportServer D
I've got a report that can have about 50 possible parameter combinations. The
underlying query is fairly expensive, so I want to cache the dataset every
morning after I expire yesterday's cache. So I set up a data-driven
subscription to run every morning and execute all the parameter combinations
and deliver it to the Null delivery extension. The problem is that when the
scheduled time rolls around, it tries to run all 50 parameter combinations at
once. (Actually, it looks like it runs 2 or 3 combinations a second without
waiting for the first one to finish.) The query of the data sources run fine,
but I get a deadlock when Reporting Services tries to write the dataset to
the cache. Somewhere between 10% and 50% of the 50 fail every day. The logs
show a standard deadlock error. The error is below.
Is there any config file setting to tell RS to retry writing to the cache a
few times before giving up because of a deadlock? Is this possibly a SP2 fix?
Or is there any way to tell Reporting Services to run the 50 executions
serially instead of concurrently? Or do I need to investigate creating some
custom code to execute and cache the reports on schedule (so I can make it
execute them serially)?
Please let me know if you need more info... or if you need something from
the SQL Server logs. Thanks in advance.
--
ReportingServicesService!library!2e72c!10/28/2004-21:25:21:: e ERROR:
Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Data.SqlClient.SqlException: Transaction (Process ID
132) was deadlocked on lock resources with another process and has been
chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.DBInterface.AddReportToExecutionCache(Guid
reportId, ReportSnapshot snapshotData, DateTime executionDateTime, DateTime&
expirationDateTime)
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)
-- End of inner exception stack trace --Hi,
Try setting MaxQueueThreads to 1 in the RSReportServer.config file. You may
want to escalate this to the RS PSS since it looks like a bug to me.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"FurmanGG" <FurmanGG@.discussions.microsoft.com> wrote in message
news:516B456B-0E41-46AA-B775-D3BA1B13C1F0@.microsoft.com...
> I've got a report that can have about 50 possible parameter combinations.
The
> underlying query is fairly expensive, so I want to cache the dataset every
> morning after I expire yesterday's cache. So I set up a data-driven
> subscription to run every morning and execute all the parameter
combinations
> and deliver it to the Null delivery extension. The problem is that when
the
> scheduled time rolls around, it tries to run all 50 parameter combinations
at
> once. (Actually, it looks like it runs 2 or 3 combinations a second
without
> waiting for the first one to finish.) The query of the data sources run
fine,
> but I get a deadlock when Reporting Services tries to write the dataset to
> the cache. Somewhere between 10% and 50% of the 50 fail every day. The
logs
> show a standard deadlock error. The error is below.
> Is there any config file setting to tell RS to retry writing to the cache
a
> few times before giving up because of a deadlock? Is this possibly a SP2
fix?
> Or is there any way to tell Reporting Services to run the 50 executions
> serially instead of concurrently? Or do I need to investigate creating
some
> custom code to execute and cache the reports on schedule (so I can make it
> execute them serially)?
> Please let me know if you need more info... or if you need something from
> the SQL Server logs. Thanks in advance.
> --
> ReportingServicesService!library!2e72c!10/28/2004-21:25:21:: e ERROR:
> Throwing
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details., ;
> Info:
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details. --> System.Data.SqlClient.SqlException: Transaction (Process ID
> 132) was deadlocked on lock resources with another process and has been
> chosen as the deadlock victim. Rerun the transaction.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.DBInterface.AddReportToExecutionCache(Gu
id
> reportId, ReportSnapshot snapshotData, DateTime executionDateTime,
DateTime&
> expirationDateTime)
> at
>
Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(Catalog
ItemContext
> reportContext, ClientRequest session, Warning[]& warnings,
> ParameterInfoCollection& effectiveParameters)
> at
>
Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
> reportContext, ClientRequest session, Warning[]& warnings,
> ParameterInfoCollection& effectiveParameters, String[]&
secondaryStreamNames)
> -- End of inner exception stack trace --
>|||That did it. Thanks SO much for your response. Now the executions of each
individual parameter combination run serially and don't cause deadlocks.
I did some research on that config file setting you suggested, Teo. Here's
what I found:
MaxQueueThreads
Specifies the maximum number of threads dedicated to polling the event table
in the report server database.
Range: 0 to max integer.
The default is 0.
So if I understand correctly, this setting will ONLY affect the number of
threads used to process events like the fulfilling of subscriptions. Is that
correct? It will not impact performance of multiple users executing and
viewing reports on demand and at the same time, right?|||This is my understanding as well but verify it using the Performance
Monitor.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"FurmanGG" <FurmanGG@.discussions.microsoft.com> wrote in message
news:C9EF39EE-1638-47E9-AE5F-24896700A73D@.microsoft.com...
> That did it. Thanks SO much for your response. Now the executions of each
> individual parameter combination run serially and don't cause deadlocks.
> I did some research on that config file setting you suggested, Teo. Here's
> what I found:
> MaxQueueThreads
> Specifies the maximum number of threads dedicated to polling the event
table
> in the report server database.
> Range: 0 to max integer.
> The default is 0.
> So if I understand correctly, this setting will ONLY affect the number of
> threads used to process events like the fulfilling of subscriptions. Is
that
> correct? It will not impact performance of multiple users executing and
> viewing reports on demand and at the same time, right?
underlying query is fairly expensive, so I want to cache the dataset every
morning after I expire yesterday's cache. So I set up a data-driven
subscription to run every morning and execute all the parameter combinations
and deliver it to the Null delivery extension. The problem is that when the
scheduled time rolls around, it tries to run all 50 parameter combinations at
once. (Actually, it looks like it runs 2 or 3 combinations a second without
waiting for the first one to finish.) The query of the data sources run fine,
but I get a deadlock when Reporting Services tries to write the dataset to
the cache. Somewhere between 10% and 50% of the 50 fail every day. The logs
show a standard deadlock error. The error is below.
Is there any config file setting to tell RS to retry writing to the cache a
few times before giving up because of a deadlock? Is this possibly a SP2 fix?
Or is there any way to tell Reporting Services to run the 50 executions
serially instead of concurrently? Or do I need to investigate creating some
custom code to execute and cache the reports on schedule (so I can make it
execute them serially)?
Please let me know if you need more info... or if you need something from
the SQL Server logs. Thanks in advance.
--
ReportingServicesService!library!2e72c!10/28/2004-21:25:21:: e ERROR:
Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Data.SqlClient.SqlException: Transaction (Process ID
132) was deadlocked on lock resources with another process and has been
chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.DBInterface.AddReportToExecutionCache(Guid
reportId, ReportSnapshot snapshotData, DateTime executionDateTime, DateTime&
expirationDateTime)
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)
-- End of inner exception stack trace --Hi,
Try setting MaxQueueThreads to 1 in the RSReportServer.config file. You may
want to escalate this to the RS PSS since it looks like a bug to me.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"FurmanGG" <FurmanGG@.discussions.microsoft.com> wrote in message
news:516B456B-0E41-46AA-B775-D3BA1B13C1F0@.microsoft.com...
> I've got a report that can have about 50 possible parameter combinations.
The
> underlying query is fairly expensive, so I want to cache the dataset every
> morning after I expire yesterday's cache. So I set up a data-driven
> subscription to run every morning and execute all the parameter
combinations
> and deliver it to the Null delivery extension. The problem is that when
the
> scheduled time rolls around, it tries to run all 50 parameter combinations
at
> once. (Actually, it looks like it runs 2 or 3 combinations a second
without
> waiting for the first one to finish.) The query of the data sources run
fine,
> but I get a deadlock when Reporting Services tries to write the dataset to
> the cache. Somewhere between 10% and 50% of the 50 fail every day. The
logs
> show a standard deadlock error. The error is below.
> Is there any config file setting to tell RS to retry writing to the cache
a
> few times before giving up because of a deadlock? Is this possibly a SP2
fix?
> Or is there any way to tell Reporting Services to run the 50 executions
> serially instead of concurrently? Or do I need to investigate creating
some
> custom code to execute and cache the reports on schedule (so I can make it
> execute them serially)?
> Please let me know if you need more info... or if you need something from
> the SQL Server logs. Thanks in advance.
> --
> ReportingServicesService!library!2e72c!10/28/2004-21:25:21:: e ERROR:
> Throwing
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details., ;
> Info:
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details. --> System.Data.SqlClient.SqlException: Transaction (Process ID
> 132) was deadlocked on lock resources with another process and has been
> chosen as the deadlock victim. Rerun the transaction.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.DBInterface.AddReportToExecutionCache(Gu
id
> reportId, ReportSnapshot snapshotData, DateTime executionDateTime,
DateTime&
> expirationDateTime)
> at
>
Microsoft.ReportingServices.Library.RSService.RenderAsLiveOrSnapshot(Catalog
ItemContext
> reportContext, ClientRequest session, Warning[]& warnings,
> ParameterInfoCollection& effectiveParameters)
> at
>
Microsoft.ReportingServices.Library.RSService.RenderFirst(CatalogItemContext
> reportContext, ClientRequest session, Warning[]& warnings,
> ParameterInfoCollection& effectiveParameters, String[]&
secondaryStreamNames)
> -- End of inner exception stack trace --
>|||That did it. Thanks SO much for your response. Now the executions of each
individual parameter combination run serially and don't cause deadlocks.
I did some research on that config file setting you suggested, Teo. Here's
what I found:
MaxQueueThreads
Specifies the maximum number of threads dedicated to polling the event table
in the report server database.
Range: 0 to max integer.
The default is 0.
So if I understand correctly, this setting will ONLY affect the number of
threads used to process events like the fulfilling of subscriptions. Is that
correct? It will not impact performance of multiple users executing and
viewing reports on demand and at the same time, right?|||This is my understanding as well but verify it using the Performance
Monitor.
--
Hope this helps.
---
Teo Lachev, MVP [SQL Server], MCSD, MCT
Author: "Microsoft Reporting Services in Action"
Publisher website: http://www.manning.com/lachev
Buy it from Amazon.com: http://shrinkster.com/eq
Home page and blog: http://www.prologika.com/
---
"FurmanGG" <FurmanGG@.discussions.microsoft.com> wrote in message
news:C9EF39EE-1638-47E9-AE5F-24896700A73D@.microsoft.com...
> That did it. Thanks SO much for your response. Now the executions of each
> individual parameter combination run serially and don't cause deadlocks.
> I did some research on that config file setting you suggested, Teo. Here's
> what I found:
> MaxQueueThreads
> Specifies the maximum number of threads dedicated to polling the event
table
> in the report server database.
> Range: 0 to max integer.
> The default is 0.
> So if I understand correctly, this setting will ONLY affect the number of
> threads used to process events like the fulfilling of subscriptions. Is
that
> correct? It will not impact performance of multiple users executing and
> viewing reports on demand and at the same time, right?
BUG: Cannot create subscription as NT AUTHORITY\NETWORK SERVICE
Platform:
Windows 2003 Server Enterprise Edition
SQL Server 2000 Developer Edition SP 3
Reporting Services 2000 Developer Edition SP 2
Hi,
I believe I have encountered a bug in Reporting Services and SQL Server.
To reproduce:
Set the Reporting Service Web Service to run as NT AUTHORITY\NETWORK SERVICE
(I believe this is the default on Windows 2003 server as opposed to the
local ASPNET account) using rsconfig.exe, et al.
Make sure NT AUTHORITY\NETWORK SERVICE has RSExecRole privilege on the
Report Server database, Report Server temp database, master, and msdb.
Then try and create a report subscription. I receive this error:
An internal error occurred on the report server. See the error log for more
details. (rsInternalError) The specified '@.owner_login_name' is invalid
(valid values are returned by sp_helplogins[excluding Windows NT groups]).
My guess is that when the Report Server tries to create a subscription it
does so by invoking sp_add_job/sp_verify_job, this then fails because NT
AUTHORITY\NETWORK SERVICE is a Windows Group. I believe the actual error
above is thrown by the stored procedure, sp_verify_job:
Server: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 198
The specified '@.owner_login_name' is invalid (valid values are returned by
sp_helplogins [excluding Windows NT groups]).
or
From sp_verify_job:
-- Now just check that the login id is valid (ie. it exists and isn't an NT
group)
IF (@.owner_sid IS NULL) OR (EXISTS (SELECT *
FROM master.dbo.syslogins
WHERE (sid = @.owner_sid)
AND (isntgroup <> 0)))
BEGIN
-- NOTE: In the following message we quote @.owner_login_name instead of
@.owner_sid
-- since this is the parameter the user passed to the calling SP
(ie. either
-- sp_add_job or sp_update_job)
SELECT @.res_valid_range = FORMATMESSAGE(14203)
RAISERROR(14234, -1, -1, '@.owner_login_name', @.res_valid_range)
RETURN(1) -- Failure
END
Thanks,
Bryan"BDB" <bdb@.reply.to.group.com> wrote in message
news:OJi2X7QnFHA.3900@.TK2MSFTNGP09.phx.gbl...
> Platform:
> Windows 2003 Server Enterprise Edition
> SQL Server 2000 Developer Edition SP 3
> Reporting Services 2000 Developer Edition SP 2
> Hi,
> I believe I have encountered a bug in Reporting Services and SQL Server.
> To reproduce:
> Set the Reporting Service Web Service to run as NT AUTHORITY\NETWORK
> SERVICE (I believe this is the default on Windows 2003 server as opposed
> to the local ASPNET account) using rsconfig.exe, et al.
> Make sure NT AUTHORITY\NETWORK SERVICE has RSExecRole privilege on the
> Report Server database, Report Server temp database, master, and msdb.
> Then try and create a report subscription. I receive this error:
> An internal error occurred on the report server. See the error log for
> more details. (rsInternalError) The specified '@.owner_login_name' is
> invalid (valid values are returned by sp_helplogins[excluding Windows NT
> groups]).
>
> My guess is that when the Report Server tries to create a subscription it
> does so by invoking sp_add_job/sp_verify_job, this then fails because NT
> AUTHORITY\NETWORK SERVICE is a Windows Group. I believe the actual error
> above is thrown by the stored procedure, sp_verify_job:
> Server: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 198
> The specified '@.owner_login_name' is invalid (valid values are returned by
> sp_helplogins [excluding Windows NT groups]).
> or
> From sp_verify_job:
> -- Now just check that the login id is valid (ie. it exists and isn't an
> NT group)
> IF (@.owner_sid IS NULL) OR (EXISTS (SELECT *
> FROM master.dbo.syslogins
> WHERE (sid = @.owner_sid)
> AND (isntgroup <> 0)))
> BEGIN
> -- NOTE: In the following message we quote @.owner_login_name instead of
> @.owner_sid
> -- since this is the parameter the user passed to the calling SP
> (ie. either
> -- sp_add_job or sp_update_job)
> SELECT @.res_valid_range = FORMATMESSAGE(14203)
> RAISERROR(14234, -1, -1, '@.owner_login_name', @.res_valid_range)
> RETURN(1) -- Failure
> END
>
> Thanks,
> Bryan
>
This bug was fixed (hacked, IMO) in SQL Server 2000 SP4. I have no idea if
a KB article was ever published.|||We've applied SP4 for SQL and still have the error. How did you "fix" it?
--
Thanks,
CGW
"BDB" wrote:
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:OJi2X7QnFHA.3900@.TK2MSFTNGP09.phx.gbl...
> > Platform:
> > Windows 2003 Server Enterprise Edition
> > SQL Server 2000 Developer Edition SP 3
> > Reporting Services 2000 Developer Edition SP 2
> >
> > Hi,
> >
> > I believe I have encountered a bug in Reporting Services and SQL Server.
> >
> > To reproduce:
> >
> > Set the Reporting Service Web Service to run as NT AUTHORITY\NETWORK
> > SERVICE (I believe this is the default on Windows 2003 server as opposed
> > to the local ASPNET account) using rsconfig.exe, et al.
> >
> > Make sure NT AUTHORITY\NETWORK SERVICE has RSExecRole privilege on the
> > Report Server database, Report Server temp database, master, and msdb.
> >
> > Then try and create a report subscription. I receive this error:
> >
> > An internal error occurred on the report server. See the error log for
> > more details. (rsInternalError) The specified '@.owner_login_name' is
> > invalid (valid values are returned by sp_helplogins[excluding Windows NT
> > groups]).
> >
> >
> >
> > My guess is that when the Report Server tries to create a subscription it
> > does so by invoking sp_add_job/sp_verify_job, this then fails because NT
> > AUTHORITY\NETWORK SERVICE is a Windows Group. I believe the actual error
> > above is thrown by the stored procedure, sp_verify_job:
> >
> > Server: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 198
> > The specified '@.owner_login_name' is invalid (valid values are returned by
> > sp_helplogins [excluding Windows NT groups]).
> >
> > or
> >
> > From sp_verify_job:
> >
> > -- Now just check that the login id is valid (ie. it exists and isn't an
> > NT group)
> > IF (@.owner_sid IS NULL) OR (EXISTS (SELECT *
> > FROM master.dbo.syslogins
> > WHERE (sid = @.owner_sid)
> > AND (isntgroup <> 0)))
> > BEGIN
> > -- NOTE: In the following message we quote @.owner_login_name instead of
> > @.owner_sid
> > -- since this is the parameter the user passed to the calling SP
> > (ie. either
> > -- sp_add_job or sp_update_job)
> > SELECT @.res_valid_range = FORMATMESSAGE(14203)
> > RAISERROR(14234, -1, -1, '@.owner_login_name', @.res_valid_range)
> > RETURN(1) -- Failure
> > END
> >
> >
> > Thanks,
> > Bryan
> >
> This bug was fixed (hacked, IMO) in SQL Server 2000 SP4. I have no idea if
> a KB article was ever published.
>
>
Windows 2003 Server Enterprise Edition
SQL Server 2000 Developer Edition SP 3
Reporting Services 2000 Developer Edition SP 2
Hi,
I believe I have encountered a bug in Reporting Services and SQL Server.
To reproduce:
Set the Reporting Service Web Service to run as NT AUTHORITY\NETWORK SERVICE
(I believe this is the default on Windows 2003 server as opposed to the
local ASPNET account) using rsconfig.exe, et al.
Make sure NT AUTHORITY\NETWORK SERVICE has RSExecRole privilege on the
Report Server database, Report Server temp database, master, and msdb.
Then try and create a report subscription. I receive this error:
An internal error occurred on the report server. See the error log for more
details. (rsInternalError) The specified '@.owner_login_name' is invalid
(valid values are returned by sp_helplogins[excluding Windows NT groups]).
My guess is that when the Report Server tries to create a subscription it
does so by invoking sp_add_job/sp_verify_job, this then fails because NT
AUTHORITY\NETWORK SERVICE is a Windows Group. I believe the actual error
above is thrown by the stored procedure, sp_verify_job:
Server: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 198
The specified '@.owner_login_name' is invalid (valid values are returned by
sp_helplogins [excluding Windows NT groups]).
or
From sp_verify_job:
-- Now just check that the login id is valid (ie. it exists and isn't an NT
group)
IF (@.owner_sid IS NULL) OR (EXISTS (SELECT *
FROM master.dbo.syslogins
WHERE (sid = @.owner_sid)
AND (isntgroup <> 0)))
BEGIN
-- NOTE: In the following message we quote @.owner_login_name instead of
@.owner_sid
-- since this is the parameter the user passed to the calling SP
(ie. either
-- sp_add_job or sp_update_job)
SELECT @.res_valid_range = FORMATMESSAGE(14203)
RAISERROR(14234, -1, -1, '@.owner_login_name', @.res_valid_range)
RETURN(1) -- Failure
END
Thanks,
Bryan"BDB" <bdb@.reply.to.group.com> wrote in message
news:OJi2X7QnFHA.3900@.TK2MSFTNGP09.phx.gbl...
> Platform:
> Windows 2003 Server Enterprise Edition
> SQL Server 2000 Developer Edition SP 3
> Reporting Services 2000 Developer Edition SP 2
> Hi,
> I believe I have encountered a bug in Reporting Services and SQL Server.
> To reproduce:
> Set the Reporting Service Web Service to run as NT AUTHORITY\NETWORK
> SERVICE (I believe this is the default on Windows 2003 server as opposed
> to the local ASPNET account) using rsconfig.exe, et al.
> Make sure NT AUTHORITY\NETWORK SERVICE has RSExecRole privilege on the
> Report Server database, Report Server temp database, master, and msdb.
> Then try and create a report subscription. I receive this error:
> An internal error occurred on the report server. See the error log for
> more details. (rsInternalError) The specified '@.owner_login_name' is
> invalid (valid values are returned by sp_helplogins[excluding Windows NT
> groups]).
>
> My guess is that when the Report Server tries to create a subscription it
> does so by invoking sp_add_job/sp_verify_job, this then fails because NT
> AUTHORITY\NETWORK SERVICE is a Windows Group. I believe the actual error
> above is thrown by the stored procedure, sp_verify_job:
> Server: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 198
> The specified '@.owner_login_name' is invalid (valid values are returned by
> sp_helplogins [excluding Windows NT groups]).
> or
> From sp_verify_job:
> -- Now just check that the login id is valid (ie. it exists and isn't an
> NT group)
> IF (@.owner_sid IS NULL) OR (EXISTS (SELECT *
> FROM master.dbo.syslogins
> WHERE (sid = @.owner_sid)
> AND (isntgroup <> 0)))
> BEGIN
> -- NOTE: In the following message we quote @.owner_login_name instead of
> @.owner_sid
> -- since this is the parameter the user passed to the calling SP
> (ie. either
> -- sp_add_job or sp_update_job)
> SELECT @.res_valid_range = FORMATMESSAGE(14203)
> RAISERROR(14234, -1, -1, '@.owner_login_name', @.res_valid_range)
> RETURN(1) -- Failure
> END
>
> Thanks,
> Bryan
>
This bug was fixed (hacked, IMO) in SQL Server 2000 SP4. I have no idea if
a KB article was ever published.|||We've applied SP4 for SQL and still have the error. How did you "fix" it?
--
Thanks,
CGW
"BDB" wrote:
> "BDB" <bdb@.reply.to.group.com> wrote in message
> news:OJi2X7QnFHA.3900@.TK2MSFTNGP09.phx.gbl...
> > Platform:
> > Windows 2003 Server Enterprise Edition
> > SQL Server 2000 Developer Edition SP 3
> > Reporting Services 2000 Developer Edition SP 2
> >
> > Hi,
> >
> > I believe I have encountered a bug in Reporting Services and SQL Server.
> >
> > To reproduce:
> >
> > Set the Reporting Service Web Service to run as NT AUTHORITY\NETWORK
> > SERVICE (I believe this is the default on Windows 2003 server as opposed
> > to the local ASPNET account) using rsconfig.exe, et al.
> >
> > Make sure NT AUTHORITY\NETWORK SERVICE has RSExecRole privilege on the
> > Report Server database, Report Server temp database, master, and msdb.
> >
> > Then try and create a report subscription. I receive this error:
> >
> > An internal error occurred on the report server. See the error log for
> > more details. (rsInternalError) The specified '@.owner_login_name' is
> > invalid (valid values are returned by sp_helplogins[excluding Windows NT
> > groups]).
> >
> >
> >
> > My guess is that when the Report Server tries to create a subscription it
> > does so by invoking sp_add_job/sp_verify_job, this then fails because NT
> > AUTHORITY\NETWORK SERVICE is a Windows Group. I believe the actual error
> > above is thrown by the stored procedure, sp_verify_job:
> >
> > Server: Msg 14234, Level 16, State 1, Procedure sp_verify_job, Line 198
> > The specified '@.owner_login_name' is invalid (valid values are returned by
> > sp_helplogins [excluding Windows NT groups]).
> >
> > or
> >
> > From sp_verify_job:
> >
> > -- Now just check that the login id is valid (ie. it exists and isn't an
> > NT group)
> > IF (@.owner_sid IS NULL) OR (EXISTS (SELECT *
> > FROM master.dbo.syslogins
> > WHERE (sid = @.owner_sid)
> > AND (isntgroup <> 0)))
> > BEGIN
> > -- NOTE: In the following message we quote @.owner_login_name instead of
> > @.owner_sid
> > -- since this is the parameter the user passed to the calling SP
> > (ie. either
> > -- sp_add_job or sp_update_job)
> > SELECT @.res_valid_range = FORMATMESSAGE(14203)
> > RAISERROR(14234, -1, -1, '@.owner_login_name', @.res_valid_range)
> > RETURN(1) -- Failure
> > END
> >
> >
> > Thanks,
> > Bryan
> >
> This bug was fixed (hacked, IMO) in SQL Server 2000 SP4. I have no idea if
> a KB article was ever published.
>
>
Wednesday, March 7, 2012
Bug found when updating a one-time scheduled subscription...
When you first create a data-driven sub and schedule it to run "one time" it
works fine. Later, however, if you edit it to try and re-run it, you run
into a problem if the subscription is set to run on a one-time basis only
again. You select "one time" as the schedule and set the time you want it to
fire off. However you can't enter a date. Instead of picking up today as
the default like it does when you first create the subscription, it keeps the
same date that you originally used when you first set it up. So if you are
editing a one-time scheduled subscription and you didn't create the
subscription that same day, the schedule you just created is already in the
past and thus never fires. You can confirm this by checking the "startdate"
field of the "schedule table". I tried working around it by updating the
table manually...
Update Schedule
Set StartDate = '2004-11-10 14:10'
Where ScheduleID = 'whatever'
... but it still didn't fire off the job. Anyone else seen this?
sebring1130you can use the soap api and call rs.firevent on it
"sebring1130" wrote:
> When you first create a data-driven sub and schedule it to run "one time" it
> works fine. Later, however, if you edit it to try and re-run it, you run
> into a problem if the subscription is set to run on a one-time basis only
> again. You select "one time" as the schedule and set the time you want it to
> fire off. However you can't enter a date. Instead of picking up today as
> the default like it does when you first create the subscription, it keeps the
> same date that you originally used when you first set it up. So if you are
> editing a one-time scheduled subscription and you didn't create the
> subscription that same day, the schedule you just created is already in the
> past and thus never fires. You can confirm this by checking the "startdate"
> field of the "schedule table". I tried working around it by updating the
> table manually...
> Update Schedule
> Set StartDate = '2004-11-10 14:10'
> Where ScheduleID = 'whatever'
> ... but it still didn't fire off the job. Anyone else seen this?
> sebring1130
>
>
works fine. Later, however, if you edit it to try and re-run it, you run
into a problem if the subscription is set to run on a one-time basis only
again. You select "one time" as the schedule and set the time you want it to
fire off. However you can't enter a date. Instead of picking up today as
the default like it does when you first create the subscription, it keeps the
same date that you originally used when you first set it up. So if you are
editing a one-time scheduled subscription and you didn't create the
subscription that same day, the schedule you just created is already in the
past and thus never fires. You can confirm this by checking the "startdate"
field of the "schedule table". I tried working around it by updating the
table manually...
Update Schedule
Set StartDate = '2004-11-10 14:10'
Where ScheduleID = 'whatever'
... but it still didn't fire off the job. Anyone else seen this?
sebring1130you can use the soap api and call rs.firevent on it
"sebring1130" wrote:
> When you first create a data-driven sub and schedule it to run "one time" it
> works fine. Later, however, if you edit it to try and re-run it, you run
> into a problem if the subscription is set to run on a one-time basis only
> again. You select "one time" as the schedule and set the time you want it to
> fire off. However you can't enter a date. Instead of picking up today as
> the default like it does when you first create the subscription, it keeps the
> same date that you originally used when you first set it up. So if you are
> editing a one-time scheduled subscription and you didn't create the
> subscription that same day, the schedule you just created is already in the
> past and thus never fires. You can confirm this by checking the "startdate"
> field of the "schedule table". I tried working around it by updating the
> table manually...
> Update Schedule
> Set StartDate = '2004-11-10 14:10'
> Where ScheduleID = 'whatever'
> ... but it still didn't fire off the job. Anyone else seen this?
> sebring1130
>
>
Sunday, February 19, 2012
Broken link in e-mail subscription
I have scheduled the first report at this customers site to send out e-mails
of reports. It is sending out the report just fine and including the PDF
file that I requested however I also checked the Include Link box in the
schedule because of the requirements of the users wanting to hide details in
the e-mailed report and wanting to link to the report and then drill down to
see the details only when necessary.
When the e-mail is sent it doesn't formulate the URL correctly and says the
following:
The report is accessible at the following address:
http://localhost/reports?%2fAccounting%.........
The closest thing I've found online to resolve this was this link:
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/ReadmeSQL2005.htm
-- See "Incomplete Report Server Configuration on an SSL-Protected Server
Causes Broken Report Links in Report Server E-Mail Notifications" section.
Unfortunately, an examination of the suggestion revealed that we are not
using SSL and when I checked the <UrlRoot> in the RSReportServer.config file
it was set correctly to the server name that I'd want used in replacing
localhost in the URL.
Does anyone know how to fix this?You'll actually need to modify the rswebapplication.config file for that
setting.
The section should look like the following to get your issue resolved:
<ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Broken link in e-mail subscription
> I have scheduled the first report at this customers site to send out
e-mails
> of reports. It is sending out the report just fine and including the PDF
> file that I requested however I also checked the Include Link box in the
> schedule because of the requirements of the users wanting to hide details
in
> the e-mailed report and wanting to link to the report and then drill down
to
> see the details only when necessary.
> When the e-mail is sent it doesn't formulate the URL correctly and says
the
> following:
> The report is accessible at the following address:
> http://localhost/reports?%2fAccounting%.........
> The closest thing I've found online to resolve this was this link:
>
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
25641/ReadmeSQL2005.htm
> -- See "Incomplete Report Server Configuration on an SSL-Protected
Server
> Causes Broken Report Links in Report Server E-Mail Notifications" section.
> Unfortunately, an examination of the suggestion revealed that we are not
> using SSL and when I checked the <UrlRoot> in the RSReportServer.config
file
> it was set correctly to the server name that I'd want used in replacing
> localhost in the URL.
> Does anyone know how to fix this?
>|||Thanks for the quick reply!
That didn't work; the e-mailed report still says localhost. Does it require
a reboot of the server or the service?
I changed two files named rswebapplication.config located here on the server:
C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportManager
and
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager
Any ideas?
Thanks,
Keith
"Chris Alton [MSFT]" wrote:
> You'll actually need to modify the rswebapplication.config file for that
> setting.
> The section should look like the following to get your issue resolved:
> <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> > Thread-Topic: Broken link in e-mail subscription
> >
> > I have scheduled the first report at this customers site to send out
> e-mails
> > of reports. It is sending out the report just fine and including the PDF
> > file that I requested however I also checked the Include Link box in the
> > schedule because of the requirements of the users wanting to hide details
> in
> > the e-mailed report and wanting to link to the report and then drill down
> to
> > see the details only when necessary.
> >
> > When the e-mail is sent it doesn't formulate the URL correctly and says
> the
> > following:
> >
> > The report is accessible at the following address:
> > http://localhost/reports?%2fAccounting%.........
> >
> > The closest thing I've found online to resolve this was this link:
> >
> http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> 25641/ReadmeSQL2005.htm
> > -- See "Incomplete Report Server Configuration on an SSL-Protected
> Server
> > Causes Broken Report Links in Report Server E-Mail Notifications" section.
> >
> > Unfortunately, an examination of the suggestion revealed that we are not
> > using SSL and when I checked the <UrlRoot> in the RSReportServer.config
> file
> > it was set correctly to the server name that I'd want used in replacing
> > localhost in the URL.
> >
> > Does anyone know how to fix this?
> >
> >
>|||If you have two instances of Reporting Services installed then you need to
figure out which instance you are connecting to and modify the correct
configuration files. Also, if you modified the rsreportserver.config file
for the wrong instance then that could have caused it as well.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Broken link in e-mail subscription
> thread-index: AcgKl6UBYx8q8qj4SQiu7zquybnHhQ==> X-WBNR-Posting-Host: 64.4.185.178
> From: =?Utf-8?B?Z3JlZW5tdG5zdW4=?= <greenmtnsun@.discussions.microsoft.com>
> References: <F510629C-E0E1-4162-9845-87980E21B924@.microsoft.com>
<8SY8AQpCIHA.360@.TK2MSFTNGHUB02.phx.gbl>
> Subject: RE: Broken link in e-mail subscription
> Thanks for the quick reply!
> That didn't work; the e-mailed report still says localhost. Does it
require
> a reboot of the server or the service?
> I changed two files named rswebapplication.config located here on the
server:
> C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\ReportManager
> and
> C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportManager
> Any ideas?
> Thanks,
> Keith
>
> "Chris Alton [MSFT]" wrote:
> > You'll actually need to modify the rswebapplication.config file for
that
> > setting.
> >
> > The section should look like the following to get your issue resolved:
> > <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > --
> > > Thread-Topic: Broken link in e-mail subscription
> > >
> > > I have scheduled the first report at this customers site to send out
> > e-mails
> > > of reports. It is sending out the report just fine and including the
PDF
> > > file that I requested however I also checked the Include Link box in
the
> > > schedule because of the requirements of the users wanting to hide
details
> > in
> > > the e-mailed report and wanting to link to the report and then drill
down
> > to
> > > see the details only when necessary.
> > >
> > > When the e-mail is sent it doesn't formulate the URL correctly and
says
> > the
> > > following:
> > >
> > > The report is accessible at the following address:
> > > http://localhost/reports?%2fAccounting%.........
> > >
> > > The closest thing I've found online to resolve this was this link:
> > >
> >
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> > 25641/ReadmeSQL2005.htm
> > > -- See "Incomplete Report Server Configuration on an SSL-Protected
> > Server
> > > Causes Broken Report Links in Report Server E-Mail Notifications"
section.
> > >
> > > Unfortunately, an examination of the suggestion revealed that we are
not
> > > using SSL and when I checked the <UrlRoot> in the
RSReportServer.config
> > file
> > > it was set correctly to the server name that I'd want used in
replacing
> > > localhost in the URL.
> > >
> > > Does anyone know how to fix this?
> > >
> > >
> >
> >
>|||Welp, I didn't know I had a second instance, but you were right! I have it
fixed.
One thing though, I couldn't google a fix to this problem. Perhaps there is
something that could be added to BOL? Or did I miss it?
"Chris Alton [MSFT]" wrote:
> If you have two instances of Reporting Services installed then you need to
> figure out which instance you are connecting to and modify the correct
> configuration files. Also, if you modified the rsreportserver.config file
> for the wrong instance then that could have caused it as well.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> > Thread-Topic: Broken link in e-mail subscription
> > thread-index: AcgKl6UBYx8q8qj4SQiu7zquybnHhQ==> > X-WBNR-Posting-Host: 64.4.185.178
> > From: =?Utf-8?B?Z3JlZW5tdG5zdW4=?= <greenmtnsun@.discussions.microsoft.com>
> > References: <F510629C-E0E1-4162-9845-87980E21B924@.microsoft.com>
> <8SY8AQpCIHA.360@.TK2MSFTNGHUB02.phx.gbl>
> > Subject: RE: Broken link in e-mail subscription
> >
> > Thanks for the quick reply!
> >
> > That didn't work; the e-mailed report still says localhost. Does it
> require
> > a reboot of the server or the service?
> >
> > I changed two files named rswebapplication.config located here on the
> server:
> > C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportManager
> > and
> > C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportManager
> >
> > Any ideas?
> >
> > Thanks,
> > Keith
> >
> >
> > "Chris Alton [MSFT]" wrote:
> >
> > > You'll actually need to modify the rswebapplication.config file for
> that
> > > setting.
> > >
> > > The section should look like the following to get your issue resolved:
> > > <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> > > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > > --
> > > Chris Alton, Microsoft Corp.
> > > SQL Server Developer Support Engineer
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > --
> > > > Thread-Topic: Broken link in e-mail subscription
> > > >
> > > > I have scheduled the first report at this customers site to send out
> > > e-mails
> > > > of reports. It is sending out the report just fine and including the
> PDF
> > > > file that I requested however I also checked the Include Link box in
> the
> > > > schedule because of the requirements of the users wanting to hide
> details
> > > in
> > > > the e-mailed report and wanting to link to the report and then drill
> down
> > > to
> > > > see the details only when necessary.
> > > >
> > > > When the e-mail is sent it doesn't formulate the URL correctly and
> says
> > > the
> > > > following:
> > > >
> > > > The report is accessible at the following address:
> > > > http://localhost/reports?%2fAccounting%.........
> > > >
> > > > The closest thing I've found online to resolve this was this link:
> > > >
> > >
> http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> > > 25641/ReadmeSQL2005.htm
> > > > -- See "Incomplete Report Server Configuration on an SSL-Protected
> > > Server
> > > > Causes Broken Report Links in Report Server E-Mail Notifications"
> section.
> > > >
> > > > Unfortunately, an examination of the suggestion revealed that we are
> not
> > > > using SSL and when I checked the <UrlRoot> in the
> RSReportServer.config
> > > file
> > > > it was set correctly to the server name that I'd want used in
> replacing
> > > > localhost in the URL.
> > > >
> > > > Does anyone know how to fix this?
> > > >
> > > >
> > >
> > >
> >
>|||I'm sure its in Books Online somewhere. It has to get the link for the
report from somewhere and if it is configured as localhost in all the
configuration files then its going to use localhost.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Broken link in e-mail subscription
> Welp, I didn't know I had a second instance, but you were right! I have
it
> fixed.
> One thing though, I couldn't google a fix to this problem. Perhaps there
is
> something that could be added to BOL? Or did I miss it?
> "Chris Alton [MSFT]" wrote:
> > If you have two instances of Reporting Services installed then you need
to
> > figure out which instance you are connecting to and modify the correct
> > configuration files. Also, if you modified the rsreportserver.config
file
> > for the wrong instance then that could have caused it as well.
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > --
> > > Thread-Topic: Broken link in e-mail subscription
> > > thread-index: AcgKl6UBYx8q8qj4SQiu7zquybnHhQ==> > > X-WBNR-Posting-Host: 64.4.185.178
> > > From: =?Utf-8?B?Z3JlZW5tdG5zdW4=?=<greenmtnsun@.discussions.microsoft.com>
> > > References: <F510629C-E0E1-4162-9845-87980E21B924@.microsoft.com>
> > <8SY8AQpCIHA.360@.TK2MSFTNGHUB02.phx.gbl>
> > > Subject: RE: Broken link in e-mail subscription
> > >
> > > Thanks for the quick reply!
> > >
> > > That didn't work; the e-mailed report still says localhost. Does it
> > require
> > > a reboot of the server or the service?
> > >
> > > I changed two files named rswebapplication.config located here on the
> > server:
> > > C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> > Services\ReportManager
> > > and
> > > C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> > Services\ReportManager
> > >
> > > Any ideas?
> > >
> > > Thanks,
> > > Keith
> > >
> > >
> > > "Chris Alton [MSFT]" wrote:
> > >
> > > > You'll actually need to modify the rswebapplication.config file for
> > that
> > > > setting.
> > > >
> > > > The section should look like the following to get your issue
resolved:
> > > > <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> > > > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > > > --
> > > > Chris Alton, Microsoft Corp.
> > > > SQL Server Developer Support Engineer
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > > --
> > > > > Thread-Topic: Broken link in e-mail subscription
> > > > >
> > > > > I have scheduled the first report at this customers site to send
out
> > > > e-mails
> > > > > of reports. It is sending out the report just fine and including
the
> > PDF
> > > > > file that I requested however I also checked the Include Link box
in
> > the
> > > > > schedule because of the requirements of the users wanting to hide
> > details
> > > > in
> > > > > the e-mailed report and wanting to link to the report and then
drill
> > down
> > > > to
> > > > > see the details only when necessary.
> > > > >
> > > > > When the e-mail is sent it doesn't formulate the URL correctly
and
> > says
> > > > the
> > > > > following:
> > > > >
> > > > > The report is accessible at the following address:
> > > > > http://localhost/reports?%2fAccounting%.........
> > > > >
> > > > > The closest thing I've found online to resolve this was this link:
> > > > >
> > > >
> >
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> > > > 25641/ReadmeSQL2005.htm
> > > > > -- See "Incomplete Report Server Configuration on an
SSL-Protected
> > > > Server
> > > > > Causes Broken Report Links in Report Server E-Mail Notifications"
> > section.
> > > > >
> > > > > Unfortunately, an examination of the suggestion revealed that we
are
> > not
> > > > > using SSL and when I checked the <UrlRoot> in the
> > RSReportServer.config
> > > > file
> > > > > it was set correctly to the server name that I'd want used in
> > replacing
> > > > > localhost in the URL.
> > > > >
> > > > > Does anyone know how to fix this?
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>
of reports. It is sending out the report just fine and including the PDF
file that I requested however I also checked the Include Link box in the
schedule because of the requirements of the users wanting to hide details in
the e-mailed report and wanting to link to the report and then drill down to
see the details only when necessary.
When the e-mail is sent it doesn't formulate the URL correctly and says the
following:
The report is accessible at the following address:
http://localhost/reports?%2fAccounting%.........
The closest thing I've found online to resolve this was this link:
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad125641/ReadmeSQL2005.htm
-- See "Incomplete Report Server Configuration on an SSL-Protected Server
Causes Broken Report Links in Report Server E-Mail Notifications" section.
Unfortunately, an examination of the suggestion revealed that we are not
using SSL and when I checked the <UrlRoot> in the RSReportServer.config file
it was set correctly to the server name that I'd want used in replacing
localhost in the URL.
Does anyone know how to fix this?You'll actually need to modify the rswebapplication.config file for that
setting.
The section should look like the following to get your issue resolved:
<ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Broken link in e-mail subscription
> I have scheduled the first report at this customers site to send out
e-mails
> of reports. It is sending out the report just fine and including the PDF
> file that I requested however I also checked the Include Link box in the
> schedule because of the requirements of the users wanting to hide details
in
> the e-mailed report and wanting to link to the report and then drill down
to
> see the details only when necessary.
> When the e-mail is sent it doesn't formulate the URL correctly and says
the
> following:
> The report is accessible at the following address:
> http://localhost/reports?%2fAccounting%.........
> The closest thing I've found online to resolve this was this link:
>
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
25641/ReadmeSQL2005.htm
> -- See "Incomplete Report Server Configuration on an SSL-Protected
Server
> Causes Broken Report Links in Report Server E-Mail Notifications" section.
> Unfortunately, an examination of the suggestion revealed that we are not
> using SSL and when I checked the <UrlRoot> in the RSReportServer.config
file
> it was set correctly to the server name that I'd want used in replacing
> localhost in the URL.
> Does anyone know how to fix this?
>|||Thanks for the quick reply!
That didn't work; the e-mailed report still says localhost. Does it require
a reboot of the server or the service?
I changed two files named rswebapplication.config located here on the server:
C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportManager
and
C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager
Any ideas?
Thanks,
Keith
"Chris Alton [MSFT]" wrote:
> You'll actually need to modify the rswebapplication.config file for that
> setting.
> The section should look like the following to get your issue resolved:
> <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> > Thread-Topic: Broken link in e-mail subscription
> >
> > I have scheduled the first report at this customers site to send out
> e-mails
> > of reports. It is sending out the report just fine and including the PDF
> > file that I requested however I also checked the Include Link box in the
> > schedule because of the requirements of the users wanting to hide details
> in
> > the e-mailed report and wanting to link to the report and then drill down
> to
> > see the details only when necessary.
> >
> > When the e-mail is sent it doesn't formulate the URL correctly and says
> the
> > following:
> >
> > The report is accessible at the following address:
> > http://localhost/reports?%2fAccounting%.........
> >
> > The closest thing I've found online to resolve this was this link:
> >
> http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> 25641/ReadmeSQL2005.htm
> > -- See "Incomplete Report Server Configuration on an SSL-Protected
> Server
> > Causes Broken Report Links in Report Server E-Mail Notifications" section.
> >
> > Unfortunately, an examination of the suggestion revealed that we are not
> > using SSL and when I checked the <UrlRoot> in the RSReportServer.config
> file
> > it was set correctly to the server name that I'd want used in replacing
> > localhost in the URL.
> >
> > Does anyone know how to fix this?
> >
> >
>|||If you have two instances of Reporting Services installed then you need to
figure out which instance you are connecting to and modify the correct
configuration files. Also, if you modified the rsreportserver.config file
for the wrong instance then that could have caused it as well.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Broken link in e-mail subscription
> thread-index: AcgKl6UBYx8q8qj4SQiu7zquybnHhQ==> X-WBNR-Posting-Host: 64.4.185.178
> From: =?Utf-8?B?Z3JlZW5tdG5zdW4=?= <greenmtnsun@.discussions.microsoft.com>
> References: <F510629C-E0E1-4162-9845-87980E21B924@.microsoft.com>
<8SY8AQpCIHA.360@.TK2MSFTNGHUB02.phx.gbl>
> Subject: RE: Broken link in e-mail subscription
> Thanks for the quick reply!
> That didn't work; the e-mailed report still says localhost. Does it
require
> a reboot of the server or the service?
> I changed two files named rswebapplication.config located here on the
server:
> C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
Services\ReportManager
> and
> C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
Services\ReportManager
> Any ideas?
> Thanks,
> Keith
>
> "Chris Alton [MSFT]" wrote:
> > You'll actually need to modify the rswebapplication.config file for
that
> > setting.
> >
> > The section should look like the following to get your issue resolved:
> > <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > --
> > > Thread-Topic: Broken link in e-mail subscription
> > >
> > > I have scheduled the first report at this customers site to send out
> > e-mails
> > > of reports. It is sending out the report just fine and including the
> > > file that I requested however I also checked the Include Link box in
the
> > > schedule because of the requirements of the users wanting to hide
details
> > in
> > > the e-mailed report and wanting to link to the report and then drill
down
> > to
> > > see the details only when necessary.
> > >
> > > When the e-mail is sent it doesn't formulate the URL correctly and
says
> > the
> > > following:
> > >
> > > The report is accessible at the following address:
> > > http://localhost/reports?%2fAccounting%.........
> > >
> > > The closest thing I've found online to resolve this was this link:
> > >
> >
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> > 25641/ReadmeSQL2005.htm
> > > -- See "Incomplete Report Server Configuration on an SSL-Protected
> > Server
> > > Causes Broken Report Links in Report Server E-Mail Notifications"
section.
> > >
> > > Unfortunately, an examination of the suggestion revealed that we are
not
> > > using SSL and when I checked the <UrlRoot> in the
RSReportServer.config
> > file
> > > it was set correctly to the server name that I'd want used in
replacing
> > > localhost in the URL.
> > >
> > > Does anyone know how to fix this?
> > >
> > >
> >
> >
>|||Welp, I didn't know I had a second instance, but you were right! I have it
fixed.
One thing though, I couldn't google a fix to this problem. Perhaps there is
something that could be added to BOL? Or did I miss it?
"Chris Alton [MSFT]" wrote:
> If you have two instances of Reporting Services installed then you need to
> figure out which instance you are connecting to and modify the correct
> configuration files. Also, if you modified the rsreportserver.config file
> for the wrong instance then that could have caused it as well.
> --
> Chris Alton, Microsoft Corp.
> SQL Server Developer Support Engineer
> This posting is provided "AS IS" with no warranties, and confers no rights.
> --
> > Thread-Topic: Broken link in e-mail subscription
> > thread-index: AcgKl6UBYx8q8qj4SQiu7zquybnHhQ==> > X-WBNR-Posting-Host: 64.4.185.178
> > From: =?Utf-8?B?Z3JlZW5tdG5zdW4=?= <greenmtnsun@.discussions.microsoft.com>
> > References: <F510629C-E0E1-4162-9845-87980E21B924@.microsoft.com>
> <8SY8AQpCIHA.360@.TK2MSFTNGHUB02.phx.gbl>
> > Subject: RE: Broken link in e-mail subscription
> >
> > Thanks for the quick reply!
> >
> > That didn't work; the e-mailed report still says localhost. Does it
> require
> > a reboot of the server or the service?
> >
> > I changed two files named rswebapplication.config located here on the
> server:
> > C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> Services\ReportManager
> > and
> > C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> Services\ReportManager
> >
> > Any ideas?
> >
> > Thanks,
> > Keith
> >
> >
> > "Chris Alton [MSFT]" wrote:
> >
> > > You'll actually need to modify the rswebapplication.config file for
> that
> > > setting.
> > >
> > > The section should look like the following to get your issue resolved:
> > > <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> > > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > > --
> > > Chris Alton, Microsoft Corp.
> > > SQL Server Developer Support Engineer
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > --
> > > > Thread-Topic: Broken link in e-mail subscription
> > > >
> > > > I have scheduled the first report at this customers site to send out
> > > e-mails
> > > > of reports. It is sending out the report just fine and including the
> > > > file that I requested however I also checked the Include Link box in
> the
> > > > schedule because of the requirements of the users wanting to hide
> details
> > > in
> > > > the e-mailed report and wanting to link to the report and then drill
> down
> > > to
> > > > see the details only when necessary.
> > > >
> > > > When the e-mail is sent it doesn't formulate the URL correctly and
> says
> > > the
> > > > following:
> > > >
> > > > The report is accessible at the following address:
> > > > http://localhost/reports?%2fAccounting%.........
> > > >
> > > > The closest thing I've found online to resolve this was this link:
> > > >
> > >
> http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> > > 25641/ReadmeSQL2005.htm
> > > > -- See "Incomplete Report Server Configuration on an SSL-Protected
> > > Server
> > > > Causes Broken Report Links in Report Server E-Mail Notifications"
> section.
> > > >
> > > > Unfortunately, an examination of the suggestion revealed that we are
> not
> > > > using SSL and when I checked the <UrlRoot> in the
> RSReportServer.config
> > > file
> > > > it was set correctly to the server name that I'd want used in
> replacing
> > > > localhost in the URL.
> > > >
> > > > Does anyone know how to fix this?
> > > >
> > > >
> > >
> > >
> >
>|||I'm sure its in Books Online somewhere. It has to get the link for the
report from somewhere and if it is configured as localhost in all the
configuration files then its going to use localhost.
--
Chris Alton, Microsoft Corp.
SQL Server Developer Support Engineer
This posting is provided "AS IS" with no warranties, and confers no rights.
--
> Thread-Topic: Broken link in e-mail subscription
> Welp, I didn't know I had a second instance, but you were right! I have
it
> fixed.
> One thing though, I couldn't google a fix to this problem. Perhaps there
is
> something that could be added to BOL? Or did I miss it?
> "Chris Alton [MSFT]" wrote:
> > If you have two instances of Reporting Services installed then you need
to
> > figure out which instance you are connecting to and modify the correct
> > configuration files. Also, if you modified the rsreportserver.config
file
> > for the wrong instance then that could have caused it as well.
> > --
> > Chris Alton, Microsoft Corp.
> > SQL Server Developer Support Engineer
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > --
> > > Thread-Topic: Broken link in e-mail subscription
> > > thread-index: AcgKl6UBYx8q8qj4SQiu7zquybnHhQ==> > > X-WBNR-Posting-Host: 64.4.185.178
> > > From: =?Utf-8?B?Z3JlZW5tdG5zdW4=?=<greenmtnsun@.discussions.microsoft.com>
> > > References: <F510629C-E0E1-4162-9845-87980E21B924@.microsoft.com>
> > <8SY8AQpCIHA.360@.TK2MSFTNGHUB02.phx.gbl>
> > > Subject: RE: Broken link in e-mail subscription
> > >
> > > Thanks for the quick reply!
> > >
> > > That didn't work; the e-mailed report still says localhost. Does it
> > require
> > > a reboot of the server or the service?
> > >
> > > I changed two files named rswebapplication.config located here on the
> > server:
> > > C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting
> > Services\ReportManager
> > > and
> > > C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting
> > Services\ReportManager
> > >
> > > Any ideas?
> > >
> > > Thanks,
> > > Keith
> > >
> > >
> > > "Chris Alton [MSFT]" wrote:
> > >
> > > > You'll actually need to modify the rswebapplication.config file for
> > that
> > > > setting.
> > > >
> > > > The section should look like the following to get your issue
resolved:
> > > > <ReportServerUrl>http://SERVERNAME/ReportServer</ReportServerUrl>
> > > > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > > > --
> > > > Chris Alton, Microsoft Corp.
> > > > SQL Server Developer Support Engineer
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > > --
> > > > > Thread-Topic: Broken link in e-mail subscription
> > > > >
> > > > > I have scheduled the first report at this customers site to send
out
> > > > e-mails
> > > > > of reports. It is sending out the report just fine and including
the
> > > > > file that I requested however I also checked the Include Link box
in
> > the
> > > > > schedule because of the requirements of the users wanting to hide
> > details
> > > > in
> > > > > the e-mailed report and wanting to link to the report and then
drill
> > down
> > > > to
> > > > > see the details only when necessary.
> > > > >
> > > > > When the e-mail is sent it doesn't formulate the URL correctly
and
> > says
> > > > the
> > > > > following:
> > > > >
> > > > > The report is accessible at the following address:
> > > > > http://localhost/reports?%2fAccounting%.........
> > > > >
> > > > > The closest thing I've found online to resolve this was this link:
> > > > >
> > > >
> >
http://download.microsoft.com/download/5/0/e/50ec0a69-d69e-4962-b2c9-80bbad1
> > > > 25641/ReadmeSQL2005.htm
> > > > > -- See "Incomplete Report Server Configuration on an
SSL-Protected
> > > > Server
> > > > > Causes Broken Report Links in Report Server E-Mail Notifications"
> > section.
> > > > >
> > > > > Unfortunately, an examination of the suggestion revealed that we
are
> > not
> > > > > using SSL and when I checked the <UrlRoot> in the
> > RSReportServer.config
> > > > file
> > > > > it was set correctly to the server name that I'd want used in
> > replacing
> > > > > localhost in the URL.
> > > > >
> > > > > Does anyone know how to fix this?
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
>
Broken hyperlinks in subscription emails
Users are receiving link-only subscriptions with broken links where the break
always starts with an exclamation mark. It looks like this in email source
view:
<table><tr><td><span>My comment text added to
subscription</span></td></tr></table><table><tr><td><span>The report is
accessible at the following address:</span></td><tr><td><a
href="http://links.10026.com/?link=http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&r!
s%3aParameterLanguage=en-US">http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&rs%3aParameterLanguage=en-US</a></td></tr></table>
Any suggestions how to fix or work around this?I have updated Reporting Services to version 9.00.2040.00 but I am still
getting broken hyperlinks in subscription emails.
"PeterG" wrote:
> Users are receiving link-only subscriptions with broken links where the break
> always starts with an exclamation mark. It looks like this in email source
> view:
> <table><tr><td><span>My comment text added to
> subscription</span></td></tr></table><table><tr><td><span>The report is
> accessible at the following address:</span></td><tr><td><a
> href="http://links.10026.com/?link=http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&r!
> s%3aParameterLanguage=en-US">http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&rs%3aParameterLanguage=en-US</a></td></tr></table>
> Any suggestions how to fix or work around this?
>
always starts with an exclamation mark. It looks like this in email source
view:
<table><tr><td><span>My comment text added to
subscription</span></td></tr></table><table><tr><td><span>The report is
accessible at the following address:</span></td><tr><td><a
href="http://links.10026.com/?link=http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&r!
s%3aParameterLanguage=en-US">http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&rs%3aParameterLanguage=en-US</a></td></tr></table>
Any suggestions how to fix or work around this?I have updated Reporting Services to version 9.00.2040.00 but I am still
getting broken hyperlinks in subscription emails.
"PeterG" wrote:
> Users are receiving link-only subscriptions with broken links where the break
> always starts with an exclamation mark. It looks like this in email source
> view:
> <table><tr><td><span>My comment text added to
> subscription</span></td></tr></table><table><tr><td><span>The report is
> accessible at the following address:</span></td><tr><td><a
> href="http://links.10026.com/?link=http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&r!
> s%3aParameterLanguage=en-US">http://servername/reportportal/viewreport.aspx?%2fEncoded+Report+Name&Par1=Encoded+param+value&&Par2=Encoded+param+value&rs%3aParameterLanguage=en-US</a></td></tr></table>
> Any suggestions how to fix or work around this?
>
Subscribe to:
Posts (Atom)