musescore.com download PDF including parts returns "NoSuchKey" error from AWS when re-edit & re-download

• Jul 12, 2015 - 08:37

I was reuploading scores and got error when try to download PDF including parts a second time after revising a score.

I think the replication steps are:

  1. upload a multi-part score to musescore.com
  2. on the score webpage, press "Download"->"PDF including parts"
  3. go ahead and re-edit your mscz and re-upload
  4. on the score webpage, press "Download"->"PDF including parts"

and then I get an error message from AWS:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>65943/1448986/fd30337f66/general-parts/score-parts.pdf</Key>
<RequestId>5F7885A9CC15C89D</RequestId>
<HostId>p7fHngL5LIOHO6C9W6MKE9PgOz7cnJR6Un76K/bHToCQZ9NSKEY5bhXy+l84+Gj6</HostId>
</Error>

If I redit my score again and reupload, then I get a slightly different RequestID and HostID and the 2nd / of Key:

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>NoSuchKey</Code>
<Message>The specified key does not exist.</Message>
<Key>65943/1449021/fd30337f66/general-parts/score-parts.pdf</Key>
<RequestId>DEF57FDCF8635CDC</RequestId><HostId>i+PiXhsH8VEF1jlKDzQmUZYf3BmRDzQZi/d6iN6DrnmcPTfsgXAPCwhD5ykEadm2/BcLEvoQvEo=</HostId>
</Error>

I suspect that upon re-upload, the musescore.com server is not updating it's database to indicate that the multi-part PDF needs to be regenerated.

I originally noticed this when I was updating https://musescore.com/ericfontainejazz/moonlight-sonata but I have been able to replicate with new scores simply by first downloading/generating the multi-part pdf, re-editing, re-uploading, and trying to re-download multi-part PDF.

Attachment Size
error.txt 403 bytes
error2.txt 406 bytes

Comments

Hi Eric, a fix for this problem has been deployed. Thanks again for letting us know. For a next time, you may also report site problems directly via the contact form or to support at musescore dot com.

Do you still have an unanswered question? Please log in first to post your question.