I have two servers running SQL Server 2005 64 bit with all the available
patches, running on Windows 2003 64 bits fully patched.
On both servers I get the same error everytime I use this sequence to export
data:
1) Right click DB and choose Tasks/Export Data
2) I select the same server as the datasource
3) When choosing the destination, the moment I select "Flat File" or
"Microsoft Excel" I get the same error:
===================================
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle. (SQL Server Import and Export Wizard)
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
Program Location:
at System.RuntimeMethodHandle._InvokeConstructor(Obje ct[] args,
SignatureStruct& signature, IntPtr declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(Objec t[] args,
SignatureStruct signature, RuntimeTypeHandle declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(Bi ndingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes)
at
Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSource ComboBox_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChang ed(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Mes sage& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.O nMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.W ndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager. get_Properties()
at
Microsoft.DataTransformationServices.Controls.Flat FileConnectionManagerUtils.GetLocaleID(ConnectionM anager connectionManager)
at
Microsoft.DataTransformationServices.Controls.Flat FileManagerGeneralPage.LoadState(ConnectionManager connManager)
at
Microsoft.DataTransformationServices.Controls.Flat FileManagerGeneralPage.set_ConnectionManager(Conne ctionManager value)
at
Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm ..ctor(DataSourceInfo info,
Boolean bDest, WizardInputs inputs, WizardPage page)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSProper tiesProvider90.get_Properties()
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager. get_Properties()
=================================
So I cannot export data from these servers, I have tried everything and
installed all of the components and started all services to no avail.
I have even asked several Microsoft technicians and nobody seems to have a
clue and it's exactly the same behavior in both servers.
Please Help!
Hello John, I have tried using the management studio and business
intelligence studio on the same server and also using the management studio
from one server (acting as client) to the other server. Every time I get the
same error.
I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
all the tools and services installed and started.
I never had any issues with sql server 2000 and after we spent so much money
to upgrade it's absurd you cannot even export a single excel worksheet from
the database.
"John Bell" wrote:
> Hi Luis
> "Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
> news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
> Have you tried to export data from a workstation?
> Are you running SP2 or higher?
> John
>
>
|||Hi Luis
"Luis Jahn" wrote:
> Hello John, I have tried using the management studio and business
> intelligence studio on the same server and also using the management studio
> from one server (acting as client) to the other server. Every time I get the
> same error.
> I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
> all the tools and services installed and started.
> I never had any issues with sql server 2000 and after we spent so much money
> to upgrade it's absurd you cannot even export a single excel worksheet from
> the database.
>
If you install the client tools on a workstations, can you use SSMS to
export the data when connected to the server? If so they you should be able
to create SSIS packages and import them on the server.
I don't have a 64bit server to connect to check this out, but I would not
expect this to be specific to your system although a similar post was created
at the same time as yours http://tinyurl.com/24w8jh !
John
Showing posts with label patched. Show all posts
Showing posts with label patched. Show all posts
Thursday, March 29, 2012
Cannot Export Data from SQL Server 2005
I have two servers running SQL Server 2005 64 bit with all the available
patches, running on Windows 2003 64 bits fully patched.
On both servers I get the same error everytime I use this sequence to export
data:
1) Right click DB and choose Tasks/Export Data
2) I select the same server as the datasource
3) When choosing the destination, the moment I select "Flat File" or
"Microsoft Excel" I get the same error:
===================================
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle. (SQL Server Import and Export Wizard)
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
Program Location:
at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
SignatureStruct& signature, IntPtr declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
SignatureStruct signature, RuntimeTypeHandle declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttri
butes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes)
at
Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChan
ged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.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)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
at
Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils
.GetLocaleID(ConnectionManager connectionManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.Loa
dState(ConnectionManager connManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set
_ConnectionManager(ConnectionManager value)
at
Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo info
,
Boolean bDest, WizardInputs inputs, WizardPage page)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Propert
ies()
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
=================================
So I cannot export data from these servers, I have tried everything and
installed all of the components and started all services to no avail.
I have even asked several Microsoft technicians and nobody seems to have a
clue and it's exactly the same behavior in both servers.
Please Help!Hi Luis
"Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
>I have two servers running SQL Server 2005 64 bit with all the available
> patches, running on Windows 2003 64 bits fully patched.
> On both servers I get the same error everytime I use this sequence to
> export
> data:
> 1) Right click DB and choose Tasks/Export Data
> 2) I select the same server as the datasource
> 3) When choosing the destination, the moment I select "Flat File" or
> "Microsoft Excel" I get the same error:
> ===================================
> An error occurred which the SQL Server Integration Services Wizard was not
> prepared to handle. (SQL Server Import and Export Wizard)
> ===================================
> Exception has been thrown by the target of an invocation. (mscorlib)
> --
> Program Location:
> at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> SignatureStruct& signature, IntPtr declaringType)
> at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> SignatureStruct signature, RuntimeTypeHandle declaringType)
> at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> Binder
> binder, Object[] args, CultureInfo culture, Object[] activationAtt
ributes)
> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> Binder binder, Object[] args, CultureInfo culture, Object[]
> activationAttributes)
> at
> Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexCh
anged(Object
> sender, EventArgs e)
> at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> at System.Windows.Forms.ComboBox.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)
> ===================================
> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> at
> Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUti
ls.GetLocaleID(ConnectionManager
> connectionManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.L
oadState(ConnectionManager
> connManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.s
et_ConnectionManager(ConnectionManager
> value)
> at
> Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> info,
> Boolean bDest, WizardInputs inputs, WizardPage page)
> ===================================
> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at
> Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Prope
rties()
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> =================================
> So I cannot export data from these servers, I have tried everything and
> installed all of the components and started all services to no avail.
> I have even asked several Microsoft technicians and nobody seems to have a
> clue and it's exactly the same behavior in both servers.
> Please Help!
Have you tried to export data from a workstation?
Are you running SP2 or higher?
John|||Hello John, I have tried using the management studio and business
intelligence studio on the same server and also using the management studio
from one server (acting as client) to the other server. Every time I get the
same error.
I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
all the tools and services installed and started.
I never had any issues with sql server 2000 and after we spent so much money
to upgrade it's absurd you cannot even export a single excel worksheet from
the database.
"John Bell" wrote:
> Hi Luis
> "Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
> news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
> Have you tried to export data from a workstation?
> Are you running SP2 or higher?
> John
>
>|||Hi Luis
"Luis Jahn" wrote:
> Hello John, I have tried using the management studio and business
> intelligence studio on the same server and also using the management studi
o
> from one server (acting as client) to the other server. Every time I get t
he
> same error.
> I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 an
d
> all the tools and services installed and started.
> I never had any issues with sql server 2000 and after we spent so much mon
ey
> to upgrade it's absurd you cannot even export a single excel worksheet fro
m
> the database.
>
If you install the client tools on a workstations, can you use SSMS to
export the data when connected to the server? If so they you should be able
to create SSIS packages and import them on the server.
I don't have a 64bit server to connect to check this out, but I would not
expect this to be specific to your system although a similar post was create
d
at the same time as yours http://tinyurl.com/24w8jh !
John
patches, running on Windows 2003 64 bits fully patched.
On both servers I get the same error everytime I use this sequence to export
data:
1) Right click DB and choose Tasks/Export Data
2) I select the same server as the datasource
3) When choosing the destination, the moment I select "Flat File" or
"Microsoft Excel" I get the same error:
===================================
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle. (SQL Server Import and Export Wizard)
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
Program Location:
at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
SignatureStruct& signature, IntPtr declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
SignatureStruct signature, RuntimeTypeHandle declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttri
butes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes)
at
Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChan
ged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.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)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
at
Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils
.GetLocaleID(ConnectionManager connectionManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.Loa
dState(ConnectionManager connManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set
_ConnectionManager(ConnectionManager value)
at
Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo info
,
Boolean bDest, WizardInputs inputs, WizardPage page)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
Program Location:
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Propert
ies()
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
=================================
So I cannot export data from these servers, I have tried everything and
installed all of the components and started all services to no avail.
I have even asked several Microsoft technicians and nobody seems to have a
clue and it's exactly the same behavior in both servers.
Please Help!Hi Luis
"Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
>I have two servers running SQL Server 2005 64 bit with all the available
> patches, running on Windows 2003 64 bits fully patched.
> On both servers I get the same error everytime I use this sequence to
> export
> data:
> 1) Right click DB and choose Tasks/Export Data
> 2) I select the same server as the datasource
> 3) When choosing the destination, the moment I select "Flat File" or
> "Microsoft Excel" I get the same error:
> ===================================
> An error occurred which the SQL Server Integration Services Wizard was not
> prepared to handle. (SQL Server Import and Export Wizard)
> ===================================
> Exception has been thrown by the target of an invocation. (mscorlib)
> --
> Program Location:
> at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> SignatureStruct& signature, IntPtr declaringType)
> at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> SignatureStruct signature, RuntimeTypeHandle declaringType)
> at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> Binder
> binder, Object[] args, CultureInfo culture, Object[] activationAtt
ributes)
> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> Binder binder, Object[] args, CultureInfo culture, Object[]
> activationAttributes)
> at
> Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexCh
anged(Object
> sender, EventArgs e)
> at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> at System.Windows.Forms.ComboBox.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)
> ===================================
> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> at
> Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUti
ls.GetLocaleID(ConnectionManager
> connectionManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.L
oadState(ConnectionManager
> connManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.s
et_ConnectionManager(ConnectionManager
> value)
> at
> Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> info,
> Boolean bDest, WizardInputs inputs, WizardPage page)
> ===================================
> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at
> Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Prope
rties()
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> =================================
> So I cannot export data from these servers, I have tried everything and
> installed all of the components and started all services to no avail.
> I have even asked several Microsoft technicians and nobody seems to have a
> clue and it's exactly the same behavior in both servers.
> Please Help!
Have you tried to export data from a workstation?
Are you running SP2 or higher?
John|||Hello John, I have tried using the management studio and business
intelligence studio on the same server and also using the management studio
from one server (acting as client) to the other server. Every time I get the
same error.
I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
all the tools and services installed and started.
I never had any issues with sql server 2000 and after we spent so much money
to upgrade it's absurd you cannot even export a single excel worksheet from
the database.
"John Bell" wrote:
> Hi Luis
> "Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
> news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
> Have you tried to export data from a workstation?
> Are you running SP2 or higher?
> John
>
>|||Hi Luis
"Luis Jahn" wrote:
> Hello John, I have tried using the management studio and business
> intelligence studio on the same server and also using the management studi
o
> from one server (acting as client) to the other server. Every time I get t
he
> same error.
> I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 an
d
> all the tools and services installed and started.
> I never had any issues with sql server 2000 and after we spent so much mon
ey
> to upgrade it's absurd you cannot even export a single excel worksheet fro
m
> the database.
>
If you install the client tools on a workstations, can you use SSMS to
export the data when connected to the server? If so they you should be able
to create SSIS packages and import them on the server.
I don't have a 64bit server to connect to check this out, but I would not
expect this to be specific to your system although a similar post was create
d
at the same time as yours http://tinyurl.com/24w8jh !
John
Cannot Export Data from SQL Server 2005
I have two servers running SQL Server 2005 64 bit with all the available
patches, running on Windows 2003 64 bits fully patched.
On both servers I get the same error everytime I use this sequence to export
data:
1) Right click DB and choose Tasks/Export Data
2) I select the same server as the datasource
3) When choosing the destination, the moment I select "Flat File" or
"Microsoft Excel" I get the same error:
===================================
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle. (SQL Server Import and Export Wizard)
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
--
Program Location:
at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
SignatureStruct& signature, IntPtr declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
SignatureStruct signature, RuntimeTypeHandle declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes)
at
Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.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)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
at
Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager connectionManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager connManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager value)
at
Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo info,
Boolean bDest, WizardInputs inputs, WizardPage page)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
--
Program Location:
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
=================================
So I cannot export data from these servers, I have tried everything and
installed all of the components and started all services to no avail.
I have even asked several Microsoft technicians and nobody seems to have a
clue and it's exactly the same behavior in both servers.
Please Help!Hi Luis
"Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
>I have two servers running SQL Server 2005 64 bit with all the available
> patches, running on Windows 2003 64 bits fully patched.
> On both servers I get the same error everytime I use this sequence to
> export
> data:
> 1) Right click DB and choose Tasks/Export Data
> 2) I select the same server as the datasource
> 3) When choosing the destination, the moment I select "Flat File" or
> "Microsoft Excel" I get the same error:
> ===================================> An error occurred which the SQL Server Integration Services Wizard was not
> prepared to handle. (SQL Server Import and Export Wizard)
> ===================================> Exception has been thrown by the target of an invocation. (mscorlib)
> --
> Program Location:
> at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> SignatureStruct& signature, IntPtr declaringType)
> at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> SignatureStruct signature, RuntimeTypeHandle declaringType)
> at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> Binder
> binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> Binder binder, Object[] args, CultureInfo culture, Object[]
> activationAttributes)
> at
> Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object
> sender, EventArgs e)
> at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> at System.Windows.Forms.ComboBox.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)
> ===================================> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> at
> Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager
> connectionManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager
> connManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager
> value)
> at
> Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> info,
> Boolean bDest, WizardInputs inputs, WizardPage page)
> ===================================> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at
> Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> =================================> So I cannot export data from these servers, I have tried everything and
> installed all of the components and started all services to no avail.
> I have even asked several Microsoft technicians and nobody seems to have a
> clue and it's exactly the same behavior in both servers.
> Please Help!
Have you tried to export data from a workstation?
Are you running SP2 or higher?
John|||Hello John, I have tried using the management studio and business
intelligence studio on the same server and also using the management studio
from one server (acting as client) to the other server. Every time I get the
same error.
I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
all the tools and services installed and started.
I never had any issues with sql server 2000 and after we spent so much money
to upgrade it's absurd you cannot even export a single excel worksheet from
the database.
"John Bell" wrote:
> Hi Luis
> "Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
> news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
> >I have two servers running SQL Server 2005 64 bit with all the available
> > patches, running on Windows 2003 64 bits fully patched.
> >
> > On both servers I get the same error everytime I use this sequence to
> > export
> > data:
> > 1) Right click DB and choose Tasks/Export Data
> > 2) I select the same server as the datasource
> > 3) When choosing the destination, the moment I select "Flat File" or
> > "Microsoft Excel" I get the same error:
> >
> > ===================================> >
> > An error occurred which the SQL Server Integration Services Wizard was not
> > prepared to handle. (SQL Server Import and Export Wizard)
> >
> > ===================================> >
> > Exception has been thrown by the target of an invocation. (mscorlib)
> >
> > --
> > Program Location:
> >
> > at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> > SignatureStruct& signature, IntPtr declaringType)
> > at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> > SignatureStruct signature, RuntimeTypeHandle declaringType)
> > at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> > invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> > at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> > Binder
> > binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
> > at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> > Binder binder, Object[] args, CultureInfo culture, Object[]
> > activationAttributes)
> > at
> > Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object
> > sender, EventArgs e)
> > at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> > at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> > at System.Windows.Forms.ComboBox.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)
> >
> > ===================================> >
> > Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> >
> > --
> > Program Location:
> >
> > at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager
> > connectionManager)
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager
> > connManager)
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager
> > value)
> > at
> > Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> > info,
> > Boolean bDest, WizardInputs inputs, WizardPage page)
> >
> > ===================================> >
> > Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> >
> > --
> > Program Location:
> > at
> > Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
> > at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> > =================================> >
> > So I cannot export data from these servers, I have tried everything and
> > installed all of the components and started all services to no avail.
> >
> > I have even asked several Microsoft technicians and nobody seems to have a
> > clue and it's exactly the same behavior in both servers.
> >
> > Please Help!
> Have you tried to export data from a workstation?
> Are you running SP2 or higher?
> John
>
>|||Hi Luis
"Luis Jahn" wrote:
> Hello John, I have tried using the management studio and business
> intelligence studio on the same server and also using the management studio
> from one server (acting as client) to the other server. Every time I get the
> same error.
> I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
> all the tools and services installed and started.
> I never had any issues with sql server 2000 and after we spent so much money
> to upgrade it's absurd you cannot even export a single excel worksheet from
> the database.
>
If you install the client tools on a workstations, can you use SSMS to
export the data when connected to the server? If so they you should be able
to create SSIS packages and import them on the server.
I don't have a 64bit server to connect to check this out, but I would not
expect this to be specific to your system although a similar post was created
at the same time as yours http://tinyurl.com/24w8jh !
John
patches, running on Windows 2003 64 bits fully patched.
On both servers I get the same error everytime I use this sequence to export
data:
1) Right click DB and choose Tasks/Export Data
2) I select the same server as the datasource
3) When choosing the destination, the moment I select "Flat File" or
"Microsoft Excel" I get the same error:
===================================
An error occurred which the SQL Server Integration Services Wizard was not
prepared to handle. (SQL Server Import and Export Wizard)
===================================
Exception has been thrown by the target of an invocation. (mscorlib)
--
Program Location:
at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
SignatureStruct& signature, IntPtr declaringType)
at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
SignatureStruct signature, RuntimeTypeHandle declaringType)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder
binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
Binder binder, Object[] args, CultureInfo culture, Object[]
activationAttributes)
at
Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.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)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
--
Program Location:
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
at
Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager connectionManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager connManager)
at
Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager value)
at
Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo info,
Boolean bDest, WizardInputs inputs, WizardPage page)
===================================
Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
--
Program Location:
at
Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
=================================
So I cannot export data from these servers, I have tried everything and
installed all of the components and started all services to no avail.
I have even asked several Microsoft technicians and nobody seems to have a
clue and it's exactly the same behavior in both servers.
Please Help!Hi Luis
"Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
>I have two servers running SQL Server 2005 64 bit with all the available
> patches, running on Windows 2003 64 bits fully patched.
> On both servers I get the same error everytime I use this sequence to
> export
> data:
> 1) Right click DB and choose Tasks/Export Data
> 2) I select the same server as the datasource
> 3) When choosing the destination, the moment I select "Flat File" or
> "Microsoft Excel" I get the same error:
> ===================================> An error occurred which the SQL Server Integration Services Wizard was not
> prepared to handle. (SQL Server Import and Export Wizard)
> ===================================> Exception has been thrown by the target of an invocation. (mscorlib)
> --
> Program Location:
> at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> SignatureStruct& signature, IntPtr declaringType)
> at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> SignatureStruct signature, RuntimeTypeHandle declaringType)
> at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> Binder
> binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> Binder binder, Object[] args, CultureInfo culture, Object[]
> activationAttributes)
> at
> Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object
> sender, EventArgs e)
> at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> at System.Windows.Forms.ComboBox.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)
> ===================================> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> at
> Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager
> connectionManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager
> connManager)
> at
> Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager
> value)
> at
> Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> info,
> Boolean bDest, WizardInputs inputs, WizardPage page)
> ===================================> Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> --
> Program Location:
> at
> Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
> at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> =================================> So I cannot export data from these servers, I have tried everything and
> installed all of the components and started all services to no avail.
> I have even asked several Microsoft technicians and nobody seems to have a
> clue and it's exactly the same behavior in both servers.
> Please Help!
Have you tried to export data from a workstation?
Are you running SP2 or higher?
John|||Hello John, I have tried using the management studio and business
intelligence studio on the same server and also using the management studio
from one server (acting as client) to the other server. Every time I get the
same error.
I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
all the tools and services installed and started.
I never had any issues with sql server 2000 and after we spent so much money
to upgrade it's absurd you cannot even export a single excel worksheet from
the database.
"John Bell" wrote:
> Hi Luis
> "Luis Jahn" <Luis Jahn@.discussions.microsoft.com> wrote in message
> news:41A2A90F-2C98-4FAE-A1C0-DB432AD7D38C@.microsoft.com...
> >I have two servers running SQL Server 2005 64 bit with all the available
> > patches, running on Windows 2003 64 bits fully patched.
> >
> > On both servers I get the same error everytime I use this sequence to
> > export
> > data:
> > 1) Right click DB and choose Tasks/Export Data
> > 2) I select the same server as the datasource
> > 3) When choosing the destination, the moment I select "Flat File" or
> > "Microsoft Excel" I get the same error:
> >
> > ===================================> >
> > An error occurred which the SQL Server Integration Services Wizard was not
> > prepared to handle. (SQL Server Import and Export Wizard)
> >
> > ===================================> >
> > Exception has been thrown by the target of an invocation. (mscorlib)
> >
> > --
> > Program Location:
> >
> > at System.RuntimeMethodHandle._InvokeConstructor(Object[] args,
> > SignatureStruct& signature, IntPtr declaringType)
> > at System.RuntimeMethodHandle.InvokeConstructor(Object[] args,
> > SignatureStruct signature, RuntimeTypeHandle declaringType)
> > at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
> > invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
> > at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr,
> > Binder
> > binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
> > at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr,
> > Binder binder, Object[] args, CultureInfo culture, Object[]
> > activationAttributes)
> > at
> > Microsoft.SqlServer.Dts.DtsWizard.Step2.DataSourceComboBox_SelectedIndexChanged(Object
> > sender, EventArgs e)
> > at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
> > at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
> > at System.Windows.Forms.ComboBox.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)
> >
> > ===================================> >
> > Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> >
> > --
> > Program Location:
> >
> > at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileConnectionManagerUtils.GetLocaleID(ConnectionManager
> > connectionManager)
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.LoadState(ConnectionManager
> > connManager)
> > at
> > Microsoft.DataTransformationServices.Controls.FlatFileManagerGeneralPage.set_ConnectionManager(ConnectionManager
> > value)
> > at
> > Microsoft.SqlServer.Dts.DtsWizard.FlatFileDestForm..ctor(DataSourceInfo
> > info,
> > Boolean bDest, WizardInputs inputs, WizardPage page)
> >
> > ===================================> >
> > Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap)
> >
> > --
> > Program Location:
> > at
> > Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSPropertiesProvider90.get_Properties()
> > at Microsoft.SqlServer.Dts.Runtime.ConnectionManager.get_Properties()
> > =================================> >
> > So I cannot export data from these servers, I have tried everything and
> > installed all of the components and started all services to no avail.
> >
> > I have even asked several Microsoft technicians and nobody seems to have a
> > clue and it's exactly the same behavior in both servers.
> >
> > Please Help!
> Have you tried to export data from a workstation?
> Are you running SP2 or higher?
> John
>
>|||Hi Luis
"Luis Jahn" wrote:
> Hello John, I have tried using the management studio and business
> intelligence studio on the same server and also using the management studio
> from one server (acting as client) to the other server. Every time I get the
> same error.
> I'm running Windows 2003 64 bit with SP2 and SQL Server 64 bit with SP2 and
> all the tools and services installed and started.
> I never had any issues with sql server 2000 and after we spent so much money
> to upgrade it's absurd you cannot even export a single excel worksheet from
> the database.
>
If you install the client tools on a workstations, can you use SSMS to
export the data when connected to the server? If so they you should be able
to create SSIS packages and import them on the server.
I don't have a 64bit server to connect to check this out, but I would not
expect this to be specific to your system although a similar post was created
at the same time as yours http://tinyurl.com/24w8jh !
John
Thursday, March 22, 2012
Cannot delete maintenance plan.
Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
means I was dumb enough to apply service pack 2 immediately and then
microsoft release a patch a couple days later because spk2 was broken)
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column...
--Apparently the job you try to delete has one or more subplans that (for some
reason) should be deleted apart.
Try deleting the single subplans before deleting the Maintenance Plan itself.
Each Subplan has foreign keys referencing the sysjobs table, containing the
definition of the Plan.
I cannot define the exact cause of your issue because i don't know the
complete history of the plan, his subplans, the schedules etc.
Look in msdb at the system tables to undertand the relationships between the
various table but DON'T TRY to operate updates directly over them!
Gilberto Zampatti
"SQLdba" wrote:
> Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
> means I was dumb enough to apply service pack 2 immediately and then
> microsoft release a patch a couple days later because spk2 was broken)
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column...
>
> --
>
means I was dumb enough to apply service pack 2 immediately and then
microsoft release a patch a couple days later because spk2 was broken)
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column...
--Apparently the job you try to delete has one or more subplans that (for some
reason) should be deleted apart.
Try deleting the single subplans before deleting the Maintenance Plan itself.
Each Subplan has foreign keys referencing the sysjobs table, containing the
definition of the Plan.
I cannot define the exact cause of your issue because i don't know the
complete history of the plan, his subplans, the schedules etc.
Look in msdb at the system tables to undertand the relationships between the
various table but DON'T TRY to operate updates directly over them!
Gilberto Zampatti
"SQLdba" wrote:
> Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
> means I was dumb enough to apply service pack 2 immediately and then
> microsoft release a patch a couple days later because spk2 was broken)
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column...
>
> --
>
Tuesday, March 20, 2012
Cannot delete maintenance plan.
Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
means I was dumb enough to apply service pack 2 immediately and then
microsoft release a patch a couple days later because spk2 was broken)
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column...
Apparently the job you try to delete has one or more subplans that (for some
reason) should be deleted apart.
Try deleting the single subplans before deleting the Maintenance Plan itself.
Each Subplan has foreign keys referencing the sysjobs table, containing the
definition of the Plan.
I cannot define the exact cause of your issue because i don't know the
complete history of the plan, his subplans, the schedules etc.
Look in msdb at the system tables to undertand the relationships between the
various table but DON'T TRY to operate updates directly over them!
Gilberto Zampatti
"SQLdba" wrote:
> Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
> means I was dumb enough to apply service pack 2 immediately and then
> microsoft release a patch a couple days later because spk2 was broken)
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column...
>
> --
>
means I was dumb enough to apply service pack 2 immediately and then
microsoft release a patch a couple days later because spk2 was broken)
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column...
Apparently the job you try to delete has one or more subplans that (for some
reason) should be deleted apart.
Try deleting the single subplans before deleting the Maintenance Plan itself.
Each Subplan has foreign keys referencing the sysjobs table, containing the
definition of the Plan.
I cannot define the exact cause of your issue because i don't know the
complete history of the plan, his subplans, the schedules etc.
Look in msdb at the system tables to undertand the relationships between the
various table but DON'T TRY to operate updates directly over them!
Gilberto Zampatti
"SQLdba" wrote:
> Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
> means I was dumb enough to apply service pack 2 immediately and then
> microsoft release a patch a couple days later because spk2 was broken)
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column...
>
> --
>
Cannot delete maintenance plan.
Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
means I was dumb enough to apply service pack 2 immediately and then
microsoft release a patch a couple days later because spk2 was broken)
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column...Apparently the job you try to delete has one or more subplans that (for some
reason) should be deleted apart.
Try deleting the single subplans before deleting the Maintenance Plan itself
.
Each Subplan has foreign keys referencing the sysjobs table, containing the
definition of the Plan.
I cannot define the exact cause of your issue because i don't know the
complete history of the plan, his subplans, the schedules etc.
Look in msdb at the system tables to undertand the relationships between the
various table but DON'T TRY to operate updates directly over them!
Gilberto Zampatti
"SQLdba" wrote:
> Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
> means I was dumb enough to apply service pack 2 immediately and then
> microsoft release a patch a couple days later because spk2 was broken)
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column...
>
> --
>
means I was dumb enough to apply service pack 2 immediately and then
microsoft release a patch a couple days later because spk2 was broken)
The DELETE statement conflicted with the REFERENCE constraint
"FK_subplan_job_id". The conflict occurred in database "msdb", table
"dbo.sysmaintplan_subplans", column...Apparently the job you try to delete has one or more subplans that (for some
reason) should be deleted apart.
Try deleting the single subplans before deleting the Maintenance Plan itself
.
Each Subplan has foreign keys referencing the sysjobs table, containing the
definition of the Plan.
I cannot define the exact cause of your issue because i don't know the
complete history of the plan, his subplans, the schedules etc.
Look in msdb at the system tables to undertand the relationships between the
various table but DON'T TRY to operate updates directly over them!
Gilberto Zampatti
"SQLdba" wrote:
> Cannot delete a maintenance plan. SQL 2005 patched service pack 2. (That
> means I was dumb enough to apply service pack 2 immediately and then
> microsoft release a patch a couple days later because spk2 was broken)
> The DELETE statement conflicted with the REFERENCE constraint
> "FK_subplan_job_id". The conflict occurred in database "msdb", table
> "dbo.sysmaintplan_subplans", column...
>
> --
>
Wednesday, March 7, 2012
Cannot copy : Insufficient system resources
Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both fully
patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2 2GB
Fiber NICS teamed
Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
Raid 5 SCSI controller, 4 100 mb NICS teamed
Both servers have lots of room on the partition.
We've been refreshing the development server with fresh production data
every three months. My method for doing this has been to do a local backup of
the production server, then copy the bak file to the development server. This
has been working for several years. The bak file is now 70 GB. The last time
it worked the bak file was around 65 GB. Last night the copy of the bak file
over the network failed about halfway through with a popup:
"Cannot copy prd. bak : Insufficient system resources exist to complete the
requested service" There are no entries in either server's application or
system event logs. I've read the MSFT KB Article 259837 but that doesn't seem
to apply because (a) the failure occured about one hour into the copy process
and (b) both servers are fully patched.
Developers are beating on me to get this done tonight. I suspect in the long
run, I will have to get something like SQL lite speed. But I would like a
quick fix for tonight. I would prefer not to shut down the production db and
copy the individual files.
Here are my thoughts:
1. Would I have better luck if I backed up with a UNC path to the
development server?
2. Can I compress the bak file with something?
Any suggestions?Personally, I prefer working with UNC paths for backups.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MangroveGeek" <carl@.tenthousandislands.net(DoNotSpam)> wrote in message
news:130BD949-316B-44F2-9117-B30B9477D24C@.microsoft.com...
> Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both
> fully
> patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2
> 2GB
> Fiber NICS teamed
> Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
> Raid 5 SCSI controller, 4 100 mb NICS teamed
> Both servers have lots of room on the partition.
> We've been refreshing the development server with fresh production data
> every three months. My method for doing this has been to do a local backup
> of
> the production server, then copy the bak file to the development server.
> This
> has been working for several years. The bak file is now 70 GB. The last
> time
> it worked the bak file was around 65 GB. Last night the copy of the bak
> file
> over the network failed about halfway through with a popup:
> "Cannot copy prd. bak : Insufficient system resources exist to complete
> the
> requested service" There are no entries in either server's application or
> system event logs. I've read the MSFT KB Article 259837 but that doesn't
> seem
> to apply because (a) the failure occured about one hour into the copy
> process
> and (b) both servers are fully patched.
> Developers are beating on me to get this done tonight. I suspect in the
> long
> run, I will have to get something like SQL lite speed. But I would like a
> quick fix for tonight. I would prefer not to shut down the production db
> and
> copy the individual files.
> Here are my thoughts:
> 1. Would I have better luck if I backed up with a UNC path to the
> development server?
> 2. Can I compress the bak file with something?
> Any suggestions?
patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2 2GB
Fiber NICS teamed
Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
Raid 5 SCSI controller, 4 100 mb NICS teamed
Both servers have lots of room on the partition.
We've been refreshing the development server with fresh production data
every three months. My method for doing this has been to do a local backup of
the production server, then copy the bak file to the development server. This
has been working for several years. The bak file is now 70 GB. The last time
it worked the bak file was around 65 GB. Last night the copy of the bak file
over the network failed about halfway through with a popup:
"Cannot copy prd. bak : Insufficient system resources exist to complete the
requested service" There are no entries in either server's application or
system event logs. I've read the MSFT KB Article 259837 but that doesn't seem
to apply because (a) the failure occured about one hour into the copy process
and (b) both servers are fully patched.
Developers are beating on me to get this done tonight. I suspect in the long
run, I will have to get something like SQL lite speed. But I would like a
quick fix for tonight. I would prefer not to shut down the production db and
copy the individual files.
Here are my thoughts:
1. Would I have better luck if I backed up with a UNC path to the
development server?
2. Can I compress the bak file with something?
Any suggestions?Personally, I prefer working with UNC paths for backups.
HowTo: Backup to UNC name using Database Maintenance Wizard
http://support.microsoft.com/default.aspx?scid=kb;en-us;555128
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"MangroveGeek" <carl@.tenthousandislands.net(DoNotSpam)> wrote in message
news:130BD949-316B-44F2-9117-B30B9477D24C@.microsoft.com...
> Production Server: Win2k Advanced Server, SQL 2k Advanced Server, Both
> fully
> patched, 4 processors, 5 GB RAM, 320 GB partition, 68 GB DataBase, SAN, 2
> 2GB
> Fiber NICS teamed
> Development Server: Win2k Server, SQL 2k Server, two processors, 2 GB RAM,
> Raid 5 SCSI controller, 4 100 mb NICS teamed
> Both servers have lots of room on the partition.
> We've been refreshing the development server with fresh production data
> every three months. My method for doing this has been to do a local backup
> of
> the production server, then copy the bak file to the development server.
> This
> has been working for several years. The bak file is now 70 GB. The last
> time
> it worked the bak file was around 65 GB. Last night the copy of the bak
> file
> over the network failed about halfway through with a popup:
> "Cannot copy prd. bak : Insufficient system resources exist to complete
> the
> requested service" There are no entries in either server's application or
> system event logs. I've read the MSFT KB Article 259837 but that doesn't
> seem
> to apply because (a) the failure occured about one hour into the copy
> process
> and (b) both servers are fully patched.
> Developers are beating on me to get this done tonight. I suspect in the
> long
> run, I will have to get something like SQL lite speed. But I would like a
> quick fix for tonight. I would prefer not to shut down the production db
> and
> copy the individual files.
> Here are my thoughts:
> 1. Would I have better luck if I backed up with a UNC path to the
> development server?
> 2. Can I compress the bak file with something?
> Any suggestions?
Subscribe to:
Posts (Atom)