Micro Focus Expert
Micro Focus Expert

Re: Windows Explorer vs CALWIN32.DLL

I would recommend verify all of the Support Files listed by Alan Adams.

There is a good chance some install backdated one or more core Windows
files.

On 2/2/2010 1:16 PM, AMCooper63 wrote:
>
> 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
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

Still working with a Novell Engineer. This is his response right now:

The Client Development team has evalauated the dump you submitted, and determined that this is the same issue as had been reported earlier (though a slightly different symptom). We see the same key attributes of having "success" returned with a buffer that is all zeros and NULLs. And the memory being allocated for that response is relatively huge, implying that the code has had to retry multiple times for "insufficient buffer" prior to the failure finally seen in the dump.

The next step will be for engineering to deliver a test/debug module to gather additional information. That's what we are waiting for.


So waiting on test module.
0 Likes
agillint Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

Probably a silly question but they did give you a date on when that fix will be released?
0 Likes
creda Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

GreenNight;1928296 wrote:
Still working with a Novell Engineer. This is his response right now:



So waiting on test module.


Wow! Looks like we found them something to do! Any news yet?
0 Likes
croftonhouse Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

I have the same issue. Any program that opens a windows dialog for opening or saving has about an 80% chance of crashing.
I checked the supporting DLLs listed:
aud
calwin32.dll
clnwin32.dll
clxwin32.dll
locwin32.dll
ncpwin32.dll
netwin32.dll

All are Version 6.01.0004.0000 same as the client install DLLs
I did notice in process explorer that some programs would access system32 and others sysWOW64. Although the files in both cases are the same version.

Here are two examples from the event viewer for two programs Explorer.exe and winimage.exe (Crashed when trying to browse for a file):

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: 0x1080
Faulting application start time: 0x01cabc82916bfb83
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\system32\CALWIN32.DLL
Report Id: cf89f725-2875-11df-aaf7-005056c00008


Faulting application name: winimage.exe, version: 8.0.0.8000, time stamp: 0x46ac6ac4
Faulting module name: CALWIN32.DLL, version: 6.1.4.0, time stamp: 0x4afa6ce3
Exception code: 0xc0000005
Fault offset: 0x00001e88
Faulting process id: 0xe74
Faulting application start time: 0x01cabc83b79b0129
Faulting application path: C:\Program Files (x86)\WinImage\winimage.exe
Faulting module path: C:\Windows\system32\CALWIN32.DLL
Report Id: fb71ea3e-2876-11df-987b-005056c00008

I tried reinstalling the client just in case to no avail. continued to crash right after reboot.

Hopefully this helps find a solution!

Tyler
0 Likes
agillint Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

Did anyone get an ETA on a fix for this issue? Just curious if I need to slate testing WIN 7on Novell! Thanks.
0 Likes
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

agillint;1954055 wrote:
Did anyone get an ETA on a fix for this issue? Just curious if I need to slate testing WIN 7on Novell! Thanks.


Still nothing. Not sure what the point was in even opening the incident. It's been months and now they don't even respond to my emails.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Windows Explorer vs CALWIN32.DLL

GreenNight,
> Still nothing. Not sure what the point was in even opening the
> incident. It's been months and now they don't even respond to my emails.
>

Can you tell me the incident number so we can investigate?

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)


Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
Highlighted
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

SR# 10589037901+EO

This is the last email I received from them. Nice enough.

Hi John,

With reference to: Novell Service Request # 10589037901 - Explorer.exe crashes when unc path is entered (Explorer.exe crashes when unc path is entered)

I updated the bug report, adding that you are still awaiting a fix for this issue. As before, I can't give a date when the engineering department might continue their investigation of this bug, but I know it hasn't been forgotten or ignored. I'll let you know as soon as there is news. Of course, please feel free to inquire about this issue at any time.


This was on 3/4 responding to an email where I asked for an update. The incident was initially opened 1/18.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Windows Explorer vs CALWIN32.DLL

GreenNight,
> SR# 10589037901+EO
>
> This is the last email I received from them. Nice enough.
>

OK. I have asked.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)


Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
Knowledge Partner
Knowledge Partner

Re: Windows Explorer vs CALWIN32.DLL

OK. All I got back was that it is a tricky issue and engineering is
working on it.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)


Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
croftonhouse Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

Found this and it seems to work in stopping Windows Explorer from crashing on the Windows 7 machines:

I've solved this by going to My Computer > click on "Organize" tab (top left) > folder and search options > view tab. Check "Always show icons, never thumbnails" option and uncheck "Display file icon on thumbnails". This stops windows from generating the images and solved the problem for me. Less visually flashy yes, but at least it works =).

I have no idea why it works but it does make me very happy!

t
0 Likes
GreenNight Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

croftonhouse;1958075 wrote:
Found this and it seems to work in stopping Windows Explorer from crashing on the Windows 7 machines:

I've solved this by going to My Computer > click on "Organize" tab (top left) > folder and search options > view tab. Check "Always show icons, never thumbnails" option and uncheck "Display file icon on thumbnails". This stops windows from generating the images and solved the problem for me. Less visually flashy yes, but at least it works =).

I have no idea why it works but it does make me very happy!

t


HAHAHAHA

You sir are a god among men. That worked great. I can't believe it.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Windows Explorer vs CALWIN32.DLL

Croftonhouse,
> olved this by going to My Computer > click on "Organize" tab (top
> left) > folder and search options > view tab. Check "Always show icons,
> never thumbnails" option and uncheck "Display file icon on thumbnails".
> This stops windows from generating the images and solved the problem for
> me. Less visually flashy yes, but at least it works =).
>

Nice catch!

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)


Novell has a new enhancement request system,
or what is now known as the requirement portal.
If customers would like to give input in the upcoming
releases of Novell products then they should go to
http://www.novell.com/rms

0 Likes
jirsaj Absent Member.
Absent Member.

Re: Windows Explorer vs CALWIN32.DLL

I've solved this by another messy way. I've replaced calwin32.dll in Win7 safe mode by the older one from the latest client for XP. Now after the 3 weeks it seems to be working well.


croftonhouse;1958075 wrote:
Found this and it seems to work in stopping Windows Explorer from crashing on the Windows 7 machines:

I've solved this by going to My Computer > click on "Organize" tab (top left) > folder and search options > view tab. Check "Always show icons, never thumbnails" option and uncheck "Display file icon on thumbnails". This stops windows from generating the images and solved the problem for me. Less visually flashy yes, but at least it works =).

I have no idea why it works but it does make me very happy!

t
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.