January 13, 2010 at 5:12 am
Ive tried this on two seperate installations and im recieving the same error message for both when ever i attempt to use an Access Database as a data source.
When i click on Preview in the OLE DB Source Editor i recieve the following error message:
===================================
There was an error displaying the preview. (Microsoft Visual Studio)
===================================
Index and length must refer to a location within the string.
Parameter name: length (mscorlib)
------------------------------
Program Location:
at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at Microsoft.DataTransformationServices.Design.PipelineUtils.ComposeSelectTableSqlStatement(ConnectionManager connectionManager, IServiceProvider serviceProvider, String tableName)
at Microsoft.DataTransformationServices.DataFlowUI.DataFlowConnectionPage.GetCurrentSqlStatement()
at Microsoft.DataTransformationServices.DataFlowUI.DataFlowConnectionPage.previewButton_Click(Object sender, EventArgs e)
I have tried using the Data Import wizard from within SQL 2005 to create the SSIS package which does import the data correctly but again the preview will not work from within Visual Studio and its this functionality that i require to work correctly.
Im using Native OLE DB\Microsoft Jet 4.0 OLE DB Provider (when i click on Test Connection it connects successfully) and there is no password requirements for the access file. Also this works on my colleagues setup perfectly and he's stumped as to why its not working for me (he even created a SSIS package which prompted the same error msg again when i imported it).
I'm very new to this application suite and really just finding my feet so it may be something very basic such as some service or settings that im missing but if anyone has any ideas it would be greatly appreciated.
Addition: Have just created a virtual machine, installed IIS, SQL 2005 & Service Pack 3, all microsoft updates. Didnt install Visual Studio 2005 but used instance from SQL2005 and still getting the same results.
Sick as a chip 🙁
--
I thought what I'd do was, I'd pretend I was one of those deaf-mutes.
January 13, 2010 at 9:01 am
Its something in SQL2005 Service Pack 3 causing the problem. I've installed a clean system in VMWARE and updated and tested all the way through to SP2 and everything works as planned until installation of SP3. Any one got any ideas what in SP3 could be causing this problem ??
--
I thought what I'd do was, I'd pretend I was one of those deaf-mutes.
January 13, 2010 at 10:07 am
certainly something in SP3 which specifically stops you from accessing datasources that have spaces in the table name.
--
I thought what I'd do was, I'd pretend I was one of those deaf-mutes.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply