FTers,

I have been having a persistent inability to process upgrade requests online. This is the message I get:

"The passenger name in the reservation and the Mileage Plus number do not match. Please check the number and try again. If you encounter the error again, and the ticket was purchased through a travel agent, contact your agent."

I've been trying to solve this with my company's travel agency for 2 months. Today the 1K rep said it must be part of the larger issue of not being able to request upgrades online that they�re aware of and �working on.� He couldn�t give me a date of when it might be corrected.

Anyone else having this experience? More importantly, anyone found a workaround?

I just upgraded an entire trip on .bomb yesterday...no problems whatsoever. Same thing with a trip two weeks ago. Dunno.

No, my upgrades process fine. A theory: perhaps your M+account name uses a middle initial or middle name, and your travel agency does not.

Do your names actually not match? .bomb upgrade almost always works for me..

The names actually match! That's what is so frustrating about this. It started about 2 months ago after years of working fine.

This was my expierence.

My wife was listed as (not literally) Jane A Doe so if I would enter as Jane Doe it would not work.

It works when I use First Name: Jane A Last Name: Doe

Two hours ago, just did an on-line SWU C-F on an ORD-FRA flight for Monday. Worked just fine.

I have had this problem now for 2 months. Here is what I have found. I did an international leg in July, and somehow my passport actual entire name etc all got into my UA record. I can't remember if I entered it due to international flight or some computer sucked it from the record base. Ever since then...it gives me the exact same error msg. when I try to upgrade. All the names appear to match...I only found one place it doesn't. On .bomb, under the upgrade tab choice the name in that section of the web does not match...it lacks my middle initial etc. How exactly the upgrade section got a different "version" of my name is a puzzle to me. And why it retains this version even though MP has the correct name...

I have spoken to website support, they told me a month ago it was a "known issue" they are trying to debug. In the meantime I have just been calling in any upgrade requests...and not holding my breath that they are gonna debug it.

I've had no problems at all. Not for upgrades for me, by me, or upgrades for me, sponsored by someone else, or upgrades for someone else sponsored by me.

I have multiple variations of my name in "my itineraries". None seem to give a problem.

Maybe your problem is with your Travel Agency? I would check there...

Good luck!

Here's an earlier thread with the same issue.

I have the same problem requesting upgrades online, but I've just been calling the automated 1K line and submitting the requests there. If they're confirmed, I log onto .bomb and update my seat selection.

Good luck!

+1 with problems.

Has been mentioned before on FT.

Started a few months ago and I don't book with a TA.

Way to go .bomb

Thanks for the information about your experience. There may be something in yours that will help mine.

Thanks too to the person that supplied the other thread. I thought it had been addressed before but I couldn't find it.

I have the exact same problem and it started in the Spring/Summer timeframe. I suspect it has something to do with my last name, it has a space on my passport, but on UA it is all one word. I've reported it several times with no response or fix. I continue to call in my upgrades for now. I notice that on my itineraries they have my name listed now as 'FIRST LASTNAMEMRS' - I've pointed this out to them, but it doesn't seem to ring a bell in their minds that this could be the problem. Sigh....

The problem is caused by a difference of your name in your corporate travel department profile.
For example, if your name is Nicholas, it may be stated as Nick with your MP account, and Nicholas with your travel department. The discrepancy causes .bomb to error out.

+2 for me and my partner. In fact, one trip was booked using .bomb, and it still gave us the error message. Ended calling anyways - no problem there.