"Version 2.0 Is Not A Compatible Version"

When using VS2003 and Reporting Services 2005, I am met with the following
compilation error after creating a dataset then trying to design it:
"Version 2.0 Is Not A Compatible Version"
I cant drag any tools to the design surface, or add any fields. I have both
SQL Server 2000 Reporting Services as well as 2005.
Anyone have a hint on how I can remedy this?
Here is the stack:
************** Exception Text **************
System.BadImageFormatException: Version 2.0 is not a compatible version.
at System.Reflection.CustomAttribute.CreateCAObject(Int32& propNum,
Assembly& assembly)
at System.Reflection.CustomAttribute.GetObject()
at
System.Reflection.CustomAttribute.CheckConsistencyAndCreateArray(CustomAttribute
caItem, Type caType)
at System.Reflection.CustomAttribute.GetCustomAttributes(MemberInfo
member, Type caType, Boolean inherit)
at System.Reflection.RuntimeFieldInfo.GetCustomAttributes(Type
attributeType, Boolean inherit)
at System.Xml.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
provider)
at
Microsoft.ReportDesigner.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
provider)
at
Microsoft.ReportDesigner.Serialization.TypeMapper.ImportMemberField(StructMapping
mapping, MemberInfo field)
at
Microsoft.ReportDesigner.Serialization.TypeMapper.ImportTypeMembers(StructMapping
mapping, Object obj)
at
Microsoft.ReportDesigner.Serialization.TypeMapper.ImportStructMapping(Type
objBaseType, Object obj)
at Microsoft.ReportDesigner.Serialization.TypeMapper.GetTypeModel(Type
baseType, Object obj)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
objType, Object obj, String name, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArrayContent(Object
array, ArrayMapping mapping, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArray(Object
array, String name, String ns, ArrayMapping mapping)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteMember(Object
component, Object obj, MemberMapping memberMapping, String name, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructureContent(Object
obj, StructMapping mapping, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructure(Object
obj, String name, String ns, StructMapping mapping)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
objType, Object obj, String name, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.SerializeComponent(IDesignerSerializationManager
manager, Object component, Object serializationStream)
at
Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.Serialize(IDesignerSerializationManager
manager, Object value)
at
Microsoft.ReportDesigner.Serialization.UndoManager.Serialize(CodeDomSerializer
serializer, Object component)
at
Microsoft.ReportDesigner.Serialization.UndoManager.TakeSnapshot(ICollection
undoEntries, UndoSnapshot snapshot)
at
Microsoft.ReportDesigner.Serialization.UndoUnit.ComponentChanging(Object
comp, MemberDescriptor member)
at
Microsoft.ReportDesigner.Serialization.UndoManager.OnComponentChanging(Object
sender, ComponentChangingEventArgs e)
at
System.ComponentModel.Design.ComponentChangingEventHandler.Invoke(Object
sender, ComponentChangingEventArgs e)
at
Microsoft.VisualStudio.Designer.Host.DesignerHost.OnComponentChanging(Object
component, MemberDescriptor member)
at
Microsoft.ReportDesigner.Design.FieldChooserControl.Transaction(Command
command, String sUndo, Field field, Field oldfield)
at Microsoft.ReportDesigner.Design.FieldChooserControl.OnAddClick()
at Microsoft.ReportDesigner.Design.FieldChooserControl.ShowContextMenu()
at
Microsoft.ReportDesigner.Design.FieldChooserControl.listView1_MouseUp(Object
sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.ListView.WmReflectNotify(Message& m)
at System.Windows.Forms.ListView.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)Its an issue with VS 2003 and the 2000 Report Designer. Is there any way I
can specify 2000's Report Designer rather than have it default to 2005?
Right now I cant put the projects in the same solution, and the conversion
wizard tries to convert my web project as well as my report project, which I
do not want.
"Elliot Rodriguez" <elliotrodriguezatgeemaildotcom> wrote in message
news:eolheyESGHA.5656@.TK2MSFTNGP11.phx.gbl...
> When using VS2003 and Reporting Services 2005, I am met with the following
> compilation error after creating a dataset then trying to design it:
> "Version 2.0 Is Not A Compatible Version"
> I cant drag any tools to the design surface, or add any fields. I have
> both SQL Server 2000 Reporting Services as well as 2005.
> Anyone have a hint on how I can remedy this?
> Here is the stack:
> ************** Exception Text **************
> System.BadImageFormatException: Version 2.0 is not a compatible version.
> at System.Reflection.CustomAttribute.CreateCAObject(Int32& propNum,
> Assembly& assembly)
> at System.Reflection.CustomAttribute.GetObject()
> at
> System.Reflection.CustomAttribute.CheckConsistencyAndCreateArray(CustomAttribute
> caItem, Type caType)
> at System.Reflection.CustomAttribute.GetCustomAttributes(MemberInfo
> member, Type caType, Boolean inherit)
> at System.Reflection.RuntimeFieldInfo.GetCustomAttributes(Type
> attributeType, Boolean inherit)
> at System.Xml.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
> provider)
> at
> Microsoft.ReportDesigner.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
> provider)
> at
> Microsoft.ReportDesigner.Serialization.TypeMapper.ImportMemberField(StructMapping
> mapping, MemberInfo field)
> at
> Microsoft.ReportDesigner.Serialization.TypeMapper.ImportTypeMembers(StructMapping
> mapping, Object obj)
> at
> Microsoft.ReportDesigner.Serialization.TypeMapper.ImportStructMapping(Type
> objBaseType, Object obj)
> at Microsoft.ReportDesigner.Serialization.TypeMapper.GetTypeModel(Type
> baseType, Object obj)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
> objType, Object obj, String name, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArrayContent(Object
> array, ArrayMapping mapping, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArray(Object
> array, String name, String ns, ArrayMapping mapping)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteMember(Object
> component, Object obj, MemberMapping memberMapping, String name, String
> ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructureContent(Object
> obj, StructMapping mapping, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructure(Object
> obj, String name, String ns, StructMapping mapping)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
> objType, Object obj, String name, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.SerializeComponent(IDesignerSerializationManager
> manager, Object component, Object serializationStream)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.Serialize(IDesignerSerializationManager
> manager, Object value)
> at
> Microsoft.ReportDesigner.Serialization.UndoManager.Serialize(CodeDomSerializer
> serializer, Object component)
> at
> Microsoft.ReportDesigner.Serialization.UndoManager.TakeSnapshot(ICollection
> undoEntries, UndoSnapshot snapshot)
> at
> Microsoft.ReportDesigner.Serialization.UndoUnit.ComponentChanging(Object
> comp, MemberDescriptor member)
> at
> Microsoft.ReportDesigner.Serialization.UndoManager.OnComponentChanging(Object
> sender, ComponentChangingEventArgs e)
> at
> System.ComponentModel.Design.ComponentChangingEventHandler.Invoke(Object
> sender, ComponentChangingEventArgs e)
> at
> Microsoft.VisualStudio.Designer.Host.DesignerHost.OnComponentChanging(Object
> component, MemberDescriptor member)
> at
> Microsoft.ReportDesigner.Design.FieldChooserControl.Transaction(Command
> command, String sUndo, Field field, Field oldfield)
> at Microsoft.ReportDesigner.Design.FieldChooserControl.OnAddClick()
> at Microsoft.ReportDesigner.Design.FieldChooserControl.ShowContextMenu()
> at
> Microsoft.ReportDesigner.Design.FieldChooserControl.listView1_MouseUp(Object
> sender, MouseEventArgs e)
> at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
> at System.Windows.Forms.ListView.WmReflectNotify(Message& m)
> at System.Windows.Forms.ListView.WndProc(Message& m)
> at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
> at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
>

"Next Page" is extremely slow - like it's requerying

I have a report with a single dataset, 3-levels of table grouping, and
returns 5 pages. When I preview the report in VStudio, it returns the 5
pages and I can navigate the pages real quickly. The problem is, when I run
it online via the RS front-end and click "Next Page," it takes a good 30
seconds to load the subsequent page or pages. The query itself runs in about
45 seconds, but why is the paging not near instantaneous?
Thanks,
jI hope you must have asked some questions yourself like
1. Is this report is slow or all the reports are slow?
2. Is your dev environment and production is different then how fast is your
production machine, is the machine slow (database server)?
3. Is Cache enabled/disabled ?
4. Are you doing the dev and online chking on the same machine ?
Probabily you can go to configuration from RS manager screen and check for
the cache options.
Amarnath
"Jordan" wrote:
> I have a report with a single dataset, 3-levels of table grouping, and
> returns 5 pages. When I preview the report in VStudio, it returns the 5
> pages and I can navigate the pages real quickly. The problem is, when I run
> it online via the RS front-end and click "Next Page," it takes a good 30
> seconds to load the subsequent page or pages. The query itself runs in about
> 45 seconds, but why is the paging not near instantaneous?
> Thanks,
> j
>
>|||Absolutely.
1. This report is slow. All the other reports paginate just fine, even those
that use the same datasources.
2. It's a production machine.
3. It's not caching a temporary copy, but neither is any of the other
reports. I set the caching (every 10 minutes) and it's 99% faster, but I
still don't understand. The report shouldn't refresh itself on every page,
only every time it is run.
4. Yes. Would this really matter?
Thanks,
j
"Amarnath" <Amarnath@.discussions.microsoft.com> wrote in message
news:DC42BC35-CD2A-42EB-BADA-E7FA77FCCA5F@.microsoft.com...
>I hope you must have asked some questions yourself like
> 1. Is this report is slow or all the reports are slow?
> 2. Is your dev environment and production is different then how fast is
> your
> production machine, is the machine slow (database server)?
> 3. Is Cache enabled/disabled ?
> 4. Are you doing the dev and online chking on the same machine ?
> Probabily you can go to configuration from RS manager screen and check for
> the cache options.
> Amarnath
> "Jordan" wrote:
>> I have a report with a single dataset, 3-levels of table grouping, and
>> returns 5 pages. When I preview the report in VStudio, it returns the 5
>> pages and I can navigate the pages real quickly. The problem is, when I
>> run
>> it online via the RS front-end and click "Next Page," it takes a good 30
>> seconds to load the subsequent page or pages. The query itself runs in
>> about
>> 45 seconds, but why is the paging not near instantaneous?
>> Thanks,
>> j
>>|||Absolutely.
1. This report is slow. All the other reports paginate just fine, even those
that use the same datasources.
2. It's a production machine.
3. It's not caching a temporary copy, but neither is any of the other
reports. I set the caching (every 10 minutes) and it's 99% faster, but I
still don't understand. The report shouldn't refresh itself on every page,
only every time it is run.
4. Yes. Would this really matter?
Thanks,
j