|
Prev: Custom assembly with unmanaged code
Next: Using RowNumber to count Table Footers, not to include the Details
From: terry on 9 Jul 2008 10:14 My environment is different from yours, but I am having this EXACT problem. If a solution turns up I will definitely share what I find. "Mark" wrote: > bump... > > "Mark" wrote: > > > Hi. > > > > I have 2x SQl Servers - 1x Development and 1x Production. I have a working > > SQLRS already deployed to production. > > > > I have just created a new DB and Analysis solution on development and > > published a set of reports to the production server. From the production > > server, i can call http://servername/reportserver and browse the reports > > successfully. however, trying the same URL on the development server returns > > the following : > > > > An error has occurred during report processing. (rsProcessingAborted) > > Cannot create a connection to data source 'developmentserver_AS'. > > (rsErrorOpeningConnection) > > The connection either timed out or was lost. > > Unable to read data from the transport connection: An existing connection > > was forcibly closed by the remote host. > > An existing connection was forcibly closed by the remote host > > > > As all of the development occurs on the development server, browsing the > > reports through BI Studio works successfully. > > > > I thinkk that this is a permissions issue however, i am unsure of where to > > begin to debug the permissions setup. > > > > Can you please suggets a pathway to resolve access to the reports? > > > > thanks in advance..
From: Tom Regan Tom on 22 Jul 2008 17:25 Having the exact same problem. Did you ever learn what was causing this? "Mark" wrote: > Hi. > > I have 2x SQl Servers - 1x Development and 1x Production. I have a working > SQLRS already deployed to production. > > I have just created a new DB and Analysis solution on development and > published a set of reports to the production server. From the production > server, i can call http://servername/reportserver and browse the reports > successfully. however, trying the same URL on the development server returns > the following : > > An error has occurred during report processing. (rsProcessingAborted) > Cannot create a connection to data source 'developmentserver_AS'. > (rsErrorOpeningConnection) > The connection either timed out or was lost. > Unable to read data from the transport connection: An existing connection > was forcibly closed by the remote host. > An existing connection was forcibly closed by the remote host > > As all of the development occurs on the development server, browsing the > reports through BI Studio works successfully. > > I thinkk that this is a permissions issue however, i am unsure of where to > begin to debug the permissions setup. > > Can you please suggets a pathway to resolve access to the reports? > > thanks in advance..
From: zzx375 on 7 Aug 2008 10:47
On Jul 22, 4:25 pm, Tom Regan <Tom Re...(a)discussions.microsoft.com> wrote: > Having the exact same problem. Did you ever learn what was causing this? > > > > "Mark" wrote: > > Hi. > > > I have 2x SQl Servers - 1x Development and 1x Production. I have a working > > SQLRS already deployed to production. > > > I have just created a new DB and Analysis solution on development and > > published a set of reports to the production server. From the production > > server, i can callhttp://servername/reportserverand browse the reports > > successfully. however, trying the same URL on the development server returns > > the following : > > > An error has occurred during report processing. (rsProcessingAborted) > > Cannot create aconnectiontodatasource 'developmentserver_AS'. > > (rsErrorOpeningConnection) > > Theconnectioneither timed out or was lost. > >Unabletoreaddatafrom thetransportconnection: An existingconnection > > was forcibly closed by the remote host. > > An existingconnectionwas forcibly closed by the remote host > > > As all of the development occurs on the development server, browsing the > > reports through BI Studio works successfully. > > > I thinkk that this is a permissions issue however, i am unsure of where to > > begin to debug the permissions setup. > > > Can you please suggets a pathway to resolve access to the reports? > > > thanks in advance..- Hide quoted text - > > - Show quoted text - I'm seeing the same issue. The RS Report is on server A which attempts to access the datasource on server B. I thought that it was related to Kerberos security but even turning that on in AD did not solve. |