nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Activation Errors

mdbrandy

Been using Quicken forever. At the end of my first 2-year subscription (12 more days). Bought a new Activation key and tried to use it. I go through the Help->Enter Activation Code process, and after clicking the "activate" button, it just says that an error occured and to log in again. Tried multiple times over the past couple of hours. When I try to access Help->check membership status, it returns that it can't contact the Quicken server. I can login to my Quicken.com account on the web, so I do know the username and password. This is very frustrating. Is it likely just a Quicken server problem?

Find more posts tagged with

Accepted answers

Sherlock

I'm not having any difficulty with Help > Check Membership Status. I suggest you try Help > My Quicken Account.

If the issue persists, I suggest you reset the Quicken ID associated with the data file:

Image: https://us.v-cdn.net/6031128/uploads/editor/kx/bleg4hfycn9f.png

All comments

Sherlock

thecreator

Hi @Sherlock ,

The instructions are wrong for the Subscription program.

Open Quicken.
Click Edit.
Click Preferences.
Click Quicken ID, Sync & Alerts

Image: https://us.v-cdn.net/6031128/uploads/editor/1y/et6tors1xyrh.jpg

Click Sign in as a different user.

Sherlock

thecreator said:

Hi @Sherlock ,

The instructions are wrong for the Subscription program.

Open Quicken.
Click Edit.
Click Preferences.
Click Quicken ID, Sync & Alerts

Click Sign in as a different user.

I don't see the difference. They're a cut and paste directly from a current Quicken Support page. Your version of the instructions appears to be incomplete.

mdbrandy

Signing out and back in did the trick. I had seen that page in preferences, but since the login ID was correct, I didn't think I needed to do anything. But apparently the credentials had gotten messed up, so re-logging in did it. Thanks!