System Redundancy Error - Aloha

[mixerjv]

I'm getting a system redundancy error on a terminal and can't fix it for the life of me.

Aloha 5.3.32 TS with 4 terminals & EDC
BOH running W2k
2 Posiflex's running W2K, (plus one currently down - bad HDD)
1 Javelin LCP running W95B

Has worked for the last year and a half, HDD went bad on Javelin , reghosted HDD image, set up parameters (autoexec.bat on w95), got it up and running and now getting system redundancy errors whenever i try to log in at the terminal (I assume when it tries to write to the fileserver)

Z: working correctly, mapped to the server bootdrv

lanacfg shows lan card on the server is 0

Help! Thanks.

 

[zahead31]

Is the C: drive shared on the terminal as BOOTDRV with full permissions allowed?

 

[mixerjv]

Yes.

I am using the winlogon method on the Javelin.

I did try switching to Client for Microsoft and using tweak to login with same username/password as the server - same error.

However, you just gave me an idea, although I checked Z and it comes up, I'll try writing a file from the javelin to the server and see if it works. I will report back shortly.

Thanks for the quick reply.

 

[mixerjv]

Yes the Javelin (problem terminal) can write a file to the server.

Still coming up with System Redundancy error.

 

[posknowitall]

Delete the downtime.ini. Turn off all terms. Allow one terminal to come up as master (not the one that is having redundancy error) Turn on other terms including the one with error. Should work!

 

[mixerjv]

Deleted downtime.ini on all terminals while they were disconnected from the network. Immediately shut down terminals, restarted one by one, starting with a known good terminal.

Still having issue.

What causes the System Redundancy error? Is it that the terminal can't write to the fileserver or is there another cause? Thanks for your help.

 

[mixerjv]

OK, I think I'm getting closer.

I shut off all the terminals except the Javelin (problem terminal), deleted downtime.ini and restarted.

The Javelin should have come up as the master. It's firing up, but now says "make fileserver".

However, using windows explorer I can easily browse the network and access the server bootdrv. I went a step futher and mapped Z: to the server bootdrv.

Still "make fileserver"

What would cause Aloha 5.3.32 not to able to access the server but windows explorer can?

 

[zahead31]

I am not familiar with the Javelin terminal, but from the oroginal post, it looks like this terminal is using Win95? Have you checked the contents of your ibercfg.bat to make sure the settings are correct? I would be most interested to make sure the server name is listed correctly.

 

[mixerjv]

Yes, it's running w95b. Server name is correct.

Upon further examination I think it's related to the Daylight Savings time update. I'll report back here what I find.

 

[posknowitall]

Daylight savings time problem? That surprises me that the system redundancy error should occur. Then again, daylight savings ALWAYS causes problems in Aloha. The redundancy error comes from the trans.log. The only way to correct it is to do a fileserver recovery. This somehow unflags the trans.log. If the term can't find fileserver you probably have some log-on issue. To test thi-- Enable guest account on the server and log term in as guest.

 

[mixerjv]

OK It's fixed!

My screw up. I did have the back of house server name incorrect in the system environment variables on the javelin. I fixed it yesterday, but it still didn't solve the problem, it took an EOD (end of day) to work it out.

Thank you everyone for your assistance!