Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Captain
Captain
6317 views

Novell Client 2 SP3 for Windows (IR5) now available

The Novell Client 2 SP3 for Windows (IR5) is now available for download, at this link:

https://download.novell.com/Download?buildid=gCT45TxxTHQ~

New fixes included in the Novell Client 2 SP3 for Windows (IR5):
1. Applications report "path not found" when creating new directories after installing Novell Client 2 SP3 (IR4). See TID 7014269. (Bug 853122)
2. Possible exception or memory corruption when TCP connection attempt for NCP timed out. (Bug 849409)
3. "Save profile after successful login" not working in conjunction with "Login with non-Novell Credential Provider". See TID 7014285. (Bug 844978)
4. Potential denial of service attack when requesting intentionally unsupported IOCTL. See TID 7014276 and CVE-2013-3705. (Bug 844766)
5. Volume serial number on Novell mapped drives is 0 or not displayed after installing Novell Client 2 SP3. See TID 7013397. (Bug 843704)
6. Address potential NCNetProvider hang which prevented Citrix session logoff from completing. See TID 7014271. (Bug 841102)
7. Address DORIS32.EXE application expectations by creating application-specific override of file and directory info cache timeout. See TID 7014264. (Bug 839519)
8. Address potential NCNetProvider hang which prevented Microsoft Excel from showing network-based data sources. See TID 7013373. (Bug 834312)
9. Windows Explorer high CPU utilization due to RPC failure on XTSVCMGR.EXEservice. See TID 7014274. (Bug 801765)
10. Unexpected ZENworks logon prompting when performing Switch User or Remote Desktop to existing user session. (Bug 801159)
11. Mapped drive may not disappear from non-elevated Windows Explorer when drive is unmapped from elevated session. (Bug 785858)
12. Preserve existing Novell-specific file and directory attributes that do not translate into Windows platform attributes. (Bug 747049)
13. eDirectory user's "Network Address" attribute potentially not updated in a timely manner after workstation resume or reconnect. See TID 7013371. (Bug 737552)
14. Updated bundled Novell SPMNWCC library to 8.8.8.1.
15. Updated bundled Novell NMAS Client to 8.8.8.10.
16. Updated bundled Novell NICI to 2.77.2.
Labels (1)
0 Likes
19 Replies
Absent Member.
Absent Member.

Earle,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

For Windows8 (x64), this client version seems to be fine.
For Windows7 (x64), my users have to be more patient during the login. It takes now up to one minute for all mappings. With Client 2 SP3 (IR4), the loginscript were executed in less than 5 seconds ...
0 Likes
Absent Member.
Absent Member.

* bytesnake wrote, On 01/03/2014 01:16 PM:
> For Windows7 (x64), my users have to be more patient during the login.
> It takes now up to one minute for all mappings. With Client 2 SP3 (IR4),
> the loginscript were executed in less than 5 seconds ...


Not here, IR5 is at least as fast as IR4. Take a LAN trace and see if something is going wrong.

Uwe

--
Novell Knowledge Associate
Please don't send me support related e-mail unless I ask you to do so.
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Well Lucky You,

IR5 Does not allow me to logon. Every time I get to a Logon Screen I attempt to put in a Username & Password. They are accepted, I get a Novell Logon Succeeded, then a short popup from ZCM 11.2.2.12991 "processing Logon" and then a flash of the screen and right back to the main logon screen.

Started with NCSP3IR3 & ZCM 11.2.2.12991 - Has been working with no issues

I have attempted removing NCSP3IR5 and Applying IR3 - No problems
I have attempted removing NCSP3IR5 and Applying IR4 - No problems
Started with IR3, Applied IR5 - Major Problem
Started with IR3, Applied IR4 - No Problems. Rebooted, Applied IR5 - Major Problem, back to the issue described above....

Not sure if this may be related to the NICCI/NMAS Updates and the ZCM Agent Version more than the Client itself, however I did not see any "Requirements" for ZCM and the IR5 Release....

14. Updated bundled Novell SPMNWCC library to 8.8.8.1.
15. Updated bundled Novell NMAS Client to 8.8.8.10.
16. Updated bundled Novell NICI to 2.77.2

I do know of a shop running an older version of ZCM 11.2.0.16 or close to that...they did not see the issue.

Not sure what the issue is yet, however we do have a ZCM upgrade for 11.2.4 planned either this weekend or next.... So for now I will stick with the SP3IR3 Client
0 Likes
Absent Member.
Absent Member.

MCCFL MLA <MCCFL_MLA@no-mx.forums.novell.com> wrote:

> ...then a short popup from ZCM 11.2.2.12991 "processing Logon" and
> then a flash of the screen and right back to the main logon screen.


That symptom is suggestive of "the Windows LOGONUI.EXE process
crashed", which can still be due to ZENworks and/or Novell Client,
both of which run code in the LOGONUI.EXE process space.

Perhaps confirm that you're seeing "*loginui.exe*"-named directories
being created under the Windows Error Reporting (WER) directories in
"C:\ProgramData\Microsoft\Windows\WER\" (ReportArchive or
ReportQueue), which would confirm that WER is catching the LOGONUI.EXE
process crashing. If you're not getting new directories named like
that, next I would check the Windows "Application" event log for
anything reported regarding the LogonUI.exe process terminating
unexpectedly.

But ideally that would means opening a support call and submitting the
dumps for analysis and working with the support engineer to collect
whatever additional information was needed. I'm not aware of
"LogonUI.exe crashes" already being any known or in-progress
investigation for the Novell Client 2 SP3 (IR5) release.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
www.novell.com

Upgrade to OES Community
http://www.novell.com/communities/coolsolutions/upgradetooes/
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

Yes,

I am seeing C:\ProgramData\Microsoft\Windows\WER\ReportQueue\ ***AppCrash_LogonUI.exe_****** folders.....

Along with the following in the event log:

########################################################

Event ID: 1000 - Application Error

Faulting application name: LogonUI.exe, version: 6.1.7601.17514, time stamp: 0x4ce79f70
Faulting module name: nccredprovider.dll, version: 1.0.73.2500, time stamp: 0x52b16fc4
Exception code: 0xc0000005
Fault offset: 0x0000000000005b2b
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

#######################################################################
Event ID: 1001 - Application Error

Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: LogonUI.exe
P2: 6.1.7601.17514
P3: 4ce79f70
P4: nccredprovider.dll
P5: 1.0.73.2500
P6: 52b16fc4
P7: c0000005
P8: 0000000000005b2b
P9:
P10:

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_LogonUI.exe_54fff1cd515e403ccadd70ca9b7687addb571ed_118fb376

Analysis symbol:
Rechecking for solution: 0
Report Id: 5d77ed9a-7cb8-11e3-b9ba-001b21b2b6cd
Report Status: 4

############################################################
0 Likes
Absent Member.
Absent Member.

MCCFL MLA <MCCFL_MLA@no-mx.forums.novell.com> wrote:

> Fault offset: 0x0000000000005b2b


Agreed, definitely a crash of the LogonUI.exe process. And it was
either NCCredProvider.dll code that was running at the time and/or was
the last non-Microsoft code that was running prior to the crash.

Unfortunately "Fault offset: 0x0000000000005b2b" looks like it must
have been memory corruption or a NULL pointer dereference, and isn't a
code offset in NCCredProvider.dll that might provide an additional
clue. So it will take looking at the dumps, and maybe even changing
the WER "DumpType" to 0x2 and duplicating again so that WER will write
a full process dump of LogonUI.exe instead of just a mini-dump.

So if you have the ability to open an SR with Novell Support on this
issue, that would be the best way to go to work with a support
engineer on investigating and resolving this. If you aren't going to
be able to open an SR but wanted to upload the dump for analysis
anyway, I'd be happy to make sure the dump gets looked at. There just
wouldn't be any open case or guaranteed communication back on any
findings or expected resolution, though we would still make a best
effort to provide that.

If you do want to upload the current dumps, .ZIP together all of the
"C:\ProgramData\Microsoft\Windows\WER\ReportQueue\***AppCrash_LogonUI.exe_******
folders" you are seeing (i.e. put them all into a single "Compressed
Folder" file like "AppCrashLogonUINovellClient2SP3IR5.zip" or some
other sufficiently unique file name) and upload the single .ZIP file
to ftp://ftp.novell.com/incoming/. (Note you can upload a .ZIP file
there, but intentionally cannot see/browse any files there, so you
will not see your file even once successfully uploaded.) Confirm what
file name you uploaded once it's done, and we'll get it looked at.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
www.novell.com

Upgrade to OES Community
http://www.novell.com/communities/coolsolutions/upgradetooes/
0 Likes
Cadet 3rd Class
Cadet 3rd Class

After the update to IR5 (from Novell Client 2 SP2 IR5), only 3/4 drives map successfully upon logon to a Windows 7 x64 workstation. One drive fails with the following logon script results:

"LOGIN-LGNWNT32-100: Access has been denied.
You are attached to server SHS_XXXX.
LOGIN-LGNWNT32-430: The following drive mapping operation could not be completed.

The error code was c7e50014."

Help?
0 Likes
Micro Focus Expert
Micro Focus Expert

Hi,

Care to share a snippet of your login script with us? Just the part that is failing. Also, what OS, version & SP is the server running?

Looking forward to hearing back from you.

Cheers,
Laura Buckley

Views/comments expressed here are entirely my own.
If you find this post helpful, please show your appreciation and click on "Like" below...
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

FYI:



I did the ZCM 11.2.4 upgrade over the weekend in help to eliminate Zenworks from being the problem. The problem above still exists after the update ZCM client material.

I am also able to replicate among multiple machines, we only run Windows 7 x64, SP1. I have not had a successful deployment yet....

I have not yet opened a support request.
0 Likes
Cadet 2nd Class Cadet 2nd Class
Cadet 2nd Class

I did upload the file as well.....even though I have not opened a support request...


Alan Adams;2301333 wrote:
MCCFL MLA <MCCFL_MLA@no-mx.forums.novell.com> wrote:

> Fault offset: 0x0000000000005b2b


Agreed, definitely a crash of the LogonUI.exe process. And it was
either NCCredProvider.dll code that was running at the time and/or was
the last non-Microsoft code that was running prior to the crash.

Unfortunately "Fault offset: 0x0000000000005b2b" looks like it must
have been memory corruption or a NULL pointer dereference, and isn't a
code offset in NCCredProvider.dll that might provide an additional
clue. So it will take looking at the dumps, and maybe even changing
the WER "DumpType" to 0x2 and duplicating again so that WER will write
a full process dump of LogonUI.exe instead of just a mini-dump.

So if you have the ability to open an SR with Novell Support on this
issue, that would be the best way to go to work with a support
engineer on investigating and resolving this. If you aren't going to
be able to open an SR but wanted to upload the dump for analysis
anyway, I'd be happy to make sure the dump gets looked at. There just
wouldn't be any open case or guaranteed communication back on any
findings or expected resolution, though we would still make a best
effort to provide that.

If you do want to upload the current dumps, .ZIP together all of the
"C:\ProgramData\Microsoft\Windows\WER\ReportQueue\***AppCrash_LogonUI.exe_******
folders" you are seeing (i.e. put them all into a single "Compressed
Folder" file like "AppCrashLogonUINovellClient2SP3IR5.zip" or some
other sufficiently unique file name) and upload the single .ZIP file
to ftp://ftp.novell.com/incoming/. (Note you can upload a .ZIP file
there, but intentionally cannot see/browse any files there, so you
will not see your file even once successfully uploaded.) Confirm what
file name you uploaded once it's done, and we'll get it looked at.

Alan Adams
Novell Client CPR Group
alan.adams@novell.com

Novell
Making IT Work As One
www.novell.com

Upgrade to OES Community
http://www.novell.com/communities/coolsolutions/upgradetooes/
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.