Square for Retail has all the tools for smooth selling with a POS, online store, inventory. Cloud based and stand alone point of sale system for restaurant, salon, retail. CRM, Safe Sync 'Always On' mode, loyalty and gift card programs, robust reporting. By PC America. Learn more about Cash Register Express. Heartland pcAmerica believes a retailer should devote its time to customers, not to administrative tasks and tech support. Our Cash Register Express point of sale (POS) software streamlines your retail operation, automating many tasks, and gives you more time to focus on your customers — and to stand out from your competitors.
Cash Register Express/Restaurant Pro Express software connects to SQL server for database operations. While all stations may show evidence that SQL has been installed by default, only one station holds the store database and all other stations connect as clients. If that store server is not running, clients will not be able to connect.
Configuration:
IMPORTANT: CLIENT STATIONS MUST BE RUNNING THE SAME DATABASE VERSION OF CASH REGISTER EXPRESS AS THE SERVER STATION. FAILURE TO COMPLY MAY RESULT IN DATABASE CORRUPTION
I. Determine which Station is the “Server” (SQL Database Server):
A. All stations may have SQL Server installed and have the capacity of serving the database, but only on station contains the live database used by the business. This machine is the “Server”.
B. The Server is USUALLY the station labeled “Station 1”, “Server”, or “T1”
C. On this station, Navigate to File>Database Maintenance>View Database Settings.
D. Note the Server Name and Database Name.
E. The Server Name is the hostname of the computer that CRE is referencing for the database.
F. If the Server Name is “localhost”, CRE is looking to this machine to find the database.
G. If the Server name is not “localhost”, it should explicitly point to the hostname or IP address of one of the computers on the LAN
H. Search hostnames and IP addresses as required to determine which machine is the Server
1. In Windows, right click on My Computer to select ‘Properties’ and view the computer hostname.
2. Open a DOS shell (Windows Start>Run>CMD>OK) and key in the command “hostname”
3. Open a DOS shell (Windows Start>Run>CMD>OK) and key in the command “ipconfig”
I. Once the Server has been located, Open CRE navigate to File>Database Maintenance>Backup Database
J. Enter Password first, and then User ID
K. Create a database backup at C:Backup, before attempting to connect Client Stations. Include the date in the filename
L. At the main login screen, navigate to File>About and look for “CRE DB Version”. This is the MUST be the same on all stations in the LAN to avoid database corruption.
A. All stations may have SQL Server installed and have the capacity of serving the database, but only on station contains the live database used by the business. This machine is the “Server”.
B. The Server is USUALLY the station labeled “Station 1”, “Server”, or “T1”
C. On this station, Navigate to File>Database Maintenance>View Database Settings.
D. Note the Server Name and Database Name.
E. The Server Name is the hostname of the computer that CRE is referencing for the database.
F. If the Server Name is “localhost”, CRE is looking to this machine to find the database.
G. If the Server name is not “localhost”, it should explicitly point to the hostname or IP address of one of the computers on the LAN
H. Search hostnames and IP addresses as required to determine which machine is the Server
1. In Windows, right click on My Computer to select ‘Properties’ and view the computer hostname.
2. Open a DOS shell (Windows Start>Run>CMD>OK) and key in the command “hostname”
3. Open a DOS shell (Windows Start>Run>CMD>OK) and key in the command “ipconfig”
I. Once the Server has been located, Open CRE navigate to File>Database Maintenance>Backup Database
J. Enter Password first, and then User ID
K. Create a database backup at C:Backup, before attempting to connect Client Stations. Include the date in the filename
L. At the main login screen, navigate to File>About and look for “CRE DB Version”. This is the MUST be the same on all stations in the LAN to avoid database corruption.
II. Check CRE DB Version on Client Stations:
A. Open CRE/RPE on the Client Station.
B. Navigate to File>About and confirm that the Database Version is the same as the Server
C. IF THE DATABASE VERSION IS NOT THE SAME, THE STATION MUST BE PATCHED BEFORE DATABASE CONNECTION.
D. If CRE does not successfully open on the client station, the following procedure will allow CRE to connect temporarily on its local SQL Server to verify the CRE DB Version:
A. Open CRE/RPE on the Client Station.
B. Navigate to File>About and confirm that the Database Version is the same as the Server
C. IF THE DATABASE VERSION IS NOT THE SAME, THE STATION MUST BE PATCHED BEFORE DATABASE CONNECTION.
D. If CRE does not successfully open on the client station, the following procedure will allow CRE to connect temporarily on its local SQL Server to verify the CRE DB Version:
III. Temporarily Connect Client Station to its local SQL Server (skip this step if you have already identified the CRE DB Version)
A. Locate the db configuration file,C:Program FilesCRE.NETcresetup.pca
B. Rename file to cresetup.pca.old1
C. Open CRE
D. Click Next
E. Select Business Type and click Next
1. CRE – A Retail Store
2. RPE – A Quick Service Restaurant …
3. RPE (Alternate) – A Fine Dining Restaurant …
F. Check “Use Advanced Configuration” and click Next
G. Click “Change Local Database Info”
H. Server Name: localhost
I. Database Name: test
J. Instance Name: PCAMERICA
K. User Name: sa
L. Password: pcAmer1ca
M. Select MS SQL Radio Button
N. Click Done
O. Click Next
P. If prompted, select option to “Keep My Existing Database”
Q. Select “1001: …..” from left pane (Store ID)
R. Select “01” from the right pane (Station ID)
S. Click Done and Begin
T. If prompted to enter an Encryption Key, decline and disregard warning
U. Navigate to File>About and confirm that the Database Version is the same as the Server.
V. IF THE DATABASE VERSION IS NOT THE SAME, THE STATION MUST BE PATCHED BEFORE DATABASE CONNECTION.
A. Locate the db configuration file,C:Program FilesCRE.NETcresetup.pca
B. Rename file to cresetup.pca.old1
C. Open CRE
D. Click Next
E. Select Business Type and click Next
1. CRE – A Retail Store
2. RPE – A Quick Service Restaurant …
3. RPE (Alternate) – A Fine Dining Restaurant …
F. Check “Use Advanced Configuration” and click Next
G. Click “Change Local Database Info”
H. Server Name: localhost
I. Database Name: test
J. Instance Name: PCAMERICA
K. User Name: sa
L. Password: pcAmer1ca
M. Select MS SQL Radio Button
N. Click Done
O. Click Next
P. If prompted, select option to “Keep My Existing Database”
Q. Select “1001: …..” from left pane (Store ID)
R. Select “01” from the right pane (Station ID)
S. Click Done and Begin
T. If prompted to enter an Encryption Key, decline and disregard warning
U. Navigate to File>About and confirm that the Database Version is the same as the Server.
V. IF THE DATABASE VERSION IS NOT THE SAME, THE STATION MUST BE PATCHED BEFORE DATABASE CONNECTION.
IV. Connecting Client Stations to Server Database
A. Open CRE to the main login screen
B. Navigate to File>Select Database
C. Enter Admin Password:
1. “password” – POSNation Default
2. “admin” – If you had to connect CRE to its local SQL Server to verify the CRE DB Version
D. Check box to ‘Use Advanced Configuration’.
E. Click Next.
F. Click ‘Change Local Database Info’.
G. Input the following settings to connect to the server:
1. Server: Computer Name/Hostname of the database server station
2. Instance: PCAMERICA
3. Database Name: Name of database as viewed on the database server
4. User Name: sa
5. Password: pcAmeri1ca
6. Uncheck ‘Use Trusted Connection with Windows Authentication’ (never check)
7. Select the ‘MS SQL’ radio button.
H. Click Done.
I. Click Next.
J. Select ‘Keep My Existing Database’ (the other option deletes the existing database)
K. Select Store ID 1001 on the left column that appears.
L. If more than 1 option appears, contact Technical Support. This is a web portal/multi-site configuration.
M. Select a unique station number for each client that connects to the database, beginning with Station ‘02’.
N. Click ‘Create New Station’ to add new Station ID’s as needed.
O. Click Done and Begin to set configuration.
A. Open CRE to the main login screen
B. Navigate to File>Select Database
C. Enter Admin Password:
1. “password” – POSNation Default
2. “admin” – If you had to connect CRE to its local SQL Server to verify the CRE DB Version
D. Check box to ‘Use Advanced Configuration’.
E. Click Next.
F. Click ‘Change Local Database Info’.
G. Input the following settings to connect to the server:
1. Server: Computer Name/Hostname of the database server station
2. Instance: PCAMERICA
3. Database Name: Name of database as viewed on the database server
4. User Name: sa
5. Password: pcAmeri1ca
6. Uncheck ‘Use Trusted Connection with Windows Authentication’ (never check)
7. Select the ‘MS SQL’ radio button.
H. Click Done.
I. Click Next.
J. Select ‘Keep My Existing Database’ (the other option deletes the existing database)
K. Select Store ID 1001 on the left column that appears.
L. If more than 1 option appears, contact Technical Support. This is a web portal/multi-site configuration.
M. Select a unique station number for each client that connects to the database, beginning with Station ‘02’.
N. Click ‘Create New Station’ to add new Station ID’s as needed.
O. Click Done and Begin to set configuration.
Testing:
I. Open CRE/RPE on the Client Station to the main login screen
II. Click the Manager button
III Login using password first, and then the user id
IV. Navigate to Administrative>Inventory Maintenance>Lookup>Search
V. Verify that inventory is synchronized to the Server Station.
VI. Ring up a cash transaction and verify peripherals are working properly
VII. Ring up a credit transaction and verify credit card processing is configured properly
Common Problems:
I. Client Station is not able to connect
A. Verify that the following windows services are set to automatic and running on the Server
1. SQL Server (PCAMERICA)
2. SQL Server Browser
B. Uninstall unsupported security applications. Support applications include:
1. Microsoft Security Essentials
2. ESET NOD32 Antivirus
C. Examples of unsupported security applications include, but are not limited to:
1. Any Norton Product
2. Any McAfee Product
3. Any products with the phrase “Internet Security”, which indicate a 3rd party software firewall
D. Windows 7: Ensure the current network connection is assigned as a “Work Network”
E. Temporarily disable Windows firewall (if this is the resolution, you must configure Windows Firewall and re-enable for security – see below)
F. Reboot Router
G. Check for network Configuration Errors
1. Nested Routers
a. From client, ping hostname of server – failed response indicated DNS/Nested Router configuration error (usually from daisy-chained routers)
b. From client, ping IP address of server (if hostname fails, but IP address is successful, use IP address instead of hostname when configuring client stations in CRE
A. Verify that the following windows services are set to automatic and running on the Server
1. SQL Server (PCAMERICA)
2. SQL Server Browser
B. Uninstall unsupported security applications. Support applications include:
1. Microsoft Security Essentials
2. ESET NOD32 Antivirus
C. Examples of unsupported security applications include, but are not limited to:
1. Any Norton Product
2. Any McAfee Product
3. Any products with the phrase “Internet Security”, which indicate a 3rd party software firewall
D. Windows 7: Ensure the current network connection is assigned as a “Work Network”
E. Temporarily disable Windows firewall (if this is the resolution, you must configure Windows Firewall and re-enable for security – see below)
F. Reboot Router
G. Check for network Configuration Errors
1. Nested Routers
a. From client, ping hostname of server – failed response indicated DNS/Nested Router configuration error (usually from daisy-chained routers)
b. From client, ping IP address of server (if hostname fails, but IP address is successful, use IP address instead of hostname when configuring client stations in CRE
II. Windows Firewall Settings and Folder Security
A. Windows Firewall Exceptions for Work Networks AND Public Networks (Incoming)
1. Add Program Exceptions: Control Panel>Windows Firewall>Allow Programs or Features Through Firewall
a. File and Printer Sharing
b. Exception Name: CRE; Application: C:Program FilesCRE.NETCRE2004.exe
c. Exception Name: CRE SQL Server; Application: C:Program FilesMicrosoft SQL ServerMSSQL.%MSSQLBinnsqlservr.exe (exact folder location may vary slightly, and more than 1 may be available – allow all that may be found)
d. Exception Name: SQL Browser; Application: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
2. Add Port Exceptions: Control Panel>Windows Firewall>Advanced Settings>Right Click “Inbound Rules”
a. Exception Name: Pocket Inventory; Port: 32001
b. Exception Name: PCCharge; Port 50000
B. Folder Security Options (Windows Users; Read/Write/Execute)
1. C:Program FilesCRE.NET
2. C:Program FilesCREUpdateEngine
3. C:Program FilesMicrosoft SQL Server
A. Windows Firewall Exceptions for Work Networks AND Public Networks (Incoming)
1. Add Program Exceptions: Control Panel>Windows Firewall>Allow Programs or Features Through Firewall
a. File and Printer Sharing
b. Exception Name: CRE; Application: C:Program FilesCRE.NETCRE2004.exe
c. Exception Name: CRE SQL Server; Application: C:Program FilesMicrosoft SQL ServerMSSQL.%MSSQLBinnsqlservr.exe (exact folder location may vary slightly, and more than 1 may be available – allow all that may be found)
d. Exception Name: SQL Browser; Application: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
2. Add Port Exceptions: Control Panel>Windows Firewall>Advanced Settings>Right Click “Inbound Rules”
a. Exception Name: Pocket Inventory; Port: 32001
b. Exception Name: PCCharge; Port 50000
B. Folder Security Options (Windows Users; Read/Write/Execute)
1. C:Program FilesCRE.NET
2. C:Program FilesCREUpdateEngine
3. C:Program FilesMicrosoft SQL Server
III. CRE Database Versions do not match. How do I perform the upgrade?
Please contact technical support for assistance.
Please contact technical support for assistance.