Framemaker 10 trail install failure

Report · Jun 05, 2011

I am trying to decide between upgrading Framemaker 8 to FM 10 or migrating to Madcap Flare. I need to produce both print and web outputs and most of the documents are structured. I have lots of legacy FM files.

I downloaded and installed Flare without problems but found that it does not have runin paragraph styles and some of the FM features that allow styles to cross columns.

I tried to install FM but got error messages. I downloaded the Adobe installer diagnostic tool and it said there were conflicting programs to the FM installation but was not specific on what they were. Basically I went down the same route and had the same problems as mentioned in a similar post about Robohelp installation problems: http://forums.adobe.com/message/3422315

Unlike Madcap, Adobe support is pretty difficult to contact and it has taken literally days to fix problems with other adobe programs.

I am using a 2011 Macbook Pro using Bootcamp Win 7 64 bit home version. I also have parallels installed and can run FM 8 on either system. Acrobat Pro X is installed.

Here is the error log (edited to remove redundant line breaks):

Exit Code: 7

-------------------------------------- Summary --------------------------------------

- 0 fatal error(s), 16 error(s), 15 warning(s)

WARNING: PayloadPolicyNode.SetAction: IN payload {AC76D478-1031-0000-3478-000000000004} Adobe PDF Creation Add-On 9 is required by {3E6C41F9-8CDB-4358-9A9D-D34D0550750E} Adobe FrameMaker 10 but isn't free.

WARNING: Payload cannot be installed due to dependent operation failure

ERROR: The following payload errors were found during install:

ERROR: - Microsoft_VC90_ATL_x86: Install failed

ERROR: - Microsoft_VC80_ATL_x86: Install failed

ERROR: - Adobe Linguistics 5.1: Install failed

ERROR: - Adobe FrameMaker 10: Failed due to Language Pack installation failure

ERROR: - AdobeTypeSupport CS5: Install failed

ERROR: - Adobe FrameMaker 10_AdobeFrameMaker10_en_US: Install failed

ERROR: - Suite Shared Configuration CS5: Install failed

ERROR: - Adobe PDF Creation Add-On 9: Install failed

ERROR: - AdobePDFL CS5: Install failed

ERROR: - AdobeCMaps CS5: Install failed

ERROR: - Microsoft .NET Framework 3.0 (Please wait... This might take a while): Install failed

ERROR: - AdobeHelp: Install failed

ERROR: - AdobeJRE: Install failed

ERROR: - Adobe ExtendScript Toolkit CS5: Install failed

ERROR: - Adobe AIR: Install failed

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

Report · Jun 06, 2011

First of all, this should be in the Installation Issues topic, not the General Discussion; anyways, you're probably running into issues because you've already got Acrobat X installed. I wouldn't go messing around trying to install a trial version on my production environment - I would either find another machine to play around with or use the Adobe offer of a virtual machine hosted environment to try it out.

Report · Jun 06, 2011

I wouldn't go messing around trying to install a trial version on my production environment -

Specifically, unless Adobe declares that this doesn't happen ...

... a "successful" install of the trial version might turn some pre-existing licensed products into trial versions.

Report · Jun 06, 2011

I appreciate the advice. I am unable to demo FM 10 on another computer and had some specific issues of how it would work in Bootcamp and Parallels, that are only really testable by installing this on my computer. But the warning that it might corrupt FM 8 or Acrobat Pro are real concerns, as tech support with Adobe is problematic these days if things go wrong. One of the issues is if the trial will not install, if I pay the $700 to upgrade from version 8, will I be able to use it. That, I do not know.

Report · Jun 07, 2011

Hello IsleofGough

By looking up the errors that you are getting

Here are the steps that you can follow

1> Uninstall Framemaker 10 completely from your computer

2 >The place where you have extracted the .7z file in your computer, there you will find the setup.exe for Framemaker and there must be a Payloads folder

Inside this payloads folder you will find out Microsoft payloads like Microsoft_VC80_ATL_x86 and there will be around 7-8 of them

