An error occurred in the PD layer; transaction terminated in SC

Hi experts,
I have an issue like this "An error occurred in the PD layer; transaction terminated". This error came when i save Shopping Cart.
Just for the information, I have maintained number range assignment for BUS2121 - Shopping Carts also.
And I am working on SRM 7.0
Do you have any idea to solve this issue?
Thanks,
Rhesa Syahrial

Hi Sam,
Thanks for your fast reply.
Below is the error analysis from st22.
An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
therefore caused a runtime error.
The reason for the exception is:
Buffer table not up-to-date
I have checked in sapnote also about this issue. but still not resolved.
Regards,
Rhesa Syahrial

Similar Messages

  • Create RFx Response: An error occurred in the PD Layer transaction terminated

    Hello Experts,
    Currently we are in SRM 7.02 implemenation: we are facing below problem while creating RFx response with popup screen.
                             "An error occurred in the PD Layer transaction terminated"
    For this we have checked below
    1. http://scn.sap.com/thread/1912966    ----> it didn't help
    2. We have assigned SAP_ALL role to bidder also ----> Facing same issue
    3. Check Number ranges ---> everything is fine.
    there is no clue from above points.
    Thanks & Regards
    Sandeep.

    Hello Sandeep,
    I am facing the same problem while creating the RFx response in SUS side. Same error occurred while i am creating the Rfx response with bidder.
    error: An error occurred in the PD Layer transaction terminated
    Could you please let me know, did you find any solution for this issue?
    Thanks in advance!!
    Thanks,
    Anil

  • A fatal error occured in the PD Layer. The transaction needs to be terminat

    Hi experts,
    Do you know these error message?
    A fatal error occured in the PD Layer. The transaction needs to be terminated
    We applied note 1174283, but it didn't work.
    The problem is related to users that don´t belong to SRM structure anymore, but their shopping carts are still in sourcing process.
    Thanks
    Juliana

    Hi PM,
    Note 1269719 - display a more detailled message in abort popup
    Symptom
    In some cases, the SRM application cannot continue and must be aborted.
    Then a popup is displayed with an error message "A fatal error occured in
    the PD layer. The transaction needs to be terminated.".
    The error message is quite general, it is displayed even if a more specific
    error message is available.
    Note 1174283 - SOCO: SC data will not be saved correctly in secend step
    Symptom
    You saved some data in the second step of Sourcing Cockpit using the button
    'Save'. You closed the application and started it again.
    You selected data in the first step of SOCO or went directly to the second
    step. The system display a message: "A fatal error occured in the PD layer.
    The transaction needs to be terminated".
    regards
    Muthu

  • A fatal error occured in the PD Layer during create Supplier RFx response

    Dear SRM 7 Experts,
    I am implementing SRM 7.  I can successfully create a Supplier RFx Response on behalf of a supplier using the Surrogate Bid functionality.  However, if I log on as a supplier contact person and try to create a Supplier RFx Response, I get error u201D A fatal error occured in the PD Layer. The transaction needs to be terminatedu201D. 
    Number ranges for Supplier RFx response (BUS2202) are maintained and assigned to the transaction type correctly.
    What could be the problem? 
    Kind regards
    Pedzi

    Hi
    Here is the thread which solved the same problem:
    Re: A fatal error occured in the PD Layer during RFx response
    with regards
    Manjunath

  • A fatal error occured in the PD Layer during RFx response

    Dear Experts,
    While creating the RFx response the error is,
    "A fatal error occured in the PD Layer. The transaction needs to be terminated."
    I just checked the earlier threads discussed on this forum says, this is due to non maintaining of number ranges , but i have maintained the no ranges for RFx response,
    got stuck here, kindly help me to solve this issue.
    Thanks

    Sorry  wrongly posted...  the details are below.
    The Rfx response no range 01 & 02 are matching with transaction type Supplier quote 01 & 02,
    In Define Transaction type -- for Transaction category BUS2200 -- Transaction type RFQU -- the entries are
    *Tran.cat            Trns.type                     subsequent obj.type                     Follow up trns.type
    *Bus2200            RFQU                            BUS2202                                     ECPO
    The entries are correct or not???
    Regards
    Rakesh

  • Fatal error occured in the PD layer srm 7.0

    Hi,
    While creating the RFx response i am getting following error.
    "A fatal error occured in the PD Layer. The transaction needs to be terminated."
    I tried as per following thread(number range is correct, i had full authorization), but still i am getting same error.
    Any suggestion...Thanks in advance.
    A fatal error occured in the PD Layer during RFx response
    Thanks,
    Narayan

    Hi ,
    Tell me the steps what you are performing in creating Rfx .
    I am also working in the same scenario in SRM 7.0
    This is a generalises error
    Regards
    G.Ganesh Kumar

  • Windows 8 RDP error security package error occurred in the transport layer.

    We have an issue where in windows 7 this rdp works fine but windows 8 gives this error on all machines.
    Your computer can't connect to the remote computer because a security package error occurred in the transport layer.  Retry the connection or contact your network administrator for assistance.

    Hi,
    Thanks for your post.
    Please elaborate your scenario. Which OS version you trying to access? Windows Server 2012 or earlier version? Trying to access Session Host, RemoteApp or VM?
    Please install latest Windows update on both side. Verify the port 3389 was not blocked by firewall, anti-virus or intermediate device. In addition, check the event viewer, to see if any related error was recorded.
    Best Regards,
    Aiden
    If you have any feedback on our support, please click
    here
    Aiden Cao
    TechNet Community Support

  • "An RFC error occurred in the TMS communications layer.

    Hi all,
    We are running SAP ECC 6 in SUSE Linux. I am trying to configutre the STMS by keeping my Developement server as a domain controller. But when i login to my Production server and try to add the server in TMS its throwing an error message.
    "An RFC error occurred in the TMS communications layer.
    Target system: DOM_CTL.(000)
    Function: TMS_CFG_CREATE_A2D_REQUEST
    RFC message:Error opening an RFC connection.
    System response
    The function terminates."
    Procedure
    Correct the error and execute the command again.
    Any help would be greatly appreciable
    Regards,
    Pradeep

    Hi,
    When I have had problem's like this before I have deleted the complete TMS configuration, then made sure the TMS RFC connections are deleted then re-installed the TMS as if it was a fresh install, this usually fixed these communication issues.
    I did however have a problem with the TMS configuration if the Password Parameters indicating there must be a digit is configured. I removed this parameter configured TMS then set this parameter again.
    Regards
    Krishna

  • JMS-204: An error occurred in the AQ JNI layer

    Approach 1) works fine but not 2).
    Approach 1
    =================
    // Use the DriverManager to get the DB Connection
    DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver());
    java.sql.Connection dbConnection = DriverManager.getConnection("the url" , "the uid", "the pwd");
    javax.jms.QueueConnection queueConnection = AQjmsQueueConnectionFactory.createQueueConnection( dbConnection );
    Approach 2 (doesn't work)
    =================
    // Use the JNDI Lookup to get the DB Connection
    Context ctx = get the context;
    DataSource dataSource = (DataSource)ctx.lookup("datasoruce jndi");
    dbConnection = dataSource.getConnection();
    queueConnection = AQjmsQueueConnectionFactory.createQueueConnection( dbConnection );
    Please note that I'm able to get the Queue Connection. But when I try to send the message, I get the exception.
    Exception: JMS-204: An error occurred in the AQ JNI layer
    Linked Exception: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
    [java.rmi.MarshalException: failed to marshal setORAData(ILoracle.sql.ORAData;); nested exception is:
         java.io.NotSerializableException: oracle.jms.AQjmsTextMessage_C]
    App Server: WebLogic 8.1
    Any thougts...
    Thanks in advance.

    It is complaining about the AQjmsTextMessage not being serialized. I have seen errors with not using the actual oracle connection directly. Usually the datasource has some wrapper database connection. However, i would expect a different error. I will have to experiment with this.

  • Error occured in the phase MOVE NAMETABS while updating patch.

    Hi Gurus
    When i implementing a SP15 to SP16 in a queue, i got the Dump.
    Please help me in this issue.
    The import was stopped, since an error occurred during the phase
       IMPORT_PROPER, which the Support Package Manager is unable to resolve
       without your input.
       After you have corrected the cause of the error, continue with the
       import by choosing Support Package -> Import queue from the initial
       screen of the Support Package Manager.
       The following details help you to analyze the problem:
           -   Error in phase: IMPORT_PROPER
           -   Reason for error: TP_STEP_FAILURE
           -   Return code: 0008
           -   Error message: OCS Package ALL, tp step "6", return code 0008
       Notes on phase IMPORT_PROPER
       In this phase repository objects and table entries are imported. This
       phase can terminate due to the following reasons:
       o   TP_INTERFACE_FAILURE: The tp interface could not be called.
       o   TP_FAILURE: The program tp could not be executed. For more
           information on this, see the SLOG or ALOG log file.
       o   TP_STEP_FAILURE: A tp step could not be executed. To find the cause
           of the error, see the appropriate log, such as the import log.
           If the cancelation message contains a tp step 6, N or S, the step in
           question is independent of the transport request. You can find these
           logs under the node Import steps not specific to transport request
           in the log overview.
           Alternatively, you can find these logs in the following files in the
           log directory of your transport directory (usually:
           /usr/sap/trans/log):
        -   tp Step 6: P<YY><MM><DD>.<SID>
        -   tp Step N: N<YY><MM><DD>.<SID>
        -   tp Step S: DS<YY><MM><DD>.<SID>
        You can display these files using the report RSPUTPRT or by calling
        transaction AL11.
    A prerequisite of the Support Package Manager is that the Change and
    Transport System (CTS) is configured correctly. For more detailed
    information, read the online documentation available from Help -> SAP
    Library -> mySAP Technology Components -> SAP Web Application Server ->
    Change and Transport System .
    A list of the most important SAP Notes for Online Correction Support
    (OCS) is available in SAP Note 97620, which is updated regularly.
    Regards,
    Ganesh

    Hi jazz,
    I want to update the patch SAPKA70016 for SAP_ABA component.
    Queue log
    System              : ISP
    tp path             : tp
    Version and release: 372.04.36 700
    Activate inactive nametabs
    End date and time : 20081215012202
    Ended with return code:  ===> 8 <===
      TP request log is
    START CMDIMPORT            ISP L      20081222014354              DDIC         usirs254 20081222014354043
    STOP  CMDIMPORT            ISP L      20081222014401              DDIC         usirs254 20081222014354043
    START DD IMPORT            ISP H      20081222014540              DDIC         usirs254 20081222014540574
    STOP  DD IMPORT            ISP H      20081222014616              DDIC         usirs254 20081222014540574
    START DD ACTIVATION        ISP A      20081222014617              DDIC         usirs254
    START tp_getprots          ISP J      20081222014617              DDIC         usirs254
    STOP  tp_getprots          ISP J      20081222014723              DDIC         usirs254
    STOP  DD ACTIVATION        ISP A      20081222014723              DDIC         usirs254
    START imp all              ISP        20081222014723              DDIC         usirs254 20081222014723434
    INFO: event SAP_IMPORT_START triggered successfully
    START DISTRIBUTION OF DD-O ISP S      20081222014723              DDIC         usirs254 20081222014723434
    START tp_getprots          ISP S      20081222014723              DDIC         usirs254 20081222014723434
    STOP  tp_getprots          ISP S      20081222014726              DDIC         usirs254 20081222014723434
    STOP  DISTRIBUTION OF DD-O ISP S      20081222014726              DDIC         usirs254 20081222014723434
    INFO  TBATG CONVERSION OF  ISP N      not needed                  DDIC         usirs254 20081222014723434
    START MOVE NAMETABS        ISP 6      20081222014726              DDIC         usirs254 20081222014723434
    START tp_getprots          ISP P      20081222014726              DDIC         usirs254 20081222014723434
    ERROR ALL                  ISP 6 0008 20081222014743              DDIC         usirs254 20081222014723434
    STOP  tp_getprots          ISP P      20081222014747              DDIC         usirs254 20081222014723434
    STOP  MOVE NAMETABS        ISP 6      20081222014747              DDIC         usirs254 20081222014723434
    ERROR: stopping on error 8 during MOVE NAMETABS
    START INFORM SAP-SYSTEM OF ISP Q      20081222014747              DDIC         usirs254 20081222014723434
    START tp_getprots          ISP Q      20081222014747              DDIC         usirs254 20081222014723434
    STOP  tp_getprots          ISP Q      20081222014748              DDIC         usirs254 20081222014723434
    STOP  INFORM SAP-SYSTEM OF ISP Q      20081222014748              DDIC         usirs254 20081222014723434
    STOP  imp all              ISP   0008 20081222014748              DDIC         usirs254 20081222014723434
    START CMDIMPORT            ISP L      20081222015155              DDIC         usirs254 20081222015155637
    STOP  CMDIMPORT            ISP L      20081222015158              DDIC         usirs254 20081222015155637

  • Error while saving the documents in Transactions MIRO,VA02, VA01, ects

    Hi SAP Gurus,
    i am geting an popup error while saving or after changing the documents in MIRO VA01, VA02 transactions..
    The error is  * " Condition Table Missing : Access JST1 60 ( Pricing Taxes ) " *
    can u please help me out.
    Regards
    Kumar m

    Hi,
    Found a note explaining the significance of these errors.
    It says:
    "NZE-28862: SSL connection failed
    Cause: This error occurred because the peer closed the connection.
    Action: Enable Oracle Net tracing on both sides and examine the trace output. Contact Oracle Customer support with the trace output."
    For further details you may refer the Note: 244527.1 - Explanation of "SSL call to NZ function nzos_Handshake failed" error codes
    Thanks & Regards,
    Sindhiya V.

  • An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070003.

    I received the above error reinstalling SQL Server 2008.  I have tried all suggestions.  This error also appears when I install any version of SQL Server.
    I have also installed;
    Microsoft® .NET Framework Version 2.0.50727.4927
    Microsoft® .NET Framework Version 4.0.31106.0
    Microsoft® .NET Framework Version 3.0.6920.50
    Microsoft Visual C++ 2005 Redistributable (x64) 8.0.59192
    Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
    Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
    Microsoft Visual C++ 2010 x64 Redistributable 10.0.40219
    Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219
    Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
    Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Exit code (Decimal):           -2068052081
      Exit facility code:            1212
      Exit error code:               1935
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
    rerun SQL Server Setup.
      Start time:                    2014-02-23 19:17:20
      End time:                      2014-02-23 19:21:35
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SqlSupport_KatmaiRTM_Cpu64_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
    Machine Properties:
      Machine name:                  OHPC
      Machine processor count:       2
      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
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       0
      Installation location:         H:\SQLServer2008R2_SP1\x64\setup\
      Installation edition:          DEVELOPER
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Manual
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  <empty>
      FTSVCPASSWORD:                 *****
      HELP:                          False
      IACCEPTSQLSERVERLICENSETERMS:  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:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 FilesOnlyMode
      RSSVCACCOUNT:                  <empty>
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           OHPC\Robert
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  True
      TCPENABLED:                    0
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SystemConfigurationCheck_Report.htm
    SFC/ Scannow
    2014-02-23 19:08:22, Info                  CSI    0000016f [SR] Verifying 100 (0x0000000000000064) components
    2014-02-23 19:08:22, Info                  CSI    00000170 [SR] Beginning Verify and Repair transaction
    2014-02-23 19:08:23, Info                  CSI    00000172 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:23, Info                  CSI    00000174 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:26, Info                  CSI    00000176 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:26, Info                  CSI    00000177 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
    2014-02-23 19:08:26, Info                  CSI    00000179 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
    source file in store is also corrupted
    2014-02-23 19:08:27, Info                  CSI    0000017c [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:08:27, Info                  CSI    0000017d [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
    2014-02-23 19:08:27, Info                  CSI    00000180 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
    source file in store is also corrupted
    2014-02-23 19:08:27, Info                  CSI    00000182 [SR] Verify complete
    2014-02-23 19:12:33, Info                  CSI    00000326 [SR] Verifying 100 (0x0000000000000064) components
    2014-02-23 19:12:33, Info                  CSI    00000327 [SR] Beginning Verify and Repair transaction
    2014-02-23 19:12:33, Info                  CSI    00000329 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:12:35, Info                  CSI    0000032b [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:12:35, Info                  CSI    0000032c [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
    2014-02-23 19:12:35, Info                  CSI    0000032f [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
    source file in store is also corrupted
    2014-02-23 19:12:36, Info                  CSI    00000331 [SR] Verify complete
    2014-02-23 19:13:14, Info                  CSI    0000035d [SR] Repairing 3 components
    2014-02-23 19:13:14, Info                  CSI    0000035e [SR] Beginning Verify and Repair transaction
    2014-02-23 19:13:14, Info                  CSI    00000360 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000362 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000364 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000366 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:14, Info                  CSI    00000367 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
    2014-02-23 19:13:15, Info                  CSI    0000036a [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
    source file in store is also corrupted
    2014-02-23 19:13:15, Info                  CSI    0000036c [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
    Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:15, Info                  CSI    0000036d [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
    2014-02-23 19:13:15, Info                  CSI    0000036f [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
    source file in store is also corrupted
    2014-02-23 19:13:15, Info                  CSI    00000371 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
    Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2014-02-23 19:13:15, Info                  CSI    00000372 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
    2014-02-23 19:13:15, Info                  CSI    00000375 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
    source file in store is also corrupted
    2014-02-23 19:13:15, Info                  CSI    00000377 [SR] Repair complete
    2014-02-23 19:13:15, Info                  CSI    00000378 [SR] Committing transaction
    2014-02-23 19:13:15, Info                  CSI    0000037c [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction 
    have been successfully repaired

    Summary:
    Attempted proposed solution.  Error still appears.
    This is installed:
    Microsoft Visual C++ 2005 ATL Update kb973923 - x86 8.0.50727.4053
    Microsoft Visual C++ 2005 Redistributable               8.0.56336
    Microsoft Visual C++ 2005 Redistributable (x64)         8.0.59192
    Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
    Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
    Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219
    Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
    Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
    Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
    I reinstalled:
    vcredist_x64 Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) .exe
    vcredist_x86 Microsoft Visual C++ 2005 SP1 Redistributable Package (x86).exe
    Results:
    Windows Installer reconfigured the product. Product Name: Microsoft Visual C++ 2005 Redistributable (x64). Product Version: 8.0.56336. Product Language: 0. Manufacturer: Microsoft
    Corporation. Reconfiguration success or error status: 0.
    Windows Installer reconfigured the product. Product Name: Microsoft Visual C++ 2005 Redistributable. Product Version: 8.0.56336. Product Language: 0. Manufacturer: Microsoft Corporation.
    Reconfiguration success or error status: 0.
    I installed SQLServer2008R2_SP1
    Same error message came up;
    SqlSupport_KatmaiRTM_Cpu64_1.log
    MSI (s) (64:94) [23:03:43:910]: Source for file 'pfbafgaq.dll' is uncompressed, at 'H:\SQLServer2008R2_SP1\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\'.
    MSI (s) (64:94) [23:03:43:926]: Executing op: SetTargetFolder(Folder=C:\Windows\winsxs\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.1833_none_8a17faaf2edd3e00\)
    MSI (s) (64:94) [23:03:43:926]: Executing op: SetSourceFolder(Folder=1\Windows\winsxs\nvdlei3o.taa\)
    MSI (s) (64:94) [23:03:43:926]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
    C8B3B9A1E18E},ComponentVersion=8.0.50727.1833,ProductCode={B40EE88B-400A-4266-A17B-
    E3DE64E94431},ProductVersion=10.1.2731,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
    MSI (s) (64:94) [23:03:43:941]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\ATL80.dll,FileKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-
    3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
    C8B3B9A1E18E},ComponentVersion=8.0.50727.762,ProductCode={071c9b48-7c32-4621-a0ac-
    3f809523288f},ProductVersion=8.0.56336,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
    MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.cat,FileKey=ul_catalog.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.manifest,FileKey=ul_manifest.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-
    3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\ATL80.dll,FileKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-
    26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:957]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
    C8B3B9A1E18E},ComponentVersion=8.0.50727.762,ProductCode={D40172D6-CE2D-4B72-BF5F-
    26A04A900B7B},ProductVersion=11.0.0,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
    MSI (s) (64:94) [23:03:43:972]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.cat,FileKey=ul_catalog.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:972]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
    \amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
    ww_f19a562a.manifest,FileKey=ul_manifest.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-
    26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
    MSI (s) (64:94) [23:03:43:972]: Executing op: AssemblyCopy(SourceName=uvdlei3o.taa|
    ATL80.dll,SourceCabKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,DestName=ATL80.dll,Attributes=0,FileSize=113152,PerTick=65536,,VerifyMedia=1,ElevateFlags=4,,,,ComponentId=
    {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E},,,,AssemblyMode=0,)
    MSI (s) (64:94) [23:03:43:972]: Assembly Error:The system cannot find the path specified.
    MSI (s) (64:94) [23:03:43:972]: Note: 1: 1935 2: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E} 3: 0x80070003 4: IAssemblyCache 5: CreateAssemblyCacheItem 6:
    Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"
    MSI (s) (64:94) [23:03:43:972]: Assembly Error (sxs): Please look into Component Based Servicing Log located at -169675656ndir\logs\cbs\cbs.log to get more diagnostic information.
    MSI (s) (64:94) [23:03:49:882]: Product: Microsoft SQL Server 2008 Setup Support Files  -- Error 1935. An error occurred during the installation of assembly
    'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
    HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}
    Error 1935. An error occurred during the installation of assembly
    'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
    HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}
    MSI (s) (64:94) [23:03:49:882]: User policy value 'DisableRollback' is 0
    Thanks, Ted U

  • Error 1935 - Adobe Reader (11) - An error occurred during the installation of assembly component - Windows 7

    NOT RESOLVED
    It seems to be a problem with my windows installation. I will re-install at a later date since installing PDF viewing programs the only issue.
    Problem:
    While installing Adobe Reader XI using the install_reader11_en_mssd_aaa_aih.exe from Adobe Reader Install for all versions and AdbeRdr11000_en_US.msi from a forum post on here. Error 1935 occurs using both installers and causes the setup to fail and initiate rollback.
    Additional information:
    In Programs & Features list there is no adobe reader as you can see:
    This is pretty much a clean install of windows on which I have installed: Adobe Flash Player (16), Steam + some games, Chrome, Skype and some Visual C++ Redistributables, .NET Framwork, Drivers for GPU, CPU, Motherboard and USB devices.
    Error:
    Error 1935. An error occurred during the installation of assembly component
    {B708EB72-AA82-3EB7-8BB0-D845BA35C93D}.
    HRESULT: 0x80070308
    System:
    Windows 7 x64 - installed on a SSD.
    Motherboard: ASRock Z97 Extreme 4
    GPU: Gigabtye - G1 Gaming GTX 970
    CPU: Intel Core - i7 4770K @4.00 GHz
    RAM: 16GB Kingston Hyper X (8x2)
    Steps taken:
    1. I have cleared the transaction log using command prompt with the following command:
        fsutil resource setautoreset true C:\
    Restarting the computer and trying to install Adobe Reader 11 results in the same error.
    2. Restarting the computer, disabling Malwarebytes Anti-Malware and installing Adobe Reader 11 results in the same error.
    3. Chrome has "allow all sites to run JavaScript" checked.
    Thanks
    Edit:
    I have attempted to install an earlier version (10.1.4) of Adobe Reader - Same error occurs.
    Edit 2:
    I'm going to look for some alternatives for the mean time
    Edit 2.1:
    These alternative programs are failing to install as well. Multiple errors, I now assume the issue is with my windows installation.

    Hi Kanker ,
    Please refer to the following link and see if it helps.
    https://helpx.adobe.com/acrobat/kb/error-1935-install-acrobat-reader.html
    Let us know with your response .
    Stay well.
    Regards
    Sukrit Dhingra

  • An error occurred in the source system, DBIF_RSQL_SQL_ERROR

    Dear All,
    last 4 days my process chain stop, now todya i activate the process chain. i found a error In 0FI_AR-4.
    the error i found
    Error message from the source system
    Diagnosis
    An error occurred in the source system.
    System Response
    Caller 09 contains an error message.
    Further analysis:
    The error occurred in Extractor .
    Refer to the error message.
    Procedure
    How you remove the error depends on the error message.
    Note
    If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
    i already check in RSA3 , Once execute 0FI_AR_4 I Found a dump
    An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
    neither
    caught nor passed along using a RAISING clause, in the procedure
    "BWFIR_READ_BSID_CPUDT_DATA" "(FUNCTION)"
    Since the caller of the procedure could not have expected this exception
    to occur, the running program was terminated.
    The reason for the exception is:
    How to correct the error
    The exception must either be prevented, caught within the procedure
    "BWFIR_READ_BSID_CPUDT_DATA"
    "(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
    Database error text........: "ORA-25153: Temporary Tablespace is Empty"
    Internal call code.........: "[RSQL/FTCH/BKPF_BSID ]"
    Please check the entries in the system log (Transaction SM21).
    You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
    "DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
    "SAPLBWFIR" or "LBWFIRU10"
    "BWFIR_READ_BSID_CPUDT_DATA"
    please any one help on this issue
    Advance in thanks
    Regards
    Priya

    Hi,
    Can you please try adding the datafile to the PSAPTEMP tablespace in the source system, and try to start the process chain again. If required you have to contact the Basis Administration. Also please find the system logs and dumps in the source system at the point of time.
    Can you please let me know if it got fixed.
    Thanks & Regards,
    VR

  • SQL error occurred in the database when acces

    Dear All,
    I am getting following error message while doing file to file scenario.
    source side messages are pickedup and entering into the Queues .receiver side i cant able to see any souce messages.
    SYSFAIL Message is showing in the Queues when i was double click that message its giving following message.
    SQL error occurred in the database when acces
    a table.
    Plz, help me in this regard.
    Thanks,
    Mahesh

    Hi Mahesh,
    Did you get a chance to check the IPC log directories
    Also usually for a sysfail message you can check the smw01
    You will see a bdoc with status F05. What does it say there?
    or
    Is it "Scheduled for outbound processing" or "recorded for outbound processing".
    I guess the message has not been processed, so the next step is to go to transaction SMQ2, and check for info as to why it is not processed.
    If you see a queue status of SYSFAIL, first try resetting it to "Ready" again. If it still fails then, delete that particular LUW. And if you still have some more messages in the queue just click the unlock queue button.
    Reward points if this helps
    Regards
    Pragathi.

Maybe you are looking for