1393a - Everything Server - Invalid username or password

[nps_matt]

Howdy,

Updated a client to 1393a and found the network index went dark for that client.

Debug console has:

Code: Select all

RDC U:  34
SEND 272 OS_WINSOCK_SOCKET WAIT socket closed
Invalid username or password

Updated the server instance to 1393a. Updated the Everything Server plugin to 1.0.1.2. Reconfigured the Everything Server plugin, share, user and password.

However, my 1393a client still has Invalid username or password.

Notably, the 1391a clients do not have this issue. They connect to the 1393a + 1.0.1.2 Everything Server just fine. All clients are configured with the same Group Policy object, so I'm pretty confident it's not actually an incorrect credential.

Downgrading my 1393a client to 1392a resolves the issue.

Cheers

[void]

Please update Everything on your server and all clients to 1393a.
Please update your Everything server plugin

Everything 1393a will require Everything Server 1.0.1.2 or later.

Everything Server 1.0.1.2 improved encryption.

[nps_matt]

Hi void,

Just to be unambiguous, I have:

Everything 1393a on the server
Everything Server 1.0.1.2 plugin on the server with Everything 1393a
An Everything 1393a client

The 1392a client connects to the 1393a server with plugin 1.0.1.2.

The 1393a client does not.

See server details:

tX7siklWn9.png (38.62 KiB) Viewed 3419 times

Cheers

[void]

The 1392a client connects to the 1393a server with plugin 1.0.2.1.

The 1393a client does not.

This indicates the server is still running the old 1.0.0.1 plugin.

Are you running an Everything Server as a client service?
-If so, please restart your client service.

[void]

Please upload a debug log in a bug report:

• On the Server, In Everything, from the Tools menu, under the Debug submenu, click Start Debug Logging.
• From the Tools menu, Click Options.
• Click the Everything Server tab on the left.
• Uncheck Enable Everything Server.
• Click Apply.
• Check Enable Everything Server.
• Click OK.
• From the Tools menu, under the Debug submenu, click Stop Debug Logging.
  ---This will open your %TEMP%\Everything Debug Log.txt in Notepad.
• Please upload this file in a bug report.

[nps_matt]

This indicates the server is still running the old 1.0.0.1 plugin.

Are you running an Everything Server as a client service?
-If so, please restart your client service.

This was the right place to look.

I'd thought to stop the client service and restart it after updating, but that itself wasn't the problem.

In fact the client service on our server was running from a portable setup, not the standard installer.

This was done so that the service could be run without using a user's APPDATA and without putting config files in the Program Files folder.

The fix was to stop services, download the plugin DLL and client executable and replace those files in the portable folder, and restart services.

This one comes down to administrator error.

Thank you for your time!

[void]

I am glad to hear you found the issue.

There's a lack of error reporting on Everything's behalf.
-I have put on my TODO list to show the Everything Server status somewhere under Tools -> Options -> Everything Server.