PBC Book Publishing ERROR

Hi experts
I've a problem with the tool "Book publication Wizard" within ePublish tab. I create a PDF of reports that the user consult and update once a month.
During last update the system has produced this error : "ERROR OPENING PDF DUCUMENT", and now i can't publish any report.
I tried to delete the updates or create new book but i've the same problem.
Can anyone help me?

Patrick, thanks for your help. Our tech person looked that issue number up and the error message that came back was:
Error : Cannot update book list on the server.
Error Message : Section definition was changed
Cause
*The issue occurs when the default location path for the report in !REPNAME has been modified.
*The default location path is =EVSVR()&"/"&EVAST()&"/"&EVAPP()&"/eExcel/Reports/Book Reports/"&DXX (where XX is the row number for the corresponding workbook name for a section)
Our error message was
"Object reference not set to an instance of an object"
We checked our section definitions and they are correct so it appears to be something else.

Similar Messages

Iweb - Publish error - can't create the file "..."

Hey guys,
I've seen this issue in a couple of discussions but nothing helps. When I try to publish my site I'm getting the following error note:
"Publish error. Can't create the file "...png". The disk may be damaged or full, or you may not have sufficient access privileges."
Same result whether I publish to an ftp or to a local folder.
My disk is far from full and the site is merely a few megas heavy.
The content is just text and a few photos.
I have OS version 10.6.8 and Iweb 3.0.4.
No passwords involved.
I've tried all the tricks in the book:
Duplicating the page that won't publish.
Re-creating the page that won't publish.
Deleting com.apple.iweb.plist from home/library/preferences
Moving my site domain to another location, creating a new site and then putting the old one back
Deleting cache from libray/caches/com.apple.iweb
I re-installed Ilife
Reboots
Banging head repeatedly again wall
Any idea what could be causing this and how to fix it?
Pleymo

Try the following:
delete the iWeb preference file, com.apple.iWeb.plist, that resides in your Home() /Library/Preferences folder.
go to your Home()/Library/Caches/com.apple.iWeb folder and delete its contents.
launch iWeb and try again.
If that doesn't help continue with:
move the domain file from your Home/Library/Application Support/iWeb folder to the Desktop.
launch iWeb, create a new test site, save the new domain file and close iWeb.
go to the your Home/Library/Application Support/iWeb folder and delete the new domain file.
move your original domain file from the Desktop to the iWeb folder.
launch iWeb and try again.
OT

I am unable to share or export out my movie. I keep getting an publishing error 49?

I am using a mack book pro and imovie 11. I am trying to share/export the file out to my desktop. The video clip is being shared for an hour or so and when I get down to a minute left, It says there was a publishing error (-49). Can anyone help!

We purchased the year access tech support so I actually did call and his suggestion was to check out the AP store for CD/DVD burners (Which is how I acquired the "MyLife" to try.) or come to an Apple Support Forum like..... here! LOL!!! (I was probably directed to a "tech" person. Not an "application" person perhaps.)
I'll try again I guess.

Unidentified publish error

I am very close to giving up on Iweb altogether.
After installing ILife '11, my previously reliable IWeb started having hiccups. Every time I published, I started getting unidentified Publish Errors. It simply says "Publish Error, cannot publish to Mobile Me", with no reason given.
After reading previous posts I did all the obvious things, deleting plists; repairing permissions, etc. Then I read a post about deleted blog entries, and sure enough IWeb had corrupted years of prior blog entries (nearly causing me to throw my Mac out the window).
Then I changed users and managed to publish a blank web page on my site. From there, I got the idea that the blog was causing publish problems, so I decided to recreate my web site page by page to see where the problem lay. Obviously, I could not publish the blog, but several other pages (about 4 of 40) were also "corrupted" for some reason that was not immediately apparent. My web site is now "functional", but not entirely reliable. Every once in awhile, when I try to post a new page, I get this ******** publish error. Sometimes I get it, sometimes not. It is entirely unpredictable. And of course, my original blog is still "damaged" (irretrievable?).
Help!

Sorry for bumping an old post, but I have this exact same
problem using the same book.
For those familiar with the book, you would know to get to
chapter 10, your connections and test servers have already been
used, so I do not understand why this is happening.
The book has you create a new Recordset in the Bindings panel
and then has you go to the Advanced view and enter the SQL
mentioned by the OP.
What's strange is the book starts you on the Simple view of
the recordset dialog and selecting your connection, and the tables
all show up perfectly fine, so I do not know why it is erroring out
on me.
If it helps/matters, my testing server is the same server,
but I have it giong to a subdomain. Here's the direct info:
Remote server info:
Host Directory: teamslow.com/newland
Testing server info:
Host directory: teamslow.com/newland
URL Prefix:
http://newlandtest.teamslow.com/newland
Please let me know if any of this makes sense...

IWeb: publishing error message

Out of the blue this afternoon when I tried to upload some changes to the web site I received the following error message
PUBLISHING ERROR: There was an error communicating with the FTP server. Try again later, or check with your service provider
To double check the connection to the FTP server I clicked on the "Test Connection" button on the 'FTP Server Settinngs' of the 'Site Publishing Settings' page and the result came back clear and ready to use. I also ran a speed test on my broadband and that was fine too.
I cannot see any reason why I would get a publishing error. Can anyone help me please.
Thanks

Apply the two fixes below in order as needed to your iPhoto Library:
Fix #1
1 - launch iPhoto with the Command+Option keys held down and rebuild the library.
2 - run Option #4 to rebuild the database.
Fix #2
Using iPhoto Library Manager to Rebuild Your iPhoto Library
1 - download iPhoto Library Manager and launch.
2 - click on the Add Library button and select the library you want to add in the selection window..
3 - Now that the library is listed in the left hand pane of iPLM, click on your library and go to the Library ➙ Rebuild Library menu option.
4 - In the next window name the new library and select the location you want it to be placed.
5 - Click on the Create button.
Note: This creates a new library based on the LIbraryData.xml file in the library and will recover Events, Albums, keywords, titles and comments. However, books, calendars, cards and slideshows will be lost. The original library will be left untouched for further attempts at fixing the problem or in case the rebuilt library is not satisfactory.

Editing of Books Published on iBooks

I just finished a book published on iBooks for the iPad, by Annie Proulx, "Accordion Crimes". This comment has nothing to do with the literary work, but everything to do with the editing and publishing.
In the most polite terms possible, the publishing work was very, very disappointing. I found numerous spelling errors, misplaced emphasis (the word "eyes" appeared in italics throughout the 500= page book, for no apparent reason), some just plain new words never seen before in the English language which were not the product of the writer, I'm sure. It felt a lot like I was being asked to proofread, and that I was working with a draft.
If this was the final version of the book, then the software used to publish it is not ready for prime time.
I don't want my money back, but I sure do think that Apple needs to look into the publishing that they're selling. If this book was a representative sample, it's pretty shoddy work.
If this is the wrong forum for these comments, please accept my apologies, but I found no other channel to accept product quality feedback.

Since the bookstore is part of itunes, you should send feedback here:
http://www.apple.com/feedback/itunesapp.html
However, it sounds like you should also send feedback to the publisher. Coding books for the ibookstore is a tricky process (despite the people who tell you it's a snap), and they need to know that what they're doing isn't working.
You should also have a link in your receipt to report a problem; you could use that, too, if you do decide you want a refund.

DPS Feedback From Client: A Book Publisher's Perspective

Greetings,
I thought it might be helpful to both Adobe and other publishers to post some real-world feedback from one of our clients.
But first, some background:
We are a book publisher moving into the realm of book apps. Our book apps or not at all like their printed counterparts and mix in a bunch of new content and interactive features. Our apps are also not like magazines, which is what DPS feels like it was designed for.
We've been doing some testing with DPS, especially as it relates to a business model for us and our clients. We've also been testing resolutions, and figuring out the differences between single-issue and multi-issue apps.
I posted an overview of where our tests led us in terms of single vs. multi, here:
http://forums.adobe.com/message/4333151#4333151
and I posted some resolutions tests to see if an iPad 1/2 resolution app would look "good enough" on an iPad 3 (or the new iPad), here:
http://forums.adobe.com/message/4333426#4333426
and finally an overview of what we hope Adobe will do with single-issue apps and renditions, here:
http://forums.adobe.com/message/4333494#4333494
Below is a continuation of our DPS discovery process. At the same time we are exploring HTML5/CSS3/Javascript development with Baker. Although we've developed our own webapps, run everything in Amazon's cloud (ec2, s3) and have a development team familiar with everything needed to get a book app out via HTML, we are giving DPS a fair shot because we've invested so much money in Adobe's software and we'd rather our production team handle book apps instead of our development team.
With all of that said as a backdrop, we presented an interested client with the option of publishing two single-issue apps (iPad 1/2 and iPad 3) or publishing one multi-issue app.
Pricing wise, we kept our design fees the same with either option. The only pricing difference was $395x2 for the single-issue app route vs. a monthly charge to help us offset Adobe's monthly charge for the multi-issue app.
The questions from the client and answers from us went like this, in roughly this order:
Q: With the single-issue app, we don't pay an ongoing monthly fee?
A: Correct. It's just the up-front per-app fee.
Q: And in the multi-issue app arrangement, it doesn't matter how little our sales trickle in 6-9 months down the line, we're still paying the monthly fee if we want to have the app for sale at all?
A: Yes.
Q: Does either option limit us in terms of how long the app will be available for download?
A: No. Both options allow for ongoing sales of the app. The primary difference being you pay monthly to keep the app "alive" for multi-issue apps whereas single-issue apps live indefinitely with no monthly cost.
Q: So it seems like single-issue apps are the way for us.
A: From a pricing standpoint alone, yes, because most of your app sales will occur in the first month or two and single-issue apps do not carry any monthly costs down the line. That said, single-issue apps have some serious limitations.
Q: Like?
A: For starters, we would have to develop two apps to target iPad 1/2 and iPad 3.
Q: So the customer would have to make the choice? We are expecting the customer to get technical and figure out which app is for their device?
A: Yes. Renditions only exist in multi-issue apps, currently.
Q: Let's suppose we can get over that because eventually we will want to develop an Android version and a Kindle Fire version and in that case we are expecting customers to know which app works on their device...
A: Let me stop you there. Single-issue apps only work for iPad.
Q: So if we go the single-issue route, we simply can't ever develop an Android or Kindle Fire app?
A: Not as a single-issue app for any other platform than iPad. If it was essential you release on other platforms, we could look into converting the single-issue app into a multi-issue app later on, although we'd be looking at that monthly charge again.
Q: Right, which simply doesn't make sense for our app because of its timely nature.
A: We agree. Let's give up developing for other platforms for now and even indefinitely and focus in on just the iPad single-issue app development.
Q: Okay. So we release two apps, one for iPad 1/2 and one for iPad 3 using single-issue apps. What if we want to update the app down the road? Do we update both apps at once?
A: Actually, with single-issue apps, you can't update the app. Once it's submitted to Apple, it's locked in once and for all. Only multi-issue apps can be updated.
Q: That's another serious issue for us. Are there any other limitations we haven't discussed?
A: There are two more limitations: 1) Single-issue apps rely on the latest version of Adobe Content Viewer approved by Apple. Currently, version 19 of Adobe's DPS tools work with the Adobe Content Viewer that's approved and live in the App Store. That means we can develop your app using v19 of Adobe's tools but will have to hold off on updating to v20. This isn't so much a real issue as a potential issue. If, for example, v20 has some killer feature you really want to have, we simply couldn't use it. 2) Single-issue apps have no analytics.
Q: With all of these limitations, we're going to have to discuss internally which way to go. What's your recommendation?
A: All things considered, we think single-issue apps is the best solution now for your app. We have no exact target sales numbers in mind, but it's almost a certainty you will sell 80% of all app sales in the first 1-2 months. Knowing you want to keep the app available indefinitely means a single-issue app is the only way to go.
After two days and a few conference calls, the client decided to move forward with two single-issue apps, although a bit begrudgingly. We didn't pull any punches and let them know we expect Adobe to spend some time refining their pricing strategy and unifying the feature set as the technology starts to grow up. At this point, the seemingly wonky pricing structure and feature parity is the cost of being on the bleeding edge.
And we are now jumping into developing the app with DPS for our client. I should say, however, we are also working quickly to come up with a viable HTML5 route for publishing to avoid Adobe's system altogether. At this point I anticipate we will move to HTML in the next 2-5 months if Adobe's pricing/features don't start to move toward what we need. If we do jump to HTML, the answer to most clients' questions will be, "we can do that; for cheap; on all devices" and so on, which is a pretty attractive thing.
This ended up being considerably longer than I had originally envisioned, but my hope is it is useful for Adobe in refining the product and helpful for other publishers just starting down the DPS path.
Thanks,
Chris

Alistair,
Agreed. It wouldn't be right for us to pass on Adobe DPS' entire monthly charge to one client, and we have no plans to do so. We are still fine tuning the amount we would pass on to each client.
From our perspective, we are hesitant to invest anything at all in the multi-issue route because other paths to digital publishing/apps are looking more and more attractive. If we put out a handful of DPS multi-issue apps now (say, 4-5) then jump to HTML in 3-6 months, we will have to maintain Adobe's monthly fee indefinitely for the first 4-5 apps. It's as if we are paying Adobe for the right to be locked into paying Adobe monthly. No thanks.
From the client's perspective, even if the monthly amount we pass on is minimal, simple math shows at some point monthly sales will not cover the monthly carrying cost. When that point comes is pretty crucial to figure out, but it's likely it will come in month 2 or 3, which means the client would be forced to pull the app from the app store just 2-3 months after its release.
I keep trying to find a parallel for the business model in this new book app world. What is Adobe's role if we were talking traditional book publishing?
- The book store? No, that's the role of whichever app store the app is sold through (Apple's App Store, Android Market, etc.).
- The distributor? Possibly, since you could consider Adobe hosting the files as a type of distribution service (although, I'd prefer to host it all myself). If Adobe is the distributor, $0.30/download seems reasonable.
- The press? I suppose this could be argued since Adobe takes an input of files and outputs an app like a press takes an input of files and outputs a printed product. That's sorta like a press. But if that's the case, a per app fee (or even a per download fee) makes more sense than a monthly carrying cost. We don't pay our presses monthly after they've printed our books for the right to sell them.
Obviously, there's a flaw in thinking about this new world in old ways, but I'd still like to figure out exactly what Adobe's role is and why we (or our clients) would pay Adobe monthly. If, for example, Adobe's pricing scheme was something more like $400 per app created (with all features like renditions, updates, social sharing, etc.) + $0.30 per download to host the file with an option to bypass Adobe's (shaky) hosting service, we'd jump into DPS with no reservations and be publishing dozens of apps per year. Instead, we're dabbling with publishing one app and working as quickly as possible to find other solutions, which would eventually lead to converting our Adobe Create Suite based production team to an HTML/CSS/Javascript team.
Thanks,
Chris

Publish Error after copying domain file from one mac to another

Hello there,
so here is the problem: I have had iweb installed on a MBP, and a website up and running. Now that I just bought an iMac I wanted to transfer all the iWeb over to the iMac and make it the main machine. I was doing all the transfer work manually rather than using the migration assistant or time machine.
I have copied the domain file in the iWeb directory over to the iMac. iWeb starts and displays all the pages and sites normally, but when I try to publish I get the " Publish Error. An unknown error occurred" message.
On the MBP everything was/is working normally.
I have tried to copy the same file again, no change. I have deleted the preference file, no change.
I have tried publishing to a local folder, and get the same error message.
Does anybody have an idea how to get this fixed? I browsed through the discussions here but couldn't find anything regarding this specific issue.
cheers
grani

Welcome to the Apple Discussions. Try the following:
1 - delete the iWeb preference file, com.apple.iWeb.plist, that resides in your User/Library/Preferences folder.
2 - go to your User/Library/Caches/com.apple.iWeb folder and delete the contents.
3 - reboot.
4 - launch iWeb and try to publish.
If that doesn't help continue:
5 - move the domain file from your User/Library/Application Support/iWeb folder to the Desktop.
6 - launch iWeb, create a new test site and save.
7 - go to the your User/Library/Application Support/iWeb folder and delete the new domain file.
8 - move your original domain file from the Desktop to the iWeb folder.
9 - launch iWeb and try again.
OT

I keep getting the following error message while sharing my iMovie to iDVD. "Unable to prepare project for publishing" error (-2125).

I keep getting the following error message while sharing my iMovie to iDVD. "Unable to prepare project for publishing" error (-2125). I'm running iMovie 09 v. 8.0.6 on a iMac with OSX v 10.6.8, 2Ghz core duo, 1GB 667 Mhz DDR2 SDRAM. Any ideas why?

That particular error comes up for a number of reasons, sometimes it's the size of the movie you're trying to export. Bengt Wärleby a longtime contributor to the iMovie Discussion Group has advised a number of people on this error code, so I am going to link to his latest advice he's given to anyone trying to export to DVD from iMovie: Bengt's tips for great DVDs.
Specifically, try bypassing Share to iDVD by using Share to Media Browser instead.
In the Share to Media Browser dialog box choose the Large Size.
When(If?) it gets through that process, quit iMovie altogehter then go to iDVD.
Create a new project and click on the Media button near the lower right hand side of the Project Window.
Then click the Movies button in the Browser window just above that.
Under the iMovie star icon you should see the name of the project you shared out from iMovie.
Drag that into the project and burn the DVD.
If it's still to large or you get the same -2125 error code trying to Share using the Medium size instead. But again if you really get stuck consult Bengt Warleby's User tips:
Bengt's tips for great DVDs

IMovie '09 "Unable to Prepare Project for Publishing" error (-2009)

Please help ! I have just created a small movie in iMovie '09 from imported clips from Sony Handycam with miniDV tapes. All clips imported easily and can be viewed and edited. Though when I try to share the project to iTunes or even export it to my desktop I get the message "Unable to prepare the project for publishing" error (-2009).
I have been searching the forum and the web for an answer or quick fix and I see none, though i do see that many people are having this same issue. I already have all permission set to read & write on all the appropriate folders. I don't know what else to do.....I was hoping to have this project done for a Christmas present for my wife.
Please help .... ! ! !

I think I know what was the problem in my case. My project-file wasn´t very large, but I imported all my movies in one single event. After splitting the movies up into different events, I was able to export my project....

BI Publisher Errors

Hi all,
How to read the BI Publisher Errors. I mean, how to determine what the error is? I am creating an rtf template and preview PDF leads to following error.
Font Dir: C:\Program Files\Oracle\BI Publisher\BI Publisher Desktop\Template Builder for Word\fonts
Run XDO Start
RTFProcessor setLocale: en-us
FOProcessor setData: C:\PGW\Reports\Purchase Order Report\PO_data_143296.xml
FOProcessor setLocale: en-us
java.lang.ArrayIndexOutOfBoundsException: 13
     at oracle.apps.xdo.template.fo.elements.table.TableColumnInfoServer.getCellRectangle(Unknown Source)
     at oracle.apps.xdo.template.fo.area.TableRow.getAvailableAreaInfo(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.table.FOTableRow.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.table.FOTableBody.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.table.FOTableBody.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.table.FOTable.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.FOBlock.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.FOBlock.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.FOBlock.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.FOFlow.doLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.FormattingEngine.startLayout(Unknown Source)
     at oracle.apps.xdo.template.fo.elements.FormattingEngine.run(Unknown Source)
     at oracle.apps.xdo.template.fo.FOHandler.endElement(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLTHandler$EEEntry.sendEvent(Unknown Source)
     at oracle.apps.xdo.common.xml.XSLTMerger.startElement(Unknown Source)
     at oracle.xml.parser.v2.XMLContentHandler.startElement(XMLContentHandler.java:167)
     at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1182)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:301)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:268)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:149)
     at oracle.apps.xdo.template.fo.FOProcessingEngine.process(Unknown Source)
     at oracle.apps.xdo.template.FOProcessor.generate(Unknown Source)
     at RTF2PDF.runRTFto(RTF2PDF.java:632)
     at RTF2PDF.runXDO(RTF2PDF.java:466)
     at RTF2PDF.main(RTF2PDF.java:254)
