Report Delivery -- HELP

Is SSRS limited to delivering reports to recipients inside your domain (active directory)? I'm using an SMTP server for report delivery an have set the SendMailToUserAlias to False and still can only send reports to e-mails with my domain (user@.mycompany.com). I need to send reports to recipients outside my company -- is SSRS capable? If so, how do I configure it to do so?If PermittedHosts config setting is not set there shouldn't be restrictions to the receiving hosts. Look at the RS logs and see if there are any exceptions. The restriction could be set at the SMTP server as well.sql

Report Builder and Report Server cross domain communication

I have client machine in one domain, say A domain , on which I have installed .net 2.0 without any problem. I have report server running in other domain (B domain) where I have deployed few models which will be used from domain A to create ad hoc reports by launching Report Builder. I can access other reports in domain B from A

But when I click on Report Builder ..it tries to connect to server in domain B but fails to connect and shows following log in a text pop up

I know, problem is because of cross domain communication but question is then how to fix it ? what changes I need to do for that in firewall, domain etc etc settings?

Here is the error, I have highlighted lines which might give some clue:

PLATFORM VERSION INFO
Windows : 5.2.3790.65536 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES
Deployment url : http://192.168.1.197/ReportServer/ReportBuilder/ReportBuilder.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://192.168.1.197/ReportServer/ReportBuilder/ReportBuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://192.168.1.197/ReportServer/ReportBuilder/ReportBuilder.application did not succeed.
+ The remote server returned an error: (500) Internal Server Error.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [12/19/2006 6:49:58 AM] : Activation of http://192.168.1.197/ReportServer/ReportBuilder/ReportBuilder.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [12/19/2006 6:50:14 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://192.168.1.197/ReportServer/ReportBuilder/ReportBuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (500) Internal Server Error.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

After spending one night, I have fixed this problem myself

In IIS you should allow anonymous access to folder ReportServer/ReportBuilder folder and thats it....

One night's effort to fix a bug in 30 seconds...what a waste :-(

Prashant

Report Authenication

Hi,
I have the following scenario:
1) A database server (machine A, Windows 2000 Server Standard) within a
domain
2) A Reporting Server (machine B, Windows 2003 Server Standard) within the
same domain; the Reporting-Services-Database is also on the Database-server
3) My Client (windows XP) within the same domain.
My Problem: When I publisch a Report to the Reporting Server and I use
"Windows integrated Authentication", I get an error "NT-Authority/Anonymous
User" cant access the database. That's right, but why wouldn't be used my
Username/password instead of Anonymous? What have I to do, to pass my
Logonuser form XP over the Reporting-Services to the Database ? A always
thought "windows integrated authentication" in the shared Connection object
would be enough?
Thanks
HansIt sounds to me like you have IIS setup for anonymous access. When you do
this all users are the same user (the anonymous user as you see below). You
should only be doing this if you are implementing custom authorization.
Otherwise this is a really bad idea.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Hans" <sqlserver@.strengberg.net> wrote in message
news:O0FIBcazEHA.2600@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have the following scenario:
> 1) A database server (machine A, Windows 2000 Server Standard) within a
> domain
> 2) A Reporting Server (machine B, Windows 2003 Server Standard) within the
> same domain; the Reporting-Services-Database is also on the
Database-server
> 3) My Client (windows XP) within the same domain.
> My Problem: When I publisch a Report to the Reporting Server and I use
> "Windows integrated Authentication", I get an error
"NT-Authority/Anonymous
> User" cant access the database. That's right, but why wouldn't be used my
> Username/password instead of Anonymous? What have I to do, to pass my
> Logonuser form XP over the Reporting-Services to the Database ? A always
> thought "windows integrated authentication" in the shared Connection
object
> would be enough?
> Thanks
> Hans
>|||If you are trying to authenticate in a scenerio which involves more than two
endpoints eg: client connects to remote RS web service which connects to a
remote database (3 endpoints) and tou're using Integrated security, NTLM
authentication will not work, you will have to setup a delegation scenerio
using kerberos authentication which supports more than one network hop. Look
here for help about setting up a asp.net app for delegation.
http://support.microsoft.com/default.aspx?scid=kb;en-us;810572
To test that this is your problem first access the report from the reporting
services console, this seems to cache your credential locally, now try from
your remote client try the same report, it should work until you log off the
rs server.
HTH,
Dan
"Hans" wrote:
> Hi,
> I have the following scenario:
> 1) A database server (machine A, Windows 2000 Server Standard) within a
> domain
> 2) A Reporting Server (machine B, Windows 2003 Server Standard) within the
> same domain; the Reporting-Services-Database is also on the Database-server
> 3) My Client (windows XP) within the same domain.
> My Problem: When I publisch a Report to the Reporting Server and I use
> "Windows integrated Authentication", I get an error "NT-Authority/Anonymous
> User" cant access the database. That's right, but why wouldn't be used my
> Username/password instead of Anonymous? What have I to do, to pass my
> Logonuser form XP over the Reporting-Services to the Database ? A always
> thought "windows integrated authentication" in the shared Connection object
> would be enough?
> Thanks
> Hans
>
>|||Thanks to all for the answers. I have disabled all anonymous and I think,
its the problem, Dan reports, because I have 3 Endpoints. I will test this.
Thanks again.
Hans
"Hans" <sqlserver@.strengberg.net> schrieb im Newsbeitrag
news:O0FIBcazEHA.2600@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have the following scenario:
> 1) A database server (machine A, Windows 2000 Server Standard) within a
> domain
> 2) A Reporting Server (machine B, Windows 2003 Server Standard) within the
> same domain; the Reporting-Services-Database is also on the
> Database-server
> 3) My Client (windows XP) within the same domain.
> My Problem: When I publisch a Report to the Reporting Server and I use
> "Windows integrated Authentication", I get an error
> "NT-Authority/Anonymous User" cant access the database. That's right, but
> why wouldn't be used my Username/password instead of Anonymous? What have
> I to do, to pass my Logonuser form XP over the Reporting-Services to the
> Database ? A always thought "windows integrated authentication" in the
> shared Connection object would be enough?
> Thanks
> Hans
>

reply

I am not using the SA account when I log in using windows authentication it seems to pick up my domain and active directory ID which is "us\app1dxd" it appears greyed out as well as the password on the login screen so you can't change it.

If you go into the management studio and right click on the server name in the left hand pane go to properties security the radio button for sql server and Windows authentication mode is selected.

It is normal because the BOL says if you install SQL Server with Windows Authentication the sa account gets disabled, the account remains disabled even when you change to mixed authentication you have to enable the account after changing to mixed authentication.

http://msdn2.microsoft.com/en-us/library/ms144284.aspx