Showing posts with label subscription. Show all posts
Showing posts with label subscription. Show all posts

Friday, March 30, 2012

Report Distribution

Through report manager I am trying to see if it is possible
to set up a data-driven subscription, that will save the
file on a file share AND notifiy user via email based on values
stored in sql table.

I can get each to work as independent jobs but I want this to
be run as one.

Can this be done? How?

Thanks.

Not out of the box. Each subscription has only one delivery extension it uses. It is not possible to chain delivery extensions.

You can write a custom delivery extension that would do both of these operations. There's a printer delivery sample in the Samples that come with SQL Server 2000 Reporting Services and SQL Server 2005.

-Lukasz


This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi,
Me too wants to have some simillar to your requirement. Have you created some custom delivery extension for this purpose.

Regards;
Rakesh

Report Distribution

Through report manager I am trying to see if it is possible
to set up a data-driven subscription, that will save the
file on a file share AND notifiy user via email based on values
stored in sql table.

I can get each to work as independent jobs but I want this to
be run as one.

Can this be done? How?

Thanks.

Not out of the box. Each subscription has only one delivery extension it uses. It is not possible to chain delivery extensions.

You can write a custom delivery extension that would do both of these operations. There's a printer delivery sample in the Samples that come with SQL Server 2000 Reporting Services and SQL Server 2005.

-Lukasz


This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi,
Me too wants to have some simillar to your requirement. Have you created some custom delivery extension for this purpose.

Regards;
Rakesh

sql

Monday, March 26, 2012

Report Delivery problem with Data Driven Subscription

I created a data driven subscription for a report that will email a copy of the report based on a parameter passed from a table. The report runs successfully as indicated in Report Manager but the email is not delivered. I checked the ReportServerService log file and a message states that the report was sent to the proper email address. There is another log, ReportServerWebApp, that shows the message "The extension Report Server Email does not have a LocalizedNameAttribute" .

I created a regular subscription and it emails the report successfully so it can't be the SMTP server.

Any ideas how I can fix this problem with the Data Driven Subscription? Thank you.

David

I did some further checking. If I send off a second job, it delivers the emailed reports. However, the problem persists with the second job.That is, Reporting Services indicates that the job ran successfully and delivered the reports, but some of the reports are getting stuck in a queue somewhere between the reporting server, the remote SMTP server and Microsoft Exchange.

Is there anyone else having problems with Reporting Services reports not getting fully delivered by a remote SMTP server? Would using a local SMTP server fix the problem?

David

|||Sorry for the delay with replying this. From the SSRS prospective your data driven subscription has been delivered to SMTP server successfully. Then SMTP server failed to deliver e-mal. Any chance that e-mail TO address is build off a data-driven subscription query results and is incorrect? Per every successfully sent e-mail SSRS will write into the service logfile ReportServerService__<Date>.log a line: Email successfully sent to {0}. Can you double check that TO addresses are correct for the cases that you thin are failing?|||

All of the reports are being sent to the same email address. Some get there successfully, others don't make it out of the queue.

David

|||

Then it really looks like a problem with SMTP server. It’s likely not related to SSRS.

-Igor

Report Delivery problem with Data Driven Subscription

I created a data driven subscription for a report that will email a copy of the report based on a parameter passed from a table. The report runs successfully as indicated in Report Manager but the email is not delivered. I checked the ReportServerService log file and a message states that the report was sent to the proper email address. There is another log, ReportServerWebApp, that shows the message "The extension Report Server Email does not have a LocalizedNameAttribute" .

I created a regular subscription and it emails the report successfully so it can't be the SMTP server.

Any ideas how I can fix this problem with the Data Driven Subscription? Thank you.

David

I did some further checking. If I send off a second job, it delivers the emailed reports. However, the problem persists with the second job.That is, Reporting Services indicates that the job ran successfully and delivered the reports, but some of the reports are getting stuck in a queue somewhere between the reporting server, the remote SMTP server and Microsoft Exchange.

Is there anyone else having problems with Reporting Services reports not getting fully delivered by a remote SMTP server? Would using a local SMTP server fix the problem?

David

|||Sorry for the delay with replying this. From the SSRS prospective your data driven subscription has been delivered to SMTP server successfully. Then SMTP server failed to deliver e-mal. Any chance that e-mail TO address is build off a data-driven subscription query results and is incorrect? Per every successfully sent e-mail SSRS will write into the service logfile ReportServerService__<Date>.log a line: Email successfully sent to {0}. Can you double check that TO addresses are correct for the cases that you thin are failing?|||

All of the reports are being sent to the same email address. Some get there successfully, others don't make it out of the queue.

David

|||

Then it really looks like a problem with SMTP server. It’s likely not related to SSRS.

-Igor

Report Delivery Options To field is not editable

In the Report Delivery Options page of a new subscription the To: field is
read only. I followed the step: "Configuration Options for Setting the To:
Field in a Message" in the document "Configuring a Report Server for E-Mail
Delivery" http://technet.microsoft.com/en-us/library/ms159155.aspx. However
the To: field still can not be changed.
What am I over looking?
Thanks, MikeI donâ't know if it has to do with the way we are configured or a step that
was omitted for the procedure outline in my post below. But I logged off of
the network then back on and now the To: field can be change when subscribing.
"Mike Mullane" wrote:
> In the Report Delivery Options page of a new subscription the To: field is
> read only. I followed the step: "Configuration Options for Setting the To:
> Field in a Message" in the document "Configuring a Report Server for E-Mail
> Delivery" http://technet.microsoft.com/en-us/library/ms159155.aspx. However
> the To: field still can not be changed.
> What am I over looking?
> Thanks, Mike
>

Tuesday, February 21, 2012

Replication: remove merge subscription without existing publisher?

Hi all,
I'm a rather newbie, not only to this forum but also to sql server having a question to the following issue:
Is it possible to drop/remove/delete the "orphan" of a merge subscription on one instance of sql server without having the (former) distributor/publisher (on other instance) available?
The background is: I had a small replication infrastructure with two instances (on two machines), one the publisher and distributor, the other the subscriber. Now it happened that the publisher/distributor machine was completely set up new without having the replication dropped in advance, what remained on the subscriber is now a database with all the merge/replication tables and the guid columns in the user tables.
Moreover this, an entry remained in the subscription saying that a subscription with the former publisher exists...

Can I remove these "orphans" without having to setup the instance again?

Thank you,
AndyDid you recreate the Publisher again?|||Originally posted by smasanam
Did you recreate the Publisher again?

No, I didn't recreate the publisher, but I plan to do so, however, with slightly different properties (e.g. publisher db name has changed)...|||Originally posted by AndreasJaehn
No, I didn't recreate the publisher, but I plan to do so, however, with slightly different properties (e.g. publisher db name has changed)...
Sorry to ask again. Can you please give more details about your question.

Looks like you want to drop the subscription. If that is so you can drop the subscription or subscriber database.

Once you dropped the subscription and remove the subscription databases you can go head and change the schema of the database at the subscriber|||Originally posted by smasanam
Once you dropped the subscription and remove the subscription databases you can go head and change the schema of the database at the subscriber

The thing is that I cannot drop the subscription as this implies having a valid publisher, but I don't have the publisher anymore. The system Stored Procedure requires the publishing/distributing instance alive, even if I set the ignore_distributor flag...

I found something in the archive which comes quite close to my problem: http://dbforums.com/arch/69/2002/4/348973

I'll try it that way (see Ramakrishna Koni's comment)...

Thank you.