May 24, 2017 at 5:01 am
This one is starting to drive me nuts. I'm using Visual Studio Ultimate 2012 for SSIS 2012. On an old PC last year, I had a C: drive for windows and updates and a D: drive for everything else, including a ConfigFiles folder for SSIS. Everyone in the office uses D:\ConfigFiles for the SSIS config files so that when someone else has to edit a package I created, we all know where to put the config files or expect them to be. When I got a new PC last August, it only had a C: drive so I had to map a D: drive for the ConfigFiles folder.
On and off (not consistently, not all the time) suddenly the SSIS packages don't see the D: drive mapping when I open them up in VS to troubleshoot or build. It's not just config files either. I've got a faux Program Files folder that contains WinZip and other things which happens to be the same location on the servers these packages will eventually be on. Again, the issue isn't consistent. Sometimes the package sees the WinZip executable / config file, sometimes it tells me the D: drive doesn't even exist. I don't understand why it would be on and off thing.
Any thoughts as to what could be causing this? I'm not running the package via SQL Server at this point. It's open in VS on my PC under my credentials and I can see the D: drive just fine in Windows Explorer.
May 24, 2017 at 9:22 am
Possibly the mapped drive is disconnected / offline when you have the problem?
I'd suggest the next time it happens, before doing anything to try to fix the problem (and what do you have to do to fix the problem when it does happen?) drop to a Command Prompt and run "net use" and see what comes back. Does it show the D:\ drive and what does it show for the status of the drive?
May 24, 2017 at 10:53 am
That's the thing. The drive is online well before I open up the SSIS solution. It shows online and I can browse it in Windows Explorer, but when I open up a task in the package to browse, yes all mapped drives show disconnected even though they aren't.
That's what I'm trying to figure out. Why does SSIS think everything is unavailable with the rest of my programs see them as available? And sometimes SSIS / VS does see the drives as available. I've yet to figure out why the inconsistency. Although I didn't see this behavior the first few months after I got my new PC. Only in the past few months.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply