title: ZIP files not working in SSIS (server level issue?)
body: <p>I'm posting this rather odd issue here in the remote chance that someone has come across this before, or possibly just has an idea or two about what I could try or check next because I'm stumped.</p>
  
  <p><strong>Summary</strong>: SQL 2008 SSIS package tasks that attempt to create files with .zip extension fail with </p>
  
  <blockquote>
    <p>"Access to the path is denied"</p>
  </blockquote>
  
  <p><strong>Detail</strong>: This first occurred in a test environment with a package that works fine in Dev (and Prod). The part that makes this problem odd is that it is all about the File Extension, not security. I mention this now to curb replies about checking the security (SSIS Account, Directory Level permissions etc.) :- it's not that, 100%.</p>
  
  <p>So, I've built an SSIS package as a proof of behavior, that takes 3 files (<code>a.txt, b.txt, c.txt</code>) and respectively for </p>
  
  <p>(a) uses <code>CozyRoc Zip</code> to Create a Zip, </p>
  
  <p>(b) uses a script task to create a <code>.zip</code> (using <code>GZipStream</code> - I know this creates a GZIP not a ZIP but bear with me...) and </p>
  
  <p>(c) native SSIS File System Task copies the file from <code>c.txt</code> to <code>c.zip</code> (yes, creating a <code>.zip</code> file that is not really a zip file).</p>
  
  <p>All Three fail with the above message - the <code>.ZIP</code> files are created for (a) and (b), but remain at 0 length. (For (c) just the error message).</p>
  
  <p>Now, I edit the SSIS package and change the extensions of the destinations (to <code>.ZOP</code> or <code>.ZIP2</code> or <code>.GZ</code> or <code>.ANYTHING</code>), and all 3 work perfectly. And this is obviously how I know that it's the <code>.ZIP</code> extension not a "normal" security issue.</p>
  
  <p>So I've initially assumed this is a one-off on this test server because it was the only place it happens, but I've found another box (build rehearsal) on which exactly the same problem exists. I've tried associating <code>.ZIP</code> with various different programs (Windows Explorer, WinZip, 7Zip, WinRar &amp; "no program") and nothing works, and I've googled the problem to death with no luck yet. </p>
  
  <p>I've tried creating <code>.ZIP</code> files with the various installed archive programs using their GUIs and they all work fine. Existing <code>.ZIP</code> files can be unzipped using <code>CozyRoc</code>. Existing <code>.GZ</code> (GZIP) files renamed to <code>.ZIP</code> can be unzipped using the script GZipStream decompress. And I can rename files to and from <code>.ZIP</code> using SSIS or Explorer/CMD. It's just SSIS (specifically SSIS) creating a file with extension .ZIP (specifically .ZIP) throws this error.</p>
  
  <p>I'm starting to suspect it might have something to do with SSIS thinking that .ZIP is an archive "folder" not a ".ZIP File" but I don't know where to go with this idea, proving it or fixing it.</p>
  
  <p>Any ideas at all? - at my wits end!!</p>
  
  <p>Thanks in advance</p>
  
  <p><strong>P.S.</strong> The "obvious" answer of using <code>.ZIP2</code> and renaming is not an option, there are (literally) hundreds of packages running in production that create <code>.ZIP</code> files and packages need to move from Test to Prod without modification. I really need a solution, not a workaround, in this instance if there is one.</p>