[Termie]

Been having a problem with my WIA service, which hung on starting a few days ago. Ever since, it has been terminating unexpectedly, won't run at all when I try to start it, gives me Error 1067... I don't know how to fix this. I suspect that my picture viewer and Paint have some sort of relation to it, because when I try to use them, it takes forever to generate a picture preview in my folder, and to open up a GIF pic in Paint-or just open up Paint, period, takes even longer... I do use these frequently, so it's a pain having to wait, and wait, and wait...

This isn't the first time it's happened, as I had this same problem a month or two ago, but then it seemed to resolve itself. I'm just curious to find out what could cause this type of behavior and what I can do to fix it, other than just doing a system restore... Thanks!

Oh...I'm using Windows XP Prof.

[Advertisements]

Termie, look in Event Viewer, see if there are any errors posted there that will help identify what is causing this. Post the results here please.

You can access Event Viewer via WinKey+r, type eventvwr.msc and press Enter.

[Ztruker]

Termie, look in Event Viewer, see if there are any errors posted there that will help identify what is causing this. Post the results here please.

You can access Event Viewer via WinKey+r, type eventvwr.msc and press Enter.

[Termie]

Well, the first instance of anything happening with WIA, as noted in the Event Viewer, was that it hung on starting (Event ID 7022) when I booted the computer. Then 20 seconds later, it "terminated unexpectedly" (Event ID 7034). Another 20 seconds later, it was successfully sent a start control, but after 12 seconds, it terminated unexpectedly again, and this is pretty much the pattern it's been following ever since, the system sends the start control and it just keeps terminating like this over and over. Mixed in between-and I have no idea whether this information is connected to this issue or not, but it has been appearing with the same frequency, is that "The server {A1F4E726-8CF1-11D1-BF92-0060081ED811} did not register with DCOM within the required timeout." Every time I boot the computer, WIA hangs on starting, terminates, the system sends start control, it terminates, etc. and the cycle repeats itself over and over.

I hope this info gives you something-to me it's all Greek. Thanks for your help!! I greatly appreciate it.

[Ztruker]

That definitely helps. I searched on imapi Event ID 7034 and got quite a few hits. This one on Experts Exchange sounds like a good candidate. You don't have to register, just keep scrolling down and eventually you'll get to the initial post and the responses.

http://www.experts-e...Q_20873815.html

In this case, disabling Messenger Service resolved the problem, but you need to work through the process to identify the common denominator as described by gemarti. Read through it and if you have any questions post back and I (or one of the real experts) will try to help.

[Termie]

Thanks a bunch Z! I've already had Messenger disabled, but I will definitely go through the link you've provided and see if I can't come up with something. Thanks so much for your help!

[Termie]

Well dookie...I could have sworn that the page you linked me to showed up with the comments the other day, but this morning it just shows the original question and then a bunch of repeated "you must be a premium member to view these comments" with the option of either signing up or logging in I see that it gives you a 7-day free trial with a monthly subscription, but have the suspicion that if I chose to do that, it would want my credit card info from me regardless...something I don't really care to do at this point. Could you possibly copy the comment from gemarti that you referred to above, or would that be a no-no? I did a Google search on the imapi Event ID 7034 and I'm going through those, but so far no luck.

[Ztruker]

Termie, you need to scroll way, way down to get to the posts. Probably faster to do a Ctrl+End then scroll up

[Termie]

They must have a magic "shut me off" feature to this website, because I was able to access the posts as you described, clicked on a link within one of them, tried to return...and got the same crapola. Luckily, I was on to their game (the heads up from the day before) and was able to copy/paste the information into a Word doc ahead of time...hehehe

Anyway...okay....as far as I can see....there is no "common denominator." I queried all services in command prompt (sc query) and all are running. Or at least it shows the only ones that ARE running...it doesn't show the status of stisvc. When I query stisvc, it comes back with "stopped" (gee, ya think?) and "interrogate" the stisvc tells me that "ControlService failed 1062." I Googled this code, found a really nifty listing of all Win32 Error codes, and 1062 says: 1062 The service has not been started. ERROR_SERVICE_NOT_ACTIVE (Gee. YA THINK?) Grrr.

I've also checked through Services to see if any of the services that WIA might be dependent on are not active, but the only one is RPC, and that's started and has no problem.

An aside...

As I figured would happen, when I tried to upload some images from my digital camera to my computer today, the computer saw the camera, gave it the correct name, told me all was good to go, but I couldn't access the pictures. I use Nikon Picture Project to upload and that program could not detect the camera at all, even though the computer had. Go figure.

<sigh> I'm afraid this is above my head. Over my head. I'm getting a headache. (Insert the smilie beating head against brick wall here.) Can't I just copy some file or driver from my XP disk and be done with it?

[Ztruker]

Well, you can do a Repair Install. Read here:

How to do a Repair Install

[Termie]

Well, after doing a risks versus benefits comparison (the risks outweighing the benefits here, I believe) I decided to just wait it out. It fixed itself before, maybe it will do it again. If not, then I'll do a more drastic measure, I guess, and backup all of my personal files and do a reformat/reinstall. I've already tried a Restore, and it told me that it couldn't do that, so as far as I know, a reinstall is pretty much all I have left to use.

I hate computers. LOL

Thanks so much for your help. I do appreciate it....a LOT.

Edited by Termie, 08 January 2008 - 05:42 PM.

[Termie]

Adding this update for your info!!

I decided to hunt down more information on the problem I was having. I admit that this had me irritated and a bit worried, combined with the fact that now, after having tried to upload pics from my camera, every time I tried to access My Computer, the window would go blank and the system would have to search for itself. GAH!! I went to Dell's website to see what drivers it recommended, and it came up with quite a few. Unfortunately, some of them were confusing....such as the BIOS update it listed for my system actually had the name of another system (I have an XPS 410, this update had it specified for a Dell Dimension) so I got on the phone and called Dell to see if this BIOS, amongst the others, actually applied to my system as well. While I had the guy on the phone, I also brought the problems I had been having into the conversation. I explained to him that WIA was not able to start, terminating repeatedly, etc., and that I could not upload pics from my camera. He went to look for new software for my camera. His other solution was for me to switch my USB
connection from the front to the back, saying that the back was "more powerful" or something like that. Well sure, as soon as I switched, the system recognized the connection, named the camera and he assumed all was well, even though when I tried to use this new updated software, it still told me there was no camera detected, and I knew it had to be WIA. When I unplugged the camera and tried again, it didn't see it again. Then he suggested a system restore, which I had already tried and failed with, and then said I would have to do a recovery... and that is where he left me.

I did some more exploring and ran across an old post at another site from 2004 which described, to a T, the problems I was having, right down to My Computer searching. Turns out that it had to do with the printer software/driver, so I went to HP's website to see if there were new drivers there. After checking my printer driver date and comparing it to the newest driver on the site, turned out it was about a year older, so I downloaded that. In the meantime, I did a crossover connection to my work computer and started backing up my important stuff to that computer, just in case. (I used a crossover because I figured if I was having problems with my USBs, then it would be insane to try to use the My Book external drive I had. I also happened to notice that if I only had my XPS system on, it would not power my KVM switch and enable me to switch over and power up the other system, so I was pretty sure my USBs were screwed that way...)

I am happy to announce that the installation of this newer printer driver (well, it's actually a complete software package, not just the driver) fixed ALL of the problems I had been having. My Computer no longer seeks to find itself. Paint fires up immediately, all of my picture thumbnails have their automatic preview back, and I connected my camera (IN FRONT!) and uploaded the test shot I had taken, my Adobe Photoshop immediately started on turning on the camera as it should be...and all is right in my computing world once again.

This leaves me with one hanging question though...should I trust this guy from Dell, who told me that YES, the BIOS update on the website, which specifies a Dimension product, would apply to my XPS as well? I have to admit that this experience has left me very skeptical of their so-called "expertise" and I probably won't ever call a Dell "specialist/expert" again, considering the only other alternative they give you is to do a system recovery once their shot in the dark fails. The email he promised to send me so that I had a way to recontact him if I had further problems never showed up either...so I got the impression that they don't really give a flying leap once they get off the phone.

Sorry to ramble about it. Hopefully this will help someone else down the line...

Edited by Termie, 11 January 2008 - 10:18 AM.

[happyrock]

This leaves me with one hanging question though...should I trust this guy from Dell, who told me that YES, the BIOS update on the website, which specifies a Dimension product, would apply to my XPS as well? I have to admit that this experience has left me very skeptical of their so-called "expertise"

this falls in the category of...If its not broke...don't fix it...OR let sleeping dogs lie...

[Ztruker]

Excellent bit of determined sleuthing, and thanks for posting back with how you fixed. For the record, what HP printer was it?

Re: The BIOS update, I agree with Happyrck, I would definitely NOT install it.

[Termie]

It's an HP 7410 (All-in-one). I wish I could find the site that I had found previously to give more information about what the situation there was, but I can't remember exactly what I put in for my Google search string-I know it must have been one of the event ID numbers or the DCOM error info.

Anyway...the printer mentioned there wasn't a 7410, but it was an HP (PSC? PCS?)...and there was some kind of problem between WIA and TWAIN, there was a remark made about HP not giving the option of TWAIN and leaving WIA out of it, or something to that effect. That is what got me to thinking about searching for an updated driver...instead, I used the new software package I found, figured it would cover all bases there. I am assuming that the HP software I had been using, installed from the original disk that came with it, did not detect this software update. I guess you can't rely solely on your programs to update themselves with the stuff they need, because obviously it doesn't always happen, even though it LOOKS like they are. Since installing the new software, and getting things back to operating the way they should, everything has come back on board, including my KVM power. I imagine that plugging the camera into the USB port must have caused some kind of conflict for the system based off of WIA, which is why it had to go searching for itself every time I tried to access My Computer...that's just a guess, but to me it kinda makes sense. The original poster had the same problem, as well, with My Computer. I had a feeling the two problems were linked somehow.

As an aside...just because it's got something to do with HP....
Interestingly, when I booted up my other computer (an older model HP, a450n) yesterday morning, AVG detected a Trojan called AutoTbar.exe. Googling that told me it was an HP view toolbar. Seemed harmless enough, but nonetheless, I had it quarantined. This computer is running on the older software-I'll update that when I'm able, but no hurry since there hasn't been any problem with that one aside from this detection.