Get Access Back

You Can View User Feedback To This Tip

Need the ability to get access back to all applications on a server or assign a certain group access to all databases? This code will allow you to set the ACL of any and all databases on a server, even with local security enforced. This code will work as long as the server has Manager Access to the application. Place this code into a scheduled agent on the server.

Use the server ID to Schedule and save the agent. The agent will walk though all databases on the server and make the changes. It will create an entry in the Log.nsf file for each database.

Sub Initialize
 Dim session As New Notessession
 Dim count As Integer
 count =0
 On Error Goto ErrorHandle
 Set Directory = New Notesdbdirectory("")
 Set db=directory.getfirstdatabase(TEMPLATE_CANDIDATE)
 While Not (db Is Nothing)
  Count = count +1
  Print Count
  Call db.Open( "","")
  Print db.filename
  Call db.GrantAccess("Admin",ACLLEVEL_MANAGER)
  Call db.GrantAccess("Anonymous",ACLLEVEL_NOACCESS)
  Set db = directory.getnextdatabase
 Exit Sub
        Print "Skipped " + db.filename 
        Resume Next 
End Sub


  • There are two problems with this tip that render it mostly worthless for R5:

    1. You can no longer sign elements with the server ID from your workstation. The whole premise of the tip is that your ID no longer has access. However, you do have access to the server ID and can thus sign the element. This step is not easily done in R5 which should have been mentioned along with the instructions for doing so. Based on information from Lotus on how this is done in R5, the tip is of little help. A link to the tip from support.lotus.com is below: http://support.lotus.com/sims2.nsf/802ee480bdd32d0b852566fa005acf8d/d888c4b45ce7bf76862567dd00646502?OpenDocument&Highlight=0,signing,ID,R5

    2. The agent is described as a "Scheduled" agent. These types of agents can run on two types of documents -- all documents in the database and new or modified documents. That being the case, where would this agent be created since it is not truly "acting" on any documents but instead is modifying the ACL of a database. When you actually run the agent, it doesn't work because NO documents 'match' the agents criteria.

    — Reese Spears

This was first published in February 2001

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.