We are having recurring problems whenever we take data sources and reports that were developed for SQL Server 2005 Reporting Services, and redeploy them on a new installation of SSRS.
I have a project consisting of one Shared Data Source and several Reports all based on this Data Source and all using Windows integrated security. In the past, we deployed these reports to the old server, using setting a TargetServerURL of [ignore][/ignore] to point to that old server. We changed the TargetServerURL to [ignore][/ignore] and redeployed everything to the new server. All of the RDS and RDL files appear as they should, but none of the reports can be executed on the new server.
The sysadmin tells me that both servers are running properly, that the user permissions are exactly the same on both machines, and that the network connections are fine. He has noticed, though, that he can access the new SSRS installation without problems locally on the new server, but when he attempts to connect remotely, he gets the following messages:
I have a project consisting of one Shared Data Source and several Reports all based on this Data Source and all using Windows integrated security. In the past, we deployed these reports to the old server, using setting a TargetServerURL of [ignore][/ignore] to point to that old server. We changed the TargetServerURL to [ignore][/ignore] and redeployed everything to the new server. All of the RDS and RDL files appear as they should, but none of the reports can be executed on the new server.
The sysadmin tells me that both servers are running properly, that the user permissions are exactly the same on both machines, and that the network connections are fine. He has noticed, though, that he can access the new SSRS installation without problems locally on the new server, but when he attempts to connect remotely, he gets the following messages:
Has anyone else had this same problem? Has anyone else solved it? Any help you can offer would be greatly appreciated!