EDC Error

[alohaakamai3]

Sorry I didn't write down the exact error message, but those of you who know the fix will likely know what I am talking about. I have seen it before as well, and just dont remember what I did to fix it.

Aloha was recently installed on a new server. EDC runs find as a service, but when you go to run the EDC executabe that brings up the user interface, it will occassionally come up with the error message to the effect: CannotOpenInitDialog: The path to \\Alohaboh\bootdrv\aloha could not be found.

Rebooting it will allow the interface to work fine for a while, but eventually will come up with that error msg sfter its open and closed enough times. The actual processing of credit cards is never disrupted, just the interface portion.

I have tried reinstalling and I have also tried re-registerting the services.

Any ideas?

Thanks

 

[bigblok403]

Strange, usually only works or doesn't work. This happens on my test server (Multiple Aloha's on 1 server) sometimes if the wrong Aloha folder path is specified in the environment variables, the wrong folder has the bootdrv share, or the bootdrv share has incorrect privileges.

 

[DTSMAN]

I always have a seperate user that is a member of administrators for the two services. I have had similar issues if it was registering under the loacal system account. But is does sound like a share issue. Cancel the share and then reshare it again.

Bo

Remember,
If the women don't find you handsome,
they should at least find you handy.
(Red Green)

http://www.redgreen.com

 

[alohaakamai3]

I don't know why this didn't occur to me earlier, but this is a 11 terminal site using windows xp pro. could this be a connection limit issue? Is there a way for me to increase this without changing the OS?

 

[bigblok403]

Could be the issue. Other than using a different O/S somewhere in the network or using a version of Aloha that supports RFS, I don't know what else you could do.



In Progress...

 

[alohaakamai3]

Bigblok-

So whats the official connections with Aloha? One with EDC, one for Aloha Manager, and then one per station?

Thanks

 

[bigblok403]

1 for EDC, 1 for each terminal running an NT based OS, 1 for certain 3rd party apps.

 

[alohaakamai3]

The offical situation is actually:

10 terms and EDC (based on what you've told me)

That would make it sound like that this is indeed a connection issue: max number xp pro connections is 10, and we're trying to do 11.

What I DONT understand is I have been able to get EDC working with all 10 terminals without rhyme or reason. Usually, I'd have them reboot the server once or twice, and then EDC would open-they'd leave it open-all all was fine.

So, why then, did the BOH not refuse a connection from one of the FOH terminals when EDC was open.

Another thought-I know XP didn't put this limitation in until service pack one. Wonder how much trouble I am asking for going back to SP1 to get around this issue.

 

[bigblok403]

I've had sites do the same things (Hit and miss connections) due to CAL problems, but never effect EDC, so that's why this is kind of confusing. If processing is never interrupted, maybe EDC.exe itself has a problem, but not EDCSVR.exe

 

[alohaakamai3]

Bigblok-

I had exactly the same thought. My theory at this point is as follows:

That EDC needs that connection temporarily to start the executable, but doesn't need it after the interface is running, and doesn't need it for edcsvr at all, because the actual processing has never been an issue.

Just out of curiosity, I wanted to see if I started all the terms, then shut one off, and started EDC (that's 10 connections)-then restarted that term, to see if that would be refused. But thankfully it's not. Again, this leads me to believe the connection is temporary for EDC and only when starting the executable.

Assuming that any of this is accurate (who knows), I told the MGR the best thing to do at this point is probably just to work around it at this point. Just leave EDC open all the time. And if they happen to close it, they can possibly do a refresh (to break the connections and start EDC, if that will work), or reboot one of the terms.

In any case, if they leave it open, there shouldn't be any problems.

The only other two options in this case are two upgrade to an expensive server class operating system or roll back to XP SP1 before the connection limit was imposed.

I am not sure either two is worth the work for what looks like may be a minor in convenience.

I'll post back if I find anything different, not crazy about playing around with it on a Friday-bad karma