Errors exporting to excel

Report works fine in HTML and exporting to PDF but when exporting to excel and opening the file we receive a notification that errors were detected and a repair was attempted. The repair notification states that the damage to the file was too extensive to repair and the file can be opened with only the raw tabular data (no formatting or charts).
This only happens with certain parameter values?
--
Message posted via http://www.sqlmonster.comThere are a couple of fixes out there for Excel. Take a look at
Microsoft.com for Excel\Reporting services issues.
If you have a good repro I can do in house, please send it to me.
--
| From: "William Nichols via SQLMonster.com" <forum@.SQLMonster.com>
| Subject: Errors exporting to excel
| Date: Fri, 28 Jan 2005 13:07:35 GMT
| Organization: http://www.SQLMonster.com
| Message-ID: <b4e260ddb47c48b7bf16a89e152b3412@.SQLMonster.com>
| X-Abuse-Report: http://www.SQLMonster.com/Uwe/NB/Abuse.aspx
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| NNTP-Posting-Host: 178.67-18-207.reverse.theplanet.com 67.18.207.178
| Lines: 1
| Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXS01.phx.gbl!cpmsftngxa06.phx.gbl!TK2MSFTNGP08
.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.reportingsvcs:41174
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Report works fine in HTML and exporting to PDF but when exporting to
excel and opening the file we receive a notification that errors were
detected and a repair was attempted. The repair notification states that
the damage to the file was too extensive to repair and the file can be
opened with only the raw tabular data (no formatting or charts).
|
| This only happens with certain parameter values?
|
| --
| Message posted via http://www.sqlmonster.com
||||I've got the same problem!
I turned off the legend on the chart, and now it works perfectly!
Any ideas'
Try turning off the legend and let me know if that worked.
- Joel
"William Nichols via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:b4e260ddb47c48b7bf16a89e152b3412@.SQLMonster.com...
> Report works fine in HTML and exporting to PDF but when exporting to excel
> and opening the file we receive a notification that errors were detected
> and a repair was attempted. The repair notification states that the
> damage to the file was too extensive to repair and the file can be opened
> with only the raw tabular data (no formatting or charts).
> This only happens with certain parameter values?
> --
> Message posted via http://www.sqlmonster.com

Error:The type initializer for "Microsoft.ReportDesigner.Drawing.Language" threw an except

Hi,
I've been trying to get to the bottom of this error it prevents be
from loading the report in Design Mode. As of right now when opening
a report in design mode through the VS .Net 2003 IDE I get the
following:
Deserialization failed: The type initializer for
"Microsoft.ReportDesigner.Drawing.Language" threw an exception.
I've tried uninstall/reinstall, reporting services service pack 1 and
debuging the devenv.exe from another ide instance. Debug error is:
System.ComponentModel.Design.Serialization.CodeDomSerializerException:
Deserialization failed: The type initializer for
"Microsoft.ReportDesigner.Drawing.Language" threw an exception. -->
Microsoft.DataWarehouse.Serialization.XmlSerializationException:
Deserialization failed: The type initializer for
"Microsoft.ReportDesigner.Drawing.Language" threw an exception. -->
System.TypeInitializationException: The type initializer for
"Microsoft.ReportDesigner.Drawing.Language" threw an exception. -->
System.ArgumentException: Culture ID 31770 (0x7C1A) is not a supported
culture.
Parameter name: culture
at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean
useUserOverride)
at System.Globalization.CultureTable.GetCultures(CultureTypes
types)
at Microsoft.ReportDesigner.Drawing.Language.GetStandardValues()
at Microsoft.ReportDesigner.Drawing.Language..cctor()
-- End of inner exception stack trace --
at Microsoft.ReportDesigner.Drawing.Language..ctor(String value)
at Microsoft.ReportDesigner.Drawing.LanguageConverter.CreateObject(String
value)
at Microsoft.ReportDesigner.Drawing.XmlStringListConverter.ConvertFrom(ITypeDescriptorContext
context, CultureInfo culture, Object value)
at System.ComponentModel.DefaultValueAttribute..ctor(Type type,
String value)
-- End of inner exception stack trace --
at Microsoft.ReportDesigner.Serialization.DesignXmlReader.ReadRoot(Type
type)
at Microsoft.ReportDesigner.Serialization.DesignXmlReader.DeserializeComponent(IDesignerSerializationManager
manager, XmlReader reader, Type root)
at Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.DeserializeObject(IDesignerSerializationManager
manager, Object serializationStream)
at Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.Deserialize(IDesignerSerializationManager
manager, Object serializationStream)
at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseDesignerLoader.Deserialize()Hi, I got the same error here, if you already fixed this problem, please post
here waht is going on.
Thanks, Rafael
"Ricardo" wrote:
> Hi,
> I've been trying to get to the bottom of this error it prevents be
> from loading the report in Design Mode. As of right now when opening
> a report in design mode through the VS .Net 2003 IDE I get the
> following:
> Deserialization failed: The type initializer for
> "Microsoft.ReportDesigner.Drawing.Language" threw an exception.
> I've tried uninstall/reinstall, reporting services service pack 1 and
> debuging the devenv.exe from another ide instance. Debug error is:
> System.ComponentModel.Design.Serialization.CodeDomSerializerException:
> Deserialization failed: The type initializer for
> "Microsoft.ReportDesigner.Drawing.Language" threw an exception. -->
> Microsoft.DataWarehouse.Serialization.XmlSerializationException:
> Deserialization failed: The type initializer for
> "Microsoft.ReportDesigner.Drawing.Language" threw an exception. -->
> System.TypeInitializationException: The type initializer for
> "Microsoft.ReportDesigner.Drawing.Language" threw an exception. -->
> System.ArgumentException: Culture ID 31770 (0x7C1A) is not a supported
> culture.
> Parameter name: culture
> at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean
> useUserOverride)
> at System.Globalization.CultureTable.GetCultures(CultureTypes
> types)
> at Microsoft.ReportDesigner.Drawing.Language.GetStandardValues()
> at Microsoft.ReportDesigner.Drawing.Language..cctor()
> -- End of inner exception stack trace --
> at Microsoft.ReportDesigner.Drawing.Language..ctor(String value)
> at Microsoft.ReportDesigner.Drawing.LanguageConverter.CreateObject(String
> value)
> at Microsoft.ReportDesigner.Drawing.XmlStringListConverter.ConvertFrom(ITypeDescriptorContext
> context, CultureInfo culture, Object value)
> at System.ComponentModel.DefaultValueAttribute..ctor(Type type,
> String value)
> -- End of inner exception stack trace --
> at Microsoft.ReportDesigner.Serialization.DesignXmlReader.ReadRoot(Type
> type)
> at Microsoft.ReportDesigner.Serialization.DesignXmlReader.DeserializeComponent(IDesignerSerializationManager
> manager, XmlReader reader, Type root)
> at Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.DeserializeObject(IDesignerSerializationManager
> manager, Object serializationStream)
> at Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.Deserialize(IDesignerSerializationManager
> manager, Object serializationStream)
> at Microsoft.DataWarehouse.VsIntegration.Designer.Serialization.DataWarehouseDesignerLoader.Deserialize()
>|||I have problem in Reporting Services 2005 with width of report - max. limit is probably 406,34921 cm. Is it possible to increase this limit to for exapmle 450 cm ?
From http://www.developmentnow.com/g/115_2004_11_0_0_453315/ErrorThe-type-initializer-for-Microsoft-ReportDesigner-Drawing-Language-threw-an-exception.ht
Posted via DevelopmentNow.com Group
http://www.developmentnow.com

