Today I ran into an application issue with an application, when a normal user would start the application the application would prompt for a file. When browsing to the file and opening the file the application would throw an error message: ‘unnamed file contains an invalid path’
The application was packaged with APP-V 4.* and was already running for ages in a Windows 2003/PS4.5/RES WM 2012 environment without any problems. During the project we’ve implemented a new environment based on Windows 2008R2 with RES Workspace Manager 2012 and tried to re-use as much packages as possible to minimize risk during the migration.
Basically the application was launched and you could browse to an application specific file to open it but the application would rapport ‘unnamed file contains an invalid path’.
To check the file we browsed to the folder that contained the application specific files using Windows Explorer, that worked without a problem so apparently we had access to the file.
We’ve copied the file into a home directory and it would start the application without any problems and we could select this file and run the business process.
After that we tried to copy the file back into the original directory but explorer gave an error:
When we tried the file copy from the old Windows 2003 environment it would copy the file without any problem.
That did put us in the right direction, opening the fileshare from the existing environment we could see the top level folder but when opening the fileshare from the new environment we couldn’t see the top level folder.
Apparently the sys admins turned on Access Based Enumeration (ABE) on this folder and didn’t install the component on their Windows 2003 servers. By using RES Workspace Manager for the drive mappings we could do the drive mappings without any problems but accessing the files would result in problems. The resolution was a review of the rights on the top level folder so the users could see the top level folder, after the review the file could be copied and the application could be launched with the application specific file so the business process could run.
Latest posts by Kees Baggerman (see all)
- Recovering a Protection Domain snapshot to a VM - September 13, 2019
- Checking power settings on VMs using powershell - September 11, 2019
- Updated: VM Reporting Script for Nutanix with Powershell - July 3, 2019
- Updated (again!): VM Reporting Script for Nutanix AHV/vSphere with Powershell - June 17, 2019
- Updated: VM Reporting Script for Nutanix AHV with Powershell - April 8, 2019