I have a aloha pos 5.3 , the terminals get a msg can't find file server , i have already changed the hub to the BOH server and also checked all the connections , is their a file i on the server i should look to see if it needs attention or needs to be removed as the problem still exists...many thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Aloha POS Can't find file server
- Thread starter Micros888
- Start date
Have you tried to see if you can see the terminals from the boh server or vice versa ?
Try a UNC path from the BOH server in Windows Explorer like \\term1\bootdrv\aloha and see if you pull anything up -- adjust the path to suit your system name/path if needed.
Make sure the ctlsvr service is started on the BOH server as well...
and check your debug file outputs to see if there is anything usefull
Try a UNC path from the BOH server in Windows Explorer like \\term1\bootdrv\aloha and see if you pull anything up -- adjust the path to suit your system name/path if needed.
Make sure the ctlsvr service is started on the BOH server as well...
and check your debug file outputs to see if there is anything usefull
- Thread starter
- #3
When it is displaying that message, you might test at that point and see if the UNC path works from term to term, and from a term to boh and vice-versa.
Might be something as simple/annoying as the BOH networking locking up/bad network card/driver or something in BOH server, since you already changed the Switch, wiring or that would be my next bet.
When you do get the error - what do you have to do to fix it ? Restart ctlsvr or have to reboot boh or everything ?
Might be something as simple/annoying as the BOH networking locking up/bad network card/driver or something in BOH server, since you already changed the Switch, wiring or that would be my next bet.
When you do get the error - what do you have to do to fix it ? Restart ctlsvr or have to reboot boh or everything ?
- Thread starter
- #5
If you have a bad trans log.. it should show up in your EOD logs.
Since this is happening over multiple days, I don't think it can be a bad trans log, because that gets moved into the dated dir each night, and a new one gets created. (There should not be a trans.log at all in the newdata directory)
Also since it's saying can't find fileserver, It pretty much has to be that something with the BOH server - otherwise you would be getting term1/2/3 down from the other terminals intermittently as well if it was the switch/hub.
So I would think it's either intermittent problem with cable - only to the BOH server, something wrong with the ctlsvr locking up for some reason, or something wrong with the network card on the BOH machine... epecially if the BOH machine is not completely locked up.
If when the terms are at the point of can't find fileserver, and you try to access the unc path of a terminal from the BOH machine, or boh from a terminal -- and it works -- then obviously the network and BOH machine are find, and that would narrow it down to the aloha install on the machine locking up. If not.. I would think wiring/network card problem.
If your debug files are not helpfull.. you could always do the unreg/rereg of all of the aloha system services. I have never done that, but many other messages on the forum suggest doing that when the system is acting flaky.
Hopefully this is helpful
Since this is happening over multiple days, I don't think it can be a bad trans log, because that gets moved into the dated dir each night, and a new one gets created. (There should not be a trans.log at all in the newdata directory)
Also since it's saying can't find fileserver, It pretty much has to be that something with the BOH server - otherwise you would be getting term1/2/3 down from the other terminals intermittently as well if it was the switch/hub.
So I would think it's either intermittent problem with cable - only to the BOH server, something wrong with the ctlsvr locking up for some reason, or something wrong with the network card on the BOH machine... epecially if the BOH machine is not completely locked up.
If when the terms are at the point of can't find fileserver, and you try to access the unc path of a terminal from the BOH machine, or boh from a terminal -- and it works -- then obviously the network and BOH machine are find, and that would narrow it down to the aloha install on the machine locking up. If not.. I would think wiring/network card problem.
If your debug files are not helpfull.. you could always do the unreg/rereg of all of the aloha system services. I have never done that, but many other messages on the forum suggest doing that when the system is acting flaky.
Hopefully this is helpful
- Thread starter
- #7
You can make a copy of it, and then do fixlog on it, if you have fixlog for your version...
See this thread :
See this thread :
- Thread starter
- #9
One of the more common causes of terminals not connecting to the fileserver in Aloha is a software firewall running on the fileserver. Make sure the windows firewall is turned of if using XP SP2. Also make sure there is not another 3rd party firewall running.
When testing network connections for Aloha be sure you can edit or delete files on the fileserver from the terminals, (any terms that will ever be the master.
Cheers
When testing network connections for Aloha be sure you can edit or delete files on the fileserver from the terminals, (any terms that will ever be the master.
Cheers
- Thread starter
- #11
LEBANESEROD
Technical User
Hi everyone.. i am a new user here and i am not an expert in ALoha environment. I am actually an IT Technical consulatant helping some guys out after confronting a certain messed up configuration with their Aloha POS. (Aloha Table Service Version 5.202, Serial Num: 838770347)
Briefly, after backing up all necessary folders in the ALoha directory, i used the "one-click upgrade" feature and then proceeded with the license keys etc.. Nevertheless upon rebooting an finishing DBUP2.EXE and DBUP3.exe; a CtlSvr pop message was shown stating: "DAtabse version is not current. Run database upgrade". This error is mainly preventintg me from logging on to the ALoha MAnager...
Any soon help would be more than appreciated... Thanks
Briefly, after backing up all necessary folders in the ALoha directory, i used the "one-click upgrade" feature and then proceeded with the license keys etc.. Nevertheless upon rebooting an finishing DBUP2.EXE and DBUP3.exe; a CtlSvr pop message was shown stating: "DAtabse version is not current. Run database upgrade". This error is mainly preventintg me from logging on to the ALoha MAnager...
Any soon help would be more than appreciated... Thanks
- Status
Similar threads