Errors: Recovery Mode: Full and Simple

Hi
I have a production database that is set to Recovery Mode: Simple.
However I decided to change this to Recovery Mode: Full. A scheduled
backup of the database was then run that night.
Unfortunately I was then told to reset the Recovery Mode back to
Simple as not enough testing had been done. So I did this.
The next day we received error messages that "The log file for the
database is full. Back up the transaction log for the database to free
up some log space."
The production db was then unusable for the apps. As a quick solution
I changed the recovery mode back to full and backed up the transaction
log ( because you cannot backup the transaction log in simple mode).
This made the database operational again.
I then changed the Recovery mode back to simple for the next night's
scheduled backup.
So..... the nightly backup goes ahead with the db still in simple
mode.
HOWEVER we are still getting the log full error messages and I keep
having to change to recovery mode full and backup the transaction log
and then swap back again to simple mode.
I realise that if the database is set to Recovery Mode: Full then the
transaction log must be backed up regularly. But we are no longer
running in Full mode and I don’t not want to run in full mode
and the transaction logs never used to get full in Simple mode and we
never had to back them up.
I would just like things to get back to how they were - the database
running in simple mode and nightly backups taking place. Then those
nightly backups - which are in one file - restoring ok on a test
machine.
Has anyone got any ideas?
Many thanks!
Thiko!Thiko
How large is your transaction log? Even with simple
recovery model the transaction log is still used.
It is just cleared when transactions complete. If you have
some/one very large transaction running on the system you
may still fill up the transaction log even in simple
recovery mode.
If your transaction log is quite small, you may solve your
problem by increasing it.
Regards
Johnsql

Errors with SRS in Sharepoint Integration Mode

Hi Everyone,

Our project has two servers. One server is running WSS 3.0 and the SQL Reporting Services web front-end. We have a second server that operates all the databases involved (WSS Content, SRS, and our application specific DB).

We do not have a domain controller in our architecture. The WSS site is configured to use SQL authentication to connnect and modify the WSS Content database. We installed SRS, SRS service pack 2, and the Sharepoint add-in. We are using forms authentication for our WSS site. We would like to use SRS in Sharepoint Integration mode, but we are unable to create datasources, view reports, etc. SRS is configured to use the "Trusted Account" in WSS Central Admin.

When we attempt to create a new datasource, and we received an error stating the object moved and to check that SRS is in Sharepoint integration mode.

When we attempt to view a report, we get an error stating:

"An unexpected error occurred while connecting to the report server. Verify that the report server is available and configured for SharePoint integrated mode."

I have a feeling this has to do with the Windows Service Account and the Web Service Identity for SRS. What type of account should we use since we do not have a domain?

Thank you,

Michael milazzo

As explained here, in Trusted Account mode, WSS sends the requests to the Report Server under the identity of the SharePoint application. By default, the IIS 6.0 application pool runs under NT AUTHORITY\Network Service. Since you don't have a domain setup, try changing the application domain identity to a local Windows user account which has the same name and password as a privileged account on the Report Server that has access to the report catalog. If you had domain setup, the request could have gone under Domain\WSS machine name$ and you could have granted access to that account.

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