Structured FrameMaker failure on startup

[Scott Prentice]

Wow .. Alan .. that's a good one. If this was April 1, I'd think you 
were joking.

I can't imagine what would affect both FM11 and FM12 simultaneously. 
FM10 is OK? Are these part of a Tech Com Suite or standalone programs? 
To me that indicates that the problem lies in some shared resource of 
some kind. I know there is some sharing of resources .. but have no idea 
what they are. I assume you've rebooted the VM?

Maybe Creative Cloud has gone haywire (naw), and attacked some FM resources?

I have a feeling that you'll need to push this to Adobe .. someone on 
the FM dev team might have some ideas.

I hate to say it but you may need to reinstall.

...scott

On 6/19/14 8:25 AM, Alan Houser wrote:
> Hi All,
>
> Windows 7 running on MacOS/Parallels; FM 11 and 12 fully patched.
>
> I'm getting immediate failure of structured Framemaker 11 and 12 on 
> startup. ("Internal Error ... FrameMaker has detected a serious 
> problem and must quit").
>
> The apps start fine in unstructured mode.
>
> I've tried:
> - Removing the user-specific ini files 
> ($HOME/AppData/Roaming/Adobe/FrameMaker)
> - Disable all third-party plugins
> - Disable "LoadStartupScripts" setting in maker.ini
>
> This happened suddenly; I don't know what might have triggered it.
>
> Any ideas?
>
> -Alan
> -- 
> Alan Houser
> Group Wellesley, Inc.
> Consultant and Trainer, Technical Publishing
> arh on Twitter
> 412-450-0532
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20140619/f2f3174b/attachment.htm>