Inline images broken after SCP Upgrade
We suspect that this issue may arise if the migration schedule has not been run post-upgrade.
To troubleshoot this issue further, we kindly request the output of the following query.
Please connect to the database of the working build and execute the query below:
select * from globalconfig where category = 'InlineImageMigrationToCorrectLocation_SCP';
Kindly copy the output of the query to a notepad and send it to us for further analysis.
Additionally, we kindly request you to share the complete upgrade logs to facilitate a more thorough investigation.
You can conveniently upload the zipped log folder by following this link. Click log analysis and mention the ticket number while uploading the logs.
The logs folder is located under the following path:
<Drive:>/ManageEngine/SupportCenterPlus/logs
New to ADSelfService Plus?
Related Articles
Inline Images are Not Fetched Properly due to the IsInline Property 'false' assignment
About : For the customers using Microsoft Graph or EWS, Microsoft API returns isInline as "false" for inline images in some environment. There is no known reasons behind this behaviour from their documentation. One such possible reason for this ...Exception while Processing Inline Image with incorrect file name extension
Reference : #7938623, #8561970 Cause : Inline Images could not be processed with incorrect file name, for example "4d54308871ec465c8233d0f470db0308.do?sys_id=4fdfcb17475c1d50c594c133846d436a" . While constructing the filename in our end, the values ...SCP upgrade from 11.0 to 14.0 prerequisites
Before migration to scp version 14 below 2 points has to be done in scp 11027 1. Back up password should not be default i.e SCP123!, it should be updated 2. TLSv1, TLSv1.1 has to be added under the file /home/jre/lib/security/java.security file ( ...solution for postgres 11 upgrade issues
When Supportcenter Plus is upgraded to 14300 or later, postgres is also upgraded to 11.17. If you are using bundled postgres, data migration through pgdump and restore mechanism also happens. To ensure efficiency in Postgres 11.17, make sure your ...Error - Sanity Failed - Upgrade from 8121 to 11
While upgrading from 8121 to 11, after executing Updatemanager.bat and if the update fails, You need to check the Updatemanager logs in the path < Support Center Plus Application path -> Server-> Default-> Logs > . And if you find the below ...