Problems after using nconvert to update R5 mail files with the R6 template

After using nconvert to update our R5 mail files with the R6 template, we have numerous problems:

(1) For starters, all mail messages in the Inbox disappeared. We found them in the All Documents folder, and are in the process of copying them back.

(2) After opening a Calendar and clicking the ‘View and Create Group Calendars’ button, the Group Calendar folder (blue R6 design) opens up. It is also blank (existing Group Calendars disappeared). When we click the ‘New Group Calendar’ button, then fill in the Group Calendar dialog, we receive the error message ‘Notes Error: A folder or view with this name already exists: ((GroupCalendarFolder))’. GroupCalendarFolder is the Alias for the currently open Group Calendar folder (I’m not surprised that it already exists!).

By holding CTRL-SHIFT when entering the mail file, we can access some hidden views, including one called ‘MiniView - Group Calendars’. This does contain the Group Calendars which existed prior to the upgrade. Opening the Group Calendar, displays the Calendar summary screen, but double-clicking on a specific person’s Calendar (other than that of the currently open mail file’s owner) results in many error messages. Group Calendaring doesn’t seem to work properly at all.

(3) The ‘Upgrade Folder Design’ action (used to upgrade R5 folders not upgraded during nconvert to the R6 format) does not work. The error message is ‘Object variable not set’.

I’ve tried rebuilding views (Shift-F9, CTRL-SHIFT-F9). I’ve tried refreshing the mail file design. I’ve tried running updall, fixup and compact on some of the mail files, but these have no effect. I’ve also tried reinstalling Notes and upgrading to Notes 6.0.1. Our server is currently 6.0.

If anyone can advise on a course of action, I’d appreciate it.

Paul.

Subject: Problems after using nconvert to update R5 mail files with the R6 template

I have successfully upgraded all our users to the iNotes 6.01 template on an iSeries and the only problem I have had is a few users had some folders deleted and a couple of are having archiving problems. Upgrading folder design works, group calendars work, everything else is fine. Our clients are Windows 2000 SP3 with Notes 6.01 CF1.

You may want to try upgrading the server to 6.01, and apply CF1 if you’re using Windows 2000.

Subject: RE: Problems after using nconvert to update R5 mail files with the R6 template

Thanks Charles.

The problem does appear to be with the mail files. Everything was working perfectly prior to Friday, and these are the only databases that have been modified.

I will try upgrading the server though.

Paul.

Subject: RE: Problems after using nconvert to update R5 mail files with the R6 template

I just created a new R5 mail file with a Group Calendar and some folders.

After upgrading to the R6 template with nconvert, the R5 folders still won’t upgrade (‘Object variable not set’) but this time the Group Calendar seems to have converted o.k. and is working.

I’m going to try recreating one of the problematic mail files. If I can get rid of the Calendar problems I’ll be happy (the R5 folder problem isn’t such a big deal - it seems to be a template bug that might be fixed in a later release?).

Paul.

Subject: RE: Problems after using nconvert to update R5 mail files with the R6 template

Double check the command you are using to run nconvert. For example, the -u switch tells it to upgrade folder designs when it is replacing the template. If you haven’t tried using this switch, that might be something to think about.

Subject: RE: Problems after using nconvert to update R5 mail files with the R6 template

Hi Kevin, thanks.

I’ve tried using the nconvert -u switch to convert the folders from R5 to R6 format, but this has no effect. Since I can’t upgrade the folders with the ‘Upgrade Folder Design’ button either, it looks like I’m stuffed.

I think the other error message I’m receiving (‘Not a sub or function name: UICOPYINTONEWDOCUMENT’) when using Group Calendars may be related to the folder design - someone else has asked about a similar problem to mine. There is no fix for me though - ‘Upgrade Folder Design’ worked for them.

Could the Use “(ScriptWhereSubIsDefined)” statement be of use to me (see the threads about UICOPYINTONEWDOCUMENT)? If so, where should I place it in the mail file in order to fix Group Calendars?

Paul.

Subject: RE: Problems after using nconvert to update R5 mail files with the R6 template

The error message ‘Notes Error: A folder or view with this name already exists: ((GroupCalendarFolder))’ seems to be gone now.

I’m sure it vanished when I edited the folder aliases of the (Group Calendars) folder so that there are spaces between them:

Group Calendars|(GroupCalendarFolder)

Group Calendars | (GroupCalendarFolder)

The other error messages that come up when we try to open another person’s calendar seem to be related to permissions granted in the ACL of a database?

I can open anyone else’s calendar from my workstation (I have Manager access to all databases) but people who have less priviledges (such as read/write public, which is enough to access other people’s calendars with the R5 template) cannot, and receive the following errors:

‘Not a sub or function name: UICOPYINTONEWDOCUMENT’

‘You are not authorised to perform that operation.’

I’m still getting the ‘Object variable not set’ error when I try to upgrade R5 folders.

Any more ideas?

Paul.

Subject: Problems after using nconvert to update R5 mail files with the R6 template

Hi Paul,

the problem of the blank inbox happened to me more than once. I opened an incident with Lotus Support whitch after a month provided me a script to “recover” lost inbox,send and rules documents.

Call them and try it out…

Simone

Subject: RE: Problems after using nconvert to update R5 mail files with the R6 template

Simone,

Thankyou. I’ll see if I can find that.

Paul.

Subject: MORE INFO: Problems after using nconvert to update R5 mail files with the R6 template

I just found out how to use the LotusScript debugger.

The ‘Object variable not set’ error message occurs when LotusScript tries to refresh the ‘$FolderAllInfo’ view (view.refresh).

This view exists in the database, and refreshes fine when you open it manually and press F9.

The Notesview object appears to be set properly as well, as are the other script objects (db etc…).

Any thoughts?

Paul.

The script is as follows if it helps:

'//Local Variables Declaration

Dim session As notessession	

Dim db As notesdatabase

Dim view As Notesview

Dim note As notesdocument

Dim Initialdlg As NotesDocument

Dim Profile As Notesdocument

Dim version As Variant



Set session = New notessession

Set db = session.currentdatabase

version = session.notesbuildversion  		'//This should work only in R6 or higher versions

If version <= 166 Then

	Exit Sub

End If

BuildCollection:

Set note = db.createdocument

Set Initialdlg = db.createdocument	

Set Profile = db.getprofiledocument("CalendarProfile")

Set view = db.GetView("($FolderAllInfo)")

view.refresh ****ERROR OCCURS HERE****

Subject: RE: MORE INFO: Problems after using nconvert to update R5 mail files with the R6 template

I tried to run the updall routine on the ($FolderAllInfo) view. It wouldn’t work, so I created an alias for the view, and ran the updall ( ‘load updall -R (mail filename) -T (view alias name)’ ) on that. Now the ‘Upgrade Folder Design’ agent works.

It looks like the nconvert routine corrupted the view or the view name/alias.

The only problem remaining is that with Group Calendars (the error messages ‘Not a sub or function: UICOPYINTONEWDOCUMENT’ & ‘You are not authorised to perform that operation’).

Paul.

Subject: RE: MORE INFO: Problems after using nconvert to update R5 mail files with the R6 template

I know this is a rather late response, but my last problem (the error messages ‘Not a sub or function: UICOPYINTONEWDOCUMENT’ & ‘You are not authorised to perform that operation’) was fixed by resaving the script libraries in all the mail databases in which calendars were being shared AND resaving the $Calendar view.

The problem seemed to be caused by corruption of the view and/or view names/aliases.

Paul.