New BOH Server, trying to get terminals setup again Error Iber.exe

[bbrunning]

I've installed aloha BOH and moved everything over. Now the terminals need to be setup to see it again. I've kept the settings on the server exactly as they were (to the best of my knowledge) before. The terminals cannot connect to the file server so I ran terminst and set the number of terminals to 3, when I hit okay it get's all the way to the end and fails with error:
Failed to copy \\alohaboh\BOOTDRV\Aloha\BIN\iber.exe to c:\Aloha\BIN\iber.exe GetLastError returned 32.

We moved from an old Win2000 server running 8.3.xx to win 7 pro 32bit 8.3.xx

Any ideas?

 

[bbrunning]

EDIT**
It was because the terminal was running. I stopped it and re-ran the terminal installer. It installs, reboots, then comes up looking for file server and gives me the make file server option again that asks for a code after.

 

[bakins]

It is probably a problem with the lana number on the network card. Run lanacfg and set lana number to 0 for TCP/IP for the NIC.

 

[bbrunning]

I doubled checked that, here's my output.

C:\lanacfg>lanacfg showlanapaths
Lana: 0
-->WINS Client(TCP/IP) Protocol-->Internet Protocol Version 4 (TCP/IPv4)-->Intel
(R) 82579LM Gigabit Network Connection
Lana: 3
-->WINS Client(TCP/IP) Protocol-->Internet Protocol Version 6 (TCP/IPv6)-->Tered
o Tunneling Pseudo-Interface
Lana: 1
-->WINS Client(TCP/IP) Protocol-->Internet Protocol Version 6 (TCP/IPv6)-->Micro
soft ISATAP Adapter
Lana: 2
-->WINS Client(TCP/IP) Protocol-->Internet Protocol Version 6 (TCP/IPv6)-->Intel
(R) 82579LM Gigabit Network Connection


It looks like I'm having an issue with ctlsvr, I checked the logs and it keeps terminating:Heres debout.txt
Jan 27, 12:14:36 AlohaMgr starting... version 5.3.19.212
Jan 27, 12:14:36 MODE SETTINGS
Jan 27, 12:14:36 ***** Version: 5.3.19.212
Jan 27, 12:14:36 LoadIberStrings() - Loaded version 5.3.19.0, IBERSTR.DLL
Jan 27, 12:14:36 ***** Workstation: ALOHABOH
Jan 27, 12:14:36 ***** TableService Only
Jan 27, 12:14:36 ***** Labor Scheduler enabled.
Jan 27, 12:14:36 ***** Site Id: 0
Jan 27, 12:14:36 *****Start of WORK in InitInstance
Jan 27, 12:14:37 *****Before AlohaMgr create
Jan 27, 12:14:37 *****Before AlohaMgr RequestCtlSvr
Jan 27, 12:14:37 CAlohaMgrApp::RequestCtlSvr() called...
Jan 27, 12:14:37 WaitForCtlSvrStartupComplete()...
Jan 27, 12:14:37 ACtlSvrConnect: (thread) - Begin Run()
Jan 27, 12:14:38 ACtlSvrConnect: (ICtlSvrCom::AreYouAlive failed (0x0))
Jan 27, 12:14:38 ACtlSvrConnect: Connection to CtlSvr lost. Prompting for reconnect...
Jan 27, 12:17:40 ACtlSvrConnect: Starting CtlSvr...
Jan 27, 12:17:40 ACtlSvrConnect: StartCtlService Failed (ICtlSvrCom::AreYouAlive failed (0x4))
Jan 27, 12:17:40 ACtlSvrConnect: Failed to reconnect to CtlSvr.


Here's debout.svr
Jan 27, 12:17:40 CTLSVR: Started CtlServiceThread... version 5.3.19.212
Jan 27, 12:17:40 CTLSVR 5.3.19.212 is running on workstation ALOHABOH
Jan 27, 12:17:40 CTLSVR: IBERDIR is C:\Aloha
Jan 27, 12:17:40 Operating system is unknown or unsupported. (BuildNumber 7601, Platform 2, Version 6.1, Service Pack 1)
Jan 27, 12:17:40 Hasp driver: Version 4.96, AutoDetect=Y, HaspLptPort=NULL
Jan 27, 12:17:40 LoadIberStrings() - Loaded version 5.3.19.0, IBERSTR.DLL
Jan 27, 12:17:40 TIMEZONE=INTL - using time zone information from the BOH computer
Jan 27, 12:17:40 TIMEZONE: operating system time zone settings match values in TIMEZONE.INI
Jan 27, 12:17:40 CTLSVR: Is NOT running in SQLMODE.
Jan 27, 12:17:40 CTLSVR: bRobust = TRUE
Jan 27, 12:17:40 Failed to open C:\Aloha\SQL\SQL.INI
Jan 27, 12:17:40 Error: 0
Jan 27, 12:17:40 Error: 1689824533
Jan 27, 12:17:40 CTLSVR: Start background processing...
Jan 27, 12:17:40
Jan 27, 12:17:40 CTLSVR: CtlServiceThread Terminated.

This is windows 7 32-bit and I installed the HASP drivers.

 

[coorsman]

On the server - Is the CTRLSVR started in services.

Cheers,
Coorsman

 

[coorsman]

I'm not 100% but I don't think ver 5.3 will run on windows 7, and I'm sure the program dosn't install correctly on 7 environment. Did you create a folder - bootdrv and install Aloha in there or is it installed on the root path of the drive?


Cheers,
Coorsman

 

[bbrunning]

CTRLSVR is not started in services. If I try to start it, it stops but I can't remember the exact error. They were getting busy and I had to reinstate their old system. Also, I looked on the working server and that service wasn't started either, I believe it only starts when it needs to verify the system, then turns back off.
I spoke with our vendor and they said that 5.3 does work with Win7. Although they were pretty annoyed I was doing this myself instead of having them come out and do it. Who knows, maybe they were just letting me waste my time in hopes that I would give up and call them.

I'll be back there on Monday attempting again. I may even bring a server 2003 copy with me since I've read more people having luck getting everything up on that.

I still have remote access to both systems if anything else in the logs would help.

 

[coorsman]

1. 5.3 does not set up the environment vairables on the W7 server. You will need to set these up menually. Also the install path of the Aloha directory on a W7 machine will need to be in a shared folder called bootdrv. ie c:\bootdrv\aloha.

I have an FAQ above expaining the steps ot install on a W7 machine listed on the menu abouve in this forum.

Also turn off ip6 on the network card.

I can help you over the weekend using goto meeting. We can set up a time/day if you like.

And you are right about your dealer.

Ctrlsvr has to be running unless the terminals are in redundancy.

(running in stand alone mode)



Cheers,
Coorsman

 

[bbrunning]

Sorry coorsman, forgot to answer the other questions.
I followed your tutorial on installing and changing the settings manually.

ipv6 is disabled in the lan properties, was I supposed to remove it via the registry instead?

Aloha is installed in c:\Aloha with c: being shared as BOOTDRV so the paths are \\ALOHABOH\BOOTDRV\Aloha\...

I might be able to get out there sometime Sunday, but I'm not positive. I could probably get RDP running and then initiate a GTM that way. Won't physically be there but I could always call and have them swap the dongle before anything gets started. What time zone are you in?

Thanks!

 

[coorsman]

Central time zone.

On a win 7 setup c:\aloha won't work. It needs to be in c:\bootdrv\aloha. Even if it's shared correctly. I presume it's the environment variables, unless you set them manually the do not get installed using anything under 6.4 and then the ctrlsvr won't get installed and started.
I could dial in anytim this WE or maybe even monday morning. Shouldn't take but a few minutes to get it up and running.






Cheers,
Coorsman

 

[bbrunning]

Thanks for the info. I'll go ahead and remove aloha and reinstall it in the correct location and move all their data this weekend. Do you have a gtalk/gmail handle or should I just post in here after I'm done to see about getting you to log in at some point and check it out?

Thanks!

 

[coorsman]

Ya just post. I'll get an email. Then well set up a goto
Meeting. That's about the only contact info I can
use w/o getting reprimanded by the tek-tip gods.

Cheers,
Coorsman

 

[bbrunning]

Alright, so I reinstalled everything under the correct location c:\bootdrv\aloha and I still cannot get ctlsvr to run without crashing. Let me know when you're around to do a gotomeeting.

Thanks

 

[bbrunning]

To add a little more troubleshooting. When running ctlsvr.exe /service it outputs the error "Database version is Not Current. Run Database Upgrade.

I've run dbconfig.exe and it successfully runs the upgrade, but I still get that error.

 

[bbrunning]

Another interesting problem. Now that everything is installed at c:\bootdrv\aloha, Alohamgr is still looking for files in c:\aloha.

 

[bakins]

You need to set your Environment variables. IBERDIR, IBERROOT, etc.

 

[bbrunning]

They are both set already. It seems to be an issue with Aloha 5.3 being installed into a different directory. Coorsman had me install it in c:\BOOTDRV\Aloha
I've verified my variables for iber are correct and ctlsvr runs just fine when it's set.

 

[bbrunning]

To add to that. Alohamgr would not start up properly until I copied the data back to c:\aloha
So yes it's the environmental variables, but seems to be more of a problem with win7 and the paths actually working correctly.
Are there other variables I'm missing?
I set the following
IBERROOT=Aloha
IBERDIR=c:\BOOTDRV\Aloha
SERVER=ALOHABOH
and a couple others but I've turned the old system back on since they are getting more customers now.

 

[coorsman]

I can remote in using gotomeeting.com

https://www2.gotomeeting.com/join/755135898

Cheers,
Coorsman

 

[bakins]

IBERDIR- C:\Bootdrv\Aloha, IBERRROOT- Aloha?