Invalid character in a report

Hi!

Trying to generate a report (using WebForm ReportViewer, from dynamically created RDL report and SQL Server 2005 OLAP cube), if a database field contains control characters (code < 0x20), Reporting Services generate following message:

' ', hexadecimal value 0x02, is an invalid character. Line 1, position 2376.

Is it possible to ignore that? I don't care if browser shows an octopus, the report must work.

Thanks, Andrei.

Could you publish RDL (or e-mail it to me)?

thanks!

|||

Lev,

I've just emailed RDL and other details to you.

I could reproduce the problem using sample AdventureWorksDW and OLAP (standard edition).

Create an OLAP table report, put e.g. Model Name in one of columns. The report works fine. Now change e.g. ModelName for one of products, to include control character(s), e.g.:

update DimProduct
set ModelName = 'Mountain-100 ' + char(31) + char(2) + ' AB'
where ProductAlternateKey = 'BK-M82S-38'

Reprocess Product dimension.

Refresh the report. Once Montain-100 model is about to be displayed on the page you should get following message:

hexadecimal value 0x1F, is an invalid character. Line 1, position 2385.

I've just noticed that after the change applied even OLAP browser of SQL Server Management Studio generates the same error if only the ModelName is about to be displayed.

So it may be Analysis Service's problem indeed.

I've tried with non-OLAP reports in Reporting Services, and they work fine, displaying square placeholders.

|||That is known AS issue. Certain control characters cannot be transmitted from server to client.

Invalid character in a report

Hi!

Trying to generate a report (using WebForm ReportViewer, from dynamically created RDL report and SQL Server 2005 OLAP cube), if a database field contains control characters (code < 0x20), Reporting Services generate following message:

' ', hexadecimal value 0x02, is an invalid character. Line 1, position 2376.

Is it possible to ignore that? I don't care if browser shows an octopus, the report must work.

Thanks, Andrei.

Could you publish RDL (or e-mail it to me)?

thanks!

|||

Lev,

I've just emailed RDL and other details to you.

I could reproduce the problem using sample AdventureWorksDW and OLAP (standard edition).

Create an OLAP table report, put e.g. Model Name in one of columns. The report works fine. Now change e.g. ModelName for one of products, to include control character(s), e.g.:

update DimProduct
set ModelName = 'Mountain-100 ' + char(31) + char(2) + ' AB'
where ProductAlternateKey = 'BK-M82S-38'

Reprocess Product dimension.

Refresh the report. Once Montain-100 model is about to be displayed on the page you should get following message:

hexadecimal value 0x1F, is an invalid character. Line 1, position 2385.

I've just noticed that after the change applied even OLAP browser of SQL Server Management Studio generates the same error if only the ModelName is about to be displayed.

So it may be Analysis Service's problem indeed.

I've tried with non-OLAP reports in Reporting Services, and they work fine, displaying square placeholders.

|||That is known AS issue. Certain control characters cannot be transmitted from server to client.

Interop.DTS in SQL 2005?

Been given a vbs project that uses Interop.DTS object to dynamically create a DTS package for data transfer.

Will this code work on a SQL 2005 server?

I'm going to take a stab and say "no" because DTS is no longer shipped with SQL Server. Instead, the new product, SSIS is shipped with Standard, Enterprise, and Developer editions. SSIS contains its own API, of which Interop.DTS is not part of.|||Yeah, i'm assuming DTS isn't supported.|||The DTS runtime ships with SQL 2005 and is supported. It is an option during installation, and

the best thing about the DTS to SSIS migration story is that you can upgrade o SQL 2005, and DTS keeps working.

For more info try the documentation - Books Online - http://msdn2.microsoft.com/en-us/library/ms143706.aspx

Interop.DTS in SQL 2005?

Been given a vbs project that uses Interop.DTS object to dynamically create a DTS package for data transfer.

Will this code work on a SQL 2005 server?

I'm going to take a stab and say "no" because DTS is no longer shipped with SQL Server. Instead, the new product, SSIS is shipped with Standard, Enterprise, and Developer editions. SSIS contains its own API, of which Interop.DTS is not part of.|||Yeah, i'm assuming DTS isn't supported.|||The DTS runtime ships with SQL 2005 and is supported. It is an option during installation, and

the best thing about the DTS to SSIS migration story is that you can upgrade o SQL 2005, and DTS keeps working.

For more info try the documentation - Books Online - http://msdn2.microsoft.com/en-us/library/ms143706.aspx