Windows client 2.5.19 - windows 7 problem

client
#1

Hi,

On Windows 7 64bit after automatic client upgrade from 2.4.11 to 2.5.19 the client stopped working.
The last connection to the server is from before the update (still on the old client version).
On stations with Windows 10/11 64bit everything works fine after automatic client update to version 2.5.19.

If I click on the urbackup agent icon in windows I get an error:
“There was an error. Currently nothing can be backed up”.

Logs from client on win7:

2022-08-30 11:17:32: ERROR: Loading DLL “fileservplugin.dll” failed. Error Code: 127
2022-08-30 11:17:32: ERROR: Loading fileservplugin.dll failed
2022-08-30 11:17:33: ERROR: Loading DLL “fsimageplugin.dll” failed. Error Code: 127
2022-08-30 11:17:33: ERROR: Loading fsimageplugin.dll failed
2022-08-30 11:17:40: ERROR: Loading DLL “urbackup.dll” failed. Error Code: 127
2022-08-30 11:17:40: ERROR: Loading urbackup.dll failed
2022-08-31 16:35:06: ERROR: Loading DLL “fileservplugin.dll” failed. Error Code: 127
2022-08-31 16:35:06: ERROR: Loading fileservplugin.dll failed
2022-08-31 16:35:06: ERROR: Loading DLL “fsimageplugin.dll” failed. Error Code: 127
2022-08-31 16:35:06: ERROR: Loading fsimageplugin.dll failed
2022-08-31 16:35:07: ERROR: Loading DLL “urbackup.dll” failed. Error Code: 127
2022-08-31 16:35:07: ERROR: Loading urbackup.dll failed
2022-08-31 16:42:57: ERROR: Loading DLL “fileservplugin.dll” failed. Error Code: 127
2022-08-31 16:42:57: ERROR: Loading fileservplugin.dll failed
2022-08-31 16:42:57: ERROR: Loading DLL “fsimageplugin.dll” failed. Error Code: 127
2022-08-31 16:42:57: ERROR: Loading fsimageplugin.dll failed
2022-08-31 16:42:57: Loaded -cryptoplugin- plugin
2022-08-31 16:42:57: ERROR: Loading DLL “urbackup.dll” failed. Error Code: 127
2022-08-31 16:42:57: ERROR: Loading urbackup.dll failed
2022-08-31 16:42:57: Looking for old Sessions… 0 sessions
2022-08-31 17:12:58: Looking for old Sessions… 0 sessions
2022-08-31 17:42:59: Looking for old Sessions… 0 sessions
2022-08-31 18:13:00: Looking for old Sessions… 0 sessions

1 Like
Client on older Windows version
#2

I am getting similar results from a Windows 7 client running 2.5.19

Edit: I turned off auto update and reverted back to 2.4.11 to get current backups.
Edit 2: Sorry, Win7x64 here, not 8.1.

#3

I know, rollback client to 2.4.11 resolve a problem.
But why not working 2.5.19 client on win7?

#4

I run into the same error on Windows 2008R2. I check all that dlls in dependency walker and found unresolved import from KERNEL32.DLL

urbackup_dll
urbackup_dll842×567 20.8 KB

2 Likes
#5

Same here, after auto update to 2.5.20 on Win7 (ver. 6.1.7601), I get the following:

2022-09-12 11:40:26: ERROR: Loading DLL “fileservplugin.dll” failed. Error Code: 127
2022-09-12 11:40:26: ERROR: Loading fileservplugin.dll failed
2022-09-12 11:40:26: ERROR: Loading DLL “fsimageplugin.dll” failed. Error Code: 127
2022-09-12 11:40:26: ERROR: Loading fsimageplugin.dll failed
2022-09-12 11:40:26: ERROR: Loading DLL “urbackup.dll” failed. Error Code: 127
2022-09-12 11:40:26: ERROR: Loading urbackup.dll failed

#6

I have the same error on computers with windows 2008 server and windows 7 (64bits). I have my URbackup Server in Debian 11.
2022-09-14 15:53:30: ERROR: Loading DLL “fileservplugin.dll” failed. Error Code: 127
2022-09-14 15:53:30: ERROR: Loading fileservplugin.dll failed
2022-09-14 15:53:30: ERROR: Loading DLL “fsimageplugin.dll” failed. Error Code: 127
2022-09-14 15:53:30: ERROR: Loading fsimageplugin.dll failed
2022-09-14 15:53:30: ERROR: Loading DLL “urbackup.dll” failed. Error Code: 127
2022-09-14 15:53:30: ERROR: Loading urbackup.dll failed
2022-09-14 15:58:52: ERROR: Loading DLL “fileservplugin.dll” failed. Error Code: 127
2022-09-14 15:58:52: ERROR: Loading fileservplugin.dll failed
2022-09-14 15:58:52: ERROR: Loading DLL “fsimageplugin.dll” failed. Error Code: 127
2022-09-14 15:58:52: ERROR: Loading fsimageplugin.dll failed
2022-09-14 15:58:52: ERROR: Loading DLL “urbackup.dll” failed. Error Code: 127
2022-09-14 15:58:52: ERROR: Loading urbackup.dll failed

#7

I just had all my Win7 clients update to 2.5.20 and they all stopped working, logs show the same errors about unable to load all the dll’s

#8

All our Windows 7 machines also stopped doing all backups when using UrBackUp v2.5.20

Does anyone know when this will be fixed? We’ll have to drop UrBackup entirely, otherwise.
(We can’t just keep fixing things with solutions like “just keep reinstall the older/buggy versions instead”.)

We were doing backups at the end of each 8 hour shift. Over the past 20 days, we’ve missed 60 backups. Just too risky.

1 Like
#9

This is quite bad. Download page says client should work on Windows 7 so I guess it’s not being dropped just yet?

#10

ping @uroni

#11

I have the same problems with the server 2008R2 after upgrade :frowning:

#12

Description for Windows Client in download section now goes “UrBackup Client 2.5.21 (x86/x64) (10/11 + Server editions)”. So no more Win7/Win2008R2 compatibility.

#13

Very sad to hear that. I wonder what odd thing exists in W7 that forbids all newer versions of the client from ever working again.

#14

Hello everyone,
Any news on this issue ?
I was about to update my 2.4.x systems to 2.5.x but while I was reading changelog I saw something concerning about “Don’t install on Windows <= 8”, I still have a few Windows 7 machines and it will be a pity to not be able to do backups from those.

#15

The news is that Windows 7/8 support was officially dropped.

For now, 2.4 client works with 2.5 server. That can end at any time I guess and you are on your own when that happens.

It is a bit early in my opinion as I see quite a lot of Windows 7 machines still being used but hey, there is nothing better than UrBackup, so we should be grateful anyways.

#16

I was afraid that this is the answer.
And don’t get me wrong, I’m very grateful, UrBackup is a great software, it already saved me some headaches, but as You mentioned, in my opinion too, it is definitely too early to drop support for Windows 7, but apparently devs made that decision and we have to deal with it.
Have a good day.

1 Like
#17

It’s open source software so you are all welcome to fix it yourselves and hopefully submit pull requests to also fix it for others.

Also perhaps this would have gone differently if anybody spoke up when all those beta versions were posted to the “testing” category?