RH9 hangs while generating printed doc

I was generating a printed doc and left my desk. When I came back, the laptop had gone to sleep. When I woke it, it was stuck on the last part, Updating Index.
I let it go for a while (the progress bar was showing that it was almost done and still processing topics). After 20 minutes, I tried to cancel by clicking Cancel. It ignored me. I killed it with Task Manager.
I waited a minute, then restarted RH. I tried again. It said the document was in use. I shut everything down, restarted Windows, and tried again. Got the same message. Went and deleted everything in the output folder for the printed doc. Deleted the .CPD file, just because.
Restarted Windows again. Tried generating the printed doc again. It's stuck at the same point, and it's been over a half hour.
I could go back to yesterday's backup without much pain (no major changes since then), but just in case this happens again and I don't have that option, what should I do?
It's a long weekend here in the States (Memorial Day) and I think it's a Bank Holiday in the UK (Spring Bank Holiday), so I'm sure you all aren't glued to your screens , so I'll be patient.

In order:
Use Windows Explorer to delete the content of the target location and try again.
Generate to a different location.
Create a new layout, not a duplicate.
Create two duplicate layouts and trash the different halves of the content.
Open a bottle.
Resign.
Seriously, post back if Steps 1 to 4 don't work.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Similar Messages

Error while generating ARE doc. Internal number .

Error while generating ARE doc. Internal number .
Message no. 4F238
while creating ARE1 ,whilke saving the system is giving a message.
please help.
points will be rewarded.

check whether You activated the SPRO setting for BEX.
SPRO -->SAP Business Information Warehouse --> reporting relevant settings -->
general reporting settings > activate personilisation in BEX>
P

Error while generating printed documentatin in RH 7

Dear Sir,
while generatig Printed Documentation, the following message
appear:-
"Microsoft Word seems to not be responding , would you like
to continue waiting for a response?"
then "The Macros in this project are disabled, please refer
to online help"
then "VBA Macro version register is incorrect , please re
install printed documentation"
thanks.

It's probably as simple as change the Word security settings
to Medium.
If not, take a look at Print Issues on my site.

Aperture 3: multiple export hangs while generating thumbnails?

Sigh. I was almost ready to write a blog post claiming that while AP3 has its share of bugs, it's not the unusable mess some have painted it to be. This morning I'm no so sure anymore. I think this is stellar update with tons of potential. When it works it screams on my machine and the new features are amazing. But guys, i need the basics to work.
Here's what I've just sent t via the feedback form:
I've been trying to export 29 pictures in web format for the past 40 minutes. I've had to force-quit AP three times and restart my machine twice. Aperture starts exporting at a normal pace but then completely hangs on a "generating thumbnails" process. At this point it becomes impossible to either cancel the task or quit Aperture normally. It also kicks my iMac's fan into overdrive - something that NEVER happens.
This is not good.
Other problems:
- random crashes while using brushes.
- second display doesn't follow "blank" command and keeps reverting to "alternate" even when the menu says Blank.
This is a great version of Aperture with a lot of potential. These bugs are killing me though.
I've just rebuilt the database. If it's still not working I'm going to remove plugins and see if it helps.
Anyone else having problems with this?

Absolutely has to be a bug. This isn't a setting or configuration problem. It might even be a Snow Leopard problem. I had the same problems with A2.1.4 on SL as I do with version A3.0.1. Export hangs seem to happen on images that came from my A2 library that was imported into A3 but originally adjusted in A2. These images were imported from scanned TIFF files. If the adjustment mechanism was flawed in prior Aperture versions then Apple needs to create and distribute a utility that converts these images into something that A3 can use.
I will have to revert to A2 running on Leopard until Apple can get this fixed. If I cannot export, there is no point in running the software. On this discussion thread, we are just trying to fly by flapping our arms.

Application Error while generating printed documentation

I have Rh 10 installed in my 64-bit machine with Windows 7 OS.
The problem is when I click Printed Documentation and click Next in the Printed Documentation screen, Rh crashes.
Without clicking Next, if I click Save & Generate, pdf is generated with missing topics.
When I check the event log, I see Application Error. What exactly is causing this crash? Please help.

Which version of Word do you have installed and is it the 32 or 64 bit version?
The latter will not play nicely and even Microsoft recommend the 32 bit version for compatability with other apps.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Robohelp 8 hangs while generating Webhelp

Hi.
Two members of my team are trying to generate WebHelp in RH8. When they try to generate, the green status bar gets almost all the way to the end in the Uploading Files section, and then hangs. Nothing happens beyond that. They have to kill RoboHelp to get out of it. Both of them have Lenovo Thinkpad T400 laptops running Win7 (32 bit). To make things more interesting, I have an HP Elitebook 8460p running Win7 (also 32 bit) and I have no problem generating the exact same project.
What is really weird is that they were both able to generate previously. What changed was that we had a corrupt CPD and had to recreate it. After that, the problems started.
I was hoping the log file would provide some insight into what is happening, but it seems like the process hangs before the log file is written.
Any thoughts?
Thanks,
Rob Myre

Hi Rob
Where exactly are the project files? Are they on a LAN? If so, try copying them locally to the C drive and see if things improve. If so, there's your answer.
Cheers... Rick
Helpful and Handy Links
RoboHelp Wish Form/Bug Reporting Form
Begin learning RoboHelp HTML 7, 8 or 9 within the day!
Adobe Certified RoboHelp HTML Training
SorcerStone Blog
RoboHelp eBooks

RoboHelp 10: Problems generating Printed Documentation

Environment
Windows 7 Enterprise, Service Pack 1, 64-bit operating system
Office Professional Plus 2010 Versions 14.0.7106.5001 (64-bit)
RoboHelp 10: 10.0.0.287
Visual Studio 2010 Professional. I open RoboHelp from within Source Control (have been doing it for two years).
Problem
Sometime after moving to RoboHelp 10, and even after successfully generating Printed Documentation output, I encountered a major problem generating Printed Documentation from RoboHelp: “Internal error encountered. Failed to generated Printed Documentation”. The error occurred when I tried to generate Printed Doc using my default TOC, which looks something like this:
Topic A
Topic B
Book 1
Book 2
Book 3
Topic C
Topic D
Based on an old Peter Grainge reply to someone about a similar problem, I removed all but the first topic from the Chapter Layout pane and generated the Help. Everything was fine until I got to the topics after Book 3. At that point everything started to fail again. When I removed Topics C, D, etc. from the Chapter Layout pane, the output was built successfully.
I tried moving Topics C, D, etc. to the top of the Chapter Layout pane, and got the same error. I tried creating a new folder and put Topics C, D, etc. into that folder. Failure after failure.
As an experiment, I removed all the Topics C, D, etc from the Chapter Layout pane, but then added them to the Print Document Section Layout pane (not where I want them). The Printed Documentation built successfully.
During attempts to build with Topics C, D, etc. in the Chapter Layout pane, I kept getting a Word error: Word is trying to recover your information. After that there was always a failure.
Selecting PDF as the output did not work when the Topic C, D, etc. files were at the bottom of the Chapter Layout pane.
I create a new TOC and a new Printed Documentation SSL. Failed to generate.
As a matter of reference, I've been generating Printed Documentation from the same TOC for more than a year and so cannot figure out what has changed in RoboHelp or Word to cause this grief .
Has anyone experienced anything like this?
Carol

Dear Peter,
Thanks for following up. Last Friday I finished extensive testing on my own and working with RoboHelp Support. Here's what I sent to Support this morning.
If after reading this screed, you think it worthwhile for me to get a copy from Source Control for you to look at, I will do so. Thanks for offering to look at it.
Environment
Windows 7 Enterprise Service Pack 1, 8.00 GB RAM, 64-bit OS
Microsoft Office Professional Plus 2010 Version 14.0.7106.5003 64-bit--Note: We repaired my current version of Word, in case that was the problem, but did not reinstall Office--we do not think that the Word version is the problem because we generated successfully with other TOCs and when generating individual documents.
RoboHelp 10.0.1.292. Upgraded from RoboHelp 9 in May 2013. Replaced hard drive in September 2013 and reinstalled RoboHelp.
Visual Studio 2010 Professional 10.0.40219.1 SP1Rel (I open the project from Source Control and check files out to a folder on my desktop.)
Issue
Printed Documentation failed multiple times with the default Table of Contents, which contains all the topics in the project. TOC specs are as follows:
Properties: .docx, desktop location, no conditions, embedded images, “Generate a single document”, “Retain hyperlinks”.
330 files, 12 top-level books, 15 second-level books, 7 third-level books, 6 fourth-level books, and 8 fifth-level books
Results
Generation to Printed Documentation does NOT fail for other, module-specific TOCs, nor to WebHelp Pro SSLs for the same sets of topics. In addition, and perhaps more important, generation to Printed Documentation does NOT fail with “Generate Individual Documents” selected, or when there are approximately fewer than 259 files in the TOC.
Did not fail consistently based on any particular topic.
Did not fail consistently based on location of any particular topic in the TOC.
Failed when I created new TOCs based on ‘working’ TOCs. For example, copied a module-specific TOC and then added topics to it from the default (superset) TOC. I did this in case the original default TOC was corrupted.
Failed when I create a new TOC with the same folder/file structure from scratch.
Failed when I created a new TOC with a flat file structure from scratch.
Failed when I retrieved an older TOC from the last release of the product.
Failed when I created new SSLs each time. I did this in case the SSLs had got corrupted.
Failed when I did not open the project from Source Control (removed project from Source Control and worked locally).
Began to see failure when there were more than about 258-263 files in the TOC. For example, successfully generated Printed Documentation with 262 files in the TOC. Added one topic and the generation failed. Removed that topic and added several others, one at a time. Consistently failed. To test this, I created a TOC with all the files in a flat structure, generated a report for the TOC, printed it, and counted the number of files. I then began deleting files and regenerating the Printed Document to try to identify the number of files in the TOC when the generation failed. Successfully generated up to about 258 files and then it began failing. (Occasional successes at 260 and 261, but that may be because I didn’t always consistently remove the Glossary and Index from the Chapter Layout pane.)
Other Comments
(I know that we should generally post non-RH issues to other forums, but in this case I wanted to include all potentially related issues in this posting.)
The first time you generate any type of output, the “Critical error of Source Control Provider. Please restart IDE.” Message appears. This message appears behind RoboHelp. As a result, if the RoboHelp window is maximized, you think that RoboHelp is hung. Forcing a close of RoboHelp leaves the partially generated Word document in an unstable state. When you re-open RoboHelp and try to generate the output again, RoboHelp says that the output is in use. Unfortunately, there is no way to ‘free’ the Word document and you have to restart the computer. In addition, when the dialog box is hidden, even using Alt+Tab to find the dialog box is complicated because you can’t grab it and click OK until RoboHelp completes its processing. The workaround is to reduce the size of the application window so that you can see the dialog box and try to quickly grab it and click OK. That said, as soon as processing is complete you can grab the dialog box and click OK; at that point RoboHelp displays its own error message about the success or failure of the output generation. It is not clear whether the RoboHelp API or Source Control puts up this error message, but it’s definitely a problem until you happen upon the workaround.
RoboHelp does not check SSLs even when I right-click the SSL in the Single Source Layouts pane, click Check In, select the XML and SSL files, and leave “Keep checked out” deselected. The red check mark remains next to the SSL name. In addition, even when I Check In All files before closing the project, the next time I open the project RoboHelp displays a series of Check In dialog boxes requiring me to check them in again.
When RoboHelp hangs during a Printed Documentation failure and the Version Control setting is to check in all files when closing a project (which I’ve now deselected to avoid this problem), Ctrl+Alt+Del indicates that you cannot shut down the program because RoboHelp is waiting for a response. Yes, RoboHelp was waiting for me to check in some files (because of the Version Control setting), but hid the Check In Source Files dialog box behind the application. This usually left a Word document in limbo, forcing me to restart the computer.
At one point RoboHelp stopped saving changes to an SSL after I made changes and clicked Save and Generate. Each time I reopened the SSL, I had to select .docx, etc. all over again.
Carol

