Search results for query: *

From what I recall optimization is merely that, it's basically a defrag for database. Upgrade will possibly rebuild certain sections of the database depending on what is actually causing the issue, assuming the database is somewhat intact.

I would try an upgrade before optimization. It sounds like your database is damaged, do you have any backups?

FOH

In the ibercfg.bat file that starts Aloha on the other terminals, check for anything in regards to "SET QSRVIDEO" or something, and put the same things on the new terminal if it does. Also most QSR setups need XMLRDS.DLL, XMLKDS.DLL, and XMLTABLE.DLL placed in the Windows\System(32) and...

I don't know if it works for dated subs (I assume it does, but I've never done it), but for a dated sub Forceconverlog it would be more like this - c:\bootdrv\alohaqs\bin\grindq /date 20150426 /forceconvertlog

Depends on the circumstance. forceconvertlog is usually used for the DATA folder right after an upgrade on a current says trans.log. If that error is popping up for a dated sub or could be anything from the version to missing files, wrong directly, invalid variables. Debout.g01, debout.U000, and...

For an update it is /Forceconvertlog

You technically have to purchase the license

What version are they running?

It is probably either in the environment variables or another ibercfg.bat that is overwriting it.

It has to do with the fact the DST can cause short temporary 2 hour time jump and in newer versions it waits a minute to validate if the time sticks as to not inadvertently fire events such as EOD, thus even changing EOD time to say 4:02 can help prevent EOD from firing early.

I would change EOD to 4:15AM or later. I just saw you have NCR hardware, so unless it's really old you shouldn't have to run any DST patches.

I would delete the timezone.ini and recreate it anyway. It is recommend not setting EOD time to 4am because of this. Have you run any DST patches from NCR on the servers?

In Aloha Manager, make sure "International Daylight Savings Time" is checked along with "Synchronize POS Time With Back Office Time" under maintenance>Store Settings>System. Delete the timezone.ini in the Aloha DATA folder on the server and then restart the CTLSVR servioe. Run a refresh after...

Ill see what i can do tomorrow, but i prefer to be messaged through reddit (you just need to create an account and message me there) for providing links. You can use any 6.5 version, even the latest With your key.

Shouldn't matter, but I'd put it up top just to be safe.

Instead of "rpt.exe /date data /XP" use "rpt.exe /date %1 /XP

Either log in as the Administrator (not an admin user) or check this registry entry (HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer) and remove any data from a field called "ValueShell" if it exists.

Looks like an item was deleted before EOD ran. If you drop in an itm.dbf and possibly cit.dbf/cat.dbf from the previous dated sub it should grind. If it happens every day then is this a 24 hour site or has the trans.log been carried over each day because EOD is failing? That error is grind...

Versions after March 2013 should correct this issue, but it will also be caused if RFS is not running under its own admin account with full BOOTDRV share permissions and if ANY Win7 FOH/BOH PC's do not have the Disable File Caching and USENEWSMB registry settings updated on them according to NCR...