EnablerWiki - User contributions [en]

Change EEPOS Machine Role

2024-02-11T23:05:46Z

Jake: /* Overview */

== Overview ==
The role of a EEPOS installation can be changed using the command line.

This means that a store can be reconfigured without needing to reinstall EEPOS.

The command line tool is accessed as follows:

* Ensure EEPOS is closed on the till.

* Open Command Prompt as an administrator.

* Enter the below command to browse to the EEPOS folder.
cd "c:\Program Files (x86)\Magenta Retail\EEPOS"

* Run EEE_POS.exe /c storeservername storeserverdatabase replicationsourceiseee
** Storeservername is the full SQL instance name of the store server including \MAGENTAPOS if necessary.
** StoreServerdatabase is the store servers database name
** Replicationsourceiseee is a flag indicating if this machine will replicate from EEE or from the store server (e.g. Y or N)
** All parameters must be supplied
* After a few moments it should display the below message indicating the change is
complete.
* Once the Process complete text is shown, press Enter to return to the command prompt.
* Open EEPOS and ensure the till is displaying the green POS Service light.
* If the POS Service is displaying the orange light, this may indicate the wrong computer name was used in the above command. The command can be run again with the correct computer name.

== Available Versions ==
The table below details which versions contain which functionality

{| class="wikitable" style="margin:left"
|+ Versions
|-
! Function !! EEE Version !! POS Version(s)
|-
| Reconfigure POS Role || 1.92.05 || 2.20.16.00
|-
| Reconfigure POS Role || 1.88.26 || 2.18.12.00
|-
|}

== Configuration Required ==

None

== Detail ==
Here are some scenarios where this can be used. There are 3 machines at the store in the following scenarios.
:- MAG1 – Store Server
:- MAG2 – Till 2
:- MAG3 – Till 3

== Scenario 1 – Promoting a till to a store server ==
MAG1 is the existing store server but it has had a hardware failure.
Whilst MAG1 is being replaced, MAG2 is going to be the store server.

=== Promoting a till to a store server ===
On MAG2
* Close EEPOS
* Open an Administrator command prompt.
* Change to the EEPOS installation folder (e.g. C:\Program Files (x86)\Magenta Retail\EEPOS)
* Run the command
EEE_POS.exe /c MAG2\magentapos EEPOS Y

* Start EEPOS and ensure the POS Service indicator light is green

=== Updating tills to communicate with the replacement store server ===
On MAG3
* Close EEPOS
* Open an Administrator command prompt.
* Change to the EEPOS installation folder (e.g. C:\Program Files (x86)\Magenta Retail\EEPOS)
* Run the command
EEE_POS.exe /c MAG2\magentapos EEPOS N
* Start EEPOS and ensure the POS Service indicator light is green

== Scenario 2 – Store Server replacement ==
The store server (MAG1) hardware has been replaced and it has had EEPOS re-installed to the correct version (note: the same version as the other tills in the store) and replication from EEE has completed successfully.

=== Install new store server ===
On MAG1
* Ensure the hostname on the tills record has been updated to the new machine name (if a new machine name has been assigned)
* Install EEPOS to replicate from EEE
* Upgrade EEPOS to the same version that is installed on the existing store tills
* Replication from EEE must complete prior to completing further steps

=== Demoting the existing store server to a till ===
On MAG2
* Close EEPOS
* Open an Administrator command prompt.
* Change to the EEPOS installation folder (e.g. C:\Program Files (x86)\Magenta Retail\EEPOS)
* Run the command
EEE_POS.exe /c MAG1\magentapos EEPOS N
* Start EEPOS and ensure the POS Service indicator light is green

=== Updating tills to communicate with the new store server ===
On MAG3
* Close EEPOS
* Open an Administrator command prompt.
* Change to the EEPOS installation folder (e.g. C:\Program Files (x86)\Magenta Retail\EEPOS)
* Run the command
EEE_POS.exe /c MAG1\magentapos EEPOS N
* Start EEPOS and ensure the POS Service indicator light is green

== Scenario 3 – All tills replicate from EEE ==
MAG1 will still be classified as the store server as it will hold stocktake data, suspended transactions, and local journal data however MAG1, MAG2 and MAG3 will replicate master data and transactions directly to and from EEE.

=== Update tills to replicate directly with EEE ===
MAG1 as the existing store server does not need to be reconfigured.

On MAG2 and MAG3
* Close EEPOS
* Open an Administrator command prompt.
* Change to the EEPOS installation folder (e.g. C:\Program Files (x86)\Magenta Retail\EEPOS)
* Run the command
EEE_POS.exe /c MAG1\magentapos EEPOS Y
* Start EEPOS and ensure the POS Service indicator light is green

== Scenario 4 – All tills replicate from a store server ==
MAG1 will still be classified as the store server and MAG2 and MAG3 will replicate master data and transactions from MAG1

=== Update tills to replicate from the store server ===
MAG1 as the existing store server does not need to be reconfigured.

On MAG2 and MAG3
* Close EEPOS
* Open an Administrator command prompt.
* Change to the EEPOS installation folder (e.g. C:\Program Files (x86)\Magenta Retail\EEPOS)
* Run the command
EEE_POS.exe /c MAG1\magentapos EEPOS N
* Start EEPOS and ensure the POS Service indicator light is green

Change EEPOS Machine Role

2024-02-08T01:51:38Z

Jake: Created page with "== Overview == The role of a EEPOS installation can be changed using the command line. This means that a store can be reconfigured without needing to reinstall EEPOS. The..."

Network Testing

2019-03-21T02:27:36Z

Jake: Created page with "= .Net Remoting Port Testing = The below steps can be used to troubleshoot remoting connectivity problems. You can check if a port is open and accessible from Windows powersh..."

= .Net Remoting Port Testing =

The below steps can be used to troubleshoot remoting connectivity problems.

You can check if a port is open and accessible from Windows powershell (at least on Windows 10). Windows 7 you may need to use Telnet client or curl. tnc should work in Powershell on modern WinServer machines too.

In Windows 10: This is an example of a successful test: The EEPOS Service (OR SOMETHING) is running, listening on port 8080 and server BH is reachable.

[[File:PortSuccess.png]]

Now the firewall port has been closed to block incoming connections to port 8080:

[[File:PortFailed.png]]

If it fails, possible reasons are:

1. Connection blocked by a firewall, internet security package (e.g. combined AV and firewall etc)

2. POS Service not running

3. POS Service not listening on the port you think it is (check POS settings):

[[File:EEPOSPortConfig.png]]

4. Another problem on the clients network?

You can determine if it is (1) vs 2, 3, or 4 by repeating the tnc test on the store server itself. If the tnc test succeeds when run locally on the store server but fails when run remotely, then it is a network or firewall issue.

When running locally, make sure it runs against the LAN/WAN IP address and not LOCALHOST or 127.0.0.1. Best to use ipconfig to obtain the local machine's network IP address and test that explicitly:

'''tnc 192.168.2.53 -port 8080.'''

Also check that the till is correctly represented in the EEE database in ReplicationClientLogins:

'''select * from ReplicationClientLogins where TillCode = '078201''''

[[File:ReplicationClientLogins.png]]

Make sure the HostName and Port are correct. Use the hostname exactly as it appears in ReplicationClientLogins in the tnc test:

[[File:PortTest2.png]]

Another possibility is something else running on the machine using port 8080. If this is the case, reconfigure the pos service to use a different port. Note that port 8080 is sometimes used for http proxies.
You can try moving the PosService to a different port and test again.

You can use netstat -a -b to check what is running on port 80 (and what IP address(es) it is bound to). If netstat output is too fast to read, redirect it to a file and review later. netstat -a -b > ns.txt. Note netstat can take a minute or two to complete - be patient!

This is the expected netstat output bound to my LAN ip address:

TCP 192.168.2.53:8080 bh:0 LISTENING [PosService.exe]

File:PortTest2.png

2019-03-21T02:19:05Z

Jake: PortTest2

PortTest2

File:ReplicationClientLogins.png

2019-03-21T02:17:22Z

Jake: ReplicationClientLogins

ReplicationClientLogins

File:EEPOSPortConfig.png

2019-03-21T02:12:06Z

Jake: EEPOS Port Config

EEPOS Port Config

File:PortFailed.png

2019-03-21T02:08:07Z

Jake: Port Test Failed

Port Test Failed

File:PortSuccess.png

2019-03-21T02:03:22Z

Jake: Successful Test

Successful Test

EEPOS:Database Suspect

2017-03-27T00:52:27Z

Jake: /* Repairing Suspect Database */

== Suspect EEPOS Database Recovery ==

It is possible for a database to become ‘Suspect’ for many reasons, such as:
* There was an unexpected SQL Server Shutdown, power failure or a hardware failure.

* The database could have become corrupted.

* The database cannot be opened due to inaccessible files or insufficient memory or disk space.

* The database files are being held by operating system, third party backup software etc.

The below instructions show how to recover a Suspect database.

=== Stop EEPOS Service ===

EEPOS and the POS Service need to be closed before performing the steps to resolve the suspect database.

1. Close EEPOS.

2. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

3. Stop the '''EEPOS Service – MAGENTAPOS''' service.

=== Backup EEPOS Database Files ===

Perform a backup of the EEPOS Database files.

1. Browse to '''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''
2. Make a copy of the '''EEPOSdat.mdf''' and '''EEPOSlog.ldf''' files.

'''Note:''' If a prompt appears saying that the files are currently in use you will need to temporarily stop the SQL Service.

3. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

4. Stop the '''SQL Server (Magentapos)''' service.

5. Attempt to copy the '''EEPOSdat.mdf''' and '''EEPOSlog.ldf''' files again.

6. Start the '''SQL Server (Magentapos)''' service again.

=== Connect to Magentapos SQL Instance ===

Open SQL Management Studio on your EEE Server. Then connect to the tills local SQL Database over the network using the below details.

'''Server Name''' – Hostname\magentapos

'''Example:''' If hostname of machine is Server40, then Server name should be Server40\magentapos

'''Authentication''' – SQL Server Authentication

'''Login''' – Magentasupport

'''Password''' – Please contact Magenta Support for the SQL Database Password.

[[File:SSMSLogin.jpg]]

=== Repairing Suspect Database ===

Once connected to the Tills SQL Database, follow the below steps to check and repair and corrupt data on the EEPOS Database.

1. Begin a new query by selecting '''New Query (CTRL+N)'''.

2. Copy the below SQL command into the new query window.
<pre>
EXEC sp_resetstatus EEPOS;
ALTER DATABASE EEPOS SET EMERGENCY
DBCC checkdb(EEPOS)
ALTER DATABASE EEPOS SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (EEPOS, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE EEPOS SET MULTI_USER
</pre>

3. Select '''Execute (F5)''' to run the command.

This command should bring the database out of suspect mode and repair any corrupt data if possible.

4. Once completed, the EEPOS database should no longer be marked as suspect and should be accessible.

5. Remove the previous command and copy in the below command.

This command will replicate all data from EEE down to the till again.

<pre>EXEC usp_ReplicateMasterTablesLoop 1,10000</pre>

Note: It may take some time to complete this command as the EEPOS database is replicating all data from EEE over the network again.

6. Remove the previous command and copy the below command.

<pre>USE EEPOS
EXEC usp_ReplicateUpstreamData</pre>

If the above command fails, this indicates that the EEPOS database was unable to send its data up to the store server or EEE Server.
Please contact Magenta Support if this occurs.

Once replication is complete the EEPOS Database should now be repaired and ready for use again.

=== Testing ===

Perform the below steps to ensure EEPOS is working correctly.

1. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

2. Start the '''EEPOS Service – MAGENTAPOS''' service.

3. Open EEPOS and check that you can search for products (F4.

4. Search for a customer (F12).

Once EEPOS is running again, we recommend reviewing the SQL Server logs to check for what caused the database to become suspect, to ensure the problem does not re-occur.

The SQL Server logs can be found under -
'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\Log'''

