Installing Reporting Services 2005 on SQL Server 2005 64-bit server

Installing Reporting Services 2005 on SQL Server 2005 64-bit server

Post by imarchenk » Wed, 12 Apr 2006 04:07:26


Hello!

I am trying to install Reporting Services 2005 on SQL Server 2005 64-bit
Edition. Installation process goes without errors. But when I try to
configure Reporting Services through Reporting Services Configuration
manages, I am getting an error/warning when configuring Database setup
section:

Verifying Database Edition:

This feature: "Using other editions of SQL Server for report data sources
and/or the report server database" is not supported in this edition of
Reporting Services.

I am trying to install from the same MSDN CD and original SQL Server 2005
installation. I am able to configure all objects (Virtual directory, Web
service identity etc.) but 'Database Setup'. Can I install reporting
services on SQL Server 2005 64-bit?

Thanks,
Igor
 
 
 

1. Migration from SQL 2000 Enterprise Server to the SQL 2005 Enterprise Server (64 bit-Itanium Server)

2. Problem accessing SQL Server 2000 from SQL Server 2005 64-bit

Hello!

I was trying to test linked server on configured from two different SQL
Server 2005 64-bit servers to SQL Server 2000 SP3. The initial error on both
source servers was: 'Cannot obtain the schema rowset "DBSCHEMA_TABLES_INFO"
for OLE DB provider "SQLNCLI" for linked server "<LinkedServerName>"'.
This has been addressed by applying MS patch:
http://www.yqcomputer.com/

One of the SQL Server 2005 64-bit servers is working fine now. This is a
non-clustered server.
But I am getting different error on second (active/passive cluster) SQL
Server 2005 64-bit:

OLE DB provider "SQLNCLI" for linked server "172.16.5.232" returned message
"Unspecified error".

OLE DB provider "SQLNCLI" for linked server "172.16.5.232" returned message
"Communication link failure".

OLE DB provider "SQLNCLI" for linked server "172.16.5.232" returned message
"Communication link failure".

Msg 121, Level 16, State 1, Line 0

TCP Provider: The semaphore timeout period has expired.

Both source servers are in the same domain/network and Netwrok guys are
swearing that firewall is fully open for this traffic. I was running netwrok
sniffer, WireShark, and didn't find any lost packages or errors. I was
running SQL Profiler on SQL 2000 server and gather several meta data call on
SQL 2000 before it errored out on SQL Server 2005 64-bit side. I also saw
successful TCP connection established from source server using netstat.

I am not sure if this is clustered related or something else.

Any help is greately appreciated,
Igor

3. Confusion - Reporting services, VS 2005, SQL Server 2005, VS 2003, SQL Server 2000

4. SQL Server 2005 Performance issue on 64 bit server running Windows 2003 Server

5. Oracle Linked Server on SQL Server 2005 64-bit

6. SQL Server 2005 64-bit Total Server Memory(KB)

7. Linked Servers in 64-bit SQL Server 2005

8. Missing server components for 64-bit SQL 2005 install

9. linked server - sql 2005 (64-bit) to sql7 (32-bit)

10. SQL Server 2005 Enterprise: running 32-bit and 64-bit versions side-by-side

11. 32-bit SQL 2005 Standard on 64-bit Windows Server 2003

12. linked server - sql 2005 (64-bit) to sql7 (32-bit)

13. 32-bit version of SQL 2005 Std on 64-bit W2K8 Std Server

14. SQL Server 2000 DTS Designer Components on SQL 2005 64-bit

15. SQL Server 2005 64 bits on a system with Windows Server 2003 32 bi