Deployment Framework for BizTalk (BTDF) Issue

Hi ,
I am getting file not found and other issue,while deploying application using BTDF,for more details please see the attached screen shot.
Note: I am able to build the same application without BTDF .
any help...

just cross check in your orcehstration project properties and check what is the assembly name you mentioned.
Your BTDF settings in build server is expecting for the dll with name
"ProjectName.Orchestrations.dll" , that is in your case BTDF_Deploy.Orchestrations.dll
so your orchestration's  project assembly name should be same like
BTDF_Deploy.Orchestrations  so that the generated dll will be with name
BTDF_Deploy.Orchestrations.dll
if this does not solve it, then we need to verify settings in BTDF proj file for your project and if required in build server configuration too.
Please mark the post as answer if this answers your question. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Similar Messages

  • BizTalk Deployment Framework Query

    Hello,
    We recently decided to use BTDF for Biztalk deployment.
    With our old solutions we create 3 applications in BizTalk. Now when I started working on BTDF I realised that this needs Deployment.btdfproj with the name of <SolutionName>.Deployment.btdfproj and this should be in the folder <SolutionName>.Deployment
    which should be at the root whre solutions file exists.
    I guess this means that we can have only *.btdfproj file and this will end up in one MSI, and which can ceate only one application.
    So for doing what we were doing earlier do we have to split main solution into 3 different solutions, have 3 different set of *.btdfproj  file/files and then created 3 different MSIs ?
    Please advise.
    regards,

    AppsToReference is an element in ItemGroup that needs to be mentioned in your .btdfproj file depending on requirement.
    This is how it looks like
    <ItemGroup>
    <AppsToReference Include="YourAppName1,YourAppName2" />
    </ItemGroup>
    this makes sure that after your application is deployed, a reference to the applications mentioned in the above list are created ( like YourAppName1 and YourAppName2 ). Means if you want to use the resources present in other applications, you have to create
    a reference to those applications.
    So for your applications, if you want any reference from other applications, use this element AppsToReference
    Please mark the post as answer if this answers your question. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • HELP PLS -exception in deploy transformation for "0ANALYSIS_PATTERN"

    Hi All,
    I have a serious problem here. Please help me here...thanks
    We have recently upgraded our BI 7.0 system from BI ABAP - 10 to
    Support Package Stack - 16, which includes BI ABAP - 18 and BI JAVA -
    16. After the upgrade we are facing problems running any query on the
    portal. We get the same consistent error throughout. The portal error
    message is enclosed. I tried installing 0Analysis_Pattern many times
    but it didn't work.
    Secondly when that didn't work I tried running RSPOR_SETUP, in step 2 I
    get the error message, Different ABAP and JAVA support package.
    SAP came back with a reply saying to do BI JAVA config using template installer. We did that, all looks fine. We also ran the Netweaver Diagnostic tool and all looks fine there as well except the ADS is not configured( I doubt this error is anything to do with ADS as we are not using abode export)
    We went through all these notes, 917950, 937697 and 983156 for the configuration.
    But again when we run the RSPOR_SETUP we get the same error message: Different ABAP and JAVA support package
    Also I ran queries using RSRT ....when I execute using the ABAP Web works fine but opens in port 8000, but when I execute using JAVA web it throws the same error message again as below using port 50000. Also I get the same error message when I open 0ANALYSIS_PATTERN using WAD and try to execute it.
    Has anyone faced this problem before?
    Error message below
    500 Internal Server Error
      BEx Web Application
    To avoid this exception see the steps below. To help SAP better investigate this issue, you will need to provide the diagnostic information from these steps.
    1. Most likely, the issue you are experiencing has already been corrected. Please make sure that the most recent patch level is deployed on your system according to notes 1033246 and 1011241. Starting with Support Package Stack 16 patch level 30, BI Java is delivered according to the synchronized delivery process described in the note 1033246.
    2. Please ensure that NetWeaver Business Intelligence Diagnostics & Support Desktop Tool  does not report any issues on your server according to note 937697. You can start it by clicking here (administrator permissions are required).
    3. When opening any customer message on this issue, please attach:
    Support Desktop Tool support info ZIP  file according to note 937697,
    Required information for reproduction  according to note 948490.
    Error Summary
    Exception occured while processing the current request; this exception cannot be handled by the application or framework
    If the information on this page does not help you locate and correct the cause of the problem, contact your system administrator
    To facilitate analysis of the problem, keep a copy of this error page Hint: Most Web browsers allow you to select all content, and copy and paste it into an empty document (such as in an email or simple text file)
    Root Cause
    The initial exception that caused the request to fail was:
    General exception in deploy transformation for object "0ANALYSIS_PATTERN"
    com.sap.ip.bi.base.exception.BIBaseRuntimeException: General exception in deploy transformation for object "0ANALYSIS_PATTERN"
    at com.sap.ip.bi.deploytime.BISP2Jsp.convert(BISP2Jsp.java:555)
    at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:90)
    at com.sap.ip.bi.webapplications.runtime.preprocessor.Preprocessor.parseTemplate(Preprocessor.java:163)
    at com.sap.ip.bi.webapplications.runtime.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:79)
    at com.sap.ip.bi.webapplications.runtime.template.TemplateAssembler.init(TemplateAssembler.java:128)
    Log ID 0017A4AB12A7006B00000395000016180004605B78DEE173
    Details: Full Exception Chain
    System Environment
    Server
    BI Java Release: 7 - Patch level: 0000000016 - Description: BI Web Applications Java - Additional info:  - Production mode: true
    BI ABAP Release: 700 - Patch level: 0018 - Description: SAP NetWeaver BI 7.0 (GBDCLNT100) - Additional info:  - Production mode: true
    Java Virtual Machine Java HotSpot(TM) 64-Bit Server VM - Sun Microsystems Inc. - 1.4.2_15-b02
    Operating System Windows 2003 - ia64 - 5.2
    Context
    ACCESSIBLE false
    CACHE true
    CONTENT_PADDING true
    COUNTRY 
    DEBUG false
    DEBUG_LEVEL 0
    DEBUG_MESSAGES false
    DEBUG_TEXTS false
    DEFAULT_FONT 
    DISPLAY_STACK_TRACE_IN_ERROR_PAGES true
    LANGUAGE en
    Master System Alias GBDCLNT100
    NAVIGATION_NODE_ACTIVE_IVIEW pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/iViews/com.sap.ip.bi.bex
    PROFILING false
    Query String (Initial Browser Request) QUERY=TEST30
    RTL false
    Request URL
    SAP_BW_IVIEW_ID pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/iViews/com.sap.ip.bi.bex
    SERVER_URL_PREFIX
    THEME_NAME sap_tradeshow
    TRACE false
    TRAY_TYPE PLAIN
    Time Tue Jan 13 11:24:52 GMT 2009
    USE_HTTPS_FOR_ADS false
    USE_SAP_EXPORT_LIB false
    User SERCOWNKN (USER.R3_DATASOURCE.SERCOWNKN)
    VALIDATION_DATA false
    Deployed SCAs
    SCA Version SP Patch Compiled Deployed
    ADSSAP 7.00 16 0 2008-06-10 11:48:09 BST 2008-12-29 12:21:02 GMT
    BASETABLES 7.00 16 0 2008-06-10 12:02:26 BST 2008-12-29 12:02:50 GMT
    BI-BASE-S 7.00 17 23 2008-12-24 10:27:08 GMT 2009-01-07 11:53:24 GMT
    BI-IBC 7.00 16 0 2008-06-10 17:29:06 BST 2008-12-29 12:45:13 GMT
    BI-REPPLAN 7.00 16 0 2008-06-10 18:46:18 BST 2008-12-29 12:59:08 GMT
    BI-WDALV 7.00 16 0 2008-06-10 18:46:28 BST 2008-12-29 12:57:58 GMT
    BIWEBAPP 7.00 17 23 2008-12-24 10:27:42 GMT 2009-01-07 11:52:59 GMT
    BI_MMR 7.00 16 0 2008-06-10 12:03:07 BST 2008-12-29 12:21:38 GMT
    BI_UDI 7.00 16 0 2008-06-10 12:03:25 BST 2008-12-29 12:30:20 GMT
    CAF 7.00 16 0 2008-06-10 19:14:45 BST 2008-12-29 12:34:53 GMT
    CAF-KM 7.00 16 0 2008-06-10 18:52:06 BST 2008-12-29 13:12:43 GMT
    CAF-UM 7.00 16 0 2008-06-10 19:14:53 BST 2008-12-29 12:22:26 GMT
    CORE-TOOLS 7.00 16 0 2008-06-10 12:06:18 BST 2008-12-29 12:03:19 GMT
    EP-PSERV 7.00 16 0 2008-06-10 17:37:42 BST 2008-12-29 13:00:07 GMT
    EP-WDC 7.00 16 0 2008-06-10 15:20:00 BST 2008-12-29 13:01:10 GMT
    EPBC 7.00 16 0 2008-06-10 17:36:02 BST 2008-12-29 12:23:03 GMT
    EPBC2 7.00 16 0 2008-06-10 17:36:14 BST 2008-12-29 13:01:15 GMT
    EP_BUILDT 7.00 10 0 2006-10-24 18:44:00 BST 2007-10-03 17:16:57 BST
    JLOGVIEW 7.00 16 0 2008-06-10 11:07:00 BST 2008-12-29 12:03:55 GMT
    JSPM 7.00 16 0 2008-06-10 11:07:00 BST 2008-12-19 11:42:33 GMT
    KM-KW_JIKS 7.00 16 0 2008-06-10 12:09:28 BST 2008-12-29 12:23:19 GMT
    KMC-BC 7.00 16 0 2008-06-10 17:38:03 BST 2008-12-29 13:02:33 GMT
    KMC-CM 7.00 16 0 2008-06-10 17:38:59 BST 2008-12-29 13:03:37 GMT
    KMC-COLL 7.00 16 0 2008-06-10 17:39:23 BST 2008-12-29 13:04:00 GMT
    LM-PORTAL 7.00 16 0 2008-06-10 18:55:57 BST 2008-12-29 13:04:05 GMT
    LM-TOOLS 7.00 16 0 2008-06-10 19:19:13 BST 2008-12-29 12:40:40 GMT
    NET-PDK 7.00 16 0 2008-06-10 17:39:31 BST 2008-12-29 12:53:38 GMT
    RTC 7.00 16 0 2008-06-10 17:39:47 BST 2008-12-29 12:53:44 GMT
    RTC-STREAM 7.00 16 0 2008-06-10 17:39:48 BST 2008-12-29 12:44:16 GMT
    SAP-EU 7.00 16 0 2008-06-10 18:57:14 BST 2008-12-29 13:11:27 GMT
    SAP-JEE 7.00 16 0 2008-06-10 12:14:29 BST 2008-12-29 12:04:52 GMT
    SAP-JEECOR 7.00 16 0 2008-06-10 12:16:00 BST 2008-12-29 12:08:11 GMT
    SAP_BUILDT 7.00 10 0 2006-10-21 20:06:00 BST 2007-10-03 17:17:12 BST
    SAP_JTECHF 7.00 16 0 2008-06-10 12:17:05 BST 2008-12-29 12:09:31 GMT
    SAP_JTECHS 7.00 16 0 2008-06-10 12:24:43 BST 2008-12-29 12:29:00 GMT
    UMEADMIN 7.00 16 0 2008-06-10 19:27:45 BST 2008-12-29 12:41:03 GMT
    UWLJWF 7.00 16 0 2008-06-10 17:40:28 BST 2008-12-29 13:04:23 GMT
    VCBASE 7.00 16 0 2008-06-10 17:40:33 BST 2008-12-29 13:13:00 GMT
    VCFLEX 7.00 16 0 2008-06-10 17:41:04 BST 2008-12-29 12:55:50 GMT
    VCFRAMEWORK 7.00 16 0 2008-06-10 17:41:13 BST 2008-12-29 12:56:00 GMT
    VCKITBI 7.00 16 0 2008-06-10 17:34:47 BST 2008-12-29 12:44:17 GMT
    VCKITGP 7.00 16 0 2008-06-10 17:41:13 BST 2008-12-29 12:44:20 GMT
    VCKITXX 7.00 16 0 2008-06-10 17:41:13 BST 2008-12-29 12:44:21 GMT
    WDEXTENSIONS 7.00 16 0 2008-06-10 18:58:51 BST 2008-12-29 13:13:18 GMT
    Full Exception Chain
    Log ID 0017A4AB12A7006B00000395000016180004605B78DEE173
    com.sap.ip.bi.base.exception.BIBaseRuntimeException: Error during conversion of the Web template "0ANALYSIS_PATTERN from the master system     at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:95)     at com.sap.ip.bi.webapplications.runtime.preprocessor.Preprocessor.parseTemplate(Preprocessor.java:163)     at com.sap.ip.bi.webapplications.runtime.xml.XmlTemplateAssembler.doInit(XmlTemplateAssembler.java:79)     at com.sap.ip.bi.webapplications.runtime.template.TemplateAssembler.init(TemplateAssembler.java:128)     at com.sap.ip.bi.webapplications.runtime.base.Template.doInit(Template.java:113)     at com.sap.ip.bi.webapplications.runtime.base.PageObject.doInit(PageObject.java:286)     at com.sap.ip.bi.webapplications.runtime.base.PageObject.init(PageObject.java:261)     at com.sap.ip.bi.webapplications.runtime.base.ItemRenderer.init(ItemRenderer.java:39)     at com.sap.ip.bi.webapplications.runtime.impl.Page.initPageObject(Page.java:4995)     at com.sap.ip.bi.webapplications.runtime.impl.Page.createPageObject(Page.java:5342)     at com.sap.ip.bi.webapplications.runtime.impl.Page.setTemplate(Page.java:6537)     at com.sap.ip.bi.webapplications.runtime.impl.Page.doSetTemplateCommand(Page.java:6249)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:324)     at com.sap.ip.bi.util.MethodInvoker.callMethod(MethodInvoker.java:101)     at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:415)     at com.sap.ip.bi.webapplications.runtime.command.CommandProcessorHelper.processCommand(CommandProcessorHelper.java:330)     at com.sap.ip.bi.webapplications.runtime.base.CommunicationProcessor.processCommand(CommunicationProcessor.java:175)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandSuper(Page.java:1821)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandInternal(Page.java:1787)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processCommandSequence(Page.java:2497)     at com.sap.ip.bi.webapplications.runtime.impl.Page.doProcessRequest(Page.java:4018)     at com.sap.ip.bi.webapplications.runtime.impl.Page._processRequest(Page.java:3021)     at com.sap.ip.bi.webapplications.runtime.impl.Page.processRequest(Page.java:2864)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.doProcessRequest(Controller.java:994)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller._processRequest(Controller.java:883)     at com.sap.ip.bi.webapplications.runtime.controller.impl.Controller.processRequest(Controller.java:860)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService._handleRequest(BIRuntimeService.java:362)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.services.BIRuntimeService.handleRequest(BIRuntimeService.java:279)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.components.LauncherComponent.doContent(LauncherComponent.java:24)     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)     at java.security.AccessController.doPrivileged(Native Method)     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)     at java.security.AccessController.doPrivileged(Native Method)     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)Caused by: com.sap.ip.bi.base.exception.BIBaseRuntimeException: General exception in deploy transformation for object "0ANALYSIS_PATTERN"     at com.sap.ip.bi.deploytime.BISP2Jsp.convert(BISP2Jsp.java:555)     at com.sap.ip.bi.webapplications.runtime.jsp.portal.service.template.PortalTemplateAccessService.getTemplateContent(PortalTemplateAccessService.java:90)     ... 63 more

    Hi,
    Please help.
    How did you manage to resolve this. I have similar issues.
    I have SAP_ALL and can run the reports without problems but users have error message
    general exception in deploy transformation for object "WEB_TEMPLATE"
    thanks

  • BAM Deployment error - Microsoft.BizTalk.Bam.Management.BamManagerException: The BAM deployment failed. --- Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server "ServerName".

    HI,
    I am getting below error while deploying BAM activity ...Pls help me resolve this issue.
    Microsoft.BizTalk.Bam.Management.BamManagerException: The BAM deployment failed. ---> Microsoft.BizTalk.Bam.Management.BamManagerException: Encountered error while executing command on SQL Server
    "ServerName". ---> System.Data.SqlClient.SqlException: An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or
    [] are not allowed. Change the alias to a valid name.An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed.
    Change the alias to a valid name.An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias
    to a valid name.An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An
    object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An object or column
    name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An object or column name is missing
    or empty. For SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An object or column name is missing or empty. For
    SELECT INTO statements, verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An object or column name is missing or empty. For SELECT INTO statements,
    verify each column has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An object or column name is missing or empty. For SELECT INTO statements, verify each column
    has a name. For other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For
    other statements, look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.An object or column name is missing or empty. For SELECT INTO statements, verify each column has a name. For other statements,
    look for empty alias names. Aliases defined as "" or [] are not allowed. Change the alias to a valid name.   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) 
     at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock,
    Boolean asyncClose)   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)   at
    System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean
    sendToPipe, Int32 timeout, Boolean asyncWrite)   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()   at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteBatches(String cmdText)   at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteNonQuery(String
    cmdText, CommandType cmdType, Boolean inTransaction, Transaction transaction)   --- End of inner exception stack trace ---   at Microsoft.BizTalk.Bam.Management.SqlHelper.ExecuteNonQuery(String cmdText, CommandType cmdType, Boolean inTransaction,
    Transaction transaction)   at Microsoft.BizTalk.Bam.Management.ViewModule.Create(XmlDocument defXmlDoc)   at Microsoft.BizTalk.Bam.Management.WorkerModule.DispatchOperation(OperationType operation, XmlDocument defXmlDoc)   at
    Microsoft.BizTalk.Bam.Management.BamManager.ProcessOneBamArtifactType(BamArtifactType bamArtifact, OperationType operation)   at Microsoft.BizTalk.Bam.Management.BamManager.ManageInfrastructure(OperationType operation)   at Microsoft.BizTalk.Bam.Management.BamManager.Deploy() 
     --- End of inner exception stack trace ---   at Microsoft.BizTalk.Bam.Management.BamManager.Deploy()   at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.HandleDeployAll()   at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.DispatchCommand() 
     at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.Run()   at Microsoft.BizTalk.Bam.Management.BamManagementUtility.BamManagementUtility.Main(String[] args)

    Your View Name, OLAP Cube Name and certain other restrictions listed @http://msdn.microsoft.com/en-us/library/aa561577.aspx
    Please review your BAM Definitons.
    Regards.

  • Checklist for Exchange Certificate issues

    Checklist for Exchange Certificate issues
    1. 
    Why certificate is important for Exchange and What are Certificates used for
    Exchange is now using certificates for more than just web, POP3, or IMAP. In addition to
    securing web services, it has also incorporated Transport Layer Security (TLS) for session based authentication and encryption.
    Certificates are used for several things on Exchange Server. Most customers also use certificates
    on more than one Exchange server. In general, the fewer certificates you have, the easier certificate management becomes.
    IIS (OWA, ECP, EWS, EAS, OA, Autodiscover, OAB, UM)
    POP/IMAP
    SMTP
     2. 
    Common symptoms for
    certificate issue
    Here we can see three different types of the certificate warning, mainly from the Outlook
    side.
    a.
    Certificate mismatch issue
    b.
    Certificate trust issue
    c.
    Certificate expiration issue
    3. 
    Checklists
    In this section, checklists will be provided according to the three different scenarios:
    Certificate Mismatch Issue
    [Analysis]:
    This issue mainly occurs because the URL of the web services Outlook tries
    to connect does not match the host name in the certificate.
    [Checklist]:
    Firstly make sure how many host name in your certificate the certificate. Run “Get-ExchangeCertificate | select certificatedomain”.
    Secondly, check the web services URLs which Outlook are trying to connect to. Run “Test Email AutoConfiguration”
    In this scenario, you need to check the host name for the following services:
    Autodiscover
    EWS
    OAB
    ECP
    UM
    If any of the urls above does not match the one in the certificate, refer to the following article to change
    it via EMS:
    http://support.microsoft.com/kb/940726
     1.
    Do not forget to restart the IIS service after applying the changes above.
     2. Make sure a valid certificate is enabled on the IIS service.
    Certificate Trust Issue
    [Analysis]:
    For the self-signed and PKI-based (Enterprise)
    certificates, they are not automatically trusted by the client computer or mobile device, you must make sure that you import the certificate into the trusted root certificate store on client computers and devices. On the other hand, Third-party or commercial
    certificates do not have this problem. Most commercial CA certificates are already trusted because the certificate already resides in the trusted root certificate store. Because the issuer is trusted, the certificate is also trusted. Using third-party certificates
    greatly simplifies deployment.
    [Checklist]:
    If it’s an Enterprise CA certificate, manually install the root certificate to the “Trusted Root Certification Authorities” folder:
    If it is a 3<sup>rd</sup>-party certificate, first remove and reinstall the certificate. Check whether the Windows Certificate Store on the local
    client is corrupted. If it still does not work, please contact the third-party CA support to verify the certificate.
    Certificate Expiration Issue
    [Checklist]:
    When a certificate is about to expired, we just need to renew it by referring the following article:
    Renew an Exchange Certificate
    http://technet.microsoft.com/en-us/library/ee332322(v=exchg.141).aspx
    To avoid any conflictions, it’s recommended to remove the expired certificate from the certificate store.
    [How to set a reminder to alert the administrator when a certificate is about to expired]:
    It’s easy to fix the certificate expire issue. But it should be more important to set a reminder before the
    certificate expiration. Or there can be a large user impacts.
    Generally, the Event ID “^(24|25)$” will appear in Application log when a certificate is about to expire.
    If it’s not quite visible, we can refer to the following solution:
    http://blogs.technet.com/b/nexthop/archive/2011/11/18/certificate-expiration-alerting.aspx
    OWA certificate revoked issue
    [Analysis]:
    IE
    includes support for server certificate revocation which verifies that an issuing
    CA has not revoked a server certificate. This feature checks for CryptoAPI revocation when certificate extensions
    are present. If the URL for the revocation information is unresponsive, IE cancels the connection.
    [Solution or workaround]:
    1. Contact CA provider and check whether the questioned certificate is in the Revoked List.
    2. If not, check whether the certificate has a private key.
    3. Remove the old certificate and import the new one.
    Workaround:
    IE Internet Options -> Advanced tab -> Clear the "Check for server certificate revocation"
    checkbox.
    4. 
    More References
    Digital Certificates and SSL
    http://technet.microsoft.com/en-us/library/dd351044(v=exchg.150).aspx
    More on Exchange 2007 and certificates - with real world scenario
    http://blogs.technet.com/b/exchange/archive/2007/07/02/3403301.aspx

    (Reported previous post with link to SIS package to moderator)
    This is not the correct SIS package for the N73. The package shown is for S60 3.2 devices, but the N73 is not S60 3.2, I believe it is S60 3.0.
    Most features may work with this SIS, but if you experience strange problems, try using the S60 3.0 version.
    But there are no significant difference between 2.5.3 and 2.5.5 with regard to attachments. The only changes were with localization (languages).
    At this point, try 2.7.0 which is out now:
    http://businesssoftware.nokia.com/mail_for_exchange_downloads.php
    Make sure to pick the right phone on the drop down list. It does matter! There are 4 different packages. This list makes sure you get the right one.
    I have seen some issues with attachments not completing that seem to be carrier dependent. You can test this my using Wifi (if possible).
    Message Edited by m4e_team_k on 28-Sep-2008 12:25 AM

  • General exception in deploy transformation for object "ZWAD_PPQM_Q009.

    hi experts
    I am getting this error when i am tring to access  report
    General exception in deploy transformation for object "ZWAD_PPQM_Q009.
    thanks

    Hi,
    Please help.
    How did you manage to resolve this. I have similar issues.
    I have SAP_ALL and can run the reports without problems but users have error message
    general exception in deploy transformation for object "WEB_TEMPLATE"
    thanks

  • Error at the time of deploying App for SP 2013

    When I try to deploy any App created using VS 2012, giving error below. Please provide some help to resolve it.
    Build started: Project: FleetManagementApp, Configuration: Debug Any CPU ------
    ------ Deploy started: Project: FleetManagementApp, Configuration: Debug Any CPU ------
    Active Deployment Configuration: Deploy App for SharePoint
    Skipping deployment step because a pre-deployment command is not specified.
    Skipping the uninstall step because the app for SharePoint is not installed on the server.
    Install app for SharePoint:
    Uploading the app for SharePoint...
    Error occurred in deployment step 'Install app for SharePoint': We're sorry, we weren't able to complete the operation, please try again in a few minutes.
    If you see this message repeatedly, contact your administrator.
    ========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
    ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

    Hi,
    Please check the link below, it about the simialr issue.
    https://social.msdn.microsoft.com/Forums/vstudio/en-US/c8eb6c92-e1b2-45a9-840e-c782bdc933ec/error-occurred-in-deployment-step-install-app-for-sharepoint-were-sorry-we-werent-able-to?forum=sharepointdevelopment
    Best Regards
    Dennis Guo
    TechNet Community Support

  • Bpel deployment fails for all processes that have revision other than 1.0.

    Using: Release *10.1.3.3.1*
    Hello All,
    Bpel deployment fails for all processes that have revision other than *1.0*.
    We have been attempting to deploy several BPEL projects via ANT script to a target environment and are encountering failures to deploy for every project which isn’t a (revision 1.0). We are getting the following error whenever we try to deploy a process with a revision other than 1.0:
    D:\TJ_AutoDeploy\BPEL_AutoDeploy_BETA\build.xml:65: BPEL archive doesnt exist in directory "{0}"
         at com.collaxa.cube.ant.taskdefs.DeployRemote.getJarFile(DeployRemote.java:254)
         at com.collaxa.cube.ant.taskdefs.DeployRemote.deployProcess(DeployRemote.java:409)
         at com.collaxa.cube.ant.taskdefs.DeployRemote.execute(DeployRemote.java:211)
         at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
         at org.apache.tools.ant.Task.perform(Task.java:364)
         at org.apache.tools.ant.Target.execute(Target.java:341)
         at org.apache.tools.ant.Target.performTasks(Target.java:369)
         at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
         at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
         at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
         at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
         at org.apache.tools.ant.Main.runBuild(Main.java:668)
         at org.apache.tools.ant.Main.startAnt(Main.java:187)
         at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
         at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
    The structure of our automated deployment script is as follows:
    First, a batch script calls (Jdeveloper_BPEL_Prompt.bat) in order to set all necessary environment variables i.e. ORACLE_HOME, BPEL_HOME, ANT_HOME, etc for ant.
    Next, the script lists every .jar file within the directory to an .ini file called BPEL_List.ini. Furthermore, BPEL_DIR, ADMIN_USER and ADMIN_PSWD variables are set and initialized respectively to:
    -     “.” – point to directory where script is running from because all the BPEL processes are located here
    -     “oc4jadmin”
    -     “*********” (whatever the password for out environment is)
    We’ve developed a method to have the script prompt the user to select the target environment to deploy to. Once the user selects the appropriate environment, the script goes through the BPEL_List.ini files and a loop tells it that for every BPEL process listed:
    DO ant
    -Dprocess.name=%%b
    -Drev= !Rev!
    -Dpath=%BPEL_DIR%
    -Ddomain=default
    -Dadmin.user=%ADMIN_USER%
    -Dadmin.password=%ADMIN_PWD%
    -Dhttp.hostname=%HOST%
    -Dhttp.port=%PORT%
    -Dverbose=true
    (What’s happening is that the variables in the batch file are being passed on to the ANT script where *%%b* is the process name, !rev! is revision #, and so on…)
    The loop goes through each line in the BPEL_List.ini and tokenizes the BPEL process into 3 parts *(%%a, %%b, and %%c)* but we only extract 2 parts: *%%b* (process name) and *%%c* which becomes !Rev! (revision number).
    Example:
    Sample BPEL process:
    bpel_ThisIsProcess1_1.0.jar
    bpel_ThisIsProcess2_SOAv2.19.0.001B.jar
    After tokenizing:
    %%a     %%b     %%c
    bpel     ThisIsProcess1     1.0.jar
    bpel     ThisIsProcess2     SOAv2.19.0.001B.jar
    *!Rev!* and not *%%c* because *%%c* will return whatever the revision number is + the “.jar” file extension as illustrated above. So to circumvent this, we parse *%%c* so that the last 4 characters are stripped. Such is done like this:
    set RevN=%%c
    set RevN=!RevN:~0,-4!
    Hence, the usage of !Rev!.
    Below is a screenshot post of the ANT build.xml that goes with our script:
    <!--<?xml version="1.0"?>-->
    <!--BUILD.XML-->
    <project name="bpel.deploy" default="deployProcess" basedir=".">
         <!--
         This ant build file was generated by JDev to deploy the BPEL process.
         DONOT EDIT THIS JDEV GENERATED FILE. Any customization should be done
         in default target in user created pre-build.xml or post-build.xml
         -->
         <property name="process.dir" value="${basedir}" />
              <!-- Set BPEL process name -->
              <!--
              <xmlproperty file="${process.dir}/bpel/bpel.xml"/>
              <property name="process.name" value="${BPELSuitcase.BPELProcess(id)}"/>
              <property name="rev" value="${BPELSuitcase(rev)}"/>
              -->
         <property environment="env"/>
         <!-- Set bpel.home from developer prompt's environment variable BPEL_HOME -->
              <condition property="bpel.home" value="${env.BPEL_HOME}">
                   <available file="${env.BPEL_HOME}/utilities/ant-orabpel.xml" />
              </condition>
         <!-- show that both bpel and oracle.home are located (TESTING purposes ONLY) -->
         <!-- <echo>HERE:${env.BPEL_HOME} ${env.ORACLE_HOME}</echo> -->
         <!-- END TESTING -->
         <!--If bpel.home is not yet using env.BPEL_HOME, set it for JDev -->
         <property name="oracle.home" value="${env.ORACLE_HOME}" />
         <property name="bpel.home" value="${oracle.home}/bpel" />
         <!--First override from build.properties in process.dir, if available-->
         <property file="${process.dir}/build.properties"/>
         <!--import custom ant tasks for the BPEL PM-->
         <import file="${bpel.home}/utilities/ant-orabpel.xml" />
         <!--Use deployment related default properties-->
         <property file="${bpel.home}/utilities/ant-orabpel.properties" />
         <!-- *************************************************************************************** -->
         <target name="deployProcess">
              <tstamp>
                   <format property="timestamp" pattern="MM-dd-yyyy HH:mm:ss" />
              </tstamp>
              <!-- WRITE TO LOG FILE #tjas -->
              <record name="build_verbose.log" loglevel="verbose" append="true" />
              <record name="build_debug.log" loglevel="debug" append="true" />
              <echo></echo>
              <echo>####################################################################</echo>
              <echo>BPEL_AutoDeploy initiated @ ${timestamp}</echo>
              <echo>--------------------------------------------------------------------</echo>
              <echo>Deploying ${process.name} on ${http.hostname} port ${http.port} </echo>
              <echo>--------------------------------------------------------------------</echo>
              <deployProcess
                   user="${admin.user}"
                   password="${admin.password}"
                   domain="${domain}"
                   process="${process.name}"
                   rev="${rev}"
                   dir="${process.dir}/${path}"
                   hostname="${http.hostname}"
                   httpport="${http.port}"
                   verbose="${verbose}" />
              <sleep seconds="30" />
              <!--<echo message="${process.name} deployment logged to ${build_verbose.log}"/>
              <echo message="${process.name} deployment logged to ${build.log}"/> -->
         </target>
         <!-- *************************************************************************************** -->
    </project>
    SUMMARY OF ISSUE AT HAND:
    ~ Every bpel process w/ 1.0 revision deploys with no problems
    ~ At first I would get an invalid character error most likely due to the “!” preceding “Rev”, but then I decided to set rev=”false” in the build.xml file. That didn’t work quite well. In another attempt, I decided to leave the –Drev= attribute within the batch script blank. That still led to 1.0s going through. My next thought was deploying something other than a 1.0, such as 1.2 or 2.0 and that’s when I realized that if it wasn’t a 1.0, it refused to go through.
    QUESTIONS:
    1.     IS THERE A WAY TO HAVE ANT LOOK INTO THE BPEL PROCESS AND PULL THE REVISION ID?
    2.     WHAT ARE WE DOING WRONG? ARE WE MISSING ANYTHING?
    3.     DID WE GO TOO FAR? MEANING, IS THERE A MUCH EASIER WAY WE OVERLOOKED/FORGOT/OR DON’T KNOW ABOUT THAT EXISTS?
    Edited by: 793292 on Jul 28, 2011 12:38 PM

    Only thing i can think of is instead of using a MAC ACL , u cud jus use the default class
    Policy Map Test
    class class-default
    police 56000 8000 exceed-action drop
    Class Map match-any class-default (id 0)
    Match any
    You would be saving a MAC-ACL ;-).

  • Hotfix KB2830546 for BizTalk Server 2013?

    This is a question for MS:
    I am a bit puzzled by the fact that a BizTalk Server hotfix is all of a sudden rolled out automatically through Windows Update?
    Also this hotfix is marked "Important", but reading the description (The verical scroll bar on the target schema....) hardly seems critical to a production environment. 
    When examining the hotfix:
    http://support.microsoft.com/kb/2830546
    it seems that there are two additional fixes inside it:
    Note This update also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:•
    2832136
     FIX: User cannot perform certain database-related operations in BizTalk Server 2013 
    2832137
     FIX: BAM tools cannot be configured in a multi-node BizTalk Server 2013 environment 
    Now these seems more critical! Is that the reason that it is pushed automatically? And why are two important updates "hidden" inside a "non-important vertical scroll bar" hotfix?
    Can we expect other hotfixes for BizTalk to be pushed automatically in the future? (After all they used to require manual installation from CU's etc., which I found best practice since we then have the ability to install them in a test environment first)?
    Morten la Cour

    You can decide if you want to have automatic updates for BizTalk or not. BizTalk Server 2013 will release all updates through windows update (optionally you can download these manually). Why it only showed that one element is probably a bug, I'll inform
    MS about this topic. But yes, MS have started pushing BizTalk updates through windows update in BizTalk 2013.
    Best regards,
    Tord

  • Deploying OneDrive for Business

    Hello,
    I am trying to deploy OneDrive for Business using the XML.
    <Configuration>
    <Add SourcePath="\\domain\dfs\netapps\Microsoft\Microsoft Office 365\Office" OfficeClientEdition="64">
    <Product ID="GrooveRetail">
    <Language ID="en-us" />
    </Product>
    </Add>
    </Configuration>
    But when it runs on the client, I get the error below: 
    The computer already has Office 2013 Pro installed.
    Regards,
    Ramu V Ramanan

    Hi,
    We can try OCT(Office Customization Tool) in this scenario. After you create a network installation point, but before you install Office 2013, you can use the Office Customization Tool to create a Setup customization file (.msp file) to configure the installation
    for users.
    The details can be found in this library article:
    Configure feature installation states for Office 2013
    http://technet.microsoft.com/en-us/library/cc179043(v=office.15).aspx
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

  • TCPIP adapter for BizTalk 2013

    Hello,
    Is there a TCPIP adapter for BizTalk 2013. The one on codeplex can not be installed.
    Regards,
    Paul

    You should download the one from CodePlex for BizTalk 2009 and edit the setup project where it is checking for BizTalk Version and modify this to the value for 2013. Rebuild and then you'd be able to deploy.
    You would also need to re-target the one for 2009 from .Net 3.0 to .Net 4.0
    Regards.

  • Is this project a good candidate for BizTalk?

    Hi all
    We have a project as outlined below, I’d like your input to understand if BizTalk is a suitable candidate assuming cost is not an issue and we'll have other uses for BizTalk.
    - 300+ retail sites
    - Sales transaction information stored in a DBF file
    - DBF file updated with latest sales information by placing a marker file which initiates an external program to update the file
    - DBF file will grow from 0MB (no records) to up to 3.5MB (9000 records)
    - Once the DBF is updated it can be picked up in some way by BizTalk
    - Assume I just want to store the raw data in a SQL table but need to ensure BizTalk will only add new records
    Without getting into what exactly i expect BizTalk to do with the file does the process of collecting files from multiple remote sites\processing 3.5MB\9000 records sound like a typical use case?
    My main worry is picking up files from 300+ remote sites and hearing that these files may grow 10x as they are converted to XML - don’t know if this is something to look into or nothing to worry about.
    Thanks in advance for reading.

    Its typical use case but for SQL-SSIS. SSIS data source connection manager has connection properties to Dbase files( dBASE 5.0) access the Dbase file and send to SQL Server
    table.
    For this type of ETL process which could involve high message volumes (may in future) I would consider using SQL SSIS not BizTalk. With SSIS you can access files from remote
    server, extract it upload/insert the record from Dbase to SQL table. Why do you need to “BizTalk” or “message box” or “publish-subscription” for this ETL process? I would consider SQL-SSIS for this requirement.
    Have this to get some idea:
    Importing DBF files to SQLServer Table using SSIS
    http://timothychenallen.blogspot.co.uk/2007/07/how-to-import-dbase-tables-into-sql.html
    http://webcache.googleusercontent.com/search?q=cache:SklMA9_RcscJ:simonsuthers.wordpress.com/2013/05/20/importing-dbf-files-to-sql-server-using-ssis/+&cd=8&hl=en&ct=clnk&gl=uk
    If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

  • Change deployment package for software updates

    Hi there
    Currently we have different deployment packages and software update groups based on year, product, etc.
    In the near future i'd like to rearange our software deployment process in configuration manager 2012:
    1x Deployment Package for all updates
    1x "Full" Software Update Groups with all updates in it. Additional to that we'll create a "Diff" Software Update Group at the Patchday and merge the updates later via edit membership in the "Full" Software Update Group.
    Are the following steps which i would perform correct?
    1. Select all updates which are deployed and not expired and not superseeded
    2. Create a new Software Update Group "Full"
    3. Select the new Software Update Group --> Download --> Create my new deployment package
    4. Deploy the new software update group to my collections
    5. Delete the obsolete software update groups / deployment package
    6. Delete the old updates source folders on our filer.
    I current don't know if the redownload process let the updates "forget" the old deployment package. With the above described steps i should get rid of all expired and superseeded updates.
    Thanks for any advice :-)
    Regards,
    Simon

    That is correct they only receive and install the updates they require, but don't confuse the metadata and deployments with the updates themselves. They will still receive the metadata and the policies for every update you deploy to them and that's where
    the problem lies. Each and every update assigned to a client (using a deployment) has it's own policy which of course must be downloaded by the client and stored in WMI causing the bloat. Note that I haven't experienced this first-hand but am relying on the
    accounts of others here in the forums but to me, if there is any chance of this being an issue, I would avoid it.
    For Update Groups, just a few categories is sufficient to break things up and I typically do three: workstations, server, office. These are often on different patching schedules anyway so it makes sense to have three separate ADRs for them anyway.
    For packages, I typically organize based on the calendar creating a new package every 3-6 months with the package containing all updates. There's really no need to divide the package up by product unless you have DPs dedicated to a specific product. Note
    that pre-R2, to change the package an ADR referenced you had to use PowerShell -- it's been added into the GUI in R2 though.
    Jason | http://blog.configmgrftw.com

  • Where is Support for Windows Update issues for Windows Server?

    Where is Support for Windows Update Issues for Windows Server?
    Windows Update keeps prompting to install an important update, KB2871690 and continually fails with error code 0x800f922
    I ran all the fixes I can find, it still fails.
    I also tried the manual install, fails.
    Microsoft used to provide no charge support for Windows Update issues. They additionally offer online fixes  for other versions of windows, but not server, and I can't find a forum.
    I also cannot ignore the update, it continually prompts.
    I ran the windowsupdate.diagcab and it continually states it fixes Windows Update error 0x80070057, by resetting windows update data store. It further states it fixes Problems installing recent updates.
    But it doesn't. I've run it 50 times, and it says the same thing every time.
    So there is no support for windows update, and no support for windowsupdate.diagcab.
    What's the deal?

    I've done the SFC/ SCANNOW and DISM
    here is the cbs.log
    What are we looking for?
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~BT\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Scratch directory set to 'X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360'. -
    CDISMManager::put_ScratchDir
    2013-12-04 19:48:19, Info                  DISM   PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$Windows.~BT\sources" - CDISMManager::LoadLocalImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.2.9200, Running architecture=amd64, Number of processors=4
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Dism.exe version: 6.2.9200.16384
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Executing command line: X:\$Windows.~BT\sources\dism.exe  /logpath:X:\$Windows.~BT\sources\Panther\cbs.log
    /scratchdir:X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360 /image:X:\ /is-serviceable
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\FolderProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\FolderProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\WimProvider.dll -
    CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\WimProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\VHDProvider.dll -
    CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\VHDProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\ImagingProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Warning               DISM   DISM Provider Store: PID=1612 TID=1616 Failed to Load the provider: X:\$Windows.~BT\sources\ImagingProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Loading Provider from location X:\$Windows.~BT\sources\CompatProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Connecting to the provider located at X:\$Windows.~BT\sources\CompatProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: FolderManager
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2013-12-04 19:48:20, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2013-12-04 19:48:20, Warning               DISM   DISM.EXE: Failed to load WimManager. Try running from the Deployment Tools Command Prompt. If the issue persists, ensure that wimgapi.dll
    and wimserv.exe are up to date.
    2013-12-04 19:48:20, Warning               DISM   DISM.EXE: Failed to add any commands.
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 physical location path: X:\ - CDISMManager::CreateImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Copying DISM from "X:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation
    2013-12-04 19:48:20, Info                  DISM   DISM Manager: PID=1612 TID=1616 Successfully loaded the ImageSession at "X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD"
    - CDISMManager::LoadRemoteImageSession
    2013-12-04 19:48:20, Info                  DISM   DISM Image Session: PID=1644 TID=1656 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:20, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\OSProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:20, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Defaulting SystemPath to X:\ - CDISMOSServiceManager::Final_OnConnect
    2013-12-04 19:48:20, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Defaulting Windows folder to X:\Windows - CDISMOSServiceManager::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\LogProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\PEProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Failed to get and initialize the PE Provider.  Continuing by assuming
    that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting Provider DISMLogger - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Manager: PID=1612 TID=1616 Image session successfully loaded from the temporary location: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD
    - CDISMManager::CreateImageSession
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting Provider OSServices - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Setting SystemPath to X:\ - CDISMOSServiceManager::SetSystemPath
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Target image information: OS Version=6.2.9200.16384, Image architecture=amd64
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Getting the collection of providers from an image provider store type. -
    CDISMProviderStore::GetProviderCollection
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\CbsProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1656 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\MsiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IntlProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\IBSProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\DmiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM OS Provider: PID=1644 TID=1656 Get the registry path to the SOFTWARE hive located at X:\Windows\system32\config\SOFTWARE
    and determine if it is loaded. - CDISMOSServiceManager::DetermineBootDrive
    2013-12-04 19:48:22, Info                  DISM   DISM Driver Manager: PID=1644 TID=1656 Further logs for driver related operations can be found in the target operating
    system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\UnattendProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to get the IDismObject Interface - CDISMProviderStore::Internal_LoadProvider(hr:0x80004002)
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\Wow64provider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x80004002)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\SmiProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Warning               DISM   DISM Provider Store: PID=1644 TID=1656 Failed to Load the provider: X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\EmbeddedProvider.dll.
    - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AppxProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\AssocProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Provider has not previously been encountered.  Attempting to initialize
    the provider. - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Loading Provider from location X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Connecting to the provider located at X:\$WINDOWS.~LS\PackageTemp\3a4a5dfb-c322-402c-a12e-4f1ed21dd360\0C032313-F68B-4BD3-B62F-52A81CE58FCD\TransmogProvider.dll.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1656 Encountered a servicing provider, performing additional servicing initializations.
    - CDISMProviderStore::Internal_LoadProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Current image session is [OFFLINE] - CTransmogManager::GetMode
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Determined WinDir path = [X:\Windows] - CTransmogManager::GetWinDirPath
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 GetProductType: ProductType = [ServerNT] - CTransmogManager::GetProductType
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Product Type: [ServerNT] - CTransmogManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM Transmog Provider: PID=1644 TID=1656 Product Type ServerNT : [Yes] - CTransmogManager::Initialize
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: OSServices
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Package Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: MsiManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: MsiManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: IntlManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: IntlManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DriverManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DriverManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: SmiManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AppxManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AppxManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: AssocManager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: AssocManager.
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Attempting to add the commands from provider: Edition Manager
    2013-12-04 19:48:22, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Provider has previously been initialized.  Returning the existing instance.
    - CDISMProviderStore::Internal_GetProvider
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Processing the top level command token(is-serviceable). - CPackageManagerCLIHandler::Private_ValidateCmdLine
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
    2013-12-04 19:48:22, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Found the PE Provider.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Package Manager: PID=1644 TID=1672 Finalizing CBS core. - CDISMPackageManager::Finalize
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:23, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM OS Provider: PID=1644 TID=1672 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1644 TID=1672 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2013-12-04 19:48:24, Info                  DISM   DISM.EXE:
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Found the OSServices.  Waiting to finalize it until all other providers
    are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2013-12-04 19:48:24, Info                  DISM   DISM Provider Store: PID=1612 TID=1616 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

  • Steps to deploy Lync for users who own Office 365 E1/E2 licenses, but don't have Office 365 E3, using Office Deployment tool.

    After many hours of debugging with Microsoft support the system to install the Lync Client silently can be done with a SINGLE LINE command.  The steps to take are below. It should be an easy next step to put this as GPO installation since
    it is a simple command.
    Comments appreciated. 
    side question: Why is there no Lync 2013 or Lync Office 365 forum?
    Basic steps to deploy Lync for users who own Office 365 E2 licenses, but don’t have Office 365 E3, using Office Deployment tool.
    This also applies for other Office 365 service types where the full office suite download is not included.  In April 2015 This was impossible to find online and not know by the Lync support team.
    Steps are:
    Download the Office deployment tool from
    http://www.microsoft.com/en-in/download/details.aspx?id=36778 and extract it to a folder. For this
    example we will use the \\server\sharename
    location.
    Extracting it creates a setup.exe file and it show a sample XML file.
    2. Create XML file and give it a name such as LyncEntryRetail.xml
    Note: The key is the productID that has to be the “LyncEntryRetail”. Other product IDs will download a version that needs another office 365 license. The productID “LyncRetail” needs an E3 license of Office 365.
    <Configuration>
      <Add SourcePath="\\server\sharename" OfficeClientEdition="32" >
        <Product ID="LyncEntryRetail">
          <Language ID="en-us" />
        </Product>
      </Add> 
    </Configuration>
    3. From the folder where you extracted the Office deployment tool, run the following command on the command prompt to download the source files and store them on the shared drive:
     (on single line)
    Setup.exe /download LyncEntryRetail.xml  
    (This is the name of the XML file created above)
    One can also run the same on a server share by using UNC path names such as  (on single line)
    \\servername\sharename\Setup.exe /download
    \\servername\sharename\LyncEntryRetail.xml  
    (This is the name of the XML file created above)
    4. Run the following command on the command prompt on a machine where you want to install the software: (on single line)
    \\servername\sharename\Setup.exe /configure
    \\servername\sharename\LyncEntryRetail.xml  
    (This is the name of the XML file created above)
    Once you are comfortable that it all works, you may want to edit the XML file if you want to have silent installation and add the following lines.
      <Display Level="None" AcceptEULA="TRUE" /> 
      <Property Name="AUTOACTIVATE" Value="1" /> 
    Regards
    Bart
    Bart Louwagie

    Hi Chudly，
    For the office365 issue, I also recommend you can post in dedicated forum for more efficient support:
    http://community.office365.com/en-us/f/166.aspx
    If you want to modify the powershell script, please post the current script and the issue, we will notice and continue to follow up.
    If there is anything else regarding this issue, please feel free to post back.
    If you have any feedback on our support, please click here.
    Best Regards,
    Anna Wang
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Maybe you are looking for