|
|
You're in the
sql server reporting services
group:RS server cannot connect to SQL
sql server reporting services:
Does anybody know what I'm doing wrong when trying to connect to SQL database placed on other than RS server computer? When I'm connecting to SQL database, placed on the same computer as RS server, everything works properly, by if am going to execute report for database from another computer, the error occurs. What I have to define or change to allow RS server to execute report without depending on database and computer. Best regards!
Hi Igor,
I had the same problem with developers edition - seems to work fine with Enterprise addition - may be undocumented 'feature restriction'. Darren [quoted text, click to view] Igor wrote:
> Hi everyone! > > Does anybody know what I'm doing wrong when trying to connect to SQL > database placed on other than RS server computer? > When I'm connecting to SQL database, placed on the same computer as RS > server, everything works properly, by if am going to execute report for > database from another computer, the error occurs. > > What I have to define or change to allow RS server to execute report without > depending on database and computer. > > Best regards! > Igor.
Thanks.
As I remember, there is standard edition installed om my server. I'll try with other editions. Best regards! Igor. [quoted text, click to view] "darrenmr2@gmail.com" wrote:
> Hi Igor, > > I had the same problem with developers edition - seems to work fine > with Enterprise addition - may be undocumented 'feature restriction'. > > Darren > > > Igor wrote: > > Hi everyone! > > > > Does anybody know what I'm doing wrong when trying to connect to SQL > > database placed on other than RS server computer? > > When I'm connecting to SQL database, placed on the same computer as RS > > server, everything works properly, by if am going to execute report for > > database from another computer, the error occurs. > > > > What I have to define or change to allow RS server to execute report without > > depending on database and computer. > > > > Best regards! > > Igor. >
Standard edition is not a problem.
Seems to me to be a credential problem How is your shared datasource setup? -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Igor" <Igor@discussions.microsoft.com> wrote in message news:AEC9C7AF-1149-42D3-91BC-98A0E119E309@microsoft.com... > Thanks. > As I remember, there is standard edition installed om my server. > I'll try with other editions. > > Best regards! > Igor. > > "darrenmr2@gmail.com" wrote: > >> Hi Igor, >> >> I had the same problem with developers edition - seems to work fine >> with Enterprise addition - may be undocumented 'feature restriction'. >> >> Darren >> >> >> Igor wrote: >> > Hi everyone! >> > >> > Does anybody know what I'm doing wrong when trying to connect to SQL >> > database placed on other than RS server computer? >> > When I'm connecting to SQL database, placed on the same computer as RS >> > server, everything works properly, by if am going to execute report for >> > database from another computer, the error occurs. >> > >> > What I have to define or change to allow RS server to execute report >> > without >> > depending on database and computer. >> > >> > Best regards! >> > Igor. >> >>
Hi!
We work without shared datasource. What we cannot understand is why there is does not work. We simply create a connection string with credentials "sa" with empty password. The same user and password defined on each SQL server I want to connect to. If I try to work with SQL server placed on the same computer with RS server everything works properly, but if I try connect to SQL server on another computer, the error will occurred. It seems like we have no permission to connect from RS server to any other SQL servers except local. Of cause the problem is in permissions, but is it in SQL server connection on generally other computer accessing that is a question. The Datasource definition to work with SQL server on the same computer with RS server looks like this: <DataSources> <DataSource Name="LSRDSOURCEREMP1"> <ConnectionProperties> <DataProvider>SQL</DataProvider> <ConnectString>Data Source=multi-rack2003;Initial Catalog=IBSQL;Packet Size=4096;Workstation ID=IGOR; </ConnectString> </ConnectionProperties> </DataSource> </DataSources> To connect to another SQL server looks like this: <DataSources> <DataSource Name="LSRDSOURCEREMP1"> <ConnectionProperties> <DataProvider>SQL</DataProvider> <ConnectString>Data Source=IGOR;Initial Catalog=IBSQL;Packet Size=4096;Workstation ID=IGOR; </ConnectString> </ConnectionProperties> </DataSource> </DataSources> The call to RenderReport we produce with the same parameters: In Credentials parameters we send one element with ..DataSourceName = ="LSRDSOURCEREMP1" ..UserName = “sa†..Password = “†Of cause “sa†is accessible on both SQL servers. What we are missing in our work? Best regards! Igor. [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> Standard edition is not a problem. > > Seems to me to be a credential problem How is your shared datasource setup? > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Igor" <Igor@discussions.microsoft.com> wrote in message > news:AEC9C7AF-1149-42D3-91BC-98A0E119E309@microsoft.com... > > Thanks. > > As I remember, there is standard edition installed om my server. > > I'll try with other editions. > > > > Best regards! > > Igor. > > > > "darrenmr2@gmail.com" wrote: > > > >> Hi Igor, > >> > >> I had the same problem with developers edition - seems to work fine > >> with Enterprise addition - may be undocumented 'feature restriction'. > >> > >> Darren > >> > >> > >> Igor wrote: > >> > Hi everyone! > >> > > >> > Does anybody know what I'm doing wrong when trying to connect to SQL > >> > database placed on other than RS server computer? > >> > When I'm connecting to SQL database, placed on the same computer as RS > >> > server, everything works properly, by if am going to execute report for > >> > database from another computer, the error occurs. > >> > > >> > What I have to define or change to allow RS server to execute report > >> > without > >> > depending on database and computer. > >> > > >> > Best regards! > >> > Igor. > >> > >> > >
Have you tried to get all the reports working from Report Manager?
-- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "Igor" <Igor@discussions.microsoft.com> wrote in message news:AE3713E8-3E99-4D0F-929A-4E4D6FAC5FC6@microsoft.com... > Hi! > > We work without shared datasource. > What we cannot understand is why there is does not work. We simply create > a > connection string with credentials "sa" with empty password. The same user > and password defined on each SQL server I want to connect to. > If I try to work with SQL server placed on the same computer with RS > server > everything works properly, but if I try connect to SQL server on another > computer, the error will occurred. It seems like we have no permission to > connect from RS server to any other SQL servers except local. > Of cause the problem is in permissions, but is it in SQL server connection > on generally other computer accessing that is a question. > > The Datasource definition to work with SQL server on the same computer > with > RS server looks like this: > <DataSources> > <DataSource Name="LSRDSOURCEREMP1"> > <ConnectionProperties> > <DataProvider>SQL</DataProvider> > <ConnectString>Data Source=multi-rack2003;Initial > Catalog=IBSQL;Packet Size=4096;Workstation ID=IGOR; > </ConnectString> > </ConnectionProperties> > </DataSource> > </DataSources> > > > To connect to another SQL server looks like this: > <DataSources> > <DataSource Name="LSRDSOURCEREMP1"> > <ConnectionProperties> > <DataProvider>SQL</DataProvider> > <ConnectString>Data Source=IGOR;Initial Catalog=IBSQL;Packet > Size=4096;Workstation ID=IGOR; > </ConnectString> > </ConnectionProperties> > </DataSource> > </DataSources> > > The call to RenderReport we produce with the same parameters: > In Credentials parameters we send one element with > .DataSourceName = ="LSRDSOURCEREMP1" > .UserName = "sa" > .Password = "" > > Of cause "sa" is accessible on both SQL servers. > > What we are missing in our work? > > Best regards! > Igor. > > "Bruce L-C [MVP]" wrote: > >> Standard edition is not a problem. >> >> Seems to me to be a credential problem How is your shared datasource >> setup? >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >> >> "Igor" <Igor@discussions.microsoft.com> wrote in message >> news:AEC9C7AF-1149-42D3-91BC-98A0E119E309@microsoft.com... >> > Thanks. >> > As I remember, there is standard edition installed om my server. >> > I'll try with other editions. >> > >> > Best regards! >> > Igor. >> > >> > "darrenmr2@gmail.com" wrote: >> > >> >> Hi Igor, >> >> >> >> I had the same problem with developers edition - seems to work fine >> >> with Enterprise addition - may be undocumented 'feature restriction'. >> >> >> >> Darren >> >> >> >> >> >> Igor wrote: >> >> > Hi everyone! >> >> > >> >> > Does anybody know what I'm doing wrong when trying to connect to SQL >> >> > database placed on other than RS server computer? >> >> > When I'm connecting to SQL database, placed on the same computer as >> >> > RS >> >> > server, everything works properly, by if am going to execute report >> >> > for >> >> > database from another computer, the error occurs. >> >> > >> >> > What I have to define or change to allow RS server to execute report >> >> > without >> >> > depending on database and computer. >> >> > >> >> > Best regards! >> >> > Igor. >> >> >> >> >> >> >>
Hi! No, we did not.
We'll try ! [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> Have you tried to get all the reports working from Report Manager? > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Igor" <Igor@discussions.microsoft.com> wrote in message > news:AE3713E8-3E99-4D0F-929A-4E4D6FAC5FC6@microsoft.com... > > Hi! > > > > We work without shared datasource. > > What we cannot understand is why there is does not work. We simply create > > a > > connection string with credentials "sa" with empty password. The same user > > and password defined on each SQL server I want to connect to. > > If I try to work with SQL server placed on the same computer with RS > > server > > everything works properly, but if I try connect to SQL server on another > > computer, the error will occurred. It seems like we have no permission to > > connect from RS server to any other SQL servers except local. > > Of cause the problem is in permissions, but is it in SQL server connection > > on generally other computer accessing that is a question. > > > > The Datasource definition to work with SQL server on the same computer > > with > > RS server looks like this: > > <DataSources> > > <DataSource Name="LSRDSOURCEREMP1"> > > <ConnectionProperties> > > <DataProvider>SQL</DataProvider> > > <ConnectString>Data Source=multi-rack2003;Initial > > Catalog=IBSQL;Packet Size=4096;Workstation ID=IGOR; > > </ConnectString> > > </ConnectionProperties> > > </DataSource> > > </DataSources> > > > > > > To connect to another SQL server looks like this: > > <DataSources> > > <DataSource Name="LSRDSOURCEREMP1"> > > <ConnectionProperties> > > <DataProvider>SQL</DataProvider> > > <ConnectString>Data Source=IGOR;Initial Catalog=IBSQL;Packet > > Size=4096;Workstation ID=IGOR; > > </ConnectString> > > </ConnectionProperties> > > </DataSource> > > </DataSources> > > > > The call to RenderReport we produce with the same parameters: > > In Credentials parameters we send one element with > > .DataSourceName = ="LSRDSOURCEREMP1" > > .UserName = "sa" > > .Password = "" > > > > Of cause "sa" is accessible on both SQL servers. > > > > What we are missing in our work? > > > > Best regards! > > Igor. > > > > "Bruce L-C [MVP]" wrote: > > > >> Standard edition is not a problem. > >> > >> Seems to me to be a credential problem How is your shared datasource > >> setup? > >> > >> > >> -- > >> Bruce Loehle-Conger > >> MVP SQL Server Reporting Services > >> > >> "Igor" <Igor@discussions.microsoft.com> wrote in message > >> news:AEC9C7AF-1149-42D3-91BC-98A0E119E309@microsoft.com... > >> > Thanks. > >> > As I remember, there is standard edition installed om my server. > >> > I'll try with other editions. > >> > > >> > Best regards! > >> > Igor. > >> > > >> > "darrenmr2@gmail.com" wrote: > >> > > >> >> Hi Igor, > >> >> > >> >> I had the same problem with developers edition - seems to work fine > >> >> with Enterprise addition - may be undocumented 'feature restriction'. > >> >> > >> >> Darren > >> >> > >> >> > >> >> Igor wrote: > >> >> > Hi everyone! > >> >> > > >> >> > Does anybody know what I'm doing wrong when trying to connect to SQL > >> >> > database placed on other than RS server computer? > >> >> > When I'm connecting to SQL database, placed on the same computer as > >> >> > RS > >> >> > server, everything works properly, by if am going to execute report > >> >> > for > >> >> > database from another computer, the error occurs. > >> >> > > >> >> > What I have to define or change to allow RS server to execute report > >> >> > without > >> >> > depending on database and computer. > >> >> > > >> >> > Best regards! > >> >> > Igor. > >> >> > >> >> > >> > >> > >> > >
We checked !
The connection string is: Data Source=IGOR;Initial Catalog=IBSQL;Packet Size=4096;Workstation ID=IGOR; On both SQL servers there is a database with the same name IBSQL and user "sa" with blank password. If we just change Data Source to name of SQL server which placed on the same computer with RS server every thing works properly. We works with SQL server user "sa" with empty password. The message we are getting: "An error has occurred during report processing. Cannot create a connection to data source 'LSRDSOURCEREMP1'." Where "LSRDSOURCEREMP1" is the name of our datasource. What wrong with our datasource or may me have to configurate IIS on RS server computer to work with specific user not with anonymous access. Thanks! Igor [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> Have you tried to get all the reports working from Report Manager? > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services > > "Igor" <Igor@discussions.microsoft.com> wrote in message > news:AE3713E8-3E99-4D0F-929A-4E4D6FAC5FC6@microsoft.com... > > Hi! > > > > We work without shared datasource. > > What we cannot understand is why there is does not work. We simply create > > a > > connection string with credentials "sa" with empty password. The same user > > and password defined on each SQL server I want to connect to. > > If I try to work with SQL server placed on the same computer with RS > > server > > everything works properly, but if I try connect to SQL server on another > > computer, the error will occurred. It seems like we have no permission to > > connect from RS server to any other SQL servers except local. > > Of cause the problem is in permissions, but is it in SQL server connection > > on generally other computer accessing that is a question. > > > > The Datasource definition to work with SQL server on the same computer > > with > > RS server looks like this: > > <DataSources> > > <DataSource Name="LSRDSOURCEREMP1"> > > <ConnectionProperties> > > <DataProvider>SQL</DataProvider> > > <ConnectString>Data Source=multi-rack2003;Initial > > Catalog=IBSQL;Packet Size=4096;Workstation ID=IGOR; > > </ConnectString> > > </ConnectionProperties> > > </DataSource> > > </DataSources> > > > > > > To connect to another SQL server looks like this: > > <DataSources> > > <DataSource Name="LSRDSOURCEREMP1"> > > <ConnectionProperties> > > <DataProvider>SQL</DataProvider> > > <ConnectString>Data Source=IGOR;Initial Catalog=IBSQL;Packet > > Size=4096;Workstation ID=IGOR; > > </ConnectString> > > </ConnectionProperties> > > </DataSource> > > </DataSources> > > > > The call to RenderReport we produce with the same parameters: > > In Credentials parameters we send one element with > > .DataSourceName = ="LSRDSOURCEREMP1" > > .UserName = "sa" > > .Password = "" > > > > Of cause "sa" is accessible on both SQL servers. > > > > What we are missing in our work? > > > > Best regards! > > Igor. > > > > "Bruce L-C [MVP]" wrote: > > > >> Standard edition is not a problem. > >> > >> Seems to me to be a credential problem How is your shared datasource > >> setup? > >> > >> > >> -- > >> Bruce Loehle-Conger > >> MVP SQL Server Reporting Services > >> > >> "Igor" <Igor@discussions.microsoft.com> wrote in message > >> news:AEC9C7AF-1149-42D3-91BC-98A0E119E309@microsoft.com... > >> > Thanks. > >> > As I remember, there is standard edition installed om my server. > >> > I'll try with other editions. > >> > > >> > Best regards! > >> > Igor. > >> > > >> > "darrenmr2@gmail.com" wrote: > >> > > >> >> Hi Igor, > >> >> > >> >> I had the same problem with developers edition - seems to work fine > >> >> with Enterprise addition - may be undocumented 'feature restriction'. > >> >> > >> >> Darren > >> >> > >> >> > >> >> Igor wrote: > >> >> > Hi everyone! > >> >> > > >> >> > Does anybody know what I'm doing wrong when trying to connect to SQL > >> >> > database placed on other than RS server computer? > >> >> > When I'm connecting to SQL database, placed on the same computer as > >> >> > RS > >> >> > server, everything works properly, by if am going to execute report > >> >> > for > >> >> > database from another computer, the error occurs. > >> >> > > >> >> > What I have to define or change to allow RS server to execute report > >> >> > without > >> >> > depending on database and computer. > >> >> > > >> >> > Best regards! > >> >> > Igor. > >> >> > >> >> > >> > >> > >> > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |