Updated PKGBUILD for vmware-server-modules 2.0.2

Hi.
I have updated the PKGBUILD for the vmware-server-modules and added patches for kernel 2.6.35 and 2.6.36.
The package is currently marked as an orphan, so I'll have to adopt it do upload the changes, right?
Could someone please take a look at this, and say if it is good enough.
I haven't really made any changes other than adding patches for kernel 2.6.35 and 2.6.36, but since there are some 'not so positive comments' following this package in AUR maybe there is more that should be done?
It works on my x86_64 2.6.36-arch install.
pkgname=vmware-server-modules
pkgver=2.0.2
pkgrel=4
pkgdesc="Kernel modules for VMware Server"
arch=('i686' 'x86_64')
url="http://www.vmware.com/products/server/"
license=('custom')
depends=('kernel26>=2.6.32')
makedepends=('kernel26-headers')
conflicts=('vmware-workstation-modules' 'vmware-player-modules')
install=vmware-server-modules.install
_kernver=`uname -r`
source=(VMware-server-2.0.2-203138-update-2.patch vmware-server-modules-autoconf.patch vmware-server-modules-vsock-kernel2.6.35.patch vmware-server-modules-vmmon-kernel2.6.36.patch)
md5sums=('774a6361a443834205bc0172498bb2c0'
'91ea48c3d4779f531cb942be09248dba'
'3325f1b34eb21ee7d4cceb5f0da852f1'
'bfd62533e023b696cf7ff45379732b71')
case ${CARCH} in
i686)
source=(${source[@]} 'VMware-server-2.0.2-203138.i386.tar.gz')
md5sums=(${md5sums[@]} '6eb844d1ab4aed6128438e5f587d10bb');;
x86_64)
source=(${source[@]} 'VMware-server-2.0.2-203138.x86_64.tar.gz')
md5sums=(${md5sums[@]} 'cc7aef813008eeb7150c21547d431b39');;
esac
build() {
cd "$srcdir/vmware-server-distrib/lib/modules/source"
for module in *.tar; do
tar xf $module
done
cd "$srcdir/vmware-server-distrib"
# patch
patch -p1 < ../VMware-server-2.0.2-203138-update-2.patch
patch -p2 < ../vmware-server-modules-autoconf.patch
if [[ ${_kernver:0:6} == "2.6.35" ]]; then
patch -p1 < ../vmware-server-modules-vsock-kernel2.6.35.patch
fi
if [[ ${_kernver:0:6} == "2.6.36" ]]; then
patch -p1 < ../vmware-server-modules-vsock-kernel2.6.35.patch
patch -p1 < ../vmware-server-modules-vmmon-kernel2.6.36.patch
fi
cd "$srcdir/vmware-server-distrib/lib/modules/source"
for module in vmci vsock vmmon vmnet; do
make -C $module-only HEADER_DIR=/lib/modules/$_kernver/build/include || \
return 1
install -D -m644 $module-only/$module.ko \
"$pkgdir/lib/modules/$_kernver/misc/$module.ko"
done
# License
install -D -m644 "$srcdir/vmware-server-distrib/doc/EULA" \
"$pkgdir/usr/share/licenses/vmware-server-modules/EULA"
install -D -m644 "$srcdir/vmware-server-distrib/doc/open_source_licenses.txt" \
"$pkgdir/usr/share/licenses/vmware-server-modules/open_source_licenses.txt"
sed -i -e "s|KERNEL_VERSION='.*'|KERNEL_VERSION='$_kernver'|" \
"$startdir/vmware-server-modules.install"

i don'T think that there will ever be a PKGBUILD for VMWare, because it's commercial software... but i posted alot of hints in the "Package Configuration Problems" Forum...
http://bbs.archlinux.org/viewtopic.php? … highlight=
nearly each posible problem is described there... if u still have problems, post ur errors and anything u got about it there, and i try to help u.....

Similar Messages

  • Tarball for vmware-server-modules' PKGBUILD missing [SOLVED]

    Edit: I realized that my subject line was mis-leading
    Hello,
    I've been an arch user for several months now. Amazingly, I've been able to work my way through all the problems I've had thus far (due, in large part, to the arch community and wikis). This is my first time actually posting for help.
    I've been trying to install VMware-Server on my latest install of arch, when I run a 'makepkg' on the vmware-server-modules package I get:
    ==> ERROR: VMware-server-2.0.2-203138.x86_64.tar.gz was not found in the build directory
    and is not a URL.
    A link to the missing tarball can be found on the vmware-server-2.0.2 AUR page (http://aur.archlinux.org/packages.php?ID=6182), however, when I click on the link, it 404's. I've done multiple Google, vmware.com, and archlinux.org/forum searches and have found nothing. I'm at a complete loss for what to do at this point. I really can't find anything of use on the subject, am I the only person who's had/having this problem? Any help/suggestions are greatly appreciated.
    Last edited by purilepolterguist (2010-07-18 19:21:51)

    Turns out I'm just retarded. That's the actual vmware-server package from the VMware download site, which I actually downloaded and unpacked in search of the file itself For those who looked at this post, could no one have just gone, "Hey dumbass, it's the actual file from the VMware site."?

  • Vmware-server-modules and kernel 2.6.19 [solved]

    I'm trying to rebuild the vmware server modules from AUR for the new kernel. After adjusting the files for the kernel version and doing makepkg I get the following:
    ==> Validating source files with MD5sums
    VMware-server-1.0.1-29996.tar.gz ... Passed
    ==> Extracting Sources...
    ==> tar --use-compress-program=gzip -xf VMware-server-1.0.1-29996.tar.gz
    ==> Starting build()...
    Using 2.6.x kernel build system.
    make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
    make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/driver.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/linux/hostif.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/cpuid.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/hash.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/memtrack.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/phystrack.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/task.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/common/vmx86.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmcore/moduleloop.o
    LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.mod.o
    LD [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only/vmmon.ko
    make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
    cp -f vmmon.ko ./../vmmon.o
    make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmmon-only'
    Using 2.6.x kernel build system.
    make: Entering directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
    make -C /lib/modules/2.6.19-ARCH/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. modules
    make[1]: Entering directory `/usr/src/linux-2.6.19-ARCH'
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/driver.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/hub.o
    CC [M] /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o
    /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c: In function 'VNetCopyDatagramToUser':
    /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: 'CHECKSUM_HW' undeclared (first use in this function)
    /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: (Each undeclared identifier is reported only once
    /home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.c:629: error: for each function it appears in.)
    make[2]: *** [/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only/userif.o] Error 1
    make[1]: *** [_module_/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only] Error 2
    make[1]: Leaving directory `/usr/src/linux-2.6.19-ARCH'
    make: *** [vmnet.ko] Error 2
    make: Leaving directory `/home/mars/SRC/vmware-server-modules/src/vmware-server-distrib/lib/modules/source/vmnet-only'
    ==> ERROR: Build Failed. Aborting...
    It seems the userif module breaks.  I haven't a clue how to solve this.  :?

    Progress:
    AUR
    which leads to
    http://www.vmware.com/community/thread. … 4&tstart=0
    EDIT: package in AUR has been updated. Thnx pizzapunk.

  • Do I need to install Security Hotfix (KB2977319) after Cumulative Update 12 for SQL Server 2008 R2 SP2

    HI,
    I have installed Cumulative Update 12 for SQL Server 2008 R2 SP2 on my SharePoint instances. This was to resolve a known  issue faced with the instance. CU12 helped resolve the issue. My company is rather strict regarding security hotfixes. But I am
    not sure if this particular hotfix [Security Hotfix (KB2977319)] is required if the instance has CU12 applied.
    Tested this on a Lab server, the installation did run fine, the summary log also stated that the KB is applied. But the Build Number did not change. Hence the doubt.
    Overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Exit message:                  Passed
      Start time:                    2014-09-06 10:31:21
      End time:                      2014-09-06 10:55:49
      Requested action:              Patch
    Instance SPNTSQLTRN overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Exit message:                  Passed
      Start time:                    2014-09-06 10:48:08
      End time:                      2014-09-06 10:55:45
      Requested action:              Patch
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL2008
      Type:                          RTM
      Version:                       10
      SPLevel:                       2
      KBArticle:                     KB2977319
      KBArticleHyperlink:            http://support.microsoft.com/?kbid=2977319
      PatchType:                     QFE
      AssociatedHotfixBuild:         0
      Platform:                      x64
      PatchLevel:                    10.52.4321.0
      ProductVersion:                10.52.4000.0
      GDRReservedRange:              10.50.4001.0:10.50.4199.0;10.50.4200.0:10.50.4250.0
      PackageName:                   SQLServer2008-KB2977319-x64.exe
      Installation location:         e:\ac2af22d88ee645b5b32b5c178\x64\setup\
    Please inform if I need to apply the hotfix on CU12. Thanks in advance.
    John S

    Yes you must install Security update mentioned in KB 2977319 it is important for SQL Server to be patches with this security update. Without this it could allow an attacker to compromise your system and gain control over it.
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
    My Technet Articles

  • October 2014 update rollup for Windows Server 2012 R2 and Data Protection Manager 2012 R2

    Hello all,
    After installing the October 2014 update rollup for Windows Server 2012 R2 (KB2995388) on our Windows 2012 R2 Core Edition backup jobs of System State start to Fail, below the generic error:
    The replica of Non VSS Datasource Writer on hostname.domain is inconsistent with the protected data source. All protection activities for this data source will fail until the replica is synchronized with consistency check.
    The job was cancelled. The user either cancelled the job or modified the associated protection group.
    Removing the update rollup all jobs complete without errors. Somebody is expiriencing the same issue? How can we resolve the problem?
    Thnks, Andrea

    Hi Andrea,
    Have you installed the update 2919355?
    To apply update 2995388, you must first install update 2919355 on Windows 8.1 or Windows Server 2012 R2.
    According to the official website, the issue which you described is not listed as the known issue.
    Please uninstall this update and continue to monitor the official website for the latest news.
    Best Regards.
    Steven Lee
    TechNet Community Support

  • Cumulative update 15 for SQL Server 2012 SP1 is released

    Cumulative update 15 for SQL Server 2012 SP1 is released
    http://support.microsoft.com/en-us/kb/3038001
    MDS related fix is:
    FIX: Add three stored procedures to clean up history that is created when you use SQL Server 2012 MDS
    http://support.microsoft.com/en-us/kb/3036601
    After using MDS for a while, the transaction/validation/staging history may grow very large. In this CU we provide 3 store procedure to clean them up manually.
    The fix will be ported over to SQL 2012 SP2 and SQL 2014 CUs in the coming 2 months.
    In next SQL Server release, it will be automated by MDS maintenance job.
    --@ModelID is the model ID that you clean up the log for.
    --@CLeanupOlderThanDate is the date before that the logs or records is deleted.
    DECLARE @CleanupOlderThanDate date = '<Date>', @ModelID INT = <ID>
    --Cleanup Transaction History
    EXEC mdm.udpTransactionsCleanup @ModelID, @CleanupOlderThanDate;
    --Cleanup Validation History
    EXEC mdm.udpValidationsCleanup @ModelID, @CleanupOlderThanDate;
    --Cleanup entity-based staging table
    EXEC mdm.udpEntityStagingBatchTableCleanup @ModelID, @CleanupOlderThanDate;

    Hi SelvaOnline,
    I would recommend to install SP2 and the hotfix that came after it.
    If you don't have a reason to install a CU than don't bother with it.
    SP2:
    http://www.microsoft.com/en-us/download/details.aspx?id=43340
    Hotfix for SP2;
    http://support.microsoft.com/kb/2969896/en-us
    Thanks, 
    Teun

  • Cumulative update 5 for SQL Server 2012 SP2 is released

    Cumulative update 5 for SQL Server 2012 SP2 is released
    https://support.microsoft.com/en-us/kb/3037255
    MDS related fix is:
    FIX: The notification email link is broken when a special character is part of the URL in SQL Server 2012 MDS
    http://support.microsoft.com/en-us/kb/3036201

    Hello,
    The following blog shows the latest builds (updates) available for each version of SQL Server.
    http://sqlserverbuilds.blogspot.com/
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.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

  • Cumulative Update 1 for SQL Server 2014

    Microsoft has released Cumulative Update #1 for SQL Server 2014. Relevant for @@VERSION 12.0.2000 through 12.0.2341
    http://support.microsoft.com/kb/2931693/en
    [Personal Site] [Blog] [Facebook]

    Shanky,  I did not want to write clearly in the forum, what I think if there are dozens of fixes at bug's level like fails, error messages, crashes, etc.., about three weeks after the release of the production version. but I wrote about it few words
    at facebook Israeli SQL Server User Group. In short.. It's realy look bad in my opinion.
    [Personal Site] [Blog] [Facebook]

  • Cumulative Update 5 for Exchange Server 2013 (KB2936880)

    Hi,
    i have installed exchange server 2013 on separate servers, I deployed the Mailbox role on the first server, and the CAS role on the second server.
    I checked the edition using the exchange management shell on the mailbox server and on the CAS server:
    >>>
    [PS] C:\Windows\system32>Get-ExchangeServer | fl name,edition,admindisplayversion
    Name                : EXMBX
    Edition             : Standard
    AdminDisplayVersion : Version 15.0 (Build 516.32)
    Name                : EXCAS
    Edition             : Standard
    AdminDisplayVersion : Version 15.0 (Build 516.32)
    <<<
    My question is, is it possible to update this current edition to the "Cumulative update 5 for Exchange Server 2013 (KB293688) ?
    if it is, in my case, on which servers should i install this update ? on the Mailbox server ? or on the CAS server ?
    i appreciate you fast response,
    Thanks.

    Hello,
    It doesn't matter which build you choose: you should first update the mailbox role and then CAS. The best option is to have same version of all your Exchange servers (e.g. CU5).
    It is not necessary to install Exchange binaries on DC.
    Hope it helps,
    Adam
    www.codetwo.com
    If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
    find the answer faster.

  • Pkgbuild for vmware on kernel 2.6.1? [FXx]

    had try intsall vmware on kernel 2.4.24 and 2.6.1 (have read all articles in this forums), but all failed!
    could you provide a pkgbuild for vmware? for kernel 2.6

    i don'T think that there will ever be a PKGBUILD for VMWare, because it's commercial software... but i posted alot of hints in the "Package Configuration Problems" Forum...
    http://bbs.archlinux.org/viewtopic.php? … highlight=
    nearly each posible problem is described there... if u still have problems, post ur errors and anything u got about it there, and i try to help u.....

  • Will Cumulative Update 12 for SQL Server 2008R2 SP2 fix: Warning: Unable to Verify TimeStamp for Path\ProgramName?

    Hello,
    I had a server crash recently and our outsource hosting tech support suggested applying Cumulative Upade 12 for SQL server 2008R2 SP2 to fix the issue.  The exception from our dump file "Warning: Unable to Verify TimeStamp for Path\ProgramName"
    is not in the list of hotfixes for this CU.  Do you know if this will fix this issue?  The CU warns not to apply the CU if your issue id not addressed by the CU.  Here is a portion of the dump file with the relevant error:
    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (7e8.2ab4): Unknown exception - code 000042ac (first/second chance not available)
    ntdll!NtWaitForSingleObject+0xa:
    00000000`777412fa c3              ret
    0:240> .sympath srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols;
    Symbol search path is: srv*c:\Websymbols*http://msdl.microsoft.com/download/symbols
    Expanded Symbol search path is: srv*c:\websymbols*http://msdl.microsoft.com/download/symbols
    0:240> .reload /f
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlservr.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlservr.exe
    ..........Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlos.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlos.dll
    ...............Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\opends60.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for opends60.dll
    .......Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\BatchParser.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for BatchParser.dll
    ....Unable to load image C:\Program Files\Microsoft SQL Server\100\Shared\instapi10.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for instapi10.dll
    *** ERROR: Module load completed but symbols could not be loaded for instapi10.dll
    ..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\sqlevn70.rll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlevn70.rll
    *** ERROR: Module load completed but symbols could not be loaded for sqlevn70.rll
    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.
    .................Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\ftimport.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ftimport.dll
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\msfte.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for msfte.dll
    *** ERROR: Module load completed but symbols could not be loaded for msfte.dll
    ...........Unable to load image C:\Windows\System32\sqlncli10.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlncli10.dll
    ...Unable to load image C:\Windows\System32\1033\SQLNCLIR10.RLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for SQLNCLIR10.RLL
    *** ERROR: Module load completed but symbols could not be loaded for SQLNCLIR10.RLL
    ..Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\xpsqlbot.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for xpsqlbot.dll
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\XPStar.DLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for XPStar.DLL
    .Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\sqlscm.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for sqlscm.dll
    ...*** ERROR: Module load completed but symbols could not be loaded for odbcint.dll
    ...Unable to load image C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Binn\Resources\1033\XPStar.RLL, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for XPStar.RLL
    Thank you,
    Steve -

    The error message appears to be related to a debug session and not come from the actual crash.
    So all I know is that you hade a server crash. I don't even know exactly what that means. Did Windows bite the dust? Or was it only SQL Server?
    Assuming the latter, I would expect the SQL Server errorlog to have some information (and that would be ERRORLOG.1 or earlier, since the server have been restarted), but if SQL Server died the output may be incomplete.
    There may be also dump files, but as I rarely look into these, I am not sure how to interpret them. But I am quite confident that "Unable to verify TimeStamp..." is not the reason SQL Server went down.
    I would suggest the following course:
    *  If the server is not critical, do nothing. As long as it has onlyl happened once, it has only happened once.
    *  If the server is critical, open a case with Microsoft if you are not able to figure out the reason yourself. The key here is "Unknown exception - code 000042ac".
    *  If it happens again, you should absolutely open a case. An important thing here is whether the stack dump is identical or something different. If the stack dumps are identical, you may have hit a bug in SQL Server or the OS, and applying CUs or OS
    fixes could help if it is a known issue. If the stack dump is something else, you have ghosts in the machine - that is, bad hardware.
    Erland Sommarskog, SQL Server MVP, [email protected]

  • SP1 for Windows Server 2008 R2 - Host ok for VmWare Server 2??

    Hello,
    I am running a VmWare Server 2.02 on a Windows Server 2008 R2 - Host. Are there any known problems with regard to VmWare Server 2 when installing SP1 on the Windwos Server 2008 R2 - Host? I was reluctand to install SP1, because I was unable to find information to that question. Has anybody out there with the same configuration done the SP1-Update already?
    Regards,Martin Kluge

    Thanks.. That's what I wanted to hear..
    any updates since you posted this thread? still working?
    It amazes me that they killed off Server, they could have moved it to paid and we would have been happy.
    ESXi is great if your hardware supports it, ours doesn't.
    We upgraded our linux OS when we did some disk upgrades on our secondary server a few weeks ago only to find server can't run on 2.6.41.. so -- its going to windows r2 2008.

  • Oracle license for VMWare server

    A vendor is telling me I can not put their Oracle database on a VMWare server because it is only licensed for one CPU. I tried to explain I could set the VMWare session to only use one CPU but they said Oracle will not allow that. They have already proven it runs fine on VMWare but refuse to budge saying it is a dumb Oracle licensing requirement.
    Is this really true? Is it OK to use a product utilizing an Oracle database licensed for a single CPU to run on a VMWare server if I restrict the session to use only one CPU?

    Yes, this is correct. When using Oracle products in a virtual environment, you must count the amount of CPU-cores within the complete environment and/or cluster. So not only the single CPU which was assigned to your virtual server. The idea behind this calculation is simple: you can not guarantee that your virtual server will not consume more CPU power in the near future. You are able to assign more CPU's on the spot.
    If you need more info or help buying the right amount against the right price, feel free to contact me at: [email protected]
    Regards,
    Ruben van der Zwan
    Yenlo | Oracle license specialist | [email protected] | www.yenlo.nl
    Edited by: www.yenlo.nl on Aug 7, 2010 11:47 PM

  • Proper url for vmware server pkgbuild

    i cant seem to find the right url for this pkgbuild.  it fails every time with what is in the URL= field in the AUR pkgbuild (http://www.vmware.com/products/server/).   i visited the site, logged in and copied the URL of the tar.gz file for x86_64 and pasted that URL in the pkgbuild and now it still fails but without giving an error.  how are people getting around this?  i also tried storing it locally and just entering the file path but pacman doesnt seem to like that.  TIA

    the tarball is only available by secure login.  should i just change the "url" field in the PKGBUILD to localhost and make the tar available in the document root?

Maybe you are looking for

  • Not able to see My number its is locked and my facetime is not working?

    Hi, I bought an an I phone4S  from Vodafone in qatar and i am using with another carrier Q tel I am unable to use the following features on my phone: My phone and facetime with my Network provider when i put the Vodafone's card these work so can some

  • Retro entires in HR Forms are not printed when using device type ZHPP3005

    Hi All, We are doing a HCM implementation. We are using HP P3005n printer and ZHPP3005 device type to print our HR forms. We are using ZCalibri font.These are smartforms. Everything was printing perfectly. Then there were retro calculations made to t

  • Ipod update problem

    Problem in attempting to put the latest version of 7.02 software onto ipod to synch songs. Update is greyed out. Restore gives the following: Error message: There was a problem downloading the ipod software to the ipod "iPod" The requested resource w

  • X-Fi Driver Won't Save Setti

    First of all, X=FI rules! The sound quality and placement on my 24 bit 5. speakers is unbelievable. Now, on to the problem. I usually keep the mode set to Game, so I can take advantage of the EAX 5.0 effects in all my favorite new games. However, whe

  • How to attach file to web page

    how to attach a file to a web page