|
Sunil,
It means that whomever sent the request to the server is running
a different version of DASL than the FCS is. Things, in most cases,
will work just fine. It is just a warning that the other guy
from teh connection MAY send something across that this server
can't handle, in which case it will simply be dropped.
The big question is, how did this happen? DMW never talks directly
to the FCS, only TeamLinks and IOS, TeamLinks is using the same
dasl version number as the FCS and so is IOS, this code to trap this
was put in for detection in a distributed environment, ie connections
to remote servers or server-server connections.
Can you give more information about the setup. You say they are
sending dmw mail to IOS. Are they using TL? If so what version? If
TL is not involved, I can't see how this pulled in the FCS since the
mail would go via normal VMS mail channels which do not involve the
FCS.
If this doesn't give better info, you will have to turn on FCS tracing
and do the operation again, so that you can see where the FCS on
CNB06V thinks the connect is coming from.
--Bob
|
| Hi Bob,
>-< confused >-
I must say that I was well and truely confused myself, I won't go into
that right now. So to get rid of the confusion I talked to the real
systems mangler.
I don't think that the upgrade of DMW's has much to do with the error
message in the OAFC$SERVER.LOG. The customer has TeamLinks 2.0 EFT
version on site and my guess is that they were trying to access
ALL-IN-1 IOS with not MUPA or TLC installed. The customer is looking
into this as the TL version 2.0 clients are users are ment to only
access ALL-IN-1 IOS on their test system. Would this explain the error
message ?
I have been trying to test this on our system and thanks to DECinspect
someone has mangled our ALL-IN-1 IOS 3.0-1 system. So I would be
grateful if you can confirm that this is the case.
Regards,
Sunil
|
| Hi All,
We have managed to solve the DECinspect problems and have tried to
access ALL-IN-1 3.0-1. We had a few networking type of error messages
displayed on the TL client 2.0.
In the OAFC$SERVER.LOG we had the base note error messages logged.
These messages are logged everytime we try to do E-mail type of
functions.
Regards,
Sunil
|