Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Setup / May 2004

Tip: Looking for answers? Try searching our database.

Problem installing VS6 SP6 on Windows 2003 server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
David C. Allen - 05 May 2004 15:45 GMT
When I try to intall the VS6 SP6 for VB6 on my Windows 2003 server the
install gives a list of ocxs and one dll (htmutil.dll) that were not
registered. How do I fix this?

The message goes like this: msmask32.ocx unable to register itself in the
system registry.

Any ideas?
Brad - 08 May 2004 18:18 GMT
>-----Original Message-----
Wow, finally a similar problem!

I have the exact same errors installing VS6 on my Windows
2000 Pro machine.

Did you ever find a solution?

Thanks,

Brad

>When I try to intall the VS6 SP6 for VB6 on my Windows 2003 server the
>install gives a list of ocxs and one dll (htmutil.dll) that were not
[quoted text clipped - 6 lines]
>
>.
gagarux - 18 May 2004 22:49 GMT
>When I try to intall the VS6 SP6 for VB6 on my Windows
>  2003 server the
>install gives a list of ocxs and one dll (htmutil.dll)
>that were not
>registered. How do I fix this?

>The message goes like this: msmask32.ocx unable to
>register itself in the
>system registry.

>Any ideas?

Try the following:
1) Delete the offending DLL from your Program Files\Common
  Files\System folder and subfolders.  You will notice
  that the Windows File Protection mechanism will
  immediately replace the file you have just deleted,
  hopefully with the right version of the DLL

2) Run your VS6 installation again

If you are still having problems, do the following:
3) Rename the offending DLL found in %SystemRoot%\System32
  \DllCache

4) Search on your hard drive for the latest version of the
  offending DLL. You should find the latest DLL typically
  in any Service Pack, HotFix or Windows Update folder,
  if you had selected to save these files when you last
  updated.  If you do not find the latest DLL, proceed to
  the next step

5) If you found the latest DLL in the previous step, copy
  it to the DLLCache folder

6) Reboot your machine

7) Repeat Steps 1 and 2 from above.  If you did not find a
  replacement DLL from Step 4, you will be prompted to
  insert your Windows CD-ROM

Of course, you will need to be logged on as a user with
local administrator privileges on your machine to perform
the above procedure.

Hope this helps

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.