mscomm32.ocx : file is missing or invalid
Hi when installing a visual basic 6 project in Vista 32/64, the process completes fine but when i try to execute the file after i get the error:
"component 'mscomm32.ocx' or one of its dependencies not correctly registered: a file is missing or invalid".
I have made sure i have the control in the correct place and that it is registered fine aswell. Any ideas?
[379 byte] By [
YimTaka] at [2008-2-27]

YimTaka,
When installing a Visual Basic 6.0 application on Vista, you need to be an admin and run elevated (right click on the exe or shortcut and select "Run as Admin"). You'll need to do this when installing the IDE and SP6 on your box as well.
When running VB6 applications on Vista, you'll need to run under these settings (Admin/Elevated).
Please let me know if you are having issues installing/running under these conditions.
Thanks,
Chris Mayo
Visual Basic Program Manager
Hi All,
I had the same problem.
I found a workaround: if I don't run my application as an administrator (but still using an administrator account), it works fine.
The problem is that I need to run it as an administrator for other components of my project to work...
Any idea how I can get mscomm32.ocx to work when I run my app as an administrator?
I find all this very confusing.
Thanks.
I believe this is a Vista bug.
I had the same problem from a customer who installed my program on his brand new Toshiba with Vista Home. Doing the regsvr32 thing did not get it to work. Running Adminitrator privilege and WinXP compatibility also did not work.
The solution which is very surprising and weird, do not make sense at all is to UNREGISTER the OCXs. I managed to solve my customer problem with the steps I found in this Intuit TurboTax support forum. The actual solution to unregister is found in page 4 of this thread.
http://forums.turbotax.com/intuit/board/message?board.id=installupdate06&message.id=1307&view=by_date_ascending&page=1
As programmers, our immediate reaction would be to register the OCXs. Won't work.
Hi Chris,
I have (as others) have encountered similar problems (error 339). Please see post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1499007&SiteID=1
I have tested my application which uses a dcube3.ocx - installed with Installshield. It works well under Windows Vista Hoe Premium - but I get a error 339 when I run it under Vista Enterprise. Angelo discovered that using the msiexec /i <MSI file path> ALLUSERS=TRUE resolved his 339 problem.
In general how do I use the msiexec command to install an application with ALLUSERS=TRUE?
Also, why would the installtion work on Vista Home Premium and not Vista Enterprise?
Regards,
David Reeves