@Dennis: Glad to hear that disabling AME's native sequence import has resolved this for you. The basic difference is that with native sequence import, all the code used to decipher the Premiere sequence is internal to AME; when that option is disabled, AME resorts to PProHeadless to read the sequence. Beyond that, I'm not intimately familiar with any differences, but my understanding is that the actual code should be the same--it's just a matter of where it "lives."
But that does lead me to wonder exactly what version you have installed of Premiere Pro and AME. I'm thinking this could result from the two apps being on slightly different versions, like PPro being on 2014.0.1 while AME is on 2014.0.0.