trans.log error in structure 0

[liquidcherry]

Hi everybody,

I am the IT guy for a Restaurant and they use Aloha (Version 5.3.16) with 6 Terminals(Server is on Win 2000 Pro), the Terminals use all Win98,2 of

the Terminals are Javelin Viper, the rest are POSpioneer.

Their Aloha Dude went MIA and i took over somehow at least the hardware part (and a bit the software part) so here comes my problem:

One of the terminals died and i installed Win 98 on a spare(a pioneer, what a pita to get the drivers) but it was neccessary because of the others being Win98 machines.

So, i put it back in the network with the same terminal name/number and booted it up and it initialized it and all of the sudden it copied some files from the server( i had to replace a terminal in the past and it didn't do this and i successfully installed it)...So after copying the files it rebooted itself and after coming back to life it tried to init but than i got a strange message:

Trans.log is corrupted at location 0 (or similar, haven't written it down)

So, i looked on the server and fair enough there was a "fixlog" programm(only up to version 2.5.72, i tried to apply but of course not worky)...but now after browsing this great forum and seeing that there is no fixlog program for the version we have(5.3.16) i am completely lost and would need the help from the pros here, if possible

Cheers

Liquid

 

[coorsman]

Try renaming the trans.log file. Run without one it will create a new one. This is the file that contains all sales and transactions. Dont Delete it.

Also, there is a \aloha\tmp\debout*.* directory on the terminal. Post the last page of lines of the debout on this site for review.

 

[liquidcherry]

Cheers "coors"man!

Thx for your fast reply...

I will post the debut file tomorrow when i am at that terminal(i am home now, much needed rest here lol)

I forgot to mention, i did copy the trans.log file to the destkop and deleted it from the data folder :-(

But most important, it started not with the translog file it started with a "date".log file what i also copied to the desktop...i also need to mention that in order to get the new terminal running(POSpioneer with prior XP installed) i cloned a POSpioneer with Win98(since i couldn't get any pospioneer driver for this particular machine with different chipsets than the other POSpioneer machines)

So, before it get's confusing i stop now and will post the debout findings tomorrow, thx guys, you and this forum rocks!

Cheers

Liquid

 

[liquidcherry]

Hi there,

I have the debout content:

Jan 01, 05:51:47
Jan 01, 05:51:47 ................................................................
Jan 01, 05:51:47 IBER started (robust mode)... version 5.3.16.153
Jan 01, 05:51:48 LoadIberStrings() - Loaded version 5.3.16.0, IBERSTR.DLL
Jan 01, 05:51:49 Begin initializing network...
Jan 01, 05:51:49 Initializing network...
Jan 01, 05:51:49 Node = 3 String = 'D'
Jan 01, 05:51:49 NBInit()-> Before NBAddName()-> StationName = "IBERD "
Jan 01, 05:51:52 NBInit()-> After NBAddName()-> StationNumber = 6
Jan 01, 05:51:52 NBInit()-> Before NBAddGroupName()-> SessionName = "IBERLINK"
Jan 01, 05:51:55 NBInit()-> After NBAddGroupName()-> SessionNumber = 7
Jan 01, 05:51:55 Station number 6, session 7
Jan 01, 05:51:55 Network initialization complete.
Jan 01, 05:51:55 Done initializing network.
Jan 01, 05:51:55 Determining Master And Fileserver
Jan 01, 05:51:55 Local DOB is 9/22/2010 in C:\Aloha\DATA\ALOHA.INI (09 22 2010)
Jan 01, 05:51:55 Creating terminal status for 1
Jan 01, 05:51:55 Terminal 1 asserts 1 is master
Jan 01, 05:51:55 Master terminal is 1. Now determining fileserver...
Jan 01, 05:51:55 Master Terminal 1 asserts fileserver is 'ALOHABOH'
Jan 01, 05:51:55 Attempting to connect to server 'ALOHABOH'...
Jan 01, 05:51:55 Successfully connected Z: to \\ALOHABOH\BOOTDRV
Jan 01, 05:51:55 Ignoring file on server with long filename: Z:\Aloha\BIN\AlohaMgrCommon.tlb (ALOHAM~1.TLB)
Jan 01, 05:51:55 Ignoring file on server with long filename: Z:\Aloha\BIN\CalcEditField.tlb (CALCED~1.TLB)
Jan 01, 05:51:55 Ignoring file on server with long filename: Z:\Aloha\BIN\DocumentationUpdates53x.pdf (DOCUME~1.PDF)
Jan 01, 05:51:55 Ignoring file on server with long filename: Z:\Aloha\BIN\InterceptActivity.tlb (INTERC~1.TLB)
Jan 01, 05:51:55 Ignoring file on server with long filename: Z:\Aloha\BIN\InterceptPrinting.tlb (INTERC~2.TLB)
Jan 01, 05:51:55 Ignoring file on server with long filename: Z:\Aloha\BIN\UserTools.tlb (USERTO~1.TLB)
Jan 01, 05:51:55 Found fileserver. Updating DOWNTIME.INI...
Jan 01, 05:51:55 Delete MultiSync flag 'C:\Aloha\DATA\MSYNC'
Jan 01, 05:51:55 Beginning synchronize data...
Jan 01, 05:51:55 Iberdir: Z:\Aloha Localdir: C:\Aloha Target: C:\Aloha\DATA
Jan 01, 05:51:55 Creating terminal status for 4
Jan 01, 05:51:56 Creating terminal status for 5
Jan 01, 05:51:57 Creating terminal status for 2
Jan 01, 05:51:57 End synchronize data (total 432 files)...
Jan 01, 05:51:57 Synchronize Data Local DOB is 9/22/2010 in C:\Aloha\DATA\ALOHA.INI (09 22 2010)
Jan 01, 05:51:58 TIMEZONE=INTL - using time zone information from the BOH computer
Jan 01, 05:51:58 TIMEZONE: operating system time zone settings match values in TIMEZONE.INI
Jan 01, 05:51:58 Begin reading data...
Jan 01, 05:52:01 Check For Unregistered applications...
Jan 01, 05:52:01 Don't need to start VBOINST.EXE
Jan 01, 05:52:01 ConvertTransLog(): Analysing TRANS.LOG for conversion...
Jan 01, 05:52:01 Iber(): No log conversion required.
Jan 01, 05:52:01 Done reading data.
Jan 01, 05:52:01 Number of color bits is 16, Physical Memory 259547136 bytes
Jan 01, 05:52:01 Using Enhanced Graphics Interface (EGI) display
Jan 01, 05:52:01 Begin reading transaction log...
Jan 01, 05:52:01 Fatal error: ProcessTXNLog()..C:\Aloha\DATA\TRANS.LOG appears corrupt at position 0
Jan 01, 06:06:45 Warning: Destroying thread for printer 3
Jan 01, 06:06:45 net shutdown!
Jan 01, 06:06:45 Canceling datagrams...
Jan 01, 06:06:45 Canceling datagrams second time...
Jan 01, 06:06:45 Dropping names...
Jan 01, 06:06:52 Net shutdown complete
Jan 01, 06:06:52 Operating system is Windows 98 (BuildNumber 67766446, Platform 1, Version 4.10, A )
Jan 01, 06:06:52 Exiting Windows...


I know the date is off but can't change it right now....

I noticed one thing, even i deleted the trans.log file it is still producing the error message? :-(

Thx everybody for your help!!

Cheers

Liquid

 

[coorsman]

You said you imaged the terminal from another - this error can be because the term string is the same as another terminal.

each terminsl should be named/numbered term1 term2 term3 and the ibercfg.bat file should contain a system varaible term="?" ans numterms="?" termsrt="?" they should all be the sane exept the term="".

 

[liquidcherry]

Hi coorsman,

Yes you are right, i cloned one term(same hardware) and i made sure the new iber config on the new term is different from the others, each Term has his own #...i also tried the Terminst to no avail i still end up with the error message...:-(

Cheers

Liquid

 

[DTSMAN]

The rest of the system works fine but this one terminal gives an error?

Check the date, time, and time zone on that terminal. Change them from January and you will be fine.

That is your problem..

Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com

 

[liquidcherry]

Thx Bo,

Will do that later and will let you know, that would be cool if this works

Cheers

 

[coorsman]

Good call dtsman didn't see the date the first time.

 

[DTSMAN]

I believe anytime there is an error 0 in Aloha, it is a date/time issue.

Determining Fileserver fails at 0 and never counts higher
Translog errors like this one that point to location 0

Very common when restoring a terminal from an image.

Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com

 

[liquidcherry]

THX DTSMAN and coorsman,

You guys rock(especially dtsman)

Went this afternoon there and fixed the terminals time problems, it then updated the files from the server, rebooted, registered, rebooted again and than...Ta Ta!

Terminals runs just fine, thx again

Cheers

Liquid