RE: Disable app or fix corresponding tables for marketplace app "Liferay In

Dominik Kern, modified 5 Years ago. New Member Posts: 5 Join Date: 11/10/17 Recent Posts
We are currently upgrading Liferay Portal from 6.1.20-ee-ga2 to 7.2.10-fp3.

After database migration from 6.1 to 7.1, I see following error on startup:
2019-11-29 14:45:39.276 ERROR [Portal Dependency Manager Component Executor--1][JDBCExceptionReporter:234] Incorrect string value: '\xC2\x80\xC2\x99s ...' for column 'description' at row 1
2019-11-29 14:45:39.286 ERROR [Portal Dependency Manager Component Executor--1][LPKGDeployerRegistrar:185] Unable to track installed app Liferay Collaboration - Liferay Invite Members - Impl with Marketplace
org.hibernate.exception.GenericJDBCException: Could not execute JDBC batch update
        at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:140)
        at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:128)
        ...
        (same for API, whole stacktrace attached)

I thought the upgrade tool was not able to upgrade some tables but there are no modules left when I execute gogo shell with upgrade:check. And furthermore I am able to deploy the app via widget control panel , its working so far.

So I tried to find the broken table but the log is not really helpful. There are too many tables with the column 'description'. If someone knows where this incorrect string values lies, please give me a hint.

Since we dont need this app anyway, I tried to deactivate it with a com.liferay.portal.bundle.blacklist.internal.BundleBlacklistConfiguration.config file containing the blacklisted bundle name. Now the module disappears from the widgets control panel but the error still appears on startup.

Is there a possibility to configure this "Portal Dependency Manager Component Executor" to not start "Liferay Invite Members" app?

I would be super happy if someone can help me fix this issue.
thumbnail
David H Nebinger, modified 5 Years ago. Liferay Legend Posts: 14933 Join Date: 9/2/06 Recent Posts
Those \xXXX things are all UTF8 char strings.

I don't know how you created your database and/or column, but it looks like something is trying to evaluate UTF8 as straight-up string instead of UTF8.
Dominik Kern, modified 5 Years ago. New Member Posts: 5 Join Date: 11/10/17 Recent Posts
Some tables were actually in the wrong character set. I fixed them and now it works. Thank you very much!
I guess because this database is currently running on liferay 6.1, I never had the idea that the tables could be in the wrong character set. Its strange that nobody noticed that before.