Upgrade to CRM 4.0 issue: Error in Reporting Services due to localization? RRS feed

  • Question

  • I upgraded to CRM 4.0 but I have difficulty getting Reporting Services to work. When I try to run any report I am getting the following error:

  • "Ungültiges Zeichen in der angegebenen Codierung. Zeile 2, Position 86."

    Translated literally this means:

    "Invalid character in the specified encoding. Line 2, position 86"


    How can I track down the source of this error?


    I have the feeling that it could have to do with German number formatting. After upgrading I had another problem when recalculating invoices. CRM used for no apparent reason the number format (no comma involved). I had to change it to US and then back to German. After that it was correct: 1.000.000,00

    This had to be done for every CRM user.


    Maybe it has nothing to with that at all. So any idea how to solve the problem is very much appreciated.




Saturday, August 23, 2008 9:32 PM

All replies

  • When you say any report, do you mean just any report in CRM, or any report run off of the report server?  Your theory sounds like it might be a good one, the test would be to download one of the reports (which you can do in the edit report screen, open up in visual studio, change the format, and then upload it again.


    If you create a new report, say with the report wizard, do you also get these errors when you run those reports?

    Sunday, August 24, 2008 11:06 AM
  • I mean any report even reports I create from within CRM.


    I have difficulty setting up Visual Studio to execute it in there.


    I had a look into the event logs and found an interesting entry which contains a stack trace of the exception. I think that it's throwing an exception while parsing an XML file. Maybe someone can make a more educated guess than myself so that we can track down the error.


    Ereigniscode: 3005
    Ereignismeldung: An unhandled exception has occurred.
    Ereigniszeit: 28.08.2008 20:33:18
    Ereigniszeit (UTC): 28.08.2008 18:33:18
    Ereignis-ID: 46206e958dec4e4382b947876114bb87
    Ereignissequenz: 164
    Vorkommen: 5
    Ereignisdetailcode: 0
        Anwendungsdomäne: /LM/W3SVC/396012969/root/Reports-2-128644203693294480
        Vertrauensebene: RosettaMgr
        Virtueller Anwendungspfad: /Reports
        Anwendungspfad: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\ReportManager\
        Computername: S15249665
        Prozess-ID: 7924
        Prozessname: w3wp.exe
        Ausnahmetyp: XmlException
        Ausnahmemeldung: Ungültiges Zeichen in der angegebenen Codierung. Zeile 2, Position 86.
        Anforderungs-URL: http://www.ourserver.de/Reports/Reserved.ReportViewerWebControl.axd?OpType=StyleSheet&Version=2005.090.3042.00
        Anforderungspfad: /Reports/Reserved.ReportViewerWebControl.axd
        Benutzer: SATURN\Dirk
        Ist authentifiziert: True
        Authentifizierungstyp: Negotiate
        Threadkontoname: NT-AUTORITÄT\NETZWERKDIENST
        Thread-ID: 5
        Threadkontoname: NT-AUTORITÄT\NETZWERKDIENST
        Identitätswechsel für: True
        Stapelüberwachung:    bei System.Xml.XmlTextReaderImpl.Throw(Exception e)
       bei System.Xml.XmlTextReaderImpl.Throw(String res, String arg)
       bei System.Xml.XmlTextReaderImpl.Throw(Int32 pos, String res)
       bei System.Xml.XmlTextReaderImpl.InvalidCharRecovery(Int32& bytesCount, Int32& charsCount)
       bei System.Xml.XmlTextReaderImpl.GetChars(Int32 maxCharsCount)
       bei System.Xml.XmlTextReaderImpl.ReadData()
       bei System.Xml.XmlTextReaderImpl.ParseText(Int32& startPos, Int32& endPos, Int32& outOrChars)
       bei System.Xml.XmlTextReaderImpl.FinishPartialValue()
       bei System.Xml.XmlTextReaderImpl.get_Value()
       bei System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
       bei System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
       bei System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
       bei System.Xml.XmlDocument.Load(XmlReader reader)
       bei Microsoft.Reporting.WebForms.WebRequestHelper.ExceptionFromWebResponse(Exception e)
       bei Microsoft.Reporting.WebForms.ServerReport.ServerUrlRequest(Boolean isAbortable, String url, Stream outputStream, String& mimeType, String& fileNameExtension)
       bei Microsoft.Reporting.WebForms.ServerReport.GetStyleSheet(String styleSheetName)
       bei Microsoft.Reporting.WebForms.ReportServerStyleSheetOperation.PerformOperation(NameValueCollection urlQuery, HttpResponse response)
       bei Microsoft.Reporting.WebForms.HttpHandler.ProcessRequest(HttpContext context)
       bei System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
       bei System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
    Details des benutzerdefinierten Ereignisses:

    Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.

    Thursday, August 28, 2008 7:14 PM
  • Did you resolve the Problem?
    I have the same with my 2005 Reportserver.

    lg Andy
    Tuesday, November 3, 2009 3:12 PM