Multiple Concepts on One Fileserver

[posrescue]

One fileserver, Two independent installs of Aloha running at the same time. Each Aloha Manager sets its environment variables thru a BAT file and uses the NOMUTEX switch and CTLSVRNOCOM switch to allow mutual exclusivity and to force CTLSVR to not run as a COM service. The Iberdir has been removed from the registry. Has been working flawlessly.

The end user that decided to uninstall then reinstall Norton. During the Norton install, Aloha Manager for one of my concepts shut down and now will not initialize CTLSVR. (the Aloha Manager loin window does not come up automatically, after logging in it sits at waiting for CTLSVR to initialize.

The debout.txt shows :

*****Before AlohaMgr RequestCtlSvr
CAlohaMgrApp::RequestCtlSvr() called...
WaitForCtlSvrStartupComplete()...
MaACtlSvrConnect: (thread) - Begin Run()
could not start ctlsvr in the No COM mode. Error = 2
WaitForCtlSvrStartupComplete()...complete.

I cannot find a reference to what error 2 is when running in NO COM mode and can't seem to make this work. The working concept shows CTLSVR in NO COM mode was successful.

The other concept is still working great and EDC is still picking up req files from both concepts in the FOH.

The event log that the uninstall of Norton was unsuccessful. I'm guessing the guy restarted the computer during the uninstall.

Anyone ideas? I don't want to go cross country to reinstall the Server again...

Thanks

 

[DTSMAN]

Delete any environment variables in windows that reference aloha except robust and server, these will conflict with the batch files. You may need to reinstall the concept that isn't working. It sounds like you have troubleshooted everything else.
Norton has killed so many of my sites, we now roll out servers with the AVG free edition loaded on them and it seems to be ok.

Bo

Kentucky phone support-
"Mash the Kentrol key and hit scape."

 

[posrescue]

Environment variables are in for IBERDIR, IBERROOT, EDCPATH pointing to the EDC install. I was going to run these from an EDC config and start batch file but Aloha's docs say these will not bother Alohas as they have their paths set in their batch files. EDC is using the STO.DBF with both concepts listed with thier uniqe store numbers, termstr etc. The TRM.DBF used by EDC includes the terminals from both concepts. That is why EDC has to run from it's own directory and not from one of the Aloha folders...
It would seem that if nthe EDC environment variables was causing problems neither of the Aloha installs would work?
The iberdir assigned to CTLSVR was removed from the registry...

Thanks