Error: 1 is not supported codepage when unzipping snapin pack
-
Hi,
We are trying to deploy a snapin pack, but when the fog client tries to unzip the snapin pack, we get this error.
I have read this post: https://forums.fogproject.org/topic/11616/snapinpack-snapinclient-error-1-is-not-a-supported-code-page-parameter-name-codepage as it looks quite the same we have. Our envrionment:- Fog project 1.5.7
- Fog client 0.11.16
- Windows 10 Pro version 1809 and newer
- Language: English (United States)
- Keyboard: US English
I have tried to zip the snapin pack with various zip tools: 7zip, Windows builtin zip tool, download a zip from Gitlab (linux), but all gives the same error:
------------------------------------------------------------------------------ ---------------------------------SnapinClient--------------------------------- ------------------------------------------------------------------------------ 03/09/2019 14:05 Client-Info Client Version: 0.11.16 03/09/2019 14:05 Client-Info Client OS: Windows 03/09/2019 14:05 Client-Info Server Version: 1.5.7 03/09/2019 14:05 Middleware::Response Success 03/09/2019 14:05 SnapinClient Running snapin Onetrail MailSignature Install 03/09/2019 14:05 Middleware::Communication Download: http://fog.onetrail.net/fog/service/snapins.file.php?mac=1C:39:47:2E:F8:9B|E0:94:67:A6:E1:37|E2:94:67:A6:E1:36|00:FF:1E:AA:B0:FA|00:FF:52:22:4A:DF|00:FF:C9:DC:0C:28|00:FF:62:19:D9:92|E0:94:67:A6:E1:36&taskid=38 03/09/2019 14:05 SnapinClient C:\Program Files (x86)\FOG\tmp\mailsignature-master.zip 03/09/2019 14:05 SnapinClient Processing SnapinPack mailsignature-master.zip 03/09/2019 14:05 SnapinClient Extracting SnapinPack 03/09/2019 14:05 SnapinClient ERROR: 1 is not a supported code page. Parameter name: codepage 03/09/2019 14:05 Middleware::Communication URL: http://fog.onetrail.net/fog/service/snapins.checkin.php?taskid=38&exitcode=-1&mac=1C:39:47:2E:F8:9B|E0:94:67:A6:E1:37|E2:94:67:A6:E1:36|00:FF:1E:AA:B0:FA|00:FF:52:22:4A:DF|00:FF:C9:DC:0C:28|00:FF:62:19:D9:92|E0:94:67:A6:E1:36&newService&json ------------------------------------------------------------------------------What else can we try?
Thanks in advance!
/Jurgen.
-
@Sebastian-Roth : then don’t rush for me. What I can do for now is install the fog client and then copy the modules.dll that uses codepage 850. I have already created a script that does this. I will use this script to roll out the Fog client to all existing workplaces with psexec.
-
@Jurgen-Goedbloed While I might be able to get out a test version till then I don’t see that we have enough time to do testing before that. Can you delay the final roll out?
-
@Sebastian-Roth Our plan was to roll out the clients by the end of this week. Thursday or Friday.
-
@Jurgen-Goedbloed So what is your time schedule on this? Just asking because I have a lot of work and can’t promise to have this ready on shot notice!
-
@Sebastian-Roth We would be happy with that.
-
@Jurgen-Goedbloed said:
Can you implement this in a new version of the client, so that we can roll out the client via the MSI installer?
What’s your time schedule on this? There are a couple of things involved to bring out a new fog-client version and I don’t see us doing it all at in the next weeks. But I can imagine building sort of a pre next release version that you can use and help us testing things before the official release. What do you think?
-
@Jurgen-Goedbloed Thanks for testing and the information. Sure I will add this simple fix to the official code! Though I can’t promise you we’ll get out a new fog-client release soon.
-
@Sebastian-Roth We tested the DLLs and both are working fine for us.
My gut feeling says that codepage 850 is better, as it has more readable characters in it.Can you implement this in a new version of the client, so that we can roll out the client via the MSI installer?
-
Thanks. I’ll test and let you know.
-
@Jurgen-Goedbloed Here we go. Wasn’t sure if code page 850 (mostly used in USA) or 437 (more in UK, Ireland, Canada) would be the “better” choice (see wikipedia) so I build two DLLs:
- https://github.com/FOGProject/fog-client/releases/download/0.11.16/Modules_zip_default_codepage_437.dll
- https://github.com/FOGProject/fog-client/releases/download/0.11.16/Modules_zip_default_codepage_850.dll
Stop
FOGService(Windows services.msc), then go toC:\Program Files (x86)\FOG\and renameModules.dll. Now download the ones from above put in place of the original one. Start the service and try running your snapin pack. Please try both DLLs and let me know.
-
Great, thanks!
-
@Jurgen-Goedbloed I will build a DLL for you that sets a defualt code page for testing. But won’t get to that before tonight I suppose.
-
Hi Sebastian,
The suggested option: Control Panel > Region > Administrative Tab > Copy Settings indeed makes the extraction of the snapin pack work.Especially, setting the option “Copy Settings -> to Welcome screen and system accounts” works for us.
But, as we’re starting to deploy the fog client on a number of existing machines, that would mean that we have to manually do that on all machines. I will see if we can automate that, but can you look if you can build it into the client as you suggested? I’m happy to test.
-
@Jurgen-Goedbloed Ahhh, found an interesting post here: https://forums.sonarr.tv/t/update-process-failed-1-is-not-a-supported-code-page/3253/10
Our fog-client runs as service as well. So this probably causes the issue. If you change language settings after the install code pages differ somehow (maybe?!) and cause the issue.
Try as suggested: Control Panel > Region > Administrative Tab > Copy Settings
Otherwise we might go ahead and default to a code page as they do here: https://github.com/chef/fastmsi-custom-action/commit/40e1be8fcdf238c3f4bac94bb102e761d406651b
-
@Jurgen-Goedbloed Interesting issue you got here. From what you say it’s not as described in the other topic where @emc said:
I will still lookout for it, but I would say it is an issue with either 1709 or something specific with Windows internally.
Could it be related to the German language mentioned there. What language do you have your Windows installed with?
The error message “1 is not a supported code page” is not something specific to the fog-client as I can find many results on the web about this (1, 2, 3). Looks like people using the so called
SharpZipLibreport this kind of issue. We use this library as well. Possibly we need to update to the latest version of the library or just default to a code page.Do you have a OEM version of Windows running?? https://github.com/chef/chef-dk/issues/1290