aloha not grinding properly

[alohahello]

I have never seen this error before. when i open the debout.svr for the alohaboh it reads

cannot read aloha.ini
ctlsvr cannot open aloha.ini.

It gets stuck on grind so after the end of day all the terminals are stuck waiting for the date to grind.

all i do is manually grind the date and the terminals are back up and running with no problems thru out the course of the day. any suggestions?

 

[Stingrae]

I have seen on occasion that the server doesn't have full permissions to it's own BOOTDRV. I know this sounds odd.

That is: the folder to which your Aloha directory is a subdirectory of. Aloha automatically creates this shared BOOTDRV during installation, but I have found that it is best to manually go and re-share this folder.

Try un-sharing and re-sharing your BOOTDRV.

 

[SwampGas]

See what the debout.g01 says if grind is failing.

Also remove any white spaces in the aloha.ini.

MegabyteCoffee.com

 

[alohahello]

Yes i am aware of the bootdrv. I have all the permissions setup for access. There is no space in the name Aloha.ini.
The system was running fine up until the owner tried to make the alohaboh server host the dvr security software as well. I told him i do not recommend doing that, since the dvr is constantly writing to the hard drive and using up system resources. Since then i told him to unintall the software but the grind for the end of day is not properly executing.

 

[SwampGas]

I wasn't referring to spaces in the aloha.ini name. And the piece about the owner doing something wasn't part of your origiinal message which puts a whole new spin on everything.

MegabyteCoffee.com

 

[alohahello]

okay i get what your saying with the aloha.ini now. It was working fine before he jacked up the system, but i can always try to take an aloha.ini file from one of the dated folders to see if that resolves the issue. thanks for the help!

 

[SwampGas]

I wasn't referring to spaces in the aloha.ini name. And the piece about the owner doing something wasn't part of your origiinal message which puts a whole new spin on everything.

MegabyteCoffee.com

 

[alohahello]

yea i know. i am talking about the file and whats inside it. not the name itself.

 

[coorsman]

Check the dated subdirectory - see if all the files are in there, compare to the previous day, except that the files that start with gnd*.* won't be in there.

Sometimes the directory doesn't get created properly at eod. The ini file might be missing. Check that the trans.log is there and has a file size greater than 1.

Make a copy of the trans.log and copy all the data from the previous days dated sub to the day that won't grind.

Replace the saved trans.log and edit the aloha.ini
file and search for DOB= in it. Change the date to the correct day and regrind.

 

[alohahello]

No thats not the issue. I know how to to manual grind the dated folders. It is not even making a dated folder for the day. it gets stuck on the end of day because it cannot read the aloha.ini. In all terminals are stuck at waiting for date to grind. I have to delete the eod marker it creates, then create the dated folder for that day. Then i use the C:\aloha\bin\grind.exe /date command to grind the folder.
my problem is it doesn't eod properly, because it cannot read aloha.ini and ctlsvr cannot open aloha.ini

 

[SwampGas]

Since I cannot see your system, this is just a guess cause it sounds familiar:

Make sure all files in the DATA and NEWDATA directory do not have a Read Only atrribute, nor system attribute. Also a screwed up mirror.log can cause this. If mirror.log is hosed, just delete it.

Use the following attrib command in the DATA and NEWDATA directories, as well as the terminals DATA directories (since EOD actually starts on the master term in the first place):
attrib -h -r -s *.*


MegabyteCoffee.com

 

[alohahello]

I was able to resolve the issue. all the permissions didn't get wiped so they were still in place. The entire time from reading the debouts the ctrsvr wanted to open ALOHA.ini and the ALOHA.ini in the data folder was Aloha.ini so it wasnt able to find it. I went back a year in the dated folder and found that the AlOHA.ini was in all caps. dialed into a few sites and verified that it was all caps in the data folder. I changed the aloha.ini file to all caps and it grinded just fine last night. I don't know what that customer is doing with his system, and why he would change things around with aloha.