xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns="http://www.w3.org/TR/REC-html40">
href="When%20the%20WSL%20encryption%20is%20set%20to%20128_files/filelist.xml">
When the WSL encryption is set to 128, though the domain boots,
user is unable to login. It gives an error,
Network API error – unable to connect to appserver because of
possible causes...
Tuxedo log shows a warning:
***************: WSNAT_CAT:1229: WARN: A client failed
encryption negotiation
***************: WSNAT_CAT:1229: WARN: A client failed
encryption negotiation
Check BEA On-line documentation for the description of
WSNAT_CAT:1229- style='color:#3333FF'>http://edocs.beasys.com/tuxedo/tux65/ style='font-size:11.0pt'>
Starting with the Tuxedo 7.1 release, there is no 128 encryption
add on package. The way it now works is that both the client and server need
128 bit license. Hence the solution here is to copy the style='font-size:11.0pt;font-family:"Trebuchet MS";color:#990000'>lic.txtstyle='font-size:11.0pt;font-family:"Trebuchet MS";color:black'> from the
Tuxedo install, $TUXDIR/udataobj to %PS_HOME%\tuxedo\udataobjstyle='font-size:11.0pt;font-family:"Trebuchet MS";color:black'> on your file
server (the location where you are launching the executable to logon 3-tier).style='font-size:11.0pt;font-family:"Trebuchet MS";color:#000033'> style='font-size:11.0pt'>
No comments:
Post a Comment