gregarican
IS-IT--Management
One custom VB 6.0 app our company uses kept on throwing
a 'Runtime Error 481 - Invalid Picture' error right before
displaying the initial form. This only happened on one
particular workstation.
Researching this error message left me initially stumped
because we weren't working with any BMP or other graphic
files during the initial form load. Trying to reinstall
the app resulted in the same error message as part of
VB 6.0 Setup Toolkit startup process. The error is 481 - CTL_E_INVALIDPICTURE - 0x800A01E1.
I looked a bit deeper into the error in various forums on the Internet and found some tips that pointed to file/directory permissions. Since the app runs on the local Win98SE workstations, has no networked application file dependencies, and links to an MSSQL 2000 database using the 'sa' account authentication I had to look elsewhere.
Network connectivity to the MSSSQL 2000 database was fine,
as was connectivity to the rest of the file/printer sharing resources. Besides, the error message differs from that thrown from loss of network connectivity. I still had to look elsewhere.
Checking the hard drive I saw plenty of space on that
workstation. But I did see that the C:\temp folder had
more than 32,768 individual items! I know that cleaning out
temporary folders is always a good idea and all, yet this must be some type of VB 6.0 threshold in terms of specific
number of items. All other apps ran fine on that workstation.
Once I cleared out the temp folder all is well. Just wished
that the error message was a little more descriptive. I know
that trapping all error conditions and throwing up an
insightful message isn't an easy as it seems. But the 481
error left me initially puzzled.
Just wanted to share this tip in case anyone out there
runs into a similar situation.
a 'Runtime Error 481 - Invalid Picture' error right before
displaying the initial form. This only happened on one
particular workstation.
Researching this error message left me initially stumped
because we weren't working with any BMP or other graphic
files during the initial form load. Trying to reinstall
the app resulted in the same error message as part of
VB 6.0 Setup Toolkit startup process. The error is 481 - CTL_E_INVALIDPICTURE - 0x800A01E1.
I looked a bit deeper into the error in various forums on the Internet and found some tips that pointed to file/directory permissions. Since the app runs on the local Win98SE workstations, has no networked application file dependencies, and links to an MSSQL 2000 database using the 'sa' account authentication I had to look elsewhere.
Network connectivity to the MSSSQL 2000 database was fine,
as was connectivity to the rest of the file/printer sharing resources. Besides, the error message differs from that thrown from loss of network connectivity. I still had to look elsewhere.
Checking the hard drive I saw plenty of space on that
workstation. But I did see that the C:\temp folder had
more than 32,768 individual items! I know that cleaning out
temporary folders is always a good idea and all, yet this must be some type of VB 6.0 threshold in terms of specific
number of items. All other apps ran fine on that workstation.
Once I cleared out the temp folder all is well. Just wished
that the error message was a little more descriptive. I know
that trapping all error conditions and throwing up an
insightful message isn't an easy as it seems. But the 481
error left me initially puzzled.
Just wanted to share this tip in case anyone out there
runs into a similar situation.
