Highlighted
sselaya
New Member.
7581 views

XTSvcMgr.exe Fault

Faulting application name: XTSvcMgr.exe, version: 1.0.0.0, time stamp: 0x4c0584a5
Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp: 0x4a5be02b
Exception code: 0xc0000374
Fault offset: 0x00000000000c6cd2
Faulting process id: 0x4f8
Faulting application start time: 0x01cb0d57af2c03b4
Faulting application path: C:\Program Files\Novell\Client\XTier\Services\XTSvcMgr.exe
Faulting module path: C:\windows\SYSTEM32\ntdll.dll
Report Id: fdabad15-794c-11df-8624-78e7d18348c6


We have recently started deploying Windows 7 using Novell Client 2 SP1 IR1 (and now IR2). We have been getting reports of pc hangs on a few computers and I also have the issue on my brand new HP desktop pc. It appears to happen while accessing network drives. Everything is fine when first booting up and accessing files on the network. After about 20 minutes or longer the Computer will show not responding in the Task manager. Every time this happens I will see the Application Error above in the event log. Also, I cannot stop the explorer process, shutdown or do anything other than turn the pc off and back on. I can temporarily use applications that are open as long as they do not have to access the network. I can browse to my local drives but no network drives once this happens (although I can get to the mapped drives from a command prompt). No high utilization on the computer at all. In the past when I have lost access to explorer I have been able to kill that process.
Labels (1)
0 Likes
7 Replies
jcegstad Absent Member.
Absent Member.

Re: XTSvcMgr.exe Fault

I'm seeing the same behavior on my Windows 7 x64 workstation, using Novell Client 2 SP1 IR1. However I only see it happen once every few weeks.

Unfortunately I don't have much to add beyond sharing your pain. I suspect this hanging behavior has something to do with how vista/win7 deals with crashing programs and process 'wait chains' compared to how Windows XP handled it, but I don't know enough to add anything more constructive than that.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: XTSvcMgr.exe Fault

sselaya <sselaya@no-mx.forums.novell.com> wrote:

> Faulting application name: XTSvcMgr.exe, version: 1.0.0.0, time stamp:
> 0x4c0584a5
> Faulting module name: ntdll.dll, version: 6.1.7600.16385, time stamp:
> 0x4a5be02b
> Exception code: 0xc0000374
> Fault offset: 0x00000000000c6cd2
> Faulting process id: 0x4f8
> Faulting application start time: 0x01cb0d57af2c03b4
> Faulting application path: C:\Program
> Files\Novell\Client\XTier\Services\XTSvcMgr.exe
> Faulting module path: C:\windows\SYSTEM32\ntdll.dll
> Report Id: fdabad15-794c-11df-8624-78e7d18348c6


STATUS_HEAP_CORRUPTION (0xC0000374) may represent an issue that was
only recently identified, and could result in corruption of the memory
heap on the XTSVCMGR.EXE process.

The situation in which the corruption could occur had to do with
conditions that occurred when a previously responsive SLP DA was
determined to now be non-responsive. In the process of marking that
DA "bad" in memory, it was also possible for memory to become
corrupted.

One way to avoid /this/ particular known cause should be to disable
"SLP" as a name resolution method on the "Name Services" tab of the
Novell Client Properties. In place of resolving the names by SLP, you
would have to use DNS names for the tree and/or server, or literal IP
addresses to work around the issue until a solution was available.

Note that even with "SLP" disabled in the "Name Services" tab,
attempting to use the "Trees" or "Servers" button on the eDirectory
tab of the Novell Client login dialog will still attempt to use SLP,
because SLP is the only name resolution provider capable of the
wildcard searches needed for "browse" functionality.

(Also note one cause of this "DA that was responsive is now
non-responsive" is the NetWare SLPTCP.NLM issue cited under TID
7006181, so obtaining that fix from Novell might also potentially
mitigate the issue if NetWare-based SLP DAs are in use.
http://www.novell.com/support/viewContent.do?externalId=7006181)

If attempting to avoid the use of SLP doesn't work around the issue,
or you require a more timely solution to the issue for continuing to
use SLP for name resolution, opening a support call with Novell and
citing Bug 611833 as a starting point for determining whether the
corruption you're seeing is due to the same root cause or something
different.

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
sselaya
New Member.

Re: XTSvcMgr.exe Fault

Thanks for the info. I did see posts regarding SLP and had tried the idea of disabling SLP as one of my choices under Name Services. Unfortunately it still happened, but it is interesting that you mention that it still tries SLP in certain circumstances. I did not use the Trees or Servers button but I am wondering (assuming SLP is the culprit) if there are other things that may happen. I also saw in the posts that Novell was supposedly going to release a field patch. Are they going to allow us to download it without an incident being created?

In looking at other Windows 7 machines that do not hang we are seeing the XTier Service Manager errors on those as well but explorer is not hanging. This is easily seen by going to the start menu and typing reliability (also in the Action Center). So, I am not sure why some machines are more effected than others by this.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: XTSvcMgr.exe Fault

sselaya <sselaya@no-mx.forums.novell.com> wrote:

> Thanks for the info. I did see posts regarding SLP and had tried the
> idea of disabling SLP as one of my choices under Name Services.
> Unfortunately it still happened, but it is interesting that you mention
> that it still tries SLP in certain circumstances. I did not use the
> Trees or Servers button but I am wondering (assuming SLP is the culprit)
> if there are other things that may happen. I also saw in the posts
> that Novell was supposedly going to release a field patch. Are they
> going to allow us to download it without an incident being created?
>
> In looking at other Windows 7 machines that do not hang we are seeing
> the XTier Service Manager errors on those as well but explorer is not
> hanging. This is easily seen by going to the start menu and typing
> reliability (also in the Action Center). So, I am not sure why some
> machines are more effected than others by this.


As soon as the SLPTCP.NLM changes have been released as a formal FTF
patch, it should no longer require an incident to obtain the file, and
it will be available under the same entitlement as other NetWare FTFs.
They haven't reached that point yet since there are still customer
behavior reports coming in that are being followed-up on before
considering the SLPTCP.NLM fix design to be complete. Changes in the
status and availability of the fix will be reflected in the TID.

For the recently identified cause of XTSVCMGR heap corruption I
referred to, only an incident citing the Bug 611833 issue could get
access to a test build of the fix for that identified root cause.
Otherwise you would need to wait until the IR3 build (which should
include those fixes) before determining whether this identified cause
relates to the issues you're observing.

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
shuntress Absent Member.
Absent Member.

Re: XTSvcMgr.exe Fault

The problem, as you have described it, appears to be virtually identical to one I have been fighting for a few weeks now. I am running a fairly fresh installation of Windows 7 Professional 64-bit on a private label or "grey box" system, with Novell Client 2 SP1.

However, as I don't often need to access Novell-based resources on our network, I have taken to logging into the computer with my local account only. Then, if I do need to get to a Novell-based server, I do a Novell log-in via the Novell client icon in the system tray.

But, the problem occurs even when I have not logged into Novell during a given session. Does it make sense that XTSvcMgr.exe can be a problem even if you're not logged into Novell, i.e. just because the Novell client is present on the system?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: XTSvcMgr.exe Fault

shuntress <shuntress@no-mx.forums.novell.com> wrote:

> The problem, as you have described it, appears to be virtually identical
> to one I have been fighting for a few weeks now. I am running a fairly
> fresh installation of Windows 7 Professional 64-bit on a private label
> or "grey box" system, with Novell Client 2 SP1.
>
> However, as I don't often need to access Novell-based resources on our
> network, I have taken to logging into the computer with my local account
> only. Then, if I do need to get to a Novell-based server, I do a Novell
> log-in via the Novell client icon in the system tray.
>
> But, the problem occurs even when I have -not -logged into Novell
> during a given session. Does it make sense that XTSvcMgr.exe can be a
> problem even if you're not logged into Novell, i.e. just because the
> Novell client is present on the system?


The XTSVCMGR.EXE crash being described here is something that was
addressed in the Novell Client 2 SP1 (IR3) and later. Issue listed as
" LIBSLP potentially issuing a double-free when handling KnownDABadDA.
(Bug 611833)".
http://download.novell.com/Download?buildid=yYAo1K-DpFU~

The NetWare SLP DA issue in SLPTCP.NLM (which is what was causing the
SLP DA to be "bad" in the first place) now has a fix publicly
available, too.
http://www.novell.com/support/viewContent.do?externalId=7006181
http://download.novell.com/Download?buildid=3jTAJ9OIQAQ~

Yes, it would be possible for the XTSVCMGR.EXE crash to occur "even
though I'm not logging into eDirectory", since the Novell Client
network provider is still available to Windows even though you didn't
login, and Windows is still invoking the Novell Client to resolve
network names, etc., as part of normal Windows network operations.

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
shuntress Absent Member.
Absent Member.

Re: XTSvcMgr.exe Fault

Alan,

Many thanks for the prompt info. I have downloaded and installed Novell Client 2 SP1 (IR3), and hopefully it will resolve the problem.

Steve Huntress
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.