Reporting Services setup problem

Hi all,
I've downloaded the SQL Reporting Services eval and am trying to get
it installed but have run into the following problem:
When I get to the step for connecting to the SQL Server instance on
which the ReportServer database will reside I try and connect via SQL
Server account (sa actually). When I supply the sa, password, and
named instance of SQL Server 2000 it gives me the following error
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection." I've seen this when trying to connect through
QA via a Domain User Account but not with a SQL Server login.
Has anybody else had any problems similiar to this with Reporting
Services?
My environment...
Version: Microsoft SQL Server 2000 - 8.00.760
on Windows 2003 Server
Connecting to a named instance via TCP/IP
I can successfully connect to QA using the sa account but can't
complete the Reporting services install.
Thanks> When I get to the step for connecting to the SQL Server instance on
> which the ReportServer database will reside I try and connect via SQL
> Server account (sa actually). When I supply the sa, password, and
> named instance of SQL Server 2000 it gives me the following error
> "Login failed for user '(null)'. Reason: Not associated with a trusted
> SQL Server connection." I've seen this when trying to connect through
> QA via a Domain User Account but not with a SQL Server login.
> Has anybody else had any problems similiar to this with Reporting
> Services?
This happen when SQL machine and Reporting service machine aren't on a
single domain or on a couple of trusted domain.
Try to put the same password on local administrator user on both
machine. When the setup is completed succesfully, you can change the
passwords to a different couple again...
HTH
N|||Hi there
If its a domain member server, connect as the domain administrator,
for some reason RS uses your builtin/administrator account to verify
the account BEFORE it uses the details you typed in (why? because if
it doesnt fine the user it will prompt you re its creation if you
choose to do so).
In my case, I was logged in locally to the member as administrator,
then got the trusted connection error. I can connect fine via my SQL
user, but RS simply ignored whatever i typed and didnt attempt to use
this in its first set of checks.
With the domain admin account, my SQL authentication to my
ReportServer repository then worked a treat on install.
Cheers
Ck|||I am having the same problem.
I am trying to install Reporting Services on a Windows 2000 Server Box (Box
A) in domain A.
The SQL Server 2000 - Windows 2000 Server (Box B) that I am trying to attach
to resides in domain B. I am logged into Box as the Domain Admin (A/Admini
strator).
All three options "Service Account", "Domain Account", and "SQL Login Accoun
t" fail. I get the same error as described in previous posts.
"Login failed for user '(null)'. Reason: Not associated with a trusted SQL S
erver connection."
I want to login using "SQL Login Account".
I have tried the suggestions posted here with no luck.
Any help would be appreciated.
-- Justin Bigelow wrote: --
Hi all,
I've downloaded the SQL Reporting Services eval and am trying to get
it installed but have run into the following problem:
When I get to the step for connecting to the SQL Server instance on
which the ReportServer database will reside I try and connect via SQL
Server account (sa actually). When I supply the sa, password, and
named instance of SQL Server 2000 it gives me the following error
"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection." I've seen this when trying to connect through
QA via a Domain User Account but not with a SQL Server login.
Has anybody else had any problems similiar to this with Reporting
Services?
My environment...
Version: Microsoft SQL Server 2000 - 8.00.760
on Windows 2003 Server
Connecting to a named instance via TCP/IP
I can successfully connect to QA using the sa account but can't
complete the Reporting services install.
Thanks|||Make sure your SQL install allows SQL logins. On your SQL box, open Query
Analyzer, and attempt to log on with your SQL credentials.
That's the error you usually get when you try to login with a SQL login, but
SQL is configured for Windows Integrated only.
Jeff
"Eric" <removethis eric dot avery at durakon dot com removethis> wrote in
message news:56092B36-FCAA-4D67-915D-7FD4CC8282B8@.microsoft.com...
> I am having the same problem.
> I am trying to install Reporting Services on a Windows 2000 Server Box
(Box A) in domain A.
> The SQL Server 2000 - Windows 2000 Server (Box B) that I am trying to
attach to resides in domain B. I am logged into Box as the Domain Admin
(A/Administrator).
> All three options "Service Account", "Domain Account", and "SQL Login
Account" fail. I get the same error as described in previous posts.
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection."
> I want to login using "SQL Login Account".
> I have tried the suggestions posted here with no luck.
> Any help would be appreciated.
> -- Justin Bigelow wrote: --
> Hi all,
> I've downloaded the SQL Reporting Services eval and am trying to get
> it installed but have run into the following problem:
> When I get to the step for connecting to the SQL Server instance on
> which the ReportServer database will reside I try and connect via SQL
> Server account (sa actually). When I supply the sa, password, and
> named instance of SQL Server 2000 it gives me the following error
> "Login failed for user '(null)'. Reason: Not associated with a
trusted
> SQL Server connection." I've seen this when trying to connect through
> QA via a Domain User Account but not with a SQL Server login.
> Has anybody else had any problems similiar to this with Reporting
> Services?
> My environment...
> Version: Microsoft SQL Server 2000 - 8.00.760
> on Windows 2003 Server
> Connecting to a named instance via TCP/IP
> I can successfully connect to QA using the sa account but can't
> complete the Reporting services install.
> Thanks
>|||SQL Server is set-up for Mixed Mode Authentication and I have tested and suc
cessfully connected to it using ODBC/OLEDB connection strings from the box I
am trying to install SQL Server Reporting Services. I am still getting the
error as mentioned earlier
. Additional Information: Domain A has active directory, Domain B has an NT
classic domain. Domain A and Domain B are seperated by a firewall. The fir
ewall has 3 NICs - 1 going to Domain A, 1 to Domain B, and 1 to an Internet
Router. Is there something
that has to be allowed on the firewall?
Thanks!
-- Jeff Dillon wrote: --
Make sure your SQL install allows SQL logins. On your SQL box, open Query
Analyzer, and attempt to log on with your SQL credentials.
That's the error you usually get when you try to login with a SQL login, but
SQL is configured for Windows Integrated only.
Jeff
"Eric" <removethis eric dot avery at durakon dot com removethis> wrote in
message news:56092B36-FCAA-4D67-915D-7FD4CC8282B8@.microsoft.com...
> I am having the same problem.
(Box A) in domain A.
> The SQL Server 2000 - Windows 2000 Server (Box B) that I am trying to
attach to resides in domain B. I am logged into Box as the Domain Admin
(A/Administrator).
> All three options "Service Account", "Domain Account", and "SQL Login
Account" fail. I get the same error as described in previous posts.
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection."
> it installed but have run into the following problem:
> which the ReportServer database will reside I try and connect via SQL
> Server account (sa actually). When I supply the sa, password, and
> named instance of SQL Server 2000 it gives me the following error
> "Login failed for user '(null)'. Reason: Not associated with a
trusted
> SQL Server connection." I've seen this when trying to connect through
> QA via a Domain User Account but not with a SQL Server login.
> Services?
> Version: Microsoft SQL Server 2000 - 8.00.760
> on Windows 2003 Server
> Connecting to a named instance via TCP/IP
> complete the Reporting services install.
>|||See my other thread for my progress
http://communities2.microsoft.com/c...b3-92fb1b49099d