HP1536 scan failure - WIA error

We have problems with HP LaserJet 1536dnf scanner.
Up to 2 days ago, print and scan works great.
Now, print is working, but scan does not.
Running HP scan doctor, we got error with WIA.
We have tested the same Printer in a different PC, and both print and scan works.
Attempts to solve:
- use usb instead of network: not working;
- firmware update;
- uninstall & reinstall HP software, both full and basic, several times;
- uninstall antivirus (SEP);
- disabled windows firewall;
- reinstall .net framework;
- created new windows user profile;
- wia, rpc and shell hardware detection services in automatic mode;
- sfc /scannow: no errors;
Trying another software (Vuescan), scan work.
Any suggestion?

Hi @Sartoretto,
Welcome to the HP Forums!
I understand that you can print but not scan with your HP Laserjet pro 1536dnf printer on Windows 7. I am sorry to hear this, but happy to help you with your scanning issue!
Thank you for the break down of what you have done already, I appreciate it!
It is possible that the (Vuescan) software is not using the Wia interface, which could explain why it works, and the other software does not.
Please see this guide, How to Scan: Windows 7. Select How to scan without HP software, select How to scan with Paint, and let me know if it works or not. This will test the Wia interface directly from the Operating System.
Once I know what happens, I will look into this further for you!
RnRMusicMan
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to say “Thanks” for helping!

Similar Messages

Hp laserjet pro cm1415fnw won't scan WIA error.

We just got a hp laserjet pro cm1415fnw, it manages to print, but unfortunately it won't scan. We set it up to be wireless since it will be used by various users. When I run the HP printer and scan dr. it says that there's a WIA error. I tried uninstallin and reinstalling all the drivers and software, as the HPPSdr reccommended, nothing happened. I went into the forums and checked the services that needed to be running in order for the scan to work. All the services were up, but still it won't scan. I'm running out of options here with this device. If anyone could please give me some advice on how to fix the scanning issue I will be extremely grateful.
This question was solved.
View Solution.

Hi @sil89,
I understand that you are unable to scan, but you can print over the wireless network. I can help you.
Can you scan from any of the other networked computers?
Are you signed is a the Administrator of that computer?
WIA drivers are part of Windows Operating System.
Run this Microsoft Fit It Tool to see if it will resolve this issue.
Diagnose and repair Windows File and Folder Problems automatically.
I have provided this document, just to make sure these are the same ones you had checked.
This document is to Check the Windows Image Acquisition (WIA) services.
Windows: HP Scan Software Does Not Open or Scan on a Printer Using a USB Connection.
Disregard the title.
Go to Solution three: Check the Windows Image Acquisition (WIA) services.
Temporarily turn of the Antivirus Software and try scanning again.
If the issue persists, download and try to repair the WIA drivers. If you don't feel comfortable about doing these steps, you can contact the computer manufacturer or Microsoft to resolve this WIA error.
Back up the registry first.
How to back up and restore the registry in Windows.
Restore Default Startup Type for Windows Image Acquisition (WIA).
Please let me know the results.
Thank You.
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Gemini02
I work on behalf of HP

Word couldn't send mail because of MAPI failure, Unspecified error.

This issue is crossposted in Microsoft Answers Word and OUTLOOK. I am posting here in hopes that someone at Mircrosoft may have a solution or at least elevate the issue to someone who does.
http://answers.microsoft.com/en-us/office/forum/officeversion_other-word/word-could-not-send-mail-because-of-mapi-failure/f62678fe-ef1d-42b5-8cfe-1e43d6a1d609
http://answers.microsoft.com/en-us/office/forum/office_2013_release-outlook/word-couldnt-send-mail-due-to-mapi-failure/1f03cf74-9258-411b-9e2b-e41cb5006d71
I dabble with VBA and write and maintain several amateur Word Add-Ins. Accordingly, I have Word 2003, 2007, 2010 and 2013 installed on my PC. They get along fine. However, I am unable to "Share" or "Send" an open Word
document as an E-mail attachment in any version! In each case Word returns an error mesage "Word couldn't send mail because of a MAPI failure, Unspecified error (the same issue occurs with Excel and Powerpoint except the error dialog is a bit different.)
Using Word 2003, I (CAN) "Send to (Mail recipient for review)" in which case OUTLOOK is opened with the document as an attachment. I can also "Send to Mail Recipient" from Windows Explorer, in which case the Word file is attached to
an OUTLOOK message, and I can create an instance of OUTLOOK and send mail from Word using VBA.
I have repaired all Office versions. I have removed the registry keys for all office versions and repaired all versions again. I have run "fixmapi" until I am blue in the face. I have renamed the MAPI32.DLL files and ran sfc \scannow
to ensure that the MAPI32.DLL file is not corrupt. In view of these actions and in view of what I can do, something tells me that the MAPI files are fine.
So what is this "Unspecified error?" This problem is rife on the internet and most of the "canned" solutions have been marked "Answered" by some MS support engineer. These "canned" solutions might have
fixed the issue at one point, but they don't work now. At least not for me.
Thanks.
Greg Maxey Please visit my website at: http://gregmaxey.mvps.org/word_tips.htm

