To resolve this issue, make sure the LS CommunicationServer service has local administrative rights on the server on which it is running. If it does not, you will have to work with local IT to obtain local admin rights on the PC and possibly set up the service to run with the local admin account.
The Local System Account should have sufficient permissions. As an alternative, a specific user with local administrative rights can also be used to run the LS CommunicationServer service.
BASIS and OnGuard (All versions)
Note that the reason the access panels showed as online in Alarm Monitoring when running the CommunicationServer as an application is likely because the user who was logged into Windows was either a local or domain administrator. This provided the necessary permissions for the CommunicationServer to function properly.
In addition, each reported instance of this issue was accompanied by a NAK error containing the bold-faced bytes in the string below (though the string itself may vary). 5B 00 17 00 83 0A 00 93 8E 59 42 02 02 00 05 00 FF 07 00 06
Limited Warranty on Information: The documents contained on this website are distributed as is, without warranty of any kind, either express or implied, including but not limited to implied warranties for the document’s quality, performance, merchantability, or fitness for any particular purpose. Neither Stanley Security Solutions, Inc., nor its dealers or distributors shall be liable to the user or any other person or entity with respect to any liability, loss, nor damage caused or alleged to be caused directly or indirectly by this information.