"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)
>

"The connection could not be made to the report server......"

My test system is fine (windows 2003, VS.NET, RS). I could suffer the page
https://myserver/reports by using a browser. However, when creating a report
project, I couldn't deploy and got the error message : "The connection could
not be made to the report server https://myserver/reportserver".
Please help me.I am also having similar problems -- I tried reseting the proxy settings in
IE but not helping
"Vu Dawson" wrote:
> My test system is fine (windows 2003, VS.NET, RS). I could suffer the page
> https://myserver/reports by using a browser. However, when creating a report
> project, I couldn't deploy and got the error message : "The connection could
> not be made to the report server https://myserver/reportserver".
> Please help me.|||I was researching this error msg. I don't know if this applies to you.
When you open the browser and navigate to https://myserver/reportserver do
you get a https certificate prompt (yes/no/install cert?). This was the issue
for me... click on Install Certficate and try deploying again.
Good luck!
"Peter" wrote:
> I am also having similar problems -- I tried reseting the proxy settings in
> IE but not helping
> "Vu Dawson" wrote:
> > My test system is fine (windows 2003, VS.NET, RS). I could suffer the page
> > https://myserver/reports by using a browser. However, when creating a report
> > project, I couldn't deploy and got the error message : "The connection could
> > not be made to the report server https://myserver/reportserver".
> > Please help me.

"SQL Native Client" / "SQL Server" drivers

When creating a system DSN via the ODBC Admistrator dialog...
What is the differecne between "SQL Native Client" and "SQL Server" drivers
listed in the "Create New Data Source" drivers list?
How do they differ?
"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> When creating a system DSN via the ODBC Admistrator dialog...
> What is the differecne between "SQL Native Client" and "SQL
> Server" drivers
> listed in the "Create New Data Source" drivers list?
> How do they differ?
From MSDN:
"SQL Native Client is a data access technology that is new to
Microsoft SQL Server 2005, and it is a stand-alone data access
application programming interface (API) that is used for both OLE
DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
driver into one native dynamic-link library (DLL) while also
providing new functionality above and beyond that supplied by the
Microsoft Data Access Components (MDAC). SQL Native Client can be
used to create new applications or enhance existing applications
that need to take advantage of new SQL Server 2005 features such
as multiple active result sets (MARS), user-defined data types
(UDT), query notifications, snapshot isolation, and XML data type
support."
- Arnie
|||Thanks, that helps... but what about the other one listed? ("SQL Server"
driver)
Which is the appropriate one to use in an IIS/Website scenario in terms of
data access?
"Arnie" wrote:

> "Coder23" <Coder23@.discussions.microsoft.com> wrote in message
> news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> From MSDN:
> "SQL Native Client is a data access technology that is new to
> Microsoft SQL Server 2005, and it is a stand-alone data access
> application programming interface (API) that is used for both OLE
> DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
> driver into one native dynamic-link library (DLL) while also
> providing new functionality above and beyond that supplied by the
> Microsoft Data Access Components (MDAC). SQL Native Client can be
> used to create new applications or enhance existing applications
> that need to take advantage of new SQL Server 2005 features such
> as multiple active result sets (MARS), user-defined data types
> (UDT), query notifications, snapshot isolation, and XML data type
> support."
> - Arnie
>
>
|||"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:A3AAA0F0-1898-4453-8D19-9613BA7FAA08@.microsoft.com...
> Thanks, that helps... but what about the other one listed?
> ("SQL Server"
> driver)
> Which is the appropriate one to use in an IIS/Website scenario
> in terms of
> data access?
>
The 'normal' SQL Server Driver should be fine unless you plan to
use some of the new features that were mentioned for SQL Server
2005. We use SQL Server 2000. I haven't tried to run the new
driver against it yet.
- Arnie

"SQL Native Client" / "SQL Server" drivers

When creating a system DSN via the ODBC Admistrator dialog...
What is the differecne between "SQL Native Client" and "SQL Server" drivers
listed in the "Create New Data Source" drivers list?
How do they differ?"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> When creating a system DSN via the ODBC Admistrator dialog...
> What is the differecne between "SQL Native Client" and "SQL
> Server" drivers
> listed in the "Create New Data Source" drivers list?
> How do they differ?
From MSDN:
"SQL Native Client is a data access technology that is new to
Microsoft SQL Server 2005, and it is a stand-alone data access
application programming interface (API) that is used for both OLE
DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
driver into one native dynamic-link library (DLL) while also
providing new functionality above and beyond that supplied by the
Microsoft Data Access Components (MDAC). SQL Native Client can be
used to create new applications or enhance existing applications
that need to take advantage of new SQL Server 2005 features such
as multiple active result sets (MARS), user-defined data types
(UDT), query notifications, snapshot isolation, and XML data type
support."
- Arnie|||Thanks, that helps... but what about the other one listed? ("SQL Server"
driver)
Which is the appropriate one to use in an IIS/Website scenario in terms of
data access?
"Arnie" wrote:

