Problem with machine that has only reporting services2005 installe

Hello all,
I am new to reporting services.
We have one installation of reporting services with SQL server 2005 and
Analysis services 2005 on one machine, and we have another server with only
Reporting services 2005 installed (a proxy server). I dont have a problem
with the first machine, but the second machine keeps showing this error when
i try to enter the default 'Report service' page:
http://localhost/reports
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later.
----
A name was started with an invalid character. Error processing resource
'http://ar2krepprox/Reports/'. Line 1, Position 2
<%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
Inherits="Microsoft.ReportingServices.UI.HomePag...
I am able to deploy reports, but when run them i get this error:
' Your browser does not support scripts or has been configured not to allow
scripts. Click here to view this report without scripts. '
How do i get rid of these errors?
Is there any way to create a data driven subscription through the SQL Server
management studio?
I encountered no installation errors!
Thanks in advance
IshanI found the solution!!
a shout note by luna.dave@.gmail.com was v helpful
"Ishan Bhalla" wrote:
> Hello all,
> I am new to reporting services.
> We have one installation of reporting services with SQL server 2005 and
> Analysis services 2005 on one machine, and we have another server with only
> Reporting services 2005 installed (a proxy server). I dont have a problem
> with the first machine, but the second machine keeps showing this error when
> i try to enter the default 'Report service' page:
> http://localhost/reports
> The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
> ----
> A name was started with an invalid character. Error processing resource
> 'http://ar2krepprox/Reports/'. Line 1, Position 2
> <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.HomePag...
> I am able to deploy reports, but when run them i get this error:
> ' Your browser does not support scripts or has been configured not to allow
> scripts. Click here to view this report without scripts. '
> How do i get rid of these errors?
> Is there any way to create a data driven subscription through the SQL Server
> management studio?
> I encountered no installation errors!
> Thanks in advance
> Ishan
>|||Within IIS Manager on your RS server check you have Scripts Enabled on the
"Home Directory" tab.
Paul Walsh
"Ishan Bhalla" wrote:
> Hello all,
> I am new to reporting services.
> We have one installation of reporting services with SQL server 2005 and
> Analysis services 2005 on one machine, and we have another server with only
> Reporting services 2005 installed (a proxy server). I dont have a problem
> with the first machine, but the second machine keeps showing this error when
> i try to enter the default 'Report service' page:
> http://localhost/reports
> The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
> ----
> A name was started with an invalid character. Error processing resource
> 'http://ar2krepprox/Reports/'. Line 1, Position 2
> <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.HomePag...
> I am able to deploy reports, but when run them i get this error:
> ' Your browser does not support scripts or has been configured not to allow
> scripts. Click here to view this report without scripts. '
> How do i get rid of these errors?
> Is there any way to create a data driven subscription through the SQL Server
> management studio?
> I encountered no installation errors!
> Thanks in advance
> Ishan
>

Problem with LoadReport web method

Hi,

I'm working on a reporting client for Reporting Services 2005 using SOAP. The problem I'm having is that for reports with multiple pages or a document map, the LoadReport web method, always says they have 0 pages or no document map.

