Livecycle Designer Error- everytime I open FORMS-HELP!

OK, at least in my case, the problem seems to be triggered by the persisted toolbar state in the registry.



Ive created a work around that lets me run Livecycle Designer without the crash:



1. Create a file called resetDesigner.reg that contains these 3 lines. Note that the second blank line is required.



Windows Registry Editor Version 5.00



[-HKEY_CURRENT_USER\Software\Adobe\Designer\8.2\ToolBarsEN178]



2. Create a command file called, resetDesigner.cmd to run it, containing 1 line:

regedit /s "C:\Program Files\Adobe\Acrobat 9.0\Designer 8.2\resetDesigner.reg"



3. Place a shortcut to the command file on the desktop

4. Click the icon created in #3 before launching Livecycle Designer to remove the saved toolbar state from the registry.



I have to reset the layout of the IDE each time, but at least I can run Designer again.



Sheldon

Has anyone else here installed any special fonts?? I received a font from Adobe, Sanvito Pro, for registering the new version. I had it installed on my laptop, which is the first system to blow up. I started editing on my desktop and all was fine, then i realized i didnt' have one of the fonts i was using, and installed on my desktop. (I was in MS word at that time.) After going back to my form, later, Live designer blew up on my desktop. I just realized this could be the issue!??

I may have discovered the problem... I was editing forms on my notebook when suddenly the program blew up-same error as all above. I'm on Vista ultimate, sp1. My Live Cycle is an upgrade in the CS4 design premium set. I started w/ Photoshop 4 or 5 a million years ago!! None of that matters, though.



After my notebook wouldn't run Live Cycle, I went to my desktop system. All was fine in Live Cycle. In MS Word, I was working on a document, and needed a font not installed. I got this font from Adobe, as a "gift" for registering my product (CS4). It is Sanvito Pro... I installed the font on my desktop and finished my word doc.



Later, I went back to Live Cycle, to finish the form and POW. Blew up when I tried to open the form I edited earlier without issue. I just put this together as I was looking at the various files in the user folders in Vista. I noticed a file AdobeSystemFontCache.lst and this triggered the memory of installing the font, just before the blow up on this computer. Did anyone else install this font, or any other, then experience the blow up??

Yes I remember installing the "gift" font but did not connect the two events. I too am on Vista Ultimate SP1 and none of the workarounds have worked for me. So I am not sure of the causality of that font. I do know that I might used it once or twice but at the time I stayed with the default in LS because I was a newbie and was looking at some serious deadlines.



So now that you might have found the problem keep us posted on the solution as and when you find it. It is a real drag having to work on a desktop that has nothing else running but LiveCycle and shuttling files.

I tried uninstalling the font without any change. I then went to C:\Users\*your name*\AppData\Roaming\Adobe\Designer\8.2 and tried editing some of the font files which had many notations of invalid font... no luck. I then deleted the 8.2 folder above which is located in a different place in XP... this seems to have fixed the trouble.



I compared the 8.2 folders before (when it was not working) and after (when the program created the files fresh) and there are only 3 files that are different. I'll save this in case it crashes again, then i'll see if there is a common denominator, so only the offending file will need to be deleted, possibly, saving customizations I hope!



I'm also going to go downstairs to my desktop and see if the "fix" works without uninstalling the Sanvito Pro font. I'll post again then.

After LiveCycle Designer crashed, I have got from VistaSP1 the following notice:



Follow the steps in the Knowledge Base (KB) article to solve the problem with the Microsoft Visual Studio mfc80u.dll or mfc80.dll module

This problem was caused by the Microsoft Visual Studio mfc80u.dll or mfc80.dll module, which was created by Microsoft Corporation.

Solution

--------------------------------------------------------------------------------

To fix this problem, follow the steps in this online Microsoft Support Knowledge Base (KB) article:

KB961894: An application crashes after you install a product that updates the Mfc80.dll or Mfc80u.dll module

problem.



After installing the MS Hotfix from the MS support site (vcredist_x86.exe) LiveCycleDesigner runs without problems

[q]After installing the MS Hotfix from the MS support site (vcredist_x86.exe) LiveCycleDesigner runs without problems[/q]



I am experiencing a similar issue. I previously installed this fix and have had now problems since ... until today. I installed an evaluation version of CommonLook 4.1 which included a vcredist_x86.exe of its own (I discovered this after installation). The issue I am running into now is when attempting to open or create any document in LiveCycle (8.2.1) it crashes. Note that I can start LiveCycle without any problem. The crash occurs when attempting to create or open a document. I have tried applying the fix (several times before and after uninstalling CommonLook 4.1) discussed above but it does not address the issue.



Has anyone else experienced this or the like and if so were you able to address the issue without a reinstall of Acrobat/LiveCycle (I'm still reserving this as a last resort)?

Well after much searching with no answers I started exploring possibilities. I noticed that This seemed only to occur when running LiveCycle under my user account and that it did not crash when running with Admin privileges. What finally fixed the issue for me was going into the C:\Documents and Settings\#username#\Application Data\Adobe\Designer directory and removing the 8.0 and 8.2 directories. Of course this seems to have forced LiveCycle to recreate all the necessary default files there. Low and behold all seems to be good again. *shrug* Oh well. I hope this is helpful to others that may find themselves with a similar situation.