Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

NWInitUnicodeTables failed and returned FE15 (-491)

0 views
Skip to first unread message

Alan Moss

unread,
Dec 4, 1997, 3:00:00 AM12/4/97
to

Hi,

We recently installed LDVP 5.0 on a NW 4.11 server and recieve the
following error:

NWInitUnicodeTables failed and returned FE15 (-491)

during login script proccessing on DOS machines. I've found that the
following line in the login script causes this error:

#PUSHPOP +I \\SERVER\SYS\LOGIN\LANDESK\VPROTECT\VPTEMP

Novell Support says:

Symptom
Executing the API NWInitUnicodeTables() fails with return value 0xFE15
(UNI_NO_SUCH_FILE). The unicode tables have been installed correctly in an
NLS subdirectory in SYS:PUBLIC and SYS:LOGIN.

Cause
NWInitUnicodeTables() fails to find the unicode tables since they are not
located in one of the five areas specified in the developers' manual
1. The current working directory.
2. The directory the application was loaded from.
3. A directory named \NLS immediately subordinate to the directory the
application was loaded from.
4. A directory name \NLS descended from the directory the application was
loaded from.
5. A directory in the local search path.

Solution
InitUnicodeTables() does search the current working directory. Hence to
find the unicode tables an application can modify the current working
directory searching for an NLS subdirectory off its search path.

Is there a patch to fix this problem or is it my directory structure?

Thanks,
Alan Moss
am...@miami.edu

Terry K

unread,
Dec 8, 1997, 3:00:00 AM12/8/97
to am...@miami.edu

In a message received by Intel on 12/4/97 1:49:00 PM, Alan Moss wrote:

:> Hi,

Alan,

The best thing to do is either map a permenant drive for the product
and remove pushpop or map early in the scrip a drive to public/nls. By
the way this error is not common for this product.

Terry K
ICS-ASC
Intel Internet Support


0 new messages