EEPOS:Connect To Remote SQL Server

2017-03-17T03:00:34Z

Jake: Created page with "== Unable to Connect to Remote Database == This error indicates that a network problem is preventing the EEPOS database from communicating with the store server or vice versa. ..."

== Unable to Connect to Remote Database ==

This error indicates that a network problem is preventing the EEPOS database from communicating with the store server or vice versa.

If the affected machine is a store server, this indicates it cannot communicate with the EEE SQL Server.

Please see the below instructions which cover possible causes and solutions for this problem.

=== Troubleshooting ===

* Try restarting the machine. Sometimes a simple restart can resolve network connectivity problems

* Using Command Prompt, attempt to ping to the store server using the store server’s hostname.

From the store server machine, attempt to ping with the till’s hostname also.

If the ping fails this indicates network connectivity problems. Please see the below possible fixes.

'''Note:''' If the affected machine is a store server, you will need to ping to the EEE SQL Server and attempt to ping from the EEE SQL Server back to the Store Server.

* On the store server right-click on the network icon on the task bar and select '''Open Network and Sharing Center'''.

Check whether the machine is set to a Domain network or private/public/work network group.

The till should have the same network configuration setup.

The computer should be restarted if changes are made to this configuration.

* Check that the firewall on the store server and till allows the below inbound ports.
** SQL Server – TCP Port 1433
** SQL Server – TCP Port 1434
** MSDTC Port – TCP 135
** MSDTC Port – TCP 137

* Ensure that any antivirus on the machine has exceptions added for the below folders and applications.
** '''Folder Exception''' - C:\Program Files (x86)\Magenta Retail\EEPOS
** '''EEPOS Service Exception''' - C:\Program Files (x86)\Magenta Retail\EEPOS\PosService.exe

* Check Microsoft Distributed Transaction Coordinator (MSDTC) is configured correctly.
** From the start menu select Control Panel → Administrative Tools → Component Services. Then select My Computer → Distributed Transaction Coordinator. Right-click Local DTC then select the Security tab on the Local DTC Properties window.
** The security settings should match the below screenshot.

[[File:DTCSettings.jpg]]

* Check that SQL TCP/IP is enabled on the till and store server.
** From the start menu browse to '''All Programs → Microsoft SQL Server 2012 → Configuration Tools → SQL Server Configuration Manager'''.
** Expand '''SQL Server Network Configuration''' then highlight '''Protocols for MAGENTAPOS'''.
** Check that '''TCP/IP''' is enabled.

[[File:TCPIP.jpg]]

* Check that SQL Native Client hasn’t become corrupted. This can occur due to failed\interrupted windows updates.
** Create a new empty text file anywhere on the machine and rename it to test.udl
[[File:TestUDL.jpg]]
* Double click the new test.udl shortcut.
** In the Data Link Properties window, select the Provider tab and select SQL Server Native Client 11.0 then select Next
[[File:Datalink.jpg]]

If you receive the below error when selecting Next, this indicates a problem in SQL Native Client.

If this error occurs, perform a '''Repair''' installation of SQL Native Client from '''Control Panel → Programs and Features'''

[[File:DatalinkError.jpg]]

* If the machine is still unable to communicate with the store server\EEE please contact Magenta Support for additional assistance.

File:DatalinkError.jpg

2017-03-17T02:56:32Z

Jake:

File:Datalink.jpg

2017-03-17T02:54:49Z

Jake:

File:TestUDL.jpg

2017-03-17T02:51:16Z

Jake:

File:TCPIP.jpg

2017-03-17T02:50:00Z

Jake:

File:DTCSettings.jpg

2017-03-17T02:47:48Z

Jake:

EEPOS:Database Suspect

2017-03-17T02:32:28Z

Jake: Created page with "== Suspect EEPOS Database Recovery == It is possible for a database to become ‘Suspect’ for many reasons, such as: * There was an unexpected SQL Server Shutdown, power fail..."

== Suspect EEPOS Database Recovery ==

It is possible for a database to become ‘Suspect’ for many reasons, such as:
* There was an unexpected SQL Server Shutdown, power failure or a hardware failure.

* The database could have become corrupted.

* The database cannot be opened due to inaccessible files or insufficient memory or disk space.

* The database files are being held by operating system, third party backup software etc.

The below instructions show how to recover a Suspect database.

=== Stop EEPOS Service ===

EEPOS and the POS Service need to be closed before performing the steps to resolve the suspect database.

1. Close EEPOS.

2. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

3. Stop the '''EEPOS Service – MAGENTAPOS''' service.

=== Backup EEPOS Database Files ===

Perform a backup of the EEPOS Database files.

1. Browse to '''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''
2. Make a copy of the '''EEPOSdat.mdf''' and '''EEPOSlog.ldf''' files.

'''Note:''' If a prompt appears saying that the files are currently in use you will need to temporarily stop the SQL Service.

3. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

4. Stop the '''SQL Server (Magentapos)''' service.

5. Attempt to copy the '''EEPOSdat.mdf''' and '''EEPOSlog.ldf''' files again.

6. Start the '''SQL Server (Magentapos)''' service again.

=== Connect to Magentapos SQL Instance ===

Open SQL Management Studio on your EEE Server. Then connect to the tills local SQL Database over the network using the below details.

'''Server Name''' – Hostname\magentapos

'''Example:''' If hostname of machine is Server40, then Server name should be Server40\magentapos

'''Authentication''' – SQL Server Authentication

'''Login''' – Magentasupport

'''Password''' – Please contact Magenta Support for the SQL Database Password.

[[File:SSMSLogin.jpg]]

=== Repairing Suspect Database ===

Once connected to the Tills SQL Database, follow the below steps to check and repair and corrupt data on the EEPOS Database.

1. Begin a new query by selecting '''New Query (CTRL+N)'''.

2. Copy the below SQL command into the new query window.
<pre>
EXEC sp_resetstatus EEPOS;
ALTER DATABASE EEPOS SET EMERGENCY
DBCC checkdb(EEPOS)
ALTER DATABASE EEPOS SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DBCC CheckDB (EEPOS, REPAIR_ALLOW_DATA_LOSS)
ALTER DATABASE EEPOS SET MULTI_USER
</pre>

3. Select '''Execute (F5)''' to run the command.

This command should bring the database out of suspect mode and repair any corrupt data if possible.

4. Once completed, the EEPOS database should no longer be marked as suspect and should be accessible.

5. Remove the previous command and copy in the below command.

This command will replicate all data from EEE down to the till again.

<pre>EXEC usp_ReplicateMasterTablesLoop 1,10000</pre>

Note: It may take some time to complete this command as the EEPOS database is replicating all data from EEE over the network again.

Once replication is complete the EEPOS Database should now be repaired and ready for use again.

=== Testing ===

Perform the below steps to ensure EEPOS is working correctly.

1. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

2. Start the '''EEPOS Service – MAGENTAPOS''' service.

3. Open EEPOS and check that you can search for products (F4.

4. Search for a customer (F12).

Once EEPOS is running again, we recommend reviewing the SQL Server logs to check for what caused the database to become suspect, to ensure the problem does not re-occur.

The SQL Server logs can be found under -
'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\Log'''

EEPOS:System Database Recovery with No Backup

2017-03-15T04:27:18Z

Jake: /* Rebuild System Databases */

== System Database Recovery Methods ==

The below instructions show how to recover the EEPOS System databases from a backup and how to rebuild the system databases if no backup exists.

== Review SQL and Event Logs ==
Before commencing, the SQL error log and Event Viewer logs should be reviewed as these may indicate the original cause of the database problems.
Any problems indicated in these logs should be resolved before proceeding with the below steps.

'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\Log'''

'''Control Panel → Administrative Tools → Event Viewer'''

== Restore With System Database Backups ==

Ensure EEPOS is closed before performing the below steps.

1. Browse to '''C:\Program Files (x86)\Magenta Retail\EEPOS\Support\SystemDBFiles'''

'''Note:''' If the machine is using 32bit Windows, browse to - C:\Program Files (x86)\Magenta Retail\EEPOS\Support\SystemDBFiles

2. Check that the system database backups exist.

These files are named with a date stamp and the database name at the end (eg: 20170125.EEPOS, 20170125.master, 20170125.model and 20170125.msdb)

'''Note:''' If the above files do not exist, please follow the Restore Without System Database Backups instructions further below.

3. Once the backups are confirmed to exist, open '''Command Prompt''' as '''Administrator''' (Right click command prompt → Run as administrator)

4. Execute the below command to change the directory

<pre>CD C:\Program Files (x86)\Magenta Retail\EEPOS\</pre>

'''Note:''' If the machine is using 32bit Windows, use the below command.

<pre>CD C:\Program Files\Magenta Retail\EEPOS\</pre>

5. Execute the below command to Recover the System Database Backups.

<pre>SysDbRecovery.cmd RECOVER</pre>

6. The SystemDbRecovery should detect the system backup files.
Press any key to begin the restore.

[[File:SystemDBRecovery.jpg|SystemDBRecovery]]

This process may take over 10 minutes to recover the system databases. Once completed it should display as per the below screenshot.
Once complete please perform the tests shown at the end of this document.

[[File:SystemDBRecoveryComplete.jpg|SystemDBRecoveryComplete]]

== Restore Without System Database Backups ==

The below instructions show how to recreate the system databases when there is no existing backups.

=== Backup Database Files ===

Before proceeding with the below instructions a backup of the SQL Database files should be performed.

1. Browse to '''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''

2. Copy of '''ALL''' files in this folder to a backup folder.

'''Note:''' If a prompt appears saying that the files are currently in use you will need to temporarily stop the SQL Service using the below steps

3. Open the Windows Services screen (Control Panel → Administrative Tools → Services)

4. Stop the SQL Server (Magentapos) service.

5. Attempt to copy the files again.

6. Start the SQL Server (Magentapos) service again.

----

=== Stop EEPOS Service ===

EEPOS and the POS Service need to be closed before performing the steps to rebuild the system database.

1. Close EEPOS.

2. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

3. Stop the '''EEPOS Service – MAGENTAPOS''' service.

----

=== Rebuild System Databases ===

1. Open '''Command Prompt''' as '''Administrator'''.

2. Change the Command Prompt directory to the SQL Installation folder using the below command.

<pre>CD C:\Program Files\Microsoft Sql Server\110\Setup Bootstrap\SqlServer2012\</pre>

3. Execute the below command to re-build the system databases

<pre>
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MAGENTAPOS /SQLSYSADMINACCOUNTS=Administrator /SAPWD=tempSAPwd /SQLCOLLATION=Latin1_General_CI_AS</pre>

'''IMPORTANT:'''

* SQLCOLLATION needs to match the collation of EEE and other tills, e.g. Latin1_General_CI_AS.
You can find the collation by opening SQL Management Studio on your EEE Server, then right click the server and select Properties
If you are unsure what collation you should use, please contact Magenta Support for assistance.

'''NOTES:'''

* Sys Admin account needs to be an account currently logged in so that access to the EEPOS database can be achieved.

* Ensure SA password is provided. This SA user will need to be used later to connect to the instance.

This process can take some time to complete, there is no indication of progress and it will go back to command prompt when done.

----

=== MSDB and Model databases ===
Copy back any database files (e.g. MSDBdata.mdf, tempdb.mdf, modellog.ldf etc) that you did not need rebuilt (from your backups). You may need to turn off the “SQL Server (MAGENTAPOS)” service to allow access to the files again. Please ensure the service is restarted after this is completed.

The system database files are located in the below folder.
'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''

----

=== Re-attach EEPOS Database ===

Due to EEPOS using a FileStream for image resources, FileStream access needs to be set against the database before re-attaching the EEPOS database.
1. Open a new '''Command Prompt''' window as '''Administrator.'''

2. Run the below command to connect to the Magenta SQL Instance

<pre>SQLCMD –S .\MAGENTAPOS –U SA</pre>

3. When prompted for a password enter '''tempSAPwd''' as the password. Please note that the password is case sensitive.

4. Execute the below commands
'''Note:''' You will need to run each command separately in Command Prompt

<pre>EXEC sp_configure filestream_access_level, 1
GO
RECONFIGURE
GO</pre>

[[File:FileStreamAccess.jpg|FileStreamAccess]]

5. The EEPOS Database can now be re-attached using the below command.

<pre>EXEC sp_attach_db @dbname='EEPOS', @filename1=’C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA\EEPOSdat.mdf', @filename2=’C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA\EEPOSlog.ldf'
GO</pre>

[[File:ReAttachDB.jpg|ReAttachDB]]

----

=== Re-create Logins, Linked Servers and Synonyms ===

Please contact Magenta Support to re-create the SQL users, linked server connections and Synonyms.

----

=== Testing ===

Start the '''EEPOS Service – MAGENTAPOS''' service and review the log to ensure it starts up correctly and there are no errors.

The Service log can be found under - '''C:\ProgramData\MagentaPOS\c-program files (x86)-magenta retail-eepos\PosServiceLog.txt'''

1. Open EEPOS and ensure there are no errors on start up, then test the following:

2. Create a transaction, ensure the transaction is replicated to the EEE Server.

In EEE browse to '''Analysis → Queries → Journal''' to check that the transaction appears.

3. Perform return of the same transaction, this tests communication with EEE, broker queue in EEPOS database and replication of HOS records to EEE.

4. Review journals (either Journal search from the main menu or from Reprint, Control + R), this tests stored server linked server connection.

5. Search for a customer. This can be done by pressing F12 to bring up the customer search screen.

EEPOS:Database Not Online and Multi-User

2017-03-09T05:40:52Z

Jake: Created page with "== Database Offline or in Single-User Mode == The database may be put into ‘offline’ or single user mode due to a failed\interrupted windows update or unexpected shutdown. ..."

== Database Offline or in Single-User Mode ==

The database may be put into ‘offline’ or single user mode due to a failed\interrupted windows update or unexpected shutdown.

Perform the below steps to mark the database as online or to mark the database as multi-user.

== Bring EEPOS Database Online ==

=== Stop EEPOS Service ===

EEPOS and the POS Service need to be closed before performing the steps to bring the database online or set to multi-user.

1. Close EEPOS.

2. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

3. Stop the '''EEPOS Service – MAGENTAPOS''' service.

=== Backup EEPOS Database Files ===

Perform a backup of the EEPOS Database files.

1. Browse to '''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''

2. Make a copy of the '''EEPOSdat.mdf''' and '''EEPOSlog.ldf''' files.

'''Note:''' If a prompt appears saying that the files are currently in use you will need to temporarily stop the SQL Service.

3. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

4. Stop the '''SQL Server (Magentapos)''' service.

5. Attempt to copy the '''EEPOSdat.mdf''' and '''EEPOSlog.ldf''' files again.

6. Start the '''SQL Server (Magentapos)''' service again.

=== Connect to Magentapos SQL Instance ===

Open SQL Management Studio on your EEE Server. Then connect to the tills local SQL Database over the network using the below details.

'''Server Name''' – Hostname\magentapos
'''Example:''' If hostname of till is Server40, then Server name should be Server40\magentapos

'''Authentication''' – SQL Server Authentication

'''Login''' – Magentasupport

'''Password''' – Please contact Magenta Support for the SQL Database Password.

[[File:SSMSLogin.jpg]]

=== Bringing Database Online ===
Once connected to the till’s Magentapos SQL Instance you will notice that the EEPOS database is shown as offline as per the screenshot below.

[[File:EEPOSOffline.jpg]]

Follow the below steps to bring the database back online.

1. Begin a new query by selecting '''New Query (CTRL+N)'''.

2. Copy the below SQL command into the new query window.

<pre>ALTER DATABASE EEPOS SET ONLINE</pre>

3. Select '''Execute (F5)''' to run the command.

4. Once this command has been run, select refresh in the Object Explorer (Red square below).
The EEPOS database should show as online.

[[File:EEPOSOnline.jpg]]

== Set Database Multi-User ==
If your database was diagnosed as being in Single-User mode, please follow the steps below.

=== Stop EEPOS Service ===

EEPOS and the POS Service need to be closed before performing the steps to bring the database online or set to multi-user.

1. Close EEPOS.

2. Open the Windows Services screen (Control Panel → Administrative Tools → Services)

3. Stop the EEPOS Service – MAGENTAPOS service.

=== Set Database as Multi-User ===

