I've installed Umbraco latest version on SQL CE yesterday and everything went smoothly. Then my session timed out and I couldn't login again. First I thought that I've misspelled the password so I re-installed the bastard and everything was fine.
Now, this morning, I can't login again, what the heck is going on here ?
Am I totally losing it ?
- Smokey, this is not 'Nam. This is bowling. There are rules.
Check your cookies and make sure that the UMB_UCONTEXT cookie doesn't have an experiation in the past (it should be 24 hour from when you logged in).
If you got desperate and tried to log in loads of times, your account will be locked. You can see a message in the log about that. The default number of password attempts is set to 10 so after 10 tries your account will be locked. You'll need to go into the umbracoUser table and find your user, the column userNoConsole should be set to 0, if it is set to 1 then that means your account is locked.
Unable to login, using 7.2.6 on SQL CE
I've installed Umbraco latest version on SQL CE yesterday and everything went smoothly. Then my session timed out and I couldn't login again. First I thought that I've misspelled the password so I re-installed the bastard and everything was fine.
Now, this morning, I can't login again, what the heck is going on here ? Am I totally losing it ?
- Smokey, this is not 'Nam. This is bowling. There are rules.
Hi Sebastian,
Are you running on IIS Express. I self had some issues with changes not being persisted in SQL CE.
There is also an issue about it : http://issues.umbraco.org/issue/U4-4621
Dave
No, running on 2008 R2 with IIS 7, I guess.
If you look at the issue the problem is definitely SQL CE. In some cases data is not written to the database.
Two things to look at:
UMB_UCONTEXT
cookie doesn't have an experiation in the past (it should be 24 hour from when you logged in).umbracoUser
table and find your user, the columnuserNoConsole
should be set to0
, if it is set to1
then that means your account is locked.It was the userNoConsole :)
But I don't get why I got it in the first place, since I use a password manager.
Now it's fixed.
is working on a reply...