Missing Topics in Printed Doc

I am losing my mind! I am trying to generate printed doc for
the sole purpose of sorting a bunch of pages in hard copy to
rethink the organization of one part of my projects. Ironically,
every time I generate the printed doc (i've done it about 20 times
so far), these pages are nowhere to be found! I've included them in
the TOC, I've moved them out of a book within a book, I've deleted
them from the TOC and added them to a book that is generated as a
chapter. I've renamed the book to remove non-alpha characters. I've
deleted the book and created a new book with a completely unrelated
name. NOTHING I do will get these pages to print. SO - I have 175
pp. document of the 175 pages that DONT need to be printed and I
can't for the life of me print the +/-20 pages that are the ones I
want in hard copy.

first, I am using RH version X5.0.2.
1. On your Project tab, all the way at the bottom, open the
Single Source Layouts directory. Double click on Printed
Documentation.
2. Set up your doc name, path, and build expression as
needed. Click on Next.
3. This next window is where you can select any or all topics
to include in the printed doc. It defaults, I believe, to all
topics and chapters. Just select each chapter or topic you do not
want and click on the left-pointing arrows to move these topics out
of the list on the right side of the window. Only the topics and
chapters listed in the right side (under chapter layout) will
print. This selection window works much like the Browse Sequencer
tool.
4. When all appropriate topics are excluded / included, click
on Next. In this window, you are establishing the sections of the
resulting doc - set up sections as needed. If you aren't publishing
this doc for distribution (just for yourself), I wouldn't worry too
much about this step. Click on Next.
5. The last step before the doc generates is to determine
which Styles set you will use - the styles you use in RH, or a Word
Style set. Again, since this is just for you, don't sweat it. I
just use the Project's CSS Styles (select this option from the menu
at the top of the window).
6. Click on Finish, let 'er rip, and see what comes out.

Duplicated topics in printed docs

Is there a way to prevent RoboHelp from duplicating topics in
the Print Document Content - Printed Documentation dialog when
generating printed docs? I just noticed my PDFs have doubled
topics. I'm going back and manually deleting them on the dialog.
How did they get duplicated in the first place?

Hi Gina,
One cause of duplicated topics in your printed documentation
is having topics linked to books in the TOC. If a topic is linked
to a book and also appears separately within the book, it will
appear twice in the printed output.
If that's not the cause, someone else might be able to help.
Have you checked out all the info on Peter Grainge's excellent
site? He's got a whole section on printed documentation. His site
is
www.grainge.org.
Anne

RH 10: not use Master Page in Printed Docs

I have a Master Page set up with a company logo and horizontal rules, which works great with the help topics. The problem occurs when I generate printed docs from the source files.
Everything else works well enough to get by (I have some tweaking to do), BUT every single topic shows up with the rules and the company logo. I don't see anywhere to NOT apply the Master Page to the printed output. Is there a secret to not using the online help layout in the printed docs?
thanks,
Alia

Master page headers and footers 100% guaranteed do not survive the trip to printed documentation. My guess is that in the master page your "headers" and "footers" have been created in the body section of the master page.
Create a new topic attaching that master page in the process. Then unlink the master page from that topic. Do you still see the header and footer? If you do, my theory is proved. If you do not, post back.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

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

Error while printing generated XML doc using DBMS_OUTPUT

while generating XML document using XDK for PL/SQL i am getting " ORU-10027: buffer overflow, limit of 1000000 bytes " error even though i had set DBMS_OUTPUT to 1000000.
Is there any way to getrid of this problem .
i am using this code ..
CREATE OR REPLACE procedure SQLToXML1 is
queryCtx DBMS_XMLquery.ctxType;
result CLOB;
begin
DBMS_OUTPUT.ENABLE (1000000);
queryCtx := DBMS_XMLQuery.newContext ('select * from depolib_library' )
result := DBMS_XMLQuery.getXML(queryCtx);
printClobOut(result);
DBMS_XMLQuery.closeContext(queryCtx);
exception
when others then
dbms_output.put_line(sqlerrm);
end;
urgent help is needed
Thanks
null

