Recent Searches

No recent searches

    Popular Articles

      Articles

      View all

        Topics

        View all

          Tickets

          View all
            no results

            Sorry! nothing found for

            GuardPoint10 - Using an Existing SQL Server Installation

            Created by Piotr Jamny, Modified on Tue, 22 Sep at 1:39 PM by Piotr Jamny

            GuardPoint10 - Using an Existing SQL Server Installation 

            This guide explains how to install GuardPoint 10 using an existing Microsoft SQL Server instance instead of the bundled SQL Express installation.

            GuardPoint 10 supports Microsoft SQL Server 2016, 2017, 2019, 2022 and 2025 releases in both Express and Standard editions. 

            Note: While we have tested multiple SQL versions successfully, environmental or SQL configuration differences may occasionally cause issues. If you encounter problems during setup, contact Sensor Access Technical Support.

            Before You Begin

            Before installing GuardPoint 10:

            1. Install Microsoft SQL Server
            2. Install SQL Server Management Studio (SSMS)
            3. Confirm you can connect to the SQL instance using SSMS
            4. Ensure TCP/IP is enabled on the SQL Server instance
            5. Confirm the SQL Server service is running


            Step 1 – Create the GuardPoint 10 Databases


            Open SQL Server Management Studio (SSMS).

            Create the following two databases exactly as shown below:


            Database Name
            AC8_Default
            AC8Journal_Default

            To create a database

            1. In SSMS, expand the SQL Server instance
            2. Right-click Databases
            3. Select New Database
            4. Enter the database name
            5. Click OK
             

            Repeat for both databases listed above.


            Step 2 – Configure SQL Permissions


            The required SQL permissions must be configured before installing GuardPoint 10.

            Verify NT AUTHORITY\SYSTEM Permissions

            Follow this guide:

            How to Verify NT AUTHORITY Permissions in SQL Server


            Step 3 – Configure the sa Account 


            GuardPoint10 uses the SQL sa account to connect to the SQL database, so the account must be enabled and correctly configured.


            Make sure that:

            • SQL Server is configured for SQL Server and Windows Authentication mode (Mixed Mode).
            • The sa login is enabled.
            • Password policy enforcement is disabled if required for the password being used by GuardPoint10.
            • The GuardPoint10 databases are owned by sa.


            If you are already connected to SQL Server using a Windows account with sysadmin permissions, the following script can be used:


            Enable Mixed Mode Authentication
            USE [master];
            GO

            EXEC xp_instance_regwrite
            N'HKEY_LOCAL_MACHINE',
            N'Software\Microsoft\MSSQLServer\MSSQLServer',
            N'LoginMode',
            REG_DWORD,
            2;
            GO


            Enable the sa Login
            ALTER LOGIN [sa] ENABLE;
            GO


            Disable Password Policy and Expiry Checks
            ALTER LOGIN [sa]
            WITH CHECK_POLICY = OFF,
            CHECK_EXPIRATION = OFF;
            GO


            Set sa as Owner of the GuardPoint10 Databases
            USE [master];
            GO

            ALTER AUTHORIZATION ON DATABASE::[AC8_Default] TO [sa];
            GO

            ALTER AUTHORIZATION ON DATABASE::[AC8Journal_Default] TO [sa];
            GO


            Important: After changing the authentication mode, restart the SQL Server service before attempting to connect using sa.

            If the sa password needs to be set or changed, run:


            Set or Change the sa Password
            ALTER LOGIN [sa]
            WITH PASSWORD = 'YourNewPassword';
            GO


            Use the same sa password when configuring the SQL connection in GuardPoint10.

            If you receive:

            Create failed for User 'sa'. (Microsoft.SqlServer.Smo)

            Run:

            Correct GuardPoint10 Database Ownership
            USE [master];
            GO

            ALTER AUTHORIZATION ON DATABASE::[AC8_Default] TO [sa];
            GO

            ALTER AUTHORIZATION ON DATABASE::[AC8Journal_Default] TO [sa];
            GO


            Then retry the GuardPoint10 configuration.


            Step 4 – Configure a Custom SQL Login [Optional]


            If preferred, you may create a dedicated SQL login specifically for GuardPoint 10 instead of using the sa account.

            The custom SQL login should have:

            • sysadmin server role permissions
            • db_owner permissions on:
              • AC8_Default
              • AC8Journal_Default

            Repeat the same steps shown in the NT AUTHORITY permissions guide for the custom SQL login:

            How to Verify NT AUTHORITY Permissions in SQL Server


            Note: Any custom SQL login must be created and tested before starting the GuardPoint 10 installation.


            Step 5 – Configure SQL Network Settings

            If GuardPoint 10 is connecting to SQL across the network, verify SQL network protocols are enabled.

            Open SQL Server Configuration Manager


            Navigate to:

            SQL Server Network Configuration → Protocols for [AC8SQL or other Instance Name]

            Ensure the following are enabled:

            • TCP/IP
            • Named Pipes [recommended to Enable]


            Step 6 – Install GuardPoint 10

            Launch the GuardPoint 10 installer.

            Select:

            • Advanced Installation
            • Full Installation
            • Select an existing SQL Server

            Enter:

            ParameterExample
            SQL Server NameSERVERNAME\INSTANCE NAME
            SQL Port49999
            Authentication TypeSQL Authentication
            Usernamesa or custom SQL login
            PasswordYour SQL password

            Click:

            • Test Connection

            Once successful, continue the installation.

            The GuardPoint 10 installation wizard supports connecting to an existing SQL Server instance. 


            Recommended SQL Configuration

            For best results:

            • Enable TCP/IP
            • Enable Named Pipes
            • Use static SQL ports where possible
            • Allow SQL traffic through Windows Firewall
            • Ensure SQL Browser service is running for named instances


            Necessary GuardPoint 10 

            Ensure that local firewalls, antivirus software and network firewalls are not blocking the required ports below.


            ServiceProtocolPort
            AcsServer HTTPTCP7654
            AcsServer Net.TCPTCP8765
            AcsServer → NM HTTPTCP4567
            AcsServer → NM Net.TCPTCP5678
            AcsServer → GUI HTTPTCP4568
            AcsServer → GUI Net.TCPTCP5679
            AcsWatchdog HTTPTCP5656
            AcsWatchdog Net.TCPTCP5757
            WatchdogClient HTTPTCP6767
            WatchdogClient Net.TCPTCP6868
            SQL ServerTCP1433 / 49999
            SQL BrowserUDP1434
            Tibbo ControllersTCP1001
            Lantronix ControllersTCP10001
            Tibbo DS ManagerTCP65534
            Lantronix DeviceInstallerTCP9999
            Suprema Biometric ReadersTCP51211
            API Service (AcsApiService)TCP10695


            GuardPoint 10 default ports are documented throughout the installation and prerequisite documentation. 

            Additional Information

            GuardPoint 10 supports installation against existing SQL Server environments using custom SQL parameters during advanced installation. 

            Default GuardPoint 10 installations normally create two SQL databases automatically during installation. 


            If you experience any issues during installation or SQL configuration, contact: 

            support@sensoraccess.co.uk



            Was this article helpful?

            That’s Great!

            Thank you for your feedback

            Sorry! We couldn't be helpful

            Thank you for your feedback

            Let us know how can we improve this article!

            Select at least one of the reasons
            CAPTCHA verification is required.

            Feedback sent

            We appreciate your effort and will try to fix the article

            Preview
            0 of 0