[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1032.0. "VCS crash, ACCVIO reason mask=01" by 23535::KENNETH () Wed Oct 11 1995 22:58

Hi,

I have a customer report that their VCS process crash and the details are
as below.  The VCS Version is V1.4 running on VAX VMS V5.2-H4.

I know that VCS is being retired, is it still support now?  
Does anyone face a similar crash before?  

The customer already install the CSCPAT_1055015.

Any ideas about the crash?  I don't know what is the reason that cause the
crash, according to the customer, there is no changes or even they do not 
touch the workstation.

Thanks for your help in advance.

Kenneth Leung


X error event received from server:  BadWindow (invalid Window parameter)
  Failed request major op code 2 (X_ChangeWindowAttributes)
  Failed request minor op code 0 (if applicable)
  ResourceID 0x700242 in failed request (if applicable)
  Serial number of failed request 97749
  Current serial number in output stream 97751
%VCS-I-X_ERR, Error event received from server: BadWindow (invalid Window
parameter)
-VCS-I-X_ERR_MINOR,   Failed request major op code 2 (X_ChangeWindowAttributes)
X error event received from server:  BadWindow (invalid Window parameter)
  Failed request major op code 2 (X_ChangeWindowAttributes)
  Failed request minor op code 0 (if applicable)
  ResourceID 0x700242 in failed request (if applicable)
  Serial number of failed request 97750
  Current serial number in output stream 97751
%VCS-I-X_ERR, Error event received from server: BadWindow (invalid Window
parameter)
-VCS-I-X_ERR_MINOR,   Failed request major op code 2 (X_ChangeWindowAttributes)
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=32314646,
PC=00413D09, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                00470E78
        Name   = 0000000C                00000000
                 00000001                203C0000
                 32314646                00000000
                 00413D09                20040000
                 03C00000                7FEE32E4
                                         7FEE32A8
                                         004140BB
                                         00425F40
                                         00000007

        Register dump

        R0 = 0000000C  R1 = 0049BA58  R2 = 3231463E  R3 = 7FEE32EE
        R4 = 00196304  R5 = 00000002  R6 = 00000000  R7 = 0019360C
        R8 = 004B4680  R9 = 00425798  R10= 0070024D  R11= 00008840
        AP = 7FEE2A28  FP = 7FEE29E8  SP = 7FEE2A64  PC = 00413D09
        PSL= 03C00000

T.RTitleUserPersonal
Name
DateLines
1032.129067::BUTTERWORTHGun Control is a steady hand.Thu Oct 12 1995 12:3213
    This was the C3 that failed then which means all the VCS processes
    didn't crash. This looks like the problem where a
    user closes the "Show Events" window using the "Close" option from 
    window manager menu instead of using the "Dismiss" button on the
    Show Events window. There are insturctions in the release notes for
    CSCPAT_1055 that outline how to remove the Close option for the
    window menu for the 'Show Events" window only. This will force the
    user to use the Dismiss button to get rid of the SHOW EVENTS window.
    This is a side effect of trying to keep the C3 compatible with Motif
    or DEcwindows V2.
    
    Regs,
       Dan