Hello Greg,
I noted that there are 2 knowledge articles that describe scenarios where you may encounter this error.
KB 291152 You receive a "Word couldn't send mail because of MAPI failure" error message when you try to send a Word document as an e-mail attachment in Word 2002
http://support.microsoft.com/kb/291152/EN-US
KB 929362 You cannot send a file by clicking Send in a different program when Outlook 2007 is running as administrator
http://support.microsoft.com/kb/929362/EN-US
Please let me know the following:
1. What version of Outlook are you using?
2. Do you have Outlook open when you attempt the File > Share > Email as attachment from Word? If not, does the error occur if you open Outlook, open Word and then try to send the email?
3. If you close/reopen Word and then try the send again, do you get the same error?
4. Are you running either Outlook or Word in an elevated mode?
5. What happens if you start both Outlook and Word as "Run As Administrator". You may have to right-click each applications' .exe file to be able to choose the "Run As Administrator" option.
6. Do you get the same error when using File > Share > Email as attachment using Excel?
7. In Internet Explorer, open the Internet Options. On the General tab within the browsing history, delete your temporary Internet files and website files
8. Does the issue occur in selective startup mode?
Steps to setup selective startup mode:
Click on the Windows Start button, in the Search box type msconfig and then hit enter. This should open up the System Configuration Utility. Make the following adjustments within each tab.
Services Tab:
- Check the option 'Hide All Microsoft Services'
- Click on button 'Disable All'
Startup Tab:
- Click the button 'Disable All'
- Go back through the list and enable any Microsoft items
Click Ok. It will say “You must restart your computer for some of the changes
made by System Configuration to take effect”. Hit the ‘Restart’ button.
When the PC reboots try to run your test again.
To return back to a normal boot launch msconfig again and choose 'normal startup' on the general tab, click Ok and then reboot the PC.
Regards,
Dennis

SQL Server 2012 installation failure An error occurred for a dependency of the feature causing the setup process for the feature to fail.

I am installing SQL Server 2012 Developer (from ISO image written on DVD), my machine has Windows 7 (Edit: Windows 7 with service pack 1) on it. This machine already has SQL Express and SQL 2008 R2 Express installed in it.
On running 2012 setup it goes fine from Setup Support Rules to Installation Progress. In Installation Progress after some progress installation fails.
Windows show the following components couldn't installed:
Managment Tools Complete Failed. Client Tools Connectivity Failed. Client Tools SDK Failed. Client Tools Backwards Compantibility Failed. Managment Tools Basic Failed. SQL Server Data Tools Failed. Reporting Services -Native Failed. Database Engine
Services Failed. Data Quality Services Failed. full-Text and Semantic Extractins for Search Failed. SQL Server Replication Failed. Integration Services Failed. Analysis Services Failed. SQL Client Connectivity SDK Failed.
In detail for failure of every component it provide these details:
Action required:
Use the following information to resolve the error, and then try the setup process again.
Feature failure reason:
An error occurred for a dependency of the feature causing the setup process for the feature to fail.
In summary log file it provide the following details:
Overall summary:
Final result:                  Failed: see details below
Exit code (Decimal):           -2068643839
Start time:                    2012-07-31 16:23:37
End time:                      2012-07-31 16:33:32
Requested action:              Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for Adv_SSMS:        Use the following information to resolve the error, and then try the setup process again.
Next step for Conn:            Use the following information to resolve the error, and then try the setup process again.
Next step for SDK:             Use the following information to resolve the error, and then try the setup process again.
Next step for BC:              Use the following information to resolve the error, and then try the setup process again.
Next step for SSMS:            Use the following information to resolve the error, and then try the setup process again.
Next step for BIDS:            Use the following information to resolve the error, and then try the setup process again.
Next step for RS:              Use the following information to resolve the error, and then try the setup process again.
Next step for SQLEngine:       Use the following information to resolve the error, and then try the setup process again.
Next step for DQ:              Use the following information to resolve the error, and then try the setup process again.
Next step for FullText:        Use the following information to resolve the error, and then try the setup process again.
Next step for Replication:     Use the following information to resolve the error, and then try the setup process again.
Next step for IS:              Use the following information to resolve the error, and then try the setup process again.
Next step for AS:              Use the following information to resolve the error, and then try the setup process again.
Next step for SNAC_SDK:        Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name:                  Haansi-PC
Machine processor count:       4
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
SQL Server 2005      SQLEXPRESS           MSSQL.1
Database Engine Services                 1033                 Express Edition
9.4.5000        No
SQL Server 2005      SQLEXPRESS           MSSQL.1
SQL Server Replication                   1033                 Express Edition
9.4.5000        No
SQL Server 2005      SQLEXPRESS           MSSQL.1
SharedTools                              1033
Express Edition      9.4.5000        No
SQL Server 2005
Tools                                    1033
Express Edition      9.4.5000        No
SQL Server 2005
ToolsClient                              1033
Express Edition      9.4.5000        No
SQL Server 2005
ToolsClient\Connectivity                 1033                 Express Edition
9.4.5000        No
SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    Database Engine Services                 1033
Express Edition      10.50.1617.0    No
SQL Server 2008 R2   SQLSERVER08EXPR2     MSSQL10_50.SQLSERVER08EXPR2    SQL Server Replication                   1033
Express Edition      10.50.1617.0    No
SQL Server 2008 R2
Management Tools - Basic                 1033                 Express Edition
10.50.1617.0    No
SQL Server 2012
LocalDB                                  1033
Express Edition      11.0.2318.0     No
SQL Server 2012
Reporting Services - SharePoint
11.0.2100.60    No
Package properties:
Description:                   Microsoft SQL Server 2012
ProductName:                   SQL Server 2012
Type:                          RTM
Version:                       11
SPLevel:                       0
Installation location:         F:\x64\setup\
Installation edition:          Developer
Product Update Status:
None discovered.
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      false
AGTSVCACCOUNT:                 NT Service\SQLAgent$SS2012
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Config
ASDATADIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Data
ASLOGDIR:                      C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Log
ASPROVIDERMSOLAP:              1
ASSERVERMODE:                  TABULAR
ASSVCACCOUNT:                  NT Service\MSOLAP$SS2012
ASSVCPASSWORD:                 <empty>
ASSVCSTARTUPTYPE:              Manual
ASSYSADMINACCOUNTS:            PC\Haansi
ASTEMPDIR:                     C:\Program Files\Microsoft SQL Server\MSAS11.SS2012\OLAP\Temp
BROWSERSVCSTARTUPTYPE:         Automatic
CLTCTLRNAME:                   <empty>
CLTRESULTDIR:                  <empty>
CLTSTARTUPTYPE:                0
CLTSVCACCOUNT:                 <empty>
CLTSVCPASSWORD:                <empty>
CLTWORKINGDIR:                 <empty>
COMMFABRICENCRYPTION:          0
COMMFABRICNETWORKLEVEL:        0
COMMFABRICPORT:                0
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
CTLRSTARTUPTYPE:               0
CTLRSVCACCOUNT:                <empty>
CTLRSVCPASSWORD:               <empty>
CTLRUSERS:                     <empty>
ENABLERANU:                    false
ENU:                           true
ERRORREPORTING:                false
FEATURES:                      SQLENGINE, REPLICATION, FULLTEXT, DQ, AS, RS, BIDS, CONN, IS, BC, SDK, SSMS, ADV_SSMS, SNAC_SDK
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  NT Service\MSSQLFDLauncher$SS2012
FTSVCPASSWORD:                 <empty>
HELP:                          false
INDICATEPROGRESS:              false
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    SS2012
INSTANCENAME:                  SS2012
ISSVCACCOUNT:                  NT Service\MsDtsServer110
ISSVCPASSWORD:                 <empty>
ISSVCSTARTUPTYPE:              Automatic
MATRIXCMBRICKCOMMPORT:         0
MATRIXCMSERVERNAME:            <empty>
MATRIXNAME:                    <empty>
NPENABLED:                     0
PID:                           *****
QUIET:                         false
QUIETSIMPLE:                   false
ROLE:                          <empty>
RSINSTALLMODE:                 DefaultNativeMode
RSSHPINSTALLMODE:              DefaultSharePointMode
RSSVCACCOUNT:                  NT Service\ReportServer$SS2012
RSSVCPASSWORD:                 <empty>
RSSVCSTARTUPTYPE:              Manual
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT Service\MSSQL$SS2012
SQLSVCPASSWORD:                <empty>
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           Haansi-PC\Haansi
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  false
TCPENABLED:                    0
UIMODE:                        Normal
UpdateEnabled:                 true
UpdateSource:                  MU
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\ConfigurationFile.ini
Detailed results:
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Client Tools SDK
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       SQL Server Data Tools
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Reporting Services - Native
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Data Quality Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Integration Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       Analysis Services
Status:                        Failed: see logs for details
Reason for failure:            An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Feature:                       SQL Client Connectivity SDK
Status:                        Failed: see logs for details
Reason for failure:            An error occurred during the setup process of the feature.
Next Step:                     Use the following information to resolve the error, and then try the setup process again.
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20120731_161013\SystemConfigurationCheck_Report.htm

Please help.
I did what you suggested, but, still got error message to install SQL server data tools: Here is the log.
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068037632
Start time: 2014-09-29 15:05:38
End time: 2014-09-29 15:15:55
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SSDTBI_VS2012: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: MSBI
Machine processor count: 4
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 32 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered Configured
SQL Server 2008 Management Tools - Basic
1033 Express Edition 10.0.1600.22 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Database Engine Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER SQL Server Replication 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Full-Text and Semantic Extractions for Search 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSSQL11.MSSQLSERVER Data Quality Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSAS11.MSSQLSERVER Analysis Services 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 MSSQLSERVER MSRS11.MSSQLSERVER Reporting Services - Native 1033
Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Basic
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Management Tools - Complete
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Connectivity
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools Backwards Compatibility
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Client Tools SDK
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 SQL Server Data Tools
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Integration Services
1033 Enterprise Evaluation Edition 11.0.2100.60 No Yes
SQL Server 2012 Reporting Services - SharePoint
11.0.2100.60 No Yes
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: C:\9f7a58aa5d6d76ffe6be968a4ad339f5\x86\setup\
Installation edition: Express
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x86
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x86
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: true
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE:
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: true
FEATURES: SSDTBI_VS2012, SNAC_SDK
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTANCEID: <empty>
INSTANCENAME: <empty>
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: AllFeatures_WithDefaults
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: <empty>
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: true
TCPENABLED: 0
UIMODE: AutoAdvance
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\ConfigurationFile.ini
Detailed results:
Feature: SQL Server Data Tools - Business Intelligence for Visual Studio 2012
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: Microsoft Visual Studio Tools for Applications 2012
Component error code: 0x80044000
Component log file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\VSTA2012_LangsSupport_Cpu32_1.log
Error description: VS Shell 2012 installation has failed with exit code -2147205120.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3436.0&EvtType=VSTA2012_LangsSupport%40Install%400x-2147205120
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files (x86)\Microsoft SQL Server\110\Setup Bootstrap\Log\20140929_150412\SystemConfigurationCheck_Report.htm

Ipod scan and fix error

I have A 160 gb ipod classic and am using windows 8, I plugged it in this morning and got the "scan and fix" error message and accidentally clicked it and it erased all 5,600 songs I have on ipod. when I go to summary it still shows all the space is still taken up but instead of music files, they're "other" is there a way to fix this?

I am having the same issue with my iPod Shuffle (512MB). I keep hitting No, but is there anything out there to fix this issue? Is there something wrong with my iPod? Please advise.

SASL(-1): generic failure: GSSAPI Error. No Credentials Cache Found

When I try to use any ldap command line utilties on my Xserve dual G5 running OS X Server 10.4.11, I get any number of errors including:
SASL/GSSAPI authentication started
ldapsasl_interactive_binds: Local error (-2)
additional info: SASL(-1): generic failure: GSSAPI Error: Miscellaneous failure (No credentials cache found)
If I run kadmin, or klist as super user I get the same error or similar error
If I run kdelete and then kinit I don't get an error message, but I still can't log in using the directory administrator account, or even root if I enable the root account.
The Server Admin tool shows that Kerberos is running and it appears to be working on all the clients on the network (OS X 10.3 and 10.4), but I just can't use the command line. This is frustrating because there are a number of batch tasks I prefer doing with the command line such as ldapadd and ldapmodify. The only command line utility for LDAP that does seem to work is slapcat. Workgroup Admin works as does phpldapadmin.
Any ideas?
Message was edited by: Christopher Dart
Message was edited by: Christopher Dart

Solved the problem by myself
- Disable the automatic recognition of the account settings-

FREQUENT FAILURES AND ERRORS:PLZ

can any one send some frequent failures and errors.with sol if possible.

Prasanth
Check these weblogs. Hope these helps.
Thnaks
Sat
/people/siegfried.szameitat/blog/2005/07/28/data-load-errors--basic-checks
Re: dataloading problems from r/3 ?

Lenovo g580 hardware scan failure

hi the lenovo solutions centre says hardware scan failure but i have found no where to fix it
the laptop is only around 4months old

Hi jon342,
Welcome and Thanks for posting in the Lenovo Community,
Am sorry to hear about you issue and as I can understand from you that Lenovo Solution Center provides you with a report for the scan that the HDD failure is detected,
I’d like to ask you to share with you the service provider contact numbers:
United Kingdom
IDEA-branded and
B, C, E, G, H, K, N, Q, V, Y Series Products
0844-249-1112
(5 pm from BT landlines)
9AM - 6PM
Monday - Friday
Thanks and Best Regards,
Soha
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Scan Failure on the 7520

To Garytech1: I am having the same problem with scan failure that you discussed earlier. You inboxed everyone the solution. Please inbox me. I have tried everything else.

Hi there @lrrealtor , welcome to the forums
Your post happened to be a new thread, so I am unsure of which post you were responding to.
I would suggest trying the steps in this guide for the Scanner Failure, and if you have tried them all, to contact HP directly to see about a replacement or trade in.
A 'Scanner Failure' Message Displays on the All-in-One Control Panel and You Cannot Scan, Copy, or F...
Please call our technical support at 800-474-6836. If you live outside the US/Canada Region, please click the link below to get the support number for your region. http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html
Best wishes
R a i n b o w 7000I work on behalf of HP
Click the “Kudos Thumbs Up" at the bottom of this post to say
“Thanks” for helping!
Click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution!

Scan Doc's error 4,[(3,42,0)] -- win 7 ult 64 -- hpC309a

After install, setup, hitting scan button delivers error message 4,[(3,42,0)] and shows only small top section of scan screen.
Thanks for your time and consideration.
Dave

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=...

Installation job encountered some failures. Error = 0x80240022

Hello,
Below error occurs in wuhandler.log for the security update deployment. How can this be fixed. Please let me know.
Installation job encountered some failures. Error = 0x80240022
Regards,
Boopathi S

Could be several reasons. Bad cab file,blocked from installing, I even had this kinds of error, not sure on the error code. The problem there was the WSUS NLB had an issue
http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

I am able to print but cannot scan as the error message shown is that 3510 series is not found.

I am able to print but cannot scan as the error message shown is that 3510 series is not found.
Rgds,
Sanjay

Hi VijayAhuja,
Welcome to the HP Support Forums! I see you are able to print but when you attempt a scan on your HP Deskjet 3510 you get an error message saying the 3510 series is not found.
I would first like you to run the HP Print and Scan Doctor- It was designed by HP to provide users with the troubleshooting and problem solving features needed to resolve many common problems experienced with HP print and scan products connected to Windows-based computers.
What did the PSDR find, are you now able to scan with your DJ 3510? If you are still not able to scan please leave me with the following information:
1. How do you have the printer connected, USB or Wireless?
2. What is you current Operating system?
3. Do you have any anti virus programs running, Norton or McAfee, please disable and retry the scan?
I will watch for your reply.
Thanks,
HevnLgh
I work on behalf of HP
Please click “Accept as Solution” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos Thumbs Up" to the left of the reply button to say “Thanks” for helping!

4630 scan to email error message no email app found

4630 scan to email error message no email app found

Hi, Please try: http://www.dummies.com/how-to/content/how-to-set-default-browser-and-email-programs-in-w.html Regards.

Updates not applying: Scan failed with error = 0x80072efd.

