Viewing 15 posts - 1 through 15 (of 43 total)
That's brilliant, I removed it and not only did the error message disappear, but the package ran in about a quarter of the time. Adding the variable...
July 4, 2018 at 6:57 am
I deployed the package in SSISDB, the All Executions report gives more detail, but no other information about the error (other than it gets thrown at the very end of...
July 4, 2018 at 6:31 am
I've just run the package and again it's worked fine (delivered the flat file as it should) and once again thrown the error messages.
July 4, 2018 at 3:03 am
I think it's appearing at the run time. When I execute the package all the validation steps succeed, and the flat file appears in the right folder location, with the right...
July 3, 2018 at 9:37 am
Thanks loads for putting this list together. There's loads of new utilities and tools here that I'd never heard of (along with some old favourites!)
June 23, 2017 at 4:33 am
Just to finish the tale...in the end the way I fixed this was to move the backup location to a different server and try again. It worked fine...
May 16, 2017 at 9:32 am
Thanks for your help on this last week bmg002 and Sue_H .
I just picked this work up again and ran your hello world script above bmg002. It worked fine:...
May 15, 2017 at 9:07 am
Non Production. It's part of a new development server that I've just built. Only I'm using it currently.There's just a single user database on there at the moment, but I can create...
May 10, 2017 at 6:50 am
May 10, 2017 at 5:52 am
May 10, 2017 at 2:08 am
From checking, it sounds like the service account does have read/write permission on the backup folder unfortunately.So that doesn't sound like the cause (despite the error message)🙁
May 9, 2017 at 9:23 am
Not a stupid question at all. When I was first working in SSMS and worried about breaking stuff I remember being alarmed when I 'lost' Object explorer.
May 9, 2017 at 6:08 am
Ah that makes complete sense. I'll see what access the service account has and alter that if necessary.
Hopefully we've found a solution!
Cheers for your help everyone.
May 9, 2017 at 5:08 am
This leads me...
May 9, 2017 at 4:55 am
Verify both the SQL Server logs and...
May 8, 2017 at 7:44 am