September 30, 2005 at 6:22 am
I have a DTS job that runs a query, puts the recordset in a global variable, and then in an ActiveX step creates a flat file with specific formatting requirements. There are a couple of steps after that which update the database, etc, but I'm done with the flat file after the ActiveX step (step 2). The job starts at 11:30pm and finishes at about 11:30:30pm -- it's not rocket science.
The file is being created on a Windows Share using a fully qualified UNC address in the ActiveX step. The file is being created just fine every night, it's what happens afterward that's puzzling.
The file has to be sent to an outside vendor. We have a corporate file transfer facility that is used for all these transfers to ensure appropriate security, encryption, etc. The file transfer job is set up to run at 11:45, xcopy the file from the UNC share to it's own server, encrypt it, then FTP to the vendor. Every night the file transfer task receives a message saying it cannot access the file. The next morning we come in, run the job manually and it runs fine.
It appears there's some kind of lock on the file, though how that can be after the SQL Agent Job that runs the DTS package finished executing 15 minutes before the file transfer job tries to read the file is totally beyond me. We've already gone over security (Share permissions and Windows permissions) and they're all correct. The job wouldn't run manually if they weren't.
Any clues? Any help at all would be greatly appreciated.
September 30, 2005 at 12:22 pm
I knew it wasn't me...
The delete step in the file transfer job was coded incorrectly.
This admission of course after a week of debugging and insisting that I was somehow "locking" the file.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply