Anonymous_User Absent Member.
Absent Member.
1974 views

nwlscrpt.exe

Netware client sp3. Illegal operation pointing to nwlscrpt.exe on several
machines. Windows xp fully patched. Netware 5.0 server. Anybody has any
clues I would appeciate it.

Randy Hermundson
Network + Computer Specialist
Whitehall and Independence Schools


Labels (1)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: nwlscrpt.exe

you might try 491psp3_nwgina_2

> Netware client sp3. Illegal operation pointing to nwlscrpt.exe on several
> machines. Windows xp fully patched. Netware 5.0 server. Anybody has any
> clues I would appeciate it.
>



0 Likes
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: nwlscrpt.exe

"Randy Hermundson" <randy@whitehallsd.k12.wi.us> wrote:

> Netware client sp3. Illegal operation pointing to nwlscrpt.exe on several
> machines. Windows xp fully patched. Netware 5.0 server. Anybody has any
> clues I would appeciate it.


No issue that comes to mind specifically for 4.91 SP3 on Windows XP.

There was a report not too long ago in these newsgroups from someone
who found that NTFS permissions set on some files in SYSTEM32
apparently had started such a symptom:

> From: shaun_dark_lord <shaun_dark_lord.294ppb@no-mx.com>
> Newsgroups: novell.support.netware.client.winnt-2x-xp,novell.support.open-enterprise-server.client.windows
> Subject: nwlscrpt.exe - Application Error
> Message-ID: <shaun_dark_lord.294ppb@no-mx.com>
> Date: Fri, 09 Jun 2006 09:50:07 GMT
> http://groups.google.com/group/novell.support.netware.client.winnt-2x-xp/browse_frm/thread/8212bfe70b07cabc/


One thing that does bring to mind, but should not apply to Windows XP
SP2, is TID 10096109 where NWLSCRPT.EXE was crashing due to a bug in
NTDLL.DLL:

10096109: WINLOGON.EXE or NWLSCRPT.EXE crashing in Windows Heap32Next
call when LDAP Contextless Login enabled.
http://support.novell.com/docs/Tids/Solutions/10096109.html

Whether its "possible" for either of those two issues to be the cause
could be supported or refuted by the numbers being reported on the
DRWTSN32.EXE / application exception dialog. (e.g. "Instruction at
xxxxxxxx tried to read/write memory at xxxxxxx".)

Also, if you can confirm that the DRWTSN32.LOG is being appended to,
jumping to the bottom of that .LOG and then searching backwards for
"application exception" and then cut-n-paste from that point down to
the end of the file.

(Run DRWTSN32.EXE without any parameters to see where its currently
configured to write the log. The newest entries are appended to the
end of that log.)

Alan Adams
alancrumbadams@drcrumb.com
(for email, remove the crumbs)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.