Unable to authenticate the package: 9780987119711.itmsp

I have been getting this same error message since I moved and changed Internet connection. I have contacted my provider, as advised by Apple. If anyone has a solution, it would be appreciated.

any clue anyone?

I too am having the same problem Mac version 10.6.7, everything is updated and up to speed...

Error Messages:

Error invoking web-service

An exception has occurred: javax.xml.bind.JAXBException

- with linked exception:

[java.lang.ClassNotFoundException: com/sun/xml/bind/v2/ContextFactory]

Could not connect to Apple's web service.

Unable to authenticate the package: 0793573022974.itmsp

It works on my laptop (older version), but is no good to me as everything is now to be done on our new MAC's.

I called support and they had no idea, they told me to go to their support page and that was no help, so I have been googling for hours now and still have got now where.

Anything anyone?

So, here is what support last replied to me for this problem:

Did you make sure to open all of the ports listed in the iTunes Producer user guide?

The thing is, I have no idea how to open those ports! I went to Network Utility in App/Utilities. Then, in Scan Ports, I entered the IPs that are in the guide, but it took hours to check them, and the result didn't make any sense to me. And even if the ports were closed, I have no idea how to open them! 🙂 I am a book publisher, not a developper!

With what you just said, I believe that it's due to an update that we've done. in November, I got this new MacBook Pro, and I published my first book smoothly with iTunes Producer, then a couple of months later, I started getting the error message, 'Unable to athenticate package', etc. and never again was I able to update or publish books in the ibookstore.

But what specific update caused it? And how to go back to the previous settings? I don't have an older computer with me. I would really like Apple to give us a solution.

Haha me too!...I'm just the music uploader..I'm not port/java/inter-ma-nerd language savy at all! (now I wish I was 😟)

I too think it has been caused by some update, as a lot of things went pear shaped after updates, but as to what it is I have no idea and I wish their support system was much better, especially if more than a hand full of people are having issues.

Well if I hear back from them I will let you know 🙂

I'm having this problem too. Very frustrating. I've done my best to make sure my epub file has its best shot at passing the additional validation that Apple performs (no non-unicode characters, no unmanifested files, correct date formats) as suggested by the "Contact Us" page that the iTunes Producer dumps me to, but no love. I've even tried uploading it to lulu.com's validator, which purports to do addtional checking over and above the epubcheck basic validation, and it passes that.

Did anyone hear back from Apple on this issue?

I have heard back today from Apple (yes really), who said:

"Hello,

This issue has been resolved. Please let us know if you have any further trouble.

Best Regards,

Kristen

iTunes Store

Indie Music Content

Technical Label Relations Group "

I don't now have a book I need to update so can't test it out (I uploaded eventually from another Mac).

If any of you who have this problem can now upload successfully it would be great to hear from you on this thread.

Thanks,

Robin

You got my hopes up, but I just tried it. Got the same error 😟

Thanks for posting anyway. I think I'm just going to let Lulu be my aggregator and let them take their 30% slice in order to resolve this issue for me.

*sigh*

ah ah! exactly the same here! Not successful. I also would like to go through an aggregator, but when I tried, it didn't work because one of my books is already published on iBookstore. I guess it recognised my Isbn or somehting... So I'm stuck. Ideas?

The only thing I can suggest you try is making sure that you have covered off as many of the points listed on Apple's FAQ (perhaps they tightened up the ePub validation since you first published it? Who knows!). This means checking the stuff that epubcheck doesn't, including:

- not including files not listed in the manifest (although I'm certain epubcheck does check for this)

- valid xhtml namespaces in every file

- valid date formats (perhaps including the time zone as they may be strict on this)

- correctly escaped characteres in URIs (e.g. no spaces)

- no characters that aren't UTF8 or UTF16. I have read of authors removing the copyright symbol and their epub then passing, which is crazy, as this symbol is part of UTF8, but I digress

- check that your file permissions when creating the epub are OK (see this thread: http://connect.lulu.com/t5/General-Discussions/Invalid-file-permissions-after-up loading-epub/td-p/75135)

I honestly don't know if there is anything else that Apple checks for when validating, but if there is, it's not clear. I guess it's not in the interest of the aggregators to divulge what extra checks are performed, as that knowledge is key to their business model.

And of course, having said all that, I have done this and my file *still* doesn't pass.

*grumble*

Good luck.

Thanks for that. I have checked all of the requirements and my Epub are definitely valid. I passed my aggregator's test. I do edit with Sigil, so I followed the instructions on your link. But still get the same unable to athenticate error message.

So I just heard back from iTunes support on this issue (a month later!!). The advice was "please make sure to open all of the ports listed in the iTunes Producer User Guide (see page 8 of the iTunes Producer User Guide 2.4)."

Like many of you, I am not a system administrator by trade, so while I studied computer science and am not intimidated by the Unix command line, I still didn't quite know what this meant. However, I asked a more knowledgable friend of mine who suggested that the issue might be my router blocking certain ports, not my machine (even though I have disabled the firewall on my router). Some googling turned up this site: http://portforward.com which contains step-by-step instructions on how to configure various models of ADSL routers to allow traffic on certain ports.

That said, after enabling port forwarding on my router for the specific ports listed in the iTunes Producer User Guide (TCP:33001, TCP:44001, UDP:33001-33100, UDP:44001-44100) I still get the "unable to authenticate" error message. The only difference is that the upload fails after about 13 minutes instead of about 2 minutes.

And now my attempts to upload my book to the ibookstore is no further progressed. But maybe this is useful for someone else!

Ooh, ooh. I stumbled upon the fact that I was running iTunes Producer 2.1.2, and the latest version is 2.4. Upgraded to 2.4 and the problem went away! Weee!

I hope this is the case for everyone else!!

PS. Apple: how's about some kind of notification in iTunes Producer that a newer version is available, huh? If Software Update can update the Java runtime on my machine, surely iTunes Producer could get added to that list???

I have encountered exactly the same problem (Unable to authenticate the package: etc.) and have received the same advice from the ibookstore, "please make sure to open all of the ports listed in the iTunes Producer User Guide (see page 8)."

Has anyone discovered how to make sure all the ports are open? My firewall is turned off and I cannot understand why they should be closed. I have downloaded the latest version of iTunes Producer.

It took Apple nearly four months to reply to my original question - 15th April until 5th August! I am beginning to lose patience.

Hi Maunderbeak

I had the same advice from Apple and asked a more technically literate person than myself. You may have noticed that the "Using iTunes Producer 2.4" guide lists a bunch of ports that it requires be open—443, 33001, 44001 for TCP; 33001-33500 and 44001-44500 for UDP.

My friend pointed out that the "opening of ports" refers to port numbers that are either blocked or made available for communication on your modem (router), not on your Mac. Apparently many routers, by default, do not permit communication on all port numbers, so a minimum level of security is in place by default. You can change this configuration by either opening these ports, or setting up "port forwarding" whereby an application on your local machine thinks it is using one port, but the modem sends it out to the internet on another port. If you know how to access the control panel (usually a web interface) for your router, then you can probably find some configuration settings that will let you configure this (I found this website useful: http://portforward.com/).

If you still can't figure it out then I would try asking a tech-savvy friend to have a look at your router settings with you and they should be able to work it out.

Hope that helps!

Matt