Hello everyone,
I've come across an unusual error on some of our machines. I'm trying to track down why only certain ones will give an error. I thought it might have something to do with .NET 2.0 not being installed, but I assume that they wouldn't even be able to launch Report Builder if this is the case. I'm at the point now where I've been told these machines have .NET 2.0. I plan on trying to verify soon, but I thought I'd get everyone's opinion on what it could be.
With even the simplist report (just 1 field dragged onto the report) the following error appears: "Report execution error The report might not be valid or the server could not process the data." When I clicked on the details, the following appears: "The numeric portion of 0pt cannot be parsed as a unit of type Point. -- The type initializer for 'Microsoft.ReportingServices.Design.Constants' threw an exception."
This model was created with Business Intelligence Development Studio and we're using SQL 2005 Enterprise.
Anyone have any thoughts on what this could be or how I can better troubleshoot it?
Thanks,
Dan
Alright, I think I've narrowed the problem down, although I still don't have a viable solution.
I had a similar problem with Analysis Services. The user could not browse a cube or dimension. We ended up solving this by recreating the user's profile.
Using that knowledge, I was working with someone from our desktop group today. We had the user who was having this unusual error try logging in on another machine. When she did this, the Report Builder worked perfectly. I am not personally well versed on how anything with profiles work, but it appears that the new profile that was put on the the new machine was different than the older one, and everything worked.
At this point I'm still stuck not knowing how to troubleshoot it any further. The desktop group is going to try to look at the profiles and determine what the differences might be, but I don't know how well that will work.
Re-creating everyone's profiles is not going to work (especially for what could be 100 users) and this will definately lose some of our user support. I understand this might not be the type of question for this group, but If anyone has come across a similar situation like this, I would appreciate some insight.
Regards,
Dan
|||Hi Dan,
can you send an RDL that causes the problem?
In Report Builder, create report, go to File -> Save to File...
almineev atatat microsoft dotdot com
|||I'm fairly confident it doesn't have anything to do with the RDL/Report itself, but doing this allowed me to get some more details about what is happening.
I’m having trouble saving the report on that user’s computer.I have tried saving to a file and saving to the My Reports folder (this user has admin privs on the report server).It gives this error: Operation failed An error occurred while processing your request. Save your report and restart the application. The contents of the details section is the same as the first message I posted.
We tried one more thing.We attempted to close the report builder app (using the X on the toolbar) and it prompted to save.We clicked yes and we got a much more detailed stack trace.I have included this below. I excluded the assembly information.
Dan
************** Exception Text **************
System.TypeInitializationException: The type initializer for 'Microsoft.ReportingServices.Design.Constants' threw an exception. > System.FormatException: The numeric portion of 0pt cannot be parsed as a unit of type Point.
at Microsoft.ReportingServices.Design.RdlModel.Unit.Init(String value, CultureInfo culture, UnitType defaultType)
at Microsoft.ReportingServices.Design.RdlModel.Unit..ctor(String value, CultureInfo culture, UnitType defaultType)
at Microsoft.ReportingServices.Design.RdlModel.StyleUnit..ctor(String exprStr)
at Microsoft.ReportingServices.Design.Constants..cctor()
End of inner exception stack trace
at Microsoft.ReportingServices.Design.RdlModel.Margins.set_Top(Unit value)
at Microsoft.ReportingServices.Design.RdlModel.Margins..ctor()
at Microsoft.ReportingServices.Design.RdlModel.Report..ctor()
at Microsoft.ReportingServices.ReportBuilder.ReportModel.Report.WriteTo(TextWriter w)
at Microsoft.ReportingServices.ReportBuilder.MainForm.GetReportRdlBytes()
at Microsoft.ReportingServices.ReportBuilder.MainForm.SaveReportToServer(String reportPath)
at Microsoft.ReportingServices.ReportBuilder.MainForm.SaveReportToServer(Boolean doSaveAs)
at Microsoft.ReportingServices.ReportBuilder.MainForm.CanDiscardChanges()
at Microsoft.ReportingServices.ReportBuilder.MainForm.OnClosing(CancelEventArgs e)
at System.Windows.Forms.Form.WmClose(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
