In Prevail version 5 and version 6, the Prevail executable auto-detects for the presence of the Advantage Database Server. If for any reason the ADS server isn't "seen" by the client the Prevail executable reverts to running in LOCAL mode.
At this point, should someone login to Prevail - in local mode. The ADS server, no matter if started or restarted afterwards will NOT be detected on ANY WORKSTATIONS until EVERYONE IS OUT OF PREVAIL, even if the ADS service is restarted it will not be detected until EVERYONE is accessing Prevail using the same method of connectivity.
The age old rule applies - you cannot have a mix of 'remote' and 'local' users on a dataset. This issue is more prevalent with versions 5 and 6 of Prevail because the client detects for the presence of the ADS server and lets them in using LOCAL mode when the Advantage Server isn't available.
So - get everyone out of Prevail. If need be, reboot the server - alternatively, use 'computer management' on the server PC to remove all connections to any ADT/ADM/ADD on the server shared folder.
Sometimes, even after getting everyone out, a final restart of the Advantage Database Server is necessary in order for it to be detected on the workstations. |
|
|
|
|
|
| User Opinions |
|
| No users have voted. |
|
| How would you rate this answer? |
|
|
|
