Error updating view ($IDVaults), ($PoliciesExt) and ($PoliciesByGroup)

hcl-bot · February 23, 2009, 5:50am

We are getting the following errors repeatedly in the log following an upgrade of Domino from 7.0.3 FP1 to 8.5:

Error updating view ‘#357102’ in names.nsf: Document has been deleted

Error updating view ‘#354142’ in names.nsf: Document has been deleted

Error updating view ‘#354130’ in names.nsf: Document has been deleted

The three views affected are

($PoliciesExt)

($PoliciesByGroup)

($IDVaults)

I have tried deleting the views from the database, changing the setting to force removal of the deletion stubs, doing a load updall names.nsf -R and reapplying the template. The same views keep generating the errors a few hours later.

Does anyone have any ideas why these views keep causing me problems and what, if anything, I can do about it?

Regards,

John

hcl-bot · April 14, 2010, 8:51am

Subject: Solution Found - for us anyway.

I know this is Old, but a solution was not posted and we just had this issue.

For the views in question ($IDVaults) and ($PoliciesByGroup), if you try to save the views, we received a message saying the document has been deleted, we also could not preview in the notes client. We copied the views, deleted the original and then renamed the views we copied back to the original name. Sign the database database and the error has gone away.

hcl-bot · January 18, 2011, 10:27am

Subject: More detailed info on solution.

For the views in question ($IDVaults), ($PoliciesExt) and ($PoliciesByGroup), if you try to save the views, I received a message saying the document has been deleted. I also could not preview in the notes client as above.

I copied the views, deleted the original and then renamed the views I then renamed back to the original name.

Did a load fixup -l -f on the names.nsf and no errors now.

I then removed the prohibit design refresh and ran a load design. The views were then updated from the template seeting them back to being owned by Lotus.

Retested with a fixup and all still fine. Looks as if this has resolved the error.

Note: DELETING and running design task does NOT however fix it. This is because design puts the view back with the SAME note id every time. Copying and renaming and refreshing has a different note id!

Why this makes a difference - no bloody idea.

hcl-bot · February 23, 2009, 6:31am

Subject: Error updating view ($IDVaults), ($PoliciesExt) and ($PoliciesByGroup)

Did a fixup on the names.nsf. Now getting the following:

Database Fixup: Error fixing view 357102 in names.nsf: This database cannot be read due to an invalid on disk structure

Have tried a copy-style compact with no effect.

John

hcl-bot · April 15, 2009, 9:15pm

Subject: Error updating view ‘#7350’ in names.nsf: This database cannot be read due to an invalid on disk structure

I have a similar issue only on the servers I upgraded have upgraded from 6.5.5.

The servers I have built clean 8.5 are fine.

My issue is — Error updating view ‘#7350’ in names.nsf: This database cannot be read due to an invalid on disk structure.

And

Error updating view ‘#7310’ in names.nsf: Document has been deleted

I have been working with IBM support for two weeks and even they can’t figure this out.

They also tell me they none of their other customers have reported anything like this….

Any advice?

hcl-bot · February 23, 2009, 7:05am

Subject: Same problem here

neither fixup nor updall did help.At least I did the following:

I opened each server document in edit mode and resaved it.

The same procedure I did with server configuration documents and policies.

Knock on wood; since then the issue did not occur any longer.

hcl-bot · February 23, 2009, 11:43am

Subject: I’ll give it a try and let you know…

Thanks Ulrich.

hcl-bot · February 27, 2009, 4:24am

Subject: No luck…

Hi Ulrich,

No luck with opening, editing and saving the policy documents.

Any other suggestions welcome!

hcl-bot · August 6, 2009, 10:52am

Subject: Policies

We ended up creating new policies completely and reassigning our users to the new. That solved our problem, Cheryl

hcl-bot · March 29, 2009, 8:06pm

Subject: Similar Problem - Found a Solution

Had trouble updating an existing policy document; also could not see the document. I was able to resolve it, at least for now by:

Ensuring server INI file permits creating DB’s with ODS48 (R8): Create_R8_Databases=1
Do a copy-style compact on names.nsf. Had to run it from the command line with the server down.

All is working now.