Application error when using VB6 Intrinsic Controls [Visual Basic]

Prev: System Error &H80070057 "The parameter is incorrect"
Next: Command line MAKE crashes - works in IDE

From: garydbutler on 25 Jul 2008 17:28

I have been using VB6 on my PC for over a year now. About a week ago I
started getting an application error anytime I open a form in the designer.
I thought my projects had been corrupted but it happens if I start a brand
new project, add a standard Label control (or text box) to the form then try
to close the form. If I save then close the project I get the error when I
open the project and try to view the form in the designer.

I have uninstalled and reinstalled VB6 with no luck.

The error message says:

Label:VB6.EXE - Application Error

The instruction at "0x004581f1" referenced memory at "0x00000000". The
memory could not be "read".

From: MikeD on 25 Jul 2008 18:40

"garydbutler" <garydbutler(a)discussions.microsoft.com> wrote in message
news:AE58E566-73C8-4E9D-8280-BA0810BF662E(a)microsoft.com...
>I have been using VB6 on my PC for over a year now. About a week ago I
> started getting an application error anytime I open a form in the
> designer.
> I thought my projects had been corrupted but it happens if I start a brand
> new project, add a standard Label control (or text box) to the form then
> try
> to close the form. If I save then close the project I get the error when
> I
> open the project and try to view the form in the designer.
>
> I have uninstalled and reinstalled VB6 with no luck.
>
> The error message says:
>
> Label:VB6.EXE - Application Error
>
> The instruction at "0x004581f1" referenced memory at "0x00000000". The
> memory could not be "read".

Can't provide much help, but do have a couple comments.

First, I'm pretty sure this problem has been asked about before. Not sure
though and can't remember details. I suggest you search the newsgroups at
http://groups.google.com/advanced_search.

Second, it does appear that some part of VB is corrupted. Unfortunately,
simply uninstalling and re-installing is frequently not sufficient because
that doesn't actually remove EVERYTHING. There will still be certain files
and Registry entries left over even after uninstalling. My experience has
been that doing a Repair is usually better than uninstalling/reinstalling,
so you might want to try that. My belief (I have no proof of this) is that
VB's Setup tries to take shortcuts to hasten the installation. In doing
that, if it finds an existing file, Registry entry, etc., etc., it simply
skips everything to do with that. A Repair expects certain files, Registry
entries, whatever to exist and does just what it's supposed to do....repair
it. You'd EXPECT a full installation would do the same thing (especially
after an uninstallation), but I don't think it does. This belief is based
mostly on the fact that I've tried the uninstall/reinstall bit and still had
the exact same problem. However, then trying a Repair did indeed fix it.
So, I don't even bother with uninstall/reinstall anymore and just do the
Repair (and I've only ever had to do this a couple times in over 10 years of
using VB5/6 and that's including a lot of installations of VB6 on virtual
PCs). Furthermore, the well-known problem of licensing information for
controls not getting added to the Registry
(http://support.microsoft.com/kb/194751/en-us and
http://support.microsoft.com/kb/177799/EN-US) sort of lends credence to this
(if the same or newer version of the control already exists and is
registered, VB5/6's Setup skips adding licensing information for that
control). Microsoft doesn't actually document this as bug, but as a
"problem". So, whatever VB's Setup is doing is "by design". IOW, VB's Setup
is trying to take a shortcut, but the developers of its Setup program were
short-sighted. <g>

If a Repair still doesn't solve it, then the next step would be to uninstall
VB, but before you re-install it run a good Registry cleaner, and THEN
reinstall VB. Only do this though AFTER you've searched google because I
just have a feeling you're going to find a post providing a much easier fix
(like unregistering and then registering one file).

Oh, and in just reading the KB article referenced above, I guess the option
is Reinstall, not Repair.

--
Mike
Microsoft MVP Visual Basic

From: garydbutler on 25 Jul 2008 21:38

I've done the reinstall, uninstall, etc.. and still no luck. I see a
million registry cleaners but I've heard bad things about using them. Are
there any that can be trusted?

"MikeD" wrote:

>
>
> "garydbutler" <garydbutler(a)discussions.microsoft.com> wrote in message
> news:AE58E566-73C8-4E9D-8280-BA0810BF662E(a)microsoft.com...
> >I have been using VB6 on my PC for over a year now. About a week ago I
> > started getting an application error anytime I open a form in the
> > designer.
> > I thought my projects had been corrupted but it happens if I start a brand
> > new project, add a standard Label control (or text box) to the form then
> > try
> > to close the form. If I save then close the project I get the error when
> > I
> > open the project and try to view the form in the designer.
> >
> > I have uninstalled and reinstalled VB6 with no luck.
> >
> > The error message says:
> >
> > Label:VB6.EXE - Application Error
> >
> > The instruction at "0x004581f1" referenced memory at "0x00000000". The
> > memory could not be "read".
>
> Can't provide much help, but do have a couple comments.
>
> First, I'm pretty sure this problem has been asked about before. Not sure
> though and can't remember details. I suggest you search the newsgroups at
> http://groups.google.com/advanced_search.
>
> Second, it does appear that some part of VB is corrupted. Unfortunately,
> simply uninstalling and re-installing is frequently not sufficient because
> that doesn't actually remove EVERYTHING. There will still be certain files
> and Registry entries left over even after uninstalling. My experience has
> been that doing a Repair is usually better than uninstalling/reinstalling,
> so you might want to try that. My belief (I have no proof of this) is that
> VB's Setup tries to take shortcuts to hasten the installation. In doing
> that, if it finds an existing file, Registry entry, etc., etc., it simply
> skips everything to do with that. A Repair expects certain files, Registry
> entries, whatever to exist and does just what it's supposed to do....repair
> it. You'd EXPECT a full installation would do the same thing (especially
> after an uninstallation), but I don't think it does. This belief is based
> mostly on the fact that I've tried the uninstall/reinstall bit and still had
> the exact same problem. However, then trying a Repair did indeed fix it.
> So, I don't even bother with uninstall/reinstall anymore and just do the
> Repair (and I've only ever had to do this a couple times in over 10 years of
> using VB5/6 and that's including a lot of installations of VB6 on virtual
> PCs). Furthermore, the well-known problem of licensing information for
> controls not getting added to the Registry
> (http://support.microsoft.com/kb/194751/en-us and
> http://support.microsoft.com/kb/177799/EN-US) sort of lends credence to this
> (if the same or newer version of the control already exists and is
> registered, VB5/6's Setup skips adding licensing information for that
> control). Microsoft doesn't actually document this as bug, but as a
> "problem". So, whatever VB's Setup is doing is "by design". IOW, VB's Setup
> is trying to take a shortcut, but the developers of its Setup program were
> short-sighted. <g>
>
> If a Repair still doesn't solve it, then the next step would be to uninstall
> VB, but before you re-install it run a good Registry cleaner, and THEN
> reinstall VB. Only do this though AFTER you've searched google because I
> just have a feeling you're going to find a post providing a much easier fix
> (like unregistering and then registering one file).
>
> Oh, and in just reading the KB article referenced above, I guess the option
> is Reinstall, not Repair.
>
> --
> Mike
> Microsoft MVP Visual Basic
>
>
>
>

From: Patrick Weidener on 26 Jul 2008 04:36

If I were you, I'd delete the C:\Programs\Microsoft Visual Studio folder
manually, then re-install it.
Un-installing and re-installing never got me far.

From: expvb on 26 Jul 2008 11:27

| Next | Last
Pages: 1 2
Prev: System Error &H80070057 "The parameter is incorrect"
Next: Command line MAKE crashes - works in IDE