{
  "WorkItem": {
    "AffectedComponent": {
      "Name": "",
      "DisplayName": ""
    },
    "ClosedComment": "",
    "ClosedDate": null,
    "CommentCount": 0,
    "Custom": null,
    "Description": "The file itself is 2Gig in size, so I won't attach.  We create a lot of self-extracting zips using DotNetZip and they extract correctly.  It's only occurred on one data set which leads me to question if it's content or some other issue.\n \nI'm using the 1.9.1.5 version of DotNetZip.  I've also tried the 1.9.1.8 version and it still occurs.\n \nThe error message is \".Net Framework Initialization Error\"  Screenshot of the error message is attached.",
    "LastUpdatedDate": "2013-02-21T18:42:50.367-08:00",
    "PlannedForRelease": "",
    "ReleaseVisibleToPublic": false,
    "Priority": {
      "Name": "Low",
      "Severity": 50,
      "Id": 1
    },
    "ProjectName": "DotNetZip",
    "ReportedDate": "2012-05-29T07:05:38.163-07:00",
    "Status": {
      "Name": "Proposed",
      "Id": 1
    },
    "ReasonClosed": {
      "Name": "Unassigned"
    },
    "Summary": "Runtime error occurs when attempting to extract a self-extracting zip",
    "Type": {
      "Name": "Issue",
      "Id": 3
    },
    "VoteCount": 1,
    "Id": 15233
  },
  "FileAttachments": [
    {
      "FileId": 4399,
      "FileName": "runtime error for self extracting zip.png",
      "DownloadUrl": ".\\4399"
    }
  ],
  "Comments": [
    {
      "Message": "I should also add that we've ruled out the .net runtime missing on the machine because this is all being done on the same machine.  For one extract to work and another to fail on the same machine seems to rule out the .net runtime as the culprit.",
      "PostedDate": "2012-05-29T07:14:54.23-07:00",
      "Id": -2147483648
    },
    {
      "Message": "This issue still occurs, but I do have an update.  I can break up the contents into three separate zip packages and I do not get the error.\r\n\r\nEach zip package is under 2 Gig in size and I'm getting this error on Windows 7 / 32 bit machines so I'm wondering if the size of the zip contents is the culprit.\r\n\r\nAny thoughts? (anyone?)",
      "PostedDate": "2012-06-12T08:06:04.567-07:00",
      "Id": -2147483648
    },
    {
      "Message": "Issue resolved:  The error message occurs only on self-extracting zip packages that are larger than the 2 Gig Windows 32 bit size limitation on executables.  It's impossible to tell this from the error message.\r\n\r\nBut for the sake of someone else that may stumble across this post Windows has the following size limits:\r\n\r\nWindows 32 bit machine:  an executable can't be greater than 2 Gig.\r\nWindows 64 bit machine:  an executable can't be greater than 4 Gig.\r\n\r\nSelf-extracting zips are no different than any other Windows executable and have the same size limitations.",
      "PostedDate": "2012-06-13T06:03:32.683-07:00",
      "Id": -2147483648
    },
    {
      "Message": "Addendum: 32 bit limitation on an executable's size is 2 Gig... no one here is sure what the 4 Gig executable limit is.  I was originally told 4 Gig, but that's incorrect.",
      "PostedDate": "2012-06-14T13:40:16.36-07:00",
      "Id": -2147483648
    },
    {
      "Message": "",
      "PostedDate": "2013-02-21T18:42:50.367-08:00",
      "Id": -2147483648
    }
  ]
}