Skip to main content

Debugging Amazon Kindle Direct Publishing - Internal Error

I’ve been setting up my next book in Kindle Direct Publishing (KDP.) This is the second book I have published through KDP, and it’s a reasonably straightforward process. 

 I first uploaded a draft of the book and cover months ago to check that I had the formatting right. This is something I recommend doing; if your text layout goes into the trim area, or has some other problem, the upload will be rejected. You want to make sure your design is right before you finish the layout of your whole book.  

  Anyway, I just finished the manuscript and went to upload it and the updated cover. When I did, I got an Internal Error for both the cover and the book. That confused me, as I hadn't made significant changes to the formatting. I tried uploading the previous version of the text and cover—the ones that had uploaded successfully some months ago—and got errors on those too!  

  I tried some different things uploading different versions and managed at one point to get the original cover to upload successfully, but that was as far as I got.  

  At that point, frustrated—and since the Kindle interface wasn’t giving me any hints—I tried googling. I found a support thread where someone suggested printing to PDF rather than exporting to PDF, but I couldn’t do that from InDesign on my Mac. I then tried removing a graphic element from the book text to see if that made a difference; my theory being, keep removing things until the upload works.  

  Meanwhile, thinking that the small increase in page count (6 pages longer!) might have meant that the cover's dimensions needed to be changed, I downloaded a new cover template. Opening that template, I discovered that the new template they now provided had the same dimensions as mine, but was at 400 dpi. The original cover I had uploaded—which had worked—was at 300dpi.  

  I created a new version of the cover at 400dpi and then tried uploading that, and lo and behold, both the book AND the text was now accepted.  

  Weird.

Comments

Post a Comment

Popular posts from this blog

Grammarly - Inconsistent punctuation fix bug

As I wrote in my previous post ( Grammarly - I think I like it ), I've been using Grammarly to proof my book. I'm still happy with it, but I did discover a problem it has with certain punctuation imported in a Word .docx file. One of Grammarly's features is a fix for 'Inconsistent punctuation.' It was upset that my files (which were .docx files exported from Adobe InDesign ) contained a mix of straight and curly apostrophe and quotation marks. I think the problem is that internally  InDesign fixes these issues in your original text on the fly, but if you export the text it sends out the original formatting rather than changing the punctuation. I figured that making this change in Grammarly was a good idea, but what I discovered is that after doing this, there were instances where single apostrophes and quotation marks were moved, particularly around a 'word' or if I had a single apostrophe next to quotation marks: "And then he shouted 'Fire!&#
2 comments
Read more

Grammarly - I think I like it

I’d seen the ads for Grammarly, a tool that promised to help me “ Compose bold, clear*, mistake-free writing with Grammarly’s AI-powered writing assistant, ” but I was skeptical. Maybe I didn’t want to spend the $139.95 a year it costs (there is also a $29.95 a month option.) [* that sentence came from Grammarly’s website, and Grammarly suggested changing the word clear.] This week I finally tried the free version, just out of curiosity, and after using it I was intrigued enough to get the paid version, a nd though it’s only been a few days, I like it. I’ve been running my book through it, and while we have a lot of disagreements (primarily over Unclear Antecedents), it has found enough spelling errors I had missed, and grammar and punctuation mistakes, to make me feel that it's worth the price. Pros • It finds spelling mistakes and grammar issues that I missed using other tools, and with multiple proof-readings. • It’s easy to use, though performance c
1 comment
Read more