![]() ![]() ![]() Let me try and work through this logically. I am trying to rack my brains what has changed and the only things that have, guessing, are:ġ) Every host has had a major Windows update lately (Creators fall)Ģ) I stop using Avast AV and let Windows take over AV on some hostsģ) Some of the existing hosts have had the latest BOINC version installedĤ) Some of these are newly setup hosts, and hence would have had the latest BOINC version installed h (etc) files are where the source code expect's, and if you are using the same IDE, but if not. Technically I could recompile as I come from a C/C++ background, but it been so many years and I don't really have to time currently to go into this detail its fine when all the. In truth knowing this helps me try and work out what is going, as does your explanation on the password These are just normal desktops (workstations) with no networking used. Oh I had no idea it was both manager and client app, it is quite well hidden from the user (rightly so). The message box window is called: "BOINC Manager - Connection Error". "The password you have entered is incorrect, please try again". Yeah the error message and its window are: This isn't the first time it's prevented normal operation: we need to do some forensic research to discover why. The authentication is provided to cover the case where the Manager is being used to control a remote machine over a local network. On a default single-computer installation, this file should have been created on installation, and read from the correct location when the Manager is first run: no security is needed. The password being discussed is the contents of the file "gui_rpc_auth.cfg", which should have been created automatically in your BOINC data directory. You've mentioned that you have purchased some very expensive hardware - how good are you on software? Could you compile and run a debug version of the Manager, if we need to explore alternative reasons for the display of this message? Communications failures can occur either because the Client is not running, or because the communications channel is blocked: it's hard to distinguish between the two. BOINC consists of two local applications on your computer (the 'Client' and the 'Manager': they communicate by TCP/IP over port 31416, even on a single isolated computer). (Please confirm that the exact wording of the message you saw is "The password you have provided is incorrect, please try again.": it makes searching much easier).Īssuming that's the case, some other connection failure has occurred, and it's one I'd like to track down. It is certainly the case that the error message "The password you have entered is incorrect" is a last-chance fall-through for otherwise undiagnosed failures: see. I do appreciate everyone's help so far, it just very frustrating. I find it hard to understand how Microsoft, our AV or ISP, or something else, can trigger a 'incorrect password message box from boinc manager'. Perhaps someone can explain what 'password' this error is referring to, as no account, project, or project manager has been added to the BOINC manager yet? We add/remove projects and manager quite frequently as we run both UK Boinc team and GridCoin team via GRCPool. We have been doing BOINC for many years now and have never had this problem previously. Everthing is as default, no unusual setups.Īll I know is the error message I am getting, even after I have uninstalled and re-installed. I just tried again on a host with no AV (as it ONLY does as most of our hosts do) and that has the same problem. I come from a software development background so I appreciate the difficulties, however we are just stuck in the middle here. The thing is, the boinc manager is saying wrong password, before it even loads add project UI etc, therefore there seems to be some internal password within boinc manager which is getting/is corrupted.Īgeless mentioned deleting and recreating the auth file, which clearly stands for authorization/authentication, which very much seems like the issue at hand. No resolution was forthcoming, and he resolved the issue by going back one version, which kind of proves it is a boinc client issue and not anything else. The 2nd post, I did mentioned someone else having this issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |