Hi !
Is it necessary to prohibit the out of office agent for design refreshs in Single Copy Templates ?
I have the problem, when activating the out of office agent, it will be disabled every night by design task.
Any suggestions would be nice.
Thanks
Sascha
Subject: Out of Office & SCT
I have the exact same problem now.
We upgraded a lot of users from R5 to ND6.0.2 CF1 and we ran load converts using mail6.ntf as the template.
Then we decided to upgrade 1500 templates (there are still 6000 to go) to SCT. We did this by creating a replica of the mail6.ntf and calling it sctmail6.ntf. We made this template a single copy template and did the following:
load convert mail/*.nsf stdR6mail sctmail6.ntf
load design mail/*.nsf
load compact mail/*.nsf
These templates have been in place for weeks now. We are now experiencing the Out Of Office problem the Sascha describes above.
A user with the SCT enables their OOO agent. They go on holiday, and the next day their OOO agent is set to disabled again. No ore OOO messages are sent to them.
From all of Joe’s posts, it seems that the answer is to do the following when you convert to the SCT:
load convert mail/*.nsf stdR6mail sctmail6.ntf
load design mail/*.nsf
load design mail/*.nsf
load compact mail/*.nsf
Is this the case? If so, that is fine for new users being converted onto SCT. What do we do for the existing users?
We also run design task every night, so in many cases, the mail file has had design run over it at least twice before the user gets to it.
We are currently doing some testing here.
So does anyone know how to get out of this problem we have?
Please keep me informed of any developments.
Subject: Out of Office & SCT
You know SCT databases does not refresh form a template because the shared (or core) design elements are not in the mail file but in the template. I wonder if the SCT is the source of your problem. Did you make the SCT per the IBM red book?
Subject: RE: Out of Office & SCT
Yes, I know that all design elements are not longer in the database.I created the SCT as described in all the available technotes:
http://www-1.ibm.com/support/docview.wss?rs=474&uid=swg27002574
But I can also see the design task updating the out of office in the users mailfile, when the out of office was activated by them.
17.07.2004 01:08:15 Updating ‘OutOfOffice’ into database ‘John Doe’ from template ‘Mail6SCT’
Subject: RE: Out of Office & SCT
I am going to have to setup this up and track it specifically. If you can give me today/tonight, I will see if I can duplicate the behavior. I don’t remember if I had to make a change or not.
Subject: RE: Out of Office & SCT
Hi, thanks for your help.
I tried it again.
Activated out of office, run design -f mailfile → update
IBM send me a technote, but in my case it will update always the out of office not just at the first time design runs.
I dont like to prohibit design elements…
Title:
Out of Office agent disables in a Single Copy Template DB
Product:
Lotus Notes > Lotus Notes > 6.x, 6.5
Platform(s):
Platform Independent
Date:
11.12.2003
Doc Number:
1154528
This document is based on the following Software Problem Report (SPR):
Display SPR Links
SPR Number
SPR Status
SPR Fixed Release
CYII5TT9J8
Not a Bug
Not Applicable
Problem
Enabled out of office agent becomes disabled in a db created with mail6.ntf single copy template when design task runs for the first time in the mail file.
Tested this in notes 6.02cf2 and 6.5 on Win2000 and Solaris8.
Content
This issue was reported to Lotus Software Quality Engineering and has been determined to not be a bug. The behavior is by design. You can check the design properties of ooo agent to Prohibit design refresh or replace to modify so the enabled status won’t get changed.
Workaround is to run design task as soon as you create the mail file using single copy template or after converting the mail file to single copy template.
It only disables the out of office agent the first time design task runs if it’s enabled.
After design task run the first time in the mail file , out of office agent will stay enabled.
Subject: RE: Out of Office & SCT
From what I read you would only need to run design after the database is created. I think the disconnect here is the order of events.
If I create a new user mail database from a SCT, the new database will not be of a small size. Until design and then compact runs, the database size will change to a smaller size. Then if the user subsequently marks himself or herself “Out of Office”, I am understanding this problem would not occur.
let me know if this clears up some of the confusion. I perform a test on my domino server and this is the result I was able to verified.
Subject: RE: Out of Office & SCT
I am not really confused, but I still have the problem.
My steps:
I Eeable the out of office via tools in my mailbox
Check for activated out of office
run design on my mailfile (the same as every night)
out of office will be updated by design (disabled)
I can do this again and again.´
Can you reproduce this?
the design task will update every out of office agent, when changed by the user.
There was another discussion with Ben Rose (OpenNTF) for remove the design task from servertasksat1, but then I have the problem to run design on all new databases manually to remove the design elements and get the benefit of SCT…
Thanks
Sascha
Subject: RE: Out of Office & SCT
i>I updated the text since it has some errors (incomplete thought or bad word
usage).]
I can duplicate your situation, but there is a difference from what I am
recommending and what you are doing. Hopefully this explain will solve the
disconnect between us.
From the process you described, you (though not purposefully) are making
changes to the agent (enabling the agent) prior to Domino design task has had
time to remove those design elements from a database whose template is marked
as a Single Copy Template OR sync the database design where it did not have to
make any changes (I am calling this an extra cycle of design.) If the design
task is able to complete a design without changing of the elements in the
database (even if it is SCT) you can thereafter enable agents without having
this issue. TO WIT, I duplicated what you are doing, but what I did different
is to trigger the design task right after it disable the enable out of office
agent. On this iteration of the design task, design made no changes to the
database. Thereafter I enable the agent and load the design task again. For
this iteration the design task will not disable the enable out of office agent.
This is no different than if I enable an agent in any custom defined database.
This behavior is always similar. You can also get the same behavior if the
template’s agent had changed or recompiled (and disabled in the template) then
have design fresh all the databases from the template.
Now what I recommend for you to never have this problem, is to do the following
after you create a new mail database: 1) create the database, 2a) run the
design task prior to letting the end user use the database, and 2b) run design
again for this iteration to not make any changes to the database, 3) compact
the database (to shrink the size down to nothing since it is based on a SCT
template), and 4) give the database to the end user. The user can then use out
of office without having worrying their agent being disable by a server nightly
task.
Does this clarify things? if not feel free to email me more specifics.
I testing the able scenario and was able to verify the contents of this post to
work based on the test procedures.
HTH
Subject: RE: Out of Office & SCT
Hi Joe,
at the moment I have the dim feeling to be too stupid for that 
From the process you described, you (though not purposefully) are making changes to the agent (enabling the agent) prior to Domino design task has had time to remove those design elements from a database whose template is marked as a Single Copy Template OR sync the database design where it did not have to make any changes (I am calling this an extra cycle of design.) If the design task is able to complete a design without changing of the elements in the database (even if it is SCT) you can thereafter enable agents without having this issue. TO WIT, I duplicated what you are doing, but what I did different is to trigger the design task right after it disable the enable out of office agent. On this iteration of the design task, design made no changes to the database. Thereafter I enable the agent and load the design task again. For this iteration the design task will not disable the enable out of office agent.
When I change my out of office agent the design task was already running dozen times in the night on all mailfiles ? So all elements are already removed or are they not?
A user will work with his mailfile normally after the daily design task, mostly also after the second daily design task, after that compact -B will reduce the size.
The out of office agent will not be changed at the first day !
This is no different if I enable an agent in any custom defined database. This behavior is always similar. You can also get the same behavior if the template’s agent had changed or recompiled (and disabled in the template) then have design fresh all the databases from the template.
I thought I know about the agents when chaning the design, but the agent in the template was not changed and the signed date is prior then the enabling of the out of office. So in my opinion the designelement for the out of office agent will be part of the nsf file and not longer a link to the template ? Wrong ??
Now what I recommend for you to never have this problem when you create a new mail database was to: 1) create the database, 2a) run the design task prior to letting the end user use the database, and 2b) run design again for this iteration to not make any changes to the database, 3) compact the database (to shrink the size down to nothing since it is based on a SCT template), and 4) give the database to the end user. The user can then use out of office without having worrying their agent being disable by a server nightly task.
Here my steps:
Userservice creates user and mailfile (user will begin in 2 or 3 days)
At night the design task removes the elements and links to SCT template
compact will run the next evening to reduce the size (more than 10%) lo compact -B -S 10
design task is running the 2nd time (2nd night)
The user normally will not come to work at the first day and enable the out of office agent.
So what is the different between your step 1 to 4 and my steps? Is there the need to manually do tasks?
In the last cases I converted the mailfiles manually, directly after that I ran design and compact.
lo convert
lo design
lo compact -B
But still the same problem…
Which of my steps is wrong ??
And why is IBM saying, prohibt the design of the out of office agent, when design is changing the agent, also after the first time design ran??
Title:
Out of Office agent disables in a Single Copy Template DB
Product:
Lotus Notes > Lotus Notes > 6.x, 6.5
Platform(s):
Platform Independent
Date:
11.12.2003
Doc Number:
1154528
This document is based on the following Software Problem Report (SPR):
Display SPR Links
SPR Number
SPR Status
SPR Fixed Release
CYII5TT9J8
Not a Bug
Not Applicable
Problem
Enabled out of office agent becomes disabled in a db created with mail6.ntf single copy template when design task runs for the first time in the mail file.
Tested this in notes 6.02cf2 and 6.5 on Win2000 and Solaris8.
Content
This issue was reported to Lotus Software Quality Engineering and has been determined to not be a bug. The behavior is by design. You can check the design properties of ooo agent to Prohibit design refresh or replace to modify so the enabled status won’t get changed.
Workaround is to run design task as soon as you create the mail file using single copy template or after converting the mail file to single copy template.
It only disables the out of office agent the first time design task runs if it’s enabled.
After design task run the first time in the mail file , out of office agent will stay enabled.
Subject: RE: Out of Office & SCT
Sascha,
I hope this info helps you. I have within italics your responses with my reply
thereafter:
i>at the moment I have the dim feeling to be too stupid for that
]
I am not sure what you mean with the “that” reference.
i>When I change my out of office agent the design task was already running
dozen times in the night on all mailfiles ? So all elements are already removed
or are they not?
] The first running of the design task against the
database will remove the design elements from the newly database. The database
size will not decrease until the compact task runs.
i>So what is the different between your step 1 to 4 and my steps? Is there
the need to manually do tasks?
] The difference from what you are doing
and what you I am doing is TIME. I did all my items immediately after the
database was created. IBM’s technote also recommended for it to be done
immediately. (You could alternatively do a design refresh, compact, and a
design refresh from the desktop or an agent rather than have the server do it.)
Feel free to email me on more specifics to your situation – we can correspond
offline to LDD.
HTH
Subject: RE: Out of Office & SCT
Was there any resolution here? I’m experiencing the same thing. Every night at 1am when the design task runs, it disables the out of office agent on my SCT mail db’s.
Everything I’m reading in this thread refers to running design on a db when it’s first created. Nothing ever says how to fix the existing db’s that are currently having the problem of the out of office agent being disabled nightly. Anybody have a resolution?
Subject: RE: Out of Office & SCT
+1
I’m also looking for a solution for this issue
Subject: RE: Out of Office & SCT
Same here … same issue in terms of what to do with existing mail databases that have their OOO disabled over night
Subject: RE: Out of Office & SCT
We also get the problem. Not using SCT but r5.05 mail files on 6.5.4 servers. The problem seems localised to certain servers which suggests server setting which I have not found yet. Other useless links without solns are:http://www-1.ibm.com/support/docview.wss?rs=899&context=SWD00&context=SWC00&context=SSKTK9&context=SSKTL5&context=SSKTM2&context=SSKTMJ&context=SSPQ69&context=SSPQ7E&context=SSPQ5C&context=SS5N9B&context=SS5NA4&context=SSKTPA&context=SS5LUA&context=SSMT72&context=SSMSB2&context=SSKTXQ&context=SSTJRD&context=SSKTWB&context=SSKTWP&context=SSKTYF&context=SSYSVG&context=SSTJRP&context=SSKTZF&context=SSZHFR&context=SSYJJC&context=SSFLMV&dc=DB510&dc=DB520&dc=D800&dc=D900&dc=DA900&dc=DA800&dc=DB530&dc=DA600&dc=DB550&dc=D100&dc=D600&dc=D700&dc=DA500&dc=D200&dc=DA410&dc=DA450&dc=DA430&dc=DA440&dc=DA420&dc=DA460&dc=DB300&dc=DA470&dc=DA480&dc=DB100&dc=DA4A10&dc=DA4A20&dc=DA700&dc=DA4A30&q1=SKAI64MFEP&uid=lsj1170eab09aa33d10b492570370007d38d&loc=en_US&cs=UTF-8&lang=all
and