Aloha ctrlsvr error

[Saveabyte]

Recently had a terminal crash, repaired it,now when my computer boots running Windows NT 4, with aloha software, I get a Ctlsvr error box stating "security key not found, when I click ok I get a pop up box error that says "CTL:ctlsvr is NOT running. I can't get Aloha Control prgm. to run, and my terminals can't find the filserver.
Thanks in advance for any insight on this

 

[AdamDR]

This can happen for a variety of reasons.

1. Your key is not attached to your computer
2. You don't have the hasp drivers installed
3. Your parallel port is not working correctly
4. Your parallel port has a printer cord plugged into the hasp key and it doesn't like it.

The first one is self explanitory.
If you don't have the hasp drivers you can download them from alladin's website.
If the problem is with your parallel port, go get a PCI parrallel card and plug the hasp into that port.

Hope that helps.
Adam

 

[AkamaiAloha]

Adam, you forgot one! The key could be toast. This doesn't happen a lot--but we've seen it a few times, I think every time it has happened, it's been with power outages. If that's the case, you're going to need to call your local dealer for new key.

 

[Saveabyte]

Thanks so much, I had removed the server from the site without bringing the hasp key (unaware of its use). Connecting that solved the problem. Now I have another, apparently when the terminal went down the server or Aloha software did not close the EOD. now when either terminal is booted it wants to "process the end of day" I get a error screen from the Aloha control prgm, saying it is shuting the terminals down, the terminals reboot and it loops again and again. Aloha is new to me not sure what to purge or change so as not to lose anything

 

[DTSMAN]

On the subject of HASP Keys..

FYI--Connecting and all-in-one printer on the parallel port and running it through the hasp key will cause issues and sometimes fry it.

Bo

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

 

[AkamaiAloha]

Saveabyte--we really need more information about the condition of your system. My first thought would be to change the DOB and delete the trans.log in data. Then see if Aloha comes up. But I have no idea what version of Aloha you're running, if you're concerned about the sales data that was previously there, or your configuration? I am assuming the front of house and back of house are running on the same computer, acting as terminal and file server?

 

[Saveabyte]

AkamaiAloha- Thanks for the post, I am running one server and two terminals, using Aloha 4.268. Because of your post and other posts on tek-tips, the rebooting is solved, the terminals boot and allow user logons and what appears to be normal operations. This is my first run at POS, not the pond I usally wade in, its a "friend" thing. Thanks again and thanks to all that took the time to reply.

 

[AkamaiAloha]

Glad we could help. And good luck!