Cannot see ALOHABOH network 2

[jbeezy]

I was trying to install a new modem/router. Needed some info from isp, but their call center was closed. So I put the old modem/router back and lost internet connection.

Used network diagnostics to get internet connection back, but alohaboh said not connected. When I use windows xp in one of my other stores, I used to sometimes disable/enable the aloha network and it would resolve the issue.

However, in this store we use windows 7 and once I hit disable.. I could not see the alohaboh notification any more. I need help on getting the alohaboh back on and connected. Right now it is in redundancy mode.

 

[jbeezy]

Do I need to create the network/workgroup again? Limited troubleshooting experience for aloha. Never used windows 7 much either :
Aloha v6.4
Windows 7 32bit

 

[coorsman]

Right click in my network places select properties. On the left select network adapters. Then enable your connection again.

Cheers,
Coorsman

 

[jbeezy]

Thanks, that was a quick fix. I was getting paranoid.

Is there a way for terminal to not be master.. or does it take care of itself?

 

[coorsman]

Any terminal can be master. If term1 restarts usually term2 will become master so forth.


Cheers,
Coorsman

 

[jbeezy]

Sorry I made a typo on the earlier post. I meant is there a way to make terminal not be a "Server" not master. I guess get it out of redundancy mode.

I restarted the terminal twice, no luck.
Then logged in to aloha manager and clicked refresh data, but that didn't stop the terminal (FOH?)
Then tried restarting terminal again.
Then I read on some other posts about file server recovery, so I clicked that.
Then restarted terminal again.

Now terminal was not master, but I was just shooting in the dark. So just in case it happens again.. Is there a right way to take it out of redundancy?

 

[posrescue]

Fileserver recovery should automate the process, you should not have to reboot anything.

If after fileserver recovery the system is still in redundancy (master term is also the server) the following is a manual method.
1. Make sure no activity is on any of the terminals untill finished.
2. Copy aloha\data\trans.log from the master terminal to aloha\data on the server. You may want to rename the trans.log on the server first in case you need it later.
3. Copy aloha\data\aloha.ini from the master terminal to aloha\newdata and aloha\data on the fileserver. This is just to update the DOB. You could also manually change the DOB in the ini files on the fileserver or change it in aloha manager and refressh data before step 2.
4. On the master terminal open aloha\downtime.ini. Change the last known fileserver from the terminal's name to the actual fileserver's name. Typically that is alohaboh.
5. Turn off all the terminals.
6. Restart the master first. Once it is up and running restart the rest of the terminals.

 

[jbeezy]

Hmm so I followed the steps mentioned above, but I never checked the DOB. duh. Apparently it remained stuck at 05/19.

Today it started giving the following error " You can only clock in 10 times in a day". So I changed the DOB manually in aloha.ini for alohaboh data and newdata and aloha.ini in term1.

DOB is updated on the terminal, but it continues to give the error. Tried rebooting terminal, refresh data, shutting everything down and powering it on in sequence as mentioned above.

downtime.ini is alohaboh, verified that.

For right now I am using a different user id to clock in, but is there a way to go around this and fix it. Daily summary keeps showing data from previous 10/11 days. You think it might fix at end of day/grind?

 

[jbeezy]

Just so you know, went in today and everything was good. I guess it just fixed itself at eod.

Thanks everyone for your help.