Generating Printed Documents

Hello, I have 2 questions about generating printed doc:
1 - when I generate a .doc file the total of pages in the
screen is not the same as in the printed document . I have only the
odd pages printed. The even ones are not even shown on the screen
but they are counted in the total of pages.
2 - when trying to do a .pdf file the result is a .doc and in
the screen I can see the even pages (in blank).
I don't see anything wrong in my selections when generating
the printed documents but something is not working.
Thanks for any hint you can give me.
Beatriz.

Beatiz
The PDF issue I've come across myself occasionally (not all
the time) when I use the RoboPDF to generate PDF output from the
Word document. If you save the PDF file and then re-open it from
explorer, the content is actually there (as long as there was
content in the Word document).
With the page numbering, it sounds like section breaks have
been inserted and each section is being told to start on an odd
page. Just a couple of questions:
Do each of your topics start on a new page?
Also, do any of the topics extend over more than one page?
Lastly, have you added any topics in the Section Layout
screen of the Printed Documentation wizard?
Regards

Similar Messages

  • How to generate printed document with "continuous" section breaks versus "next page" section breaks?

    When generating a Word or PDF document from the HTML help files a "next page" section break is used after each topic. How can I get a "continuous" section break instead?

    I've been poking around a bit more. Here's the deal.
    New chapters will always start on a new page and have a next or odd page break according to the Start New Chapters setting. If ticked it will be an Odd Page break, else a Next Page break.
    Topics within a book will follow the Start Each Topic on a New Page setting. If ticked, each topic will be separated by a page break, not a section break. Else they will be on the same page with no breaks of any type.
    Topics not within a book will be followed by a section break.
    So section breaks are only created for chapters and topics not in a chapter.
    Hope that helps. Please post back if you find otherwise.
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Unable to Generate Printed Documentation in PDF Format

    This past week I started having a consistent error when attempting to generate a Printed Documentation layout. This error reads "Internal error encountered,  Failed to generate Printed Documentation."  Prior Printed Documentation builds on this same project completed fine. Nothing was done to the Help project between the times when this worked and when it no longer was able to create Printed Documentation.
    I receive this error even if I generate an entirely new "blank project" build, and then attempt to create a Printed Documentation build from this new blank project.  Researching this error, I see this has been a reoccuring problem with this product for some time. The few threads that list the problem as having been "fixed" provide resolution steps that have not worked in my case. Right now I am waiting for our IT Helpdesk people to re-install the Suite. Hopefully this will resolve this problem.
    Additional information on this problem - PDF Printed Documentation is failing - the HTML build works fine. If I select just a .DOC Printed Documentation output, this also works correctly. The resulting Word document looks good, although hyperlinks do not work within this Word document. I have reloaded Office 2003 as a troubleshooting effort, but this has nbot resulted in any change in symptoms.
    The entire error text is enclosed below, although several other people have also done this in past entries. The few lines that read "Warning, and then report a style issue is NOT the problem here. As stated earlier, when I do this same Printed Documentation build on an entirely new "blank project" it does not work, and the Output text in that case does not contain any such "Warnings" about Styles.
    Error text below:
    Starting to build Printed Documentation...
    Printed Documentation processor 8.0.1.204
    Building C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.doc ...
    Preparing to create Printed Documentation...
    Clearing output folder...
    Preparing files for Print Document...
    Copying files...
    Updating files...
    Finished preparing in 2 seconds.
    Preparing environment...
    Printed Document Generator Environment: Word 11.0.8313,  OS 5.1.2600, RAM 2048 M Bytes
    Building Printed Documentation 'Printed Documentation'...
    Building Single Document 'Printed_Documentation.doc'...
    Building 'RF-7800V-HH About this Help'...
    Building 'Table of Contents'...
    Preparing to build chapters...
    Building 'RF-7800V-HH Help and Support'...
    Processing 'RF-7800V-HH Welcome'...
    Building 'RF-7800V-HH RSP Help'...
    Processing 'RF-7800V-HH Station Information'...
    Building 'RF-7800V-HH Features'...
    Processing 'RF-7800V-HH Features'...
    Processing 'RF-7800V-HH Anc. Connector Mode'...
    Processing 'RF-7800V-HH No-Sync Beeps'...
    Processing 'RF-7800V-HH Power Management'...
    Processing 'RF-7800V-HH Retransmit'...
    Processing 'RF-7800V-HH USB Mode'...
    Processing 'RF-7800V-HH Broadcast Gateway'...
    Processing 'RF-7800V-HH IP Routing'...
    Processing 'RF-7800V-HH Voice Settings'...
    Processing 'RF-7800V-HH Time and Date Settings'...
    Processing 'RF-7800V-HH Position Reporting'...
    Processing 'RF-7800V-HH User Interfaces'...
    Processing 'RF-7800V-HH Net Switches'...
    Processing 'RF-7800V-HH Ethernet Interface'...
    Building 'RF-7800V-HH Global Settings'...
    Processing 'RF-7800V-HH Global Settings'...
    Processing 'RF-7800V-HH Radio Passwords'...
    Processing 'RF-7800V-HH GPS'...
    Processing 'RF-7800V-HH Locksets'...
    Building 'RF-7800V-HH Network Types'...
    Processing 'RF-7800V-HH Network Types'...
    Building 'RF-7800V-HH Fixed Frequency LOS'...
    Processing 'General Information - Fixed Frequency LOS'...
    Processing 'RF-7800V-HH FF Network Information'...
    Processing 'RF-7800V-HH FF Preset'...
    Processing 'RF-7800V-HH FF General'...
    Processing 'RF-7800V-HH FF Comsec'...
    Processing 'RF-7800V-HH FF Data-Voice'...
    Processing 'RF-7800V-HH FF Squelch'...
    Processing 'RF-7800V-HH FF Advanced'...
    Warning: style (p.Heading7) is not defined and will be mapped to 'Normal'.
    Building 'RF-7800V-HH Quicklook'...
    Processing 'General Information - Quicklook'...
    Processing 'Hopset Creation - Quicklook'...
    Processing 'RF-7800V-HH QL Network Information'...
    Processing 'RF-7800V-HH QL Preset'...
    Processing 'RF-7800V-HH QL General'...
    Processing 'RF-7800V-HH QL Comsec'...
    Processing 'RF-7800V-HH QL Data-Voice'...
    Processing 'RF-7800V-HH QL Advanced'...
    Building 'RF-7800V-HH Sample Plans'...
    Processing 'General Information - Sample Plans'...
    Processing 'Simple Fixed and Quicklook Nets'...
    Processing 'Single Fixed and Quicklook Nets'...
    Processing 'RF-7800V-HH Manage Keys'...
    Processing 'RF-7800V-HH Program Radio'...
    Building 'RF-7800V-HH Tech Support'...
    Processing 'RF-7800V-HH Technical Support'...
    Processing 'RF-7800V-HH Radio Firmware Compatibility'...
    Building 'FAQs'...
    Processing 'RF-7800V-HH FAQ Index'...
    Processing 'FAQ 01'...
    Warning: style (span.strong) is not defined and will be removed.
    Warning: style (p.para) is not defined and will be mapped to 'Normal'.
    Processing 'FAQ 02'...
    Processing 'FAQ 03'...
    Processing 'FAQ 04'...
    Processing 'FAQ 05'...
    Processing 'RF-7800V-HH Glossary'...
    Warning: style (p.FM_CellRowHead) is not defined and will be mapped to 'Normal'.
    Warning: style (span.Glossary) is not defined and will be removed.
    Warning: style (p.FM_CellBodyLeft) is not defined and will be mapped to 'Normal'.
    Warning: style (p.FM_GLOSSARY) is not defined and will be mapped to 'Normal'.
    Warning: style (p.FM_Para) is not defined and will be mapped to 'Normal'.
    Completed building chapters...
    Building 'Index'...
    Updating list paragraphs...
    Updating images...
    Updating page numbers...
    Updating page headers...
    Updating Table of Contents...
    Updating Index...
    Saving 'Printed_Documentation.doc'...
    Generating 'Printed_Documentation.pdf'...
    Failed the generate PDF file 'C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.pdf'...
    Failed to save 'Printed_Documentation.doc'...
    Cleaning up temporary files...
    I am pretty sure nobody will have any fix suggestions that work to solve this problem, but I am making this entry for historical purposes. I will add an entry stating whether the Suite reload resolves this issue.
    Thanks,
    Tim C @ Harris

    If I select ONLY the Word DOC Output format in the Printed Documentation
    setup, the output is created without an error (output text below).  Links do work within
    this Word document (a symptom change since installing patch 8.0.2).
    When I use this Word document to create a PDF (using the Adobe PDF
    printer driver) a PDF is successfully created, however no bookmarks are
    created in the bookmarks panel and none of the links in this PDF work
    (although they are created looking like they will work, i.e., blue
    underlined text).
    Regards,
    Tim
    ------------- Output Text --------------------------
    Starting to build Printed Documentation...
    Printed Documentation processor 8.0.1.204
    Building C:\Documents and Settings\tcleary\My Documents\My RoboHelp Projects\Adobe RoboHelp 8\10515-0366-5004_7800v-hh rsp\!SSL!\Printed_Documentation.doc ...
    Preparing to create Printed Documentation...
    Clearing output folder...
    Preparing files for Print Document...
    Copying files...
    Updating files...
    Finished preparing in 3 seconds.
    Preparing environment...
    Printed Document Generator Environment: Word 11.0.8313,  OS 5.1.2600, RAM 2048 M Bytes
    Building Printed Documentation 'Printed Documentation'...
    Building Single Document 'Printed_Documentation.doc'...
    Building 'RF-7800V-HH About this Help'...
    Building 'Table of Contents'...
    Preparing to build chapters...
    Building 'RF-7800V-HH Help and Support'...
    Processing 'RF-7800V-HH Welcome'...
    Building 'RF-7800V-HH RSP Help'...
    Processing 'RF-7800V-HH Station Information'...
    Building 'RF-7800V-HH Features'...
    Processing 'RF-7800V-HH Features'...
    Processing 'RF-7800V-HH Anc. Connector Mode'...
    Processing 'RF-7800V-HH No-Sync Beeps'...
    Processing 'RF-7800V-HH Power Management'...
    Processing 'RF-7800V-HH Retransmit'...
    Processing 'RF-7800V-HH USB Mode'...
    Processing 'RF-7800V-HH Broadcast Gateway'...
    Processing 'RF-7800V-HH IP Routing'...
    Processing 'RF-7800V-HH Voice Settings'...
    Processing 'RF-7800V-HH Time and Date Settings'...
    Processing 'RF-7800V-HH Position Reporting'...
    Processing 'RF-7800V-HH User Interfaces'...
    Processing 'RF-7800V-HH Net Switches'...
    Processing 'RF-7800V-HH Ethernet Interface'...
    Building 'RF-7800V-HH Global Settings'...
    Processing 'RF-7800V-HH Global Settings'...
    Processing 'RF-7800V-HH Radio Passwords'...
    Processing 'RF-7800V-HH GPS'...
    Processing 'RF-7800V-HH Locksets'...
    Building 'RF-7800V-HH Network Types'...
    Processing 'RF-7800V-HH Network Types'...
    Building 'RF-7800V-HH Fixed Frequency LOS'...
    Processing 'General Information - Fixed Frequency LOS'...
    Processing 'RF-7800V-HH FF Network Information'...
    Processing 'RF-7800V-HH FF Preset'...
    Processing 'RF-7800V-HH FF General'...
    Processing 'RF-7800V-HH FF Comsec'...
    Processing 'RF-7800V-HH FF Data-Voice'...
    Processing 'RF-7800V-HH FF Squelch'...
    Processing 'RF-7800V-HH FF Advanced'...
    Warning: style (p.Heading7) is not defined and will be mapped to 'Normal'.
    Building 'RF-7800V-HH Quicklook'...
    Processing 'General Information - Quicklook'...
    Processing 'Hopset Creation - Quicklook'...
    Processing 'RF-7800V-HH QL Network Information'...
    Processing 'RF-7800V-HH QL Preset'...
    Processing 'RF-7800V-HH QL General'...
    Processing 'RF-7800V-HH QL Comsec'...
    Processing 'RF-7800V-HH QL Data-Voice'...
    Processing 'RF-7800V-HH QL Advanced'...
    Building 'RF-7800V-HH Sample Plans'...
    Processing 'General Information - Sample Plans'...
    Processing 'Simple Fixed and Quicklook Nets'...
    Processing 'Single Fixed and Quicklook Nets'...
    Processing 'RF-7800V-HH Manage Keys'...
    Processing 'RF-7800V-HH Program Radio'...
    Building 'RF-7800V-HH Tech Support'...
    Processing 'RF-7800V-HH Technical Support'...
    Processing 'RF-7800V-HH Radio Firmware Compatibility'...
    Building 'FAQs'...
    Processing 'RF-7800V-HH FAQ Index'...
    Processing 'FAQ 01'...
    Warning: style (span.strong) is not defined and will be removed.
    Warning: style (p.para) is not defined and will be mapped to 'Normal'.
    Processing 'FAQ 02'...
    Processing 'FAQ 03'...
    Processing 'FAQ 04'...
    Processing 'FAQ 05'...
    Building 'RF-7800V-HH Glossary'...
    Warning: style (p.FM_CellRowHead) is not defined and will be mapped to 'Normal'.
    Warning: style (span.Glossary) is not defined and will be removed.
    Warning: style (p.FM_CellBodyLeft) is not defined and will be mapped to 'Normal'.
    Warning: style (p.FM_GLOSSARY) is not defined and will be mapped to 'Normal'.
    Warning: style (p.FM_Para) is not defined and will be mapped to 'Normal'.
    Completed building chapters...
    Building 'Index'...
    Updating list paragraphs...
    Updating images...
    Updating page numbers...
    Updating page headers...
    Updating Table of Contents...
    Updating Index...
    Saving 'Printed_Documentation.doc'...
    Completed building Printed Documentation...
    Preparing output directory...
    Cleaning up temporary files...
    Finished Printed Documentation generation in 5 minutes 36 seconds.
    Building Printed Documentation complete.

  • Error while generating PDF document

    I am using RH 8 and cannot generate a Printed PDF document.
    here is the error message output
    Warning: style (p.Table) is not defined and will be mapped to 'Normal'.
    Processing 'Setting-up and Assigning Roles'...
    Warning: The Word Document became corrupt when attempting to append following malformed topics:
    TimeTEQ\Chapter1-Administration_Functions\First_Topic.htm
    TimeTEQ\Chapter1-Administration_Functions\SettingUp_the_Parent_Organisation.htm
    TimeTEQ\Chapter1-Administration_Functions\Setting_up_and_Assigning_Sites.htm
    TimeTEQ\Chapter1-Administration_Functions\Setting_Up_Departments.htm
    TimeTEQ\Chapter1-Administration_Functions\Setting_Up_and_Assigning_Roles.htm
    Failed to build 'TimeTEQ'...
    Failed to build one or more chapters.
    Building 'Glossary'...
    Failed to build 'Glossary'...
    Building 'Index'...
    Updating list paragraphs...
    Updating images...
    Updating page numbers...
    Updating page headers...
    Updating Table of Contents...
    Updating Index...
    Saving 'Printed_Documentation.doc'...
    Generating 'Printed_Documentation.pdf'...
    Failed the generate PDF file 'C:\TimeTeq_Documentation_Aug2009\TimeTEQ_OldHelp\user guide\Timteq_test_project\!SSL!\Printed_Documentation\Printed_Documentation.pdf'...
    Failed to save 'Printed_Documentation.doc'...
    Cleaning up temporary files...
    Internal error encountered,  Failed to generate Printed Documentation.
    Starting to build Printed Documentation...
    Printed Documentation processor 8.0.0.203
    Building C:\TimeTeq_Documentation_Aug2009\TimeTEQ_OldHelp\user guide\Timteq_test_project\!SSL!\Printed_Documentation\Printed_Documentation.doc ...
    Preparing to create Printed Documentation...
    Clearing output folder...
    Preparing files for Print Document...
    Copying files...
    Updating files...
    Finished preparing in 0 seconds.
    Preparing environment...
    Printed Document Generator Environment: Word 11.0.5604,  OS 5.1.2600, RAM 768 M Bytes
    Building Printed Documentation 'Printed Documentation'...
    Building Single Document 'Printed_Documentation.doc'...
    Building 'Title Page'...
    Building 'Table of Contents'...
    Preparing to build chapters...
    Building 'TimeTEQ'...
    Building 'Chapter1-Administration Functions'...
    Processing 'Overview- Understanding Sites, Departments & Roles'...
    Processing 'Setting-up a Site Group'...
    Processing 'Setting up a Site'...
    Processing 'Setting-up and Assigning Departments'...
    Warning: style (p.Body_Text) is not defined and will be mapped to 'Normal'.
    Warning: style (p.Step2) is not defined and will be mapped to 'Normal'.
    Warning: style (p.Step) is not defined and will be mapped to 'Normal'.
    Warning: style (p.spacer) is not defined and will be mapped to 'Normal'.
    Warning: style (p.Tableheader) is not defined and will be mapped to 'Normal'.
    Warning: style (p.Table) is not defined and will be mapped to 'Normal'.
    Processing 'Setting-up and Assigning Roles'...
    Warning: The Word Document became corrupt when attempting to append following malformed topics:
    TimeTEQ\Chapter1-Administration_Functions\First_Topic.htm
    TimeTEQ\Chapter1-Administration_Functions\SettingUp_the_Parent_Organisation.htm
    TimeTEQ\Chapter1-Administration_Functions\Setting_up_and_Assigning_Sites.htm
    TimeTEQ\Chapter1-Administration_Functions\Setting_Up_Departments.htm
    TimeTEQ\Chapter1-Administration_Functions\Setting_Up_and_Assigning_Roles.htm
    Failed to build 'TimeTEQ'...
    Failed to build one or more chapters.
    Building 'Glossary'...
    Failed to build 'Glossary'...
    Building 'Index'...
    Updating list paragraphs...
    Updating images...
    Updating page numbers...
    Updating page headers...
    Updating Table of Contents...
    Updating Index...
    Saving 'Printed_Documentation.doc'...
    Generating 'Printed_Documentation.pdf'...
    Failed the generate PDF file 'C:\TimeTeq_Documentation_Aug2009\TimeTEQ_OldHelp\user guide\Timteq_test_project\!SSL!\Printed_Documentation\Printed_Documentation.pdf'...
    Failed to save 'Printed_Documentation.doc'...
    Cleaning up temporary files...
    Internal error encountered,  Failed to generate Printed Documentation.

    There is a warning about a malformed topic. I have seen projects  where there is nothing wrong with the topic but where the machine needed more RAM. What are the basics of your PC?
    Also try turning off PDF and generating a Word document instead. If that works, PDF from there. Does that work?
    See www.grainge.org for RoboHelp and Authoring tips

  • Error while generating the Document...  Bursting Status Report

    Hey all,
    I am getting some errors in a production environment when trying to burst out some invoice data.
    This process has been pretty robust and out of 1000+ invoices a day, I can only find 4 that are failing regularily.
    Why am I mentioning?, just to show that I am thinking this is a data issue, but just cannot see anything that stands out.
    I can take the xml output and run it through my development suite on my local machine and all runs fine.
    Just when it is running live through the db is when it fails.
    Here is the Bursting output that shows the error....
    <?xml version="1.0" encoding="UTF-8"?>
    <BURS_REPORT>
    <REQUESTID>27044820</REQUESTID>
    <PARENT_REQUESTID>27044726</PARENT_REQUESTID>
    <REPORT_DESC>Invoice Print Selected Invoices</REPORT_DESC>
    <OUTPUT_FILE>[$OUT_DIR]/o27044820.zip</OUTPUT_FILE>
    <DOCUMENT_STATUS>
    <KEY></KEY>
    <OUTPUT_TYPE>pdf</OUTPUT_TYPE>
    <DELIVERY></DELIVERY>
    <OUTPUT></OUTPUT>
    <STATUS>fail</STATUS>
    <LOG>Error while generating the Document...</LOG>
    </DOCUMENT_STATUS>
    </BURS_REPORT>
    The problem is that this output doesn't necessarily help, nor can I find any hints in the OPP logs.
    So... the question becomes...
    Any ideas on where I can look to resolve this issue?+
    Or where I can find any clues at, that would possible point at the issue?+
    Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
    BI Publisher 5.6.3
    Thanks
    Hayden,

    Tim,
    Thanks for the suggestion, always seems to slip my mind that the Bursting Report has debug on it.
    As far as what is generating the XML, it is oracle's standard, only slightly modified ... ;), invoice generating report, RAXINV_SEL.
    Well RAXINV_SEL, or RAXINV_NEW, doesn't matter, same code, that is the executable.
    I have turned on the debug, for both the source xml and the burst request, and unfortunately, still nothing stands out to me.
    I was really expecting to see something in the burst log, pasted at the bottom...
    but, it yet avoids me.
    If I had to guess, I would bet the user went, in our terminology, "slashwit crazy", or example "model /w options", in some description.
    But can't seem to find which field it is blowing up on, since we are catching these special characters in several places already, and slashwit is littered throughout the output.
    I was also looking in the bursting control file for the special xml tags identified there, as those would require no slashes. But those are all clean.
    Hayden,
    XML Publisher: Version : 11.5.0
    Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.
    XDOBURSTREP module: XML Publisher Report Bursting Program
    Current system time is 21-SEP-2009 10:43:12
    XML/BI Publisher Version : 5.6.3
    Request ID: 27048106
    All Parameters: ReportRequestID=27044726:DebugFlag=Y
    Report Req ID: 27044726
    Debug Flag: Y
    Updating request description
    Updated description
    Retrieving XML request information
    Node Name:{node}
    Preparing parameters
    null output =/u007/app/applmgr/{instance}/out/{instance}/o27048106.out
    inputfilename =/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
    Data XML File:/u007/app/applmgr/{instance}/out/{instance}/o27044726.out
    Set Bursting parameters..
    Temp. Directory:/u007/app/applmgr/{instance}/temp
    [092109_104315337][][STATEMENT] Oracle XML Parser version ::: Oracle XDK Java 9.0.4.0.0 Production
    [092109_104315340][][STATEMENT] setOAProperties called..
    Bursting propertes.....
    {burstng-source=EBS, font.Free 3 of 9.normal.normal=truetype./usr/java/jre/lib/fonts/FREE3OF9.TTF, font.Times New Roman.normal.normal=truetype./usr/java/jre/lib/fonts/TIMES.TTF, system-temp-dir=/u007/app/applmgr/{instance}/temp, font.Arial.italic.normal=truetype./usr/java/jre/lib/fonts/ARIALI.TTF, user-variable:cp:parent_request_id=27044726, user-variable:cp:application_short_name=XDO, font.Courier New.normal.bold=truetype./usr/java/jre/lib/fonts/COURBD.TTF, font.Times New Roman.normal.bold=truetype./usr/java/jre/lib/fonts/TIMESBD.TTF, user-variable:cp:request_id=27048106, font.Arial.normal.normal=truetype./usr/java/jre/lib/fonts/ARIAL.TTF, font.Courier New.normal.normal=truetype./usr/java/jre/lib/fonts/COUR.TTF, user-variable.OA_MEDIA=http://diierp.corio.com:8002/OA_MEDIA, font.Courier New.italic.bold=truetype./usr/java/jre/lib/fonts/COURBI.TTF, user-variable:cp:org_id=83, user-variable:cp:DebugFlag=Y, font.Times New Roman.italic.bold=truetype./usr/java/jre/lib/fonts/TIMESBI.TTF, user-variable:cp:responsibility=51270, font.Arial.italic.bold=truetype./usr/java/jre/lib/fonts/ARIALBI.TTF, font.Courier New.italic.normal=truetype./usr/java/jre/lib/fonts/COURI.TTF, user-variable:cp:user=HAYDEN, user-variable:cp:reportdescription=Invoice Print Selected Invoices, user-variable:cp:language=en, font.Times New Roman.italic.normal=truetype./usr/java/jre/lib/fonts/TIMESI.TTF, user-variable:cp:ReportRequestID=27044726, user-variable:cp:locale=en-US, user-variable:cp:territory=US, font.Arial.normal.bold=truetype./usr/java/jre/lib/fonts/ARIALBD.TTF}
    Start bursting process..
    Bursting process complete..
    Generating Bursting Status Report..
    Start of log messages from FND_FILE
    End of log messages from FND_FILE
    Executing request completion options...
    ------------- 1) PUBLISH -------------
    Beginning post-processing of request 27048106 on node {node} at 21-SEP-2009 10:43:19.
    Post-processing of request 27048106 completed at 21-SEP-2009 10:43:20.
    Finished executing request completion options.
    Concurrent request completed
    Current system time is 21-SEP-2009 10:43:20
    ---------------------------------------------------------------------------

  • How to create print document for payment to customer through cash journal

    Dear Sirs,
    I have a problem with print document from cash journal. I enter a payment to customer (when I turn the money to customer) and the system makes right posting, but when I try to print this point, system printing document for incom from customer. I'm using business transaction for customer posting in cash journal. I would like to know how I have to manage this posting - payment to customer, or incoming from vendor (returnes advances from emploee)?

    Hi,
    please check whether the two solutions below work:
    1. create a contract with milestone billing plan where there are only down payment billings, so that on the basis of the contract you can generate down payment requests and then relevant down payments, release the contract to a sales order which can then be delivered and billed, manually clear the billing document with the down payments
    2. from FI module, create down payment requests via t-code F-37 directly, and then down payment posting, generate sales order directly, and then deliver and bill, manually clear the billing document with the down payments

  • Visual C++ runtime library error when generating printed documentation from RH9

    I just upgraded a project from RH 7 to RH 9. I tried generating printed documentation in Word from it, but as soon as the Printed Documentation dialog opened, a Visual C++ Runtime Library error displayed. RoboHelp stopped working and I had to restart.
    I tried using one of the sample projects -- same thing happened.
    I then created a brand-new project. This time, opening the Printed Documentation dialog worked. I selected "Generate Word Doc" and the .docx extension, since I have Word 2010,  and tried to generate printed documentation. However, the following message then displayed: Cannot find Microsoft Word installed on your system.
    So I have two questions:
    - How can I avoid crashing RoboHelp when generating printed documentation?
    - How can I ensure that RoboHelp finds the Word 2010 installation on my system?
    Thanks for any help!
    OK, just played around a bit more and I was able to help myself on the first question:
    - I created a new Printed Documentation Layout in the Single Source Layouts pane, and from there I was able to generate .pdf files, without encountering the Visual C++ runtime error.
    - But the "Cannot find Microsoft Word installed on your system." msg still pops up when I try to generate .docx files. (When I generate .doc files, they have no content.)
    Message was edited by: mizotto

    First the fact that the problem is with old layouts suggest they were using an old template.
    The PDF creation relies on a Word document being created in the background. The fact that you cannot generate a good doc or docx makes it odd that you get a PDF. The PDF is OK I take it?
    I'm wondering if you have not applied the 901 patch and are running Word 2010 64 bit?
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Printed Document function not working

    I have a user who is trying to use the Printed Document
    function of RoboHelp to convert html files into one continuous
    document, put together in a book form, complete with a table of
    contents. The process errors out giving her error messages like
    --> "Warning: The Word Document became corrupt when attempting
    to append a malformed topic: (then it lists an htm file here)". Can
    anyone tell me what could be causing this error or if something
    might be missing from the installation?
    Thank you!

    Welcome to the forum
    You'll like this. A number of possibilities.
    See Printed Documentation Issues on my site for one
    possibility.
    The other is quite simply insufficient RAM. Yeah I know what
    RH says on the box but Word has its own requirements. I have a
    layout that gives this error on a 2gb ram machine but works quite
    happily on 3gb.
    A way of checking that it is RAM is to create two copies of
    the print layout. Leave one alone. In number two trash half the
    topics. In three trash the other half. If two and three then
    generate OK, there is clearly no problem topic so by my
    calculations it has to be RAM.

  • Print document's name in Event Log ID #307 on Server 2012

    Creating a new printer server using Windows Server 2012.  Everything is working out fine so far, however I just ran into one problem that didn't happen in our Server 2008R2 print server.
    When looking at print jobs that have completed under:  event logs --> Microsoft --> Windows --> PrintService --Operational, I have noticed that Event ID 307 is not displaying the printed document's name in Server 2012 (it did for Server 2008R2). 
    In Server 2012, the document name simply displays as "Print Document" instead of displaying the document's name.
    Anyone have any ideas on how to get the document's name to properly display in the event logs?
    Thanks for any help.

    Hi Alan,
    I have configured a Server 2012 R2 standard as print server to manage printers and Monitor the print usage of users, however I am not getting the Print logs (Event Log ID 307) in the default event logs directory on the print Server.
    I perform some search and come to know that it’s a known problem in Server 2012 and there is Hotfix available. I installed the Hotfix mentioned here
    http://support2.microsoft.com/kb/2938013/en-us , but still logs are not getting generated.
    I also made the below setting for the logs.
    Creating Registry entry
    Windows Registry Editor Version 5.00
    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Policies\Microsoft\Windows NT\Printers] "ShowJobTitleInEventLogs"=dword:00000001
    [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers] "ShowJobTitleInEventLogs"=dword:00000001
    The policy name: Computer Configuration \ Administrative Templates \ Printers
    Allow job name in event logs
    Keep printed Docs setting is also enabled on all the printers installed on Print Server.
    Noting seems to be working here or am i doing something wrong here.
    Regards
    Mukesh

  • Word styles not appearing in Print Document Appearance dialog

    My custom list styles in Style Mapping.dot are not appearing in the Print Document Appearance dialog when I try to map CSS styles to Word styles.
    The styles do appear in the template when I open it in Word. They appear in the styles task pane whether I select "In current document" or "In use" in the Style Pane Options dialog in Word. The styles have the same name (such as "Bullet" or "Number") in Word as the CSS styles in RoboHelp.
    I tried saving Style Mapping.dot as .dotx, thinking that RoboHelp 8 might work better with the current template type, but no help. I tried adding the template to the same folder as the Normal.dotm template is in and opening it there. No improvement.
    Oddly, the built-in Word styles List, List 2, & etc and List Continue and its series appear in the Robo dialog, but the styles List Bullet and others in that series do not appear.
    I suppose I could modify the list styles that do appear in Robo and map them to my CSS list styles, but that feels a bit like a desperate kluge.
    Does anyone know what might be wrong, either with my Word template or with Robo, that might be causing what seem to be perfectly good Word styles to not present themselves for mapping?
    Thanks again,
    John

    Peter,
    I think your discussion of this problem could explain the situation and propose a workaround more simply than it does.
    Based on your article, I assumed that Robo displays only the built in Word list styles such as List and List Continue (since those were the only styles showing up in the style mapping dialog and since your example shows matching a Robo style named List Mapping to a Word built in style named List). I assumed I would have to match my Bullet style to a style named List in Word, and match the indented bullet style to List 2, and so on. The actual situation is that Robo, for some godforsaken reason that only idiots would understand, will not show a Word style if any numbering (bullets or numbers) is applied to it. That is, one does not have to avoid a class of styles called “List styles”, one only has to avoid applying numbering to the styles until later.
    Thus the workaround is to create the word styles (with names that match the Robo styles!) that contain every attribute you need EXCEPT the numbering. That is, I can link Bullet to Bullet and Number to Number and Indented Number to Indented Number, and so on and on, as long as I have all the Word styles in the template with their numbering set to None.
    Then after I generate the document, I can modify the styles to add the appropriate numbering, and voila!
    Currently scrolling the doc & modifying styles. Might be a glimpse of daylight.
    John
    From: Peter Grainge [email protected]
    Sent: Thursday, October 13, 2011 8:47 AM
    To: John Dawson
    Subject: Word styles not appearing in Print Document Appearance dialog
    Re: Word styles not appearing in Print Document Appearance dialog
    created by Peter Grainge<http://forums.adobe.com/people/Peter+Grainge> in RoboHelp - View the full discussion<http://forums.adobe.com/message/3969382#3969382

  • Books are not shown in the TOC of the printed document

    Hello,
    I am using Robohelp 10. I have a project with several books and topics. When I generate a web help, everything is fine. But now, I have to generate a printed version of it. My problem is that on the table of contents of the generated document, the books are now shown. I need those books to be shown. Please advise.
    I can not post the project I am using so I just used a very simple project which I created.
    This is the original TOC.
    and this is the resulting TOC in the printed document.
    The books should still be part of the contents same with the original TOC.
    I do not know what is wring with my set-up since I only used the default one. It will be great if you can reply to me ASAP since we need to publish our help document. Thanks a lot!

    OK, the samples are a known quantity and normally generate correctly. Thus we know it is something about your environment, assuming you used the supplied style mapping template?
    In the last page of the print dialog, are you using the supplied Rh Style Mapping template?
    After generating with whatever you are using, have you tried right-clicking alongside the TOC and choosing Update Field. That might correct the TOC.
    What version of Word are you using?
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • Setting chapter font in printed document

    When I create printed documentation, the font used for the
    chapter title is the same as the font used for the titles of the
    topics in that chapter. I'd like the chapter title to be in a
    larger font, but I can't find a way to set it. How do you set the
    font of the chapter titles in the printed documentation?
    I'm using RoboHTML 6.0.

    When RH generates the printed document it will apply Heading
    1 to the chapters, nothing you can do about that.
    It will also apply headings in your topics as you have set
    them out so the topic title will also be Heading 1. You can clear
    the Maintain HTML level check box in which case all headings in the
    source will be bumped down 1. So Heading 1 in source will be
    Heading 2 in Word. Knowing that, you can adjust your styles
    accordingly.
    Take a look at the topic on Printed Documentation on my site.

  • Headings are duplicated in Printed Document

    I noticed that some headings in my Printed Document were
    duplicated. I investigated and found that topics used as Books in
    the TOC had that problem: The first heading was duplicated in the
    Printed Document. I also happened to use the first heading as the
    topic heading. What is the solution to the problem?
    I know I can delete such headings in the Word document after
    the Printed document is generated.

    Reading the other replies - I have one further comment.  You can change the heading - but that is extra work and might confuse the end-user. More, it confounds QA...best, I believe is to highlight the heading and remove the duplication by tagging it as I previous wrote.
    However - this is only in relation to the issue of there being duplicate headings because of the TOC entires.
    If you are talking about duplicate topics - this also would be a result of the topic "appearing" in two places in the TOC. In this case, you can accomplish the same thing by tagging the TOC entry and appying a conditional tag, or building a separate printed documentation TOC and an output SSL for that.

  • Using and Apex developed system and generating  word documents

    Started a new development project. We looked at using Apex for the system but ran up against a road block because the customer needs to generate word documents that they can edit and print. Does anyone know if Apex can handle this? Any suggestions on were to look for more information.

    Hi Dawn,
    Yes you can certainly do that, take a look at this quick overview -
    http://www.oracle.com/technology/products/database/application_express/html/configure_printing.html
    It refers specifically to PDF printing, however with BI Publisher you can output in Word Document format too.
    Hope this helps,
    John.
    Blog: http://jes.blogs.shellprompt.net
    Work: http://www.apex-evangelists.com
    Author of Pro Application Express: http://tinyurl.com/3gu7cd
    REWARDS: Please remember to mark helpful or correct posts on the forum, not just for my answers but for everyone!

  • Robohelp-issue in generatings printed document

    Hi,
    I have installed the trial version of Robohelp9. It was working well till friday.I have included some topics today and tried to generate the printed output. But I got the below error and system crashed. Then again i have to open the robohelp project. but when i generate the webhelp file, its working fine.
    but in 'Single Source Layout', when i select the 'Printed Document' option ->right click-> select view it gave the following message.
    Please guide me on this.

    hi,
    Sorry its not possible to share the word document.I generated the new project with the same contents but still the same. I just checked the !SSL folder but it contains the ie files. (please refer the below image)
    Thanks.

