Search results for query: *

Hi there, I would check on your patching as well. I know that the latest and greatest Aloha update files not only require c++ 2005 to be installed but it is also looking for a patch to c++ 2005 that came out last year.

Looking very quickly it looks like your Bin folder did not Update correctly. Did you use Aloha Update or an Aloha CD? I think you need to unregister all files using the batch file , update the Bin contents with all 6.4.20 files and run the register batch file.

I am not familiar with that version so I won't be much help...

If it is the same modem that was being used previously and the driver is installed correctly then it should work. There are a number of files for QSR that you may need. I am not sure which version you are running and i am only familiar with version 1 so this may not apply. Under The Program...

It also looks like you are low on Hard Drive Space at the terminal level. You could try manually updating all the Bin files on the terminal with the files from the server.

Check the Servers %iberdir%\data folder for an OK file. If it is not there bring up a command prompt, navigate to %iberdir%\data and type echo > OK

Are the terminals coming up to Looking for fileserver? Are they getting to a certain point in the load and rebooting? The syncinclusionlist.cfg was an addition in 6.4 but i believe it is not necessary to run iber. The message that goes on and on about DHCP Media sense is a Registry setting...

At the terminal level is where you will need to make the change to the Aloha.ini. When terminals are in Redundancy they are running entirely on their own without any connection to the server. So any change that you want to affect how that terminal is running needs to take place at the...

I think you were on the right route with changing the Aloha.ini date. But it is possible that you were ending the task while aloha was still working on EOD. So when you started back up it overwrote any changes you may have made. Wait for Aloha to finish 1 EOD and then log off. As it is...

One possible way to see what is now missing from your Grind files would be to copy the Bad grind files out of the Dated sub. Then Re-grind the Dated Sub to create new Grinds based on the Trans.log. You can do this in a command window from the aloha Bin folder by using "Grind /date 20101114...

Scratch that, it does not update ALoha.ini or .cfg files.

It is probably not necessary. I was using it because it seemed a cleaner way to do it. It also gave me a forced pause to allow the terminals to all realize that there was a stop file present. I cannot remember for sure but I think doing it this way updated all of the files in Data including...

Here is a good place to start. Try testing this. I have used this on a small scale. CD\ @ECHO OFF @CLS ECHO ***REFRESHING THE ALOHA POS*** ECHO ***DO NOT CLOSE WINDOW*** CD BOOTDRV\ALOHA\TMP ECHO>STOP NET SESSION /DELETE /YES START /b /MIN /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY...

Sorry I can't be of more help Lost. Without I can't figure this one out. I am guessing that it is something outside normal Aloha operations that is causing this. If as you say nothing on the system had changed before it stopped working, everything that we did should have taken out the...

Disconnect the network cable from the terminal and see if you can get it to boot up by itself without being on the network. You may have to change the Downtime.ini to say that the term is the file server. This will help rule out a network issue.

The next thing you can try is replacing all Aloha files on the terminal. Copy all files from the Aloha\bin folder on the Server to the aloha\bin folder on the terminal. Then do the same thing for the DATA folder again deleting any .log files. Make sure the ALoha.ini on the Server has today's...

Hi Lost, The error that you are seeing is an Aloha Dump. This can be caused by various kinds of Aloha Application problems. Have you recently made any changes to your system? I.e. Update Aloha, install new software? When did this first occur? Did you come in one day and the terminals were...

You might try loading from a different terminal. You will have to edit the downtime.ini which is not normally advisable. In this case it might be the only way. Change it so that the Master terminal is whichever terminal you will be booting and change the Filserver to match the Server variable...

It looks as though your terminal is trying to run in redundancy and still thinks that it is running on 8 30 2010. Open the Aloha.ini in Notepad and edit the Date Of Buisness to be today's date. Delete any and all .log files from Data on the terminal and on the Server. Should be trans.log...

This command added to your Winhook file will accomplish the creation of the PMIX file you are looking for. Change the %1 to the date you wish if using outside of winhook. The name of the Items can be found in a .csv created this way. However you will need to change the Export settings for the...