Environment
Reflection Desktop (including Pro, for X, for IBM, or for UNIX and OpenVMS) 16.0 and higher
Reflection 2014
Reflection Pro 2014
Reflection for IBM 2014
Reflection for UNIX and OpenVMS 2014
Reflection for IBM 2011
Reflection for UNIX and OpenVMS 2011
Reflection Standard Suite 2011
Situation
- A Reflection settings file has been moved from a Windows 7 Desktop folder to Windows 10 Desktop folder.
- Opening this file by double-clicking on it results in the message "Could not read file C:\Users\<username>\Desktop\<sessionfilename>.
- The error is a Reflection Workspace pop-up message with an OK button.
- After clicking OK the user is left with the Workspace but no session.
- Adding the desktop folder to "Trusted Locations", or disabling the "Trusted Locations" security feature altogether has not resolved the issue.
Resolution
- Launch the Reflection Workspace.
- Go to the File menu and select Reflection Workspace Settings.
- Under Workspace Settings, click the Configure Workspace Attributes.
- Scroll Down to the Directories section. Change the "Default user data directory:" value to a path that actually exists.
Cause
The "Default user data directory" setting is saved in the "application.settings" file for each Reflection user, which is found in C:\Users\[username]\AppData\Roaming\Micro Focus\Reflection\Desktop\[version]\. In this case, the application.settings file deployed to the Windows 10 computer came from another computer on which workspace settings had been
configured. This resulted in a saved default user data directory
value that did not exist. To avoid this problem, application.settings files that
will be deployed to other machines must be defined using the Micro
Focus Installation Customization Tool, not copied from another computer. See the Reflection
Deployment Guide for more information -
https://www.attachmate.com/documentation/reflection-desktop-v16-1-sp1/deployment-guide/data/bookinfo.htm
https://www.attachmate.com/documentation/reflection-desktop-v16-1-sp1/deployment-guide/data/bookinfo.htm
Additional Information
If the steps in this
document do not resolve the issue please contact Micro Focus
Customer Support.