Add-in 2 System Error. Code: 59 An unexpected network error occurred.

S

StevegHI

Member
Hello,
Quick note because I had a glitch and fixed it after an hour of work. I was using the following: Windows/11 (version 24H2 build 26100-4061) with the cumulative update of KB505679 and XLSPadlock 2024.3. Compiled the Excel spreadsheet. When I run the Excel .exe, I get the following critical message:
Add-in 2 System Error. Code: 59​
An unexpected network error occurred.​
Clicking "OK" kills it.​

Windows/10 computer (Build: 19045.5854): Executes (XLSPADLOCK 2024.3) without any problem. Windows/10 computer: Compiles with 2024.3 have worked without a glitch all year.

Windows/11 computer: I updated 2024.3 to 2025.0. Same problem trying to run .exe previously compiled under 2024.3.
Windows/11 computer: Recompiled into new .exe using 2025.0.
Windows/11 computer: Problem gone.

Curious about the cause. However, I hope it saves somebody else some grief.
 
Last edited:
Solution
gdgsupport
In version 2025, we also modified the way our COM add-ins are registered with Office, so it could be the explanation why Add-in 2 System Error. Code: 59 does not appear anymore for you.
Sort by date Sort by votes
gdgsupport said:
Strange because "Add-in 2 System Error. Code: 59" was indeed fixed in XLS Padlock 2024.3 and XLS Padlock 2025 uses the same fix.
Click to expand...
Now you have the scientist in me interested. Is there a specific module or modules that I can check the revision on that would provide further insight? I'm almost ready to update my Windows/10 to 2025.0 but it would be good to know what causes this.
 
Upvote 0 Downvote
In version 2025, we also modified the way our COM add-ins are registered with Office, so it could be the explanation why Add-in 2 System Error. Code: 59 does not appear anymore for you.
 
Upvote 0 Downvote
Solution
Thanks. It's seems to be something in the 2024.3 compiled version & execution on W/11. Execution error not generated on W/10. Compiling on 2024.3 on W/10 or 2025.0 on W/11 doesn't generate the error on either computer. It only occurred with 2024.3 and running on W/11. That could mean that any of us on Windows/10 and 2024.3 are on borrowed time because if Microsoft make a similar change to Windows/10 that they did to Windows/11 and we stay on 2024.3, then the same problem would occur.

Simple answer...upgrade to 2025!
 
Upvote 0 Downvote
Hi everybody, a client just told me he is having the "Add-in 2 System Error 33", he´s using Win 11 24H, XLS Padlock used to compile file was 2024.2, I will re-compile it with version 2025.0, will keep you posted to let the community be informed
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top