vmsinstal

[Klaes-Göran Carlsson]

Hi

I got "SYSTEM-F-ACCVIO" when trying to upgrading the system. Saveset seems to be OK, a backup/list bar065.a/sav looks ok. Its possible to install it on another node.
Have tried with different accounts, have tried...everything? Anyone who could give me a hint? Thanks in advance.

/Klaes-Goran

$ @sys$update:vmsinstal BAR065


OpenVMS AXP Software Product Installation Procedure V7.3-2


It is 19-FEB-2006 at 10:38.

Enter a question mark (?) at any time for help.

%VMSINSTAL-W-ACTIVE, The following processes are still active:
SERVER_0325
TCPIP$PORTM_1
TCPIP$FTP_1
DECevent_GAER19
MDMS$SERVER
ABS$COORD_CLEAN
ERALACK
ERAPOON
BATCH_2974
* Do you want to continue anyway [NO]? y
* Are you satisfied with the backup of your system disk [YES]?
* Where will the distribution volumes be mounted: SYS$SYSROOT:[SYSMGR]

* Enter installation options you wish to use (none):

The following products will be processed:

BAR V6.5


Beginning installation of BAR V6.5 at 10:38

%VMSINSTAL-I-RESTORE, Restoring product save set A ...
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=0000000000000000, PS=00000000
%VMSINSTAL-E-NOSAVESET, Save set A cannot be restored.

[Volker Halle]

Klaes-Goran,

try to enable SET VERIFY to find out, exactly which command is failing:

$ @sys$update:vmsinstal BAR065 SYS$MANAGER: OPTIONS D

Volker.

[John Gillings]

I'd start even further back than Volker:

$ BACKUP/LIST BAR065.A/SAVE

See if the saveset is OK. Same for .B, .C etc... If the saveset is bad, try repairing it (FIXSAVESET.COM attached).

[John Gillings]

sorry, attachment didn't work... try again

RENAME it to .COM and execute it against your savesets.

[Klaes-Göran Carlsson]

Hi

Thanks for your answers! Since it's a 24*7 production environment I can't do anything more during the week, maybee next weekend. I have backup/list * on all savesets, they seems to be OK
Also, some HP guys in India are involved in this case, so.... lets wait and see.

/Klaes-Goran

[Klaes-Göran Carlsson]

Got a mail from HP explaing the solution.

"The problem was with a corrupt backupshr.exe file."

Adding it in case someone else get the same problem. Problem solved!

[Klaes-Göran Carlsson]

The problem was with a corrupt backupshr.exe file.