Yes, it was definitely on the server side and NOT something any of us as the users could fix. Looks like it was finally fixed sometime in the late afternoon yesterday (PST).
But it's not right to make the users jump through hoops and spend WAY more time trying to fix it on their end before they address it themselves. Unless I have no choice next year or they, at least, offer some partial refund, I won't be using this part of the TurbotTax software suite for my returns again.
