July 23, 2018 at 12:59 am
Hello,
I was working on a SSIS Package which simply loads an excel file into a SQL table without any transformations. The package executes successfully on Visual Studio 2015. However, when I try to load it via SSIS Catalog (SSISDB), the execution fails. The size of excel source file is (approximately) 2 MB.
If I reduce the number of rows inside the excel source file and bring the file size down to around 1.16 MB, then the file is loaded successfully via SSIS Catalog (SSISDB).
July 23, 2018 at 3:38 am
pmaceke - Monday, July 23, 2018 12:59 AMHello,
I was working on a SSIS Package which simply loads an excel file into a SQL table without any transformations. The package executes successfully on Visual Studio 2015. However, when I try to load it via SSIS Catalog (SSISDB), the execution fails. The size of excel source file is (approximately) 2 MB.If I reduce the number of rows inside the excel source file and bring the file size down to around 1.16 MB, then the file is loaded successfully via SSIS Catalog (SSISDB).
Do you have a question for us?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
July 23, 2018 at 3:42 am
pmaceke - Monday, July 23, 2018 12:59 AMHello,
I was working on a SSIS Package which simply loads an excel file into a SQL table without any transformations. The package executes successfully on Visual Studio 2015. However, when I try to load it via SSIS Catalog (SSISDB), the execution fails. The size of excel source file is (approximately) 2 MB.If I reduce the number of rows inside the excel source file and bring the file size down to around 1.16 MB, then the file is loaded successfully via SSIS Catalog (SSISDB).
You say it fails, but you seem to have forgotten to provide the errors for said failure. 🙂 Could you post them please?
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
July 23, 2018 at 4:02 am
Hi.
Sorry for not including the error. Below is the error that I'm getting:
"FSSA_Data Flow Task:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "FSSACashOpenItems" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed."
Please note that my package loads more than 4 files from the same directory but only this one which is more than 2MB is not going through. The rest get loaded successful.
My question is what could be a reason for the 2MB file to fail?
July 23, 2018 at 4:12 am
pmaceke - Monday, July 23, 2018 4:02 AMHi.
Sorry for not including the error. Below is the error that I'm getting:
"FSSA_Data Flow Task:Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "FSSACashOpenItems" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed."Please note that my package loads more than 4 files from the same directory but only this one which is more than 2MB is not going through. The rest get loaded successful.
My question is what could be a reason for the 2MB file to fail?
Notice that error states "There may be error messages posted before this with more information on why the AcquireConnection method call failed.". I can't recall a case where that statement is not true (I've had people tell me there aren't, only to check myself and there are if you look back enough). Could you provide all the relevant errors please?
Thanks.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
July 23, 2018 at 4:35 am
Could you try putting the Excel file onto one of the server's local drives and loading it from there? Just to rule out any possible network issues.
I agree with Thom's comment about error messages.
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply