Domino 8.5 Unablie to store document in database, not authorized …
Home > IT Answers > Lotus Domino > Domino 8.5 Unablie to store document in datab...
DogMatrix
25 pts.
0
Q:
Domino 8.5 Unablie to store document in database, not authorized ...
Domino 8.5, Domino Administrator, Lotus Notes 8.x, Data Replication
Hi,

I am a Domino Developer and using Domino 8.5.

One of my databases (8GB)does not replicate all the documents to all servers.

 Error:

Unable to store document in CPT01/SJohns Debt CollectS Johnscdb.nsf (NoteID = 5941202) from Debt Collect/S Johns/cdb.nsf (NoteID = 6315334): You are not authorized to perform that operation (for each document)




I have googled and searched everywhere and did what they say but still not working.

I have checked that the LocalDomainServers have all rights.

I have deleted the replication history.


What happened:
 I created a reader field [BranchAccess] on a form with roles [DBN] [PTA] [CPT] [PMB] I also cleared the $readers field. Since that day the error started.

My final option I see is to delete all databases at branches and replicate again but this will take 2 to 3 days per branch and there are 4 branches and we can not affort to stand still.


Is there any other way to clear the security/encryption/authorization on bulk documents?

Thank you

Software/Hardware used:
Domino Designer 8.5, Domino Administrator 8.5
ASKED: Sep 29 2009  4:38 AM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Brucelill
295 pts.
0
A:
 RATE THIS ANSWER
+1
Click to Vote:
  •   1
  •  0
  • AddThis Social Bookmark Button
Check to see if there is any $readers fields. If you have an admin client, open the database after clicking on the menu - Administration / Full Access Administration. Then you can open the database and see all documents.

When ever you use readers field always add an author field with the Server group "LotusDomainServers" or the Domino Server names (for the servers that replicate).

Clearing the fields don't always work since not all servers can see the document to replicate the changes.
Last Answered: Sep 29 2009  1:20 PM GMT by Brucelill   295 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Gabe9527   2385 pts.  |   Sep 29 2009  4:18PM GMT

The problem you have is that if the readers field has been added to all of the documents simplely removing the field will not remove the READERS etc. This is why a DB needs to have a Admin server with the ability to change these fields. They are not easy to change as each document will need to be changed etc.

Would it be possible to run some thing against the DB to change all the relevant fields?

 

Gabe9527   2385 pts.  |   Sep 29 2009  4:22PM GMT

Information below taken from IBM Technote
 <a href="http://www.ibm.com/developerworks/lotus/library/reader-names/" title="http://www.ibm.com/developerworks/lotus/library/reader-names/" target="_blank">http://www.ibm.com/developerworks/lotus/…</a>


Rescuing hidden documents

If you use Reader Names fields on documents and you inadvertently make some documents inaccessible to all users (for example, by inserting multiple entries as a single invalid entry as described earlier), then you can use Full Access Administration mode (see figure 7) to open the database and to rescue those documents. In advance, create an agent that applies the appropriate Reader values, and then when in Full Access Administration mode, you can trigger that agent to fix your data.

In most organizations, only a select group of administrators has the ability to use this Full Access Administration mode, so users may need to queue up to get this done, but at least, it’s possible without sitting down at the server and using the local Notes client to bypass Reader security.

Figure 7. Full Access Administration option
Full Access Administration option

 

Ppolette   275 pts.  |   Sep 30 2009  2:48PM GMT

You’ll probably have to run the agent on every replicas you have. If your server is not allowed to replicate, fixing it only on the hub server not allowed will not propagate to the satellite : your hub server will still not be allowed there.

 

Ppolette   275 pts.  |   Sep 30 2009  2:51PM GMT

Another thing : if you sign the agent with an appropriate ID and enable the agent to run in full admin mode, allowing it to run on everey servers, you should be able to schedule it.

 

DogMatrix   25 pts.  |   Oct 8 2009  9:51AM GMT

I would like to thank you all for your answers. I checked all my servers and also run the agent. It worked.

Thank you

Johan

 
0