No, It is a PO Print only. Only for changes to PO that do not affect the value of the PO,this error occurs. When i select the entry for the PO and click on Output message, the output message fails. On clicking Display Message, it shows the message - No schedules exist for the Scheduling Agreement XXXXXX(the PO number".
So,it is not for Scheduling Agreements but for PO only. I know it is weird to see such an error on the PO output message in ME9F.
Pls help.

"Error while generating pdf" error come when clicking on "Print Version "

Hello ,
When we execute Query in the Portal there is a 'Print version' button.
When you select it, it opens up print dialog and click OK
It is supposed to send 'pdf' stream to Web browser client on end user but it is not able to generate the pdf .
getting ' Error while generating pdf '
I am working on BI 7.0 .
The same is running fine in the Q Environment .But in Production we are getting this error .
Thanks ,
Rahul

Hi,
I think this is an ADS error. This is a reason why pdf's are not working. We had the same issue.
You can check your installation:
Usage of SAP NetWeaver BI Diagnostics & Support Desk Tool
SAP Note Number: [937697|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d393337363937%7d]
Exceptions: Prerequisites for messages in the area BI Java
SAP Note Number: [1224043 |https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bw_bex/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31323234303433%7d]
Solution in our case was to update the SAPADS package to 7.00 17.1
Regards
Andreas

ERROR WHILE GENERATING ARE-1 doc internal number

Dear sir
while creating ARE-1 Doc following error getting
error while generating ARE 1 DOC internal number
message no : 4F238
I MAINTAIN ALL NO RANGE OBJECT ALSO THEN ALSO GETTING ERROR
Sl No
Object
Tocde
Module
After Closing the Year ;
Maintain the Number ranges for following number
range objects related to CIN for the New year
Excise/
Series Group
1
J_1IINTNUM
SNRO/SNUM
Internal Document number to be Generated
2
J_1IRG23A1
SNRO/SNUM
MM
RG23A PART1 number Range object
3
J_1IRG23A2
SNRO/SNUM
MM
RG23A PARTII number Range object
4
J_1IRG1
SNRO/SNUM
SD
RG1 Number range object
5
J_1IRG23C1
SNRO/SNUM
MM
RG23C Part1 Number Range Object
6
J_1IRG23C2
SNRO/SNUM
MM
RG23C PartII Number Range Object
7
J_1IPLA2
SNRO/SNUM
MM
PLA PartII number Range Object
8
J_1IINTPR2
SNRO/SNUM
SD
Despatch Serial number
9
J_1IEXCLOC
SNRO/SNUM
SD
DOMESTIC EXCISE INVOICE
10
J_1IDEPINV
SNRO/SNUM
SD
EXCISE INVOICE FOR PLANT STO
11
J_1IEXCEXP
SNRO/SNUM
SD
Export excise invoice number range
12
J_1I57FC
SNRO/SNUM
MM
57FC Number Range Object
13
J_1IARE1
SNRO/SNUM
SD
ARE1 Series Group
14
J_1IARE3
SNRO/SNUM
SD
ARE3
15
J_1IBOND
SNRO/SNUM
SD
Bond Maintain (2007)
16
J_1ILIC
SNRO/SNUM
SD
Licence capture - CT3 maintain (2007)
THANKS & REGARD:
ROHIT NARSALE
9624886654

check whether You activated the SPRO setting for BEX.
SPRO -->SAP Business Information Warehouse --> reporting relevant settings -->
general reporting settings > activate personilisation in BEX>
P

While generating reports in Oracle BI Publisher in pdf format, the generated pdf reports have hindi इ matra displaced by one character. For example, रिपोर्ट is printed as रपेिोरट. Word file generated of the same report have correct hindi इ matra positi

While generating reports in Oracle BI Publisher in pdf format, the generated pdf reports have hindi इ matra displaced by one character. For example, रिपोर्ट is printed as रपेिोरट. Word file generated of the same report have correct hindi इ matra position and also pdf generated from this word file also contains the same.

RH9 hangs while generating printed doc

Similar Messages

Maybe you are looking for