3> You need to open each one of these folders and inside these there will be exe with the same name, you need to double click on exe

4> Remove it, then double clik on exe once again to install it

5> The steps you can folow for all of such Microsoft_V__x exe files

6> Make sure that you just install only these 7-8 exe files, nothing else

7> Once you are done then run the setup. exe for Framemaker 10

Hope it will help to resolve your issue

If still you face the same issue, you can contact Adobe Support

Thanks

Vishal

Report · Jun 07, 2011

Vishal, could you tell us whether this solution is specific to running the install on a Mac under Bootcamp or parallels, or does it apply to installing on Windows in general?

Sheila

Report · Jun 07, 2011

Hello

If you are facing the same issue on Windows as well as in bootkemp running windows in Mac. This resolution works.

With using bootkemp in MAc , it created totally a Windows virtualization, so you can install Framemaker 10 on it and try this solution.

If you have a Windows based machine, and you are facing the same issue, then also you can try this solution

Thanks

Vishal

Report · Jun 07, 2011

Unfortunately it does not work. I tried using the two downloaded files to create a directory other than on the desktop as well (mentioned on another post) without success. I completely uninstalled FM 10 including prefs using the add/remove programs in the control panel. I rebooted. I went into the payload directory and removed and reinstalled all the microsoft items (for what it is worth, there were four VC80 and three VC90 files and they were all msi, not exe files). I tried reinstalling FM 10 and got the following error:

Exit Code: 7
-------------------------------------- Summary --------------------------------------
- 0 fatal error(s), 16 error(s), 15 warning(s)
WARNING: PayloadPolicyNode.SetAction: IN payload {AC76D478-1031-0000-3478-000000000004} Adobe PDF Creation Add-On 9 is required by {3E6C41F9-8CDB-4358-9A9D-D34D0550750E} Adobe FrameMaker 10 but isn't free.
WARNING: Payload cannot be installed due to dependent operation failure

WARNING: Payload cannot be installed due to dependent operation failure

ERROR: The following payload errors were found during install:

ERROR: - Microsoft_VC90_ATL_x86: Install failed

ERROR: - Microsoft_VC80_ATL_x86: Install failed

ERROR: - Adobe Linguistics 5.1: Install failed

ERROR: - Adobe FrameMaker 10: Failed due to Language Pack installation failure

ERROR: - AdobeTypeSupport CS5: Install failed

ERROR: - Adobe FrameMaker 10_AdobeFrameMaker10_en_US: Install failed

ERROR: - Suite Shared Configuration CS5: Install failed

ERROR: - Adobe PDF Creation Add-On 9: Install failed

ERROR: - AdobePDFL CS5: Install failed

ERROR: - AdobeCMaps CS5: Install failed

ERROR: - Microsoft .NET Framework 3.0 (Please wait... This might take a while): Install failed

ERROR: - AdobeHelp: Install failed

ERROR: - AdobeJRE: Install failed

ERROR: - Adobe ExtendScript Toolkit CS5: Install failed

ERROR: - Adobe AIR: Install failed

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

I am assuming from the above error that the primary problem is the language pack from FM 8. I share the reservations listed on this forum about messing with FM 8 and losing the license or functions by installing a trial. So it looks like (unlike previous versions of FM), this trial cannot be installed on my computer unless I am willing to remove FM 8.

Report · Jun 09, 2011

Hello,

I had a similar problem trying to install FrameMaker 10 from the TCS3 Trial on a PC Windows XP with SP3, and I confirm that it messed up the licensed and working FM8 installation from TCS1. To complete installation I had to un-install the whole TCS1, reboot, install the TCS3 and then re-install FM8 only from TCS1. The FM8 now works. The FM10 trial now crashes during start-up, while showing the splash screen: I can see in the message field that it finished loading "Font", it started "APE", and then it stopped. After a while the "Adobe Technical Communication Suite 3 Trial" appears asking to "CONTINUE TRIAL". This is probably a joke!

The error message I got is "Internal Error 10004, 7685768, 7686058, 10067517. FrameMaker has detected a serious problem and must quit", and when confirmed a successive "FrameMaker.exe - Application Error" appears saying that <the memory could not be "read">.

