Did you rename it by any chance in an older version ? There was an issue with that in an older version of Servoy.
Just export it and send it to Servoy support.
I also got that message when importing a solution that I had not attached a password to. I just reexported it with a password and used that password to import it. Is this possibly a bug?
What version of Servoy are you using ?
Also did you rename the solution at any time? Like already stated in this thread there was an issue with that in earlier versions of Servoy 5.
Note that in the end we NEVER managed to remove the password, because we don’t know what it is! We have never set it ourselves in the first place! So for now, each time we want to import this module in developer, we export it first WITH our own password!
Another annoying thing with passwords: if you export a solution with many modules, and decide you want to password-protect it (or are force to password-protect it because it uses the famous module!), the export wizard asks for ONE password - ONE time -, but then when you import in another Servoy developer, it will ask for the password for each and every module. So in the end when we export our solution with the bugged module, we usually use one letter as a password, to avoid having to type a complicated password for each module… I remember that the first time we did use a more complicated password, and when importing, failed to type it correctly for one module, the import stopped here, and the whole solution was damaged…
Now ‘a’ or ‘z’ is our ultra secure password (oops, I just said it! )
jcarlos:
I am reporting this is issue as a bug. I’ll do as Patrick prescribes for the time being -or until the bug is fixed.
Yes, Carlos, and don’t forget your one character ultra-secure password!
Thanks!
Well, I reported the bug. Issue # 291177
Ok, but how to reproduce this issue (starting from a non protected solution) ? There was a bug about password protection and solution rename but that one is fixed now.
lvostinar:
Ok, but how to reproduce this issue (starting from a non protected solution) ? There was a bug about password protection and solution rename but that one is fixed now.
You’re right Laurian, it’s not going to be easy to do, but when was it fixed?
And more importantly: how to unprotect a solution/module that was wrongly protected by this (or any previous) bug?
lvostinar:
Ok, but how to reproduce this issue (starting from a non protected solution) ? There was a bug about password protection and solution rename but that one is fixed now.
You’re right Laurian, it’s not going to be easy to do, but when was it fixed?
And more importantly: how to unprotect a solution/module that was wrongly protected by this (or any previous) bug?
It is fixed since 5.1.1 (of course if you use the rename context action and not do it manually outside developer). There is a context action to remove the protection password (visible if solution is protected). So, export from workspace with a password, import in workspace, then remove password protection.
lvostinar:
Ok, but how to reproduce this issue (starting from a non protected solution) ?
I can tell you by replicating how it happened to me:
create a solution in 5.0.1
export that solution
install servoy developer 5.1.2
perform the import (using servoy developer 5.1.2)
BTW, this happened with only one solution. This is why I didn’t report this as a bug initially. But when I realized that is was not just happening to me, I reported it.
I agree, I shouldn’t have submitted the locked solution -sorry about that.
lvostinar:
It is fixed since 5.1.1 (of course if you use the rename context action and not do it manually outside developer). There is a context action to remove the protection password (visible if solution is protected). So, export from workspace with a password, import in workspace, then remove password protection.
Right! It worked!
6 months of ultra-secure ‘a’ password and I can now import without it
When I tried from scratch, chosing ‘unprotect’ on the module, it prompted me with a password, tried my usual ‘a’ but it is not the one… So:
1/ I exported my module by giving my ultra-secure password ‘a’
2/ I switched workspace to import it, typed ‘a’ when prompted for a password.
3/ In the solution explorer, right clicked on the solution, and chose ‘unprotect’, typed ‘a’ again, - this time it accepted it!
4/ Exported it from this workspace, WITHOUT password this time.
5/ Now switched back to my original workspace, deleted the protected module, restart (safer when reimporting a solution with the same name).
6/ Importing the module, no password was asked.
7/ Reattaching it to SVN (this was the worrying part, because SVN complained about the fact that the project existed already and advised me to check-out instead, which I knew was not the thing to do), so I reattached it instead and it went well: two files were modified: rootmetadata.obj and solution_settings.obj
I want to point out that the issue that I raised is slightly different than the issue that Patrick had when importing solutions with modules.
My issue was probably caused by (1) renaming the solution (working on it for a while) and then (2) exporting it. I saw the issue after I installed 5.1.2. The import issue appeared when trying to import into Developer 5.1.2.
jcarlos:
I want to point out that the issue that I raised is slightly different than the issue that Patrick had when importing solutions with modules.
My issue was probably caused by (1) renaming the solution (working on it for a while) and then (2) exporting it. I saw the issue after I installed 5.1.2. The import issue appeared when trying to import into Developer 5.1.2.
This seems the same issue to me. The bug was that renaming a solution made it also to be password protected. So, when export and then try to import it, will ask for a password even if at export no password was set. There was also a complain related to clean import but couldn’t reproduce that one (so when no renaming was involved).