We are trying to store the sandboxes of our Thinapps on a networkshare and we encounter a lot of applications craches because of this.
We work in a VMWare View environment with Windows 7 clients and a few fileservers based on Windows Server 2008. All Thinapp packages work as expected on Windows 7 using a local default sandbox. However, when we rebuild the Thinapps pointing the sandboxes to a networkshare on a fileserver based on Windows Server 2008, most of the applications crash. Using remote Windows Xp machines as a fileserver gives no problems for 4.6.2. However, Windows 7 machines as fileserver does give problems same as Windows Server 2008.
We have two workarounds for this:
1. When we use Thinapp 4.6.1 all applications work perfectly with sandboxes located on a networkshare on either a 2003 or 2008 fileserver.
2. When we use Thinapp 4.6.2 and store all the sandboxes on a Windows Server 2003 fileserver, we encounter no problems at all.
Has anyone encountered this problem or have tips/tricks that could help us using 4.6.2 combined with Windows Server 2008?
Thanks in advance.
We encountered the same problem, no solution at the moment.
Out sandbox location is a DFS location on a netapp filer (CIFS). When we map the sandbox location to a windows 2003 share the package runs perfectly.
We have this issue when creating a Office 2003 package.
The new Thinapp version 4.7 rever to this as a known issue.
When a ThinApp package is deployed on a Windows 7, Windows Vista, Windows 2008, or Windows 2003 operating system, and the sandbox is located on a network share that is hosted on one of these operating systems, or on a SAN that also uses the SMB 2 protocol, the application crashes.
Workaround: Disable the SMB 2 protocol on the device that is hosting the network share.
We have not tested this yet.
we checked our netapp and smb2 is disabled by default.
Also the application runs fine on the netapp share when loaded on windows 2003 or XP