Error:sql mobile encountered problems when opening the database

I am trying to deploy my mobile app to treo 700wx, but when i test the app, the application gives me an error message:

sql mobile encountered problems when opening the database

It happens when I sync data.

However, when I sync data users and customer info, it doesn't give this message, But when I sync (third time) order info, this message comes out.

--when i run on my PPC (HP ra1950), there is no this error message.

I think it is a bug?

BTW, which cabs file should I install on the Treo phone? (.Net ce, sql ce mobile30 ?)

Please help me out. Thanks

James

This problem may be caused by not disposing the replication object. Make sure you always dispose all the data related objects.

These 2 forum entries refer to this problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=334604&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=478902&SiteID=1|||It may be caused by the System.Data.SqlServerCe versioning. if you are doing merge replication in using VS orcas you need to use the compact edition 3.5 instead of 9.0.242.0 Syatem.Data.SqlServerCe assembly. if you insist of using the 9.0242.0 then you need to add those compact 3.5 edition 7's .dlls in to your execution directory. The dlls are sqlceca30.dll, sqlcecompact30.dll, sqlceer30EN.dll, sqlceme30.dll, sqlceoledb30.dll, sqlceqp30.dll, sqlcese30.dll. Try to remove and add the assembly.

Error:sql mobile encountered problems when opening the database

I am trying to deploy my mobile app to treo 700wx, but when i test the app, the application gives me an error message:

sql mobile encountered problems when opening the database

It happens when I sync data.

However, when I sync data users and customer info, it doesn't give this message, But when I sync (third time) order info, this message comes out.

--when i run on my PPC (HP ra1950), there is no this error message.

I think it is a bug?

BTW, which cabs file should I install on the Treo phone? (.Net ce, sql ce mobile30 ?)

Please help me out. Thanks

James

This problem may be caused by not disposing the replication object. Make sure you always dispose all the data related objects.

These 2 forum entries refer to this problem:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=334604&SiteID=1

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=478902&SiteID=1
|||It may be caused by the System.Data.SqlServerCe versioning. if you are doing merge replication in using VS orcas you need to use the compact edition 3.5 instead of 9.0.242.0 Syatem.Data.SqlServerCe assembly. if you insist of using the 9.0242.0 then you need to add those compact 3.5 edition 7's .dlls in to your execution directory. The dlls are sqlceca30.dll, sqlcecompact30.dll, sqlceer30EN.dll, sqlceme30.dll, sqlceoledb30.dll, sqlceqp30.dll, sqlcese30.dll. Try to remove and add the assembly.