I dont know what to look for or how to look for. In PLSQL it has error code and error message by which we determine the error. Any Help?
Thanks.

Hi Kim
1. SAS cubes are not currently supported - http://download.oracle.com/docs/cd/E10415_01/doc/bi.1013/e10417.pdf. Unless SAS cubes can use the MS drivers?
2. If you try and pursue it you might check the permissions on the ddll in the error to ensure you have rights over it.
Either way you are not supported with a SAS cube so you are kinda on your own. Sorry I dont use SAS so Im not going to be much help other than stating the obvious :0)
Regards
Tim

App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results

Please Vote if you find this to be helpful!
App-V PowerShell: Script to Query XenApp Servers for App-V Publishing Errors and Output an Excel Document with the Results
Just posted this to the wiki:
http://social.technet.microsoft.com/wiki/contents/articles/25323.app-v-powershell-script-to-query-xenapp-servers-for-app-v-publishing-errors-and-output-an-excel-document-with-the-results.aspx

Hi petro_jemes,
Just a little claritification, you need to add the value to the variable "[string]$ou", and also change the language in the variable "$emailbody" in the function "Get-ADUserPasswordExpirationDate".
I hope this helps.

Need Code for book publishing in BPC

Does anyone have any VBA code for generating multiple report tabs? This would take the place of book publishing since I do not want to create PDFs or HTML reports, but rather spreadsheets.

I am just noticing this - did you resolve your issue? You basically need to write the code.
Edited by: Deborah Silverman on Mar 16, 2009 7:30 PM

Publisher error message

Every time I try to update my site I get a message saying "unknown publisher error" how do I remedy this. Do I need to recreate my entire site? or is there some way to fix the problem? Thanks

Actually, look carefully, and you will notice there is a space between the quotes!
- Bill

"Unknown Publisher" error message during installation

Ok, I have tried for several days and even got ahold of Microsoft on this issue. Every time i go to download Itunes the download is ok, but when it goes to install Itunes, I ALWAYS get "Unknown Publisher" error message and installation is cancelled. How do i resolve this issue? Any ideas?????

Welcome to AD!
Some folks have had success by downloading and installing QuickTime standalone, then installing itunes after QT. iTunes needs QT codecs to play audio & video.
http://www.apple.com/quicktime/download/
Make sure to get the version withOUT itunes.

PBC Book Publishing ERROR

Similar Messages

Maybe you are looking for