Javier:

I have not personally.  I am using R:BASE eXtreme 9.5 64-bit.  My employer 
has R:BASE X Enterprise but we have not yet fully implemented the upgrade 
to see if the issue still exists.

I totally disassembled my database today and re-built it from scratch.  I 
unloaded the structure and data files separately, deleted the original 
database and then built a totally fresh database.

I'm anxious to see what happens when the next maintenance process runs 
tomorrow.

I'll let you know.

Kind regards.




Mike Ramsour
AK Steel Coshocton Works
Quality Department
Phone:  740-829-4340
Cell:  740-502-1659



From:   "Javier Valencia" <[email protected]>
To:     <[email protected]>, 
Date:   06/15/2017 03:11 PM
Subject:        RE: [RBASE-L] - Password error
Sent by:        [email protected]



I ran into the exact same issue. I have a database with owner and password 
and I did an unload all, changed the size for all the occurrences of one 
text column (increased from 3 to 6) and ran the file and now the original 
owner and password do not work. It has been a few weeks since I did this 
and I do not recall all the details but I know I tried  working with the 
OWNER in the original file with no luck. I had never ran into this problem 
before so this has happened only in recent versions and I remembered 
seeing Alastair?s posts on the subject and my problem was similar but I 
did not have the time to work with it any more. 
Obviously, something has happened since there are several of us with the 
issue. Has anyone reported this as a potential bug?
 
Javier,
 
Javier Valencia, PE
O: 913-829-0888
C: 913-915-3137
 
From: [email protected] [mailto:[email protected]] On Behalf 
Of [email protected]
Sent: Thursday, June 15, 2017 9:40 AM
To: [email protected]
Subject: Re: [RBASE-L] - Password error
 
Salutations: 

Our situations sound very similar, Alastair. 

Thanks to all for the various suggestions that have been offered.  So far 
I can't find anything that explains this behavior, either. 

Another odd aspect to this issue is that the password error doesn't happen 
on the nightly maintenance routine.   

The nightly program does an "UNLOAD ALL" and then recreates each database 
before running the backup program. 

The morning maintenance routine only does a backup.   

In between those events the database gets loaded with new data from CSV 
files and then a "PACK KEYS" command is run. 

R:SCOPE didn't indicate any issues. 
There's no place in my programs where "NONE" is referenced. 
The owner is "PUBLIC" and there is nothing in the "User privileges . . ." 
dialog box on the Utilities menu. 

When the   -ERROR- The current password is not correct for this user 
identifier. (2867)  error is encountered entering NONE in the password box 
satisfies the program and it goes on its merry way. 

There's nothing unique about this particular database.  It only has two 
tables and a few views.  There are no forms or reports. 

I am officially stumped. 



Mike Ramsour 
AK Steel Coshocton Works 
Quality Department 
Phone:  740-829-4340 
Cell:  740-502-1659 



From:        Alastair Burr <[email protected]> 
To:        karentellef via RBASE-L <[email protected]>, 
Date:        06/15/2017 10:34 AM 
Subject:        Re: [RBASE-L] - Password error 
Sent by:        [email protected] 




I spent days editing the unload file(s); using SET USER and a few times I 
thought I had conquered it but eventually the need for NONE appeared 
again.

As far as I recollect (always dangerous) neither NONE nor PUBLIC ever used 
to appear in the unload file - only the owner password if one existed for 
the owner name. (Prior to that only the owner name.)

PUBLIC was implied by not having an owner or added via the GRANT system.
NONE just seems to have appeared but when I don't know. It can/should be 
used to remove a password according to help. Maybe R:Base is suddenly 
taking it literally and storing NONE as the password but that wouldn't 
explain why it suddenly decides to need it.

I presume AUTHOR is the SQL way of saying OWNER?

Regards,
Alastair.


On 15/06/2017 14:13, karentellef via RBASE-L wrote: 
I've never had a database with an owner PW so I don't know much
about them.  But when I unload schema for my personal consulting 
database it says:
    CREATE SCHEMA AUTHOR CONSULT PUBLIC

I'm not sure why mine says 'PUBLIC" rather than "NONE".  I do not
have any privileges granted.  Can you try changing it to Public and 
see if that sticks?

And I'm curious myself:  what does the word "AUTHOR" mean?  Is
that always there, or does it mean something?

Karen




-----Original Message-----
From: Alastair Burr <[email protected]>
To: R:Base Listserver 2016 <[email protected]>
Sent: Thu, Jun 15, 2017 5:42 am
Subject: Fwd: Re: [RBASE-L] - Password error

For some reason this went direct to Mike rather than the list. 


-------- Forwarded Message -------- 

Subject: 
Re: [RBASE-L] - Password error 
Date: 
Wed, 14 Jun 2017 17:02:25 +0100 
From: 
Alastair Burr <[email protected]> 
Reply-To: 
[email protected] 
To: 
[email protected]



I have the exact same problem - mentioned here a good few months back.

I can give you the solution but I cannot get rid of the problem - it keeps 
coming back.

The solution is that the "null" or non-existent password gets sets to 
"none" for no obvious reason.

If you type in the password as "none" you will get in as normal.

If you unload to a file and edit it you will see it in the Create Schema 
command. I've edited it endlessly but it still comes back. I gave up and 
cut my loses and now just enter "none" - I can't waste more time on it. 
It's just one database; my other four are fine.

For what it's worth, I loop through and autochk, copy (reload) to a new 
folder as well in my back-ups in case that's relevant somehow.

Good luck,
Regards,
Alastair.


On 14/06/2017 15:47, [email protected] wrote: 
Good day: 

I have a daily backup routine that loops through about 20 databases.  The 
program connects to a database, AUTOCHKs it and then copies it to a backup 
folder. 

There is one database that generates the following error when the program 
attempts to connect to it:  -ERROR- The current password is not correct 
for this user identifier. (2867) 

The owner of the database is set to public and there has never been a 
password associated with the database. 

Entering a bogus password or clicking through it generates this message:  
-ERROR- Incorrect password.  User identifier has been changed to PUBLIC. 
(2870) 

After which the database gets backed up. 

I cannot find anything that would indicate why this is happening to this 
one particular database.  I've checked it, I've rebuilt it and still I get 
the message. 

Using eXtreme 9.5, I would appreciate some suggestions or insight into why 
this happens or what I can look for. 

Thanks for any help. 



Mike Ramsour 
AK Steel Coshocton Works 
Quality Department 
Phone:  740-829-4340 
Cell:  740-502-1659 
Confidentiality Notice
This message is intended exclusively for the individual or entity to which 
it is addressed and may contain privileged, proprietary, or otherwise 
private information. 
If you are not the named addressee, you are not authorized to read, print, 
retain, copy or disseminate this message or any part of it. If you have 
received this message in error, please notify the sender immediately by 
e-mail and delete all copies of the message.
-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
For more options, visit https://groups.google.com/d/optout. 

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
For more options, visit https://groups.google.com/d/optout. 
-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
For more options, visit https://groups.google.com/d/optout. 
-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
For more options, visit https://groups.google.com/d/optout. 

Confidentiality Notice
This message is intended exclusively for the individual or entity to which 
it is addressed and may contain privileged, proprietary, or otherwise 
private information. 
If you are not the named addressee, you are not authorized to read, print, 
retain, copy or disseminate this message or any part of it. If you have 
received this message in error, please notify the sender immediately by 
e-mail and delete all copies of the message.
-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
For more options, visit https://groups.google.com/d/optout.
-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an 
email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Confidentiality Notice
This message is intended exclusively for the individual or entity to which it 
is addressed and may contain privileged, proprietary, or otherwise private 
information.  
If you are not the named addressee, you are not authorized to read, print, 
retain, copy or disseminate this message or any part of it.  If you have 
received this message in error, please notify the sender immediately by e-mail 
and delete all copies of the message.

-- 
You received this message because you are subscribed to the Google Groups 
"RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to