ODI 11.1.1.6.4 - Interface failed at SnpsSqlUnload - Unload source data Step

Hi Experts -
We are getting error during interface execution in ODI 11.1.1.6.4. We are unable to find the root cause.
Interface is using customized LKM (LKM SQL to Oracle (SQL*Loader). This LKM is basically connecting to SQLSERVER fetching required rows from the table and creating a LDR file. Post this data from LDR file is then populated in Stage Table (Oracle DB).
We are getting Error while connecting to SQLSERVER at step - Unload Source Data (It uses: SnpsSqlUnload command)
This step is connecting to SQLSERVER and LDR file also getting generated.
Any suggestions?
Regards,
Andy
Error Message in ODI-
================================
java.sql.SQLNonTransientConnectionException: [FMWGEN][SQLServer JDBC Driver]The DBMS returned an unspecified error.  The command code was 224.
at weblogic.jdbc.sqlserverbase.ddb_.b(Unknown Source)
at weblogic.jdbc.sqlserverbase.ddb_.a(Unknown Source)
at weblogic.jdbc.sqlserverbase.ddb9.b(Unknown Source)
at weblogic.jdbc.sqlserverbase.ddb9.a(Unknown Source)
at weblogic.jdbc.sqlserver.tds.ddr.c(Unknown Source)
at weblogic.jdbc.sqlserver.tds.ddr.a(Unknown Source)
at weblogic.jdbc.sqlserver.tds.ddq.a(Unknown Source)
at weblogic.jdbc.sqlserver.tds.ddr.a(Unknown Source)
at weblogic.jdbc.sqlserver.tds.ddr.a(Unknown Source)
at weblogic.jdbc.sqlserver.ddh.a(Unknown Source)
at weblogic.jdbc.sqlserverbase.ddcq.k(Unknown Source)
at weblogic.jdbc.sqlserverbase.dddm.next(Unknown Source)
at com.sunopsis.dwg.tools.SqlUnload.unloadDataDe(SqlUnload.java:711)
at com.sunopsis.dwg.tools.SqlUnload.actionExecute(SqlUnload.java:357)
at com.sunopsis.dwg.function.SnpsFunctionBase.execute(SnpsFunctionBase.java:276)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execIntegratedFunction(SnpSessTaskSql.java:3437)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.executeOdiCommand(SnpSessTaskSql.java:1509)
at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:44)
at oracle.odi.runtime.agent.execution.cmd.OdiCommandExecutor.execute(OdiCommandExecutor.java:1)
at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:558)
at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:464)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)
at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1889)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$2.doAction(StartScenRequestProcessor.java:580)
at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:513)
at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$StartScenTask.doExecute(StartScenRequestProcessor.java:1073)
at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:126)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$1.run(DefaultAgentTaskExecutor.java:49)
at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
at oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor.executeAgentTask(DefaultAgentTaskExecutor.java:41)
at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.doExecuteAgentTask(TaskExecutorAgentRequestProcessor.java:92)
at oracle.odi.runtime.agent.processor.TaskExecutorAgentRequestProcessor.process(TaskExecutorAgentRequestProcessor.java:83)
at oracle.odi.runtime.agent.support.DefaultRuntimeAgent.execute(DefaultRuntimeAgent.java:68)
at oracle.odi.runtime.agent.servlet.AgentServlet.processRequest(AgentServlet.java:512)
at oracle.odi.runtime.agent.servlet.AgentServlet.doPost(AgentServlet.java:442)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:326)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534)
at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)

So in the Operator section on step 6 'Load data into Planning' I get the below.  Fields 4 and 5 aren't even in the Select statement.  Only the mapped fields are showing up here.  My view has two fields that when you sort by in Excel do exactly what I need.  We just can't figure out how to get those fields to/from staging area.  They can't be input into Planning as they would have nowhere to go.  Maybe they can be ignored during dimension build?
from com.hyperion.odi.common import ODIConstants
from com.hyperion.odi.connection import HypAppConnectionFactory
from java.lang import Class
from java.lang import Boolean
from java.sql import *
from java.util import HashMap
# Get the select statement on the staging area:
sql= """select   C1_ACCOUNT    "Account",C2_PARENT    "Parent",C3_ALIAS__DEFAULT    "Alias: Default",C4_DATA_STORAGE    "Data Storage",C5_UDA    "UDA",C6_DATA_TYPE    "Data Type",C7_ACCOUNT_TYPE    "Account Type",C8_TIME_BALANCE    "Time Balance",C9_VARIANCE_REPORTING    "Variance Reporting",C10_AGGREGATION__PROJECTS_    "Aggregation (Projects)" from "C$_0Account"  where     (1=1)     """
srcCx = odiRef.getJDBCConnection("SRC")
stmt = srcCx.createStatement()
srcFetchSize=30
stmt.setFetchSize(srcFetchSize)
rs = stmt.executeQuery(sql)
#load the data
stats = pWriter.loadData(rs)
#close the database result set, connection
rs.close()
stmt.close()

