Member Avatar for Member #251199

Please help, this is urgent. I have a machine running Server 2008 R2 with Terminal Services installed. The software we use for our business is attache. On first run after reboot, it works fine, but any time after that, it crashes with this message:

Problem signature:
  Problem Event Name:	BEX
  Application Name:	attwinc.exe
  Application Version:	8.0.0.0
  Application Timestamp:	4b28529d
  Fault Module Name:	pngfilt.dll
  Fault Module Version:	8.0.7600.16385
  Fault Module Timestamp:	4a5bdaee
  Exception Offset:	00001e60
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7600.2.0.0.16.7
  Locale ID:	3081
  Additional Information 1:	b80f
  Additional Information 2:	b80fa8aa693f9630e858f5a976d06b8a
  Additional Information 3:	2ade
  Additional Information 4:	2adea04e810ac36f6067d59a816f636a

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

attwinc.exe is Attache. I've tried to unregister pngfilt.dll (I don't care about PNG rendering in IE, as it's a Server), but regsvr32 can't find the "dllUnregisterServer" entry-point. I've tried replacing it with an older version from IE7 - same problem.

We had the same problem on our workstations running Windows 7 Ultimate. The fix we used was to uninstall internet explorer 8, let it downgrade to IE7, then reinstall IE8; but I can't find a way to uninstall it on Server 2008 R2. It's not in the 'Features' section of Server Manager, which "Turn Windows Features on or off" redirects me to. Is it even possible? If so, how?

Does anyone have even the slightest clue as to what the problem is and how to fix it? Please? This is urgent.

vs49688

  • 2 Contributors
  • 2 Replies
  • 681 Views
  • 1 Year Discussion Span
  • Latest Post Latest Post by Member #251199

Dani AI

Generated

This is a common pattern where the Internet Explorer PNG decoder (pngfilt.dll) trips over a malformed or unusually encoded image that the app loads after the first run. @vs49688’s follow-up (re-saving the PNGs) is the practical fix; below are reliable steps to find the offending files and batch-repair them safely so others (for example ) can reproduce the fix without guessing.

First, identify which PNG(s) are being loaded by the app. Run Process Monitor as Administrator and add a simple include filter: Process Name is attwinc.exe and Path ends with .png. Clear the capture, reproduce the crash, stop capture, and inspect the last .png accesses — the files read immediately before the crash are the suspects. Also check common locations: the application folder, program data/appdata for the user, network/share folders the app reads, and any template/image repositories the software uses.

Back up suspect PNGs, then re-encode them. A safe, scriptable approach on Windows is PowerShell + .NET Image classes; run this while Attache is closed and after you’ve backed up the originals:

$root = "C:\Path\To\Attache"    # change to the folder to scan
$backup = "C:\backups\attache_pngs"
New-Item -ItemType Directory -Force -Path $backup
Get-ChildItem -Path $root -Filter *.png -Recurse | ForEach-Object {
  Copy-Item -Path $_.FullName -Destination $backup -Force
  try {
    $img = [System.Drawing.Image]::FromFile($_.FullName)
    $tmp = $_.FullName + ".tmp"
    $img.Save($tmp, [System.Drawing.Imaging.ImageFormat]::Png)
    $img.Dispose()
    Move-Item -Force $tmp $_.FullName
  } catch {
    Write-Warning "Could not re-save $($_.FullName)"
  }
}

If re-encoding doesn’t help, collect a crash dump (ProcDump or WER local dumps), run sfc /scannow, and ensure Windows/IE updates are applied; provide the dump to Attache support or Microsoft for deeper analysis. Do not delete or randomly swap system DLLs on a server — always test fixes on a non-production copy first.

Recommended Answers

All 2 Replies

Member Avatar for KrisX

Did you ever get a fix for this?

Member Avatar for Member #251199

Yes, it was a problem with the Internet Explorer HTML engine in windows. It didn't like the default png images that it was trying to load. So I opened them and resaved them and it worked

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.