Quantcast
Channel: SQL Server Integration Services forum
Viewing all articles
Browse latest Browse all 24688

Error generated by Import Wizard when switching file type to Flat File

$
0
0

I've got a 64-bit SQL server running several DB instances. For one instance I tried to do an import from a flat file. When I switched the type of file to Flat File (which should bring up a series of options for the file in question) it gives the following 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.Step1.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.DataTransformationServices.Controls.FlatFileConnectionManagerControl.set_ConnectionManager(ConnectionManager value)

  at Microsoft.SqlServer.Dts.DtsWizard.FlatFileSourceForm..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()

 

--------------------------------------------------------------------------------------------------------------------------------------

After seeing this error I decided to use our old 32-bit server to see if the wizard could be run for this particular import on the instance. It worked. I then opened the 64-bit server's Integration Services to grab the code because I need to run this import process each night. When I tried to connect via the server management studio it generated the following error:

--------------------------------------------------------------------------------------------------------------------------------------

===================================

 

Cannot connect to SQL64.

 

===================================

 

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

 

------------------------------

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

 

------------------------------

Program Location:

 

  at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)

  at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)

  at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

 

===================================

 

Connect to SSIS Service on machine "SQL64" failed:

 Error loading type library/DLL.

.

 

 

------------------------------

Program Location:

 

  at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)

  at Microsoft.SqlServer.Dts.SmoEnum.DTSEnum.GetData(EnumResult erParent)

  at Microsoft.SqlServer.Management.Smo.Environment.GetData()

  at Microsoft.SqlServer.Management.Smo.Environment.GetData(Request req, Object ci)

   at Microsoft.SqlServer.Management.Smo.Enumerator.GetData(Object connectionInfo, Request request)

  at Microsoft.SqlServer.Management.Smo.Enumerator.Process(Object connectionInfo, Request request)

 

===================================

 

Connect to SSIS Service on machine "SQL64" failed:

 Error loading type library/DLL.

.

 

 

------------------------------

Program Location:

 

  at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.GetServerInfo(String bstrMachineName, String& serverVersion)

  at Microsoft.SqlServer.Dts.Runtime.Application.GetServerInfo(String server, String& serverVersion)

 

-------------------------------------------------------------------------------------------------------------------------------------------

The database that the import is working on was migrated from the 32-bit server to the 64-bit server and seems to be working otherwise. I'm thinking there's a problem with the integration services on the 64-bit server. How would one repair the integrated services while not disrupting services? These databases are core business components for the office and can't be taken offline for any amount of time.

Alternatively, if there's a fix you know about based on what the errors above are saying, please let me know.


Viewing all articles
Browse latest Browse all 24688

Trending Articles