July 29, 2024 at 7:49 am
Hi all
We've got an SSIS package that downloads a zipped database, unzips the contents, and then copies the contents to new locations.
When doing the copy (using a file system task), we occasionally get an error that simply says "An unexpected network error occurred".
I've checked there's enough room on the receiving drive(s) for the mdf and ldf files so I know it's not that.
MDF is around 1.5GB (with 1.4TB left on the drive)
LDF is around 2GB (with 90GB left on the drive)
Is there any way of getting some more details of what the error is?
If I run it manually, I never seem to have a problem.
When run as part of a job, it usually runs but sometimes fails so I know the agent has enough rights on the drives.
Anyone any ideas?
TIA
Richard
July 29, 2024 at 8:10 am
Is that error message taken from the All Executions report?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 29, 2024 at 8:16 am
Hi @phil - yes it is. It's the only place I can find the error (job history just points me to the execution history).
July 29, 2024 at 9:32 am
I've had those 'unexpected …' errors several times in the past and they're almost always difficult to solve, exactly because of the dearth of logging info which they seem to generate.
If I were you, I would be considering replacing the FST with a Script Task containing robust TRY/CATCH code. Maybe that would get you further.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
July 29, 2024 at 9:33 am
Cheers @phil. It's not my SSIS package either but I don't think it would be difficult to swap the FST for a script task of some description.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply