For You Computer Experts
Nov 25, 2015 10:40:53 #
Tried to start PrintShop Pro 4.0 this morning and got the following message:
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
Just for kicks, would someone please translate?
I rebooted and then Print Shop worked.
It's been my experience that few computer error messages offer any insight for the average user to fix a problem.
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
Just for kicks, would someone please translate?
I rebooted and then Print Shop worked.
It's been my experience that few computer error messages offer any insight for the average user to fix a problem.
Nov 25, 2015 10:52:21 #
This was an example of sloppy programming. It means that when a program called an external routine or function using a variable which should have been first set to contain the address of the function there was no valid address set. Since the operating system couldn't find the external function without a valid address it returns with an error code which in turn was translated into the pseudo english message you reported.
This isn't a kind of error any user could "fix" and without knowing what sequence led to the function call being made with an uninitialized external function reference there would be no way to know how to avoid the problem. It could have been a "hardware" glitch (e.g. random bit change in an otherewise correct address) but more likely something in the software that doesn't happen often and potentially fixed in a future update.
This isn't a kind of error any user could "fix" and without knowing what sequence led to the function call being made with an uninitialized external function reference there would be no way to know how to avoid the problem. It could have been a "hardware" glitch (e.g. random bit change in an otherewise correct address) but more likely something in the software that doesn't happen often and potentially fixed in a future update.
Nov 25, 2015 11:15:22 #
tairving
Loc: Magnolia, Texas USA
[quote=Billbobboy42]Tried to start PrintShop Pro 4.0 this morning and got the following message:
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
Just for kicks, would someone please translate?
I rebooted and then Print Shop worked.
*****************************************************
Computers get confused. A bit or a byte gets corrupted and causes something else to get out of cattywhumpus; it all cascades and goes to pot. The only meaningful action is to reboot; you did just fine with that. Don't try to go any further.
Computer programmers live in a world of their own and speak their own language which is intentionally undecipherable to anyone else. But to try to answer your question:
"Exception has been thrown by the target of an invocation." Means that a program (app) has attempted to call up another program/app or subroutine (the attempted "invocation") but did so in a manner that the second one did not understand. It is not apparent which one of the two has the problem, just that there was a problem. The second program/subroutine answered with an "Exception", i.e. "I don't understand what you are asking."
"Object reference not set to an instance of an object." This says that the first program in calling (invoking) the second program, pointed to an important piece of information (the object) or at least thought it did. The second/called/invoked program looked and did not see what it thought it should see and replied something to the effect of "I did not find the object I was expected at the location at which you pointed."
Maybe the first program was corrupted and pointed to the wrong place. Or maybe the second program was corrupted and could not figure out how to interpret the information/object. Or maybe the object itself was corrupted. Even if you could sort this out and correct it, it is likely that something else also was corrupted. Don't try, just reboot.
FYI, the "object" might be something like a *.jpg image or a text document, etc.
TMI???
Bottom line - reboot.
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
Just for kicks, would someone please translate?
I rebooted and then Print Shop worked.
*****************************************************
Computers get confused. A bit or a byte gets corrupted and causes something else to get out of cattywhumpus; it all cascades and goes to pot. The only meaningful action is to reboot; you did just fine with that. Don't try to go any further.
Computer programmers live in a world of their own and speak their own language which is intentionally undecipherable to anyone else. But to try to answer your question:
"Exception has been thrown by the target of an invocation." Means that a program (app) has attempted to call up another program/app or subroutine (the attempted "invocation") but did so in a manner that the second one did not understand. It is not apparent which one of the two has the problem, just that there was a problem. The second program/subroutine answered with an "Exception", i.e. "I don't understand what you are asking."
"Object reference not set to an instance of an object." This says that the first program in calling (invoking) the second program, pointed to an important piece of information (the object) or at least thought it did. The second/called/invoked program looked and did not see what it thought it should see and replied something to the effect of "I did not find the object I was expected at the location at which you pointed."
Maybe the first program was corrupted and pointed to the wrong place. Or maybe the second program was corrupted and could not figure out how to interpret the information/object. Or maybe the object itself was corrupted. Even if you could sort this out and correct it, it is likely that something else also was corrupted. Don't try, just reboot.
FYI, the "object" might be something like a *.jpg image or a text document, etc.
TMI???
Bottom line - reboot.
Nov 25, 2015 11:19:52 #
EX = has been or was at one time
SPURT = Drip of water water under pressure.
EXPERT!!! =Has Been Drip Under Pressure
Sounds to me like you may have turned your computer on and tried to start your Print Shop Pro before all the services and bootup items were loaded.
This is a very common problem that many people encounter when they are in a hurry. When the "wheel" stops turning, that is not an idication the computer has booted to a "ready state".
There are software utilities and the operating system has utilities that allow you to prioritize the boot order and timing of your application that start automatically.
One of the things I do on every computer I encounter/work on is time the boot time until the computer is idle, or completely booted.
Problems the nature of your post occur when you open a program while the services and startup items are still loading.
Once you time your "on" until "cpu idle" state, you then know how long you must wait before using the system. It is often much greater than the time until the wheel stops turning on the screen.
To time the full boot sequence:
time this following process.
turn on the computer
As soon as you see the task bar press control-alt-delete to invoke the screen that includes task master
left click on task master
When task master comes up, start watching the CPU Usage percentage.
The system is not idle and ready to go until the percent usage for the CPU goes down to 0 or hovers near that state.
Do not use the system or move the mouse around until this state is reached.
The time will be much longer than it take for the little wheel to stop turning.
If the Idle State does not idle down ever or for a looong period, then unhook from the internet and run this test again from startup.
The time you determine to true idle CPU is the time you should allow before trying to use any programs or services, browser and such.
This will remain relatively consistent for future use, but can be run any time to check it.
This is one of the tests I teach in computer speed up classes and students find quite revealing. You can screw up your computer for many minutes if trying to use it before it's ready to go.
Furthermore, this test can be used to sort out problems with autobots and other spyware, including use of your computer as a "proxy server" by hackers.
No matter how much you spend on a maximum performance computer, the boot time is a function of how you use the computer and the software you have loaded which use "startup" items which you can see and control (somewhat) in MSCONFIG utility, part of your OS.
A computer that does not idle down has activity happening that you must track down and determine the source of it's usage. Unhooking from the internet and getting a better time on "time to idle" means something in your computer is actively contacting the internet (loose translation)
CBB is correct in suggesting a poorly written program, but if you go through all the programs on your computer looking for crappy programming that will be an endless task. No software is ever correct 100% or ever finished. Hence updates.
His explanation is good however on this inatance. Particularly the part about inconsistency of the problem and a likely future fix.
But time your computers boot time, clean up whatever needs cleaned, and foremost, keep your hands off the mouse, keyboard and screen until you know long it takes to idle down.
SPURT = Drip of water water under pressure.
EXPERT!!! =Has Been Drip Under Pressure
Sounds to me like you may have turned your computer on and tried to start your Print Shop Pro before all the services and bootup items were loaded.
This is a very common problem that many people encounter when they are in a hurry. When the "wheel" stops turning, that is not an idication the computer has booted to a "ready state".
There are software utilities and the operating system has utilities that allow you to prioritize the boot order and timing of your application that start automatically.
One of the things I do on every computer I encounter/work on is time the boot time until the computer is idle, or completely booted.
Problems the nature of your post occur when you open a program while the services and startup items are still loading.
Once you time your "on" until "cpu idle" state, you then know how long you must wait before using the system. It is often much greater than the time until the wheel stops turning on the screen.
To time the full boot sequence:
time this following process.
turn on the computer
As soon as you see the task bar press control-alt-delete to invoke the screen that includes task master
left click on task master
When task master comes up, start watching the CPU Usage percentage.
The system is not idle and ready to go until the percent usage for the CPU goes down to 0 or hovers near that state.
Do not use the system or move the mouse around until this state is reached.
The time will be much longer than it take for the little wheel to stop turning.
If the Idle State does not idle down ever or for a looong period, then unhook from the internet and run this test again from startup.
The time you determine to true idle CPU is the time you should allow before trying to use any programs or services, browser and such.
This will remain relatively consistent for future use, but can be run any time to check it.
This is one of the tests I teach in computer speed up classes and students find quite revealing. You can screw up your computer for many minutes if trying to use it before it's ready to go.
Furthermore, this test can be used to sort out problems with autobots and other spyware, including use of your computer as a "proxy server" by hackers.
No matter how much you spend on a maximum performance computer, the boot time is a function of how you use the computer and the software you have loaded which use "startup" items which you can see and control (somewhat) in MSCONFIG utility, part of your OS.
A computer that does not idle down has activity happening that you must track down and determine the source of it's usage. Unhooking from the internet and getting a better time on "time to idle" means something in your computer is actively contacting the internet (loose translation)
CBB is correct in suggesting a poorly written program, but if you go through all the programs on your computer looking for crappy programming that will be an endless task. No software is ever correct 100% or ever finished. Hence updates.
His explanation is good however on this inatance. Particularly the part about inconsistency of the problem and a likely future fix.
But time your computers boot time, clean up whatever needs cleaned, and foremost, keep your hands off the mouse, keyboard and screen until you know long it takes to idle down.
Nov 25, 2015 12:10:28 #
I'd agree with everything tairving said, with the addition that the "target of an invocation" was probably a plug-in PrintShop was trying to load.
Nov 25, 2015 15:28:06 #
Why Computers Sometimes Crash! by Dr. Seuss.
If a packet hits a pocket on a socket on a port,
and the bus is interrupted at a very last resort,
and the access of the memory makes your floppy disk abort,
then the socket packet pocket has an error to report.
If your cursor finds a menu item followed by a dash,
and the double-clicking icon puts your window in the trash,
and your data is corrupted cause the index doesn't hash,
then your situation's hopeless and your system's gonna crash!
If the label on the cable on the table at your house,
says the network is connected to the button on your mouse,
but your packets want to tunnel to another protocol,
that's repeatedly rejected by the printer down the hall......
And your screen is all distorted by the side effects of gauss,
so your icons in the window are as wavy as a souse;
then you may as well reboot and go out with a bang,
'cuz sure as I'm a poet, the sucker's gonna hang.
When the copy on your floppy's getting sloppy in the disk,
and the macro code instructions cause unwanted risk,
then you'll have to flash the BIOS and you'll want to RAM your ROM,
just quickly turn the darn thing off and run to tell your Mom!
If a packet hits a pocket on a socket on a port,
and the bus is interrupted at a very last resort,
and the access of the memory makes your floppy disk abort,
then the socket packet pocket has an error to report.
If your cursor finds a menu item followed by a dash,
and the double-clicking icon puts your window in the trash,
and your data is corrupted cause the index doesn't hash,
then your situation's hopeless and your system's gonna crash!
If the label on the cable on the table at your house,
says the network is connected to the button on your mouse,
but your packets want to tunnel to another protocol,
that's repeatedly rejected by the printer down the hall......
And your screen is all distorted by the side effects of gauss,
so your icons in the window are as wavy as a souse;
then you may as well reboot and go out with a bang,
'cuz sure as I'm a poet, the sucker's gonna hang.
When the copy on your floppy's getting sloppy in the disk,
and the macro code instructions cause unwanted risk,
then you'll have to flash the BIOS and you'll want to RAM your ROM,
just quickly turn the darn thing off and run to tell your Mom!
Nov 26, 2015 06:26:11 #
n3eg wrote:
Why Computers Sometimes Crash! by Dr. Seuss.
Mom!
Mom!
I really like this. Sending it to my team.
As for the answer to this post.
Get 4 years of college getting an AAS and BS in Data Processing and Computer Science. Work through the 80's 6-7 days a week, 10-15 hour days building the foundation for the computer systems people take for granted and the newbies of today frown on. Spent countless hours reading through MVS System dumps that are 2-3-5 feet thick looking for this exact problem which could be just one byte. Go to a lot of classes over your 40 years. Keep up with technology and stay ahead of the pack. Otherwise you end up a relic, forced retired or moved to some Midwestern state to spend the rest of you life babysitting your system till one day they find you redundant or out dated and when you have nothing left cause you gave it all to your system. they dump you for some COTTs software. Never rest, never sleep because problems keep you up a night and AMAZING answers come to you when everyone else is sleeping. You get excited and run to your computer at 3AM and proceed to put in one of those 15 hour days. Your family lets you be, but never understands why you spend so many hours in front of the computer. And most of all, be that one person, who bursts into the room full of CEO's to announce you solved the production problem keeping the system down on Black Friday.
Then I will tell you, you will not understand, in the end, I certainly will have to kill you unless you have a previously signed NDA.
Heroes don't always carry guns, they work silently keeping things moving.
A long time ago in the land of $700 dollar three piece suits (expensive at that time), Long hours both in the office and at the Downtown NYC bars drinking ourselves into appreciation. I was in a bar, and this absolutely hot girl next to me, trying to pick me up, asked me what I did for a living. So being young in my career and excited about it, I told her. Remember the scene from 'Airplane' Where everyone was killing themselves after the guy said "I have a drinking problem" and then proceeded with his story. Being an analyst I figured out what I did wrong and have never since told ANYONE what I do to make a living. Like my kids say. "I work with computers." Take care.
Nov 26, 2015 06:49:03 #
Thanks, all, for making this perfectly clear. Also, great poem.😁
Nov 26, 2015 08:17:56 #
Billbobboy42 wrote:
Tried to start PrintShop Pro 4.0 this morning and got the following message:
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
Someone at PrintShop has a sense of humor.
Nov 26, 2015 08:50:03 #
I certainly agree with kuzano. I use wise care 365 as one of my programs to check for errors and malware. It has a section that comes up after the computer is ready to tell me how long it took to come up, along with an appropriate icon, snail, bike, car, helicopter and jet plane. The last is for my SSD of course.
Nov 26, 2015 09:24:03 #
Billbobboy42 wrote:
Tried to start PrintShop Pro 4.0 this morning and got the following message:
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
Just for kicks, would someone please translate?
I rebooted and then Print Shop worked.
It's been my experience that few computer error messages offer any insight for the average user to fix a problem.
"Exception has been thrown by the target of an invocation. Object reference not set to an instance of an object."
Just for kicks, would someone please translate?
I rebooted and then Print Shop worked.
It's been my experience that few computer error messages offer any insight for the average user to fix a problem.
In many cases where a reboot fixes the problem, it was a resource problem. In this case the resource was ram (memory). Even though you have plenty of ram, opening and closing programs can fragment memory because of bugs in the programs. For example, you start with 4 gig and your program uses 100 meg, and each time the program is closed, it doesn't give all the memory back and leaves a chunk in use. Next time in there is a smaller contiguous block of memory to load. Eventually there are little chunks all over the place and weird things happen. A reboot cleans this mess up.
If you want to reply, then register here. Registration is free and your account is created instantly, so you can post right away.