February 2, 2022 at 10:32 pm
I have an SSIS package that was writing to a local folder on the SQL server for testing, now trying to write it to a production folder on another server. I made the folder shared to "everyone" but even that doesn't work.
Within the package, I was able to browse to the remote folder, so the SQL server can "see" it, but I get an error when trying to run the SSIS from a query window.
Microsoft (R) SQL Server Execute Package Utility
Version 15.0.4188.2 for 32-bit
Copyright (C) 2019 Microsoft. All rights reserved.
NULL
Started: 5:30:15 PM
Error: 2022-02-02 17:30:16.34
Code: 0xC0202009
Source: Warehouse Data Export Connection manager "DestinationConnectionExcel"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "The Microsoft Jet database engine cannot open the file '\My_Server\d$\Warehouse_Location_Export\Warehouse Data Export.xls'. It is already opened
exclusively by another user, or you need permission to view its data.".
End Error
Error: 2022-02-02 17:30:16.34
Code: 0xC00291EC
Source: Preparation SQL Task BP Whse Execute SQL Task
Description: Failed to acquire connection "DestinationConnectionExcel". Connection may not be configured correctly or you may not have the right permissions on this connection.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 5:30:15 PM
Finished: 5:30:16 PM
Elapsed: 0.953 seconds
NULL
February 2, 2022 at 10:53 pm
that happens a lot and sometimes without any explanation.
copy the remote file locally, change it as required and then copy it back to destination.
February 3, 2022 at 9:56 pm
Thanks, I used SSIS to write file locally, then DOS COPY in a .BAT file to move it to the remote server.
February 4, 2022 at 5:05 pm
Good one keep it up
February 4, 2022 at 6:23 pm
Good one keep it up
Really? What was good about this thread? I could be wrong but I'm thinking that you're just doing a SPAM test. If I am wrong about that, then welcome aboard.
--Jeff Moden
Change is inevitable... Change for the better is not.
February 4, 2022 at 6:54 pm
Thanks, I used SSIS to write file locally, then DOS COPY in a .BAT file to move it to the remote server.
Just curious - why not use the built-in file system task, or even a script task to copy the file? I normally just use a script task - much easier to copy/rename/move/delete files and generally only takes a line or two of code.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
February 4, 2022 at 7:32 pm
homebrew01 wrote:Thanks, I used SSIS to write file locally, then DOS COPY in a .BAT file to move it to the remote server.
Just curious - why not use the built-in file system task, or even a script task to copy the file? I normally just use a script task - much easier to copy/rename/move/delete files and generally only takes a line or two of code.
No good reason.
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy