EnablerWiki - User contributions [en]

EEE Installation - Domain User accounts

2019-09-16T03:13:52Z

Luke:

Created: 31 May 2010. Last Reviewed: September 2019

'''EEE Installation – Domain Accounts'''

When installing EEE in a domain environment using domain accounts, and the account being used to perform the installation does not have Domain Administration rights, then the user accounts and settings need to be manually created before performing the EEE Installation.

'''Domain Groups'''

The following Domain Groups need to be created exactly as shown below:-

* EEE Users
* EEE Admins
* POS Users

'''Domain Users'''

The following Domain Users need to be created as shown below. When assigning passwords, it is recommended that the password is difficult to guess:-

EEEServices

* Name is guide only; similar name can be used
* Password never expires
* User cannot change password
* Logon as a service right (SeServiceLogonRight)
* Debug programs right (SeDebugPrivilege)
* Interactive logon right (SeInteractiveLogonRight)
* Domain Users Group member
* EEE Users group member

EEEServicesSA

* Name is guide only; similar name can be used
* Password never expires
* User cannot change password
* Logon as a service right (SeServiceLogonRight)
* Interactive logon right (SeInteractiveLogonRight)
* Domain Users Group member
* EEE Users group member
* EEE Admins group member

SQLServer (optional)

* Password never expires
* User cannot change password
* Logon as a service right
* Domain Users group member

''This account only required if SQL Server hasn't already been installed.''

EEE Installation - Domain User accounts

2019-09-16T03:13:09Z

Luke:

Created: 31 May 2010. Last Reviewed: September 2019

'''EEE Installation – Domain Accounts'''

When installing EEE in a domain environment using domain accounts, and the account being used to perform the installation does not have Domain Administration rights, then the user accounts and settings need to be manually created before performing the EEE Installation.

'''Domain Groups'''

The following Domain Groups need to be created exactly as shown below:-

* EEE Users
* EEE Admins
* POS Users

'''Domain Users'''

The following Domain Users need to be created as shown below. When assigning passwords, it is recommended that the password is difficult to guess:-

EEEServices

* Name is guide only; similar name can be used
* Password never expires
* User cannot change password
* Logon as a service right (SeServiceLogonRight)
* Debug programs right (SeDebugPrivilege)
* Interactive logon right (SeInteractiveLogonRight)
* Domain Users Group member
* EEE Users group member

EEEServicesSA
* Name is guide only; similar name can be used
* Password never expires
* User cannot change password
* Logon as a service right (SeServiceLogonRight)
* Interactive logon right (SeInteractiveLogonRight)
* Domain Users Group member
* EEE Users group member
* EEE Admins group member

SQLServer (optional)
* Password never expires
* User cannot change password
* Logon as a service right
* Domain Users group member

''This account only required if SQL Server hasn't already been installed.''

EEE Installation - Domain User accounts

2019-09-16T03:08:57Z

Luke:

Created: 31 May 2010. Last Reviewed: 14 January 2011

'''EEE Installation – Domain Accounts'''

When installing EEE in a domain environment using domain accounts, and the account being used to perform the installation does not have Domain Administration rights, then the user accounts and settings need to be manually created before performing the EEE Installation.

'''Domain Groups'''

The following Domain Groups need to be created exactly as shown below:-

* EEE Users
* EEE Admins
* POS Users

'''Domain Users'''

The following Domain Users need to be created as shown below. When assigning passwords, it is recommended that the password is difficult to guess:-

* EEEServices
- Password never expires
- User cannot change password
- Logon as a service right
- Inspect programs right
- Interactive logon right
- Domain Users Group member
- EEE Users group member
- IIS_WPG Group member (this is a local group on the server where the EEE web application is installed.)

* EEEServicesSA- Password never expires- User cannot change password- Interactive logon right- Domain Users group member- EEE Users group member- EEE Admins group member- IIS_WPG Group member (this is a local group on the server where the EEE web application is installed.)
* SQLServer- Password never expires- User cannot change password- Logon as a service right- Domain Users group member

''This account only required if SQL Server hasn't already been installed.''

Where to find the Generic Host Masterfile and Generic Host Log documents

2019-07-30T00:15:07Z

Luke:

Created: 13 July 2009. Last Reviewed: 14 January 2011

As each new version of Enabler is released, updated documentation is also made available for that version. Apart from the client notes for each version, the other documents you are likely to want to download are:-

* Generic Host Master File Maintenance Formats
* Generic Host Log File Format

These documents provide details on all master file maintenance that can be imported into Enabler, and data that is exported from Enabler for import to a host system.

These documents (together with many other documents) can be found at the following location:-

[https://magentaretail.com.au/downloads/ https://magentaretail.com.au/downloads/]

Database errors

2019-07-30T00:13:34Z

Luke:

Created: 24 November 2008. Last Reviewed: 24 April 2009

Database errors in Enabler, although not common, can occur for a variety of reasons. Below are some sample errors with suggested resolutions. With all database errors, unless you are 100% sure of the method for fixing the problem, it is strongly recommended that you contact Magenta Retail for assistance before proceeding.

= Database Error – Read Failure =
[[Image:Database_errors_Figure_1.jpg]]

Need to determine whether the database (.dbf) or the index (.mdx) is corrupt:

# Close all Enabler applications including Nibbler
# Delete the index relating to the error. In the above sample this is c:\enabler\local\posdiv.mdx.
# Re-index the database that experienced the error. In the above sample this is c:\enabler\local\posdiv.dbf so the reindex command would be c:\enabler>'''infoctrl indexlocal posdiv''')
# Start POS again.
# If Database error re-occurs then most likely the .dbf is corrupt.
# If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file. If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.

= Required Database Missing =
While a missing index can often be corrected by Enabler automatically reindexing the database for the missing index, which re-creates the index, a missing database file cannot be repaired automatically in most cases.

[[Image:Database_errors_Figure_2.jpg]]

To determine the best course of action, refer to the suggestions below.

* If the database is in the LOCAL folder, refer to “Enabler Database Files – LOCAL” for information about replacing or recovering the file.
* If the database is in the LANTRAN folder, refer to “Enabler Database Files – LANTRAN” for information about replacing or recovering the file.
* If the database is in the LANMNT folder, refer to “Enabler Database Files – LANMNT” for information about replacing or recovering the file. If unsure, please contact Magenta Retail for further advice.

= Unknown fieldname =
An unknown fieldname error message indicates an incompatibility between the database structures and the fields that Enabler is expecting to see in the database. This could occur if problems happened with an Enabler upgrade, or if a file was replaced from a different version of Enabler.

[[Image:Database_errors_Figure_3.jpg]]

The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.

If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-

Infoctrl migrate

which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.

= Number is out of range =
A “Number is out of range” message will likely have a similar cause to the “Unknown Fieldname” message, and can often occur immediately after the “Unknown Fieldname” error.

[[Image:Database_errors_Figure_4.jpg]]

The first check to be done is to ensure every till in the store is on the same version of Enabler. They aren’t then all tills should be upgraded to the same version. The store server must ALWAYS be on the same or a higher version of Enabler as the tills.

If all tills are on the same version, in most cases the error can be fixed by performing a migrate. The command for this would be:-

Infoctrl migrate

which needs to be run from a command prompt in the folder where Enabler is installed, which in the above example would be c:\enabler. Ensure that all Enabler applications are closed before running this command.

= See Also =
[[Enabler_Database_Files_-_LANMNT]]

[[Enabler_Database_Files_-_LANTRAN]]

[[Enabler_Database_Files_-_LOCAL]]

[[Anti-virus_software|Anti Virus Software]]

EEE Monitoring

2019-07-30T00:12:13Z

Luke:

Created: 28 September 2007. Last Reviewed: 27 January 2009

'''EEE Monitoring2'''

== EEE Monitoring ==
=== Overview ===
The intention of the EEE monitoring is to ensure that all transactions occurring in stores are correctly processed in EEE with no errors, and also to provide an alert of problems that may have occurred. EEE monitoring is an ongoing function that should be performed each day to ensure any problems that occur are not compounded by a lack of immediate action.

'''If you are performing your own EEE Monitoring, it is essential that these procedures be followed to ensure your EEE environment contains accurate data. Failure to perform the monitoring procedures could leave you in a situation where your EEE data is not correct or a hardware/software failure occurs and you are unable to recover your data!'''

All the examples shown in this document relate to SQL Server 2005.

The alerts and weekly reports can be automatically emailed to one or more email addresses, and it is recommended that a minimum of 2 email addresses are alerted to provide coverage in the event of staff being absent.

Alert email addresses need to be configured in both EEE and SQL Server.

''EEE''

The email addresses can be configured from within EEE from the Utilities->Company Preferences menu as shown below.

[[Image:EEE_Monitoring_Figure1.JPG]]

''SQL Server''

For each EEE database in your SQL Server, you will have a EEE operator, as shown on the screen below

[[Image:EEE_Monitoring_Figure2.JPG]]

To change the email address for the EEE Operators, highlight the operator (in the example above it is EEE_Operator), and then click on Properties. You will see a screen similar to the one below.

[[Image:EEE_Monitoring_Figure3.JPG]]

You can change email addresses by adjusting the E-Mail name field as shown above. Email addresses should be separated by a semi colon (;).

The main components providing the EEE Monitoring function are:-

* Weekly reports. These reports provide various statistics on the EEE environment.
* EEE Error logs. Whenever more than 10 errors are logged in the EEE errorlog, and alert email will be generated which will include a file detailing all the errors that have occurred. These should be attended to immediately.
* EEE Data Loader. Various circumstances can cause the EEE dataloader to suspend processing, and when this occurs an email alert is generated.
* Disk space Alerts. EEE can be configured to generate email alerts when the free space on nominated disk drives falls below a specified level.
* Unacknowledged Data threshold. – When data has been exported to stores and EEE hasn’t received an acknowledgement for that data within 7 days, an alert email is generated.

=== Data Loader errors ===
Probably the most important area of EEE Monitoring is checking the EEE Error log for any records that have been rejected by EEE. Failure to monitor the EEE Error Log and fix any rejected records will lead to inaccurate data in EEE, resulting in incorrect sales information, etc.

'''''It is most important that the EEE Error Log is monitored on a regular basis.'''''

The EEE Web application is used to access the EEE Error Logs. They can be found from Utilities->Data Interchange Management->Data Loader Error Log and also Utilities->Data Interchange Management->Data Loader Activity Log, as shown below.

[[Image:EEE_Monitoring_Figure4.JPG]]

==== Data Loader Activity Log ====
The Data Loader Activity Log shows the details of every file processed by Data Loader. The defaults for this screen are shown below. You can also filter the activity log so that only files containing errors are shown.

[[Image:EEE_Monitoring_Figure5.JPG]]

A record that has a Y in the “Contains errors” column allows you to drill through to the error log records associated with the activity record.

==== Data Loader Error Log ====
There are many types of data loader errors that can appear in the error log. It is not possible to discuss resolutions for all error types, so the most common errors have been addressed below.

'''It is extremely important that errorlog records are investigated ASAP. If the problem can’t be resolved, it should be referred to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for assistance in resolving the problem.'''

''Timeout Expired''

The example below shows a number of timeout errors. These can occur when the SQL Server is very busy with other tasks such as running queries etc, and the timeout period for a transaction to occur is exceeded, so the transaction is aborted and the details of the record being inserted is added to the EEE errorlog table. To fix these types of errors you simple need to reprocess the records.

* Click on the 1st record to be re-processed. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen. In the example below, the ID number is 26539.
* Replace the number in the To ID box with the record ID number of the last record to be re-processed. In the example below, type 26553
* Click on the REPROCESS button in the bottom right corner of the screen. A file will be created containing all these records in the Reprocess sub-folder of the data loader import folder (something like d:\eeedata\import\reprocess.
* The records written to the reprocess file will then be flagged in the errorlog table as re-processed

[[Image:EEE_Monitoring_Figure7.JPG]]

* After the reprocess button is clicked, and the errorlog records updated, the above records will be removed from the screen as shown below.

[[Image:EEE_Monitoring_Figure8.JPG]]

''Transaction Deadlocked''

Deadlocked transactions occur when an attempt is made to update the same record by 2 or more SQL processes as the same time. One of the updates will be selected as the deadlocked record, and the record will be written to the errorlog.

Deadlocked transactions should be reprocessed as with timed out records above.

[[Image:EEE_Monitoring_Figure9.JPG]]

''Foreign Key Constraint errors''

Foreign Key constraint errors occur when a record contains key values such as product code, customer code, branch code, etc, that do not exist in EEE. Under normal circumstances, these shouldn’t occur so further investigation is required. Some instances that may cause these errors include:-

* Product code created in EEE and then deleted after it had been exported to stores. The store performs a transaction with that product code before it received the deletion.
* Customer code is missing. Customer was created in Enabler, but a communications failure prevented the file containing the new customer being correctly sent to Head Office. The customer then makes a purchase in the store and that transaction is sent to Head Office causing a Foreign Key error as the customer is not in EEE.

The screen below is an example of a number of Foreign Key Constraint error records.

[[Image:EEE_Monitoring_Figure10.JPG]]

If you click on an error record so it is highlighted, and then click on the DETAIL button, you are given further information on the error as shown below.

[[Image:EEE_Monitoring_Figure11.JPG]]

In the example above, you can see that the record hasn’t been processed because of a conflict in the productcode column of the Product table. This means that the product code in this record (93281355156943) is not in the product table.

This may have occurred because the product code was created in store instead of in EEE or the code may have been created in EEE and then deleted, and the deletion hasn’t been sent to the store as yet.

This record could be processed by replacing the invalid product code with the correct product code.

* ESC from the above screen, and then click on EDIT.
* You are then shown the original record, with the highlighted area of the screen to make any changes as shown below.
* Replace the product code with the correct code and then click Resubmit.
* The record is then re-processed and removed from the error log screen.

[[Image:EEE_Monitoring_Figure12.JPG]]

''Primary Key Constraint errors''

Primary Key constraint errors occur because the data that is being inserted violates a primary key setting for the table. Primary key violations stop duplicate data being processed by EEE, and also prevent duplicate items such as duplicate gift voucher numbers being entered.

In the example below, a gift voucher transaction has generated a Primary Key violation

[[Image:EEE_Monitoring_Figure13.JPG]]

Clicking on the Detail button gives the information about the error as shown below. This indicates that EEE cannot insert a duplicate key (voucher number) in the Voucher table

[[Image:EEE_Monitoring_Figure14.JPG]]

The above situation can occur if Enabler is configured to issue manual gift voucher numbers and the same number is issued twice. A common scenario for this is the store redeems part of a gift voucher, and issues a gift voucher as change, but they reissue the same gift voucher number.

The Primary Key violation example below relates to duplicate transactions being rejected by EEE. If you look at the Error Record column on the right hand side, you will see the transactions occurred on 20/02/2007 but the Date column indicates that these errors were generated on 5/03/2007. These types of primary key errors generally indicate that something unusual such as database corruption, has occurred in Enabler on the store computer.

Primary Keys prevent the same record being processed more than once. As an example, on the Saleline table, primary keys exist on the fields saledate, saleline, reference2, and kititemnumber. As Enabler can’t generate duplicate combinations of these fields in one transaction, if a combination of these fields already exists in EEE, this will be a duplicate record and EEE will not process the duplicate record and will insert the record in the errorlog table.

[[Image:EEE_Monitoring_Figure15.JPG]]

With the above error records, you should first attempt to send acknowledgements back to the store which will hopefully stop these records being resent by Enabler. If the same records appear in the errorlog a few days later, you will need to contact Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for further assistance.

To acknowledge these records, do the following.

* Click on the 1st record to be acknowledged. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen.
* Replace the number in the To ID box with the record ID number of the last record to be acknowledged. Use the arrows to move between screens if there is more than one screen of errors.
* Click on the ACKNOWLEDGE button. Acknowledgement files are then created for sending back to the stores. Acknowledgement records when processed by Enabler, indicate that the record has been processed by EEE, so doesn’t need to be sent again by Enabler. After these records have been acknowledged, you need to flag them as ignored so they don’t appear in the errorlog.
* Click on the 1st record to be ignored. The record ID number will be populated in the From ID and To Id fields towards the bottom of the screen.
* Replace the number in the To ID box with the record ID number of the last record to be ignored. Use the arrows to move between screens if there is more than one screen of errors.
* Click on the IGNORE button. The records will all be flagged as ignored and not shown on the errorlog screen.

=== Weekly emails ===
Each week, a scheduled task is run that produces a number of reports. These reports are emailed to the configured email addresses. The subject of these emails is “SQL Server Report”, and they will usually contain a zip file called WeeklyReportFiles.zip. Contained in this zip file will be:-

* dbcc_out.txt
* dbmaint.txt
* errorlog.txt
* mag_erlg.dat
* sqlbackup.txt

The text of the email will look like:-

The email should contain the

drive sizes,

database sizes and

the latest errorlog.

companyname

<nowiki>--------------------------------------------------</nowiki>

Your Company - New Zealand

(1 rows affected)

The contents of each file is explained below.

==== dbcc_out.txt ====
This document is usually very large and contains information about performing an indexdefrag on all table indexes in EEE. This report is mainly for informational purposes only.

NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037

2 0 0 Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0%

NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037

Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0%

NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037

301 159 135 Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0%

NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037

Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0%

NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037

Pages Scanned Pages Moved Pages Removed Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0%

NBSQLSVR usp_dbm_dbINDEXDEFRAG Style 2007-09-03 01:00:25.037

-------------------- -------------------- -------------------- Executing DBCC INDEXDEFRAG (eee,Style.idxModDate,2) - fragmentation currently 57%, Avg Page Density currently 0%

==== dbmaint.txt ====
This report provides information about the free space on all drives on the SQL Server, information about the file that each database/log uses, together with growth statistics, and also the total size and free space in each database and transaction log. This document is extremely useful for monitoring the changing size of your database and log files, and should be examined each month.

drive MB free

<nowiki>----- ----------- </nowiki>

C 63036

D 2968

E 376335

(3 rows affected)

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Name Fileid Filename Filegroup Size Maxsize Growth Usage

<nowiki>------------------------------ ----------- --------------------------------------------------------------------------- ---------- ------------- ------------- ---------- ---------- </nowiki>

bedb_dat 1 C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf PRIMARY 9536 KB Unlimited 80 KB data only

bedb_log 2 C:\Program Files\Symantec\Backup Exec\Data\BEDB_Log.ldf NULL 1024 KB Unlimited 10% log only

EEEData1 1 e:\eeedata\hongkong\data\EEEData1.mdf PRIMARY 5120000 KB Unlimited 512000 KB data only

EEEData1 1 e:\eeedata\NewZealand\data\EEEData1.mdf PRIMARY 5120000 KB Unlimited 512000 KB data only

EEEData1 1 e:\eeedata\production\data\EEEData1.mdf PRIMARY 10238976 KB Unlimited 512000 KB data only

EEEData1 1 e:\eeedata\test\data\EEEData1.mdf PRIMARY 3072000 KB Unlimited 512000 KB data only

EEELog1 2 e:\eeedata\test\data\EEELog1.ldf NULL 1024000 KB 2147483648 KB 512000 KB log only

EEELog1 2 e:\eeedata\production\data\EEELog1.ldf NULL 5120000 KB 2147483648 KB 512000 KB log only

EEELog1 2 e:\eeedata\NewZealand\data\EEELog1.ldf NULL 1024000 KB 2147483648 KB 102400 KB log only

EEELog1 2 e:\eeedata\hongkong\data\EEELog1.ldf NULL 1126400 KB 2147483648 KB 102400 KB log only

master 1 E:\sqldata\MSSQL.1\MSSQL\DATA\master.mdf PRIMARY 4096 KB Unlimited 10% data only

mastlog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\mastlog.ldf NULL 1280 KB Unlimited 10% log only

modeldev 1 E:\sqldata\MSSQL.1\MSSQL\DATA\model.mdf PRIMARY 2240 KB Unlimited 1024 KB data only

modellog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\modellog.ldf NULL 26816 KB Unlimited 10% log only

MSDBData 1 E:\sqldata\MSSQL.1\MSSQL\DATA\MSDBData.mdf PRIMARY 83072 KB Unlimited 10% data only

MSDBLog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\MSDBLog.ldf NULL 35712 KB 2147483648 KB 10% log only

ReportServer 1 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServer.mdf PRIMARY 69824 KB Unlimited 1024 KB data only

ReportServer_log 2 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServer_log.LDF NULL 2624 KB 2147483648 KB 10% log only

ReportServerTempDB 1 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServerTempDB.mdf PRIMARY 11456 KB Unlimited 1024 KB data only

ReportServerTempDB_log 2 E:\sqldata\MSSQL.1\MSSQL\DATA\ReportServerTempDB_log.LDF NULL 3520 KB 2147483648 KB 10% log only

tempdev 1 E:\sqldata\MSSQL.1\MSSQL\DATA\tempdb.mdf PRIMARY 38208 KB Unlimited 10% data only

templog 2 E:\sqldata\MSSQL.1\MSSQL\DATA\templog.ldf NULL 15040 KB Unlimited 10% log only

LNm Tot Mb Used Mb Free MbData %Log DB Typ EntryDt

<nowiki>------------------------- --------------- --------------- ---------------- ------------------------- ----- ----------------------- </nowiki>

ReportServerTempDB 11.1875 1.6250 9.5625 ReportServerTempDB Data 2007-09-03 05:00:01.020

ReportServer 68.1875 68.0625 .1250 ReportServer Data 2007-09-03 05:00:01.020

EEEData1 5000.0000 15.4375 4984.5625 NewZealand Data 2007-09-03 05:00:01.020

MSDBData 81.1250 74.9375 6.1875 msdb Data 2007-09-03 05:00:01.020

master 4.0000 2.9375 1.0625 master Data 2007-09-03 05:00:01.003

EEEData1 5000.0000 225.8125 4774.1875 HongKong Data 2007-09-03 05:00:01.020

EEEData1 3000.0000 207.7500 2792.2500 eeetest Data 2007-09-03 05:00:01.020

EEEData1 9999.0000 381.7500 9617.2500 eee Data 2007-09-03 05:00:01.020

bedb_dat 9.3125 9.1875 .1250 BEDB Data 2007-09-03 05:00:01.020

ReportServerTempDB 3.4297 1.0366 69.7751 ReportServerTempDB Log 2007-09-03 05:00:01.003

ReportServer 2.5547 .9551 62.6147 ReportServer Log 2007-09-03 05:00:01.003

NewZealand 999.9922 30.7939 96.9206 NewZealand Log 2007-09-03 05:00:01.003

msdb 34.8672 7.0820 79.6886 msdb Log 2007-09-03 05:00:01.003

master 1.2422 .6094 50.9434 master Log 2007-09-03 05:00:01.003

HongKong 1099.9922 53.8052 95.1086 HongKong Log 2007-09-03 05:00:01.003

eeetest 999.9922 505.6001 49.4396 eeetest Log 2007-09-03 05:00:01.003

eee 4999.9922 27.6509 99.4470 eee Log 2007-09-03 05:00:01.003

BEDB .9922 .5776 41.7815 BEDB Log 2007-09-03 05:00:01.003

==== errorlog.txt ====
The errorlog.txt contains the latest SQL Server log. Each week when the weekly reports are run, a new SQL Server error log is started and the previous log is included in this email.

==== mag_erlg.dat ====
This document contains outstanding error log records for the past week, so since the last EEE Errorlog alert was generated. Records in this file should be attended to immediately. Refer the section on “Data Loader Errors” for more information.

Id !ErrDate !ErrSource !ErrDescription !ErrData1 !ErrData2 !ErrRecord !ErrReprocessCount!EditedRecord !ErrIgnored!ActivityNumber!AddDate

<nowiki>-----------!-----------------------!------------------------------------------------------------!--------------------------------------</nowiki>

26180!2007-06-27 23:13:39.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098481|00|20070627|5932","GL",19,"00",04,"20070627","11:20:58","6688","00000400014881",2,1,24.3,48.6,"9319868102841","8924B00","0009",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:13:40.233

26181!2007-06-27 23:14:24.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098483|00|20070627|5914","GL",20,"00",04,"20070627","11:20:58","6688","00000400014881",1,1,24.3,24.3,"9319868102858","8924B00","0010",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:14:24.293

26182!2007-06-27 23:15:55.000!Microsoft OLE DB Provider for SQL Server !Timeout expired !IDispatch error #3121 !GL !"09098597|00|20070627|5710","GL",1,"00",04,"20070627","13:07:02","6688","00000400014882",1,1,70,70,"93281355163283","6971B00","0011",10,"",1,"","N",0 ! 0!NULL ! 0! 47453!2007-06-27 23:15:55.077

==== sqlbackup.txt ====
This report provides a snapshot of the last database backup date for every database on your SQL Server. This report should be examined each week to make sure that your databases are being backed up regularly.

Databases and backups on server NBSQLSVR

Database Backup Date Comment

<nowiki>---------------------------------------- ------------- ------------------------------- </nowiki>

BEDB Sep 3 2007 Backup is current within a day

eee Sep 2 2007 Backup is current within a day

eee Sep 2 2007 Backup is current within a day

eeetest Sep 2 2007 Backup is current within a day

HongKong Sep 2 2007 Backup is current within a day

master Sep 3 2007 Backup is current within a day

model Sep 3 2007 Backup is current within a day

msdb Sep 3 2007 Backup is current within a day

NewZealand Sep 3 2007 Backup is current within a day

ReportServer Aug 31 2007 Backup is current within a week

ReportServerTempDB Aug 31 2007 Backup is current within a week

=== Alert emails ===
Alert emails are intended to assist you with monitoring your EEE environment. Do not rely on them as the only means of notifying you of problems. Various conditions external to EEE can prevent alert emails being delivered.

There are many circumstances that will cause EEE to generate an alert email. The most common have been explained in the section below. If you receive any other alerts, please advise Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) immediately so you can be advised of what action to take.

==== Disk Space Alerts ====
EEE has a scheduled task where you can configure alerts to be received when the disk space on nominated drives falls below a set threshold. This task is called Magenta DBM Monitor Disk Space and is scheduled to run via SQL Agent. By default, this job runs every hour, so if you receive a disk space alert email, the emails will continue every hour until the free disk space is above the specified threshold.

This scheduled task will look similar to the script below, with one line for each disk being monitored.

exec usp_dbm_diskspace_monitor @drivename = c, @spacelimit = 5000

exec usp_dbm_diskspace_monitor @drivename = d, @spacelimit = 15000

exec usp_dbm_diskspace_monitor @drivename = e, @spacelimit = 25000

''When an alert email is generated, the email will have the subject of:-''

SQL Server Job System: 'EEE_Magenta DBM Monitor Disk Space' completed on [//MACHINE \\MACHINE]

where [//machine \\machine] is the name of the computer the alert is for.

''The email will contain information similar to:-''

JOB RUN:'EEE_Magenta DBM Monitor Disk Space' was run on 6/09/2007 at 12:28:30 PM

DURATION:0 hours, 0 minutes, 0 seconds

STATUS: Failed

MESSAGES:The job failed. The Job was invoked by User MACHINE\Trevor. The last step to run was step 1 (step1).

To get further information on the failure, you need to go to Microsoft SQL Server Management Studio, and under SQL Agent, expand Jobs as shown below.

[[Image:EEE_Monitoring_Figure16.JPG]]

Right click on the Magenta DBM Monitor Disk Space job, and then select “View History”. You will see a screen similar to below.

[[Image:EEE_Monitoring_Figure17.JPG]]

To get further information on the failed job, click on the + beside the job with the [[Image:EEE_Monitoring_Figure18.JPG]] beside it. Click on the next line which will also have a [[Image:EEE_Monitoring_Figure18.JPG]] on it, and you will see a screen similar to below.

[[Image:EEE_Monitoring_Figure19.JPG]]

The screen above shows that C: drive is less than the specified limit of 13000MB, and the available space is 12634MB. This indicates that you need free space on C: drive so the available space is > the specified limit.

==== Data Loader Alerts ====
Whenever data loader encounters a situation that causes 50 errors within 5 seconds, a Data Loader alert email is generated with the subject of “Data Loader Error Count Exceeded”. This email will contain the following text.

Data Loader has exceeded 50 server errors within 5 seconds and it is suspending operations. Please review the Windows Application Event Log and take whatever steps are necessary to resolve the problem, then stop and restart the EEE Data Loader Service.

Data Loader will not process any data for any company/database until this problem has been resolved. Data flowing in from stores will be queued until Data Loader is restarted.

'''It is very important to realize that when you receive this email, if you take no action, then data loader will not process any further transactions into EEE!'''

Usually, when the above alert is received, the first action you should take is from the Services icon, in Administrative Tools, highlight the EEE Data Loader service and restart it. In the majority of cases this will fix the problem.

If data loader immediately generates another alert, then further investigation is usually required. To find the details of what is causing Data Loader to stop, go to the Windows Application Event Log where you will see a number of error messages relating to EEE Data Loader.

There can be many causes of these errors, so if you are unsure of what action to take, this should be escalated to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) as a matter of urgency.

==== EEE Error Log Alerts ====
When data loader inserts 10 or more records in the EEE errorlog table, an alert email is sent as a warning that this has occurred. The subject of the email will be:-

SQL Server Report for EEE Errorlog for ''Your Company''

and the email will have text of:-

Threshold for Errorlog reached. This email should contain the

the latest errorlog.

There have been 17 errors from limit of 10.

companyname

<nowiki>--------------------------------------------------</nowiki>

Your Company

(1 rows affected)

This email will also contain an attachment called “mag_erlg.dat” which is a text file containing all the errors. These errors need to be immediately investigated to determine the cause. The problem maybe as simple as time outs where you need to re-process the records, or there maybe more serious issues. For further information on the types of errors you may find, see the section titled “Data Loader Errors” earlier in this document.

==== EEE Export Maintenance Threshold Alerts ====
EEE Exporter is the program that extracts data from your EEE database and creates an isl-file.dat to be imported at each store. The EEE Exporter is usually configured to export new and unacknowledged data and unacknowledged data is resent if an acknowledgement hasn’t been received from the store within a predefined time period.

When exporter extracts each record to be exporter to stores, a record is created in the exportmaintenance table in EEE. When an isl-file.dat is processed in each store, an acknowledgement record is generated for each record processed, and this acknowledgment record then removes the corresponding record from the exportmaintenance table.

Exporting unacknowledged records involves resending all records from exportmaintenance that our outside the resend time period.

When records have been in exportmaintenance for more than 7 days, an export maintenance threshold email alert is generated.

This email will have a subject of:-

SQL Server Alert System: 'UnAcknowledged Data Exceeded Threshold' occurred on \\MACHINE

And will contain text of:-

DATE/TIME:30/08/2007 8:00:00 AM

DESCRIPTION:Error: 60005 Severity: 16 State: 1 Branch 203 has 41 unacknowledged maintenance records > 7 days old.

COMMENT:Please Investigate.

JOB RUN:(None)

In addition to the above information, all export maintenance threshold alerts are also written to the SQL log as shown below.

[[Image:EEE_Monitoring_Figure20.JPG]]

When these alerts occur, you need to determine why these alerts are being generated. Possible causes include:-

* Isl-file.zip (or isl-file.dat) is still in the stores export directory. Possible communications failure.
* Enabler is configured to only process import maintenance as a scheduled task, and Enabler is being shutdown at night preventing the Enabler scheduled tasks from running.
* Isl-file.zip’s are not configured to append the date to the name and are overwriting existing files in the store. Use EEE Enterprise Configurator to turn on option to “Append date to export filenames” as shown below.

[[Image:EEE_Monitoring_Figure21.JPG]]

* Error occurring during import of host maintenance preventing acknowledgement records being created. Investigate cause of error.
* Acknowledgement records being created by Enabler but not being sent to EEE. Possible communications problem or Enabler configuration issue.

While these errors persist, stores are most likely not receiving product maintenance, so these need to be investigate ASAP. If the reason cannot be determined, please forward details to Magenta Retail Support ([mailto:support@magentaretail.com.au support@magentaretail.com.au]) for further investigation.

==== Database Backup Alerts ====
EEE has scheduled tasks which are used to perform database and transaction log backups. The backups can be configured to run on a 2 day cycle or a 7 day cycle. When one of these backups fails, an alert email is generated with a subject similar to:-

SQL Server Job System: 'eeehk_MWFSDBBackup' completed on [//DELL-TT \\DELL-TT]

And containing text similar to what is shown below.

JOB RUN:'eeehk_MWFSDBBackup' was run on 6/09/2007 at 4:37:23 PM

DURATION:0 hours, 0 minutes, 3 seconds

STATUS: Failed

MESSAGES:The job failed. The Job was invoked by User DELL-TT\Trevor. The last step to run was step 1 (Step1_RunBackup).

The above information indicates that the backup has failed, but you need to look at the scheduled task within Microsoft SQL Server Management Studio, and under SQL Agent, expand Jobs as shown below.

[[Image:EEE_Monitoring_Figure22.JPG]]

Right click on the failed database backup job, and then select “View History”. You will see a screen similar to below.

[[Image:EEE_Monitoring_Figure23.JPG]]

To get further information on the failed job, click on the + beside the job with the [[Image:EEE_Monitoring_Figure18.JPG]] beside it. Click on the next line which will also have a [[Image:EEE_Monitoring_Figure18.JPG]] on it, and you will see a screen similar to below.

[[Image:EEE_Monitoring_Figure24.JPG]]

The message shown above will then assist you in determining why the backup failed. If you are backing up to a network location, a network error can result in a corrupt backup device. The easiest fix for a corrupt backup device is to delete the file MWFSDB.BAK or TTSDB.BAK, as these devices get re-created when the job is next run. If you have deleted a backup device, you should run another backup ASAP.

==== Log Backup Alerts ====
EEE has scheduled tasks which are used to perform database and transaction log backups. The backups can be configured to run on a 2 day cycle or a 7 day cycle. When one of these backups fails, an alert email is generated with a subject similar to:-

SQL Server Job System: 'eeehk_MWFSLogBackup' completed on [//DELL-TT \\DELL-TT]

And containing text similar to what is shown below.

JOB RUN:'eeehk_MWFSLogBackup' was run on 6/09/2007 at 4:52:02 PM

DURATION:0 hours, 0 minutes, 0 seconds

STATUS: Failed

MESSAGES:The job failed. The Job was invoked by User DELL-TT\Trevor. The last step to run was step 1 (Step1_RunBackup).

The procedure for investigating a log backup failure is the same as for a database backup failure detailed earlier.

Creating new stores with EEE

2019-07-30T00:07:20Z

Luke:

Created: 14 October 2009. Last Reviewed: 3 October 2014

== Process for creating new stores with EEE & Enabler ==

The following process should be followed when creating new stores when you are using both EEE and Enabler. This process doesn't include installing Enabler on the store computers and getting the store ready for trading. For information about Staging a new store, refer to the document “Staging and Support”.

The store should be initially created in EEE and then exported from EEE to Enabler HO. Once the store is in Enabler HO, you can then clone a Store Server and Tills from another store.

=====Add the new branch in EEE (with a EEE environment)=====
# From the EEE menu select Location Management
# From the Location menu select Branch and then click on ADD
# Type in the required details for the new branch. Items shown with a red * are mandatory fields. Ensure that the logical address you used when setting up the store in Enabler H/O, is entered in the Logical Address field on this screen, and the branch is setup in the same Region as was used in Enabler H/O. (If the store is not ready to go online, you must tick the option “Exclude this branch from data exports”)
# Click on Save to save the new branch.
# On save of a new branch a prompt to clone Prices, Costs, Purge Parameters, and Min/Max levels from another branch will occur.
#* If you don’t clone prices/costs etc from another store, then there will be no prices/costs available to export to a store until they have been entered. You have an option to SKIP this step and perform the cloning at a later stage.
Enter new branch code to “clone to branch” and enable the prices required and branch code that prices will be cloned from.

<nowiki>Set the last export date/time for master file exports. Data cannot be exported to a branch until the export date and time has been completed for that branch.</nowiki>

<nowiki>Set the Last Export Date/Time. Master file records will only be exported from this date onwards.</nowiki>

''Any records modified before this date will not be sent. (If you have a large product database, you can keep a master copy of the master file databases as at a certain date, and then only export records modified since that date. This will make processing the initial isl-file.dat much quicker. The master copy of the databases would be copied to the store machines when they are being set up).''

<nowiki>Leave Export Date/Time unchanged. This will result in all Master file records being exported to the branch.</nowiki>

=====Add the new branch in Enabler (no EEE environment)=====
# On the Enabler Head Office Server from Back Office select Global Setup
# Highlight region code and select Add for a new branch record
# Enter All Branch details required.
#* Branch code (can be either alpha or numerical or both)
#* Logical address is normally four digits made up of region code and branch code.
#* Ensure offline flag is set correctly. Once disabled maintenance files will be created for new branch.
# Select OK enter to save new branch records

=====Add the store server in Enabler=====
# On the Enabler Head Office Server from Back Office select Global Setup and highlight new branch. (If using EEE confirm new branch code has been added and flowed down to Enabler H/O . Can be manually exported from EEE using data exporter to send branch records but will usually flow down during scheduled export if H/O branch is included in exports from EEE)
# To add new server we always recommend cloning from an existing store so configurations are consistent. Need to first highlight an existing store server then click on the clone button (try to clone off a store server that has Enabler installed on the same drive as the new branch. Always clone a store server from a store server and a till (node) from another till (node)if possible)
# Drag and click clone arrow over the name of the Branch where you are adding the new store server
# Key in the branch code, press Tab then key in the 2 digit till number, key in the name/location of the till, press enter to save
# Highlight the new server on the left hand side then highlight System Parameters on left and click on config button to open screen
# Key in the new branch details, press enter to save
# Highlight the new server on the left hand side then expand Sales and highlight Docket Setup, click on config button to open screen then key in the correct header details, press enter to save
# Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight Communication click on config button to open screen. Replace the cloned machine name with the store servers machine name in the following fields:
#*Database server (UNC name) \\servername
#*Time Server (UNC name) \\servername
# If you have multiple tills and wish to backup your Enabler databases and configuration to another machine on the local network, follow this step. Highlight the new server on the left hand side then expand Transaction Processing / Comms, highlight, Backup Options Setup click on config button to open screen. Replace the backup path with the path to another machine on your local network or to a another drive letter , e.g.: ''\\tillname\en\enabler\backup or d:\backup''

=====Add tills (nodes) in Enabler=====
# On the Enabler Head Office Server from Back Office select Global Setup
# Highlight a till (node) in any existing branch then click on Clone (select a till where enabler is installed on same drive as new till)
# Drag and click clone arrow over the name of the Branch where you are adding the new till then key in the 2 digit till number, then key in the name/location of the till, press enter to save.
# Highlight the new branch on the left hand side
# Highlight the new branch on the left hand side then highlight System Parameters on left and click on config button to open screen. Select All to update till docket setup configurations with those already configured for the server.
# As above highlight branch and Expand Sales and highlight Docket Setup, click on config button to open screen, Select All to update till docket setup configurations with those of the server. press enter to save changes to till
# This screen requires access at till level so ensure the till is highlighted, expand Transaction Processing / Comms, and highlight Communication click on config button to open screen. Replace the machine name with the new store servers machine name in the following fields:
#* Database server (UNC name) \\servername
#* Time Server (UNC name) \\servername
#* Configuration Base directory \\servername\enserver\enabler\comms\config
# This screen requires access at till level so ensure the till is highlighted Highlight Database Setup click on config button to open screen then replace the machine name with the store servers machine name in the following fields:
#* Lan Transactions \\servername\enserver\enabler\lantran
#* Lan Master Files \\servername\enserver\enabler\local
#* Lan Maintenance files \\servername\enserver\enabler\lanmnt
# Select Transaction Processing / Comms, Version Control Setup then replace the machine name with the store servers machine name: Upgrade Package Path: ''\\servername\enserver\enabler\comms\upgpack'' (if the upgrade path refers to a central location rather than the store server, then leave this setting unchanged)

=====Export configuration=====
# On the Enabler Head Office Server from Back Office select Global Setup
# Always highlight the Store at Branch Name level for exporting of configuration
# Click on the Export button
# Enter in the export path name when prompted (folder needs to exist if exporting to a shared network path).
# A message ‘Destination path will be erased, ok to continue?” Press OK to allow enabler to export configuration to destination path.
# A message “Include Data common to all stores but maintained by EEE”. This will only display if configured with option “This store has a EEE H/O”, select NO to this option if EEE is in use.
# You should see a configuration successfully exported message when finished. If export was unsuccessful, ensure the destination path is accessible

=====Install & configure enabler=====
Latest Install and upgrade files are available on the magenta website page,
https://magentaretail.com.au/downloads/

If a specific version is required a request can be made to the magenta support desk.
# Run the Enabler Install executable on machine (install.exe), Enabler by default will be installed on C: drive option to change location and folder name is available. (ensure drive that enabler is installed on is same as the drive referred to in database setup configurations for till)

# Once install is complete run the manual upgrade command to upgrade till to the currently Enabler version H/O enabler is on. Stores can be on a previous version or the same but never a greater version to H/O Enabler (manual upgrade files need to be extracted to upgrade folder prior to running command refer to upgrade documentation for more help)
# From Start Menu right click Back Office icon and run as administrator
# Select the diskette option when prompted and enter path where configuration have been exported to from H/O enabler (import can be done form local folder , a USB memory stick or a network shared folder)
# Enter till number for till being configured.
# A valid license number is required to be entered in licence prompt after import of configurations to enable POS to run; a NEW license can be retrieved from the online licensing function.
https://licensing.magentaretail.com.au/weblic/
# Shut down Back Office and restart all enabler apps from start menu as administrator.
If configured as a store server Nibble.exe will attempt to create and write computer name to a file called workstation.dat in the configured import path. Failure to access this location or write to file because already exist with another compute name may result in nibble displaying red or presenting a warning that another server with same name exists.
If configured as a till (node) Nibble.exe will attempt to connect to store server over the LAN

=====Enabler Sharing=====
On store server the drive containing Enabler or the Enabler folder is shared as “enserver” depending on what level the databases communication paths are share name set in configurations.
Not mandatory but on the till (node) share the drive containing Enabler or the Enabler folder as ‘en’

=====Update the new store server with master files from EEE=====
# If EEE is in use the Data Exporter is used to send master files from EEE to Store (The store would be updated during the first comms session)
From the Enabler Enterprise Edition program group, select EEE Data Exporter
# Select the Company you wish to export master files for, and then select the Branch name to receive the master file. Branch will only be available to receive exported data, if the option “exclude this branch from data exports” is not ticked in EEE > Location >Branch Maintenance.
# Select Add All for all tables to be exported, highlight tables not required and double click or select Remove to exclude table from export.
# On the very first export for branch from the Export method, select Full Export and Generate Zap command for Enabler. This will export all records with a zap command so it clears tables at store and replaces with exported records.
# Click on EXPORT to commence exporting the selected files.
# Store server import path ends need to configure to same location exported file is sent to be able to import file. Standard path is \\ EEEservername\eeedata\export\%laddr
# A Full Masterfile load of new data imported on store server will be automatically sent to store till (node) as a masterfile load if till is configured to receive and is online at time store server imports the file. If till not configured until after import of masterfile a manual masterfile load from store server to till can be performed via Back Office > File Menu> Full Masterfile load

=====Update the new store server with master files from Enabler H/O (no EEE in Use)=====
# On the Enabler Head Office Server from Back Office go to the File Menu
# Select Full Branch load
# Select enter to open Full Branch option and again to accept warning to proceed.
# Enter or select branch code data is being exported to in Send to branches field.
# Select All for selection of all master file to send to store or highlight each masterfile required and double client or select add.
# Press OK enter to confirm export and sending of data to branch.
# A *.bld file will be created in the enabler\comms\tobr\<%laddr> folder and if nibbler is configured to copy data over network will retrieve file when access to location is available and rename file to *.zld and move to enabler\comms\fromho folder and import immediately.
# If till is configured to receive maintenance and is online at time store server imports the branch load file data will be automatically sent to till as a full load. If till is not configured until after import , a Full Masterfile load can be sent from store server to till when till is communicating with server via Back Office > File Menu> Full Masterfile load

=====Check that nibbler messages are getting from the tills to the server=====
(If store till (node) has been setup and configured to communicate with store server test communications is correctly configured)
# Start-up nibble.exe by right clicking icon in start menu and run as administrator
# Confirm nibble application has access to LAN error will display if LAN not accessible. Nibble will display as a yellow icon in taskbar tray
# On a till (node) go to the PoS main screen press <enter> to start a sale
# Key in 88888 as the user ID then press <enter>
# You should see a ‘Invalid User ID’ message
# Go to Back Office on the Store Server
# Select Reports then Event Log. You should see an invalid user ID event for the till (node) confirming communication is successful.

=====Add the printers (LPT)=====
# Select Start, Settings, Printers
# Select Add Printer
# Select Local Printer click on Next
# Highlight LPT1 click on Next
# Highlight Generic then Generic/Text Only click on Next
# Select Keep existing driver click on Next
# Select No click on Next
# Select Do not share this printer click on Next
# Select Yes to print a windows test page
# Select Next then Finish
# Open Back Office on till select Till setup, expand Equipment and highlight Receipt printer. Click on config to open configuration screen. Select default printer settings and then connect device to Generic /Test Only drivers.
# Any integrated EEE functions that need to access the store printer required the store receipt printer to be available on the network and have the required permissions set for User “ EEEservices. “
# Add A4 printer and set it as the default so enabler reports can display in correct format
# For report printing select Till setup, expand equipment and highlight Report Printers. Enable the “Is a report printer attached” option for Printer1, enter printer description and type of printer. Then click on connect device and select A4 printer driver installed. Do the same for Printer2 but as a receipt printer and connect to Generic Text/Only Drivers.

=====Add the printers (USB)=====
(Adding USB printer may differ for different models of printer so any issues please contact Magenta Support)
# Connect the printer to computer and allow the system to identify an install printer using printer manufacturer drivers
# Once printer is installed test perform a windows test print through printer properties
# Select Add Printer and use wizard to add new printer
# Select Local Printer click on Next
# Highlight LPT1 click on Next
# Highlight Generic then Generic/Text Only click on Next
# Select Keep existing driver click on Next
# Select No click on Next
# Select Do not share this printer click on Next
# Select NO to print a windows test page
# Select Next then Finish
# Go into printer properties and assign the USB port to printer drivers
# Perform a windows test print through printer properties.
# Open Back Office on till select Till setup, expand Equipment and highlight Receipt printer. Click on config to open configuration screen. Select default printer settings and then connect device to Generic /Test Only drivers.
# Any integrated EEE functions that need to access the store printer required the store receipt printer to be available on the network and have the required permissions set for User “ EEEservices. “
# Add A4 printer and set it as the default so enabler reports can display in correct format
# For report printing select Till setup, expand equipment and highlight Report Printers. Enable the “Is a report printer attached” option for Printer1, enter printer description and type of printer. Then click on connect device and select A4 printer driver installed. Do the same for Printer 2 but as a receipt printer and connect to Generic Text /Only Drivers .

=====Adjust a float amount=====
On each till from the PoS main screen, select Till Control, then Float Adjustment.

=====Program the scanners to read formats used by Enabler=====
Enabler uses Code39 and Interleave 2of5 formats. Barcode scanners will need to be configured to identify these codes. Once scanner has been configured, test scanning in POS to make sure the product barcodes and transaction barcodes printed on dockets scan in Enabler successfully.

=====Test the peripherals=====
Option to test hardware connected to POS is available from the POS main screen

Select ''File Menu > Peripherals Test Utility''

=====Add POS to startup=====
To ensure POS is automatically opened on till, add the winpos.exe and nibble.exe from \enabler folder into start up menu for user

=====Use Company logo in POS=====
Add the company logo *.bmp (bitmap) files to the \enabler folder (if configured to use non-standard bitmaps to display in POS screens).

BDE Conflicts

2019-07-30T00:01:21Z

Luke:

Created: 16 March 2009. Last Reviewed: 16 March 2009

Enabler uses a technology from Borland known as the Borland Database Engine, or BDE, to access its database files. The BDE is a common, shared program component which may be utilitised by other applications.

It is possible for the BDE to enter a temporary, unstable state. This may occur if one Enabler application terminates (or is terminated) abnormally, preventing it from properly disconnecting from the BDE. We have also observed upon rare occasions that third party applications that use the BDE may prevent Enabler from accessing the BDE. This has been observed in relation to a service known as “Insight Manager” which is part of a server monitoring toolset from HP.

=== Symptoms: ===
# Enabler applications already running may freeze and become totally unresponsive. Typically the application is consuming no CPU resource when viewed in Task Manager.
# Enabler applications may fail to load. Upon attempting to start an Enabler application, nothing appears to happen. In Task Manager the EXE can be seen in the process list. The application user interface is never displayed.
# In these cases, the BDE Administration Utility (BDEADMIN.EXE) is generally also unable to be loaded.

=== To Resolve This Issue: ===
# Forcibly close any Enabler applications from Task Manager process list:
## Press Shift+Ctrl+ESC to invoke Task Manager, or use Ctrl+ALT+DELETE and choose Start Task Manager.
## Locate NIBBLE.EXE, WINPOS.EXE and INFOCTRL.EXE. ''Hint: Click image name at the top of the list to sort alphabetically. ''
## For each the above processes found, click the image name in the process list then click End Process (and confirm when prompted).
## Double-check to ensure all the above processes have been removed from the process list.
## If any other processes are known to use the BDE, close those programs or forcibly terminate through Task Manager (forcibly terminate third party applications at your own risk!).
## Try starting Enabler applications as normal.
# If the problem is not resolved or if you have reason to suspect that some other application may be using the BDE:
## Obtain Process Explorer (PROCEXP.EXE) from Sys Internals [https://docs.microsoft.com/en-us/sysinternals/downloads/ https://docs.microsoft.com/en-us/sysinternals/downloads/].
## Run procexp.exe
## From the Find menu, choose “Find File Handle or DLL”
## At the “Handle or dll substring” prompt enter IDAPI32.DLL and click Search.
## If any process is using the BDE, it will be listed in the search results. The search may take a minute or two to complete.
## If any processes are shown, identify the application that owns the process and try to stop the application. Note – the BDE can also be used by Windows services. Note – the process that directly accesses the BDE might be a child process of the offending application. Check if the listed process(es) has a parent process.
## If necessary, you might have to forcibly terminate such processes. Do this at your own risk!
## Retry the Enabler applications.
## When third party applications are found to conflict with Enabler, you may need to contact Magenta to discuss your options.

= See Also: =
[http://theoracle.magentaretail.com.au/wiki/index.php/BDE_Versions BDE Versions].

BDE Conflicts

2019-07-30T00:01:00Z

Luke:

Created: 16 March 2009. Last Reviewed: 16 March 2009

Enabler uses a technology from Borland known as the Borland Database Engine, or BDE, to access its database files. The BDE is a common, shared program component which may be utilitised by other applications.

It is possible for the BDE to enter a temporary, unstable state. This may occur if one Enabler application terminates (or is terminated) abnormally, preventing it from properly disconnecting from the BDE. We have also observed upon rare occasions that third party applications that use the BDE may prevent Enabler from accessing the BDE. This has been observed in relation to a service known as “Insight Manager” which is part of a server monitoring toolset from HP.

=== Symptoms: ===
# Enabler applications already running may freeze and become totally unresponsive. Typically the application is consuming no CPU resource when viewed in Task Manager.
# Enabler applications may fail to load. Upon attempting to start an Enabler application, nothing appears to happen. In Task Manager the EXE can be seen in the process list. The application user interface is never displayed.
# In these cases, the BDE Administration Utility (BDEADMIN.EXE) is generally also unable to be loaded.

=== To Resolve This Issue: ===
# Forcibly close any Enabler applications from Task Manager process list:
## Press Shift+Ctrl+ESC to invoke Task Manager, or use Ctrl+ALT+DELETE and choose Start Task Manager.
## Locate NIBBLE.EXE, WINPOS.EXE and INFOCTRL.EXE. ''Hint: Click image name at the top of the list to sort alphabetically. ''
## For each the above processes found, click the image name in the process list then click End Process (and confirm when prompted).
## Double-check to ensure all the above processes have been removed from the process list.
## If any other processes are known to use the BDE, close those programs or forcibly terminate through Task Manager (forcibly terminate third party applications at your own risk!).
## Try starting Enabler applications as normal.
# If the problem is not resolved or if you have reason to suspect that some other application may be using the BDE:
## Obtain Process Explorer (PROCEXP.EXE) from Sys Internals ([https://docs.microsoft.com/en-us/sysinternals/downloads/ https://docs.microsoft.com/en-us/sysinternals/downloads/].
## Run procexp.exe
## From the Find menu, choose “Find File Handle or DLL”
## At the “Handle or dll substring” prompt enter IDAPI32.DLL and click Search.
## If any process is using the BDE, it will be listed in the search results. The search may take a minute or two to complete.
## If any processes are shown, identify the application that owns the process and try to stop the application. Note – the BDE can also be used by Windows services. Note – the process that directly accesses the BDE might be a child process of the offending application. Check if the listed process(es) has a parent process.
## If necessary, you might have to forcibly terminate such processes. Do this at your own risk!
## Retry the Enabler applications.
## When third party applications are found to conflict with Enabler, you may need to contact Magenta to discuss your options.

= See Also: =
[http://theoracle.magentaretail.com.au/wiki/index.php/BDE_Versions BDE Versions].

EEE WebService

2013-04-02T23:14:42Z

Luke:

Created: 05 July 2012. Last Reviewed: 06 August 2012

'''EEE WebService'''

EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.

Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au

Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities->Configuration->Configuration Settings->Licensed Plugins tab.

Magenta Retail provide EEE Web Service documentation which can be viewed from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]

or downloaded as a PDF from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]

Recommendations

* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegrationRecommendationDiagram.pdf Integration Recommendations]
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/WebServiceIntegratingGiftCards.pdf EEE Gift Card Integration Recommendations]
* [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EmailClickandOpenlinktracking.pdf EEE Email Click and Open link tracking Recommendations]

Example XML and XSD files can be downloaded using the links below

* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]

== See Also: ==

EEE WebService

2012-08-06T22:01:37Z

Luke:

Created: 05 July 2012. Last Reviewed: 06 August 2012

'''EEE WebService'''

EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.

Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au

Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities->Configuration->Configuration Settings->Licensed Plugins tab.

Magenta Retail provide EEE Web Service documentation which can be viewed from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.htm EEE Web Service Documentation]

or downloaded as a PDF from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]

Example XML and XSD files can be downloaded using the links below

* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]

== See Also: ==

EEE WebService

2012-08-06T21:53:53Z

Luke:

Created: 05 July 2012. Last Reviewed: 06 August 2012

'''EEE WebService'''

EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.

Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au

Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities->Configuration->Configuration Settings->Licensed Plugins tab.

Magenta Retail provide EEE Web Service documentation which can be viewed from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEEWebService.htm EEE Web Service Documentation]

or downloaded as a PDF from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]

Example XML and XSD files can be downloaded using the links below

* Sample XML files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/XmlSample.zip Please click here]
* Sample Xsd files [http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/Xsd.zip Please click here]

== See Also: ==

EEE WebService

2012-08-06T21:52:43Z

Luke:

Created: 05 July 2012. Last Reviewed: 06 August 2012

'''EEE WebService'''

EEE provides an interface to allow website developers to retrieve data from EEE for publishing on a website, and also allow changes recorded on a website to be updated back to EEE. This would allow actions such as a customer calling up their account on a website and updating their contact information. The changes made on the website would then flow back to EEE.

Before this interface can be used, a licensed plugin is required from Magenta Retail. Further information on obtaining this license can be obtained by contacting our helpdesk on support@magentaretail.com.au

Once you have obtained the license plugin, this license needs to be retrieved in EEE from Utilities->Configuration->Configuration Settings->Licensed Plugins tab.

Magenta Retail provide EEE Web Service documentation which can be viewed from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEEWebService.htm EEE Web Service Documentation]

or downloaded as a PDF from here:-

[http://theoracle.magentaretail.com.au/images/EEEWebServiceDocumentation/EEE_WebService.PDF EEE Web Service Documentation]

Example XML and XSD files can be downloaded from our FTP site using the links below

* Sample XML files [ftp://ftp.magentaretail.com.au/Documents/EEEWebService/XmlSample.zip Please click here]
* Sample Xsd files [ftp://ftp.magentaretail.com.au/Documents/EEEWebService/Xsd.zip Please click here]

== See Also: ==

EEE WebService

2012-08-06T21:51:10Z

Luke:

EEE WebService

2012-08-06T21:50:28Z

Luke:

EEE WebService

2012-08-06T21:49:49Z

Luke:

EEE WebService

2012-08-06T07:46:33Z

Luke: