SQL Server Installation and Configuration

WEBGILITY 2020. ALL RIGHTS [Link]

1
SQL

Installation of Webgility Software

● Go to downloads and click on download as shown below for installation

● Most of the times, SQL will be downloaded automatically along with Webgility software

2
SQL(Structured Query Language) Manual Installation for Database

● Go to Google homepage and search for SQL server

● SQL 2016 or 2017 would be preferred option

SQL Installation for WD

● Automatic Via Software when you click on Install option

Click next, next till process completes

3
Manual - Select Connect WD to existing SQL Server Option

4
Installation of SQL Server 2012 Version

● Select from the Microsoft website

● Click on Download

5
● For 64-bit operating system, Select ENU\x64\SQLEXPR_x64_ENU.exe

● Similarly, for 32-bit operating system, Select ENU\x86\SQLEXPR_x86_ENU.exe

6
● Once installer is downloaded, click on Installer

7
8
● Click on New SQL server stand-alone installation option

9
10
● Select perform a new installation in case that option appears during installation

11
● Name the Instance as Webgility
● When you click on Instance ID field, name will be automatically changed to
Webgility(As per named Instance)

12
13
● Start Type to be selected as Automatic for both SQL server database engine and SQL
Server [Link] on Next

14
● Select Mixed Mode and Enter Password. Password is [Link] on Next
● User name: sa

15
16
● Status will be succeeded for all the features. Click on Close since installation is
complete

17
How to identify whether system type is 64/32 bit

Make a note of Computer name and System type.

● Right click on PC, Go to properties

18
● Make a note of Computer name, Named instance and Server Configuration

19
Media Family Error

● Installed SQL server and trying to restore on lower version

● For Migration of data to new computer, one should be aware of SQL server installed on Old
computer
● Same credentials of a user can be used only on one desktop at a time
● Database will be stored on one system which will act as primary system(check for primary
computer and instance name)
● From switching from computer to another computer, take backup of database to restore

20
How to check Instance Name

Type [Link] in search option.

21
How to check Source Name

C:\Webgility\UnifyEnterprise\XML. Open API Config file with notepad.

22
● Right click on api config file and open with notepad

● Source=krishnar-pc\Unify as per above screenshot. Krishnar-pc is the name of a

computer and Unify is the name of the instance

23
How to check data file size for an Instance

C:\Program Files\Microsoft SQL Server\[Link]\MSSQL\DATA. Check for latest Instance.

24
In case of restore, select the instance which has maximum size. From the above two screenshots,
you can find Unify and Webgility instances.

Webgility Instance - 6208 KB, Unify- 73728. In this case, suggest the customer to go with Unify
instance since it has more file size.

If customer wishes, we can restore with Webgility instance also.

Also this should be only in case if customer has multiple database instances and not sure which one
to go with.

Connecting to database: SQL will be installed automatically along with software or manually.

Manual Connection to Database

During the process of manual connect to database, because of the previous instance if system is not
allowing to login to database, modify the data source i.e. change the name of instance so that
system will not identify the instance.

25
Existing Instance Name

Modified Instance Name

26
● Use SQL server Authentication and enter login credentials and click on connect

● user name sa in lower case

27
Index outside the bounds of array(SQL): Everything is correct in terms of version, however
because of database file issue not able to connect.

Fix:

1. Install the management studio

2. Take the assistance of engineering team for guidance

Incorrect Database Scenarios

28
For incorrect database scenarios, there are 3 options to choose. We have to select one of the
options as per error occurred.

Option 1: Move Webgility to this computer using the backup file of the previous Webgility database

If a backup file is available, click on browse and select the database backup file.

During the backup file, there could be 3 situations that could occur.

● Media family error : Installed SQL server and trying to restore on lower version
● Index outside the bounds of array(SQL):Everything is correct in terms of version, however
because of database file issue not able to connect
● Successfully installed

Option 2: Connect Webgility database to an existing SQL server

For incorrect/wrong instance scenarios.

Option 3: Re-configure store connections and settings for mismatched stores

No backup file exists.

29
Identification of Primary Computer

1. Open C:\Webgility\Unify Enterprise\XML folder

2. Open ‘apiConfig’ file in notepad
3. Check Source Name i.e. Username and Integrated Security i.e. password of instance
4. Match the ‘Source Name’ from computer name to identify whether it is a primary computer
or not

30
SQL Troubleshooting Steps for Add on Computer not connecting to existing Instance

Troubleshooting will happen on primary computer.

In case of add on or new installation after instance creation, if the primary computer is working fine
however there is an issue in the secondary computer, below steps to be followed to rectify the issue.

● Check whether primary computer is working or not, if it is working then move to next step

● Logout the Webgility account from primary computer if the same credentials to be used in
secondary computer
● If customer is having add on account, use the add on credentials to login on secondary
computer
● Enter the login credentials, will start connecting to SQL
● Select the SQL Server authentication mode, choose the correct instance available in local SQL
server, enter the username(sa) & password(Webgility2011)

31
Note:
A. If customer is not aware/forgot about password at the time of connecting add on after few days,
take help from engineering team to reset the SQL password in case password details are not
available in API config file in primary computer

B. If the Windows authentication option was chosen(earlier) in the primary computer to connect the
SQL, log in credential details will not be available. To change the authentication mode, take the help
of engineering team

Search for [Link]

32
● Select the instance(one you are looking for) i.e. SQL Server Unify. Right click on
instance and then click on properties

33
● Click on Log On and then on browse

34
● Enter NET and click on check names as shown above

35
● Delete Login credentials, click on apply

36
Steps which were followed for SQL Server Unify, same steps to be followed for SQL Server Browser.

37
● Restart SQL Server Unify for changes to take effect

● Restart SQL server browser for changes to take effect

38
● Search SQL Server configuration Manager in search option

● Or C:\Windows\SysWOW64. Double click on SQL Server Manager

39
● Check for protocol of instance(you are looking for)
● Status to be enabled as shown above

● Click on SQL server services in case you would like to know the instances that are
existing on server

40
● Open control Panel for Windows defender firewall

● Click on System and Security

● Click on allow an app through windows firewall

41
● Click on change settings

● Click on Allow another app

42
● Click on browse

● Click on Add

43
● If Webgility is already added to the list of exceptions, the system will prompt below
message. If not will add to list of exceptions

44
● Similarly browse for SQL server windows NT-64 bit
● Path : C:\Program Files\Microsoft SQL
server\[Link]\MSSQL\Binn\[Link]
● If SQL server windows NT-64 bit is already added to the list of exceptions, system will
prompt below message. If not will add to list of exceptions

45
● Domain, Private and Public to be enabled for Webgility

● Domain, Private and Public to be enabled for SQL Server

46
● Domain, Private and Public to be enabled for all ECC apps. Click on OK

47
● Restart SQL server browser and SQL Server Unify for changes to take effect

48
If you are not able to find primary instance name in the drop down, click on browse to find

out Primary computer and instance.

After performing above troubleshooting steps, still not able to connect to database with

Primary computer and instance.

49
50
● In primary computer, Go to Run and enter CMD and click on OK

● Enter ipconfig

51
 ● Make a note of IP Address

Go to the Secondary computer and open the Webgility software. In place of computer name, place
the IP address i.e. Primary IP Config\Unify

In this case it will be [Link]\Unify. Enter the details and connect.

Still not able to connect to the database, Add the exception ‘TCP’ and ‘UDP’ Ports on the

Windows 7 machine.

[Link]

In place of ECC, it should be Webgility.

52