Corrupt WIA (WINDOWS IMAGE ACQUISITION)

[Guest Stockmoose16]

Hello,

 

I installed Windows XP PRO sp 2 on my computer a few months ago.

During the install, the computer kept hanging on the WIA (windows

Image Acquisition) drivers. I eventually skipped those files, hoping

they wouldn't be too important. Unfortunately, I just purchased a

digital camera that requires WIA to run properly

 

To rectify the problem, I borrowed a friend's XP sp 2 disc, hoping it

would be more reliable than my disc. I performed a repair install,

but when the computer rebooted, WIA was still missing from the

system. When I go into "services" and double-click on WIA, I get the

message, "Unable to open service Windows Image Acquisition (WIA) for

reading on local computer. Error 123: The filename, directory name,

or volume label syntax is incorrect."

 

How do I fix this problem and why didn't the repair install fix the

issue?

[Guest Gerry]

Re: Corrupt WIA (WINDOWS IMAGE ACQUISITION)

 

Please post copies of all Error and Warning Reports appearing in the

System and Application logs in Event Viewer relating to the last boot in

normal mode . No Information Reports or Duplicates please. Indicate

which also appear in a previous boot.

 

You can access Event Viewer by selecting Start, Control Panel,

Administrative Tools, and Event Viewer. When researching the meaning

of the error, information regarding Event ID, Source and Description

are important.

 

A tip for posting copies of Error Reports! Run Event Viewer and double

click on the error you want to copy. In the window, which appears is a

button resembling two pages. Click the button and close Event

Viewer.Now start your message (email) and do a paste into the body of

the message. Make sure this is the first paste after exiting from

Event Viewer.

 

--

 

 

 

Hope this helps.

 

Gerry

~~~~

FCA

Stourport, England

Enquire, plan and execute

~~~~~~~~~~~~~~~~~~~

Stockmoose16 wrote:

> Hello,

>

> I installed Windows XP PRO sp 2 on my computer a few months ago.

> During the install, the computer kept hanging on the WIA (windows

> Image Acquisition) drivers. I eventually skipped those files, hoping

> they wouldn't be too important. Unfortunately, I just purchased a

> digital camera that requires WIA to run properly

>

> To rectify the problem, I borrowed a friend's XP sp 2 disc, hoping it

> would be more reliable than my disc. I performed a repair install,

> but when the computer rebooted, WIA was still missing from the

> system. When I go into "services" and double-click on WIA, I get the

> message, "Unable to open service Windows Image Acquisition (WIA) for

> reading on local computer. Error 123: The filename, directory name,

> or volume label syntax is incorrect."

>

> How do I fix this problem and why didn't the repair install fix the

> issue?

[Guest Stockmoose16]

Re: Corrupt WIA (WINDOWS IMAGE ACQUISITION)

 

Here are the error reports... just as I suspected, WIA doesn't look to be

installed on the computer or in the registry, even though I performed a

repair install. How do I fix the problem?

 

Event Type: Error

Event Source: Service Control Manager

Event Category: None

Event ID: 7003

Date: 8/17/2008

Time: 11:52:24 PM

User: N/A

Computer: CMONEYDESKTOP

Description:

The Canon Camera Access Library 8 service depends on the following

nonexistent service: stisvc

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

------------

 

Event Type: Warning

Event Source: EventSystem

Event Category: (54)

Event ID: 4353

Date: 8/17/2008

Time: 11:44:56 PM

User: N/A

Computer: CMONEYDESKTOP

Description:

The COM+ Event System attempted to fire the

EventObjectChange::ChangedSubscription event but received a bad return code.

HRESULT was 80040201.

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

--------------------

Event Type: Warning

Event Source: EventSystem

Event Category: (52)

Event ID: 4356

Date: 8/17/2008

Time: 11:44:55 PM

User: N/A

Computer: CMONEYDESKTOP

Description:

The COM+ Event System failed to create an instance of the subscriber

partition:{41E90F3E-56C1-4633-81C3-6E8BAC8BDD70}!new:{D3938AB0-5B9D-11D1-8DD2-00AA004ABD5E}. CoGetObject returned HRESULT 80070422.

 

For more information, see Help and Support Center at

http://go.microsoft.com/fwlink/events.asp.

 

 

"Gerry" wrote:

> Please post copies of all Error and Warning Reports appearing in the

> System and Application logs in Event Viewer relating to the last boot in

> normal mode . No Information Reports or Duplicates please. Indicate

> which also appear in a previous boot.

>

> You can access Event Viewer by selecting Start, Control Panel,

> Administrative Tools, and Event Viewer. When researching the meaning

> of the error, information regarding Event ID, Source and Description

> are important.

>

> A tip for posting copies of Error Reports! Run Event Viewer and double

> click on the error you want to copy. In the window, which appears is a

> button resembling two pages. Click the button and close Event

> Viewer.Now start your message (email) and do a paste into the body of

> the message. Make sure this is the first paste after exiting from

> Event Viewer.

>

> --

>

>

>

> Hope this helps.

>

> Gerry

> ~~~~

> FCA

> Stourport, England

> Enquire, plan and execute

> ~~~~~~~~~~~~~~~~~~~

> Stockmoose16 wrote:

> > Hello,

> >

> > I installed Windows XP PRO sp 2 on my computer a few months ago.

> > During the install, the computer kept hanging on the WIA (windows

> > Image Acquisition) drivers. I eventually skipped those files, hoping

> > they wouldn't be too important. Unfortunately, I just purchased a

> > digital camera that requires WIA to run properly

> >

> > To rectify the problem, I borrowed a friend's XP sp 2 disc, hoping it

> > would be more reliable than my disc. I performed a repair install,

> > but when the computer rebooted, WIA was still missing from the

> > system. When I go into "services" and double-click on WIA, I get the

> > message, "Unable to open service Windows Image Acquisition (WIA) for

> > reading on local computer. Error 123: The filename, directory name,

> > or volume label syntax is incorrect."

> >

> > How do I fix this problem and why didn't the repair install fix the

> > issue?

>

>

>

[Guest Plato]

Re: Corrupt WIA (WINDOWS IMAGE ACQUISITION)

 

=?Utf-8?B?U3RvY2ttb29zZTE2?= wrote:

>

> How do I fix this problem and why didn't the repair install fix the

> issue?

 

Repair install doesn't fix or address hardware compatiabilty problems.

 

--

http://www.bootdisk.com/

[Guest Stockmoose16]

Re: Corrupt WIA (WINDOWS IMAGE ACQUISITION)

 

 

Then how do I fix it? And it's not a hardware compatibility issue, it's

that the service, WIA, was never installed during the initial installation of

Windows.

"Plato" wrote:

> =?Utf-8?B?U3RvY2ttb29zZTE2?= wrote:

> >

> > How do I fix this problem and why didn't the repair install fix the

> > issue?

>

> Repair install doesn't fix or address hardware compatiabilty problems.

>

> --

> http://www.bootdisk.com/

>

[Guest Monitor]

Re: Corrupt WIA (WINDOWS IMAGE ACQUISITION)

 

 

"Plato" <|@|.|> wrote in message

news:48acad05$0$30937$bb4e3ad8@newscene.com...

> =?Utf-8?B?U3RvY2ttb29zZTE2?= wrote:

> >

> > How do I fix this problem and why didn't the repair install fix the

> > issue?

>

> Repair install doesn't fix or address hardware compatiabilty problems.

>

 

"compatiability"? "Compatibility"? A spelling checker is a wonderful

invention, especially when churning out newsgroup replies by the dozen.

[Guest Stockmoose16]

Re: Corrupt WIA (WINDOWS IMAGE ACQUISITION)

 

On Aug 20, 5:04 pm, Stockmoose16

<Stockmoos...@discussions.microsoft.com> wrote:

> Then how do I fix it?  And it's not a hardware compatibility issue, it's

> that the service,WIA, was never installed during the initial installation of

> Windows.

>

> "Plato" wrote:

> > =?Utf-8?B?U3RvY2ttb29zZTE2?= wrote:

>

> > > How do I fix this problem and why didn't the repair install fix the

> > > issue?

>

> > Repair install doesn't fix or address hardware compatiabilty problems.

>

> > --

> >http://www.bootdisk.com/

 

BUMP!!