[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 390
  • Last Modified:

Notes archive cabinet not showing archives

Notes users are no longer showing the archive database link in their expanded cabinet icon from the tools view. When the click the + to expand the tree for the cabinet it thinks for a minute, shows the cabinet expanded but does not show the sub branch of the tree displaying the archive. This seems to be system wide. All users archive to the domino server which also hosts their mail files.

Users can CTRL-O and browse to their archive database and open. This works fine, the ACL shows they have full admins over their own archive.

If I use an ID with admins and open a users mail db the archive link appears as it should. By default only users have rights to their archive so I can see the archive but when I click the link my access is denied. I can change the ACL for the archive to allow me and it works fine. This is just to prove that it is not an ACL issue with the users archive database.

I'm not sure what is going on. The user has full ACL over their own mailbox and archive, but only when an ID with admins is used can I see the archive link. I'm guessing this is a permissions problem but where?
0
staceyb1975
Asked:
staceyb1975
  • 5
  • 4
  • 2
  • +1
1 Solution
 
Sjef BosmanGroupware ConsultantCommented:
Is this a Domino.Doc server? Which release?

> it thinks for a minute...
This is in 90% of the cases caused by some network problem: DNS issue, duplicate IP-address, etc. Is there any clue in the log.nsf database??

I'd start with restarting the server, then test again.
0
 
staceyb1975Author Commented:
Just a normal domino server R6. Remember this is happening for all staff on all PC's unless you are using an ID with admins priv's. Doens't sound like any network problem to me otherwise domino admins would be included in the problem.

One of the network admins thinks this occured shortly after he accidently replicated an old version of the global names.nsf back to the server. There was a problem with backups so the old names.nsf with all the outdated data had to be cleaned up. Perhaps there is some sort of policy conflict? I really don't know what to look for though.

I think it's time to increase points to 500 though.
0
 
staceyb1975Author Commented:
By the way, server reboot does not help and nothing looks wrong in log.nsf
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
qwaleteeCommented:
This usually indicates that the user's archive profile in the mail file does not correspond to the servers/filenames that actaully hold the archive database(s).  Pick a user, go through his archive profile, and see whether the target matches your archive server name and the expected filename.
0
 
staceyb1975Author Commented:
They all match just fine, profile shows the correct server and archvie db while using a users ID.The link is missing however. I can pick any user, open their mail file with an admins ID and it's all fine. They open with their own ID which has full ACL's over mail and archive db's and it doesn't appear.
0
 
Sjef BosmanGroupware ConsultantCommented:
Maybe it's time to start a trace, from the Notes client: File/Prefs/User Prefs, Ports, Trace, and select the server the archive database is on. You can see all steps Notes takes to access the server.
0
 
staceyb1975Author Commented:
I've fixed the problem but still unsure why it's been caused. It looks like something to do with the archive policy which is enforced on the clients. I had to reset the local user policies to make it function. My local user policies were ok, which is why I could see it from my machine with admins but the user could not.

Anyway, here is the fix which needs to be performed on each users machine to ensure you are addressing each users local names.nsf.  *ouch*

1. Backup the users names.nsf file
2. Open users address book (names.nsf)
3. Go to the hidden view ($Policies)

a. To go to this view, press and hold CTRL + Shift
b. Click on View -> Go To

4. Delete all documents listed there
5. Go to the current location document

a. To go to this view
b. Click on View -> Go To
c. Expand Advanced and select Locations

6. Select the current location
7. Click on Edit Location
8. Click on Actions -> Remove Address book preferences
9. Click on Actions -> Advanced -> Set update flag
10. Click on YES when prompted
11. Save and Close the location document
12. Restart lotus notes
13. Edit the archive settings for the user and establish the archive location.

All fixed.
0
 
Sjef BosmanGroupware ConsultantCommented:
Wow! And you figured this out all by yourself? I'd never have blamed the policies, although you pointed into the right direction with "guessing this is a permissions problem". I assume the server mentioned in the Address book preferences was wrong, so Notes would look for the wrong (or a non-existent) server for some time (that's why I said that it looks like a network problem).  

Well, never too old to learn. Thanks!

Sjef

PS And a link to the origin of the solution would be nice... ;-))
0
 
staceyb1975Author Commented:
Can I request the points returnmed to me?
0
 
Sjef BosmanGroupware ConsultantCommented:
I have no objections. Put a question in the Community Support area, with a link to this one, asking for a refund.
0
 
qwaleteeCommented:
NB: If it was archive policies, then it really was the archive profile, since that's what archive policies get pushed to.
0
 
Vee_ModCommented:
Closed, 500 points refunded.
Vee_Mod
Community Support Moderator
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 4
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now