Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backup Fails: Unsupported compression module: zip #2514

Closed
1 task
SamiLehtinen opened this issue May 31, 2017 · 6 comments
Closed
1 task

Backup Fails: Unsupported compression module: zip #2514

SamiLehtinen opened this issue May 31, 2017 · 6 comments

Comments

@SamiLehtinen
Copy link

SamiLehtinen commented May 31, 2017

I have:

  • searched open and closed issues for duplicates

Version info

Duplicati Version: 2.0.1.61
Operating System: Windows
Backend: FTPS

Bug description

Duplicati won't run a backup at all, because of this error message:
"Fatal error => Unsupported compression module: zip", even if zip is default compression algorithm.

Steps to reproduce

  • It's enough just to try running a normal backup, even without the --compression-module parameter.

Actual result: Backup fails with error message
Expected result: Well, backup should run with zip compression

@kenkendk
Copy link
Member

This looks like a duplicate of #2425

Is this after an update?

@kenkendk kenkendk added the pending user feedback needs information from the original poster label May 31, 2017
@SamiLehtinen
Copy link
Author

SamiLehtinen commented May 31, 2017

Yes, after 53 -> 61 update. Also downgrade back to 53 left system without essential .exe files in Duplicati 2 binary directory. Which is kind of strange. .config files are there, but exe's are missing.

But I did run the update using the MSI file, not the integrated update. The same problem occured on Windows Server 2012 R2 and on Windows 10, both x64 naturally.

@SamiLehtinen
Copy link
Author

SamiLehtinen commented May 31, 2017

Sorry, I were bit busy while filing this report. But now I had some time to look at the problem, and it seems that it's an interesting issue.

Reboot and reinstall (61) fixed the missing binaries issue. But the unsupported compression module issue remains. But this is probably due the fact that the SharpCompress.dll was missing. It was present after 53 (re)install. Now I restored the file back to Duplicati 2 directory, because it was strangely missing after 61 installation. And now even if the SharpCompress.dll is present, the issue still remains. Quite curious issue. Any pro-tips?

These tests were run using Windows Server 2012 R2 x64.

@NTWarrior
Copy link

NTWarrior commented May 31, 2017

I upgraded from and to the same versions the same way on Windows 10 x64 and have the same issue now. I would have used the integrated​ update but it wouldn't let me since I had a backup scheduled, and then I quit Duplicati and ran the MSI rather than turn off the schedule. I didn't reinstall, but I did extract SharpCompress.dll into Duplicati's Program Files folder and I'm not getting the error any more.

I'd have sent a bug report, but after 9 hours it didn't finish being created.

@kenkendk kenkendk removed the pending user feedback needs information from the original poster label May 31, 2017
@kenkendk
Copy link
Member

I have no idea why this happens. As I wrote i issue #2425, the SharpCompress.dll file is in the msi and zip files, so it should be installed.

The only vague clue I have is that the build is a custom version, because I needed fixes faster than the official build, so the current SharpCompress.dll has my signing key, and not the official one. Maybe that flags it for virus checking or similar.

@SamiLehtinen There is a tool that tells why it cannot load a particular file:
https://msdn.microsoft.com/en-us/library/e74a18c4(v=vs.110).aspx

If you can figure out how to use it, maybe that can shed some light on the problem?

@SamiLehtinen
Copy link
Author

Now in early morning I could restart the system without upsetting anyone too much. Complete uninstall, reboot, reinstall and now everything is working again. Yet I don't know what the root cause is. Afaik, this was duplicate and the original issue should go on with this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants