While on the phone with trend, I figured it out. I went back to an
ancient issue I was having with virus pattern files not getting updated.
http://archive.midrange.com/domino400/200609/msg00042.html
And basically changed the pattern file stuff to scan engine stuff and did
this.
1. Delete the /qibm/userdata/trend/smd/program/$Version/au_cache folder
2. Delete the /qibm/userdata/trend/smd/program/$Version/au_log folder.
3. Delete the /qibm/userdata/trend/smd/program/$Version/au_temp folder
4. Delete the /qibm/userdata/trend/smd/engine/vsapi/V* folder
5. Delete the virus scan engine file in the smency.nsf database
6. Change the virus scan engine number in the smency.nsf to a lower engine
number
(i.e. 0.100.0)
7. Do a pattern update (load smdupd)
Their phone support is pretty clueless. "(Trend) Go to the all documents
view in the smconf. (Me) I'm there - I see lots of replication/save
conflicts. (Trend) Do you see any replication conflicts? (Me) My God
man, aren't you listening? I just said so. (Trend) Sorry. Delete them.
(Me) Ok, but it won't let me delete the one on the default policy
document. (Trend) Try this fixup command. (Me) ok. Didn't work.
Getting same error. Listen, a fixup, compact, updall or a blessing from a
high priest isn't going to fix this. You would have to modify your code
to allow the deletion of a default policy document. (Trend) Then how
would we delete it? (Me) You have your coder modify the logic that does
allow the deletion of a default policy document. (Trend) Let's try
deleting smconf and copying from a different server. (Me) Mind if I just
rename it? (Trend) Maybe you'd better rename it instead of deleting it.
(Me) Ok. Copy or replicate from other server? (Trend) Replicate. (me)
The other server has the same conflict. I'm renaming it back. (Trend)
Long enough pause that I started searching archives, etc and found my
pattern file solution, modified it for a scan engine, implemented it and
tested it. When they got back on the phone I sent them the above
resolution, thanked them, and told them to close the issue.
This may have happened because I copied over the domino data directory
from another lpar (server to server migration of a domino server) and that
got out of sync with the trend portion of /qibm/userdata....
Rob Berendt
midrange.com
