Home > Forum > General > .

Based on log - "Error has occurred, only license service works" and "No license for fronton"


Start installer and go to Tools for application management > Licence Manager and check status and licence version. After upgrade to 2022 there could be an issue related to licence for specific version.

I don't use Express verion but I suppose that you have login and password for download licence online. There may be needed to add right licence by Webcon to your account.

For Standard/Enterprise it's best to use source #1.
For Express version it's best to use source #3 - Express installer has some "limitations" that prevents from using functions/configurations that are outside of Express licence scope.

Sorry, but I can't confirm that using installer of Std/Ent version cause problem in this case - i haven't come through scenario like this.

In reply to: nobody

.

I didn't mean version numbers between Std/Ent and Express but installer itself. I usually work with Ent edition but during instalation Express (two times) i noticed few less options (for example creating of additional attachement database, maybe something else.. I can't remember).
I agree with You that main components are te same and finally only license limits use of particular modules/functions.

Good luck in finding solution :)

MVP
In reply to: Jacek

I didn't mean version numbers between Std/Ent and Express but installer itself. I usually work with Ent edition but during instalation Express (two times) i noticed few less options (for example creating of additional attachement database, maybe something else.. I can't remember).
I agree with You that main components are te same and finally only license limits use of particular modules/functions.

Good luck in finding solution :)

Hi,

I have no idea for this problem, but I just noticed that the application templates are exported using version 2022.1.1.41. I'm not sure that you will be able to import them in your installed version 2022.1.1.53 in the first place. It may work or not, depending on any underlying changes which have been made. Since this is only a little update, you could be lucky. I would probably remove everything though, because of the error and reinstall version 1.41.
- Uninstall WEBCON BPS
- remove the application pool
- remove website
- remove databases.


Regarding express:
Somewhere in the EULA it's stated that you may have a single express environment in your company.
Besides this the limitations I'm aware of are:
- No attachment/archive database
- Only a single content database
- A process can be imported once. If it already exists, you won't be able to import an updated version.

Best regards,
Daniel

MVP
In reply to: nobody

.

I agree with you, getting down to the root cause would be the best option. But since I didn't have the issue, I can't tell you anything about this. Somehow I got the impression that you just installed the system so I mentioned the uninstall option. Of course, you could keep your content database, and attach this one to a new installation. That's (was) a little tricky though in the past. I haven't done this in quite some time now.


I found this in the EULA number 1.13. page 3:

EXPRESS Edition – Software intended for Productive Use and Non-productive Use, made
available free of charge. The EXPRESS Edition shall be active until the Environment
Database exceeds the size of 10 GB. Unless a separate agreement made between the
Licensee and the Licensor expressly stipulates otherwise, it is prohibited to use the
Software in the DEMO Edition and the EXPRESS Edition simultaneously; it is __prohibited__ for
one Licensee to use __more than one EXPRESS Edition__ simultaneously


The instant change technology has nothing to do with the import. You are 'simply' limited to modify the workflow in the production environment. But this is besides your original question.

@MANSOFT if you have database backups there is no problem do reinstall envirement to previous version or even directly to 2022_1_1_41. You won't loose any data, but there is no way to downgrade database version.

Daniel is right - you cannot import proces from different version, even minor version difference is significant.

"I try to avoid this at all costs. not only because of the time and work put into the configuration of the current environment. It is not difficult to put a new instance from scratch, the trick is to solve the problem in low-key situations. What if such a situation took place in full version on production? Nobody will put the implementation from scratch at the first problems."

In such cases, a backup is a must, also preceding test upgrade in dev/test enviroment.

MVP
In reply to: nobody

.

I used an answer with a short citation, but I'm referring to the previous post.


"but how to update production having a version of the target application for the external client"
Ok, so you have clients which are using express and you do the development for them on your environment. Luckily I haven't been in this situation but I need to note down this risk so this would be explicitly state in any official documents between us and the client.

Thanks for the reminder. :)

MVP
In reply to: nobody

.

Unfortunately I don't have one which could really work. Only one idea which may work, but only with simple workflows. Even if I had one which could work, I would not disclose this. This would be similar to assisting in a robbery in my point of view. The feature has been explicitly implemented to prevent this.

I tried ones to "compare" the exported application package from two environment so that I may be able to identify all changes. I have given up on this because the XML structure may chang drastically between versions. Which makes an comparison not feasible.

Best regards,
Daniel