In some cases NX users have configurations that use remote storage. This seems to be more common in virtual environments but can happen in non-virtual environments too. In certain cases, due to latency issues, a write or read operation may fail because of that and lead to the NX operation failing or an internal exception happening. To test this you should exit NX and reset your storage pointers to local and accessible locations. For instance, if UGII_TMP_DIR is set to point to a remote location change that to a local one such as C:\TEMP (make sure that folder exists and is writable). Examine any environment parameters that change the default location (which is typically a local folder) to a remote location.