Professional Documents
Culture Documents
Level 1 Documentation
First check the NCR KB KB0020309
If no information is there then this is the next place to check
Use CTRL+F to Find what you are searching for
CFC Information
All employees that are Shift Lead or higher should have an account
CFC Default Login
Username: First initial dot last name. EX: J.Smith
Password: Blank on first login, they will be prompted to set one up
Owner: Store Number
Forgot Password
Type in the Username and Owner fields, then click Request Password
Reset
A password will be sent to the stores email. If the request is for
someone above a GM the password will be emailed to the email listed for that
account.
No Account
To create an account a service request ticket must be created
To verify there is no account, anyone in IT with a CFC login can
check: Select the Store > Maintenance > Labor > Employees > Search for
employee and look under Above Store Settings Tab you will see username if
there is an account already created
Cannot Edit Punch: Clock out is less that the Clock In Time
1. Verify the punches are from the same date
2. Verify the edited punch is actually earlier than the clock in
3. If the employee is a minor, the edited punch may be outside of
legally acceptable hours.
4. If all of the above is correct and within guidelines, the time to be
edited to may not be in the same business day.
Checking business day start
1. Find the store in CMC
2. Select the terminal that the punch is being edited
from
3. Select File Manager
placing a test order. The Master terminal will not show in CMC even though it is
the Master terminal in the eyes of the store's network.
KDS Device(s) Missing in CMC / Showing Disconnected on the Screen
1. Scenario #1 (All KDS Controllers)
2. Log into CMC
3. Select the NCR server for the unit in question
4. Verify that the Aloha Kitchen Service is running
1. If the AK Service is stopped, start the service
2. If the AK Service is started, restart the service
Once the AK service has been confirmed as running, troubleshoot the network
connections leading to the switch if the issue persists
Scenario #2 (One or more (NOT all) KDS Controllers)
b.
4.
5.
a. If the device isnt showing on the network from the NCR Server, path to the
device using the address bar. Ex: \\AK57-Egg1\C$
6.
7.
Access Services.msc
Connect to the device by selecting Action > Connect to another computer in the tool bar and
using the name of the device youre connecting to. Ex. AK57-Egg1
a. If the following message is received, retry step 5
8.
9.
c.
d.
i. Reboot the device in CMC by selecting it from the unit list and clicking the
reboot button in the toolbar
If a reboot hasnt resolved the issue for steps A or B listed above, RAL/Reload the
device
If step C fails, escalate to NCR Warranty or NCR 2nd Level accordingly
10.
Verify that the device is no longer showing disconnected once you
VNC into it
FOH Stuck in Loop: Locating Fileserver/LocatingMaster Terminal
See No Master Terminal Created
Terminal Missing in CMC
Attempt# 1
1. Confirm the terminal is on network by pinging it from the NCR server in CMC
a.
If the device isnt showing on the network from the NCR Server (Pic 1), path to the
device using the address bar. Ex: \\Term7\C$ (Pic 2)
b.
a.
b.
Attempt# 2
1. While logged into the NCR server
3. Highlight the address bar and navigate to the C: for the terminal.
(Ex. \\Term7\C$)
i. Ensure that siteId value matches the Aloha HASP Key number shown
in CMC
ii. Ensure that line <nodeConfig id="(Terminal Number)" /> has the
correct terminal number listed
7. Right click "Services (Local)" from the left hand column and
select 'Connect to another computer'
10.
Close out of all windows and switch user out on the NCR File Server
11.
12.
a.
2.
iv.
Wait a few minutes for the temporary password to be sent to the units
email and use it to log into Pulse on the iPad so a new password can be
set
EOD Process
EOD is set to run at 2am automatically. It will clock out any employees who did
not and close any remaining open orders out to a cash payment of their exact
balance. The Master Terminal must be running for the EOD process to run
successfully.
The following is the process that EOD follows:
-The marker file \Aloha\DATA\EOD is created and takes all terminals except the
Master down
-All open sales are closed to cash and all employees still clocked in are clocked
out at 2am
-A dated subdirectory is created in \Aloha\YYYYMMDD
-The TRANS.LOG file is copied from the DATA directory to the
Aloha\YYYYMMDD subdirectory
-All system configuration files are copied to the Aloha\YYYYMMDD
subdirectory
--If the files are copied successfully then the originals will be deleted from their
respective locations
-The .LCK, .TXT, and all configuration files are deleted
-Any files that have changed in the BOH are updated for the FOH
--Employee profiles/passwords, configurations, and charges for the Store
-Business date is updated
-Procrecs.exe runs and updates any corporate changes to the \NEWDATA
directory
-All files from \NEWDATA are copied to \DATA
--This becomes the \DATA directory for the next day
-Once this has all completed a DONE30 marker file is created in the
Aloha\YYYYMMDD subdirectory
-The EOD marker file is deleted and terminals refresh
--Refresh=Reading the new \DATA directory and updating their files to match it
-A new TRANS.LOG file is created since the previous has been deleted
--You can check the Last updated date/time in File Explorer to verify this
Reasons EOD could Fail
-The Hard drive is full
-No Network connection to the NCR Server
--If this is the case then the Aloha\YYYYMMDD directory will be on the Master
Terminal rather than the NCR Server
-Power fluctuations
-The Business Date is out of sync with the System date
-The Master Terminal was offline or went offline during EOD
GRINDING
-GRIND.exe manages the TRANS.LOG for the day and created .DBF files
accordingly
-It runs within 30 seconds of EOD completion and is effectively an extra piece to
the EOD processed
-It creates the GNDDBF file in the Aloha\YYYYMMDD directory
-If unsuccessful the terminals will all display the Waiting to Grind 2016MMDD
message across the bottom left corner
-We have successfully tricked GRIND.EXE into running by creating the
GNDDBF file in the Aloha\YYYYMMDD directory and then deleting it, therreby
causing CTLSvr to run GRIND.EXE
Important Miscellaneous Information
-All transaction data is stored in the TRANS.LOG file which is located in the
DATA subdirectory on the NCR Server. This file also record all other FOH activity
that occurs such as voids and canceled sales.
-Also in the DATA directory are the printing logs for the store. These contain all of
the printing information from the Kitchen Printers.
-A program called GENPOLL.exe will create polling files at predefined intervals
which are then stored in the Aloaftp data location. This location is where all
corporate data updates come from as well. They are downloaded once the Alohaftp
program notices them and then processed/applied during EOD.
-Ctlsvr = Control Server Service --> This service controls Aloha's overall
operations on the system -> Takes down all POS
Restarting this service -> forces POS to take down Aloha and Start Aloha again
This is why we stop it before copying files for some fixes
-iber.exe = the Aloha POS software executable name
Ending task of Iber.exe:
(from POS) - closes aloha on TERM you ended it on