Aloha 4.268 Stuck in Redundancy

[AZBob]

I'm new to posting on the forums but I've found the site very helpful while I've had Aloha issues.

My client has Aloha TS 4.268, its old.
The BOH is Win2k FOH is win 95.

Long story short, I have to reinstall Windows. Normally I just whip out my drive image and go on with things. Because its a very different system than my standard image was made for even a repair install of Windows doesn't work. The last guy that did my job made the original drive image so Ive never actually installed Aloha before.

Ive got media for Aloha, SEC codes, HASP key and a full data backup of the drive pre-reinstall of Windows. The problem is that I'm not able to get the terminal I've got here for testing with the server out of redundancy. I have tried the following;

Ensured DOB is correct on both systems

Ensured system time\date and time zone are the same on both

Ensured proper fileshare access on both

Ensured proper usernames\permissons on the 2k system

Reinstalled the terminal's copy of Aloha using termisnt

Successfully copied files both directions to ensure proper read\write access with both systems

Verified the data in Aloha to be sound

Cleared \tmp folders on both systems

Deleted downtime.ini form the terminal

Ensured ctlsvr is running

Ensured lanacfg is properly set

Ensured proper ibercfg.bat settings relating to termstr, term number, maxterms, server name and iberroot

Ensured that the term's copy of \data is the same as the server's (I know it copies it over fresh upon a proper loadup but this isn't a proper loadup)

When it all comes down to it the terminal boots fine, it can hop into redundancy without trouble and seems perfectly content to run. Everytime I "Recover Fileserver" it never even flashes the notification on the terminal. I checked my DEBOUT.svr and the only thing that stands out is a line that reads
"BOH requesting recovery from fileserver down but denied because CtlSvr is in NON ROBUST mode"

Each time I have attempted the recovery a new reference to this has appeared. I know a terminal can be set to a non robust setup and understand what it means but this is the server. So at this point my questions are;

What is Non Robust mode for the server?

How do I fix it?

Ive tried everything I know at this point, any ideas out there?

 

[posrescue]

ROBUST = TRUE in the environment variables on the fileserver.

 

[AZBob]

Thanks for the reply posrescue. I checked the environmental variables and it was set to false. I switched it to true and refreshed data and attempted a recovery. DEBOUT.svr still had the same error. I reinstalled Aloha just to see if it would help, checked the variable again which was still true and rebooted but it still says it is in "NON ROBUST" mode.

 

[AZBob]

After alot of digging I think the problem is my HASP driver. On a whim I pulled the HASP key and rebooted the server. It didnt warn about a missing security key.

I had downloaded the driver installer from

http://www.aladdin.com/support/hasp/hasp4/enduser.aspx

and downloaded the "HASP Device Driver Command Line Installation (Hinstall)" I ran it and after that point CtlSvr would run. At that point I thought it was working but this would explain why it isnt in robust mode.

Is there a driver I should be using instead? Ive already uninstalled it and reinstalled with no success.

 

[coorsman]

check the lana number on the sever and terminal nic card.
Check my FAQ link at the top of the page

File server recovery won't work faq693-7381