1

Topic: Login problem

Oddly I'm presented with a login screen telling me that this is the first time I've logged into Recorder (not true).
It asks me to use the password "password" - that doesn't work.
Nor does my real password

Help!

2

Re: Login problem

Windows 7 update last night and I had to reset my Kaspersky too. Could that be a clue?

3

Re: Login problem

As far as I know all the usernames/passwords (and first login flag) are stored in the database. If you're not getting a database connection error (or any other error), I would check the contents of the USER table.

(Updates here as well, but no problems logging in)

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

4

Re: Login problem

It's all there, RecordCleaner detects everything without problems and opening MS SQL Server Management Studio seems to show everything fine.
You'd have to know your way around MS SQL though, I'm not getting any sense out of the dbo.USER table. Perhaps someone knows where to look in this table and what to do

5

Re: Login problem

Darwyn Sumner wrote:

I'm not getting any sense out of the dbo.USER table.

The USER table has five fields: NAME_KEY, PASSWORD, SECURITY_LEVEL, FIRST_LOGIN, FULL_EDIT_OWN_DATA, with a row for each user. Should be obvious if the password is wrong/first login flag is set.

Do you mean you're having trouble viewing the contents? User is a reserved keyword and has to be enclosed in quotes to get valid SQL.

select * from "USER"

should work. I don't use MSQ SQL SMS, but it may be having trouble with that.

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

6

Re: Login problem

If there's more ways of taking a look at the dbo.USER table than MS SQL SMS then I'm missing it.
I make a beeline for MS SQL even though it scares the willies out of me, I wouldn't dare change anything - I'm an SQL 2000 course dropout

Solved it.
I highlighted the dbo.USER table, right-clicked its name and selected "Select Top 200 Rows" (took me a while to figure out that's how you look at the actual data rather than the properties)
It still had my original JNCC 4-digit code in there, don't ask me how that happened, yesterday I used the login I'd been using for donkeys years.

(Good job I keep a decent record of all passwords in KeePass (free))
Now I'm in, I'm off to change the password back to my usual one ...

7

Re: Login problem

I think there may be more  to this that is immediate apparent. Information on users and first use is stored in the User table. Theoretically R6 could delete entries (although I don't know how), but there is no way  it could  retrieve the old information.I would check that other aspects of the database are what you expect. Could you haven't accidentally restored back to an earlier version.

Mike Weideli

8

Re: Login problem

Everything seems fine now, just as I left off the other day.
It's like an Agatha Christie mystery isn't it?
Perhaps the real culprit will never be found.
Anyway, thanks Charlie and Mike for the clues.