[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DECtp Desktop for ACMS |
|
| Moderator: | UCROW::GIBSON |
|
| Created: | Mon Sep 24 1990 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 859 |
| Total number of notes: | 3034 |
841.0. "NET_CLIDIS: DECNET(13) error on WIN95" by DEKVC::CHANGHOANN () Tue Apr 08 1997 22:53
Hello,
One of our customer, SAMSAM , has a network error using desktop acms.
Server environment:
OpenVMS/AXP V6.1, DECnet phase IV, Pathwork for VMS V5.0-E,
ACMS V4.0-2, Desktop ACMS V2.2
Client environment:
Windows 95, Pathwork V1.0A for Windows 95,
16 bit applications with Visual Basic V3,
APIs and DECNET DLL from MSDOS.EXE
The following message is from acmslog on desktop.
After VB applications sign-in eight times, we can not sign in any more.
We must re-start desktop PC.
Any idea and recommendation ?
Thanks in advance for any reply.
Chang-ho Ann
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:07:33 1997
ACMSDI_CALL_TASK: starting at Fri Apr 04 14:07:33 1997
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:07:35 1997
NET__CLIDIS: DECNET(13), DECnet error
CONNECTION_DELETE: RPC(22), Fatal internal error
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:07:35 1997
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:07:55 1997
ACMSDI_CALL_TASK: starting at Fri Apr 04 14:07:55 1997
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:07:55 1997
NET__CLIDIS: DECNET(13), DECnet error
CONNECTION_DELETE: RPC(22), Fatal internal error
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:08:23 1997
ACMSDI_CALL_TASK: starting at Fri Apr 04 14:08:23 1997
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:08:23 1997
NET__CLIDIS: DECNET(13), DECnet error
CONNECTION_DELETE: RPC(22), Fatal internal error
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:08:25 1997
ACMSDI_CALL_TASK: starting at Fri Apr 04 14:08:25 1997
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:08:25 1997
NET__CLIDIS: DECNET(13), DECnet error
CONNECTION_DELETE: RPC(22), Fatal internal error
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:08:26 1997
ACMSDI_CALL_TASK: starting at Fri Apr 04 14:08:26 1997
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:08:26 1997
NET__CLIDIS: DECNET(13), DECnet error
CONNECTION_DELETE: RPC(22), Fatal internal error
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:08:27 1997
ACMSDI_CALL_TASK: starting at Fri Apr 04 14:08:27 1997
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:08:27 1997
NET__CLIDIS: DECNET(13), DECnet error
CONNECTION_DELETE: RPC(22), Fatal internal error
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:08:28 1997
ACMSDI_CALL_TASK: starting at Fri Apr 04 14:08:28 1997
ACMSDI_SIGN_OUT: starting at Fri Apr 04 14:08:28 1997
NET__CLIDIS: DECNET(13), DECnet error
CONNECTION_DELETE: RPC(22), Fatal internal error
ACMSDI_SIGN_IN: starting at Fri Apr 04 14:08:29 1997
NET__CLICON: DECNET(55), DECnet error
RPC_BIND: RPC(54), RPC connection failed
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 841.1 | | UCROW::GIBSON | | Wed Apr 09 1997 08:52 | 31 |
| Chang-ho Ann,
The problem appears more related to signOut rather than signIn.
The DECnet error (13) on the signOut appears to be EACCESS -
"Permission denied", like some kind of privilege is being violated.
The first entry in the log shows signIn/taskCall/signOut(fail)/signOut(OK),
then it falls into a pattern where the signOut always fails. At the end
of the log there is a signIn failure with error (55) ENOBUFS. This is
probably just a resource depletion problem related to the repeated signOut
failures.
Is this a consistent pattern, and what is the possiblility of coding
errors? That is, has this application worked in the past on 16 bit
Windows, do other applications work in this environment?
Are there multiple overlapping signIn submitter sessions in effect, or
only one signIn at a time. Is there only one VB .EXE involved?
Can they explain in their application code how, after that first attempt at
signOut fails, they can then apparently issue another signOut that
succeeds?
I am not sure how much that combination has been tried - a 16 bit
application running over DECnet on Windows 95. If answers to the above
does not provide any clues we can try the combination here with the
basic VB Avertz sample and see if that works.
/Tom
|
| 841.2 | | DEKVC::CHANGHOANN | | Mon Apr 14 1997 00:05 | 26 |
| Hello Tom,
I can reproduce this problem in our office.
My sample program is only sign-in and sign-out routine.
The count of sign-in and sign-out arrive at DECnet maximum link, then we
can not sign in.
Note) When the transport is TCP/IP, there are no problems. I think this is
related to only DECnet.
> Is this a consistent pattern, and what is the possiblility of coding
> errors? That is, has this application worked in the past on 16 bit
> Windows, do other applications work in this environment?
The customer application has worked fine under MS Windows.
> Are there multiple overlapping signIn submitter sessions in effect, or
> only one signIn at a time. Is there only one VB .EXE involved?
The customer application has one signin at a time. The number of VB .EXE
involved is 1 to 5.
Thanks in advance your reply.
Chang-ho Ann/
|
| 841.3 | any more details... | UCROW::KNEELAND | | Wed Apr 16 1997 12:42 | 23 |
| Chang-ho Ann,
Did you find any more information to answer signout question from .1
>Can they explain in their application code how, after that first attempt at
>signOut fails, they can then apparently issue another signOut that
>succeeds?
What is the DECnet maximum link you refer to in .2?
> I can reproduce this problem in our office.
> My sample program is only sign-in and sign-out routine.
> The count of sign-in and sign-out arrive at DECnet maximum link, then we
> can not sign in.
Since this notes conference is not an official support channel you may
want to consider openning an IPMT case to resolve this problem in a more
efficient manner. Please include any code that reproduces problem.
Thanks,
Colette
|
| 841.4 | See note 852.3 | EYEORE::BAIRD | | Thu May 08 1997 18:28 | 2 |
| This problem was also reported in Note 852. See 852.3 for potential
solution.
|