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

Conference noted::excursion

Title:note 3 has pointer to current kit
Notice:note 3 has pointer to current kit
Moderator:PEACHS::GHEFF
Created:Wed May 29 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3301
Total number of notes:14905

3299.0. "Excursion fails with Dr.Watson over DECnet on NT4..0" by DECPRG::VODICKA () Sun Jun 01 1997 05:05

    Hello team,
    
      Our customer has serious problem after installing PW32 7.0 and
    Excursion 3.0.554 on Intels WNT4.0 Workstation. He uses Netbeui and DECnet
    protocol and  connects host node OpenVMS v 6.1, DECnet/OSI v6.3 ECO5.
      When he tries to run Session Manager (DECW$SESSION), wxserver.exe
    fails with Dr.Watson error: 
    
       Exception: access violation (0xc0000005),Adress: 0x779f85ed
    
      The same error he gets, when he sets Enable Access Control and
    defines correct DECnet Node Name. Then he can't start wxserver.exe with same Dr.Watson
    error.
    
    Last in Excursion log after failure is:
    
    29.10.1997  10:08:49  Network   Warning   dnet_addr(praha) failed,
    error=997
    
    and same with error=1813
    
    (it looks similar as 3298.0)
    
      I have installed similar configuration on 2 PCs in our office with
    same result (DECPC486,40RAM,DE205 and Venturis FX166,40RAM,DE435).
     In WinNT Event Log appears two messages (in Aplication Log) after
    wxserver crash:
    
                        source      category      Event    Detail
    
    (fatal error)       Perflib     None          1008     The Open
    Procedure 
                                                           for service
    "Decndis"
                                                           in DLL
    "Perfctrs.dll"
                                                           failed.
    Performance
                                                           data for this
    service
                                                           will not be
    avaible.
                                                           Status code
    returned is
                                                           DWORD 0.
    followed by
    (information)       DrWatson    None          4097     The
    application,,
                                                           generated an
    apllication
                                                           error ...
                                  
     I 've found some similar problems in notes and made recommended
    workarounds -without
    success! (ncp>set link state off, removing PW32 then run pws2dnst.exe
    and
    new installation of PW32 - nothing helps!)
    
    Older Excursions in customer site works properly, so I think, that
    problem is not
    in X aplications. When I configure Excursions 3.0 with TCP/IP
    everything works ok.
    It looks anything is wrong in socket interface with DECnet.
    
    Here is list from customer's Excursion log:
    
    26.4.1997  12:28:43  X Server        Information  eXcursion V3.0.554
    (Intel) logging enabled.
    26.4.1997  12:28:45  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:28:45  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:28:45  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:29:02  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:29:02  Network         Warning     
    dnet_addr(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:29:02  Network         Warning     
    getnodebyname(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:29:02  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:29:02  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:29:02  Network         Warning     
    dnet_addr(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:29:02  Network         Warning     
    getnodebyname(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:29:02  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:29:02  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:29:04  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:29:05  Network         Warning      dnet_addr(PRC017)
    failed, error=997
    -----------------------------------------
    26.4.1997  12:33:20  X Server        Information  eXcursion V3.0.554
    (Intel) logging enabled.
    26.4.1997  12:33:37  X Application Startup   Information  OK
    26.4.1997  12:33:38  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:33:40  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:33:40  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:33:42  X Protocol      Error        Reply sent to Client
    #2, Request=QueryFont, Error=BadFont
    26.4.1997  12:34:38  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:34:38  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:34:49  X Protocol      Error        Reply sent to Client
    #4, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:34:49  Network         Warning     
    dnet_addr(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:34:49  Network         Warning     
    getnodebyname(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:34:49  X Protocol      Error        Reply sent to Client
    #4, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:34:49  X Protocol      Error        Reply sent to Client
    #4, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:34:49  Network         Warning     
    dnet_addr(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:34:49  Network         Warning     
    getnodebyname(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    26.4.1997  12:34:49  X Protocol      Error        Reply sent to Client
    #4, Request=ChangeHosts, Error=BadAlloc
    26.4.1997  12:34:49  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:34:51  Network         Warning      ioctlsocket(308)
    failed, error=EINVAL
    26.4.1997  12:34:51  Network         Warning      dnet_addr(PRC017)
    failed, error=997
    -----------------------------------------
    27.4.1997  10:13:17  X Server        Information  eXcursion V3.0.554
    (Intel) logging enabled.
    27.4.1997  10:13:19  Network         Warning      ioctlsocket(260)
    failed, error=EINVAL
    27.4.1997  10:13:19  Network         Warning      ioctlsocket(260)
    failed, error=EINVAL
    27.4.1997  10:13:19  Network         Warning      ioctlsocket(260)
    failed, error=EINVAL
    27.4.1997  10:13:20  Network         Warning      ioctlsocket(260)
    failed, error=EINVAL
    27.4.1997  10:13:34  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    27.4.1997  10:13:34  Network         Warning     
    dnet_addr(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    27.4.1997  10:13:34  Network         Warning     
    getnodebyname(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    27.4.1997  10:13:34  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    27.4.1997  10:13:34  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    27.4.1997  10:13:34  Network         Warning     
    dnet_addr(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    27.4.1997  10:13:34  Network         Warning     
    getnodebyname(IPB:.PRAHA-VS.STETKOVA_UL.PRC017) failed, error=0
    27.4.1997  10:13:34  X Protocol      Error        Reply sent to Client
    #2, Request=ChangeHosts, Error=BadAlloc
    27.4.1997  10:13:35  Network         Warning      ioctlsocket(260)
    failed, error=EINVAL
    27.4.1997  10:13:37  Network         Warning      ioctlsocket(260)
    failed, error=EINVAL
    27.4.1997  10:13:38  Network         Warning      dnet_addr(PRC017)
    failed, error=997
    
    
    This is part of my Excursion log:
    
    29.10.1997  9:44:44  X Server        Information  eXcursion V3.0.554
    (Intel) logging enabled.
    29.10.1997  9:44:53  X Application Startup   Information  OK
    29.10.1997  9:44:54  Network         Warning      ioctlsocket(292)
    failed, error=EINVAL
    29.10.1997  9:44:56  Network         Warning      ioctlsocket(292)
    failed, error=EINVAL
    29.10.1997  9:45:03  X Protocol      Error        Reply sent to Client
    #2, Request=QueryFont, Error=BadFont
    29.10.1997  9:45:54  X Application Startup   Information  OK
    29.10.1997  9:45:56  Network         Warning      ioctlsocket(292)
    failed, error=EINVAL
    29.10.1997  9:46:00  Network         Warning      ioctlsocket(292)
    failed, error=EINVAL
    29.10.1997  9:46:02  Network         Warning      ioctlsocket(292)
    failed, error=EINVAL
    29.10.1997  9:46:06  Network         Warning      ioctlsocket(292)
    failed, error=EINVAL
    29.10.1997  9:46:06  X Protocol      Error        Reply sent to Client
    #1, Request=ChangeHosts, Error=BadAlloc
    29.10.1997  9:46:06  Network         Warning      dnet_addr(PRAHA)
    failed, error=183
    29.10.1997  10:04:02  X Server        Information  eXcursion V3.0.554
    (Intel) logging enabled.
    29.10.1997  10:04:24  X Application Startup   Information  OK
    29.10.1997  10:08:10  Network         Warning      dnet_addr(praha)
    failed, error=0
    29.10.1997  10:08:47  X Server        Information  eXcursion V3.0.554
    (Intel) logging enabled.
    29.10.1997  10:08:49  Network         Warning      dnet_addr(praha)
    failed, error=997
    
    
      Customer also complains problem to setup Excursion 3.0 for use colors
    from user profile
    (defined in X session manager). He can only use default colors or
    definition
    from local PC file.
    
    Because this is biggest customer with major revenue for Digital there,
    it looks I must resolve these problems soon.
     
    Thank you for reply
    
    
    Michal Vodicka
    
              
T.RTitleUserPersonal
Name
DateLines
3299.1JAMIN::prnsy5.lkg.dec.com::osmanEric, dtn 226-7122Mon Jun 02 1997 10:547
If you are willing to test our latest beta code, it may help
get this resolved faster.  Please see note 3293.

Thanks.

/Eric
3299.2JAMIN::prnsy5.lkg.dec.com::osmanEric, dtn 226-7122Mon Jun 02 1997 11:108
Something else to try is to disable decitot and see if that
makes a difference.

To do that, find your decitot.sys file and rename it to 
decitot.nosys.  Then reboot.

/Eric
3299.3JAMIN::prnsy5.lkg.dec.com::osmanEric, dtn 226-7122Mon Jun 02 1997 11:3430
o.k. I just found one thing that might help you.

I normally run my excursion apps from decnet vms node jamin:: to
my pc.  I went into excursion control panel and chose "access"
and added this decnet entry in the "valid nodes" section:

	node: jamin
	user: fooey


Note that we don't actually have a user called "fooey" on node
jamin.

After saving this entry, I could not restart excursion anymore.
I will have to look into this problem more.

However, the workaround that allowed me to be able to start excursion
again was to run "regedit" and get into this page:

	HKEY_CURRENT_USER\Software\Digital Equipment Corporation\
		eXcursionV2.0\Configuration\Config0

Once there, I double-clicked on "ValidNodes" and cleared out that
field (it had "jamin::fooey" in it), after which I was again able
to run excursion.

Does this help you ?

/Eric
3299.4DECPRG::VODICKAMon Jun 02 1997 16:4950
    Hello Eric,
    
     Thank you for quick answer. I tried your advises with this result
    
    re2
     I haven't decitot.sys file in my test PC. I didn't install TCP/IP.
     But in registry I found confusing parametr ITOT_Installed=TRUE.
       
    (HKEY_LOCAL_MACHINE/Software/Digital.../PATHWORKS/Setup/CurrentConf..).
    
    Changing to FALSE (and reboot) has no effect.
    
    re3
    > However, the workaround that allowed me to be able to start excursion
    > again was to run "regedit" and get into this page:
    >
    >         HKEY_CURRENT_USER\Software\Digital Equipment Corporation\
    >                 eXcursionV2.0\Configuration\Config0
    >
    > Once there, I double-clicked on "ValidNodes" and cleared out that
    > field (it had "jamin::fooey" in it), after which I was again able
    > to run excursion.
    
      Clearing this value has the same effect, as clearing from Excursion
     control panel. But I want to have Control access  functioning.
     ( I used valid account, in registry was: DECNET praha vodicka).
    
     re1
       My collegue, who has excursion beta test installed, gets same errors
     when runs decw$session or sets control access. But we didn't try all
     possibilities. We will continue testing.
    
     
       User profile colors may solve my collegue advise to use commands
    
        $ xrdb :== $decw$utils:xrdb
        $ xrdb -nocpp DECW$SMB_WINDOW_COLOR.DAT;2
    
     before any X application starts. But Excursion 2 doesn't need this
     commands and colors are user defined.
    
    
      Last customer complain is bad X application order in Windows task bar
     ( he uses XWindow - built-in windows manager). But I found in notes,
     that it is principal problem not solved yet. Isn't it?
    
      Thank you again for your ideas, because mine are exhausted.
    
     Michal
    
3299.5JAMIN::prnsy5.lkg.dec.com::osmanEric, dtn 226-7122Tue Jun 03 1997 11:379
My experimentation shows that even *valid* access control
node-user combinations will prevent excursion from running.
We'll need to fix this later.

Does the access control offered in dxsession or DECW$SESSION
help you for now ?

/Eric
3299.6DECPRG::VODICKATue Jun 03 1997 17:288
    Eric
    
      I am afraid that customer will be not satisfied with this solution.
    Would escalation help?
    Is it Excursion or Pathworks problem?
    Have you noticed another two problems (colours and task bar)?
    
    Michal
3299.7JAMIN::prnsy5.lkg.dec.com::osmanEric, dtn 226-7122Wed Jun 04 1997 10:539
Yes, I think an escalation on the access-control problem is in order.

As for other problems, such as color and task bar, please put
in a separate note (one per problem).  Escalation may be
required for those if we can't give you a quick answer
on them.

/Eric
3299.8DECPRG::PRSS2::csfr::markusWed Jun 04 1997 12:486
Eric,
I am coleague of Michal who did some testing. Just one info. I have 
installed SP3 from Microsoft.

Jiri Markus
NSIS Prague
3299.9JAMIN::prnsy5.lkg.dec.com::osmanEric, dtn 226-7122Wed Jun 04 1997 14:383
Do you have evidence that excursion works before sp3 and not
after ?
3299.10no wayDECPRG::PRSS2::csfr::markusThu Jun 05 1997 09:197
re .-1
Eric,
maybe I didn't express myself corectly. The true staement should be 
Even with SP3 it doesn't work. Our customer is on the SP1, I tried SP2 and 
SP3.

Jiri