To simplify the problem, i created a simple console app that just calls LoadReport on the /AdventureWorks Sample Reports/Product Catalog report to see if HasDocumentMap is true (it should be but isn't).

Any suggestions?

Kwan

I figured it out and it makes sense. The information is available only after you call Render.

So call, Render, then GetExecutionInfo to get the correct values for HasDocumentMap and NumPages.

Problem with Lesson 3 in the Analysis Services Tutorial

I am at the step of "Adding an Attribute and Defining Display Folders" where I am experiencing problems. The steps are:

2. In the Attributes pane, select the following attributes by holding down
the CTRL key to select multiple attributes, and then in the Properties
window, set the AttributeHierarchyDisplayFolder property for the selected attributes to "Location":

? City

? Country-Region

? Postal Code

? State-Province

3. In the Hierarchies and Levels pane, click Customer Geography, and then select "Location" as the value of the DisplayFolder property in the
Properties window.

The problem is that there are no choices in the DisplayFolder property of the Customer Geography hierarchy. I do not know how to force "Location" into the property drop down list. The rest of the tutorial has been fine up to this point. What am I missing?

I would guess probably you missed something when defining the cube (Lesson 2). All I can suggest is to start from scratch and do it again carefully following the tutorial instructions.

|||

hello,

i think you should be able to just type in the Location as the value for the display folder in the properties window (as i'd expect that in addition to picking from the list of available values, you should be able to also enter a new one).

hope this helps,

Problem with Large data amounts

I have a dataset with 300,000 records and I'm getting the following error with MS Reporting Services. "An error has occurred during report processing. Exception of type System.OutOfMemoryException was thrown. any help with this would be highly appreciated.

Unfortunately, Reporting Services has some memory limitations in the current (SQL 2K and SQL 2K5). Because we support things like dataset aggregates (you can have sum(x) on the first page of your report), we materialize the entire dataset. Some things you might try:

Do you need the entire data set displayed in the report or could you do some grouping / aggregation in the query?|||

I am having a similar problem with large data amounts. My reporting server is a Dual Xeon 3GHz machine with 2.5GB RAM and still has issues.

What I find is that the reportviewer object is not releasing memory after the reports are generated, viewed and closed. It recycles the application several times if I try to do an export to excel.

Is there any way to be sure to dispose of the memory being allocated by the reportviewer? I can generate one report, close it, wait, open another, and the memory allocation just keeps growing and growing.

Any help is appreciated.

|||

I seem to be having a similar problem with a Xeon and 4Gig of memory. In my case, after the out of memory error happens, remote connections stop working stating that there is insufficient memory. In other words I can't even run a select statement in Management Studio after it hits the memory error. I have to restart the SQL Service.

HELP!!!

|||

First off. A human does not look at 300,000 records. Most of the time I have seen this it has been to export to Excel. When exporting to Excel export as CSV ASCII (although I don't think Excel can handle more that 64,000 records).

Note that this is with records returned, not records in the base table. I go against tables with 150 million records but I only return the data needed.

I suggest looking at design drill through reports to limit the data.

|||

Is this still a problem with Reporting Services? We are having a similar problem with .net choking on large data sets and were considering using Reporting Services as an alternative. Is Microsoft an enterprise player or not?

We are required to periodically return several hundred thousand rows from SQL Server. I'm tired of being told that is a design problem. Unfortunately when our client says he needs to print a detail report from his general ledger for his auditor we don't have the luxury of telling him Microsoft doesn't think he needs that large of a report. If he can't get the data he needs from us, he'll be happy to go down the street to get it (read Oracle).

If I can't serialize it through .net or get it out of Reporting Services, how am I supposed to extract large data sets from SQL Server?

Will 64 bit processors and multi-GB ram implementations help?

Thanks.

Problem with Large data amounts

I have a dataset with 300,000 records and I'm getting the following error with MS Reporting Services. "An error has occurred during report processing. Exception of type System.OutOfMemoryException was thrown. any help with this would be highly appreciated.

Unfortunately, Reporting Services has some memory limitations in the current (SQL 2K and SQL 2K5). Because we support things like dataset aggregates (you can have sum(x) on the first page of your report), we materialize the entire dataset. Some things you might try:

Do you need the entire data set displayed in the report or could you do some grouping / aggregation in the query?|||

I am having a similar problem with large data amounts. My reporting server is a Dual Xeon 3GHz machine with 2.5GB RAM and still has issues.

What I find is that the reportviewer object is not releasing memory after the reports are generated, viewed and closed. It recycles the application several times if I try to do an export to excel.

Is there any way to be sure to dispose of the memory being allocated by the reportviewer? I can generate one report, close it, wait, open another, and the memory allocation just keeps growing and growing.

Any help is appreciated.

|||

I seem to be having a similar problem with a Xeon and 4Gig of memory. In my case, after the out of memory error happens, remote connections stop working stating that there is insufficient memory. In other words I can't even run a select statement in Management Studio after it hits the memory error. I have to restart the SQL Service.

HELP!!!

|||

First off. A human does not look at 300,000 records. Most of the time I have seen this it has been to export to Excel. When exporting to Excel export as CSV ASCII (although I don't think Excel can handle more that 64,000 records).

Note that this is with records returned, not records in the base table. I go against tables with 150 million records but I only return the data needed.

I suggest looking at design drill through reports to limit the data.

|||

Is this still a problem with Reporting Services? We are having a similar problem with .net choking on large data sets and were considering using Reporting Services as an alternative. Is Microsoft an enterprise player or not?

We are required to periodically return several hundred thousand rows from SQL Server. I'm tired of being told that is a design problem. Unfortunately when our client says he needs to print a detail report from his general ledger for his auditor we don't have the luxury of telling him Microsoft doesn't think he needs that large of a report. If he can't get the data he needs from us, he'll be happy to go down the street to get it (read Oracle).

If I can't serialize it through .net or get it out of Reporting Services, how am I supposed to extract large data sets from SQL Server?

Will 64 bit processors and multi-GB ram implementations help?

Thanks.

sql

Problem with Large data amounts

I have a dataset with 300,000 records and I'm getting the following error with MS Reporting Services. "An error has occurred during report processing. Exception of type System.OutOfMemoryException was thrown. any help with this would be highly appreciated.

Unfortunately, Reporting Services has some memory limitations in the current (SQL 2K and SQL 2K5). Because we support things like dataset aggregates (you can have sum(x) on the first page of your report), we materialize the entire dataset. Some things you might try:

Do you need the entire data set displayed in the report or could you do some grouping / aggregation in the query?|||

I am having a similar problem with large data amounts. My reporting server is a Dual Xeon 3GHz machine with 2.5GB RAM and still has issues.

What I find is that the reportviewer object is not releasing memory after the reports are generated, viewed and closed. It recycles the application several times if I try to do an export to excel.

Is there any way to be sure to dispose of the memory being allocated by the reportviewer? I can generate one report, close it, wait, open another, and the memory allocation just keeps growing and growing.

Any help is appreciated.

|||

I seem to be having a similar problem with a Xeon and 4Gig of memory. In my case, after the out of memory error happens, remote connections stop working stating that there is insufficient memory. In other words I can't even run a select statement in Management Studio after it hits the memory error. I have to restart the SQL Service.

HELP!!!

|||

First off. A human does not look at 300,000 records. Most of the time I have seen this it has been to export to Excel. When exporting to Excel export as CSV ASCII (although I don't think Excel can handle more that 64,000 records).

Note that this is with records returned, not records in the base table. I go against tables with 150 million records but I only return the data needed.

I suggest looking at design drill through reports to limit the data.

|||

Is this still a problem with Reporting Services? We are having a similar problem with .net choking on large data sets and were considering using Reporting Services as an alternative. Is Microsoft an enterprise player or not?

We are required to periodically return several hundred thousand rows from SQL Server. I'm tired of being told that is a design problem. Unfortunately when our client says he needs to print a detail report from his general ledger for his auditor we don't have the luxury of telling him Microsoft doesn't think he needs that large of a report. If he can't get the data he needs from us, he'll be happy to go down the street to get it (read Oracle).

If I can't serialize it through .net or get it out of Reporting Services, how am I supposed to extract large data sets from SQL Server?

Will 64 bit processors and multi-GB ram implementations help?

Thanks.

Problem with Large data amounts

I have a dataset with 300,000 records and I'm getting the following error with MS Reporting Services. "An error has occurred during report processing. Exception of type System.OutOfMemoryException was thrown. any help with this would be highly appreciated.

Unfortunately, Reporting Services has some memory limitations in the current (SQL 2K and SQL 2K5). Because we support things like dataset aggregates (you can have sum(x) on the first page of your report), we materialize the entire dataset. Some things you might try:

Do you need the entire data set displayed in the report or could you do some grouping / aggregation in the query?|||

I am having a similar problem with large data amounts. My reporting server is a Dual Xeon 3GHz machine with 2.5GB RAM and still has issues.

What I find is that the reportviewer object is not releasing memory after the reports are generated, viewed and closed. It recycles the application several times if I try to do an export to excel.

Is there any way to be sure to dispose of the memory being allocated by the reportviewer? I can generate one report, close it, wait, open another, and the memory allocation just keeps growing and growing.

Any help is appreciated.

|||

I seem to be having a similar problem with a Xeon and 4Gig of memory. In my case, after the out of memory error happens, remote connections stop working stating that there is insufficient memory. In other words I can't even run a select statement in Management Studio after it hits the memory error. I have to restart the SQL Service.

HELP!!!

|||

First off. A human does not look at 300,000 records. Most of the time I have seen this it has been to export to Excel. When exporting to Excel export as CSV ASCII (although I don't think Excel can handle more that 64,000 records).

Note that this is with records returned, not records in the base table. I go against tables with 150 million records but I only return the data needed.

I suggest looking at design drill through reports to limit the data.

|||

Is this still a problem with Reporting Services? We are having a similar problem with .net choking on large data sets and were considering using Reporting Services as an alternative. Is Microsoft an enterprise player or not?

We are required to periodically return several hundred thousand rows from SQL Server. I'm tired of being told that is a design problem. Unfortunately when our client says he needs to print a detail report from his general ledger for his auditor we don't have the luxury of telling him Microsoft doesn't think he needs that large of a report. If he can't get the data he needs from us, he'll be happy to go down the street to get it (read Oracle).

If I can't serialize it through .net or get it out of Reporting Services, how am I supposed to extract large data sets from SQL Server?

Will 64 bit processors and multi-GB ram implementations help?

Thanks.

Problem with install if machine.config username and password are stored in registry

Hi,
For information.
It looks like the SQL Reporting Services install doesn't work properly
if you have followed Microsoft's advice and have stored the server's
.net credentials (in the machine.config <processModel> element) in the
registry using aspnet_setreg. (You would do this to remove the plain
text entries from the machine.config file).
I have tried this several times and each time, the install just reads
the username and password entries as text, and can't deal with the
fact that these entries are actually pointing to the registry for the
credentials.
When you get to the Service Account screen on the install wizard, the
section entitled "The Report Server Web service will run under the
following account:" shows the following:
registy:HKLM\SOFTWARE\...\ASPNET_SETREG,userName
(or whatever the location is to your encrypted machine.config
settings).
The install starts after you've completed all of the screens in the
wizard, but then can't start the ReportServer web service
(unsurprisingly!).
The only way that I can see to get round this is to change the
machine.config processModel section before the SQL Reporting Services
install so that the userName and password entries are present in
plaintext in the file. This isn't great - particularly if your
entries have been stored in the registry because it's impossible to
find out what the password is if you haven't got a note of it (and
maybe only the Security team were allowed to have the password, etc.).
It also means that there's a possibility that .net things will stop
working on your server while you're doing the install (ie. just
because you don't really want to have to change those entries, for
risk of typos, etc.).
I hope these comments are useful.
Regards,
Rich WFor info, the same is true for when you install SQL Reporting Services
SP1 - ie. you have to change the machine.config processModel username
and password attributes so that they are not being read from the
registry.
Regards,
Rich

Problem with inconsistent report data

I am generating a report using Sql Reporting Services, with Sql Server 2000 as the backend. Sometimes, the report shows data which is not matching with the actual data available in the database. Though the query, which is used by the report is tested in the query analyser and it is successful.

Anyone, who can solve this issue, please !!!

Where are you running the report from? Browser or report viewer or Visual Studio?

If you are using the preview tab in VS then please note that some data gets cached in a <rdl name>.data file on your local drive (same directory as the RDL file). Could this caching be causing your issue?

|||

Thanx Adam.

I tried the report in the preview and also in the browser, the result is the same. The data to the report is generated by using a cursor

declare @.count uniqueidentifier
declare cursor_a cursor for select Busi_ID from Temp_View_BusinessUnit
open cursor_a
fetch next from cursor_a into @.count
insert into Temp_BusinessUnit select distinct(businessunitid)
from FilteredBusinessUnit
where FilteredBusinessUnit.businessunitid in
(select businessunitid from FilteredBusinessUnit where parentbusinessunitid = @.count )
and FilteredBusinessUnit.businessunitid not in (select Busi_ID from Temp_View_BusinessUnit)
WHILE @.@.FETCH_STATUS = 0
BEGIN
fetch next from cursor_a into @.count
insert into Temp_BusinessUnit select distinct(businessunitid) from FilteredBusinessUnit where
FilteredBusinessUnit.businessunitid in
(select businessunitid from FilteredBusinessUnit where parentbusinessunitid = @.count )
and FilteredBusinessUnit.businessunitid not in (select Busi_ID from Temp_View_BusinessUnit)
end
deallocate cursor_a

Is the cursor is the problem to this, because whenever I refresh the report preview or the browser the output from the repor is different and rarely it matches with the actual data in the database. But the same query gives the correct output when executed under the data tab.

I hope that this is what you are expecting.

problem with identifier lengths when connecting Analysis Services to Oracle

Hi All,

I'm currently trying to process a cube that is built off a DSV that points to an Oracle 10g data source. However, I keep getting errors akin to the following:

Error 1 OLE DB error: OLE DB or ODBC error: An error occurred while preparing the query " SELECT "Transaction Type" "CstOrdsTransaction_x0020_Type0_0" FROM "IAL"."BP_BI_CUSTOMER_ORDER_LINE"" for execution against OLE DB provider "MSDAORA.1" for linked server "(null)". ; 42000. 0 0

Some attributes process successfully and others don't. I have noticed that the error occurs only when the generated identifier that it uses to alias the column exceeds 30 characters in length, eg "CstOrdsTransaction_x0020_Type0_0". When I paste the query that Analysis Services is trying to run into PL/SQL Developer, it gives me a "ORA-00972: identifier is too long" error.

I have already ripped through all the tables in my DSV changing the "logical name" in the XML to something shorter (eg "CstOrds" instead of "Customer_Orders") - however, if possible I'd like to avoid the hassle of having to shorten all my column names just to get around this restriction. Then I would have to edit them in my dimension attributes to give them "friendly" names for the user to see, which is a lot of hassle.

Is there any good way to control the identifiers that Analysis Services uses to alias the column names when it processes my cube, such that it doesn't exceed Oracle's 30 character limit for identifiers?

Any help would be appreciated.

Kind regards,

Miles

You can change the Oracle cartridge - orcl7.xsl - (it’s in 2 locations, for both server and tools) to use less characters (like 15, for example). See these settings:

<mssqlcrt:limit-table-identifier-length>29</mssqlcrt:limit-table-identifier-length>

<mssqlcrt:limit-column-identifier-length>29</mssqlcrt:limit-column-identifier-length>

Restart the server/tools

Note that this is not a supported technique but should unblock you...

HTH,

Akshai

|||

Brilliant, thanks for the help Akshai. I've made the change and my cube's processing now... I guess I'll know in a few hours whether or not it worked, as the data I'm processing is huge and the source DB is a couple of continents away at the other end of a VPN ;-)

For anyone else experiencing the same issue - the locations of orcl7.xsl in a default installation of SQL server 2005 are;

c:\Program Files\Microsoft SQL Server\MSSQL.x\OLAP\bin\Cartridges\orcl7.xsl

for the server, and;

c:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\DataWarehouseDesigner\UIRdmsCartridge\orcl7.xsl

for visual studio.

Thanks again for the suggestion Akshai - I knew there must have been a sneaky trick to get around this rather than the horribly clunky XML hacking I was doing in my DSV, Cubes and Dimensions as a workaround.

Kind regards,

Miles

|||Dear All,

I'm having the same problem with Miles. After I edit orcl7.xsl (I change from 30 to 55), and when I try to design the aggregations for the cube it works. But when I want to process the cube an error message appear "Identifier too long", so now I can't process my cube. Before I change the orcl7.xsl I can process the cube. I'm developing the cube using SSAS 2005 64 bit on 64 bit server (x64). The Oracle on the same server with SSAS. I'm already install the oracle client.

The locations of orcl7.xsl in a default installation of SQL server 2005 64 bit are;

c:\Program Files\Microsoft SQL Server\MSSQL.x\OLAP\bin\Cartridges\orcl7.xsl

for the server, and;

c:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\DataWarehouseDesigner\UIRdmsCartridge\orcl7.xsl

for visual studio.

Can you please help me ? I'm looking forward to hear from you. Thanks in advance.
|||

Hi 4lb3rt,

Quick question - do you have a SQL server (or other) data source in your project as well as the oracle one? I did, and that was actually my problem. It seems that my DSV was using the SQL server connection as it's default. Therefore it was actually running all the oracle queries as distributed queries through SQL server. Not only did that make it all horribly slow, but it also caused the error described in the above post. The eventual solution was to get rid of the SQL connection altogether as I didn't need that any more, and ensure that the oracle connection was the default for the DSV. Hope this helps in your case.

Cheers,

Miles

|||Dear Miles,

I don't have another data source in my project except Oracle. FYI, I'm using "Oracle Provider for OLE DB" for the data source provider. Can you please help me ?

Thanks in advance.sql

problem with identifier lengths when connecting Analysis Services to Oracle

Hi All,

I'm currently trying to process a cube that is built off a DSV that points to an Oracle 10g data source. However, I keep getting errors akin to the following:

Error 1 OLE DB error: OLE DB or ODBC error: An error occurred while preparing the query " SELECT "Transaction Type" "CstOrdsTransaction_x0020_Type0_0" FROM "IAL"."BP_BI_CUSTOMER_ORDER_LINE"" for execution against OLE DB provider "MSDAORA.1" for linked server "(null)". ; 42000. 0 0

Some attributes process successfully and others don't. I have noticed that the error occurs only when the generated identifier that it uses to alias the column exceeds 30 characters in length, eg "CstOrdsTransaction_x0020_Type0_0". When I paste the query that Analysis Services is trying to run into PL/SQL Developer, it gives me a "ORA-00972: identifier is too long" error.

I have already ripped through all the tables in my DSV changing the "logical name" in the XML to something shorter (eg "CstOrds" instead of "Customer_Orders") - however, if possible I'd like to avoid the hassle of having to shorten all my column names just to get around this restriction. Then I would have to edit them in my dimension attributes to give them "friendly" names for the user to see, which is a lot of hassle.

Is there any good way to control the identifiers that Analysis Services uses to alias the column names when it processes my cube, such that it doesn't exceed Oracle's 30 character limit for identifiers?

Any help would be appreciated.

Kind regards,

Miles

You can change the Oracle cartridge - orcl7.xsl - (it’s in 2 locations, for both server and tools) to use less characters (like 15, for example). See these settings:

<mssqlcrt:limit-table-identifier-length>29</mssqlcrt:limit-table-identifier-length>

<mssqlcrt:limit-column-identifier-length>29</mssqlcrt:limit-column-identifier-length>

Restart the server/tools

Note that this is not a supported technique but should unblock you...

HTH,

Akshai

|||

Brilliant, thanks for the help Akshai. I've made the change and my cube's processing now... I guess I'll know in a few hours whether or not it worked, as the data I'm processing is huge and the source DB is a couple of continents away at the other end of a VPN ;-)

For anyone else experiencing the same issue - the locations of orcl7.xsl in a default installation of SQL server 2005 are;

c:\Program Files\Microsoft SQL Server\MSSQL.x\OLAP\bin\Cartridges\orcl7.xsl

for the server, and;

c:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\DataWarehouseDesigner\UIRdmsCartridge\orcl7.xsl

for visual studio.

Thanks again for the suggestion Akshai - I knew there must have been a sneaky trick to get around this rather than the horribly clunky XML hacking I was doing in my DSV, Cubes and Dimensions as a workaround.

Kind regards,

Miles

|||Dear All,

I'm having the same problem with Miles. After I edit orcl7.xsl (I change from 30 to 55), and when I try to design the aggregations for the cube it works. But when I want to process the cube an error message appear "Identifier too long", so now I can't process my cube. Before I change the orcl7.xsl I can process the cube. I'm developing the cube using SSAS 2005 64 bit on 64 bit server (x64). The Oracle on the same server with SSAS. I'm already install the oracle client.

The locations of orcl7.xsl in a default installation of SQL server 2005 64 bit are;

c:\Program Files\Microsoft SQL Server\MSSQL.x\OLAP\bin\Cartridges\orcl7.xsl

for the server, and;

c:\Program Files (x86)\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\DataWarehouseDesigner\UIRdmsCartridge\orcl7.xsl

for visual studio.

Can you please help me ? I'm looking forward to hear from you. Thanks in advance.
|||

Hi 4lb3rt,

Quick question - do you have a SQL server (or other) data source in your project as well as the oracle one? I did, and that was actually my problem. It seems that my DSV was using the SQL server connection as it's default. Therefore it was actually running all the oracle queries as distributed queries through SQL server. Not only did that make it all horribly slow, but it also caused the error described in the above post. The eventual solution was to get rid of the SQL connection altogether as I didn't need that any more, and ensure that the oracle connection was the default for the DSV. Hope this helps in your case.

Cheers,

Miles

|||Dear Miles,

I don't have another data source in my project except Oracle. FYI, I'm using "Oracle Provider for OLE DB" for the data source provider. Can you please help me ?

Thanks in advance.|||I did not have this problem (identifier too long) until I tried to design aggregations with multiple partitions. None of my Oracle data exceeds the 30 character limit, so I'm kinda lost. It is new however, since I added some additional columns to my sql for the dsv and the partitions, but they do not exceed 30! I can process, I just can't design aggregations and I sure would like to. If anyone has any more ideas, let me know. AS 2005.

Problem with high Reproting Services 100% Usage

Currently I am running SQL Server 2005 and Reporting Services 2005 on
the same machine. When no reports are being run the CPU usage stays at
100% it is split between sql server and report services 10%/90%. If
anyone can help me, as this seems like some sort of bug with reporting
services, if there is a path I would greatly appreciate it.
Kind Regards
Nilesh ChauhanOn Mar 14, 6:05 am, nilesh.k.chau...@.googlemail.com wrote:
> Currently I am running SQL Server 2005 and Reporting Services 2005 on
> the same machine. When no reports are being run the CPU usage stays at
> 100% it is split between sql server and report services 10%/90%. If
> anyone can help me, as this seems like some sort of bug with reporting
> services, if there is a path I would greatly appreciate it.
> Kind Regards
> Nilesh Chauhan
I have worked w/the same setup recently without problems. Have you
tried rebooting the machine? That may resolve the problem. How long
have you been seeing this CPU usage?
Regards,
Enrique Martinez
Sr. SQL Server Developer

Problem with Forms Authentication

I've followed the Using Forms Authentication in Reporting Services
sample at
MSDN(http://localhost/Reports/Pages/UILogon.aspx?ReturnUrl=http%3a%2f%2flocalhost%2fReports%2fPages%2fFolder.aspx)
and have the following problem:
After I'm "authenticated" in the UILogon.aspx page, it posts back to
itself...so, I'm always stuck at
http://localhost/Reports/Pages/UILogon.aspx?ReturnUrl=http%3a%2f%2flocalhost%2fReports%2fPages%2fFolder.aspx.
Any suggestions?Try accessing using your machine name instead of localhost
Example:
http://MyServer/Reports
"S0103" wrote:
> I've followed the Using Forms Authentication in Reporting Services
> sample at
> MSDN(http://localhost/Reports/Pages/UILogon.aspx?ReturnUrl=http%3a%2f%2flocalhost%2fReports%2fPages%2fFolder.aspx)
> and have the following problem:
> After I'm "authenticated" in the UILogon.aspx page, it posts back to
> itself...so, I'm always stuck at
> http://localhost/Reports/Pages/UILogon.aspx?ReturnUrl=http%3a%2f%2flocalhost%2fReports%2fPages%2fFolder.aspx.
> Any suggestions?
>|||I had that problem. The solution for me was to turn off my anti-virus system
scan. It actually caused a lot of other problems too. My final solution was
to exclude the Reporting Services folders from the scan. After that the
redirect worked fine.
Grahame
"S0103" wrote:
> I've followed the Using Forms Authentication in Reporting Services
> sample at
> MSDN(http://localhost/Reports/Pages/UILogon.aspx?ReturnUrl=http%3a%2f%2flocalhost%2fReports%2fPages%2fFolder.aspx)
> and have the following problem:
> After I'm "authenticated" in the UILogon.aspx page, it posts back to
> itself...so, I'm always stuck at
> http://localhost/Reports/Pages/UILogon.aspx?ReturnUrl=http%3a%2f%2flocalhost%2fReports%2fPages%2fFolder.aspx.
> Any suggestions?
>|||That was it! I've got to stop accessing this group through Google...My
post didn't show up until 5 hours after I posted!|||Glad I was able to help... Happy Dot netting
"S0103" wrote:
> That was it! I've got to stop accessing this group through Google...My
> post didn't show up until 5 hours after I posted!
>

Problem with Form Authentication Example

I installed the Microsoft Forms Authentication in Report Services example in
a VPC running Windows 2003, Active Directory, SQl Server Enterprise and SQL
Reporting Servcie Enterprise Edition.
I registered user "john" and modified RSReportServer.config and added and
changed the value for <UserName> tag to be "john".
Stepping through the debugger the demo fails on GetWebResponse because
cookie is null.
I have tried FQDN in RSWebApplication.config but problem persist.
Any idea what is going wrong causing GetWebResponse to fail?I'm using a solution that's primarily based on the Forms Auth sample and I
can say that it does work. Double-check your web.config modifications for
the ReportServer and ReportManager webs according to the instructions in the
sample.
Adrian M.
"John Amason" <jamason@.ics-associates.com> wrote in message
news:uH%23y30Q$EHA.2580@.TK2MSFTNGP15.phx.gbl...
>I installed the Microsoft Forms Authentication in Report Services example
>in
> a VPC running Windows 2003, Active Directory, SQl Server Enterprise and
> SQL
> Reporting Servcie Enterprise Edition.
> I registered user "john" and modified RSReportServer.config and added and
> changed the value for <UserName> tag to be "john".
> Stepping through the debugger the demo fails on GetWebResponse because
> cookie is null.
> I have tried FQDN in RSWebApplication.config but problem persist.
> Any idea what is going wrong causing GetWebResponse to fail?
>

Problem with external images

Hi!

I've got a real problem with inserting images into report. The problem is that I work with Reporting Services and SharePoint Portal. My employer wants to have CV created dynamically. Information for CV is taken from database under special account with read-only access. And photos of employees can be found with URL

http://corporate-site/Resources/Team/Name_surname.jpg (this string is also generated dynamically). When I preview report on my local machine, everything is Ok, I can see the images. But when deployed the images are not displayed. I have created an Unattended Report Processing Account to get photos. But if I want to use it I must change account for reading data from Data Source (in my case it is SharePointDB.rds) for “Credentials are not required”. And after it I can't get the information for CV.

Does someone know how to use one account for database and another one for getting external image? Or maybe there is another solution for this problem?

Thanks.

Yuliya

The configuration of the unattended account have changed as of February but there is also a solution of how to use url for your reports images, another option is to use stored procedure which means you have to use rectangle for the images and still another option is to store your images with your project. I did the later for a very complex report with just minor problems but it was accepted by the customer. The image control is just like visio shape so your can adjust your images as needed if you did not use the rectangle.

http://blog.toddtaylor.com/PermaLink,guid,b1517702-ad4b-48e1-a6e3-b736e8a982cb.aspx

http://technet.microsoft.com/en-us/library/ms156302.aspx

Problem with event-based activation

I have an application that is set up using Service Broker to pass messages between services asynchronously. I am using event-based external activation and have successfully set up my event notification in SQL Server so if a message appears on any of my Service Broker queues, I'm getting the activation event from SQL Server sent to my activation service.

The problem that I am seeing is that every time I am posting a message onto a Service Broker queue, I am losing the event notification entry in the sys.event_notifications view and I'm not receiving my activation event notifications. When I execute the CREATE EVENT NOTIFICATION T-SQL statement to recreate the event notification, I'm getting the event notification immediately (since there are messages on the queues being monitored). The event notification appears to be registered until the next message is posted on the queue.

Any ideas on what I'm doing wrong?

Thanks,

Michael

Can you check ERRORLOG for any error messages when you see your event notifications being dropped?

Problem with embedded code In REporting Services 2005

Hi,
I have a problem that seems impossible to resolve in RS but i need to be sure.
I'm creating an Embedded Code in VB of course, and i need to run a query within my code to be able to continue the rest of the code depending on the result of my query.
The problem is there is no adodb.recordset or adodb.connection like in normal VB.

So i created my query like as string:

Dim Sql as String
Sql="Select ..." into "from ........where...."

At this point if it was in normal VB,
i would do
MyConnection.Execute(SQL)
and then i will get the answer in my recordset.

I need to know if there is a way in RS to run my query since I cannot use use adodb ....
If it's not really possible, is there way to go around this problem?

Thanks for the Help

Mike
I would think you would need to put your data access code in an assembly, then call the assembly in your report code, but I am not an expert. I'm not sure there is a way around doing it that way, depending on your problem. Of course, it is a bit of a pain to get the report server to use custom assemblies that use System.Data because of security. You need to dig around MSDN and look at Security for Custom Assemblies with SSRS.

Problem with downloading SQL Server 2005 Express

Hello,

I have a problem downloading Microsoft SQL Server 2005 Express Edition with Advanced Services.

Every time I download the complete file (234 mb) I get an error that the downloaded file is corrupt. I've tried also downloading it on other locations but every time the file is corrupt.

Is there another way to obtain this version of SQL server 2005 ?

Where are you downloading from? The update is on Microsoft Update or the Microsoft download center?

Thanks,

Peter Saddow

Problem with Deploying Reports

Hi
When i try to deploy a report from VS, it asks me for a user name and
password to connect to Report Services.
I am the administrator on the machine.
Any help would be appreciated.
--
Gerry ConnollyI am assuming your report server is on another machine? When I deploy
reports to our report server from a remote PC, I am also prompted to log in.
If I deploy reports from the same machine that my report server is on, I'm
not prompted to log in.
"GerryC" <GerryC@.discussions.microsoft.com> wrote in message
news:82C10A8E-35CB-4FC3-8520-9FBD2B5D60A8@.microsoft.com...
> Hi
> When i try to deploy a report from VS, it asks me for a user name and
> password to connect to Report Services.
> I am the administrator on the machine.
> Any help would be appreciated.
> --
> Gerry Connolly

Problem with Date Output in Excel 2007

When we export data mining output including dates through Reporting Services to an Excel spreadsheet, Excel 2007 subtracts 4 years from the dates. Example, the date 11/16/2006 appears in Excel 2007 as 11/16/2002. How should this be handled? Workaround, bug fix, patch,etc.? Thanks, Sam

Sounds very weird to me.

The data renders correctly in Reporting Services, but incorrectly when exported?

Does this only happen with reports built over DMX queries? Do other reports, using SQL or MDX, render correctly in Reporting Services and in Excel?

thanks for any additional clarification you can give.

|||

Thanks, Don. The dates appear correct in the output through Reporting Services that we use as a Front End. When we export to Excel, it comes into Excel 2007 as 4 years earlier. Are the dates in Excel 2007 based on 1900 rather than 1904, and could that be the source of the problem? I will check with the developers on Tuesday with the answer to your other questions about MDX, etc. and will experiment with my SQL queries to see how Excel 2007 handles them so we can figure out if it is an Analysis Services export problem or an Excel 2007 problem.

Sam

|||

Don, Excel 2007 has no trouble bringing in dates from Excel 2003 spreadsheets or from the text output of SQL queries.

I posed your question to our developer. His reply:

Exporting to Excel or any other form is a built-in feature of Microsoft reporting services.I guess it has nothing to do with the way data is generated for the report.Moreover reports are accessing data from SQL server tables and not from the MDX/DMX.

The sequence is data is pumped from analysis server to SQL server table by using the DMX queries .Reports access data from these tables.

I hope this is helpful information--it would be surprising if no one else is having this difficulty witht the built-in export from Microsoft reporting services. Does this provide you with sufficient information to attempt to replicate the problem?

Sam

|||

Thanks. Let's see if we can narrow it down further. (We cannot reproduce the problem here, so I'm sorry but we have to ask you quite a few of these questions to get to the root of the matter.)

Are the results of the DMX queries correct when stored in SQL Server? If yes, and the results are correct when viewed in the report, then I would conclude that the problem is in the Reporting Services Excel export functionality. In that case, we would move this thread to the reporting services forum. (We have already alerted them to issue.) It would not be related to the data mining functionality.

However, if the results stored in the SQL Server are wrong, then it may well be an issue somewhere with the DMX query and we could look into that further.

hth