> "Coder23" <Coder23@.discussions.microsoft.com> wrote in message
> news:B50C82B2-70C8-4F28-89CA-248F039A048E@.microsoft.com...
> From MSDN:
> "SQL Native Client is a data access technology that is new to
> Microsoft SQL Server 2005, and it is a stand-alone data access
> application programming interface (API) that is used for both OLE
> DB and ODBC. It combines the SQL OLE DB provider and the SQL ODBC
> driver into one native dynamic-link library (DLL) while also
> providing new functionality above and beyond that supplied by the
> Microsoft Data Access Components (MDAC). SQL Native Client can be
> used to create new applications or enhance existing applications
> that need to take advantage of new SQL Server 2005 features such
> as multiple active result sets (MARS), user-defined data types
> (UDT), query notifications, snapshot isolation, and XML data type
> support."
> - Arnie
>
>|||"Coder23" <Coder23@.discussions.microsoft.com> wrote in message
news:A3AAA0F0-1898-4453-8D19-9613BA7FAA08@.microsoft.com...
> Thanks, that helps... but what about the other one listed?
> ("SQL Server"
> driver)
> Which is the appropriate one to use in an IIS/Website scenario
> in terms of
> data access?
>
The 'normal' SQL Server Driver should be fine unless you plan to
use some of the new features that were mentioned for SQL Server
2005. We use SQL Server 2000. I haven't tried to run the new
driver against it yet.
- Arnie

"Error creating MDAC instance" performing Bulk Insert

I get this error when trying to perform a bulk insert. This started
happening after the latest security fixes were loaded on the server.
Anyone know what this error means?
I was able to correct this by installing the latest sp of MDAC and SP3 of
SQLXML.
"DavidSp8" wrote:

> I get this error when trying to perform a bulk insert. This started
> happening after the latest security fixes were loaded on the server.
> Anyone know what this error means?

"Error creating MDAC instance" performing Bulk Insert

I get this error when trying to perform a bulk insert. This started
happening after the latest security fixes were loaded on the server.
Anyone know what this error means?I was able to correct this by installing the latest sp of MDAC and SP3 of
SQLXML.
"DavidSp8" wrote:

> I get this error when trying to perform a bulk insert. This started
> happening after the latest security fixes were loaded on the server.
> Anyone know what this error means?

error creating maintenance plan

Hello,
I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
includes rebuild indexes, check integrity, update statistics, etc.
I'm using the wizard to create to plan, but at the when I press the finish
button at the end of the wizard there is an error message and I'm unable to
create the plan.
The error message is include at the end of this email.
Does anybody know what could be causing the error?
In advance I appreciate your help and comments.
Edmundo J. Davila
ERROR
TITLE: Maintenance Plan Wizard Progress
Create maintenance plan failed.
ADDITIONAL INFORMATION:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Create+JobStep&LinkId=20476[/url]
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476[ /url]
BUTTONS:
OK
This question has already been answered.
Ekrem nsoy
"Edmundo J. Davila" <edavila@.monisa.com> wrote in message
news:4F578C0F-8F8A-4371-88B1-C6FDA8C0D4AD@.microsoft.com...
> Hello,
> I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
> includes rebuild indexes, check integrity, update statistics, etc.
> I'm using the wizard to create to plan, but at the when I press the finish
> button at the end of the wizard there is an error message and I'm unable
> to create the plan.
> The error message is include at the end of this email.
> Does anybody know what could be causing the error?
> In advance I appreciate your help and comments.
> Edmundo J. Davila
> ERROR
>
> TITLE: Maintenance Plan Wizard Progress
> --
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00. 1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo. ExceptionTemplates.FailedOperationExceptionText&Ev tID=Create+JobStep&LinkId=20476[/url]
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00 .1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476[ /url]
> --
> BUTTONS:
> OK
> --
>

error creating maintenance plan

Hello,
I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
includes rebuild indexes, check integrity, update statistics, etc.
I'm using the wizard to create to plan, but at the when I press the finish
button at the end of the wizard there is an error message and I'm unable to
create the plan.
The error message is include at the end of this email.
Does anybody know what could be causing the error?
In advance I appreciate your help and comments.
Edmundo J. Davila
ERROR
---
TITLE: Maintenance Plan Wizard Progress
--
Create maintenance plan failed.
--
ADDITIONAL INFORMATION:
Create failed for JobStep 'Subplan'.
(Microsoft.SqlServer.MaintenancePlanTasks)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
--
An exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.SqlServer.ConnectionInfo)
--
The specified '@.subsystem' is invalid (valid values are returned by
sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
--
BUTTONS:
OK
--This question has already been answered.
--
Ekrem Önsoy
"Edmundo J. Davila" <edavila@.monisa.com> wrote in message
news:4F578C0F-8F8A-4371-88B1-C6FDA8C0D4AD@.microsoft.com...
> Hello,
> I'm creating a maintenance plan for a SQL SERVER DB in 64 bits. The plan
> includes rebuild indexes, check integrity, update statistics, etc.
> I'm using the wizard to create to plan, but at the when I press the finish
> button at the end of the wizard there is an error message and I'm unable
> to create the plan.
> The error message is include at the end of this email.
> Does anybody know what could be causing the error?
> In advance I appreciate your help and comments.
> Edmundo J. Davila
> ERROR
> ---
>
> TITLE: Maintenance Plan Wizard Progress
> --
> Create maintenance plan failed.
> --
> ADDITIONAL INFORMATION:
> Create failed for JobStep 'Subplan'.
> (Microsoft.SqlServer.MaintenancePlanTasks)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+JobStep&LinkId=20476
> --
> An exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.SqlServer.ConnectionInfo)
> --
> The specified '@.subsystem' is invalid (valid values are returned by
> sp_enum_sqlagent_subsystems). (Microsoft SQL Server, Error: 14234)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=14234&LinkId=20476
> --
> BUTTONS:
> OK
> --
>