Error: QueryInterface for interface SAPbouiCOM.IApplication failed.

Hi,
I have a problem with UI:
We have a process that is hung. A Process  setting specialPrices to many customers and in the middle of process AddOn crash with a folloving error:
Error: QueryInterface for interface SAPbouiCOM.IApplication failed.
This occurs in several processes of our various customer. this seems a bug in the UI
Someone have any idea about this?
thanks in advanced

Hi Alejandro,
When the error occurs, how much memory is your addon using? I've seen this error before in some addons where a process is leaking memory.
Try running your process and monitoring the memory size of your addon's executable and the memory size of the SAPbouiCOM.exe in Task Manager.
Kind Regards,
Owen

Similar Messages

  • Sending Error mail for Interface level Failure

    Dear SDN,
            I have a requirement where i cannot use alerts or ccms. My scenario is to devlop a monitoring solution where if any messages fails due to whatever reason i need to send 2 emails to the sapxi admin and to the business informing the error.
    The error has to be identified by tracing the status of the messages in sxmb_moni. So what can be a fesible solution given that alerts can not be used. Can writing a report to extract the messages in error and call a function module to send email ??
    Thanks and regards,
    Anirban.

    Hi Anirban,
    IF you debug SXMB_MONI, you will get the function module that extracts this data which is stored in table.
    This will give you only the SXMB_MONI errors. Not the adapter errors.
    For the adapter errors, you can raise alert and and then retrieve the data from the table in your same report.
    Regards
    Vijaya

  • Accounting Document not posted for Cancelled Invoice -error in FI interface

    Hi,
    When I create a billing document then an accounting document gets created automatically in the background and then when I cancel the billing document no accounting document gets generated and the field Posting Status in header Detail of Billing document updated as "Errors in Financials Interface.
    I tried to release it for Posting via VFX3 but failed due to below error message in Log:
    "Incorrect doc.no.: 4900000005. Select document number between 3000000000 and 3099999999"
    I have checked the Number range assignments to the Invoice type and Accounting type.
    The number range is same for both Invoice type (Y0F2) and Cancelled Invoice type (Y0S1).
    The Accounting document type (RV) is also same for both the cases. But it is working fine for Y0F2 (Acounting document generated and cleared automatically). But not working fine for Cancelled Invoice (Y0S1).
    Can anybody please help me find out a solution to the issue.
    Thanks, Ram.

    Hi,
    The error message F5151 refers to the number range of the FI document.
    Please have a look at the note 1259505: FAQ: New cancellation procedure in SD, which covers this issue in detail.
    Question 5:
    Q5. What is the FI document type, generated by the cancellation ?
    In the old cancellation procedure, the FI document type is always
    determined in SD, and passed to FI (the same when a normal invoice  -
    not a cancellation -  is transferred to accounting).
    In transaction VOFA there is the field 'Document type' (TVFK-BLART).
    If this field is filled, then the FI document will have the document
    type maintained here.
    If TVFK-BLART is empty, then the FI document will get the default
    document type 'RV'.
    If the new cancellation procedure is performed, the FI document type is
    always determined in FI, based on the document type of the FI document
    to be reversed.
    In transaction OBA7 the FI document type has assigned the field 'Reverse
    document type' (T003-STBLA).
    If it is filled, then the FI cancellation document will get the document
    type maintained here.
    If T003-STBLA is empty, then the FI document cancellation will get the
    same document type as the cancelled FI document.
    Notice that an unexpected FI document type can cause the error message
    F5 151.
    Example:
    F2 invoice 90000001 was released, creating an accounting document with
    document type 'RV'.
    This F2 invoice is reversed by the S1 billing document 70000001.
    In customizing of SD there is:
    Billing Type    Document Type
    F2              RV
    S1
    In customizing of FI there is:
    Document Type    Number range   Reverse Document Type
    RV               00             AB
    AB               01             AB
    The FI number ranges (object RF_BELEG) are:
    No  From number    To number   Ext
    00  0090000000     0099999999  X
    01  0100000000     0199999999
    Different situations can occur, due to these customizing settings of the
    FI document type, caused by the type of cancellation.
    If the new cancellation is used:
    The FI document type 'RV' has 'Reverse Document Type' = 'AB'.
    Document type 'AB' has number range '01' set as internal.
    So the FI document will have its own number included in
    100000000-199999999.
    There is no issue.
    If the old cancellation is used:
    The cancellation billing type S1 has no 'Document type' maintained, so
    the FI document will get document type 'RV'. It has number range '00',
    set as external number range.
    So the FI document should get the same number of S1 billing document.
    But the S1 billing document has number 70000001, not included in the
    interval of number range '01'.
    This will cause error F5 151.
    I hope this information helps you.

  • Check_ntlm_password:  Authentication for user ['name'] - ['name'] FAILED with error NT_STATUS_LOGON_FAILURE

    Hi,
    We are running a Mountain Lion Server with Open Directory / LDAPv3, as far as I can tell.  My responsibility is to get my CentOS 6.3 box running Samba v. 3.5.10-125.el6 to authenticate users against the ML / OD box.  I can ssh to the CentOS box OK and I can get Guest access to the Samba share to go OK too.  Also, the OD passwords on the LDAP server are set to 'Open Directory' so I guess that means that they are encrypted and the Samba server is set to send encrypted passwords.  But when a user tries to properly authenticate using either say via a Mac client Finder [Command-K], or smbclient, the Samba server will generate this message:
    check_ntlm_password:  Authentication for user ['name'] -> ['name'] FAILED with error NT_STATUS_LOGON_FAILURE
    (I am blanking out the user name on purpose).
    Of course there is more to the story, but those are the basics.
    Here are the relevant parts of my smb.conf.  FWIW, the CentOS / Samba box is called Jupiter.
    Thank you,
    NickZ
    [smb.conf]
    [global]
              display charset = UTF-8
              realm = SATURN.MCLEAN.HARVARD.EDU
              netbios aliases = ANL
              server string = Welcome To The Jupiter Samba Server Version 3.5.10-125.el6
              interfaces = lo, em1
              security = SERVER
              update encrypted = Yes
              password server = saturn.mclean.harvard.edu
              smb passwd file = /var/lib/samba/private/secrets.tdb
              passdb backend = ldapsam:ldap://saturn.mclean.harvard.edu
              passwd program = /usr/bin/passwd %u
              unix password sync = Yes
              lanman auth = Yes
              client NTLMv2 auth = Yes
              client use spnego principal = Yes
              kerberos method = system keytab
              log level = 2
              syslog = 3
              log file = /var/log/samba/log.%m
              max log size = 50
              name resolve order = host lmhosts wins bcast
              server signing = auto
              preferred master = Auto
              ldap admin dn = uid=DirAdmin,cn=users,dc=saturn,dc=mclean,dc=harvard,dc=edu
              ldap group suffix = cn=groups
              ldap passwd sync = yes
              ldap suffix = dc=saturn,dc=mclean,dc=harvard,dc=edu
              ldap ssl = no
              ldap user suffix = cn=users
              usershare allow guests = Yes
              idmap backend = ldap:ldap://saturn.mclean.harvard.edu
              idmap uid = 10000-20000
              idmap gid = 30000-40000
              cups options = raw
    [homes]
              comment = Home Directories
              read only = No
    [printers]
              comment = All Printers
              path = /var/spool/samba
              printable = Yes
              browseable = No
    [anl]
              comment = Main ANL Share
              path = /anl
              read only = No
              guest ok = Yes
              hide dot files = No

    Turns out a printer driver installed on an XP (even W2K(?)) was (apparently?) flooding the OS X SMB server to the point of collapse. Uninstalling the "HP Tools" part of the driver cleared it up. The printer is an HP LJ1300. I had downloaded the full driver from HP.com. I don't know if any/all these conditions need to be matched, but: the printer was on the network using an HP print server JetDirect EX Plus, and the computer(s) in question were connecting directly to it (not via a print server). It's been too long ago, but there were always several errors in the System Log (Win XP Event Viewer) that correlated with the errors on the OS X server.
    Proud to say that since that day (10+ months ago) I've not seen it happen again. whew.

  • Error SapBouiCom.IApplication

    Hi,
    I have un addon then execute a store procedure in SQL.
    This store procedure is very complicated and they return a dataset with many recordset.
    When my customer launch this procedure, from the addon, after some minutes they catch this error : QueryInterface per l'interfaccia SapBouiCom.IApplication non riuscita.
    There is some new features in Sap 8.81, like TimeOut or other similar things? This procedure is OK with Sap 2007.
    This is the code:
    Dim rsMov As SAPbobsCOM.Recordset = Mydb.GetBusinessObject(SAPbobsCOM.BoObjectTypes.BoRecordset)
    Try
    rsMov.DoQuery("exec generaFileMovimenti ''")
    While Not rsMov.EoF
               'MY CODE
               rsMov.MoveNext()
    End While
    Catch ex As Exception
                System.Runtime.InteropServices.Marshal.ReleaseComObject(rsMov)
    Finally
    End Try
    Regards
    Marco

    Hi Marco,
    What is in your SP of generaFileMovimenti?
    Thanks,
    Gordon

  • How do I fix the following error   Photoshop 13.1.2 for Creative Cloud Installation failed. Error Co

    Photoshop 13.1.2 for Creative Cloud
    Installation failed. Error Code: U44M1P7

    What is the current version of Ps (Help->System Info), if you have 13.0.1.2 already applied then you need to re-install Ps to get Ps 13.1.2.
    As 13.1.2 is a subscription patch this would not get applied over 13.0.1.2.
    If this still does not resolves your issue, Kindly mail me installer logs.
    For Mac:
    "Library/Logs/Adobe",
    For Win:
    Program Fies(x86)\Common Files\Adobe\Installers
    Please mail me @ [email protected]
    Regards,
    Ashutosh

  • What does this mean:Photoshop 13.1.2 for Creative Cloud Installation failed. Error Code: U44M1P7

    What does this mean:Photoshop 13.1.2 for Creative Cloud Installation failed. Error Code: U44M1P7
    I found the manual update, which worked!
    http://www.adobe.com/support/downloads/thankyou.jsp?ftpID=5595&fileID= 5604

    Hi Barbara,
    For failed 13.1.2 update error U44M1P7, Please refer to the solution mentioned in the following threads :
    http://forums.adobe.com/message/5396792#5396792
    http://forums.adobe.com/message/5409050#5409050

  • Photoshop 13.1 for Creative Cloud Installation failed. Error Code: U44M1P7

    So, Lion won't let me deactivate, so I can't use the updates that I just bought with signing up for the Cloud, so I tried installing on my Mountain Lion Macbook and this is what I get...
    Photoshop 13.1 for Creative Cloud
    Installation failed. Error Code: U44M1P7
    Please Help, somebody!
    Spent about an hour with Adobe Tech support just trying to figure out why I couldn't deactivate my product, only to find I had to close the chat room and the advice still didn't work.
    Very frustrated, here!  I have no updates on either computer, now!

    Hi Jules,
    Sorry to hear about your difficulties.
    My recommendation would be
    - Uninstall PS via Mac HD > Applications > Utilities > Adobe Installers (Mac OS X)
    - Create a new user with Admin rights, log out of your current account and into the newly created one
    10.7 http://support.apple.com/kb/PH4600
    10.8 http://support.apple.com/kb/PH11468
    - Reinstall Photoshop CS6 via Adobe Application Manager
    - Try to update to 13.1 using Help > Updates in Photoshop CS6
    -Dave

  • [svn] 3722: Bug: BLZ-260 - Error message for a legacy =3. 0 client poll failing against a =3.1 server is unclear

    Revision: 3722
    Author: [email protected]
    Date: 2008-10-17 14:04:59 -0700 (Fri, 17 Oct 2008)
    Log Message:
    Bug: BLZ-260 - Error message for a legacy <=3.0 client poll failing against a >=3.1 server is unclear
    QA: Yes
    Doc: No
    Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-260
    Modified Paths:
    blazeds/trunk/modules/common/src/flex/messaging/errors.properties
    blazeds/trunk/modules/core/src/flex/messaging/FlexSession.java
    blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

    your problem:
    Missing class: oracle.tip.adapter.jms.JmsManagedConnectionFactory
    Dependent class: oracle.tip.adapter.fw.wsdl.WSDLUtils
    Loader: oracle.bpel.common:10.1.3
    Code-Source: /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/bpel/lib/orabpel.jar
    Configuration: <code-source> in /oraclesoa/oraclesoa/product/10.1.3.1/OracleAS_1/j2ee/home/config/server.xml
    It happens when server is custom installed, try to reinstall it as full version and problem should disappear otherwise your need another full installation to retrieve and replace orabpel.jar file from (or maybe more)

  • Error while invoking member: ManagedInit1 - Login failed for user 'SRCAdmin

    I am trying to setup a Test Server for BOP 11.60 with MS SQL 2000 in MS Windows Server 2003. After installation, I copied user directory and database from live system to the new Test server. After installed the application andI updated Configuration Manager but when I run Planning Application Services, I have the following message:
    System.Exception: Error while invoking member: ManagedInit1 - Login failed for user 'SRCAdmin'. ---> System.Runtime.InteropServices.COMException (0x80131904): Login failed for user 'SRCAdmin'.
       --- End of inner exception stack trace ---
       at SRC.Core.Common.LateBoundHelper.InvokeMethodDirect(String methodName, BindingFlags flags, Object[] args)
       at SRC.Core.Common.LateBoundHelper.InvokeMethod(String methodName, Object[] args)
       at SRC.Core.Host.HostProcess.StartUp()
    I can use SRCAdmin user login to SQL Database without any problem but use Adminbop to start the Planning Application Services, I had this message.
    Does anyone know what is the problem?
    Regards,
    Irene

    Please, review your FBA configuration https://sharepoint2013fba.codeplex.com/

  • 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

  • BW error:  "invalid call sequence for interface when recording changes"

    I am getting the error "invalid call sequence for interface when recording changes" when I try to activate a datasource in BW.  Any ideas on how to resolve this error?
    Thanks.

    I already tried that.  This is what's happening..  When I get this error, if I try again it will activate and gets collected into a transport.  I moved this transport to our QA system.  As soon as I try to execute an infopackage under this datasource in QA, I get the error datasource   xxxxx must be activated.   Before the excecution of the infopackage, the datasource is in "Active version executable".   After I get the error message "datasource must be activated", the datasource in the QA system changes to "Active version not executable".   I am not sure all these issues are related back to the "invalid call sequence" error I am getting when I try to activate the data source.
    I also tried recollecting the transport from our Dev system to QA and it still gives the above errors.
    Any help?
    Thanks.

  • Error message: Multiple definitions exist for interface

    Hi experts,
    I am developing a scenario that involves a BPM, that receives a certain abstract interface, and sends out another abstract interface.
    I have created a service interface for the result abstract interface.
    I have tested the before BPM and it worked, but now it has stopped working.
    In the java ui no errors are seen, and the BPM activates successfully, but in transaction SXI_CACHE the BPM is in status 99, and in the activation log there is a message saying: Multiple definitions exist for interface [Name of the result abstract interface].
    I have tried activating the service interface, the BPM, and doing a delta cache refresh, but it didn't change.
    What can I do to solve this problem?
    Thanks in advance,
    Gershon Osmolovski

    Hi Gershon,
    Try following thing, might help.
    Go to ID and check which communication component you have created. Check if there is any other inactive version of it. If it is existing.Delete it.
    Edit and activate the original Communication component and do cache refresh.

  • Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed

    SharePoint 2010 -
    I have created a console utility that further calls the stsadm.exe to Export sites from one site collection in a DB to another site collection in another DB of the same web application.
    Export works fine. But during Import, I get the following errors
    [ListItem] [Admin] Progress: Importing
    [ListItem] [Admin]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Hol plans.xls] Progress: Importing
    [ListItem] [Hol plans.xls]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Time.doc] Progress: Importing
    [ListItem] [Time.doc]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [AP Docs] Progress: Importing
    [ListItem] [AP Docs]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Update - June 27th.pdf] Progress: Importing
    [ListItem] [Update - June 27th.pdf]   Verbose: List URL: /pwa1/GTR/7 GTR  Programme
    [ListItem] [Update - June 27th.pdf]   Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    [ListItem] [Update - June 27th.pdf]   Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    [ListItem] [Update - June 27th.pdf]   Error: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    FatalError: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
    Progress: Import did not complete.
    1. Does the console application treated as a Sandbox Solution?
    2. Do I need to configure CAS policy in wss_usercode.config? and what?
    3. What else could be configured to make this work?
    I have tried adding the following in wss_custom_minimaltrust.config but no avail.
    <SecurityClass Name="SqlClientPermission" Description="System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/>           
    and
    <PermissionSet
                        class="NamedPermissionSet"
                        version="1"
                        Name="SPRestricted">
    <IPermission
                          class="SqlClientPermission"
                          version="1"
                          Unrestricted="true"
                                />   
    <!-- Other IPermission -->
    </PermissionSet>
    UPDATE: It has been observed that the issue is intermittent. That is, sometimes the import works fine (event without any configuration of SqlClientPermission in any config file) but sometimes it gives the above error. I'm stuck!
    Regards, Amit Gupta

    Hi,
    According to your post, my understanding is that you get Error “Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed
    Simple solution is to change the trust the trust level to FULL: <trust   level="[Full]"    originUrl="URL" />
    In addition, you can modify the wss_mediumtrust.config and wss_minimaltrust.config file under the path “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG”.
    For more information, you can refer to:
    http://blogs.msdn.com/b/navdeepm/archive/2010/02/19/system-security-securityexception-request-for-the-permission-of-type-system-data-sqlclient-sqlclientpermission-system-data-version-2-0-0-0-culture-neutral-publickeytoken-b77a5c561934e089-failed.aspx
    http://www.fewlines4biju.com/2011/01/request-for-permission-of-type_18.html
    http://techsolutions-at-desk.blogspot.com/2011/08/request-for-permission-of-type.html
    Thanks,
    Linda Li                
    Forum Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Linda Li
    TechNet Community Support

  • My installation for Photoshop Elements 12 Failed. I have Windows Vista. I get an error message stating:installer failed to initialze. Please help!!

    My installation for Photoshop Elements 12 Failed. I have Windows Vista. I get an error message stating:installer failed to initialize. Please help!!

    Error "Installer Failed to Initialize" | Install desktop application | Windows

Maybe you are looking for