Internal Email subscription fail

I'm having an issue with subscriptions. I created a subscription to
email a report both to an external address and internal address. The
subscription worked fine (Mail sent to ... ) in RS. The outside
entity received the email, but the internal entity does not receive
the email. Is there some configuration I'm missing on the exchange
side in order to accept a connection from RS? Thanks
DaveOn Aug 31, 3:29 pm, Dave <david.brueg...@.gmail.com> wrote:
> I'm having an issue with subscriptions. I created a subscription to
> email a report both to an external address and internal address. The
> subscription worked fine (Mail sent to ... ) in RS. The outside
> entity received the email, but the internal entity does not receive
> the email. Is there some configuration I'm missing on the exchange
> side in order to accept a connection from RS? Thanks
> Dave
It sounds more like your Exchange Server is filtering out the
extension type (i.e., PDF, MHTML, etc) of the report attached to the
email. Also, I'm not sure what the 'from' email is set to from SSRS;
however, if it is different than what is expected by the Exchange
Server, it may flag it as Spam. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultantsql

Intermittant Connection Errors

I have a Merge-Pull subscription setup between two SQL 2005 databases. While watching the status messages display for the subscription, I am constantly seeing the following message being displayed:

"The merge process could not connect to the Publisher '{server}:{database}'. Check to ensure that the server is running."

It will display for anywhere between 15 seconds to a few minutes, then it will display the standard "Waiting 60 seconds..." message which is what I'm used to seeing when all is working well.

There doesn't seem to be any network issues that I can identify. I ran a quick script to run ping continuously against the publisher server and verified that the server was constantly "pingable", even when the above message was displayed (which, by the way, was being displayed by using SSMS while connected to the publisher).

Does anyone know what would cause this message to appear all the time - for extended amounts of time, with occasional glimpses of a non-error status?

It's a wild guess but failing to login / authenticate ?|||I thought of that but am not sure that it applies. The reason being that I can leave the subscription/synchronization status window open in SSMS and it will toggle back and forth (seemingly randomly over time) between the message I mentioned above and some type of valid message.|||What about Timeouts (Connection or Query)? I have seen similar issues in Web Sync. If the amount of data changed since the last sync operation then I have experienced Timeouts while the sync is initialized. Not exactly as you describe but another parameter worth checking.

Rab
|||

I'm not sure what the issue was but it seems to have resolved itself - at least for the time being. If it happens again, I'll be looking for more answers :-)

Thanks for everyone's help.

|||I have this problem as well. It works sometimes and then fails with this error message which leads me to believe it isn't a login problem. I'm still new to replication so I could be wrong, but I think once I get this message, replication is broken and requires someone to intervene to reinitialize. Has anyone figured out what is going on?

Intermittant Connection Errors

I have a Merge-Pull subscription setup between two SQL 2005 databases. While watching the status messages display for the subscription, I am constantly seeing the following message being displayed:

"The merge process could not connect to the Publisher '{server}:{database}'. Check to ensure that the server is running."

It will display for anywhere between 15 seconds to a few minutes, then it will display the standard "Waiting 60 seconds..." message which is what I'm used to seeing when all is working well.

There doesn't seem to be any network issues that I can identify. I ran a quick script to run ping continuously against the publisher server and verified that the server was constantly "pingable", even when the above message was displayed (which, by the way, was being displayed by using SSMS while connected to the publisher).

Does anyone know what would cause this message to appear all the time - for extended amounts of time, with occasional glimpses of a non-error status?

It's a wild guess but failing to login / authenticate ?|||I thought of that but am not sure that it applies. The reason being that I can leave the subscription/synchronization status window open in SSMS and it will toggle back and forth (seemingly randomly over time) between the message I mentioned above and some type of valid message.|||What about Timeouts (Connection or Query)? I have seen similar issues in Web Sync. If the amount of data changed since the last sync operation then I have experienced Timeouts while the sync is initialized. Not exactly as you describe but another parameter worth checking.

Rab|||

I'm not sure what the issue was but it seems to have resolved itself - at least for the time being. If it happens again, I'll be looking for more answers :-)

Thanks for everyone's help.

|||I have this problem as well. It works sometimes and then fails with this error message which leads me to believe it isn't a login problem. I'm still new to replication so I could be wrong, but I think once I get this message, replication is broken and requires someone to intervene to reinitialize. Has anyone figured out what is going on?sql

Interesting subscription question...I could use some brainstorming help

I have a report that needs to be emailed to 40 diffferent technicians.
Each tehnician handles a different US region so the report will be
driven via a parameter (most likely a technician ID). We don't want
other technicians seeing data for someone elses region. This all has
to be automated, no user interaction with this report other than each
technician getting an email with his/her data (based on his/her
results).
What would be the best way to handle this with a subscription?I do know that this will have to be a data-driven subscription. Is it
possible for the value in a data driven query be used as a parameter in
the report'
kimcheebowl wrote:
> I have a report that needs to be emailed to 40 diffferent technicians.
> Each tehnician handles a different US region so the report will be
> driven via a parameter (most likely a technician ID). We don't want
> other technicians seeing data for someone elses region. This all has
> to be automated, no user interaction with this report other than each
> technician getting an email with his/her data (based on his/her
> results).
> What would be the best way to handle this with a subscription?|||Absolutely - DDS will be just what the doctor ordered. You will need
to feed the parameter values into a table for the DDS to pull from. I
use both Access DB and Excel spreadsheet uploads to upload subscription
parameters into a SQL Server table, which is then used by the DDS.
Matt A
kimcheebowl wrote:
> I do know that this will have to be a data-driven subscription. Is it
> possible for the value in a data driven query be used as a parameter in
> the report'
>
> kimcheebowl wrote:
> > I have a report that needs to be emailed to 40 diffferent technicians.
> > Each tehnician handles a different US region so the report will be
> > driven via a parameter (most likely a technician ID). We don't want
> > other technicians seeing data for someone elses region. This all has
> > to be automated, no user interaction with this report other than each
> > technician getting an email with his/her data (based on his/her
> > results).
> >
> > What would be the best way to handle this with a subscription?sql