Maybe you are looking for

  • WRT54G2V1 Need Open NAT for Destiny PS3

    I currently have a Linksys WRT54G2V router. My Playstation3 has a wired connection to my router. With my current settings when I play Destiny on my PS3 I have a moderate NAT, and would like an open NAT. My ISP is Charter Communications. I do get a pu

  • Transaction ME21n (Will not run as a BACKGROUND SESSION)

    The requirement is to generate Purchase Orders (Stock Transport Orders to be precise). The RFC has to create a session which will be executed...say...before midnight to generate the sto (TC -> SM35). I have used BDC inside my RFC calling the transact

  • F33-FF00-0006 Error in Recovery

    Hello, I'm attempting to fix a laptop for a friend.  The hard disk in the laptop was gradually failing with quite a number of bad sectors, all seemingly on the OS partition, and it wouldn't boot.  The first partition (WinRE?) and the last (Toshiba re

  • Help !! PHP or AS to PDF Printing

    Looking for some info on the what the PHP or AS coding would be to create what the industry is calling an "Flyer Machine". I have a client that really wants this. Essentially the PHP or AS references images on a server and allows for automatic printi

  • File-Transport over WebService

    Hi, it is possible to transport div. kinds of files (txt, pdf etc.) over an WebService (for example as attachement)? Thanks in advance Frank