ybuffetaud
Active Member
We had the case yesterday but there was no temp folder. So Adobe isn't the only responsible.Today, temp folders are recreated, and the problem occurred again...
Oracle says to contact Adobe...
We had the case yesterday but there was no temp folder. So Adobe isn't the only responsible.Today, temp folders are recreated, and the problem occurred again...
Oracle says to contact Adobe...
We are seeing this with more users as well, using JDE and Chrome. We have tried ALL of Oracle's recommendations and the issue still occurs.did anyone have found a solution we have more and more users having this problem right now...
I also tried this workaround without successThe SR is still opened at Oracle.
Last answer was :
Can you please test the below with any one customer and let us know the result:
* C:\Users\%userprofile%\appdata\local\adobe\acrobat\DC\cache and renaming the AcroFnt21.lst file.
* Rename the file to AcroFnt21_old.lst
* Clear the browser cookies & cache from all time, restart the browser
* Retest the issue.
But on a workstation, this procedure didn't work, and the client needed to reboot the workstation after that.
We do not have any users on Win 11. We're seeing this issue on Win 10 Enterprise LTSB ver 1607 and Win 10 Enterprise LTSC ver 1809.The suggested resolution above has not worked.
Out of curiosity, has anyone seen this issue in Windows 11? Users in our org affected by this are running Windows 10.
Unfortunately yes, the organization I work for is also seeing this issue on Windows 11.The suggested resolution above has not worked.
Out of curiosity, has anyone seen this issue in Windows 11? Users in our org affected by this are running Windows 10.
We tried this at my organization and unfortunately it did not solve our issue.Hi when this is happening to someone, we are installing again acrobat DC on users laptop and this is solving the problem
We have been able to replicate this issue on demand. So we've began testing this on a few test subjects in my org. After disabling the service and removing the temp files, the issue instantly resolved itself without a reboot. Regardless, we rebooted for good measure. After the fact, the test subject was unable to replicate the issue on demand. Finally seeing some light at the end of the tunnel for this issue. We will continue to monitor and report back if anything changes.New porcess given by Oracle :
1. Disable the "Windows Font Cache Service" service.
It is not enough just to stop it, you need to disable it. Chrome, Firefox, Edge and Acrobat Reader will start this service if it is still enabled and only stopped.
2. Make sure there is no temporary file under
C:\Users\Username\AppData\Local\Temp\acrord32_sbx
C:\Users\Username\AppData\Local\Temp\acrord32_super_sbx
3. Restart machine and monitor behavior
Users were prematurely exiting JD Edwards. User would exit the browser without properly signing out and/or allowing their system to go into sleep mode with a JD Edwards session open. Once the user would close the browser, re-open the browser, and navigate back to JD Edwards, the session remained logged in by the user and the characters were updated to the "garbage characters". Several users conducted this practice and the outcome was the same for each user.How have you been able to replicate this issue?
Thank you
I tried that with varied success. On some, it worked, but not on others. So, sadly, I would say this is not the final solution.Hi when this is happening to someone, we are installing again acrobat DC on users laptop and this is solving the problem
We are still testing this solution in non prod but at this time it appears to be working for us.We have an SR with Oracle and were just offered this solution:
We have an update from the developers assigned to the case:
"@ For JAS this is how customer may change (if they will like the Helvetica
@ font!), please follow the below steps.
@ .
@ 1). Edit webclient.css from
@ <E1Agent_Home>/SCFHA/targets/<JAS_Instance_Name>/owl_deployment/webclient.ear/
@ app/webclient.war/share/css
@ 2). change from font-family: Arial, Helvetica, sans-serif; to font-family:
@ Helvetica, Arial, sans-serif;
@ 3) Save the changes.
@ The Server Manager Agent install location and the JAS HTML Server instance
@ name can be determined from the Server Manager ?Management Dashboard? screen.
@ .
@ If customer is on Weblogic, stop the JAS instance and then delete the content
@ stage folder from
@ <MW_Home>/user_projects/domains/<WLS_Domain_Name>/servers/<J2EE_Server>/stage
@ .
@ 4) Sign on to the WebLogic management console and select the ?Deployments?
@ link on the left side of the screen.
@ .
@ 5) If your WebLogic Server is running in production mode, click the ?Lock &
@ Edit? button in the upper left corner of the screen.
@ .
@ 6) Select the JAS HTML deployment that you want to update by clicking the
@ check box next to that deployed application.
@ .
@ 7) Click the ?Update? button above the list of deployments. Follow the
@ prompts to complete the update (clicking ?Finish? from the next screen should
@ accomplish this). These steps will cause the EnterpriseOne HTML application
@ to be restarted with the new CSS file.
@ .
@ 8) Click the ?Activate Changes? button.
@ .
@ 9) If your WebLogic Server is running in production mode, click the ?Release
@ Configuration? button in the upper left corner of the screen.
@ .
@ At this point, the application should be restarted, and the updates should be
@ active.
@ .
@ Note: You may need to refresh your browser cache to ensure the updated file
@ is loaded
@ .
@ 10) Start the JAS instance and re-test this issue.
@ .
@ .
@ For websphere follow the below steps:
@ .
@
@ 1. Edit webclient.css from
@ <E1Agent_Home>/SCFHA/targets/<JAS_Instance_Name>/owl_deployment/webclient.ear/
@ app/webclient.war/share/css
@ 2. change from font-family: Arial, Helvetica, sans-serif; to font-family:
@ Helvetica, Arial, sans-serif;
@ 3. Save the changes.
@ 4. Now open the Websphere container staging directory. Edit webclient.css
@ from
@ ?<IBM_WebSphere_InstallFolder>\AppServer\profiles\<profileName>\installedApps\
@ <NodeCell>\<JASInstanceName>\webclient.war\share\css
@ 5. change from font-family: Arial, Helvetica, sans-serif; to font-family:
@ Helvetica, Arial, sans-serif;
@ 6. Save the changes.
@ 7. Start the JAS instance and re-test this issue.
Our hosting provider is applying the solution to non prod tonight. Has anyone else tried this?
We did find it to be necessary to bounce any web servers for the fix to apply.We are still testing this solution in non prod but at this time it appears to be working for us.
We use essential cookies to make this site work, and optional cookies to enhance your experience.