The "Adobe Technical Communication Suite 3 Trial" window continues to work and may be confirmed: of course, nothing happen then...

Acrobat X Pro, the Distiller and Photoshop CS5 Tryout, from the same TCS3 Trial, are working, so I decided that the problem is only FrameMaker, and that it's better to wait for a more stable release. I did not install the RoboHelp.

So I could complete the TCS3 install, but now I cannot start the FM10 application. I suspect that in my case there could be a problem with fonts, as suggested in other posts, because I have an old ATM and a big collection of TTF and OTF files. I will investigate a little more into that direction, at least for the "16 days remaining" of my trial.

Report · Jun 09, 2011

FM10's quite stable - it's the trying to install a trial version on a production machine that only leads to tears ;>)

Report · Jun 09, 2011

I was pretty sure I would upgrade to FM10 if it were stable. I downloaded the trial only after I had considered several alternatives over months: Word, InDesign, Scribus, LaTeX, and Flare. I'm not sure it was worth the $600 upgrade price from FM 8, but it was fairly seamless and everything is working. I've uninstalled FM 8 after converting the trial of FM 10 to a full version. I was aware that I might have had difficulties "testing" FM 10, but it worked for me.

For the projects on which I work, there really is no comparable product to FM. Word gets twitchy with many tables, complex numbering, and images even if one has a very strick way of working with absolutely no overrides and no use of books. InDesign suffers some instability with large documents despite its better typography and gets bloated. It also needs scripting workarounds and cludges for some of the things FM does natively. (I still preferentially use InDesign for short graphic intensive projects). Scribus was not powerful enough. LaTeX is great for mathematical equations but is always a struggle when one tries to substantially modify its templates. It also is not a "fun" working environment. I really wanted to like Flare. I think as a HAT tool, it may be better than FM, but there were not only problems in its interface and ability to pull FM projects over, but some issues with Word and pdf outputs (minor, but annoying none the less). Madcap is a much more responsive company for tech support than Adobe (don't shoot me for posting this on an Adobe forum), but it really is not as good a development tool for long documents (and there is not a structured FM environment equivalent within Flare).

So, for me, the stability of FM, the available of forums such as this for troubleshooting, and the fact it just works led me to stick with FM. Being able to download a fully functional trial was a decided plus.

Report · Jun 09, 2011

... Word, InDesign, Scribus, LaTeX, and Flare ...

What? You didn't consider troff or Interleaf (by whatever name now known)?

I hear [t|g|un]roff even has Unicode support now.

... is a much more responsive company for tech support than Adobe ...

All seriousness aside, if the project or enterprise workplan requires reliable, responsive, vendor support, that is a real factor in the decision, as is their roadmap for the product.

______

Speaking of which, has Adobe said anything about a release map after 10?

The Adobe India operation does, at least, seem to be more than just a

"dead software division" (which, alas, was the case for another company I worked for).

Report · Jun 12, 2011

Some of the benefits of Flare are really half way between unstructured and structured Framemaker: everything fits nicely into xml format but one does not have the ability to define what types of paragraphs/elements are allowed in a certain region in the document the way one does in a structured Framemaker EDD.

One thing that Flare has that Framemaker doesn't that is very useful is the ability in one project to have definitions for multiple outputs.For instance, Flare uses topics instead of files in its compilations (kind of like the book feature in Framemaker, but topics generally are only 2-4 pages). In Flare one can have multiple book like compilations intended for different outputs (manuals for different regions or audiences or for print vs web) in one project. But Flare goes beyond FM to also specify what conditional paragraphs will be used in different outputs and different user variables in different outputs. I think that particular feature is well beyond FM.

I am hoping in the future, either Flare adds better formatting like Framemaker, or Framemaker adds this multiple export feature.

Report · Jun 08, 2011

Solved by deleting common/adobe/installation files, uninstalling FM10, and moving the directories created from the downloaded files to c:\Frame10 (not a user subdirectory, which apparently was the issue)