DINEPLAN INSTALLATION

 

This document helps you to install the DinePlan and the SQL Server and configuring the SQL Server to access from all Terminals in the Locations

QUICK REFERENCE

We have a default Login User name and Password for SQL Server and we have default admin password for DinePlan.

SQL SERVER

User: sa

Pass: ahghbfgfc

DINEPLAN

1111

PRE-REQUISITE FOR DINEPLAN
OPERATING SYSEM WINDOWS 7/POS READY 7/8/10 or Above
SOFTWARE MICROSOFT .NET 4.5 or ABOVE

For Server, we should have the SQL SERVER EXPRESS 2005 or ABOVE

DINEPLAN INSTALLATION

Here are the Steps to be done for the Dineplan Installation.

STEP 1: Execute the install file (H:\DinePlan Installer or saved DinePlan Setup file).

STEP 2: If you receive a Security warning, this is normal and is due to your Internet Security Zone settings. Our installer is not digitally signed so this warning may be displayed. Click ‘Run’.

STEP 3: Click ‘Next’ on the initial welcome screen.

STEP 4: Click ‘Next’ to accept the default installation folder and user visibility. You can change the install folder, but we advised that you leave it as is for support purposes. (default: C:\Program Files (x86)\DinePlan\ )

STEP 5: Click ‘Next’ to confirm you are ready to begin the installation process.

STEP 6: Wait while the installation is in progress.

STEP 7: Install Complete! Click ‘Finish’ to exit the installation.

Note: See below for instruction on installing the SQL Server database software. SQL Server is used to store and manage the data used by DinePlan.

INSTALLING SQL SERVER EXPRESS

 

 Before installating the SQL Express, please make sure that the system is 64 BIT or 32 BIT. The respective installer has to be downloaded from the Repository.

Here are the steps to be done for the Installing of SQL Server.

STEP 1: Execute the install file.

STEP 2: If you receive a Security warning, this is normal and is due to your Internet Security Zone settings. Our installer is not digitally signed so this warning may be displayed. Click ‘Run’.

STEP 3: The needed files will be extracted to a temporary install folder and the SQL Server Installation Center will be displayed (this may take a minute or so).

 

 

STEP 4: Click ‘New installation or add features to an existing installation’.

 Screenshot-(6).png

STEP 5: Select ‘New Installation or add shared features’. Click ‘Next’.

STEP 6: If you agree with the license terms, check the ‘I accept the license terms’ box and click ‘Next’.

Screenshot-(25).png

 

 STEP 7: Ensure the following features are checked. Required features:

 Screenshot-(28).png

  • Database Engine Services
  • SQL Server Replication
  • SQL Client Connectivity SDK

STEP 8: Select the ‘Default instance' and Click ‘Next’.

STEP 9: The installation will verify the available disk space. If there is an issue you will see the

Screen to the right and Click ‘Next’.

STEP 10: Ensure all ‘Startup Types’ are set to ‘Default’ and click 'Next'.

STEP 11: Selecting Mixed Mode and Entering a secure password. We recommend using “ahghbfgfc" and click 'Next'.

 Screenshot-(33).png

STEP 11: Click ‘Next’.

Note: The Installation Configuration Rules screen will not be shown, unless there are issues. If there are issues, review and continue, if applicable.

STEP 12: The install progress will be displayed. When complete, click ‘Close’ on the final screen.

Screenshot-(35).png

STEP 13: Close the initial startup SQL Server Installation Center screen.

Screenshot-(23).png

CONFIGURE SQL SERVER TO OPEN THE PORT

This only needs to be done only in the Server and your location atleast one terminal

Here are the steps to be done.

STEP 1: Search for SQL Server Configuration Manager from the Start Menu

x0i1.png

STEP 2: Click the SQL Server Configuration Manager (Local).

STEP 3: Double Click the SQL Server Network Configuration.

Fak2.png

STEP 4: Double Click the Protocols for SQLEXPRESS.

 

STEP 5: Right Click the TCP/IP and then Enable that TCP/IP.

LbD3.png

STEP 6: Right Click the TCP/IP and Click Properties.

SEl5.png

STEP 7: Go to IP Addresses and Remove all the 0's in the TCP Dynamic Ports.

1Oi6.png

STEP 8: Enter '1433' in the Last TCP Port and Click 'OK'. It is mandtory to restart the SQL Express

6ar7.png

STEP 9: Click the SQL Server Services in SQL Server Configuration Manager (Local).

STEP 10: Right Click the SQL Server (SQLE...) and Click 'Restart'.

BEE8.png

STEP 11: After Restarted. Close the SQL Server Configuration Manager.

WINDOWS FIREWALL

Add the Port to the Windows Firewall exceptions list or Inbound and Outbound Rules. The Windows Firewall can be accessed through the Windows Control Panel.

 Note: You may need to restart your machine before the firewall settings take effect.

 Here are the steps to be done.

 STEP 1: Go to Control Panel\System and Security\Windows Firewall

 STEP 2: Click the Turn Windows Firewall on or off in the left side.

 STEP 3: 'Turn Off' the Windows Firewall and click 'OK'.

RESOLVING SQL SERVER CONNECTION ISSUES

Check 1 - Services
After install SQL Server, bring up SQL Server Configuration Manager and check Services are operational as depicted below:

Check 2 - TCPIP
Under the same Tool above. Make sure the TCPIP service is running for the DinePlan database. This is mainly for the Outlet which has more than one terminal.

Check 3 - Windows Authentication Vs SQL
For this, we need to have a SQL MANAGEMENT STUDIO to be installed.

Once you have changed the Login Authentication type you should get a choice when you log in to Studio, see below how Authentication is not greyed out:

Check 4 - Enable "sa" account
Again by defaut after fresh install of SQL Express the “sa' account is disabled and if you run with “SQL Authentication” you will need an SQL User Account operating. So bring up the properties as show below and enable the account:
 
Check 5 - Check Firewall opened
This will depend on if you are using windows firewall or an antivirus firewall but the concept will be the same for both. Below  the product that was shipped with the PC and by default there is no enabled port open!. Open up the port as required as depicted below. Make sure you check the properties in the SQL Server Configuration Manager TCPIP Property Editor to see what port number is being used:
 

 

 

 

Back to top