February 11, 2009 at 8:41 am
I'm new to SQL Server in general; I'm using 2005 right now. I'm going through the report services tutorials right now, and have hit a road block... previously when I was verifying than an install was clean I checked mostly to see if report server had installed properly by opening http://servername/reportserver, & http://servername/reports in IE (they are all default installs with a few modifications, I run in mixed authentication mode, and network is the primary...
This is the interesting part… there are three possible substitutions for servername when the server is on the box you are accessing it from (as far as I know), there is localhost, the actual box name (in this case ssvs004.byu.edu, it’s a 2003 box), or the IP address…
Depending on which I use, I get varying degrees of response.
http://localhost/reportserver will work immediately, no authentication required
http://10.25.67.2/reportserver will prompt me for my authentication and works after I give it my network username and password.
http://ssvs004.byu.edu/reportserver will prompt me for my authentication, and then refuse my credentials three times, before telling me that I don’t have permission to access the page.
The problem here is that when I’m publishing a report from visual studio, it tries to login the ssvs004.byu.edu way, and then it fails after it refuses my credentials! I would actually like to learn how to resolve this issue in two ways, the first being significantly more important.
1)Make it so that ssvs004.byu.edu/reportserver accepts my credentials…
2)Change the servername visual studio is trying to use (so that I can know in the future if it’s a bug I really don’t happen to care about)
Anyway, thanks in advance for any help.
EDIT: after a little tinkering around, I can log in using the ssvs004.byu.edu/reportserver remotely, or get rid of the byu.edu on the local machine. However, in Visual Studio, there is no option that I can see to get rid of the byu.edu part, and so it always messes up... I'm going to do the tutorials on a remote comp, but that is just a temporary solution...
February 11, 2009 at 9:27 am
Assuming that this ssvs004.byu.edu includes the domain name, you can try using the actual machine name (without the domain suffix). If you still can't access the server, then it has some issues with name server resolution.
BTW, you can change the deployment location in VS or BIDS in Project Properties.
--Ramesh
February 12, 2009 at 7:47 am
Ramesh (2/11/2009)
BTW, you can change the deployment location in VS or BIDS in Project Properties.
how do I do this O_o. That would solve all my problems right now! Thanks
February 12, 2009 at 7:59 am
PayCheck (2/12/2009)
Ramesh (2/11/2009)
BTW, you can change the deployment location in VS or BIDS in Project Properties.how do I do this O_o. That would solve all my problems right now! Thanks
Goto Project Properties > All Configurations > Deployment > TargetServerURL
--Ramesh
February 17, 2009 at 7:30 am
Thank you so much
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply