I had problems with the install of the December update this weekend.  
I downloaded it on Friday 5/15.  The install got to the "convert existing dictionary" portion (step 3 on installation instructions), and I got this error:
Addsum Tas Premier 7i
List Index out of bounds (3)
I clicked OK and had a blank screen, which I closed.
I got a warning that the update process had not been completed.  I tried again, and at some point got the error 115.  I checked an no other workstation was on but mine and I was logged off the server.  I restarted the server and tried again and got the List Index out of bounds message again.  I gave up and tried to restore the DBA folder copy, but I was not allowed to rename the real DBA folder so I could not restore the copy, because the "file was in use by another program"  
 
  This went on all weekend, after several server restarts and confirmation that No one was using the file.  This morning I decided to try stopping the Pervasive services and sure enough I was able to rename the DBA folder and restore my copy.  
 
I had trouble when I installed the payroll update, and apparently this full update is not going to be easy either.  I have to wait a while to try it again, but am wondering what all this means.

I have scheduled the update for next Friday (6-19) and could really use some help/answers to my dilemma:
 
What caused the failure of the December update?  
 
Should I just download and install the March update or should I try the December update again and then install the March update?

I was installing it on my workstation using remote desktop to the server.  I have administrator privileges on the server.  It is possible that my computer had not disconnected properly from Evo or Pervasive, since the first message I got indicated that Evo was open.  However, I logged off my workstation, restarted the server, and tried the install from the server, and still got the hang up during the dictionary conversion.  
 
I never had any problems on the old server (2000) and Pervasive 8.5 but with the 2008 Server and Pervasive 10 even just the Payroll update I did in January did not run smoothly-- if you remember Lynn I had to get your help. You had to send me new dictionary files.  I don't remember what else we did.
 
I don't know if this has anything to do with anything, but when I tried to change the name of the messed up DBA folder on the server, I got a message saying that the  file was being used and I could not make changes.  When I stopped Pervasive I was able to change the name and reinstate the copy.

I tried this update again today, at first from the server.  Actually I never got to the update because I was having the same problem as last time with the DBAMFG folder-- I could not re-name it.  So after re-reading this post I decided to try it from my work station and it worked!  
I am now updated.
I would still like to know what is going on with the server, and have this question about the program folder on the server:
 
How should this folder be set up as far as security goes?  Does it need to be shared, or can I just give server administrators and my "DBA Users" group permissions-- complete control for the administrator and read/write for the users or total control for users also( not really comfortable with that)?  
Should the folder be a read-only folder?  This was checked on the properties page for the folder and I unchecked it to see if this would help with my renaming efforts but it did not change anything.  I left it unchecked- should I change it back?