April 12, 2018 at 7:03 pm
SQL Server 2014. Running a package from my desktop and it works fine. Path/connectoin string for file is built from a package parameter. That passed in path does contain spaces for some of the path (directories with a space in the name... cant do anything about that).
When I deploy to the SSISDB catalog and execute, package does not execute (no entry reports) and error in SQL Agent is a bad paramter to dtexec utility.
The snippet of the dtexec cmmand shows my package parameter with spaces in the path, but spaces are cased in doublequotes
"\\host\networkshare\dir with space in name\dir\file.txt"
becomes
"\\host\networkshare\dir" "with" "space" "in" "name\dir\file.txt"
I thought it might have to do with the "\" being read as escape character, so I tried to escape the escape "\\\\host\\networkshare...", but still no luck... maybe I just didn't do that right?
Otherwise, any other ideas?
Thanks!
April 13, 2018 at 1:25 pm
I hate it, but I resolved this by just recreating the package from scratch.
The most annoying this is a just copied and pasted the connection managers and tasks/dataflows from the old package into the new.
Works.
Pfft!
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply