2.0.4 continuous alert.vbs when starting start.vbs

[451422]

Each time start.vbs is kicked off it spits out alert.vbs for both stunnel and server.dll if the services are running or not. I have tried stopping them and running them before doing start.vbs with no success. FYI.

[raybob]

That makes no sense, no such error message is programmed into FHFS.  (Please use the FHFS board for this by the way).

Can you take a screenshot please?

Also, what do you mean you tried running them?  Server.dll is not a service, and it isn't be to used by you other than when FHFS programatically uses it (and you aren't supposed to start any services before you start the server, although doing so shouldn't cause any problems anyway)

[451422]

I meant stunnel and filezilla services. Do keep in mind, please, that id doesn't matter if the filezilla or stunnel services are running. In either case, the alert.vbs is initiated with the errors. I have found a crude way to resolve the issue by just renaming alert.vbs.

Please see attachments.

[raybob]

That simply means that FHFS couldn't start the services, either because 1) they're already running, or 2) they're disabled.

There's more possible problems than that though, most likely with permissions.

First off you shouldn't be using start.vbs, go through FHFS_Launcher.exe, and if you're using a version prior to 2.0.4 make sure you run it as an administrator.

Then let me know what happens.

[451422]

It is operating normally with the launcher. I have applied all permissions of administrator to the entire path c:\program files\fhfs and the user is an administrator.

It works via the launcher fine, however, how can the platform run automatically without logging in. Thus, I am researching the use of a third-party utility within the forums at this time.

[raybob]

That's your problem then, FHFS must be run as an administrator, and running start.vbs doesn't always do that.

[451422]

So the bottom line is the platform is configured to run as a server requiring manual intervention to start it via the launcher. If so, it is not a server. Just a service that requires babysitting.

[raybob]

It's not even a service, it's a typical Windows program that uses services for some of its functions.

You just have to make sure your start.vbs file is set to run FHFS as an administrator.  Yes, of course FHFS is a server.  Personally I don't know of any software like this that doesn't require being run as an administrator...

In the context of client-server architecture, a server is a computer program running to serve the requests of other programs, the "clients". Thus, the "server" performs some computational task on behalf of "clients". The clients either run on the same computer or connect through the network.

In the context of Internet Protocol (IP) networking, a server is a program that operates as a socket listener.[2]

Servers often provide essential services across a network, either to private users inside a large organization or to public users via the Internet.

[451422]

I ended up renaming server.dll to server.exe, stuffed it's shortcut into the startup group, changed the stunnel/filezilla services to automatic start, renamed the alert.vbs to alert.vbs.orginal, and applied the auto-logon to the created administrator equivelant account. Works like a champ. Rather crude approach, but it's working. We will begin evaluation on a larger scale after the new year. This will determine the longevity of service.

Thank you for your feedback. Have a good new year.....

sd

[raybob]

Well, if it works....

I had a registry-based autostart planned for version 2.1, hopefully this would be a solution for others facing the same problem.

I just didn't think there was demand for it.

BTW the new launcher in 2.0.5 solves the administrator problem (there's no way to start FHFS now without it, or well, modifying files like you did) but sadly not the autostart problem.