Publishing to a remote SSL server

I've set up SQL Reports in 'https://www.projects.com/reports' and added a
reports project to a solution. I used the reports manager to add a folder in
which to deploy the reports, but can't figure out where it is on the server.
When I try to deploy a report to 'https://www.projects.com/reportserver' I
get the following error: 'A connection can not be made to the report server
https://www.projects.com/ReportServer'. Any help to do the following:
1. Set up a folder on the server to deploy the datasource and reports so I
can xcopy
2. Be able to make a connection when I attempt to deploy a report from
VS.NET.
Would be appreciated.
Thanks.
DanI resolved this problem by first installing the data source then the report.
The report runs on the local server, but any attempt to run the report or
sample reports over the internet gives the error: 'Cannot find server or DNS
Error'. I'm publishing behind ISA 2004. Any suggestions?
Thanks.
Dan
"Dan Slaby" <dls@.newsgroup.nospam> wrote in message
news:ucM%23rdOjFHA.3568@.tk2msftngp13.phx.gbl...
> I've set up SQL Reports in 'https://www.projects.com/reports' and added a
> reports project to a solution. I used the reports manager to add a folder
> in which to deploy the reports, but can't figure out where it is on the
> server. When I try to deploy a report to
> 'https://www.projects.com/reportserver' I get the following error: 'A
> connection can not be made to the report server
> https://www.projects.com/ReportServer'. Any help to do the following:
> 1. Set up a folder on the server to deploy the datasource and reports so I
> can xcopy
> 2. Be able to make a connection when I attempt to deploy a report from
> VS.NET.
> Would be appreciated.
> Thanks.
> Dan
>|||Hello,
I'd like to confirm that both report server and SQL server are behind ISA
2004.
Please note that Windows authentication is not supported via Internet
because Kerbose/NTLM authentication need open too many ports via firewall
which is not proper for security purpose.
If you want to run the report over the internet, you may need to enable
anonymous access. You need to configure via report manager to enable
Iusr_<computername> account to have the proper permission to the proper
roles such as browser/content manager etc.
I suggest that you perform the following steps to narrow down the issue:
1. Run the report internally from another client computer with anonymous
access.
If the user can run the report internally successfully with anonymous
access, you may need to check the configuration of the ISA server.
To enable Anonymous Access to work with SQL Server Reporting Services,
enable Anonymous Access under Directory Security in IIS and set the default
account to IWAM_machinename
NOTE: By default SQL Server Reporting Services uses the IWAM_machinename
account to connect.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.