1. Connect to the SQL Instance using the above [http://theoracle.magentaretail.com.au/index.php?title=EEPOS:Database_Not_Online_and_Multi-User&action=submit#Connect_to_Magentapos_SQL_Instance Connect to Magentapos SQL Instance] instructions.

2. Begin a new query by selecting '''New Query (CTRL+N)'''.

3. Copy the below SQL command into the new query window.
<pre>
USE master
ALTER DATABASE EEPOS
SET MULTI_USER;
GO</pre>

4. Select '''Execute (F5)''' to run the command.

5. Once completed the results windows should show '''Command(s) completed successfully''' message as per the below screenshot.

[[File:CommandComplete.jpg]]

If the command fails to complete, please contact Magenta Support for additional assistance.

File:CommandComplete.jpg

2017-03-09T05:34:07Z

Jake:

File:EEPOSOnline.jpg

2017-03-09T05:31:42Z

Jake:

File:EEPOSOffline.jpg

2017-03-09T05:30:00Z

Jake:

File:SSMSLogin.jpg

2017-03-09T05:28:20Z

Jake:

File:SSMS.jpg

2017-03-09T05:27:31Z

Jake: uploaded a new version of "File:SSMS.jpg"

File:SSMS.jpg

2017-03-09T05:23:33Z

Jake:

EEPOS:System Database Recovery with No Backup

2017-03-08T23:29:16Z

Jake: /* Review SQL and Event Logs */

== System Database Recovery Methods ==

The below instructions show how to recover the EEPOS System databases from a backup and how to rebuild the system databases if no backup exists.

== Review SQL and Event Logs ==
Before commencing, the SQL error log and Event Viewer logs should be reviewed as these may indicate the original cause of the database problems.
Any problems indicated in these logs should be resolved before proceeding with the below steps.

'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\Log'''

'''Control Panel → Administrative Tools → Event Viewer'''

== Restore With System Database Backups ==

Ensure EEPOS is closed before performing the below steps.

1. Browse to '''C:\Program Files (x86)\Magenta Retail\EEPOS\Support\SystemDBFiles'''

'''Note:''' If the machine is using 32bit Windows, browse to - C:\Program Files (x86)\Magenta Retail\EEPOS\Support\SystemDBFiles

2. Check that the system database backups exist.

These files are named with a date stamp and the database name at the end (eg: 20170125.EEPOS, 20170125.master, 20170125.model and 20170125.msdb)

'''Note:''' If the above files do not exist, please follow the Restore Without System Database Backups instructions further below.

3. Once the backups are confirmed to exist, open '''Command Prompt''' as '''Administrator''' (Right click command prompt → Run as administrator)

4. Execute the below command to change the directory

<pre>CD C:\Program Files (x86)\Magenta Retail\EEPOS\</pre>

'''Note:''' If the machine is using 32bit Windows, use the below command.

<pre>CD C:\Program Files\Magenta Retail\EEPOS\</pre>

5. Execute the below command to Recover the System Database Backups.

<pre>SysDbRecovery.cmd RECOVER</pre>

6. The SystemDbRecovery should detect the system backup files.
Press any key to begin the restore.

[[File:SystemDBRecovery.jpg|SystemDBRecovery]]

This process may take over 10 minutes to recover the system databases. Once completed it should display as per the below screenshot.
Once complete please perform the tests shown at the end of this document.

[[File:SystemDBRecoveryComplete.jpg|SystemDBRecoveryComplete]]

== Restore Without System Database Backups ==

The below instructions show how to recreate the system databases when there is no existing backups.

=== Backup Database Files ===

Before proceeding with the below instructions a backup of the SQL Database files should be performed.

1. Browse to '''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''

2. Copy of '''ALL''' files in this folder to a backup folder.

'''Note:''' If a prompt appears saying that the files are currently in use you will need to temporarily stop the SQL Service using the below steps

3. Open the Windows Services screen (Control Panel → Administrative Tools → Services)

4. Stop the SQL Server (Magentapos) service.

5. Attempt to copy the files again.

6. Start the SQL Server (Magentapos) service again.

----

=== Stop EEPOS Service ===

EEPOS and the POS Service need to be closed before performing the steps to rebuild the system database.

1. Close EEPOS.

2. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

3. Stop the '''EEPOS Service – MAGENTAPOS''' service.

----

=== Rebuild System Databases ===

1. Open '''Command Prompt''' as '''Administrator'''.

2. Change the Command Prompt directory to the SQL Installation folder using the below command.

<pre>CD C:\Program Files\Microsoft Sql Server\110\Setup Bootstrap\SqlServer2012\</pre>

3. Execute the below command to re-build the system databases

<pre>
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MAGENTAPOS /SQLSYSADMINACCOUNTS=Administrator /SAPWD=tempSAPwd /SQLCOLLATION=Latin1_General_CP1_CI_AS</pre>

'''IMPORTANT:'''

* SQLCOLLATION needs to match the collation of EEE and other tills, e.g. Latin1_General_CP1_CI_AS.
You can find the collation by opening SQL Management Studio on your EEE Server, then right click the server and select Properties
If you are unsure what collation you should use, please contact Magenta Support for assistance.

'''NOTES:'''

* Sys Admin account needs to be an account currently logged in so that access to the EEPOS database can be achieved.

* Ensure SA password is provided. This SA user will need to be used later to connect to the instance.

This process can take some time to complete, there is no indication of progress and it will go back to command prompt when done.

----

=== MSDB and Model databases ===
Copy back any database files (e.g. MSDBdata.mdf, tempdb.mdf, modellog.ldf etc) that you did not need rebuilt (from your backups). You may need to turn off the “SQL Server (MAGENTAPOS)” service to allow access to the files again. Please ensure the service is restarted after this is completed.

The system database files are located in the below folder.
'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''

----

=== Re-attach EEPOS Database ===

Due to EEPOS using a FileStream for image resources, FileStream access needs to be set against the database before re-attaching the EEPOS database.
1. Open a new '''Command Prompt''' window as '''Administrator.'''

2. Run the below command to connect to the Magenta SQL Instance

<pre>SQLCMD –S .\MAGENTAPOS –U SA</pre>

3. When prompted for a password enter '''tempSAPwd''' as the password. Please note that the password is case sensitive.

4. Execute the below commands
'''Note:''' You will need to run each command separately in Command Prompt

<pre>EXEC sp_configure filestream_access_level, 1
GO
RECONFIGURE
GO</pre>

[[File:FileStreamAccess.jpg|FileStreamAccess]]

5. The EEPOS Database can now be re-attached using the below command.

<pre>EXEC sp_attach_db @dbname='EEPOS', @filename1=’C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA\EEPOSdat.mdf', @filename2=’C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA\EEPOSlog.ldf'
GO</pre>

[[File:ReAttachDB.jpg|ReAttachDB]]

----

=== Re-create Logins, Linked Servers and Synonyms ===

Please contact Magenta Support to re-create the SQL users, linked server connections and Synonyms.

----

=== Testing ===

Start the '''EEPOS Service – MAGENTAPOS''' service and review the log to ensure it starts up correctly and there are no errors.

The Service log can be found under - '''C:\ProgramData\MagentaPOS\c-program files (x86)-magenta retail-eepos\PosServiceLog.txt'''

1. Open EEPOS and ensure there are no errors on start up, then test the following:

2. Create a transaction, ensure the transaction is replicated to the EEE Server.

In EEE browse to '''Analysis → Queries → Journal''' to check that the transaction appears.

3. Perform return of the same transaction, this tests communication with EEE, broker queue in EEPOS database and replication of HOS records to EEE.

4. Review journals (either Journal search from the main menu or from Reprint, Control + R), this tests stored server linked server connection.

5. Search for a customer. This can be done by pressing F12 to bring up the customer search screen.

EEPOS:System Database Recovery with No Backup

2017-03-08T23:28:38Z

Jake: Created page with "== System Database Recovery Methods == The below instructions show how to recover the EEPOS System databases from a backup and how to rebuild the system databases if no backup e..."

== System Database Recovery Methods ==

The below instructions show how to recover the EEPOS System databases from a backup and how to rebuild the system databases if no backup exists.

== Review SQL and Event Logs ==
Before commencing, the SQL error log and Event Viewer logs should be reviewed as these may indicate the original cause of the database problems.
Any problems indicated in these logs should be resolved before proceeding with the below steps.

'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\Log'''

'''(Control Panel → Administrative Tools → Event Viewer)'''

== Restore With System Database Backups ==

Ensure EEPOS is closed before performing the below steps.

1. Browse to '''C:\Program Files (x86)\Magenta Retail\EEPOS\Support\SystemDBFiles'''

'''Note:''' If the machine is using 32bit Windows, browse to - C:\Program Files (x86)\Magenta Retail\EEPOS\Support\SystemDBFiles

2. Check that the system database backups exist.

These files are named with a date stamp and the database name at the end (eg: 20170125.EEPOS, 20170125.master, 20170125.model and 20170125.msdb)

'''Note:''' If the above files do not exist, please follow the Restore Without System Database Backups instructions further below.

3. Once the backups are confirmed to exist, open '''Command Prompt''' as '''Administrator''' (Right click command prompt → Run as administrator)

4. Execute the below command to change the directory

<pre>CD C:\Program Files (x86)\Magenta Retail\EEPOS\</pre>

'''Note:''' If the machine is using 32bit Windows, use the below command.

<pre>CD C:\Program Files\Magenta Retail\EEPOS\</pre>

5. Execute the below command to Recover the System Database Backups.

<pre>SysDbRecovery.cmd RECOVER</pre>

6. The SystemDbRecovery should detect the system backup files.
Press any key to begin the restore.

[[File:SystemDBRecovery.jpg|SystemDBRecovery]]

This process may take over 10 minutes to recover the system databases. Once completed it should display as per the below screenshot.
Once complete please perform the tests shown at the end of this document.

[[File:SystemDBRecoveryComplete.jpg|SystemDBRecoveryComplete]]

== Restore Without System Database Backups ==

The below instructions show how to recreate the system databases when there is no existing backups.

=== Backup Database Files ===

Before proceeding with the below instructions a backup of the SQL Database files should be performed.

1. Browse to '''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''

2. Copy of '''ALL''' files in this folder to a backup folder.

'''Note:''' If a prompt appears saying that the files are currently in use you will need to temporarily stop the SQL Service using the below steps

3. Open the Windows Services screen (Control Panel → Administrative Tools → Services)

4. Stop the SQL Server (Magentapos) service.

5. Attempt to copy the files again.

6. Start the SQL Server (Magentapos) service again.

----

=== Stop EEPOS Service ===

EEPOS and the POS Service need to be closed before performing the steps to rebuild the system database.

1. Close EEPOS.

2. Open the Windows Services screen '''(Control Panel → Administrative Tools → Services)'''

3. Stop the '''EEPOS Service – MAGENTAPOS''' service.

----

=== Rebuild System Databases ===

1. Open '''Command Prompt''' as '''Administrator'''.

2. Change the Command Prompt directory to the SQL Installation folder using the below command.

<pre>CD C:\Program Files\Microsoft Sql Server\110\Setup Bootstrap\SqlServer2012\</pre>

3. Execute the below command to re-build the system databases

<pre>
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MAGENTAPOS /SQLSYSADMINACCOUNTS=Administrator /SAPWD=tempSAPwd /SQLCOLLATION=Latin1_General_CP1_CI_AS</pre>

'''IMPORTANT:'''

* SQLCOLLATION needs to match the collation of EEE and other tills, e.g. Latin1_General_CP1_CI_AS.
You can find the collation by opening SQL Management Studio on your EEE Server, then right click the server and select Properties
If you are unsure what collation you should use, please contact Magenta Support for assistance.

'''NOTES:'''

* Sys Admin account needs to be an account currently logged in so that access to the EEPOS database can be achieved.

* Ensure SA password is provided. This SA user will need to be used later to connect to the instance.

This process can take some time to complete, there is no indication of progress and it will go back to command prompt when done.

----

=== MSDB and Model databases ===
Copy back any database files (e.g. MSDBdata.mdf, tempdb.mdf, modellog.ldf etc) that you did not need rebuilt (from your backups). You may need to turn off the “SQL Server (MAGENTAPOS)” service to allow access to the files again. Please ensure the service is restarted after this is completed.

The system database files are located in the below folder.
'''C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA'''

----

=== Re-attach EEPOS Database ===

Due to EEPOS using a FileStream for image resources, FileStream access needs to be set against the database before re-attaching the EEPOS database.
1. Open a new '''Command Prompt''' window as '''Administrator.'''

2. Run the below command to connect to the Magenta SQL Instance

<pre>SQLCMD –S .\MAGENTAPOS –U SA</pre>

3. When prompted for a password enter '''tempSAPwd''' as the password. Please note that the password is case sensitive.

4. Execute the below commands
'''Note:''' You will need to run each command separately in Command Prompt

<pre>EXEC sp_configure filestream_access_level, 1
GO
RECONFIGURE
GO</pre>

[[File:FileStreamAccess.jpg|FileStreamAccess]]

5. The EEPOS Database can now be re-attached using the below command.

<pre>EXEC sp_attach_db @dbname='EEPOS', @filename1=’C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA\EEPOSdat.mdf', @filename2=’C:\Program Files\Microsoft SQL Server\MSSQL11.MAGENTAPOS\MSSQL\DATA\EEPOSlog.ldf'
GO</pre>

[[File:ReAttachDB.jpg|ReAttachDB]]

----

=== Re-create Logins, Linked Servers and Synonyms ===

Please contact Magenta Support to re-create the SQL users, linked server connections and Synonyms.

----

=== Testing ===

Start the '''EEPOS Service – MAGENTAPOS''' service and review the log to ensure it starts up correctly and there are no errors.

The Service log can be found under - '''C:\ProgramData\MagentaPOS\c-program files (x86)-magenta retail-eepos\PosServiceLog.txt'''

1. Open EEPOS and ensure there are no errors on start up, then test the following:

2. Create a transaction, ensure the transaction is replicated to the EEE Server.

In EEE browse to '''Analysis → Queries → Journal''' to check that the transaction appears.

3. Perform return of the same transaction, this tests communication with EEE, broker queue in EEPOS database and replication of HOS records to EEE.

4. Review journals (either Journal search from the main menu or from Reprint, Control + R), this tests stored server linked server connection.

5. Search for a customer. This can be done by pressing F12 to bring up the customer search screen.

File:ReAttachDB.jpg

2017-03-08T23:02:40Z

Jake:

File:FileStreamAccess.jpg

2017-03-08T23:02:31Z

Jake:

File:SystemDBRecoveryComplete.jpg

2017-03-08T22:58:47Z

Jake:

File:SystemDBRecovery.jpg

2017-03-08T22:56:46Z

Jake: