WillWilson Absent Member.
Absent Member.
14645 views

Windows Explorer vs CALWIN32.DLL

Hello all,
I'm testing out a Windows 7 workstation, connecting to our OES2 network. I got past the Login Script issues with the Client 2 for Windows by deactivating Windows Defender. After a Windows Update every time I launched Windows Explorer it crashed and put the fault on CALWIN32.DLL. I reinstalled Client 2 and that fixed the problem. I then installed MS Office 2003 and was rewarded with the same WinExplorer crash, again faulting CALWIN32.DLL. I reinstalled Client 2 again, but this time it didn't work. Any tips? Thanks.
Labels (1)
0 Likes
50 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

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

> I'm testing out a Windows 7 workstation, connecting to our OES2
> network. I got past the Login Script issues with the Client 2 for
> Windows by deactivating Windows Defender. After a Windows Update every
> time I launched Windows Explorer it crashed and put the fault on
> CALWIN32.DLL. I reinstalled Client 2 and that fixed the problem. I
> then installed MS Office 2003 and was rewarded with the same WinExplorer
> crash, again faulting CALWIN32.DLL. I reinstalled Client 2 again, but
> this time it didn't work. Any tips? Thanks.


Have not heard of that kind of thing being reported for Windows 7
workstations, for what its worth. So I tend to believe that you may
be able to identify some local variable that could avoid or resolve
the situation. (i.e. Not that this is some kind of fundamental or
common Windows 7 issue.)

In general, for a situation of "suddenly the machine starts crashing
in CALWIN32.DLL and re-installing the Novell Client fixes it
temporarily", regardless of which Windows or Novell Client version
we're talking about I would be suspicious that something is replacing
or back-revving either CALWIN32.DLL itself or any of its related
libraries (NETWIN32.DLL, CLNWIN32.DLL, AUDWIN32.DLL, CLXWIN32.DLL,
NCPWIN32.DLL, LOCWIN32.DLL) such that there is a mismatched or
otherwise incompatible set of these DLLs being loaded into memory.

It might be something specific and intentional, such as a ZENworks or
other software distribution action that was appropriately pushing some
files to Windows 5.x workstations. Or it could just be an application
that has older files which didn't cause a problem on Windows 5.x.

When the issue starts occurring, perhaps search to ensure there aren't
multiple copies of these files anywhere on the machine, and also
verify that the one that are there in SYSTEM32 are actually the
versions included in the Novell Client installation set.

You /might/ also look at whether mapped search drives or other Windows
PATH entries might be pointing to a network directory that happens to
have older copies, but that seems an unlikely source of the issue
given that we're talking about EXPLORER.EXE crashing. Which unless
some very non-standard modification of the Windows DLL search order is
in play, will be all but guaranteed to load its instanced of
CALWIN32.DLL and friends from the SYSTEM32 directory.

If none of that pans out, opening a support call with Novell to
provide the dump being generated when EXPLORER.EXE crashes (and/or to
configure Windows to generate a better/bigger dump than it does by
default) would probably be the next most effective step.

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

Re: Windows Explorer vs CALWIN32.DLL

Did you ever get this fixed? I am experiencing the same issues and may open an incident if I don't hear back.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Windows Explorer vs CALWIN32.DLL

Did you look at the Files Alan Mentioned?

--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


"GreenNight" <GreenNight@no-mx.forums.novell.com> wrote in message
news:GreenNight.43lpnz@no-mx.forums.novell.com...
>
> Did you ever get this fixed? I am experiencing the same issues and may
> open an incident if I don't hear back.
>
>
> --
> GreenNight
> ------------------------------------------------------------------------
> GreenNight's Profile: http://forums.novell.com/member.php?userid=48381
> View this thread: http://forums.novell.com/showthread.php?t=391811
>



0 Likes
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

craig_wilson;1908535 wrote:
Did you look at the Files Alan Mentioned?

--
Craig Wilson - MCNE, MCSE, CCNA
Novell Knowledge Partner

Novell does not officially monitor these forums.

Suggestions/Opinions/Statements made by me are solely my own.
These thoughts may not be shared by either Novell or any rational human.


"GreenNight" <GreenNight@no-mx.forums.novell.com> wrote in message
news:GreenNight.43lpnz@no-mx.forums.novell.com...
>
> Did you ever get this fixed? I am experiencing the same issues and may
> open an incident if I don't hear back.
>
>
> --
> GreenNight
> ------------------------------------------------------------------------
> GreenNight's Profile: NOVELL FORUMS - View Profile: GreenNight
> View this thread: Windows Explorer vs CALWIN32.DLL - NOVELL FORUMS
>


Yes, there are no other instances of calwin32 on my desktop.
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Windows Explorer vs CALWIN32.DLL

Alan listed a whole array of support DLLs for you to check.
Most likely something is backdating or breaking the support DLLs.

On 1/5/2010 5:16 PM, GreenNight wrote:

>
> Yes, there are no other instances of calwin32 on my desktop.
>
>


0 Likes
Highlighted
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

craig_wilson;1912739 wrote:
Alan listed a whole array of support DLLs for you to check.
Most likely something is backdating or breaking the support DLLs.

On 1/5/2010 5:16 PM, GreenNight wrote:

>
> Yes, there are no other instances of calwin32 on my desktop.
>
>


Well, I checked for these:

NETWIN32.DLL, CLNWIN32.DLL, AUDWIN32.DLL, CLXWIN32.DLL,
NCPWIN32.DLL, LOCWIN32.DLL

And a few of those I have about 4-5 copies in various directories. I do know that reinstalling the 7 beta client does not fix the issue.
0 Likes
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

Also, I installed the new final client and the situation is the same.
0 Likes
agillint Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

Explorer Crashing in Windows 7

--------------------------------------------------------------------------------

On a fresh install of Windows 7 and then shorty after installing Novell Client 2 SP1 for Windows 7 explorer crashes. Doesn't matter what application I'm using it just crashes. I could be trying to save a file in paint or opening a email to save a attached or just wanting to save a page on the web by going to File-> Save as or just opening My Computer

I had the same problem when I tried using the Novell "vista client" on Windows 7. But I initially thought that was isolated to it being the "vista client". Although the affects were not immediate as they were today when I installed Novell Client 2 SP1 for Windows 7.

I have attached the log from Event Viewer:

Log Name: Application
Source: Application Error
Date: 1/12/2010 11:05:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: LINCOLN.dev.org
Description:
Faulting application name: Explorer.EXE, version: 6.1.7600.16404, time stamp: 0x4a765076
Faulting module name: CALWIN32.DLL, version: 6.1.4.0, time stamp: 0x4afa6ce3
Exception code: 0xc0000005
Fault offset: 0x00001e88
Faulting process id: 0xe5c
Faulting application start time: 0x01ca93a102784db8
Faulting application path: C:\Windows\Explorer.EXE
Faulting module path: C:\Windows\system32\CALWIN32.DLL
Report Id: 52904a7b-ff94-11de-9498-00123f2fa0d3

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-01-12T16:05:38.000000000Z" />
<EventRecordID>6035</EventRecordID>
<Channel>Application</Channel>
<Computer>LINCOLN.dev.org</Computer>
<Security />
</System>
<EventData>
<Data>Explorer.EXE</Data>
<Data>6.1.7600.16404</Data>
<Data>4a765076</Data>
<Data>CALWIN32.DLL</Data>
<Data>6.1.4.0</Data>
<Data>4afa6ce3</Data>
<Data>c0000005</Data>
<Data>00001e88</Data>
<Data>e5c</Data>
<Data>01ca93a102784db8</Data>
<Data>C:\Windows\Explorer.EXE</Data>
<Data>C:\Windows\system32\CALWIN32.DLL</Data>
<Data>52904a7b-ff94-11de-9498-00123f2fa0d3</Data>
</EventData>
</Event>
0 Likes
agillint Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

Any updates from anyone regarding this issue?
0 Likes
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

agillint;1923012 wrote:
Any updates from anyone regarding this issue?


I opened an incident with Novell but it's slow going. So far I've sent them a crash dump and trace logs. Not sure why, but whatever.
0 Likes
creda Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

GreenNight;1923014 wrote:
I opened an incident with Novell but it's slow going. So far I've sent them a crash dump and trace logs. Not sure why, but whatever.


I have the same issue on Windows 7 Professional 32 bit with Client 2 for Vista and ConsoleOne 1.3.6h (a whole other story). Also this is on an older PC. Dell GX280 with 2gb memory. Find any common factors or solutions?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Antw: Re: Windows Explorer vs CALWIN32.DLL

Same issue here on all Gerrman Win 7 PCs even on fresh installs. Explorer crashes almost every time when opening network neighborhood and with a 50% chance when opening a file dialog. Completely unusable as it is now.

Novell Support was very responsive and eager in getting a crash dump and it appears to be an internal windows issue that has nothing to do with misbehaving external eDir responses or the like. They have promised me that a solution is targeted for the next update after the released SP1.


>>> creda<creda@no-mx.forums.novell.com> schrieb am Dienstag, 26. Januar 2010 um 22:26 in Nachricht <creda.45f0lc@no-mx.forums.novell.com>:



GreenNight;1923014 Wrote:

> I opened an incident with Novell but it's slow going. So far I've sent
> them a crash dump and trace logs. Not sure why, but whatever.


I have the same issue on Windows 7 Professional 32 bit with Client 2
for Vista and ConsoleOne 1.3.6h (a whole other story). Also this is on
an older PC. Dell GX280 with 2gb memory. Find any common factors or
solutions?


--
creda
------------------------------------------------------------------------
creda's Profile: http://forums.novell.com/member.php?userid=62408
View this thread: http://forums.novell.com/showthread.php?t=391811
0 Likes
Anonymous_User Absent Member.
Absent Member.

Antw: Re: Windows Explorer vs CALWIN32.DLL

Same issue here on all German Win 7 PCs even on fresh installs. Explorer crashes almost every time when opening network neighborhood and with a 50% chance when opening a file dialog. Completely unusable as it is now.

Novell Support was very responsive and eager in getting a crash dump and it appears to be an internal windows issue that has nothing to do with misbehaving external eDir responses or the like. They have promised me that a solution is targeted for the next update after the released SP1.


>>> creda<creda@no-mx.forums.novell.com> schrieb am Dienstag, 26. Januar 2010 um 22:26 in Nachricht <creda.45f0lc@no-mx.forums.novell.com>:


GreenNight;1923014 Wrote:

> I opened an incident with Novell but it's slow going. So far I've sent
> them a crash dump and trace logs. Not sure why, but whatever.


I have the same issue on Windows 7 Professional 32 bit with Client 2
for Vista and ConsoleOne 1.3.6h (a whole other story). Also this is on
an older PC. Dell GX280 with 2gb memory. Find any common factors or
solutions?


--
creda
------------------------------------------------------------------------
creda's Profile: http://forums.novell.com/member.php?userid=62408
View this thread: http://forums.novell.com/showthread.php?t=391811
0 Likes
AMCooper63 Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

I also have similar Explorer crash issues.

Log Name: Application
Source: Application Error
Date: 2/2/2010 10:05:38 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ACooper-PC
Description:
Faulting application name: explorer.exe, version: 6.1.7600.16450, time stamp: 0x4aebab8d
Faulting module name: CALWIN32.DLL, version: 6.1.4.0, time stamp: 0x4afa6e1f
Exception code: 0xc0000005
Fault offset: 0x00000000000021d1
Faulting process id: 0x1660
Faulting application start time: 0x01caa42eec6289c5
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\system32\CALWIN32.DLL
Report Id: 90a5efe6-1025-11df-a2fb-00027203bbb6
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-02-02T18:05:38.000000000Z" />
<EventRecordID>15955</EventRecordID>
<Channel>Application</Channel>
<Computer>ACooper-PC</Computer>
<Security />
</System>
<EventData>
<Data>explorer.exe</Data>
<Data>6.1.7600.16450</Data>
<Data>4aebab8d</Data>
<Data>CALWIN32.DLL</Data>
<Data>6.1.4.0</Data>
<Data>4afa6e1f</Data>
<Data>c0000005</Data>
<Data>00000000000021d1</Data>
<Data>1660</Data>
<Data>01caa42eec6289c5</Data>
<Data>C:\Windows\explorer.exe</Data>
<Data>C:\Windows\system32\CALWIN32.DLL</Data>
<Data>90a5efe6-1025-11df-a2fb-00027203bbb6</Data>
</EventData>
</Event>
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.