KCITS
asked on
Visual Studio 2008 - Reporting services login prompt
When attempting to deploy a report in Visual Studio 2008, a 'Report Services Login' is generated.
Server: http://'ServerName'/ReportServer
We have attempted to use domain admin credentials and also the sa credentials, all of which are not accepted. No error is generated, the login prompt remains.
SQL Server 2008 is hosted on Windows Server 2008 Standard.
Visual Studio is installed on Server 2003.
When browsing http://'ServerName'/ReportServer/ - the page is opened automatically.
When browsing the same server but using IP address - a username and password is requested. Logging in with domain admin credentials is fine.
Thanks in advance.
Server: http://'ServerName'/ReportServer
We have attempted to use domain admin credentials and also the sa credentials, all of which are not accepted. No error is generated, the login prompt remains.
SQL Server 2008 is hosted on Windows Server 2008 Standard.
Visual Studio is installed on Server 2003.
When browsing http://'ServerName'/ReportServer/ - the page is opened automatically.
When browsing the same server but using IP address - a username and password is requested. Logging in with domain admin credentials is fine.
Thanks in advance.
Report server path and report manager path are different. When you access reports through report server path, you can just execute reports. But thru report manager path, you can update data sources, remove reports etc. You cannot deploy reports to report manager path. Please check with your admin to get the right report server path.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
there were problems with AD, AD user names could not be resolved we jhad error messages such as RPC Server unavailable. we fixed this by changing TMG RPC rule to not require strict compliance.
Then the report server cold be used by the server name as suggested by sammy. previously we were using ip-address. this fixed the problem
Then the report server cold be used by the server name as suggested by sammy. previously we were using ip-address. this fixed the problem