I had an SSIS package fail in a script task this morning. As part of the why process I opened up one of the files it was processing and got this message:
I get the idea and I’ll hunt around to find what has it open, but I’m bemused at ‘another user’ which is either a really great domain user name or a fun default when no user name is available – presumably the latter. The package is using GetSchema to get the sheet names and I suspect it is/was the cause, but I wonder why no useful user name provided?
In the course of a quick search I found this post that doesn’t answer that question, but does go into a lot of detail (look at the flow chart!) on all the various ways it can happen.
One thought on “Another User Has Locked My File!”
it happens sometimes, copy the file with a file system task hen process the copy
Comments are closed.