Transport failed with Error Code 12 RDDEXECL

Hi,
I have applied a transport containing infoobjects from dev to qc system and the transport has failed with the erro rcode 12. The error log is as below.
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server sht014a5 were synchronized
Internal session terminated with a runtime error (refer to ST22)
Job cancelled
when I looked at ST22 log for error, I found below error.
What happened?                                                         
    The current application program detected a situation which really  
    should not occur. Therefore, a termination with a short dump was   
    triggered on purpose by the key word MESSAGE (type X).             
How to correct the error                                                            
    Probably the only way to eliminate the error is to correct the program.         
If the error occures in a non-modified SAP program, you may be able to          
    find an interim solution in an SAP Note.                                        
    If you have access to SAP Notes, carry out a search with the following          
    keywords:                                                                               
"MESSAGE_TYPE_X" " "                                                            
    "CL_RSBK_DTP===================CP" or "CL_RSBK_DTP===================CM00U"     
    "IF_RSBK_DTP_DISPLAY~GET_TH_TPL"                                                                               
If you cannot solve the problem yourself and want to send an error              
    notification to SAP, include the following information:                                                                               
1. The description of the current problem (short dump)                                                                               
To save the description, choose "System->List->Save->Local File              
    (Unconverted)".                                                                               
2. Corresponding system log                                                                               
Display the system log by calling transaction SM21.                          
       Restrict the time interval to 10 minutes before and five minutes             
    after the short dump. Then choose "System->List->Save->Local File               
    (Unconverted)".                                                                               
3. If the problem occurs in a problem of your own or a modified SAP             
    program: The source code of the program
       In the editor, choose "Utilities->More                                       
    Utilities->Upload/Download->Download".                                                                               
4. Details about the conditions under which the error occurred or which         
    actions and input led to the error.                                                                               
our system is SAP BI 7.0 and support pack is 23.
Please let me know if any has faced this problem and what was the solution
Thanks
Diwakar

Hi Diwakar,
Re-import the transport after 15 mins.
It should work
Regards,
Venkatesh

