Msched Application Error with shlwapi.dll

tony_smith · Post by **tony_smith** » Wed Dec 01, 2004 12:19 am

I am receiving the following Windows application error and I am unable to track down the cause...

"Faulting application msched.exe, version 0.0.0.0, faulting module shlwapi.dll, version 6.0.3790.212, fault address 0x000058a4."

I am using the latest version of MSched 7.3.03, however this problem started two months ago with a previous version of 7.X and after Windows update KB834707. I am running Windows 2003 Server.

The error does not seem to have an affect on the function of macros I am running, but creates multiple instances of MSched in the system tray, and pops up an error box...

"msched.exe encountered a problem and needed to close."

The weird thing is that the error box does not show up on the active remote desktop connection, but appears in a second session when the second session is opened... and never happens as long as there is a second session opened... go figure

It appears that shlwapi.dll may be the culprit... I have found reports of other specific applications (SAP for one).

Can anyone shed some light on this one?

BTW... I would be lost without Msched... it is getting better all the time... Thanks !

support · Post by **support** » Wed Dec 01, 2004 8:43 am

shlwapi.dll has something to do with IE. Could your IE installation be broken? You know how everything in Windows seems to depend on IE these days! Perhaps it would be worth reinstalling/updating IE.

tony_smith · Post by **tony_smith** » Mon Dec 13, 2004 9:13 pm

I have looked into this some more... the problem is not benign as I suspected... it is crashing a particular MS script that is called from another application. I will email the script to support separately as it is somewhat sensitive to our business.

Also, there are two variants of the problem; one is a "Reporting queued error" The other is a "Faulting Application" error. I had, by chance only had reviewed those with queued errors which do not show up in the activity log of the application that calls the MS script... the application errors do.

I have traced the problem back to when I migrated to Win2003 Server and applied all the outstanding updates. It appears to be a Windows issue, but I have no idea how to go about resolving it.

I would appreciate any help you can give.

Post by **Marcus Tettmar** » Tue Dec 14, 2004 12:32 am

shlwapi.dll is actually one of the shell libraries. The first place to check for potential problems is the Microsoft knowledge base:
http://search.microsoft.com/search/resu ... hlwapi.dll

tony_smith · Post by **tony_smith** » Thu Jan 13, 2005 9:05 pm

After a lot of fruitless research and re-installing some Windows components, I decided to write the results of each step to a log.

The result was that the problem went away.

The script moves several files from a Unix server through a Samba connection to a Win-2003 server. It then reads through each file looking for certain characters and renames the files depending on what characters are found in each of the files.

I can only guess that something was running too fast for something else to catch up and the pauses in the script to write the log gave, whatever it is, a chance to catch up.

I hope this might be helpful to someone else... it certainly caused me a lot of grief.