Similar Messages

  • Interfaces fails twice but executes correclty from next time

    Hi,
    I have interfaces which are coping data from MS Access tables to oracle tables.
    NOw here i am facing somewhat strange issue.
    I have 3 environments Dev,Test and PROD.
    Now when i am moving scenarios from TEST to PROD ,the interfaces fails for first 2 times giving following error
    ODI-1227: Task SrcSet0 (Loading) fails on the source MICROSOFT_ACCESS connection MTP_Products.
    Caused By: java.sql.SQLException: [Microsoft][ODBC Driver Manager] Invalid string or buffer length
         at sun.jdbc.odbc.JdbcOdbc.createSQLException(JdbcOdbc.java:6957)
         at sun.jdbc.odbc.JdbcOdbc.standardError(JdbcOdbc.java:7114)
         at sun.jdbc.odbc.JdbcOdbc.SQLGetDataString(JdbcOdbc.java:3907)
         at sun.jdbc.odbc.JdbcOdbcResultSet.getDataString(JdbcOdbcResultSet.java:5698)
         at sun.jdbc.odbc.JdbcOdbcResultSet.getString(JdbcOdbcResultSet.java:354)
    and executes correctly next time.
    Although i have specified fields data types and its legth more than required.
    Let me know if anyone has come across such issues or anyone has idea about something like it.
    Help appreciated.
    Thanks,
    Mahesh

    Download a new copy of the Firefox program: http://www.mozilla.com/firefox/all.html
    Trash the current Firefox application to do a clean reinstall.
    Install the new version that you have downloaded.
    Your profile data is stored elsewhere in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Firefox Profile Folder], so you won't lose your bookmarks and other personal data.

  • ODI 11.1.1.5 Installation is failing in HP UX

    Hi All,
    ODI 11.1.1.5 Installation is failing due to below error.
    OS: HP UX 11.3i Itanium system
    JDK 6
    Error:
    /usr/lib/dld.sl: Can't find path for shared library: libjli.sl
    /usr/lib/dld.sl: No such file or directory
    [HP ARIES32]: Error occured while writing core file for 32-bit
    [HP ARIES32]: PA-RISC application /opt/java6/bin/java (got signal 6).
    [HP ARIES32]: Core file may not be correct.
    Abort
    If any one have the solution, kindly share.

    Hi,
    I'm still facing this problem. Any help?
    Thanks,
    Harish

  • Error when adding multiple source data stores in ODI Interface

    I am trying to create an ODI Interface with couple of source tables and one target table. Say for example I am using the following data structure in my target table.
    Order (Target Table)
    order id
    product id
    customer id
    address id
    warehouse id
    shipment id
    for the above target table i need to extract data from each of the following source tables.
    orderitem
    product
    customer
    address
    warehouse
    shipment
    Total 6 source tables i need to join however and load data for target table.
    When I drag source data stores in to ODI interface mapping tab It throws the following Null Pointer Error. Due to this error I am not able to map target table with all the source tables.
    Please suggest me what could be the reason for the error.
    Error:
    java.lang.NullPointerException
         at oracle.odi.interfaces.interactive.support.clauseimporters.ClauseImporterDefault.importClauses(ClauseImporterDefault.java:81)
         at oracle.odi.interfaces.interactive.support.actions.InterfaceActionAddSourceDataStore.performAction(InterfaceActionAddSourceDataStore.java:124)
         at oracle.odi.interfaces.interactive.support.InteractiveInterfaceHelperWithActions.performAction(InteractiveInterfaceHelperWithActions.java:845)
         at oracle.odi.interfaces.interactive.support.InteractiveInterfaceHelperWithActions.performAction(InteractiveInterfaceHelperWithActions.java:821)
         at oracle.odi.ui.OdiSdkEntityFactory.dropSourceDataStore(OdiSdkEntityFactory.java:523)
         at oracle.odi.ui.etlmodeler.diag.dragdrop.DiagramNodeDropHandler.dropObjects(DiagramNodeDropHandler.java:150)
         at oracle.diagram.framework.dragdrop.handler.DelegateChooserDropHandler.dropSelected(DelegateChooserDropHandler.java:386)
         at oracle.modeler.dnd.ModelerTCDropHandler.access$001(ModelerTCDropHandler.java:69)
         at oracle.modeler.dnd.ModelerTCDropHandler$3.run(ModelerTCDropHandler.java:288)
         at oracle.modeler.dif.GraphicAdder.addImpl(GraphicAdder.java:387)
         at oracle.modeler.dif.GraphicAdder.addAndLayoutImpl(GraphicAdder.java:372)
         at oracle.modeler.dif.GraphicAdder.addSelectAndLayout(GraphicAdder.java:348)
         at oracle.modeler.dnd.ModelerTCDropHandler.dropSelected(ModelerTCDropHandler.java:284)
         at oracle.diagram.framework.dragdrop.handler.DelegateChooserDropHandler.drop(DelegateChooserDropHandler.java:150)
         at oracle.diagram.framework.dragdrop.DefaultDropPlugin.drop(DefaultDropPlugin.java:115)
         at oracle.modeler.dnd.ModelerDropPlugin.drop(ModelerDropPlugin.java:100)
         at oracle.diagram.framework.dragdrop.DropTargetHelper.drop(DropTargetHelper.java:188)
         at oracle.diagram.framework.dragdrop.ManagerViewDragAndDropController$MyDropTargetListener.drop(ManagerViewDragAndDropController.java:802)
         at java.awt.dnd.DropTarget.drop(DropTarget.java:434)
         at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(SunDropTargetContextPeer.java:519)
         at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(SunDropTargetContextPeer.java:832)
         at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(SunDropTargetContextPeer.java:756)
         at sun.awt.dnd.SunDropTargetEvent.dispatch(SunDropTargetEvent.java:30)
         at java.awt.Component.dispatchEventImpl(Component.java:4487)
         at java.awt.Container.dispatchEventImpl(Container.java:2099)
         at java.awt.Component.dispatchEvent(Component.java:4460)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4577)
         at java.awt.LightweightDispatcher.processDropTargetEvent(Container.java:4312)
         at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4163)
         at java.awt.Container.dispatchEventImpl(Container.java:2085)
         at java.awt.Window.dispatchEventImpl(Window.java:2478)
         at java.awt.Component.dispatchEvent(Component.java:4460)
         at java.awt.EventQueue.dispatchEvent(EventQueue.java:599)
         at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269)
         at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169)
         at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161)
         at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)

    Hello,
    does somebody have a solution for this issue?
    I am new to ODI and have the same problem. I am using ODI Designer Standalone Edition Version 11.1.1.
    Maybe there is something wrong with my configuration, maybe I am doing something wrong while creating the mapping graphically. It does not help to save and re-open the mapping. Also it does not help to re-reverse engineer the objects. Also it does not seem to have something to do with the number of objects joined (some objects seem to always cause this error, with some the error starts when there are 10 or more objects on the map before they are added).
    One possible workaround i have found is to do it all on the quick-edit tab by one by one creating the joins and mappings (+source or lookup joins and filter mapping). It seems to work with my configuration, but drag&drop functionality on the mapping tab would sometimes be faster, more convenient and just more human like.
    Br,
    Jaanus

  • Failover interface failed

    Hi,
       I have 2 ASA 5520 firewall configured with HA(Failover). but some time my primary firewall goes down standby firewall doesnt come active. i found below log from primary firewall..what is the reason & what is the mining of reason code of 4...
    Nov 30 2012 14:07:47: %ASA-1-105002: (ASA) Enabling failover.
    Nov 30 2012 14:08:43: %ASA-1-105043: (Primary) Failover interface failed
    Nov 30 2012 14:08:56: %ASA-1-103001: (Primary) No response from other firewall (reason code = 4).
    After i hard reboot my standby firewall below log had been generated..
    Nov 30 2012 15:51:57: %ASA-1-105042: (Primary) Failover interface OK
    Nov 30 2012 15:52:02: %ASA-1-709003: (Primary) Beginning configuration replication: Send to mate.
    Nov 30 2012 15:52:15: %ASA-1-709004: (Primary) End Configuration Replication (ACT)
    Please assist....
    Regards
    Suhas

    Hi,
    The explanation for that can be found in the ASAs syslog messages document.
    Here it is
    103001 Error Message    %ASA-1-103001: (Primary) No response from other firewall (reason
    code = code).
    Explanation    This is a failover message, which is displayed if the primary unit is unable to  communicate with the secondary unit over the failover cable. (Primary) can also be listed as  (Secondary). for the secondary unit. Table 1-2 lists the reason codes and the descriptions to  determine why the failover occurred.
    Table 1-2     Reason Codes
    Reason Code
    Description
    1
    The local unit is not receiving the hello packet on the failover LAN  interface when LAN failover occurs or on the serial failover cable when  serial failover occurs, and declares that the peer is down.
    2
    An interface did not pass one of the four failover tests, which are as  follows: 1) Link Up, 2) Monitor for Network Traffic, 3) ARP, and 4)  Broadcast Ping.
    3
    No proper ACK for 15+ seconds after a command was sent on the serial cable.
    4
    The local unit is not receiving the hello packet on the failover LAN and  other data interfaces and it is declaring that the peer is down.
    5
    The failover LAN interface is down, and other data interfaces are not  responding to additional interface testing. In addition, the local unit  is declaring that the peer is down.
    Recommended Action    Verify that the failover cable is connected correctly and both units have the  same hardware, software, and configuration. If the problem persists, contact the Cisco TAC.
    Are you saying that the Primary ASA loses all connectivity to the Secondary ASA (looking at the log messages). Judging by the above Cisco description it would mean the Primary ASA isnt getting Failover Hellos through any of the monitored interfaces which again would make it seem like the Secondary Firewall is expriencing some problems.
    - Jouni

  • Is my SATA Interface failing?

    History:
    Macbook Pro 13" (late 2008 with Snow Leopard installed) would not shutdown. I left it on overnight hoping it would shutdown but it was still at a gray screen in the morning. So I force-powered it off by holding the power button. When powering on again, all I got was the flashing folder with a question mark in it. Turns out the hard drive had a couple of busted blocks which happened to be right where the partition table and the allocation file (B Tree) seemed to be. I replaced the drive with a new one, installed OSX Lion (10.7.2 from App Store) on it and copied over the data from my backups. Then I got massive system freezes; spinning beach balls while typing. Sometimes it would resolve itself after a few minutes, sometimes it wouldn't, even after a few hours.
    Checking the console, I found a few of these:
    kernel[0]: disk0s2: I/O error
    I installed SMARTReporter, it said the drive was fine but it notified me every time when these i/o errors occurred, which was about once every hour or so.
    So I ran the long Apple Hardware Test, took about 5 hours and I got just one error:
    4HDD/11/40000004:SATA(0,0)
    After some googling, everyone seemed to agree that's because of a failing hard drive, possibly a failing SATA interface. To rule out the failing SATA interface, I popped in an old 80 GB SATA drive into the Macbook Pro and ran the extended hardware test again: "no troubles found". I though "great, my replacement hard drive is bad, I'll just send it in and get another one".
    But after simply surfing around with Safari (no extensions, just flash 11), the the whole system Freezes up again. Spinning Beachball, most apps (including Console, Mail, Safari) not responding at all, all I can do is move windows around. Can't even look at the console because the window was just white. But syslogd too 170% CPU according to application monitor.
    After a reboot (nothing happens even if I wait for a whole day for it to do its thing), everything seems fine but spotlight starts indexing everything.
    Here's my Questions:
    - How can I avoid these complete system freezes?
    - How can I make sure it's not my SATA interface that's causing it? Would running the system via USB rule that out? I can't keep returning hard drives all the time if they're not actually defective.
    Here's the log:
    1/2/12 10:54:26.426 PM mdworker32: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/2/12 10:54:27.253 PM com.apple.mdworker.pool.0: ImageIO: <ERROR>  readICCData Embedded profile header length is greater than data length.
    1/2/12 10:54:27.326 PM com.apple.mdworker.pool.0: ImageIO: <ERROR>  readICCData Embedded profile header length is greater than data length.
    1/2/12 10:57:01.580 PM com.apple.mdworker.pool.0: PSSniffer error: No such file or directory
    1/2/12 10:57:01.594 PM com.apple.mdworker.pool.0: PSSniffer error: Undefined error: 0
    1/2/12 10:57:33.600 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.601 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.603 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.605 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.607 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.608 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.610 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.612 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.614 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.617 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.618 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 10:57:33.619 PM com.apple.mdworker.isolation.0: FlateDecode: decoding error.
    1/2/12 11:00:20.277 PM com.apple.mdworker.isolation.0: syntax error, unexpected DICTSTART.
    1/2/12 11:01:12.129 PM com.apple.mdworker.isolation.0: syntax error, unexpected DICTSTART.
    1/2/12 11:01:12.130 PM com.apple.mdworker.isolation.0: syntax error, unexpected DICTSTART.
    1/2/12 11:01:12.130 PM com.apple.mdworker.isolation.0: syntax error, unexpected DICTSTART.
    1/2/12 11:02:40.156 PM mdworker32: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    (there's about a thousand of those DICTSTART errors until I shut the machine off and reboot.)
    1/2/12 11:33:00.927 PM mDNSResponder:  13: Could not write data to client because of error - aborting connection
    1/2/12 11:33:10.337 PM UserEventAgent: [11] error in getAndLockContext: open returned -1 (errno=2)  file was /private/var/servermgrd//servermgr_certs.lock
    1/2/12 11:33:10.340 PM UserEventAgent: [11] error in getAndLockContext: open returned -1 (errno=2)  file was /private/var/servermgrd//servermgr_certs.lock
    1/2/12 11:33:11.128 PM WindowServer: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/2/12 11:33:28.799 PM talagent: kCGErrorIllegalArgument: CGSFlushSurfaceWithOptions: Invalid window 0x1d
    1/2/12 11:33:28.799 PM talagent: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/2/12 11:43:24.167 PM mdworker32: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    1/2/12 11:43:25.591 PM com.apple.mdworker.pool.0: ImageIO: <ERROR>  readICCData Embedded profile header length is greater than data length.
    1/2/12 11:43:25.659 PM com.apple.mdworker.pool.0: ImageIO: <ERROR>  readICCData Embedded profile header length is greater than data length.
    1/2/12 11:45:25.945 PM com.apple.mdworker.pool.0: PSSniffer error: No such file or directory
    1/2/12 11:45:25.992 PM com.apple.mdworker.pool.0: PSSniffer error: Undefined error: 0
    Here's the system.log
    Jan  2 22:45:13 MyUserNames-MacBook-Pro mds[34]: (Warning) Server: No stores registered for metascope "kMDQueryScopeComputer"
    Jan  2 22:54:26 MyUserNames-MacBook-Pro mdworker32[625]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    Jan  2 22:54:27 MyUserNames-MacBook-Pro com.apple.mdworker.pool.0[613]: ImageIO: <ERROR>  readICCData Embedded profile header length is greater than data length.
    Jan  2 22:54:38: --- last message repeated 1 time ---
    Jan  2 22:54:38 MyUserNames-MacBook-Pro mdworker[613]: *** Failed to decode multipart/related data, treating as binary
    Jan  2 22:55:25 MyUserNames-MacBook-Pro mdworker[613]: *** Failed to decode multipart/related data, treating as binary
    Jan  2 22:55:29: --- last message repeated 3 times ---
    Jan  2 22:55:29 MyUserNames-MacBook-Pro mdworker[613]: Invalid char _ for PropertyName in line 47
    Jan  2 22:55:57: --- last message repeated 7 times ---
    Jan  2 22:55:57 MyUserNames-MacBook-Pro mdworker[613]: Invalid char _ for PropertyName in line 49
    Jan  2 22:55:57 MyUserNames-MacBook-Pro mdworker[613]: Invalid char _ for PropertyName in line 47
    Jan  2 22:55:57: --- last message repeated 1 time ---
    Jan  2 22:55:57 MyUserNames-MacBook-Pro mdworker[613]: Invalid char _ for PropertyName in line 38
    Jan  2 22:56:27: --- last message repeated 1 time ---
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 32784; should be 32254.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 84269; should be 50936.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 131812; should be 46992.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 200580; should be 68216.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 241736; should be 40604.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 32784; should be 32254.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 84269; should be 50936.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 131812; should be 46992.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 200580; should be 68216.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: invalid stream length 241736; should be 40604.
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.pool.0[613]: PSSniffer error: No such file or directory
    Jan  2 22:57:01 MyUserNames-MacBook-Pro com.apple.mdworker.pool.0[613]: PSSniffer error: Undefined error: 0
    Jan  2 22:57:16 MyUserNames-MacBook-Pro mdworker[613]: *** Failed to decode multipart/related data, treating as binary
    Jan  2 22:57:33: --- last message repeated 3 times ---
    Jan  2 22:57:33 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: FlateDecode: decoding error.
    Jan  2 22:58:36: --- last message repeated 11 times ---
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:00:20 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: *** process 624 exceeded 500 log message per second limit  -  remaining messages this second discarded ***
    Jan  2 23:01:04 MyUserNames-MacBook-Pro Camino[439]: AVF error: fail to setup QT accelerator
    Jan  2 23:01:04 MyUserNames-MacBook-Pro Camino[439]: HDDec_Thread_HWSliceDecoder_SampleID: CreateGPUInterface renderer 1040004
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:09 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:10 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:10 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:10 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: *** process 624 exceeded 500 log message per second limit  -  remaining messages this second discarded ***
    Jan  2 23:01:11 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:11 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:11 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:01:11 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: failed to parse embedded CMap.
    Jan  2 23:01:11 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[624]: syntax error, unexpected DICTSTART.
    Jan  2 23:49:45 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[234]: failed to parse embedded CMap.
    Jan  2 23:49:45 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[234]: syntax error, unexpected DICTSTART.
    Jan  2 23:49:45 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[234]: failed to parse embedded CMap.
    Jan  2 23:49:45 MyUserNames-MacBook-Pro com.apple.mdworker.isolation.0[234]: *** process 234 exceeded 500 log message per second limit  -  remaining messages this second discarded ***
    Jan  2 23:50:32 MyUserNames-MacBook-Pro mdworker32[257]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    Jan  2 23:51:43 MyUserNames-MacBook-Pro mdworker[200]: Invalid char _ for PropertyName in line 72
    Jan  2 23:51:43: --- last message repeated 1 time ---
    Jan  2 23:51:43 MyUserNames-MacBook-Pro mdworker[200]: Invalid char _ for PropertyName in line 79
    Jan  2 23:51:43: --- last message repeated 3 times ---
    Jan  2 23:51:43 MyUserNames-MacBook-Pro mdworker[200]: Invalid char _ for PropertyName in line 63
    Jan  2 23:52:33: --- last message repeated 1 time ---
    Jan  3 00:07:20 MyUserNames-MacBook-Pro mdworker[200]: *** Failed to decode multipart/related data, treating as binary
    Jan  3 00:07:50: --- last message repeated 2 times ---

    Okay, 250GB drives (other than SSDs and SAS) are old and today's drives really are nice cheap and fast(er). Yes, 1/3 free space sounds fine.
    why bother and waste time with repairing (receipt) permissions? there isn't anything wrong with them.
    Clone your system, repair with Disk Warrior, boot from clone.
    your hard drive needs repairs.
    Did you format drive before installing SL?
    did you clone and backup?
    is everything you run and all extensions and drivers, utility, etc SL-compatible? heck. some drivers just came out to support SL and be 32-bit/64-bit (2008 Mac Pro, not yours, can boot in 64-bit kernel mode).

  • [vmware] Virtual machine communication interface failed

    hello,
    on a fresh install of archlinux, i have installed vmware workstation 11.0 but when i execute this command :
    vmware-modconfig --console --install-all
    i have this error
    Virtual machine communication interface failed
    full log
    vmware-modconfig --console --install-all
    Stopping VMware services:
    VMware Authentication Daemon done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    make : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
    Using kernel build system.
    /sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/linux/driverLog.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/linux/driver.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/linux/hostif.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/memtrack.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/apic.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/hashFunc.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/vmx86.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/cpuid.o
    /tmp/modconfig-sc9HDC/vmmon-only/linux/driver.c:1332:1: attention : always_inline function might not be inlinable [-Wattributes]
    LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
    ^
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/task.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/comport.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/common/phystrack.o
    CC [M] /tmp/modconfig-sc9HDC/vmmon-only/vmcore/moduleloop.o
    LD [M] /tmp/modconfig-sc9HDC/vmmon-only/vmmon.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-sc9HDC/vmmon-only/vmmon.mod.o
    LD [M] /tmp/modconfig-sc9HDC/vmmon-only/vmmon.ko
    make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    /sbin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1] : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
    make[1]: « postbuild » est à jour.
    make[1] : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
    cp -f vmmon.ko ./../vmmon.o
    make : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmmon-only »
    make : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
    Using kernel build system.
    /sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/driver.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/hub.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/userif.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/netif.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/bridge.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/procfs.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/smac_compat.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/smac.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/vnetEvent.o
    CC [M] /tmp/modconfig-sc9HDC/vmnet-only/vnetUserListener.o
    LD [M] /tmp/modconfig-sc9HDC/vmnet-only/vmnet.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-sc9HDC/vmnet-only/vmnet.mod.o
    LD [M] /tmp/modconfig-sc9HDC/vmnet-only/vmnet.ko
    make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    /sbin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1] : on entre dans le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
    make[1]: « postbuild » est à jour.
    make[1] : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
    cp -f vmnet.ko ./../vmnet.o
    make : on quitte le répertoire « /tmp/modconfig-sc9HDC/vmnet-only »
    Starting VMware services:
    Virtual machine monitor done
    Virtual machine communication interface failed
    VM communication interface socket family done
    Blocking file system done
    Virtual ethernet done
    VMware Authentication Daemon done
    Unable to start services
    [root@hulk vmware-root]# ls
    vmware-818.log vmware-authdlauncher-2058.log vmware-vmis-1888.log
    vmware-apploader-1976.log vmware-vmis-1407.log vmware-vmis-1910.log
    vmware-apploader-818.log vmware-vmis-1429.log
    [root@hulk vmware-root]# chown gael:users *
    [root@hulk vmware-root]# chown -R gael:users ./
    [root@hulk vmware-root]# modprobe vmci
    modprobe: FATAL: Module vmci not found.
    [root@hulk vmware-root]# vmware-modconfig --console --install-all -v
    /usr/lib/vmware/bin/vmware-modconfig-console: invalid option -- 'v'
    Stopping VMware services:
    VMware Authentication Daemon done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    make : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
    Using kernel build system.
    /sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/linux/driverLog.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/linux/driver.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/linux/hostif.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/memtrack.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/apic.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/hashFunc.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/vmx86.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/cpuid.o
    /tmp/modconfig-KdpHql/vmmon-only/linux/driver.c:1332:1: attention : always_inline function might not be inlinable [-Wattributes]
    LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
    ^
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/task.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/comport.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/common/phystrack.o
    CC [M] /tmp/modconfig-KdpHql/vmmon-only/vmcore/moduleloop.o
    LD [M] /tmp/modconfig-KdpHql/vmmon-only/vmmon.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-KdpHql/vmmon-only/vmmon.mod.o
    LD [M] /tmp/modconfig-KdpHql/vmmon-only/vmmon.ko
    make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    /sbin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1] : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
    make[1]: « postbuild » est à jour.
    make[1] : on quitte le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
    cp -f vmmon.ko ./../vmmon.o
    make : on quitte le répertoire « /tmp/modconfig-KdpHql/vmmon-only »
    make : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
    Using kernel build system.
    /sbin/make -C /lib/modules/3.17.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1] : on entre dans le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/driver.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/hub.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/userif.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/netif.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/bridge.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/procfs.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/smac_compat.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/smac.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/vnetEvent.o
    CC [M] /tmp/modconfig-KdpHql/vmnet-only/vnetUserListener.o
    LD [M] /tmp/modconfig-KdpHql/vmnet-only/vmnet.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-KdpHql/vmnet-only/vmnet.mod.o
    LD [M] /tmp/modconfig-KdpHql/vmnet-only/vmnet.ko
    make[1] : on quitte le répertoire « /usr/lib/modules/3.17.4-1-ARCH/build »
    /sbin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1] : on entre dans le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
    make[1]: « postbuild » est à jour.
    make[1] : on quitte le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
    cp -f vmnet.ko ./../vmnet.o
    make : on quitte le répertoire « /tmp/modconfig-KdpHql/vmnet-only »
    Starting VMware services:
    Virtual machine monitor done
    Virtual machine communication interface failed
    VM communication interface socket family done
    Blocking file system done
    Virtual ethernet done
    VMware Authentication Daemon done
    Unable to start services
    thanks for your help

    Also having the same problem
    dustin ~ $ sudo vmware-modconfig --console --install-all
    [sudo] password for dustin:
    Stopping VMware services:
    VMware Authentication Daemon done
    VM communication interface socket family done
    Virtual machine communication interface done
    Virtual machine monitor done
    Blocking file system done
    make: Entering directory '/tmp/modconfig-KZzuso/vmmon-only'
    Using kernel build system.
    /sbin/make -C /lib/modules/3.18.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/lib/modules/3.18.4-1-ARCH/build'
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/linux/driverLog.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/linux/driver.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/linux/hostif.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/memtrack.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/hashFunc.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/apic.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/vmx86.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/cpuid.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/task.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/comport.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/common/phystrack.o
    CC [M] /tmp/modconfig-KZzuso/vmmon-only/vmcore/moduleloop.o
    /tmp/modconfig-KZzuso/vmmon-only/linux/driver.c:1332:1: warning: always_inline function might not be inlinable [-Wattributes]
    LinuxDriverSyncReadTSCs(uint64 *delta) // OUT: TSC max - TSC min
    ^
    LD [M] /tmp/modconfig-KZzuso/vmmon-only/vmmon.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-KZzuso/vmmon-only/vmmon.mod.o
    LD [M] /tmp/modconfig-KZzuso/vmmon-only/vmmon.ko
    make[1]: Leaving directory '/usr/lib/modules/3.18.4-1-ARCH/build'
    /sbin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-KZzuso/vmmon-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-KZzuso/vmmon-only'
    cp -f vmmon.ko ./../vmmon.o
    make: Leaving directory '/tmp/modconfig-KZzuso/vmmon-only'
    make: Entering directory '/tmp/modconfig-KZzuso/vmnet-only'
    Using kernel build system.
    /sbin/make -C /lib/modules/3.18.4-1-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= modules
    make[1]: Entering directory '/usr/lib/modules/3.18.4-1-ARCH/build'
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/driver.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/hub.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/userif.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/netif.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/bridge.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/procfs.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/smac_compat.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/smac.o
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/vnetEvent.o
    In file included from include/linux/pci.h:34:0,
    from /tmp/modconfig-KZzuso/vmnet-only/compat_netdevice.h:27,
    from /tmp/modconfig-KZzuso/vmnet-only/netif.c:43:
    include/linux/pci_ids.h:2248:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
    #define PCI_VENDOR_ID_VMWARE 0x15ad
    ^
    In file included from /tmp/modconfig-KZzuso/vmnet-only/net.h:38:0,
    from /tmp/modconfig-KZzuso/vmnet-only/vnetInt.h:26,
    from /tmp/modconfig-KZzuso/vmnet-only/netif.c:42:
    /tmp/modconfig-KZzuso/vmnet-only/vm_device_version.h:56:0: note: this is the location of the previous definition
    #define PCI_VENDOR_ID_VMWARE 0x15AD
    ^
    CC [M] /tmp/modconfig-KZzuso/vmnet-only/vnetUserListener.o
    In file included from /tmp/modconfig-KZzuso/vmnet-only/net.h:38:0,
    from /tmp/modconfig-KZzuso/vmnet-only/vnetInt.h:26,
    from /tmp/modconfig-KZzuso/vmnet-only/bridge.c:52:
    /tmp/modconfig-KZzuso/vmnet-only/vm_device_version.h:56:0: warning: "PCI_VENDOR_ID_VMWARE" redefined
    #define PCI_VENDOR_ID_VMWARE 0x15AD
    ^
    In file included from include/linux/pci.h:34:0,
    from /tmp/modconfig-KZzuso/vmnet-only/compat_netdevice.h:27,
    from /tmp/modconfig-KZzuso/vmnet-only/bridge.c:51:
    include/linux/pci_ids.h:2248:0: note: this is the location of the previous definition
    #define PCI_VENDOR_ID_VMWARE 0x15ad
    ^
    LD [M] /tmp/modconfig-KZzuso/vmnet-only/vmnet.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/modconfig-KZzuso/vmnet-only/vmnet.mod.o
    LD [M] /tmp/modconfig-KZzuso/vmnet-only/vmnet.ko
    make[1]: Leaving directory '/usr/lib/modules/3.18.4-1-ARCH/build'
    /sbin/make -C $PWD SRCROOT=$PWD/. \
    MODULEBUILDDIR= postbuild
    make[1]: Entering directory '/tmp/modconfig-KZzuso/vmnet-only'
    make[1]: 'postbuild' is up to date.
    make[1]: Leaving directory '/tmp/modconfig-KZzuso/vmnet-only'
    cp -f vmnet.ko ./../vmnet.o
    make: Leaving directory '/tmp/modconfig-KZzuso/vmnet-only'
    Starting VMware services:
    Virtual machine monitor done
    Virtual machine communication interface failed
    VM communication interface socket family done
    Blocking file system done
    Virtual ethernet done
    VMware Authentication Daemon done
    Unable to start services
    Now I have the same failed communication interface also
    Starting VMware services:
    Virtual machine monitor done
    Virtual machine communication interface failed
    VM communication interface socket family done
    Blocking file system done
    Virtual ethernet done
    VMware Authentication Daemon done
    Unable to start services
    PS, I have the vmware-patch 11.0.0-1 installed

  • Software installation external audio interface fails Terratec dmx6 fire usb

    Software installation external audio interface fails Terratec dmx6 fire usb.
    Dear Apple Power User in this forum,
    here is a question for some of us experts.
    I have a external usb audio interface Terratec, Model: DMX 6 fire USB.
    http://www.terratec.net/en/products/technical-data/produktetechnische_daten_en3246.html
    0. There should be after install enclosing software an control app in the app folder, but it isnt there. Why?
    1. the attached installer protocol seems to be normal. isnt it?
    2. the usb audio hardware appears in system profiler.
    3. there isnt the audio hardware in audio-midi-setup! Why?
    4. one of the installed content is visibil in activity monitor as an extension "35 DMX6FireService root 0,0 1 964,00 KB 18,55 MB 22 Intel 00.01 176,00 KB 184,00 KB 73 72"
    5. an other part is in the system-library-extension folder "TTDMX6fire.kext"
    6. other files i am not capacity to find....
    7. and there is the app missing in apps folder! Whitout that it can not work.
    8. Software is for 10.5 and 10.6 32-bit tested from the vendor!?
    9. My MacBookPro early 2008 2.4ghz is capabel of 64bit but is default in 32 mode says apple spec, also my osx 10.5.8 newest updates should be 32 bit. Isnt it?
    10. installation tested whit disconnected/connected ext. volumes or display or these audio interface, whith repaired permissions, on two different macs (second is iMac), whit reboot,
    11. tested on different usb ports, usb port test passed whith other equipment,
    12. on windows xp all works.
    13. tested on a new admin user, same problem.
    14. searched whith terminal command line in applications, nothing.
    15. get software from cd and homepage, no effect.
    16. asked vendor: "until now never had problems like that"
    any ideas? please help!
    for testing or showing the installer look here:
    http://www.terratec.net/en/driver-and-support/driver_21300.html?selectproduct=DM X%206Fire%20USB
    Installation Protocol:
    Dec 25 00:08:39 cadas-macbook-pro /System/Library/CoreServices/Installer.app/Contents/MacOS/Installer[400]: vm_allocate: 0, 0x5800000 - 0x25800000
    Dec 25 00:08:39 cadas-macbook-pro /System/Library/CoreServices/Installer.app/Contents/MacOS/Installer[400]: vm_protect: 0
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: @(#)PROGRAM:Install PROJECT:Install-388
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: @(#)PROGRAM:Installer PROJECT:Installer-281
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Hardware: MacBookPro4,1 @ 2.40 GHz (x 2), 4096 MB RAM
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Running OS Build: Mac OS X 10.5.8 (9L30)
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: PATH=/usr/bin:/bin:/usr/sbin:/sbin
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: TMPDIR=/var/folders/gC/gCDdYZuFE98Z28wIB40BeE+TI/-Tmp-/
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: SHELL=/bin/bash
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: HOME=/Users/cada
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: USER=cada
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: LOGNAME=cada
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: DISPLAY=/tmp/launch-MQSZjG/:0
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: SSHAUTHSOCK=/tmp/launch-x3IAC1/Listeners
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: ApplePubSub_SocketRender=/tmp/launch-YalWkk/Render
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: _CF_USER_TEXTENCODING=0x1F5:0:3
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: SECURITYSESSIONID=a1b410
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Env: COMMAND_MODE=unix2003
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: DMX6fireUSB Installation Log
    Dec 25 00:08:39 cadas-macbook-pro Installer[400]: Opened from: /Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg
    Dec 25 00:08:39 cadas-macbook-pro installdb[402]: started (uid 96)
    Dec 25 00:08:39 cadas-macbook-pro installdb[402]: Opened receipt database on '/' with schema 17.
    Dec 25 00:08:45 cadas-macbook-pro installdb[402]: done. (0.004u + 0.003s)
    Dec 25 00:09:10 cadas-macbook-pro runner[403]: Administrator authorization granted.
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: =============================================================================== =
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: User picked Standard Install
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Choices selected for installation:
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "DMX6fireUSB"
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "DMX6FireUSBCpl"
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#dmx6fireusbcpl.pkg : com.terratec.dmx6fireusb.pkg : 1
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#ttdmx6fire.pkg : com.terratec.dmx6fireusb1.pkg : 1
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "TTDMX_6fire_CUSTOMEXT"
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#ttdmx6firecustomext.pkg : com.terratec.dmx6fireusb2.pkg : 1
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "TTDMX6fire"
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#ttdmx6fire-1.pkg : com.terratec.dmx6fireusb3.pkg : 1
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "DMX6FireService"
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#dmx6fireservice.pkg : com.terratec.dmx6fireservice3.pkg : 1
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Aktualisieren: "LaunchDaemon"
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: dmx6fireusb.pkg#comterratecdmx6fire.pkg : com.terratec.dmx6fireusb4.pkg : 1
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: =============================================================================== =
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: It took 0.00 seconds to summarize the package selections.
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: location = file://localhost
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#dmx6fireusbcpl.pkg
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#ttdmx6fire.pkg
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#ttdmx6firecustomext.pk g
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#ttdmx6fire-1.pkg
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#dmx6fireservice.pkg
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: -[IFDInstallController(Private) _buildInstallPlan]: file://localhost/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg#comterratecdmx6fire.pk g
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: _installNextPackage of 1
    Dec 25 00:09:15 cadas-macbook-pro installdb[405]: started (uid 96)
    Dec 25 00:09:15 cadas-macbook-pro installdb[405]: Opened receipt database on '/' with schema 17.
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Starting installation:
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Preparing volume "250GB_MBPro2" for installation
    Dec 25 00:09:15 cadas-macbook-pro Installer[400]: Configuring volume "250GB_MBPro2"
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Preparing disk for local booted install.
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Free space on "250GB_MBPro2": 11,6 GB (12495523840 bytes).
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Create temporary directory "/private/tmp/dmx6fireusb.pkg.400aysS6s"
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Running install actions
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Processing dmx6fireusbcpl:
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Determining files to install
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: It took 0.06 seconds to create the install plan for dmx6fireusbcpl.
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Configuring deferred files
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Determining obsolete files
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Assembling temporary receipt
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
    Dec 25 00:09:16 cadas-macbook-pro Installer[400]: run preupgrade script for dmx6fireusbcpl
    Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.pCJk/./preflight[408]: : deleting previous Kernel Extensions
    Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.pCJk/./preflight[408]: PID: 43
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: Initializing new flat-package receipt.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: Extracting...
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: 20 of 20 files written in 0.05 seconds.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[419]: 408 kilobytes installed at 7.5 MB/s.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
    Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb.pkg.bom"
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing ttdmx6fire:
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.03 seconds to create the install plan for ttdmx6fire.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: Initializing new flat-package receipt.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: Extracting...
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: 9 of 9 files written in 0.01 seconds.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[420]: 92 kilobytes installed at 11.5 MB/s.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
    Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb1.pkg.bom"
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing ttdmx6firecustomext:
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for ttdmx6firecustomext.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: Initializing new flat-package receipt.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: Extracting...
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: 9 of 9 files written in 0.01 seconds.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[421]: 80 kilobytes installed at 9.7 MB/s.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
    Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb2.pkg.bom"
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing ttdmx6fire-1:
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for ttdmx6fire-1.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: run preupgrade script for ttdmx6fire-1
    Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.MEBZ/./preflight[424]: : deleting previous Kernel Extensions
    Dec 25 00:09:17 cadas-macbook-pro /private/tmp/scripts.MEBZ/./preflight[424]: PID:
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: Initializing new flat-package receipt.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: Extracting...
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: 9 of 9 files written in 0.03 seconds.
    Dec 25 00:09:17 cadas-macbook-pro payloadExtractor[435]: 832 kilobytes installed at 26.2 MB/s.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing post-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Finishing receipt
    Dec 25 00:09:17 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb3.pkg.bom"
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Processing dmx6fireservice:
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining files to install
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for dmx6fireservice.
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Configuring deferred files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Determining obsolete files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Assembling temporary receipt
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Removing obsoleted files
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Creating destination path
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Validating package payload
    Dec 25 00:09:17 cadas-macbook-pro Installer[400]: Starting file extraction
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: Initializing new flat-package receipt.
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: Extracting...
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: 2 of 2 files written in 0.01 seconds.
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[437]: 136 kilobytes installed at 13.4 MB/s.
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Performing post-extraction actions
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finishing receipt
    Dec 25 00:09:18 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireservice3.pkg.bom"
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Processing comterratecdmx6fire:
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Determining files to install
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: It took 0.00 seconds to create the install plan for comterratecdmx6fire.
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Configuring deferred files
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Determining obsolete files
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Assembling temporary receipt
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Performing pre-extraction actions
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Removing obsoleted files
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Creating destination path
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Validating package payload
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Starting file extraction
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: Initializing new flat-package receipt.
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: Extracting...
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: 2 of 2 files written in 0.01 seconds.
    Dec 25 00:09:18 cadas-macbook-pro payloadExtractor[438]: 8 kilobytes installed at 1.0 MB/s.
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Performing post-extraction actions
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finishing receipt
    Dec 25 00:09:18 cadas-macbook-pro runner[403]: Extracting BOM from "/Volumes/DMX6FireUSB.1.22/dmx6fireusb.pkg" to "/Library/Receipts/boms/com.terratec.dmx6fireusb4.pkg.bom"
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Removing temporary directory "/private/tmp/dmx6fireusb.pkg.400aysS6s"
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finalize disk "250GB_MBPro2"
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Notifying system of updated components
    Dec 25 00:09:18 cadas-macbook-pro runner[403]: Touched '/System/Library/Extensions'
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: _installNextPackage of 0
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]:
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: ** Summary Information **
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Operation Elapsed time
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: -----------------------------
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: script 0.29 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: zero 0.02 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: install 1.42 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: validate 0.01 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: os 0.00 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: extract 0.87 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: receipt 0.05 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: disk 1.01 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: config 0.19 seconds
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]:
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Starting installation:
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Finalizing installation.
    Dec 25 00:09:18 cadas-macbook-pro Installer[400]: Registering applications
    Dec 25 00:09:18 cadas-macbook-pro runner[403]: Touched '/Applications/./DMX6FireUSBCpl.app'
    Dec 25 00:09:18 cadas-macbook-pro runner[403]: Touched '/Applications/.'
    Dec 25 00:09:19 cadas-macbook-pro Installer[400]: IFDInstallController 868C80 state = 5
    Dec 25 00:09:19 cadas-macbook-pro Installer[400]: Displaying 'Install Succeeded' UI.
    Dec 25 00:09:24 cadas-macbook-pro installdb[405]: done. (0.026u + 0.040s)

    solved whith the old driver vom archive of vendor: "DMX6Fire_USBMac.1.00c.dmg" thats for 10.5.x for me works.
    The newest from the vendor delivered driver 1.22 (marked for 10.5 and 10.6) seems to not work under 10.5.

  • Webservice interface failed, sapstartsrv stopped

    Hi,
    in our SRM production (abap+java) system's syslog we get following error -->
    webservice interface failed, sapstartsrv stopped
    =================
    We are not sure what error is this.
    Can somebody help in this?
    Thanks in Advance,
    Akki.

    Hi
    Please see related links ->
    Note 1081201 SAP Start Service may crash when fetching a Java callstack
    Note 927637 Web service authentication in sapstartsrv as of Release 7.00
    Note  936273 sapstartsrv for all platforms
    Note 897933 Start and stop sequence for SAP Systems
    Note 867892 MMC shows current SAP processes as being stopped
    Note  877795 Problems w/ sapstartsrv as of Release 7.00 & 6.40 patch 169
    Re: How to stop sapstartsrv and sapstart processes ?
    https://forums.sdn.sap.com/click.jspa?searchID=7502269&messageID=3661396
    https://forums.sdn.sap.com/click.jspa?searchID=7502269&messageID=9957
    Regards
    - Atul

  • Send an email if interface fails

    Hi experts
    I am working in CRM 6.0 Service project. Here we are creating service ticket. Once the ticket is created, status and BP details will be sent to 3rd party back office system. If it is successfully posted in the back office system, CRM will get updated with new status and External reference number.  Our requirement is if interface fails, we want to send an automated email to 2nd response manager with the ticket details that is failed to send 3rd party back office system.
    Can this be achieved by Actions? Or is there any better way? If it is actions, what will be the trigger point we have to use?
    Appreciate your expert help in this.
    Regards
    Surya

    You can have the interface to set a status in your transaction to indicate an error has occurred and your action can be trigger based on that status.
    By using status management, besides email, error report can also be generated to monitor errors.

  • Chaneg data capture--interface unable to capture the changed data

    hello,
    when i add a src table to cdc and start a journal,
    i am able to view the new insertions into the source table ,in journal data of the table.
    but when i run an interface the journalised data isnt getting updated in the target table.....
    but there is no error message comming up ...what do i do ?

    Hi,
    when you create interface and check mark the Journalize Data Only, there is a filter created on that datastore with JRN_SUBSCRIBER name. Make sure this subscriber name is same as the SUBSCRIBER that you have mentioned when you registered subscriber on the Datastore. If these two are different, then you will not be able to fetch data. Check the SNP_SUBSCRIBER table to get the subscriber name for the datastore/source table and in the filter give the same name.
    Let me know if it is working...
    Regards,
    kk

  • SCCM Agent install failed - CcmUnloadWmiProviders. Unloading WMI providers

    Hi I have a SCCM 2007 SP2 setup in native mode. I have sccm client problem on Exchange server with os 2008 sp2.
    SCCM agent was working on this server few months back but it is not working now.
    SCCM agent stops at "CcmUnloadWmiProviders. Unloading WMI providers" steps.
    I tried below steps to resolve this but no luck.
    1. Uninstall sccm setup using command "ccmsetup.exe /uninstall"
    2. Run "Cccmclean.exe /all"
    3. Run delcert.exe
    4. Rename SMSCFG.ini file
    5. Run ccmsetup.exe again with source folder path too
    6. As agent installation failed i rebuild WMI repository
    7. Re run setup but it failed at same step.
    8. I rebooted server and rebuild Repository but same error.
    Any Idea about problem
    If needed i can provide Log files too
    ccmsetup.log (Last few lines)
    <![LOG[MSI:
    Action 20:07:08: CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:08.980+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:08:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:08.980+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:08:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:08:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:08:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:08.995+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.011+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.026+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.042+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.058+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.073+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.089+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.104+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.120+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.136+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.151+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.167+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.182+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.198+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.214+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.229+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.245+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.260+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.276+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.292+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.307+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.323+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.338+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.354+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTaskRollback. Removing System
    Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmRegisterSystemTask. Registering System
    Tasks]LOG]!><time="20:07:09.370+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmCreateIISApplicationPoolsInit. ]LOG]!><time="20:07:09.385+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmCreateIISVirtualDirectoriesInit.
    ]LOG]!><time="20:07:09.479+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    RegisterUser. Registering user]LOG]!><time="20:07:09.572+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmFixupServiceConfigInit. ]LOG]!><time="20:07:09.572+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:09:
    CcmSetObjectSecurityInit. Applying security
    permissions]LOG]!><time="20:07:09.650+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:11:
    CcmSetObjectSecurity. Applying security
    permissions]LOG]!><time="20:07:11.429+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:11:
    CcmSetupLoggingInit. ]LOG]!><time="20:07:11.429+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:13:
    CcmSetupLogging. Initializing
    logging...]LOG]!><time="20:07:13.176+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:13:
    SmsSwDistCacheConfigInit. ]LOG]!><time="20:07:13.176+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:13:
    SmsSwDistSetCacheConfig. Configuring Software Distribution
    Cache]LOG]!><time="20:07:13.270+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:13:
    CcmRegisterPerfCountersInit. Registering performance
    counters]LOG]!><time="20:07:13.270+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:13:
    CcmRegisterPerfCountersRollback. ]LOG]!><time="20:07:13.613+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:13:
    CcmRegisterPerfCounters. Registering performance
    counters]LOG]!><time="20:07:13.613+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:13:
    CcmRegisterComponentsInit. ]LOG]!><time="20:07:13.613+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmRegisterComponentsRollback. ]LOG]!><time="20:07:14.159+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmRegisterComponents. Registering CCM
    Components]LOG]!><time="20:07:14.174+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsSetLUAAccessPermissionsInit. Setting Access
    Permissions]LOG]!><time="20:07:14.174+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsSetLUAAccessPermissions. Setting Access
    Permissions]LOG]!><time="20:07:14.252+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    InstallServices. Installing new
    services]LOG]!><time="20:07:14.252+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    WriteEnvironmentStrings. Updating environment
    strings]LOG]!><time="20:07:14.315+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmSetServiceConfigInit. Configuring
    service]LOG]!><time="20:07:14.315+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmSetServiceConfig. Configuring
    service]LOG]!><time="20:07:14.393+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsMigrateInventoryInit. Migrating SMS Legacy Client inventory
    settings]LOG]!><time="20:07:14.393+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsMigrateInventory. Migrating SMS Legacy Client inventory
    settings]LOG]!><time="20:07:14.471+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmConfigDCOMInit. Configuring
    service]LOG]!><time="20:07:14.486+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmConfigDCOM. Configuring service]LOG]!><time="20:07:14.564+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsShellNotify. Setting SMS
    configuration]LOG]!><time="20:07:14.580+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsSetClientLookupConfigInit. ]LOG]!><time="20:07:14.580+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmInitializePolicyInit. Initializing
    policy]LOG]!><time="20:07:14.642+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmInitializePolicy. Initializing
    policy]LOG]!><time="20:07:14.736+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsSetClientConfigInit. Setting SMS
    configuration]LOG]!><time="20:07:14.736+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    SmsSetClientConfig. Setting SMS
    configuration]LOG]!><time="20:07:14.970+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:14:
    CcmMigrateDownloadSchemaInit. ]LOG]!><time="20:07:14.970+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    CcmMigrateDownloadSchema. ]LOG]!><time="20:07:15.110+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    CcmRegisterProduct. Registering
    product]LOG]!><time="20:07:15.126+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    CcmRegisterProductRollback. Registering
    product]LOG]!><time="20:07:15.126+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    SmsInstallPrepDrvrInitAMD64. ]LOG]!><time="20:07:15.126+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    SmsInstallPrepDrvr. Installing Software Metering PREP
    Driver]LOG]!><time="20:07:15.204+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    StartServices. Starting services]LOG]!><time="20:07:15.204+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    CcmStartService. ]LOG]!><time="20:07:15.204+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    SmsCleanupDesktopMigrationInfo. Deinstalling the SMS Legacy Client or
    SMS 2.0 Client]LOG]!><time="20:07:15.220+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    SmsClientInstallSucceeded. Sending status
    message]LOG]!><time="20:07:15.220+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    InstallFinalize. ]LOG]!><time="20:07:15.220+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    CcmStopServiceRollback. ]LOG]!><time="20:07:15.251+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    ProcessComponents. Updating component
    registration]LOG]!><time="20:07:15.266+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    CcmStopService. ]LOG]!><time="20:07:15.391+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    StopServices. Stopping services]LOG]!><time="20:07:15.563+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    SmsUninstallPrepDrvrAMD64. Uninstalling Software Metering PREP
    Driver]LOG]!><time="20:07:15.563+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Warning 25702. Failed to
    uninstall PrepDrvr.Sys for Software Metering
    Agent.]LOG]!><time="20:07:15.641+000" date="04-11-2014"
    component="ccmsetup" context="" type="2" thread="9048"
    file="msiutil.cpp:370">
    <![LOG[MSI: Action 20:07:15:
    SmsStopUIComponents. Stopping UI
    Components]LOG]!><time="20:07:15.641+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    DeleteServices. Deleting services]LOG]!><time="20:07:15.734+000"
    date="04-11-2014" component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    <![LOG[MSI: Action 20:07:15:
    CcmUnloadWmiProviders. Unloading WMI
    providers]LOG]!><time="20:07:15.734+000" date="04-11-2014"
    component="ccmsetup" context="" type="0" thread="9048"
    file="msiutil.cpp:374">
    

    Thanks Mike and theinfraguys for your suggestions. My problem is resolved.
    The solution which worked for me has no logic but it solved my issue.
    When my installation stopps at “CcmUnloadWmiProviders. Unloading WMI providers” step client.msi.log file have incomplete entry as “C:\Windows\SysWOW64\C”
    At this time I have to restart WMI service and service will not stop correctly so I have to forcefully kill Winmgmt process and setup will continue.
    I have to follow same process for upgrading SCCM client.  During client upgrade some time I have to kill ccmexec process too.

  • Detection Method of Date Modified fails due to copied files date modified change

    I've been working through an issue for some time now and I think it's a bug with SCCM 2012 SP1. I've built literally 50 deployments in "Application Management" in SCCM 2012, but I've been chasing my tail on a few of them throwing the
    "succeeded but couldn't detect" error. The few that have given me problems are all copying text files and then detect the modified date to verify that the file is there. All worked when I initially built them in Windows 8 but are now failing
    randomly...even on a machine where they previously worked and I deleted the files to test the deployment again. 
    What I'm doing:
    My java deployment requires policies which we control with the Deployment.config, deployment.properties and java.policy files. A simple script creates the directories and copies the files. I then create a deployment type for this "ConfigFileCopy.cmd"
    and create a detection rule for each file that I am moving over. The detection rule looks for a "date modified" date between the beginning and end of the date for the day I modified the file. This allows me to modify the files to change our
    java policies and then redeploy them with the "new" modified date as the detection rule, which forces the update.
    The problem:
    When I first created my deployment, everything worked pretty well. The files copy out and the script runs successfully. There were some minor tweaks I need to make to my scripts, so I did and then updated the content for the deployment type. I believe this
    is where things go a little wonky. At this point, my deployment starts failing with the "0x87D00324" error.
    Looking through the logs, everything looks good. The reason configuration manager is failing on detecting the modified date for those files, as it turns out, is because the modified dates don't meet the criteria. So that part is properly failing the detection.
    The problem is that the modified dates are correct on the server but not the client. Looking in c:\windows\ccmcache, I can see multiple folders....presumably one for each version of the application that I updated. Looking at any of the newer content folders
    for this app, the modified dates are the date and time the file was copied out to the workstation, which is incorrect as the file hasn't been modified during that process.
    The odd part, is that this doesn't happen EVERY time on EVERY machine. My primary desktop is windows 8.1 and received the files correctly and installed without issue. My test win 8.1 laptop initially received them correctly, but then as I refined the scripts
    it began picking up the wrong modified dates and started failing.
    I found a similar issue to this existed in SCCM 2007 (http://support.microsoft.com/kb/2276865) so I suspect that this is truly just a bug that hasn't been addressed (or maybe is fixed in R2). Unfortunately
    we have business reasons we can't upgrade to R2 at this time so I'm hoping someone has experienced this and has some sort of work around that might get me by for now. If someone can confirm it is fixed in R2, that would help my case to upgrade as well.  
    I can work around the issue by changing my logic to detect any date greater than a specific date. But I shouldn't have to do that and I'm concerned there are scenarios I haven't thought of that will cause unexpected behavior or failures with that.
     

    This outlines the behavior. It's apparently by design. 
    "SCCM has a habit of changing the ‘Date Modified’ timestamp of all files it delivers when it detects an ‘upgrade’ of the source files for that application. It typically does not touch the timestamp
    of the source files if it delivers a brand new install to a client that has never received the software, however if a single file in the source folder is changed for that application, then SCCM tries to use a previous version of the application in the cache
    (C:\windows\ccmcache) and only downloads the new file that has change. This results in all files having their ‘Data Modified’ timestamp changing (except for the brand new file). Therefore determining if that application has delivered
    successfully using ‘Date Modified’ timestamps is not recommended. The key to seeing this process in action is looking at the file properties in the
    C:\windows\ccmcache\<sccm code> folder for that application, particularly before and after a file is updated in the original source SCCM application folder."
    http://blog.kloud.com.au/tag/sccm/

  • SMS_DISCOVERY_DATA_MANAGER Message ID 2636 and 620. Discovery Data Manager failed to process the discovery data record (DDR)

    Hi
    I'm seeing this critical error on my primary.
    SMS_DISCOVERY_DATA_MANAGER Message ID 2636 and 620. 
    Discovery data manager failed to process the discovery data record (DDR)"D:\Prog.....\inboxes\auth\ddm.box\userddrsonly\adu650dh.DDR", because it cannot update the data source.
    Where these ddr's are actually under ddm.box\userddrsonly\BAD_DDRS folder
    I see a ton of DDR files in that folder. Not sure if I can delete them, so I moved them to a temp folder. AD User discovery keeps generating them.
    Any help ?
    Thanks
    UK
    

    Check the ddm.log file for more information.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

  • Distribution Manager Failed To Access The Source Directory

    Hello All,
    I have this issue distributing content to my Distribution Points for months now. I keep running into this error below:
    Distribution Manager Failed to Access the source directory (\\share\folder\file.wim)
    Possible Cause: Distribution Manager does not have sufficient rights to the source directory.
    Solution: Verify that the site server computer account has at least Read access to the directory you specify as the source directory.
    Possible Cause: There is not enough disk space available on the site server.
    Solution: Verify that there is enough free disk space available on the site server.
    I checked the distmgr.log file and received these messages: 
    GetTempFileNameA failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    CFileLibrary::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    CContentDefinition::AddFile failed; 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    Failed to add the file. Please check if this file exists.    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    SnapshotPackage() failed. Error = 0x80004005    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    Failed to take snapshot of package CSU0006A    SMS_DISTRIBUTION_MANAGER    3/24/2015 2:15:38 PM    13952 (0x3680)
    There is enough space on the site server and the site server has full control over the source directory. I wish I can give you more information but I'm hoping this is enough info to get some assistance. If more information is needed please let me know!

    We usually give the DP's computer account and the site server computer account read access to these shares in our environment.
    ... which is not enough for drivers and updates (as there will also files be added).
    Torsten Meringer | http://www.mssccmfaq.de
    ... And for capture Image too if your capture destination points on that share

Maybe you are looking for

  • Apple TV Compatibility

    Please could you advise if Apple TV is fully compatible with my MacBook 13inch, alumimium late 2008? Software wise.. MacBook HD OS X, 10.9. Many thanks

  • "No data available" in BEx Query

    There seems to be some serious issue. I created a Query but when i execute it, It returns me with an error like "no applicable data found" or 'no data available" or sometimes it is returning some weird data.  The issue here is that i don't have the a

  • In iTunes 7 playlist disappears when shuffle removed

    In iTunes 6 there was an option to keep the playlist of the shuffle shown above the smart playlist area after the iPod was removed. After updating to iTunes 7 I cannot find how to turn this back on. Now when the iPod is either ejected or removed (pro

  • Re:Close all Forms in Multi-form application

    how to Close all Forms in Multi form application's

  • How to verify payment information

    How to verify payment information