Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Adobe Experience Manager - Forms v6.3.0. Crashing on Preview

TimStaub
Level 2
Level 2

Good Afternoon,

AEM Designer keeps crashing on me whenever I attempt to preview PDF for a second time.  This issue started on/or about Thursday November 5, 2020. My Preview xml file has been verified as good.  The Data Connection Schema is also healthy with no errors.  My log will sho Generating PDF Document...PDF generated successfully, after the first preview.  If I attempt to preview a second time Designer closes.

 

Hoping someone may have any insights.

1 Accepted Solution
TimStaub
Correct answer by
Level 2
Level 2

Well this issue has somehow miraculously fixed itself.  Don't know how or why but Designer is no longer crashing on Preview. 

View solution in original post

9 Replies
Kosta_Prokopiu1
Employee
Employee
@Mayank_Gandhi - same happened here - until a few weeks ago everything fine - now crash with every second Preview. Could not yet establish what is wrong. I did not install any new versions of Acrobat and Designer.
TimStaub
Level 2
Level 2
@Mayank_Gandhi Do you have any idea's. We even replaced my laptop as we thought there was an issue with high cpu usage.
TimStaub
Level 2
Level 2
@Mayank_Gandhi Can you direct me to where I can find error logs? We have looked in Event view but have not been able to find anything there.
TimStaub
Level 2
Level 2
@Mayank_Gandhi Not to my knowledge. Would the libraries reside on the AEM servers? I can inquire with my Engineers.
TimStaub
Correct answer by
Level 2
Level 2

Well this issue has somehow miraculously fixed itself.  Don't know how or why but Designer is no longer crashing on Preview. 

View solution in original post

Kosta_Prokopiu1
Employee
Employee
🙂 yes, it has fixed itself (well, I guess this might have been some certificate issue or some Windows related problem that might have gone away after an update - who knows...)