VMware Communities > VMTN > VMware Server > VMware Server 1 > Discussions

This Question is Possibly Answered

1 "correct" answer available (10 pts) 1 "helpful" answer available (6 pts)
1 2 3 Previous Next
Reply Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Jul 11, 2007 6:56 AM
in response to: KevinG
Click to view jaysonl's profile Lurker jaysonl 2 posts since
Aug 13, 2005
You have got to be kidding me...

After many years of being a faithful user many are teling me that the fix is actually a registry hack posted by a user??? --no offense wislam but we should not have to muck up the registry due to poor coding.

This is plain unacceptable from any company...let alone one owned by EMC. How did this issue ever pass QA? This frustration makes me almost want to consider a different product.

KevinG, I think the community deserves a proper response.
When will the patch or fix be released by VMware to resolve this issue?

I am having the same issue with VMware Workstation 6 on Vista x64
-J
Reply Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Jul 11, 2007 8:14 PM
Click to view rhyno's profile Lurker rhyno 1 posts since
Jul 11, 2007
Add me to the list...

I get the same Application failure. hr = 0x80004003: (null) error.

AMD (could that be the issue?) X2 3800+, 2GB RAM, 500GB HDD.
Running Vista Business w/all patches. VMWare WS 6.0.0.45731.
Tried running as Admin. Tried setting NTFS permissions on \VMWare to Everyone|Full Control. Tried the v6 registry hack.

Same error every time.
Reply Re: VMware Server Console error: Application failure. hr = 0x80004003: (null) Jul 25, 2007 8:48 PM
Click to view RuneBergen's profile Lurker RuneBergen 3 posts since
Jul 25, 2007
Does anyone have a WORKING fix for this?!?!

I tried everything, including the registry batch file...

