Showing posts with label contains. Show all posts
Showing posts with label contains. Show all posts

Friday, March 30, 2012

rsinvaliddataSourceReference problem

Hi,
I have some rdl files to be deployed using RS 2005. I have 3 folders viz., ReportFolder1, ReportFolder2 and System Files.
ReportFolder1 - contains soem reports
ReportFolder2 - contains some other types of reports
System Files - Contains the shared Data source
All the above folders are present in a main folder called ReportMain
In all my rdl files I have given the value of DataSourceReference element as 'ReportMain/System Files/MyDatabase'.
Still when the reports are deployed and i try to view any report, I get the following error:
The report server cannot process the report. The data source connection information has been deleted.(rsInvalidDataSourceReference).

Why do I get this error still? Can anyoen help?
Thanks.

Hi SandyJ,

This is because ur not pointing the reports to the required data source

I am giving u step by step solution for this issue.

1. go to Report Manager(http://<servername>/reports/pages/Folder.aspx)

2. Click on the Folder in which u have reports

3. U will be directed into contents tab where u will find Show Details at the right top corner

4. Click on Show Details

5. Check in the particular report and click the edit button corresponding to it

6. Go to the properties tab and click on it

7. U will find a menu on left hand side, click on Data Sources link

8. There u will find radio button selected for A share data source(by default) and a browse button.

9. Click on the browse button u will find the tree structure of the datasource and the reports folder.

10. select the datasource in the datasource folder and select OK.

by this way u will be able to point the report to the datasource.

Regards,

Vamsi Krishna Korasiga

rsinvaliddataSourceReference problem

Hi,
I have some rdl files to be deployed using RS 2005. I have 3 folders viz., ReportFolder1, ReportFolder2 and System Files.
ReportFolder1 - contains soem reports
ReportFolder2 - contains some other types of reports
System Files - Contains the shared Data source
All the above folders are present in a main folder called ReportMain
In all my rdl files I have given the value of DataSourceReference element as 'ReportMain/System Files/MyDatabase'.
Still when the reports are deployed and i try to view any report, I get the following error:
The report server cannot process the report. The data source connection information has been deleted.(rsInvalidDataSourceReference).

Why do I get this error still? Can anyoen help?
Thanks.

Hi SandyJ,

This is because ur not pointing the reports to the required data source

I am giving u step by step solution for this issue.

1. go to Report Manager(http://<servername>/reports/pages/Folder.aspx)

2. Click on the Folder in which u have reports

3. U will be directed into contents tab where u will find Show Details at the right top corner

4. Click on Show Details

5. Check in the particular report and click the edit button corresponding to it

6. Go to the properties tab and click on it

7. U will find a menu on left hand side, click on Data Sources link

8. There u will find radio button selected for A share data source(by default) and a browse button.

9. Click on the browse button u will find the tree structure of the datasource and the reports folder.

10. select the datasource in the datasource folder and select OK.

by this way u will be able to point the report to the datasource.

Regards,

Vamsi Krishna Korasiga

Monday, March 12, 2012

RS stripping spaces from my text

Yello,
We have a very simple report that lists the contents of a table called
GenericReport that contains one field of varchar(120). All the report needs
to do is list the records in this table.
Unfortunately, I'm finding that RS will pick up the text from a record, and
strip out any spaces at the beginning. Which in turns destroys the
formating of the text - removing any indents created by padding with spaces.
The report doesn't do it when previewed from the designer, but does it when
rendered in the browser via report manager.
Anyone have experience of this, or know how to stop it.
Thanksbump
"Martin Cross" <martincross@.vardells.com> wrote in message
news:ubJdNSTpEHA.1164@.TK2MSFTNGP10.phx.gbl...
> Yello,
> We have a very simple report that lists the contents of a table called
> GenericReport that contains one field of varchar(120). All the report
> needs to do is list the records in this table.
> Unfortunately, I'm finding that RS will pick up the text from a record,
> and strip out any spaces at the beginning. Which in turns destroys the
> formating of the text - removing any indents created by padding with
> spaces.
> The report doesn't do it when previewed from the designer, but does it
> when rendered in the browser via report manager.
> Anyone have experience of this, or know how to stop it.
> Thanks
>
>|||The behavior your are encountering is a result of how IE handles adjacent
whitespace characters.
We have looked into changing this behavior but doing so introduces worse
problems with regards to search and wordwrap.
--
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Martin Cross" <martincross@.vardells.com> wrote in message
news:ubJdNSTpEHA.1164@.TK2MSFTNGP10.phx.gbl...
> Yello,
> We have a very simple report that lists the contents of a table called
> GenericReport that contains one field of varchar(120). All the report
needs
> to do is list the records in this table.
> Unfortunately, I'm finding that RS will pick up the text from a record,
and
> strip out any spaces at the beginning. Which in turns destroys the
> formating of the text - removing any indents created by padding with
spaces.
> The report doesn't do it when previewed from the designer, but does it
when
> rendered in the browser via report manager.
> Anyone have experience of this, or know how to stop it.
> Thanks
>
>|||Is it possible to include adjacent " " elements in a textbox to display
whitespace beyond one space? Or any html tags to be included in the
displayed report?
My problem is that I have multiple row groups in a matrix report. I'm
trying to provide headers for the row groups. The column headers for each
row group have been merged into one textbox which I can't split. If I could
insert spaces, I could at least provide a spaced string with labels
positioned above the row groups. It is confusing to the user to have
multiple row groups with no headers above them.
Thanks
Bill
"Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
news:exKUjGXpEHA.132@.TK2MSFTNGP14.phx.gbl...
> The behavior your are encountering is a result of how IE handles adjacent
> whitespace characters.
> We have looked into changing this behavior but doing so introduces worse
> problems with regards to search and wordwrap.
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "Martin Cross" <martincross@.vardells.com> wrote in message
> news:ubJdNSTpEHA.1164@.TK2MSFTNGP10.phx.gbl...
> > Yello,
> > We have a very simple report that lists the contents of a table called
> > GenericReport that contains one field of varchar(120). All the report
> needs
> > to do is list the records in this table.
> >
> > Unfortunately, I'm finding that RS will pick up the text from a record,
> and
> > strip out any spaces at the beginning. Which in turns destroys the
> > formating of the text - removing any indents created by padding with
> spaces.
> >
> > The report doesn't do it when previewed from the designer, but does it
> when
> > rendered in the browser via report manager.
> >
> > Anyone have experience of this, or know how to stop it.
> >
> > Thanks
> >
> >
> >
>|||I've tried replacing spaces with but Reporting Services converts this to
when it renders the report. So, obviously it's converting certain
characters to their HTML code values but not spaces. Has anyone found a way
to write into a report and have it render as a space?
Thanks,
Mark
"bill" wrote:
> Is it possible to include adjacent " " elements in a textbox to display
> whitespace beyond one space? Or any html tags to be included in the
> displayed report?
> My problem is that I have multiple row groups in a matrix report. I'm
> trying to provide headers for the row groups. The column headers for each
> row group have been merged into one textbox which I can't split. If I could
> insert spaces, I could at least provide a spaced string with labels
> positioned above the row groups. It is confusing to the user to have
> multiple row groups with no headers above them.
> Thanks
> Bill
> "Bruce Johnson [MSFT]" <brucejoh@.online.microsoft.com> wrote in message
> news:exKUjGXpEHA.132@.TK2MSFTNGP14.phx.gbl...
> > The behavior your are encountering is a result of how IE handles adjacent
> > whitespace characters.
> > We have looked into changing this behavior but doing so introduces worse
> > problems with regards to search and wordwrap.
> >
> > --
> > Bruce Johnson [MSFT]
> > Microsoft SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> >
> > "Martin Cross" <martincross@.vardells.com> wrote in message
> > news:ubJdNSTpEHA.1164@.TK2MSFTNGP10.phx.gbl...
> > > Yello,
> > > We have a very simple report that lists the contents of a table called
> > > GenericReport that contains one field of varchar(120). All the report
> > needs
> > > to do is list the records in this table.
> > >
> > > Unfortunately, I'm finding that RS will pick up the text from a record,
> > and
> > > strip out any spaces at the beginning. Which in turns destroys the
> > > formating of the text - removing any indents created by padding with
> > spaces.
> > >
> > > The report doesn't do it when previewed from the designer, but does it
> > when
> > > rendered in the browser via report manager.
> > >
> > > Anyone have experience of this, or know how to stop it.
> > >
> > > Thanks
> > >
> > >
> > >
> >
> >
>
>

Tuesday, February 21, 2012

RS 2005: Excessively Long String error when printing

I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:

Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?

Jon,

We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.

I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.

Is there any work around to this issue?

|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||

This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.

The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.

|||

Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.

-Dan

|||

Sure

SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.

|||

Thanks so much Brad - really appreciate the help.

Jon

|||

Brad -

In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?

Thanks,

Jon

|||

I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.

Thanks
-Dan

|||

Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.

Jon

|||It does indeed! Thanks for your note Jon!

RS 2005: Excessively Long String error when printing

I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:

Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?

Jon,

We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.

I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.

Is there any work around to this issue?

|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||

This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.

The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.

|||

Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.

-Dan

|||

Sure

SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.

|||

Thanks so much Brad - really appreciate the help.

Jon

|||

Brad -

In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?

Thanks,

Jon

|||

I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.

Thanks
-Dan

|||

Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.

Jon

|||It does indeed! Thanks for your note Jon!

RS 2005: Excessively Long String error when printing

I have a VB.NET 2003 WinForms application that contains a browser control to render reports within. I have a SQL Server 2005 Reporting Services instance - and through the RS site, the reports come up great, and print just fine. However, when pulling in the reports through the WinForms application, when trying to print - I receive an error. A message box pops up that says "An error occured trying to get the current window." The next message is:

Line: 26; Char:4; Error: Marshaler restriction: Excessively long string. Code: 0; URL: http://svr-sqlreport1/ReportServer$QA/Reserved.ReportViewerWebControl.axd?

Jon,

We are also experiencing exactly your issue described above. I read on one forum that embedded web forms using URL access to get reports is not a supported feature of RS2005 which is absolutely dumbfounding. We have invested heavily in embedding the web form in a Visual Studio application that can apparently no longer support this for 2005.

I've been told by MS that we need to use there new controls, but your assuming that our clients are willing and able to deploy the .net framework 2.0 to the desktop and that requires XP SP2 - which in the case of one of our clients is also not on the desktop.

Is there any work around to this issue?

|||We've yet to find a work around...sorry. At this point, we've decided to spend some time testing and estimating effort required to upgrade to VS.NET 2005 (.NET fx 2.0). Provided that doesn't take too long, we'll upgrade. I'm really disappointed to hear that it is not supported and MSFT's only solution is to use new controls.|||

This is a known issue and will be fixed in SP1 for RS 2005. If you cannot wait for SP1, you can contact Microsoft PSS. There is a fix in development to address this issue and should be available soon.

The workaround for now is to use the ReportViewer controls in a 2.0 .Net application instead of the Web control.

|||

Thanks Brad. Do you have a bug # / code that I can reference as I deal with support people on the Microsoft side? Much appreciated.

-Dan

|||

Sure

SQL Hotfix 319. This is the code I know it by, but PSS should be able to figure it out with a little bit of looking.

|||

Thanks so much Brad - really appreciate the help.

Jon

|||

Brad -

In speaking with product support, they are unable to provide the hotfix unless I am able to provide the actual article number associated with the hotfix - they are saying that SQL Hotfix 319 is not enough for them to go by. Do you happen to have the article number?

Thanks,

Jon

|||

I've also spoken to my contacts at MS and they are unable to help without having the Knowledge base article associatied with this issue. Problem is, i've looked on the KB and can't find a one. Brad, any assistance you can provide would be helpful - in a time crunch with our client to get a resolution on this issue.

Thanks
-Dan

|||

Dan - not sure if you've done this yet...but SQL Server 2005 Service Pack 1 appears to have fixed this issue in our environment.

Jon

|||It does indeed! Thanks for your note Jon!