Expandir minha barra de realizações na Comunidade.

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

Esta conversa foi bloqueada devido à inatividade. Crie uma nova publicação.

SOLUCIONADO

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

Avatar

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 Solução aceita

Avatar

Resposta correta de
Level 2

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

Ver solução na publicação original

9 Respostas

Avatar

Employee Advisor

@TimStaub  Is it specific to a single form?

Avatar

Level 2
No, unfortunately it is happening on all Forms.

Avatar

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.

Avatar

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.

Avatar

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.

Avatar

Employee Advisor
Any update on Acrobat or vc++ libraries?

Avatar

Level 2
@Mayank_Gandhi Not to my knowledge. Would the libraries reside on the AEM servers? I can inquire with my Engineers.

Avatar

Resposta correta de
Level 2

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

Avatar

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...)