Regsvr32 failure

[PaulFXH]

Hi David
Thanks once again for your comments and suggestions.
Yes, my primary interest is in getting wmp 10 to function in the user
account. However, I have really drawn a blank in trying to find an easy
fix for this either through a variety of newsgroups or by combing
through the MS KB library.
I have therefore turned my attention to the only other feature on my
computer that appears to be account-specific (i.e. works in my account
but NOT in the users account). I am hoping that there may be a link
between the inability of the user account to launch wmp 10 or to
register various dll files (even with admin rights).
I checked out the utilities RegMon and FileMon as you suggested.
I launched wmp 10 in the users account (admin status) with FileMon
running. Three attribute errors showed up before the Internal
Application Error message appeared.
These were:
1. C:\Program Files\Windows Media Player\wmplayer.exe.Local
NOT FOUND
2. C:\Program Files\Windows Media Player\CLBCATQ.DLL
NOT FOUND
3. C:\Program Files\Windows Media Player\COMRes.dll
NOT FOUND

None of these errors show up when I launch wmp 10 from my own account.
Nevertheless, I do get one "non-trivial" error indicating that
IMGUTIL.DLL is missing. However, this doesn't prevent the app
launching.

But what is wmplayer.exe.Local?
Paul

 

[David Candy]

..Local an optional file that tells windows to load dlls from the exe directory rather than anywhere else. Just create an empty file of that name to make it happen. This allows 2 versions of the same file to be in memory at the same time being used by different apps.
The other two are in System32 and would be found there.

What happens when it crashed. Describe it.

 

[PaulFXH]

Hi David
What happens when wmp 10 crashes from the users account? Exceedingly
little. After double-clicking the desktop icon, almost immediately a
small splash screen (with wmp 10 header) appears announcing that "An
Internal Application Error has occurred".
That's it.
I created an empty file named wmplayer.exe.Local (from notepad) and
placed it inside the C:\program files\windows media player\ folder.
I also placed in the same folder the two dll files I mentioned in the
last post, although I now realize that this was unnecessary.
Tried to launch wmp 10 from the users account again, while FileMon was
running, and got the same error message.
However, this time the only "serious" error messages were two instances
of Name Invalid for the file C:\program files\windows media
player\wmplayer.exe.Local.
Note that while the wmplayer.exe file in the above folder is "labelled"
Windows Media Player and Microsoft Corporation while the new file
wmplayer.exe.Local is labelled only Local File and 0KB. Perhaps this is
what is causing the Name Invalid message..

There were a number of Not Found messages all referring to various dll
files. However, it seems that the program subsequently went to
c:\windows\system32\ to pick these up.

Near the end of the WMP operations, however, two further Not Found
messages were posted because, in each case of c:\windows\windows
shell.config
Each instance of this produced a statement "Option Open Access All"
which seems to indicate that this was not a fatal error.

Are we making progress yet?
Paul

 

[PaulFXH]

Hi David
Guess what? I've fixed the problem!!
I just happened to stumble upon a newsgroup I hadn't used before and
found a well-explained and very easy fix.
It appears that my wmp 10 problem did indeed result from the
unregistered jscript.ddll and vbscript.dll files in the users account.
The reason they could not be registered was due to a permissions issue
in HKLM\Software\Classes.
Once I adjusted the permissions I was able to register the dll files
from the user account and then wmp 10 launched perfectly.

Here's the site I used:
http://www.softwaretipsandtricks.co...r-internal-application-error-has-occured.html

Post #7 explains the fix.
Thanks for your help and encouragement
Paul

 

[David Candy]

Users shouldn't be able to write to that key. They shouldn't be able to register dlls mainly (99.9%) because they don't have access to that key (there is a different key for User installed programs).