DataNow Affinity - Troubleshooting
| Issue | Solution |
|---|---|
| Screen capture won't capture the intended screen. Some other application like GoToMyPC or WebEx is interfering. | Add the application’s executable name to the executable filter. To do this, make sure the interfering application is running. Open the Affinity Options dialog. If you want to add the executable to the filter for your own profile, go to the Local Advanced tab. If you want to add the executable to the filter for all users, go to the Global Options tab. Click the Settings button to open the filter dialog. Click Auto Detect to add the interfering applications to the filter. If your application is not detected, find the executable name and enter it manually. Save your settings. If you make the change to the global configuration, the change may not take effect immediately for other users. Ask them to log back on to Affinity to get the changes. |
| The Freestyle dialog keeps opening for a screen that I image-enabled. | When you image-enable the screen, make note of the caption of the Image Enable dialog. It lists the executable’s file name, and the ‘fingerprint’ or ID for the screen. When the Freestyle dialog appears, you will probably see that the ID in the dialog caption has changed. This means that some feature on the screen has changed and Affinity was not able to recognize it as a screen that had been image enabled. This generally means that a key control on the screen has moved or changed size. |
| I cannot log on using Windows Authentication | If you cannot connect to the Laserfiche repository using Windows Authentication, but you can log on to the Laserfiche Client without a user name and password, make sure that a password has been set for the ‘admin’ account on your Laserfiche server. A blank password for ‘admin’ will prevent |
| It takes a very long time for the Affinity logon window to open. | The Affinity logon window automatically retrieves the names of all of the repositories that are visible on your network. This can take a while on large or slower networks. Enable the option to log on automatically, and Affinity will immediately connect to the selected repository next time you log on. This is much faster because Affinity caches the repository name in instead of searching the network. |
| I can't make the toolbar go to or stay on my secondary display device. | The toolbar in Affinity version 1.0 does not support docking on a secondary device. |
| When I right-click the Affinity session icon, nothing happens. | A modal dialog, such as an error window or the Options dialog is open. It is probably behind another window where you cannot see it. Find the window and close it. |
| I do not have the option to save an image enable screen configuration to my local profile. | Open the Affinity Options dialog and select the Global Options tab. Change the Image Enable Screen Policy to allow users to save configurations to their profile. |
| Laserfiche shows that licenses are in use on workstations running Affinity, but the Laserfiche client window is not open. | This problem applies only to Affinity 1.0.163 and earlier. When a user closes a Laserfiche client window that has been opened by Affinity, and unless they use File > Exit from the menu to close the entire application, a hidden browser window remains open in the background, tying up a conncection/license. This is caused by a bug in the Laserfiche 7.2 Toolkit. Starting with version 1.0.183, Affinity now detects this scenario and unloads the Laserfiche client in the background, freeing the license. By default, a maximum of 10 seconds will pass before Affinity unloads the client. Please see the Affinity version history for more information. |
| When I am configuring Affinity and selecting what the destination folder is, I recieve the error "Type Mismatch". | If there is a shortcut to a folder below the default folder level, you will recieve this error message. After clicking close you will still be able to choose a destination folder. The folders listed will not however be in alphanumeric order. To workaround this error, either ignore it, or make sure there are no shortcuts listed in the default folder level before browsing to select a destination folder. This error exists in v.1.0.163 and earlier. |