No luck :((((
Reply Re: VMware Server Console error: Application failure. hr = 0x80004003: (null) Dec 6, 2007 12:23 PM
Click to view S3AN@H0M3's profile Lurker S3AN@H0M3 1 posts since
Dec 6, 2007

I had the same problem with VMWare Server 1.4 when running the Console. After reading through various posts came to the conclusion that i my case it was likely to be registry perms that were causing the problems. Using SysInternals (now Micro$oft) RegMon I could see ACCESS DENIED on a number of HKCR\vmappsdk* entries. Giving read access to the appropriate user account on each of these entries and any child entries cleared up these errors and allowed the console to run.

The SysInternals tools are free and fantastic for tracking down the causes of problems like this: SysInternals Tools

Reply Re: Fix for Workstation Edition Dec 15, 2007 6:26 AM
in response to: wislam
Click to view bmn's profile Lurker bmn 1 posts since
Dec 15, 2007
Great job Wislam!
Reply Re: Fix for Workstation Edition Dec 27, 2007 1:47 PM
in response to: bmn
Click to view DocMAX's profile Lurker DocMAX 1 posts since
Dec 27, 2007

hello,

i have the same problem. and batch fix doesnt work even in safe mode. i cant get access to the specific registry entries...

Reply Re: Fix for Workstation Edition Jan 10, 2008 1:45 AM
in response to: DocMAX
Click to view eddie34's profile Lurker eddie34 2 posts since
Jan 10, 2008

Hello i am french, sorry for the translation!
I installed vmware workstation 6.02 on windows vista premium 32bit and I too error 0x80004003.
I am logged on as Administrator and the fix (vmware.6.0_0x80004003_reg_fix.bat) is not working even in safe mode.

_vmware_0x80004003_reg_fix.log :

LookupAccountName : setowner HKEY_CLASSES_ROOT\vmappcfg.AddPrinterDlg : administrators : 1337 Structure d'ID de sécurité non valide.
Current object HKEY_CLASSES_ROOT\vmappcfg.AddPrinterDlg will not be processed
LookupAccountName : setowner HKEY_CLASSES_ROOT\vmappcfg.AddPrinterDlg.9 : administrators : 1337 Structure d'ID de sécurité non valide.
Current object HKEY_CLASSES_ROOT\vmappcfg.AddPrinterDlg.9 will not be processed
LookupAccountName : setowner HKEY_CLASSES_ROOT\vmappcfg.ChangePasswordDlg : administrators : 1337 Structure d'ID de sécurité non valide.
Current object HKEY_CLASSES_ROOT\vmappcfg.ChangePasswordDlg will not be processed

vmware-eddie-5964.log :

Jan 10 10:39:55.675: vmui| Log for VMware Workstation pid=5964 version=6.0.2 build=build-59824 option=Release
Jan 10 10:39:55.675: vmui| Hostname=eddiepc
Jan 10 10:39:55.862: vmui| HostDeviceInfo: Failed to enumerate host parallel ports via the registry. Could not open device map parallel port registry key.
...
Jan 10 10:39:56.970: vmui| Unhandled COM exception: hr = 0x80004003: (null)
Jan 10 10:40:00.014: vmui| Exception caught; trying to exit app.
Jan 10 10:40:00.014: vmui| Exited abnormally.

Please can you describe the procedure for his works ?
Reply Re: Fix for Workstation Edition Jan 23, 2008 9:17 AM
in response to: eddie34
Click to view Sev's profile Lurker Sev 2 posts since
Jan 23, 2008

Hello / Bonjour,

After searching for hours how to resolve the problem for myself, I succeeded ! I used the reg_fix.bat posted somewhere here on VmWare Communities, which I had to modify because I'm French, in order to avoid the error message "Structure d'ID de sécurité non valide" . All details are explained in a text file (in English and French) compressed in the RAR file archive following this link :

http://rapidshare.com/files/86005455/vmware_6.0_0x80004003_reg_fix.rar.html

In this archive, you will find the reg_fix.bat for both French and English users, for VmWare Workstation (also works with ACE) ver. 6.0 and 6.0.2, and another helpful tool. Just read the HOW_TO...

I hope I was clear enough to help you with the explanations I wrote in this text file.

Good luck !

Reply Re: Fix for Workstation Edition Jan 24, 2008 1:01 AM
in response to: Sev
Click to view eddie34's profile Lurker eddie34 2 posts since
Jan 10, 2008

It's great thank Sev :8},
Having applied the fix vmware_6.0.2_0x80004003_reg_fix_fra.bat the software is put into operation.
Thank you again for your post
Reply Re: Fix for Workstation Edition Jan 25, 2008 9:27 AM
in response to: eddie34
Click to view Sev's profile Lurker Sev 2 posts since
Jan 23, 2008

Je t'en prie ! C'est cool, ça me fait plaisir d'avoir pu aider quelqu'un ! ;)
Reply Re: Fix for Workstation Edition Mar 24, 2008 5:50 AM
in response to: Sev
Click to view LouisK's profile Novice LouisK 16 posts since
Feb 21, 2007

Hi, I have tried the fix but it doesn't work! I have an administrator account but I apparently don't have the appropriate rights. Is there a fix for this. I have searched the forum but haven't found a solution to the problem.

See the screenshot for what I get when I run the fix.

Attachments:
Reply Re: Fix for Workstation Edition Mar 25, 2008 5:01 AM
in response to: wislam
Click to view Badgerballs's profile Novice Badgerballs 39 posts since
Sep 15, 2007

Thanks Pal, I have just spent 6 hours getting rid of a poxy piece of SynTek spyware that appears to have been installed by a Buffalo drive USB speedup utility. I wasn't looking forward to another lengthly period fixing 603. Your batch file worked great for me. Vista Business SP1 on Dell 1700 Vostro T7500.

Great job

bfn

Reply Re: Fix for Workstation Edition May 2, 2008 8:40 AM
in response to: wislam
Click to view Lahore_Pakistan's profile Novice Lahore_Pakistan 13 posts since
Jul 3, 2007
Installed new Vista . Installed Vmware Workstation latest 6.x. getting error . downloed and run bactch file . No luck same eror. ..
is this is still an issue with Vmware ? or do they have anyting to fix this?

Regards
Lahore.
Reply Re: Fix for Workstation Edition May 27, 2008 12:23 PM
in response to: Lahore_Pakistan
Click to view ionsor's profile Lurker ionsor 1 posts since
May 27, 2008

I have Windows vista home premium and Vmware 6.0.1 workstation

I had the error hr = 0x80004003 and i solve this problem using vmware_0x80004003_reg_fix.zip. (attached in this post) you have to start the pc in safe mode and i run it, when it fihish start vmware. it worked for me and right now i'm instaling xp in a virtual machine

Attachments:
Reply Re: VMware Server Console error: Application failure. hr = 0x80004003: (nul Oct 12, 2008 7:13 PM
in response to: mainframevmguy
Click to view tlh's profile Lurker tlh 2 posts since
Jun 14, 2008

After the same issue on XP professional I found that I did not have a FQDN and after adding mshome.net to my server name everything worked fine. Oh, I also ran the updated configuraiton script I hope this helps someone.
1 2 3 Previous Next
Actions