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

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

Disappearing Calendar Appointments

Hello

I have had a strange problem lately. One of my users is losing her appointments every night. These appointments are ONLY ones that my app schedules. If it matters, the code I use to schedule appointments is here www.vortexwd.net/lotusnotescalendaring1.asp.  This only happens for one user out of five who this app schedules for. The appointments go on to the calendar just fine but disappear by the next day. I have read several paq's on this subject but they didn't help. Please advise

Thank you

-jkorz
0
jkorz
Asked:
jkorz
  • 4
  • 4
1 Solution
 
Sjef BosmanGroupware ConsultantCommented:
Interesting... Losts of ideas where to look:
- If you see the document count of the database on one day and the next, are there indeed documents missing, or are they just invisible?
- Do you have a view that shows ALL documents? They are also missing there?
- Is there an agent that adds Reader fields? Or one that removes Appointments?
- Is there a replication setting for "Remove documents not modified in the last 2 days" or so?
- Mail database corrupt? Did you run a Fixup from the Admin client on the database?
0
 
jkorzAuthor Commented:
This is not my job, so I am pretty dumb when it comes to lotus notes. The people who are supposed to be supporting it insist that it is my app's fault so that they don't have to fix it so now it's my problem. Could you tell me how to get the document count or create a view that shows all documents? Additionally, I don't have access to the admin client but I can see if they will do that for me.

Thanks
0
 
Sjef BosmanGroupware ConsultantCommented:
Hm, thanks, I'll bear that in mind. By the way, that reminds me of a story about 4 guys, Anybody, Somebody, Everybody and Nobody. Must look that up some day... Found it: http://www.volunteermemphis.org/MTVVOLGUIDEPOEM.htm

Start telling those "admins" that whenever a document appears in a database, it ain't going to leave out of its own, unless the database is corrupt. There must be, and there usually is, a very plausible reason for such a phenomenon.

If the document disappears during the night, start looking at the activity log of the database: File/Database/Properties, 2nd tab (i), User Detail. Then find out who/what did something during the night. The number of documents you can see on the same tab, at the top.

Is there any archiving set up for the mail database?

Check File/Replication/Settings, Space Savers, what's configured for "Remove documents not modified in the last x days"? And how many days?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
madheeswarCommented:
and also check if there are any Schedule agents running to remove these docs.
As Sjef pointed out, check no.of docs in the database in the night and in the next day.
if it is NOT a custom made Mail database, then Refresh/Repalce the design.

First check all the scenarios what Sjef told. You will get some clue out of it.
Nice analysis Sjef.
thanks
maddy.
0
 
jkorzAuthor Commented:
I haven't forgot about you guys. The user and I have had conflicting schedules for a couple days so I haven't had a chance to try it out.
0
 
jkorzAuthor Commented:
as usual sjef, you're the man
0
 
Sjef BosmanGroupware ConsultantCommented:
:) Thanks!

And what was it after all?
0
 
jkorzAuthor Commented:
Oops, I should have accepted your first comment. The admins finally ran a fix on the database and that took care of it (you see how quick they get around to fixing things). Either way, they were disappointed when it wasn't my app's fault :-D

BTW, great story about Anybody, Somebody, Everybody and Nobody.
0
 
Sjef BosmanGroupware ConsultantCommented:
That story isn't the right one, compare it with this link: http://answering-islam.org.uk/Humor/nobody.html

Oh, heck, here it is:

This is a story about four people named Everybody, Somebody, Anybody, and Nobody. There was an important job to be done and Everybody was sure that Somebody would do it. Anybody could have done it, but Nobody did it. Somebody got angry about this, because it was Everybody's job. Everybody thought Anybody could do it, but Nobody realized that Everybody wouldn't do it. It ended up that Everybody blamed Somebody when Nobody did what Anybody could have done.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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