Hi, I'm trying to troubleshoot windows updates which are configured through SCCM2012R2. The WSUS server is installed on server 2012R2, version 6.3.9600.16384. I have it running on the custom website (using ports 8530 and 8531). For
a few weeks, my clients were configured with a conflicting group policy (pointing to the old wsus server). I removed that policy, and now the sccm agent is setting the local group policy to use the proper wusus server. Clients are windows 7 enterprise.
These clients do not have access to the internet.
Now, updates are still failing, with the following events in the wuahandler.log
Its a WSUS Update Source type ({8C51EBC1-265B-4889-8CC4-0B9EF237D704}), adding it.WUAHandler 4/9/2014 4:53:09 PM 4028 (0x0FBC)
Existing WUA Managed server was already set (http://Myserver-12R2-WSUS.mydomain.local:8530), skipping Group Policy registration. WUAHandler 4/9/2014 4:53:09 PM 4028 (0x0FBC)
Added Update Source ({8C51EBC1-265B-4889-8CC4-0B9EF237D704}) of content type: 2 WUAHandler 4/9/2014 4:53:09 PM 4028 (0x0FBC)
Scan results will include superseded updates only when they are superseded by service packs and definition updates. WUAHandler 4/9/2014 4:53:09 PM 4028 (0x0FBC)
Search Criteria is (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver') WUAHandler 4/9/2014 4:53:09 PM 4028 (0x0FBC)
Async searching of updates using WUAgent started. WUAHandler 4/9/2014 4:53:09 PM 4028 (0x0FBC)
Async searching completed. WUAHandler 4/9/2014 4:53:12 PM 3452 (0x0D7C)
OnSearchComplete - Failed to end search job. Error = 0x80072efd. WUAHandler 4/9/2014 4:53:12 PM 4028 (0x0FBC)
Scan failed with error = 0x80072efd. WUAHandler 4/9/2014 4:53:12 PM 4028 (0x0FBC)
For troubleshooting so far, I have disabled the client firewall, restarted the wsus server, and confirmed that the clients can get to the default IIS page on the wsus server. I'll try reinstalling the sccm client now, and will report back.
After much searching, none of the answers I have found online were of any help.
Any advice will be greatly appreciated.
Thanks,
Kevin

I did manage to reinstall the client, and when I look at WUAhandler.log now, I see the following:
Its a WSUS Update Source type ({8C51EBC1-265B-4889-8CC4-0B9EF237D704}), adding it. WUAHandler 4/9/2014 5:42:57 PM 3344 (0x0D10)
Unable to read existing resultant WUA policy. Error = 0x80070002. WUAHandler 4/9/2014 5:42:57 PM 3344 (0x0D10)
Enabling WUA Managed server policy to use server: http://MyServer-12R2-WSUS.Mydomain.local:8530 WUAHandler 4/9/2014 5:42:57 PM 3344 (0x0D10)
Waiting for 2 mins for Group Policy to notify of WUA policy change... WUAHandler 4/9/2014 5:42:57 PM 3344 (0x0D10)
Unable to read existing WUA resultant policy. Error = 0x80070002. WUAHandler 4/9/2014 5:43:01 PM 3344 (0x0D10)
Group policy settings were overwritten by a higher authority (Domain Controller) to: Server and Policy NOT CONFIGURED WUAHandler 4/9/2014 5:43:01 PM 3344 (0x0D10)Failed to Add Update Source for WUAgent of type (2) and id ({8C51EBC1-265B-4889-8CC4-0B9EF237D704}). Error = 0x87d00692.
So that's strange, if it's NOT CONFIGURED (microsoft's caps), you wouldn't think it would be a problem. So, If I generate a group policy results report, I get the following:
Policy:Specify intranet Microsoft update service location
Setting: Enabled
Winning GPO: Local Group Policy
Set the intranet update service for detecting updates: http://Myserver-12R2-WSUS.MyDomain.local:8530
Set the intranet statistics server: http://Myserver-12R2-WSUS.MyDomain.local:8530
Which is exactly what I think the SCCM agent is supposed to do.
Thanks in advance. Hopefully one of the wise souls in this forum can lead me to the light!
Kevin
P.S. I can post the full log if anyone's interested.

Failure (42458): Error accepting connection -5993 (Resource temporarily unavailable)

what will cause this error message for iplanet 4.0 web server?

Hi,
"failure (42458): Error accepting connection -5993 (Resource temporarily unavailable)"
The above error is Common message with SSL turned on with pre 3.6 Sp3 releases.
These were Spurious messages (defect 343349 in the release notes for 3.6).
I think it's fixed in 4.x version.
Thanks,
Daks.

HP1536 scan failure - WIA error

Similar Messages

Maybe you are looking for