Similar Messages

  • [ForumFAQ]How to troubleshoot error "SSPI handshake failed with error code 0x80090324"

    Understanding the problem:
    When connect to SQL Server with Windows authentication, you may receive the following message in the SQL Server error log:
    SSPI handshake failed with error code 0x80090324, state 14 while establishing a connection with integrated security; the connection has been closed.
    Security Support Provider Interface (SSPI) is a set of Windows APIs that allows for delegation and mutual authentication over any generic data transport layer, such as TCP/IP sockets. SQL Server supports Kerberos indirectly through the Windows Security Support
    Provider Interface (SSPI) when SQL Server is using Windows Authentication.
    "SSPI Handshake Failed" error happens usually when connection failed between the server and domain controllers or failed Kerberos Authentication. There are many reason for SSPI Handshake error to appear in SQL Server error log.
    Troubleshot the problem:
    Download and install the Windows error code lookup tool Err.exe to view error descriptions for Windows Error Codes.
    The error code 0x80090324 (SEC_E_TIME_SKEW) means "clock on client and server machines are skewed". In most case, this is a Kerberos issue. Kerberos is using a timestamp to protect against replay attacks. The maximum time skew that can be tolerated
    between a ticket's timestamp and the current time at the KDC is 5 minutes by default.
    Also check the Windows Event Log of client machine, domain controller and the SQL Server machine for existence of W32time error messages.
    The solution:
    Make sure the clock of client server, domain controller and the server running SQL Server are within five minutes of each other. Or Resynchronize the clock by run w32tm /resync on client machine and SQL Server machine.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    This error can happen due to Active Directory configuration issue or Network related issues. Assuming they are fine,
    another reason could be related to fail Kerberos Authentication to connect to SQL Server.
    In Windows 2003 and above, the default method of establishing a connection is Kerberos but if it fails, then connection may be established using NTLM. An error may be registered on SQL Server error log due to Kerberos failure.
    To confirm if you have any database connection using Kerberos authentication, run this on your SQL Server
    SELECT distinct auth_scheme FROM sys.dm_exec_connections
    If you only see NTLM and SQL then, there is no Kerberos connection.
    To use Kerberos, the client and SQL Server must be in the same domain or trusted domains and a Service Principal Name (SPN) must be registered with Active Directory for SQL Server service account.
    You can check if the service account already has SPN, by running this on the SQL Server
    setspn -l <domain\sqlserviceaccount>
    If you don't see anything starting with MSSQLSvc\ then the account is not setup with SPN.
    You can manually register SPN as a Domain Administrator using these commands.
    To      create an SPN for the NetBIOS name of the SQL Server use the following      command:
    setspn –A MSSQLSvc/<SQL Server computer name>:1433      <Domain\Account>
    To      create an SPN for the FQDN of the SQL Server use the following command:
    setspn      -A MSSQLSvc/<SQL Server FQDN>:1433 <Domain\Account>
    If SQL Server service account is granted "Validated write to service principal name" privilege in Active Directory, SQL Server database engine will register itself when it starts and unregisters at shutdown. If you Domain Administrators do not permit this setting
    then you should manually register the SPN and the SSPI error will go away.
    Also the SQL Server service account must be granted "Account is trusted for delegation" privilege in Active Directory. If your SQL Server connects to other SQL Server using Linked Server then the server must also be granted "Trust this computer for delegation
    to any service" privilege.
    For a named instance, you can use the FQDN of the named instance instead of SQL Server FQDN and use the port number.
    For a clustered server, you should use the FQDN of the SQL Server virtual name. In this case you will need two entries, one with port name and one without such as
    setspn -A MSSQLSvc/<Virtual SQL Server FQDN> <Domain\Account>
    setspn -A MSSQLSvc/<Virtual SQL Server FQDN>:1433 <Domain\Account>
    Kerberos authentication works when SQL Server, Service Account and Windows account accessing the SQL Server are in same windows domain. If anyone these are in different domain, there must be bidirectional trust established between the domains, otherwise it
    does not work.

  • ReleaseRequest failed with error code 0x80004005 \ Task Sequence Manager could not release active TS request. code 80004005

    Hi All,
    I am trying to deploy an OS but the deployment is failing part way through. I have searched the logs and identified the error: Task Sequence Manager could not release active TS request. code 80004005
    If anyone could assist with this is would be much appreciated.
    Many thanks
    Logs below:
    <![LOG[Unlocked ActualConfig successfully]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="policyutil.cpp:7898">
    <![LOG[Unlocked policy transaction lock successfully]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="policyutil.cpp:7904">
    <![LOG[Raising event:
    instance of CCM_PolicyAgent_SettingsEvaluationComplete
    ClientID = "GUID:8388E2E2-7642-4436-88D0-FC9335F6D56E";
    DateTime = "20141218122103.273000+000";
    PolicyNamespace = "\\\\wst0339\\root\\ccm\\policy\\machine\\actualconfig";
    ProcessID = 1748;
    ThreadID = 1752;
    ]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="event.cpp:729">
    <![LOG[Successfully submitted event to the Status Agent.]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="event.cpp:747">
    <![LOG[End TS policy evaluation]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="policyutil.cpp:10580">
    <![LOG[Policy evaluation initiated]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:3387">
    <![LOG[Sending success status message]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanager.cpp:659">
    <![LOG[MP server http://LONSVR0150.uk.ham.local. Ports 80,443. CRL=false.]LOG]!><time="12:21:03.273+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4855">
    <![LOG[Setting authenticator]LOG]!><time="12:21:03.288+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4877">
    <![LOG[Set authenticator in transport]LOG]!><time="12:21:03.288+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="libsmsmessaging.cpp:7592">
    <![LOG[Sending StatusMessage]LOG]!><time="12:21:03.304+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="libsmsmessaging.cpp:4020">
    <![LOG[Setting message signatures.]LOG]!><time="12:21:03.320+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="libsmsmessaging.cpp:1292">
    <![LOG[Setting the authenticator.]LOG]!><time="12:21:03.320+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="libsmsmessaging.cpp:1322">
    <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: LONSVR0150.uk.ham.local:80  CCM_POST /ccm_system/request]LOG]!><time="12:21:03.320+00" date="12-18-2014" component="TSManager" context="" type="1"
    thread="1752" file="libsmsmessaging.cpp:8422">
    <![LOG[Request was succesful.]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="0" thread="1752" file="libsmsmessaging.cpp:8758">
    <![LOG[Finalize logging request ignored from process 1748]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tslogging.cpp:1737">
    <![LOG[Waiting for CcmExec service to be fully operational]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4019">
    <![LOG[CcmExec service is up and fully operational]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="utils.cpp:4024">
    <![LOG[Access handle will be read from _SMSTSActiveRequestHandle]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanagerutils.cpp:99">
    <![LOG[Access handle: {9F9B91DA-055D-4B32-9817-52C369835080}]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanagerutils.cpp:111">
    <![LOG[Attempting to release request using {9F9B91DA-055D-4B32-9817-52C369835080}]LOG]!><time="12:21:03.351+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752"
    file="tsmanagerutils.cpp:118">
    <![LOG[CoCreateInstance succeeded]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager" context="" type="1" thread="1752" file="tsmanagerutils.cpp:133">
    <![LOG[pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136)]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager"
    context="" type="0" thread="1752" file="tsmanagerutils.cpp:136">
    <![LOG[ReleaseRequest failed with error code 0x80004005]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager" context="" type="3" thread="1752" file="tsmanagerutils.cpp:136">
    <![LOG[Task Sequence Manager could not release active TS request. code 80004005]LOG]!><time="12:21:03.382+00" date="12-18-2014" component="TSManager" context="" type="2" thread="1752"
    file="tsmanagerutils.cpp:165">
    <![LOG[Process completed with exit code 0]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="TSMBootstrap" context="" type="1" thread="1728" file="commandline.cpp:1098">
    <![LOG[Exiting with return code 0x00000000]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="TSMBootstrap" context="" type="1" thread="1728" file="tsmbootstrap.cpp:1032">
    <![LOG[Process completed with exit code 0]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="commandline.cpp:1098">
    <![LOG[Task sequence completed 0x00000000]LOG]!><time="12:21:03.413+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1384">
    <![LOG[Uninstalling Setup Hook]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1427">
    <![LOG[Removing setup hook from registry.]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="0" thread="788" file="vistasetuphook.cpp:143">
    <![LOG[Successfully removed C:\WINDOWS\system32\OSDGINA.DLL]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1183">
    <![LOG[Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXE]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1183">
    <![LOG[Successfully removed C:\WINDOWS\system32\_SMSOSDSetup]LOG]!><time="12:21:06.552+00" date="12-18-2014" component="OSDSetupHook" context="" type="1" thread="788" file="basesetuphook.cpp:1220">

    4005 can mean a few things,  Some common can be  The wrong BIOS time,  or a a bad Hard drive.   look at those two first. 

  • Installation of Photoshop update 13.1.2 for creative cloud fails with error code U44M1P7 I need help

    I need help installing update 13.1.2 for Photoshop creative cloud, installation fails with error code: U44M1P7. Could someone please help?

    Sorry to bother you.
    I could find the answer after searching previous posts about this language problem.
    Had to change my language in AAM profile and then download PS CS6 again ( english version ).
    Then open the actual Photoshop and in preferences > interface you can besides the Dutch also option for English.
    restart application and Voila.
    Greetz, Jeroen

  • DAG - Backup failing on 1 DB only with error - The Microsoft Exchange Replication service VSS Writer instance ID failed with error code 80070020 when preparing for a backup of database 'DB012'

    Hi Board,
    i´ve search across the board, technet and symantec sites but did not found a hint about my problem.
    we drive a 2 node DAG (Location1-Ex1-mb1 
    Location2-exc1-mb1), on SP2 RU4 patchlevel with 40 Databases.
    Since some time the backup of one - and only one DB - is failing with these events, logged on the Mailboxserver on which the passive DB is hosted.
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:          28.09.2012 00:37:17
    Event ID:      2112
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Location1-Exc1-MB1
    Description: The Microsoft Exchange Replication service VSS Writer instance 1ab7d204-609a-4aea-b0a7-70afb0db38de failed with error code 80070020 when preparing for a backup of database 'DB012'.
    Followed by
    Log Name:      Application
    Source:        MSExchangeRepl
    Date:         
    01.10.2012 03:33:06
    Event ID:      2024
    Task Category: Exchange VSS Writer
    Level:         Error
    Keywords:      Classic
    User:         
    N/A
    Computer:      Location1-Exc1-MB1
    Description:
    The Microsoft Exchange Replication service VSS Writer (Instance 42916d80-36c1-4f73-86d0-596d30226349) failed with error 80070020 when preparing for a backup.
    The backup Application - Symantec Backup Exec 2010 R3 – states, this error
    Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
    Check the Windows Event Viewer for details.
    Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1).
    Symatec suggests within http://www.symantec.com/business/support/index?page=content&id=TECH184095
    to restart the MS Exchange Replication Service – BUT the mentioned eventID
    8229 isn´t present on any of the both Mailboxservers.
    The affected Database is active on Location2-Exc1-Mb1 Server and in an overall healthy state. I found during my research, that below Location2-Exc1-Mb1 Server, there are not removed shadow copies present!
    This confuses me, since all Backups are normally taken from the passive copy of a Database.
    So my questions to the board are:
    * Does anyone is facing similar issues?
    * Can someone explain why snapshots are present on the Mailboxserver hosting the Active Database, whilst the errors are logged on the passive one?
    -          * Does someone know the conditions, why shadows copies remain and
    aren´t removed in a proper manner?
    What can cause the circumstance, that only 1 DB is facing such issues?
    Any suggestion is welcome!
    BR
    Markus

    Hi Lenora,
    I´ve encreases VSS / Exchange Backup Log levels to expert, before starting
    those things i´ve all tried now:
    - Backup from passive DB (forced within Symantec Backup Exec)
    - Backup from active DB (forced within Symantec Backup Exec)
    - Backup from passive DB without GRT enabled (forced within Symantec Backup Exec)
    - Backup from active DB without GRT enabled(forced within Symantec Backup Exec)
    All those attempts failed.
    But brought some more details - the backup against the active DB states, that there is still a backup in progress and therefore this backup is cancelled by VSS.
    The Solution was, that i´ve needed to restart the Exchange Replication Service on the Mailbox Server hosting the passive DB.
    Backups are working again on all DBs!
    THX for your replys.
    Best regards
    Markus

  • The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.

    I am experiencing this error with one of our cluster environment. Can anyone help me in this issue.
    The Cluster Service function call 'ClusterResourceControl' failed with error code '1008(An attempt was made to reference a token that does not exist.)' while verifying the file path. Verify that your failover cluster is configured properly.
    Thanks,
    Venu S.
    Venugopal S ----------------------------------------------------------- Please click the Mark as Answer button if a post solves your problem!

    Hi Venu S,
    Based on my research, you might encounter a known issue, please try the hotfix in this KB:
    http://support.microsoft.com/kb/928385
    Meanwhile since there is less information about this issue, before further investigation, please provide us the following information:
    The version of Windows Server you are using
    The result of SELECT @@VERSION
    The scenario when you get this error
    If anything is unclear, please let me know.
    Regards,
    Tom Li

  • SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has be

    Hello, I have a sql 2005 server, and I am a developer, with the database on my own machine.  It alwayws works for me but after some minutes the other developer cant work in the application
    He got this error
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: 192.168.1.140]
    and When I see the log event after that error, it comes with another error.
    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: 192.168.1.140]
    He has IIS5 and me too.
    I created a user on the domain called ASPSYS with password, then in the IIS on anonymous authentication I put that user with that password, and it works, on both machines.
    and in the connection string I have.
    <add key="sqlconn" value="Data Source=ESTACION15;Initial Catalog=GescomDefinitiva;Integrated Security=SSPI; Trusted_Connection=true"/>
    I go to the profiler, and I see that when he browses a page, the database is accesed with user ASPSYS, but when I browse a page, the database is accesed with user SE\levalencia.
    Thats strange.
    The only way that the other developer can work again on the project is to restart the whole machine. He has windows xp profession, I have windows 2000.
    If you want me to send logs please tellme

    Well here's my problem, maybe you can help. Intermittenly I get a login failed when connecting to a db engine through Server Management Studio using Windows authentication. When this happens the following entries are generated on the server's application event log:
    Event Type:        Error
    Event Source:    MSSQLSERVER
    Event Category:                (4)
    Event ID:              17806
    Date:                     1/14/2009
    Time:                     10:41:31 AM
    User:                     N/A
    Computer:          <server name>
    Description:
    SSPI handshake failed with error code 0x8009030c while establishing a connection with integrated security; the connection has been closed. [CLIENT: <ip address>]
    Event Type:        Failure Audit
    Event Source:    MSSQLSERVER
    Event Category:                (4)
    Event ID:              18452
    Date:                     1/14/2009
    Time:                     10:41:31 AM
    User:                     N/A
    Computer:          <server name>
    Description:
    Login failed for user ''. The user is not associated with a trusted SQL Server connection. [CLIENT: <ip address>]
    I've already ensured that the server is set to mixed authentication mode. Oddly enough, the workaround that I've found is that if I remote desktop into the server, log in and then log back out, Management Studio is suddenly able to connect again. No idea why it works. 
    As I said before, it is intermitten. Some days it errors on login, other days it doesn't and there are no configuration changes between them. Also, both client and server are in the same domain and same site so there is no VPN or anything in between. I'm really quite stumped. Any help would be great, or if you can point me in the right direction of where to look. Thank you in advance!

  • SSIS 2012: SSIS Error Code "Excel Connection Manager" failed with error code 0xC0202009.

    Hi,
    This is kind of weird issue that I am experiencing with excel connection manager in SSIS 2012. This issue occurs sometimes but when I close and re-open SSDT (SQL Server Data Tools - newer BIDS) then this issues goes off temporarily.
    Just FYI, through SSDT environment I executed the package successfully with both settings Run64bit runtime setting to Yes and No when error does not occur.
    So far I have installed
    http://www.microsoft.com/en-us/download/details.aspx?id=13255 (Microsoft Access Database Engine 2010 Redistributable).
    I still remember for older versions of SQL Server (2005 & 2008) that I have executed Excel connection SSIS packages with Run64bit runtime = false i.e. in 32-bit mode. As far as I know I think Excel 64-bit issue has been resolved with SQL Server
    2012 release.
    Here is the detail of error message:
    TITLE: Package Validation Error
    Package Validation Error
    ADDITIONAL INFORMATION:
    Error at Data Flow Task [Excel Source [2]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection
    Manager" failed with error code 0xC0202009.  There may be error messages posted before this with more information on why the AcquireConnection method call failed.
    Error at Data Flow Task [SSIS.Pipeline]: Excel Source failed validation and returned error code 0xC020801C.
    Error at Data Flow Task [SSIS.Pipeline]: One or more component failed validation.
    Error at Data Flow Task: There were errors during task validation.
    Error at Package [Connection manager "Excel Connection Manager"]: SSIS Error Code DTS_E_OLEDBERROR.  An OLE DB error has occurred. Error code: 0x80004005.
    An OLE DB record is available.  Source: "Microsoft Access Database Engine"  Hresult: 0x80004005  Description: "Unspecified error".
     (Microsoft.DataTransformationServices.VsIntegration)
    Here are my environment details:
    SQL Server 2012 {Microsoft SQL Server 2012 (SP1) - 11.0.3368.0 (X64) } , Excel 2010 (32-bit). I am developing SSIS code on Virtual desktops with Windows 7 32-bit OS.
    Also it occurred to me that since Virtual Desktops are on Shared Infrastructure, the source files and SSIS packages (code) can be on Shared drives for e.g. \\<Corpnet>\userdata\<Corp_Users_Grp>\<Username>\Visual Studio 2010\Projects\Integration
    Services Project2\Integration Services Project2\Package.dtsx.
    Does this kind of Shared drives have any impact to give this issue?
    Thanks in advance!
    Ketan
    P.S.: I had look at this forum question -->
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/903bbe1d-e070-4c43-9d3b-0a5193550029/64bit-error-in-excel-connection-manager-in-ssis

    Hi Arthur,
    Thanks for your response.
    Yes, it looks like SSIS still has bunch of issues with Excel files like as follows:
    1) Some times excel source files cannot be parsed by excel source connection manager.
    2) For derive column conversion, we can't replace the existing column. rather, we have to add the derived column as " add as new column" which is tough to manage  while destination mapping.
    3) If an column in excel contains a data which is not of the data type assigned for the column in excel, the excel source reads that data as "null". For the same, we can't validate the data and redirect the erroneous data in reject file.  <-- For
    this we tried IMEX setting also
    4) In multi-tab/sheet excel file, excel source is unable to detect a tab and identify the metadata of the excel.
    I am also checking Microsoft connect for Excel issues with SSIS 2012(https://connect.microsoft.com/SQLServer/SearchResults.aspx?SearchQuery=excel#&&PageIndex=22
    As worst case scenario, I am thinking of converting Excel to CSV file or Flat text file. (http://www.mssqltips.com/sqlservertip/2772/importing-data-from-excel-using-ssis--part-2/).
    Do you think it is advisable to convert Excel into CSV or Flat file.
    Thanks,
    Ketan

  • [Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messa

    Error
    [Load data from excel file [1]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.  The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009.  There
    may be error message
    I am using BIDS Microsoft Visual Studio 2008 and running the package to load the data from excel .
    My machine has 32 bit excel hence have set property to RUN64BITRUNTIME AS FALSE.
    But the error still occurs .
    I checked on Google and  many have used Delay validation property at Data flow task level to true but even using it at both excel connection manager and DFT level it doesnt work
    Mudassar

    Thats my connection string
    Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\SrcData\Feeds\Utilization.xlsx;Extended Properties="Excel 12.0;HDR=NO";
    Excel 2010 installed and its 32 bit edition
    Are you referring to install this component -AccessDatabaseEngine_x64.exe?
    http://www.microsoft.com/en-us/download/details.aspx?id=13255
    Mudassar
    You can try an OLEDB provider in that case
    see
    http://dataintegrity.wordpress.com/2009/10/16/xlsx/
    you might need to download and install ms access redistributable
    http://www.microsoft.com/en-in/download/details.aspx?id=13255
    Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

  • CcmSetup failed with error code 0x80004005 - windows 8.1

    using sccm 2012 r2, trying to push to a windows 8.1 client i get:
    <![LOG[==========[ ccmsetup started in process 7416 ]==========]LOG]!><time="16:05:28.041+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:9437">
    <![LOG[Running on platform X64]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="util.cpp:1837">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\cache\.]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9272" file="ccmsetup.cpp:9281">
    <![LOG[Launch from folder C:\WINDOWS\ccmsetup\]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:721">
    <![LOG[CcmSetup version: 5.0.7958.1000]LOG]!><time="16:05:28.042+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:727">
    <![LOG[In ServiceMain]LOG]!><time="16:05:28.044+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:3365">
    <![LOG[Running on 'Microsoft Windows 8.1 Pro' (6.3.9600). Service Pack (0.0). SuiteMask = 272. Product Type = 18]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="util.cpp:1919">
    <![LOG[Ccmsetup command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:3590">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context=""
    type="1" thread="9468" file="ccmsetup.cpp:3775">
    <![LOG[Command line: "C:\WINDOWS\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="16:05:28.084+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:3776">
    <![LOG[SslState value: 224]LOG]!><time="16:05:28.085+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:4425">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="16:05:28.086+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8617">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8632">
    <![LOG[CCMHTTPSSTATE:    224]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8650">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8668">
    <![LOG[FSP:    ]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8720">
    <![LOG[CCMFIRSTCERT:    1]LOG]!><time="16:05:28.087+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:8778">
    <![LOG[Config file:      C:\WINDOWS\ccmsetup\MobileClientUnicode.tcf]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:4539">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4540">
    <![LOG[MSI log file:     C:\WINDOWS\ccmsetup\Logs\client.msi.log]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468"
    file="ccmsetup.cpp:4541">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="consto" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="224" CCMFIRSTCERT="1"]LOG]!><time="16:05:28.088+00"
    date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4542">
    <![LOG[Source List:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4550">
    <![LOG[                  \\TA-SRV-SC.constoplc.local\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
    context="" type="1" thread="9468" file="ccmsetup.cpp:4557">
    <![LOG[                  \\TA-SRV-SC.constoPLC.LOCAL\SMSClient]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup"
    context="" type="1" thread="9468" file="ccmsetup.cpp:4566">
    <![LOG[MPs:]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:4569">
    <![LOG[                  TA-SRV-SC.constoplc.local]LOG]!><time="16:05:28.088+00" date="01-15-2014" component="ccmsetup" context=""
    type="1" thread="9468" file="ccmsetup.cpp:4584">
    <![LOG[MapNLMCostDataToCCMCost() returning Cost 0x1]LOG]!><time="16:05:28.091+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmutillib.cpp:5479">
    <![LOG[No version of the client is currently detected.]LOG]!><time="16:05:28.093+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:2748">
    <![LOG[Folder 'Microsoft\Configuration Manager' not found. Task does not exist.]LOG]!><time="16:05:28.094+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="wintask.cpp:622">
    <![LOG[Updated security on object C:\WINDOWS\ccmsetup\.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="0" thread="9468" file="ccmsetup.cpp:9281">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent.]LOG]!><time="16:05:28.095+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:9763">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9468" file="ccmsetup.cpp:1995">
    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='328' will not be sent.]LOG]!><time="16:05:28.118+00" date="01-15-2014" component="ccmsetup" context="" type="1"
    thread="9468" file="ccmsetup.cpp:9763">
    <![LOG[CcmSetup failed with error code 0x80004005]LOG]!><time="16:05:28.119+00" date="01-15-2014" component="ccmsetup" context="" type="1" thread="9272" file="ccmsetup.cpp:10879">
    any ideas why its failing?

    Hi,
    I've seen the same error on a customer where we had Windows Intune Client (SCCM) installed previously. Did you try it on a newly deployed computer? If you had Intune or another CCM client on it previously make sure you clean it up. Here is a well formulated
    instruction:
    http://douwevanderuit.wordpress.com/2014/01/30/removing-windows-intune-client/
    Usually when deploying to many clients we use a startup script, there is a great one that Jason Sandys made in the link below.
    http://blog.configmgrftw.com/configmgr-client-startup-script/
    There should be no problems deploying SCCM 2012 R2 clients on Windows 8.1 unless there is something wrong with either the setup or the client computer.
    All the best, Jesper Hassing - MCTS SCCM 2012 - MCSA 2012 Server - MCP

  • Windows Server 2008 R2 Service Pack 1 installation failed with error code 0x800f0a12

    Hello,
    I'm facing problem to install windows server 2008 R2 SP1. I cannot install SP1. In this server have running Exchange 2010 server. to update Win2008 R2 SP1 facing the following error:
    1. Service Pack installation failed with error code 0x800f0a12.
    2. Installation Failure: Windows failed to install the following update with error 0x80070643: Windows Server 2008 R2 Service Pack 1 for x64-based Systems (KB976932).
    Please suggest

    Please run the system update readiness tool.
    http://windows.microsoft.com/en-us/windows7/What-is-the-System-Update-Readiness-Tool?SignedIn=1
    Then post the complete contents of;
    %SYSTEMROOT%\Logs\CBS\CheckSUR.log
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • EvtFormatMessage function fails with error code 15033 (ERROR_EVT_MESSAGE_LOCALE_NOT_FOUND) on non-English Windows OS

    I have an App which subscribes to Windows events and if it is matching the filter criteria, it reports it.
    I have observed a strange problem on non-English windows 2008 OS. 
    If the Windows event is of source = EventLog (e.g. Event ID 1102: Security log was cleared), then EvtFormatMessage fails with error code 15033. But if the event is of any other source (e.g. Microsoft Security Auditing), then it works absolutely fine.
    While calling EvtOpenPublisherMetadata, I have created locale ID as MAKELCID(MAKELANGID(0x09,0x01) i.e. Primary language = LANG_ENGLISH and Sub Language = SUBLANG_DEFAULT.
    I want events details in English only and hence primary language is put as English. If I change this macro to have primary language as LANG_CHINESE and sub language as SUBLANG_CHINESE_SIMPLIFIED, then it works fine but gives back event details in native
    OS language (Chinese in this case). That's not a desirable output for me.
    Following is the way I'm calling EvtFormatMessage 
    EvtFormatMessage(hMetaData, hEvent[0], -1, 0, NULL,
                                   1 /* EvtFormatMessageEvent */, 
                                   m_pTextBufferSize/sizeof(WCHAR),
                                   m_pTextBuffer, &dwBuffUsed);
    A work-around for this is to install a MUI pack for English language. If the MUI pack is installed then it works fine. But I cannot enforce users to have this pack installed on all their systems.
    My question is  why this API is working for some set of Events whereas failing for some specific Events? Am I doing something wrong?
    Any help would be appreciated.
    TIA,
    Regards,
    Yogesh
     

    Was on vacation and hence the delay in replying.
    As mentioned earlier, while calling EvtOpenPublisherMetadata, I have created locale ID as MAKELCID(MAKELANGID(0x09,0x01)
    i.e. Primary language = LANG_ENGLISH and Sub Language = SUBLANG_DEFAULT.  If I change this macro
    to have primary language as LANG_CHINESE and sub language as SUBLANG_CHINESE_SIMPLIFIED, then it works fine but gives back event details in native OS language (Chinese in this case).
    This is not an option for me as I want event details in English language only.
    Regards,
    Yogesh
    Regards, Yogesh

  • The user '*' preference item in the 'User - 6th Form Students Policy {E03166E7-A848-48B5-AA93-97B848AA9C13}' Group Policy object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppres

    I am looking at an issue with users not getting specific group policies. 
    After searching a number of client computers I found that the following error
    The user '*' preference item in the 'User - 6th Form Students Policy {E03166E7-A848-48B5-AA93-97B848AA9C13}' Group Policy object did not apply because it failed with error code '0x80070003 The system cannot find the path specified.' This error was suppressed.
    I can find the folder in the Sysvol folder on all of the domain controllers. 
    The issue with end users seems to be that the proxy settings for internet explorer is not being applied. 
    Potential problems?
    one folder in sysvol entry is empty 
    \\<server>\SYSVOL\<domain.name>\Policies\{E03166E7-A848-48B5-AA93-97B848AA9C13}\User\microsoft\IEAK\LOCK
    or is this our issue
    The old method of configuring proxy settings  to Internet Explorer 9 has changed?
    https://support2.microsoft.com/kb/2530309?wa=wsignin1.0 
    http://thommck.wordpress.com/2013/11/08/the-new-way-to-configure-internet-explorer-proxy-settings-with-group-policy/

    Hi all 
    In administering this policy I am a little confused. 
    We have a policy that distributes proxy settings in the internet explorer maintenance settings section - however when opening this policy up in GPO editor the internet explorer maintenance section is not present.
    I plan to apply the settings via User/preferences/control panel settings/ internet settings (or registry settings from article) however I am unable to edit the settings for internet explorer maintenance and these will persist. Ideas????

  • CC app manager update  failed with error code 50 after reaching about 35%

    Trying to update the CC app manager. The update is always very slow  (I have ATT DSL, lowest level) and I usually terminate it after an hour or so. Today I let it run and it failed with error code 50 after reaching about 35%. Any ideas?

    Update to my original post. I read through some of the suggestions that I found in other threads for fixing this problem, and it appears that this has been an ongoing issue. Numerous fixes have been suggested, some very convoluted, difficult, and involved, including those that came from the customer support folks.  I passed on those as this should be something simple. How Adobe manages to let updating of their own software turn into an ongoing problem is beyond me and sort of defeats the purpose of subscribing. I then noticed that a simple fix had been suggested a few times, so I tried that.
    The user suggested fix that worked for me was:
    1) Restarted computer (Asus Windows 7 i3 machine for me) in Safe Mode with Networking. Logged into my separate Admin account just in case.
    2) Started the creative cloud desktop app.
    3) The app said it needed to be updated. I hit the update button.
    4) Update started and proceeded slowly as it had in many previous failed attempts (I have ATT DSL at the slowest level, but it is not dial-up). Within about 30 min, the update succeeded.
    5) Restarted computer in normal mode.
    6) The creative cloud desktop app now did not say it needs to be updated, and I can update my other apps normally. Have not updated LR or PS yet, but plan to try. If that fails, I may try doing it in the Safe Mode with Networking.
    So, that was relatively painless and much much simpler than many of the other suggestions I saw. Do not know if it will work for everyone, but I wanted to post the fix that worked for me. Thank you very much to the 2 or 3 users who had suggested this fix earlier (sorry, I did not write down your IDs, but the threads can be found by searching for creative cloud desktop update fail error code 50). Hope this saves some people a lot of time.

  • SCCM 2012 CU2 OSD forest trust: ReleaseRequest failed with error code 0x87d00317

    Hello,
    Actually i have a difficult Problem with my SCCM 2012 R2 CU2 Windows 7 x64 SP1 Tasksequence:
    I get the folowing error in smsts.log:
    ::RegQueryValueExW(hSubKey, szReg, NULL, NULL, NULL, &dwSize), HRESULT=80070002 (e:\qfe\nts\sms\framework\tscore\utils.cpp,811) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    GetTsRegValue() is unsuccessful. 0x80070002. TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    End program:  TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Finalize logging request ignored from process 1736 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Waiting for CcmExec service to be fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    CcmExec service is up and fully operational TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Access handle will be read from _SMSTSActiveRequestHandle TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Access handle: {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Attempting to release request using {B699D570-B2BF-4874-8CB7-3B208B380969} TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    CoCreateInstance succeeded TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    pISoftwareExecutionRequestMgr->ReleaseRequest(ActiveRequestGUID), HRESULT=87d00317 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanagerutils.cpp,136) TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    ReleaseRequest failed with error code 0x87d00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Task Sequence Manager could not release active TS request. code 87D00317 TSManager 9/5/2014 1:20:35 PM 1740 (0x06CC)
    Here is the complete smsts.log: http://1drv.ms/1pwTEBf
    To explain the Problem in Detail:
    The SCCM Primary Site Server and the Clients are in different trusted (bidirectional) forests!
    Everythings working fine in this Scenario, I can install SCCM Agent on the Clients with Manual ccmsetup and with Client Push Installation. Additionally i can deploy Software Updates and so on... only OSD is crashing in the releaserequest step.
    During my Tasksequence new Clients are joined to Domain A while SCCM Primary Site Server is installed in Domain B
    If I change my TS and let the Clients also join Domain B everything works without any Problems and the Tasksequence finish without any Errors.
    My Problem must be related to the different Domains and the forest trust.
    My Setup:
    MP published to DNS in both domains
    Schema Extended in both domains
    System Management Container published and verified in both domains
    ccmsetup Parameters in TS: ccmsetup SMSMP=sccm.domain.b FSP=sccm.domain.b DNSSUFFIX=Domain.b
    Network Access account configured with Domain B account
    Domain Join account has create Computer rights on the OU in Domain A (Domain join is successful)
    DNs conditional forwarders configured in both Domains and DNS resolutin is working in both directions
    Any suggestions?
    Many thanks.
    regards,
    Christian

    Hi Christian,
    So do you actual get an error message in your TS or is it just failing to join Domain B?  (Could be both if the machines fails to join the domain).
    Can you review netsetup.log on the machines after the issue and see what error message you might be getting during the domain join process?
    Also, if it a domain join issue, can you try manually joining to domain B using the same service account?

Maybe you are looking for