OS V6R1M0 cume package C8190610, ptf SF99354

Hi Team,
I would like share the issues that we encounted after applying the OS V6R1M0 cume package C8190610.
The SAP Systems were not coming up and there were several issues after that
1) netstat option 3, and it was displaying garbage data
We had apply group ptf SF99354 to fix the above problem. Even after this the SAP Systems were not coming up as the WP's were dieing immediately.
2) We had applied the PTF SI32608, which resolves a low level machine error regarding "pointer settings" based on an OS message id MCH3601.
So folks, if you are planning on applying the OS V6R1M0 cume package C8190610, do not forget to apply group ptf SF99354 and PTF SI32608 or else your SAP systems won't come up and IBM and SAP does not have any information updated in any of their Notes.
Good Luck
Thank You
Reg,
Kishore

Hallo again Kishore.
    I contacted IBM in the meantime and got the following information. The general *** includes the PTF SI32608: please see [this link|http://www-912.ibm.com/s_dir/sline003.NSF/3a8f58452f9800bc862562900059e09e/59cd6799f6f4d82886257408005db281?OpenDocument] for details. This *** should also include the PTF for the netstat problem, according to my contact. He suggested that there may have been a problem with the application of the ***, as you should not have needed to apply either PTF if everything had worked properly. He therefore recommends that you reapply the general *** package to ensure that nothing else is missing.
Regards,
   Sally Power
   Dev. Support for SAP on IBM i

Similar Messages

Need assistance with a transport (TP)

As information/background, I have been away from SAP and basis for about four years. Due to personnel changes here, I am now returning to it. While I was away, our SAP system was upgraded from version 4.0B to SAP R/3 ENTERPRISE 47X110. I was not a part of the upgrade and have no details as to how it was accomplished.
We have two SAP systems: DEV and PRD and they are on separate partitions of an i5 520. Both are running on OS/i5 V5R3M5 with up-to-date CUMe packages, etc, and PASE is installed. Both of these systems use the 6.20 kernel at patch level 1598. We know that this is an OLD kernel and we need to upgrade. That may be the problem in this case but I have no way to patch our kernel because it is so long out of support and no patches are available. Moreover, I am pulling my hair out trying to create a plan to upgrade to kernel 6.40.
We use ABAP only, we have no JAVA anything and therefore, no NetWeaver (I don't even know what it looks like).
All that being said, we need to implement changes per note 1004311.
Here is what I have done so far and the resulting errors:
Downloaded the .zip file in note 1004311 to my PC.
Unzipped the files locally using WinZip.
FTP'd to the development partition.
Issued command QUOTE SITE NAMEFMT 1
Issued command lcd '/usr/sap/trans/data'
Issued command bin
Issued command put R242611.p6b
Issued command lcd '/usr/sap/trans/cofiles'
Issued command ascii
Issued command put K242611.p6b
Issued command quit
Logged on to the development partition as DEVOFR
Issued command lcd /usr/sap/trans/bin
Command WRKLNK reveals actual path is /QFileSvr.400/<production partition>/sapmnt/trans/bin
Issued command tp 'addtobuffer P6BK242611 DEV'
Results:
This is R3620DEV/TPOS4 version 320.56.80 (release 620)
E-TPSETTINGS could not be opened.
EXIT
Error in TPSETTINGS: transdir not set.
tp returncode summary:
TOOLS: Highest return code of single steps was: 0
ERRORS: Highest tp internal error was: 0208
tp finished with return code: 208
meaning:
    error in transportprofil (param missing, unknown,...)
Press ENTER to end terminal session.
Of course, if I can't get it into the buffer, I can't import it.
Where do I go from here to resolve this issue? Is there some other process that I should use instead? I can't find anything in STMS that will allow me to add anything to the buffer.
Any help is greatly appreciated.
Robert

Hi, Victor
Thanks, again.
It imported but has this message:
Ended with return code: ===> 4 <===
Is that okay to ignore?
Robert

Objects missing in database (views)

As information/background, I have been away from SAP and basis for about four years. Due to personnel changes here, I am now returning to it. While I was away, our SAP system was upgraded from version 4.0B to SAP R/3 ENTERPRISE 47X110. I was not a part of the upgrade and have no details as to how it was accomplished.
At this point, we have two SAP systems: DEV and PRD and they are on separate partitions of an i5 520. Both are running on OS/i5 V5R3M5 with mostly updated CUMe packages, etc, and PASE is installed. Both of these systems use the 6.20 kernel at patch level 1598. We know that this is an OLD kernel and we need to upgrade. I am currently planning the kernel upgrade to 6.40.
In our PRD instance, using transaction DB02 I have been seeing that we are missing four views in the database:
Views
    SYSTRIGCOL    Obligatory Base object is missing in DB
    SYSTRIGDEP    Obligatory Base object is missing in DB
    SYSTRIGGERS   Obligatory Base object is missing in DB
    SYSTRIGUPD    Obligatory Base object is missing in DB
Is this a big deal? Should I worry about it or just continue with my kernel-upgrade planning?
If needed, can I just retrieve the source from the DEV instance, modify the source, and create the views in PRD?
I have confirmed that I can retrieve the DDL source from DEV via iSeries Navigator. It would then just be a matter of copying it, modifying it for PRD, and then executing it for PRD.
Thanks in advance for any advice.
Robert

Hi Robert,
no this isn't critical during daily business, at least not in base release 6.20.
You are missing a couple of system catalog views providing SQL trigger information on a schema basis. (They are views on top of the systemwide cross reference files.)
I've seen this happening if you restore a library from an old OS/400 release (that did not know about those views) to a newer release.
SAP does not use triggers in 6.20 during daily business that's why it is not critical.
It's easy to fix though: You may consider removing all system catalog logical files from your R3<sid>DATA schema (WRKOBJ, 4) according to the following list:
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/db2/rbafzmstcatalogtbls.htm#catalogtbls .
The following command will recreate them:
     CALL QSYS2/QSQXRLF PARM(CRT R3<sid>DATA)
Hope that helps!
Best regards,
Dorothea

Need advice/assistance with kernel upgrade planning

As information/background, I have been away from SAP and basis for about four years.
Due to personnel changes here, I am now returning to it. While I was away,
our SAP system was upgraded from version 4.0B to SAP R/3 ENTERPRISE 47X110.
I was not a part of the upgrade and have no details as to how it was accomplished.
At this point, we have two SAP systems: DEV and PRD and they are on separate
partitions of an i5 520.
Both are running on OS/i5 V5R3M5 with mostly updated CUMe packages, etc, and
PASE is installed.
Both of these systems use the 6.20 kernel at patch level 1598.
We know that this is an OLD kernel and we need to upgrade.
Upgrading the kernel used to be a really simple thing to do but now, it seems
so complicated! The sheer volume of data on the SMP is very dauntingwhen
it can be found. As a result, I have many questions:
1.     Should we upgrade to kernel 6.40 or kernel 7.00?
2.     The most recent support package that we have is SAPKB62028.
What is the purpose of support packages? Do they have anything to do with the
kernel version? The reason I ask is that in some places, it is stated that
you
MUST be current with support packages before you attempt to upgrade your kernel to 6.40. In other places, it isnt even mentioned.
Note 664679 states:
   Before you can use the 6.40 kernel,
the following Support Package must be installed in your SAP system:
   SAP_BASIS 620: SAPKB62041
   To avoid the problems described in note 787328,
the following Support Packages are also recommended:
   SAP_BASIS 620: SAPKB62047
So, obviously, I need to get these support packages up to level 47. Why?
Isnt the new kernel a fresh start? Why would the existing kernel and
its support package level make any difference to the new kernel?
Since we are currently using kernel 6.20, do I need to install support
packages ?
5.     I know that we dont have a J2EE server. Do I need to even worry
about that at all?
6.     Is there any basis functionality that exists in the J2EE server
that doesnt exist anywhere else? In other words, are we doing ourselves
(and, particularly, me) a disservice by not having it?
7.     What is the difference between SAP NetWeaver 04 and SAP NetWeaver 2004s?
8.     As long as I have a backup, would it be safe to create a new kernel
for DEV but leave PRD alone? Will the transport functions still operate if I do?
9.     Someone mentioned an R3OPT Support Package Stack. Would this be
preferable to loading from the installation CD and patching?
Is this in addition to the new kernel installation?
Any information is greatly appreciated because, as you can see,
I have a lot to learn in a very short time.
Robert
Message was edited by: Robert Clay
Reformmatted, adding line breaks

Hi Robert,
I now try to answer a bit ...
1) So, I must use 6.40 kernel. What determines "basis 6.20"? YES - 6.20 kernel is no longer supported - even for not for 4.7 or other systems on basis 6.20
2) Okay, you agree with SAP that I need this package but...
a) I don't know where to get it - on the SMP in the Support Package Patch area ... look via the following web-page and then 4.7: http://www.4soi.de/SupportPackages.php
(I did it without this patch already, but I can only support Thomas, that is pretty tricky then ...)
b) I don't know how to install it - SPAM as usual ...
c) WHY do I need it if the new kernel totally replaces the
old one? (See also question number 9).
BECAUSE, the new kernel runs in PASE and needs other locales etc.
3) If I have TMKSVRxx libraries on my systems, can I safely delete them? YES, no problem
4) If I have PCHxxx libraries on my systems, can I safely delete them? YES, no problem (reapear after each APYR3FIX and can always be deleted again)
5/6) How am I supposed to know what my needs are if I have no idea what
the product is supposed to deliver? Try finding any useful
information about it in SMP. I can't.
so
YOU do NOT have J2EE - otherwise you would know that - it was very complicated to setup in the past. => be happy as long as you do not need it.
7) Do you have to have the J2EE server before you can even consider your
systems to be running "NetWeaver"? I just don't understand what
"NetWeaver" is. Try finding any useful information about it in SMP. I can't.
Sorry, but this is too much via this forum :-((
NetWeaver on 6.20 technology doesn't really make sense. Therefore, please wait until you upgraded to ECC 6.0 or install another 7.0 product next to it ... (but not everybody needs that - so be happy as long you do not need to install that)
8) Do I understand you correctly that I must upgrade the kernel for ALL
systems simultaneously? There's no allowing for testing for a few weeks?
NO, you SHOULD do this with testing !!!!
9) Would this be preferable to loading from the installation CD and patching?
Is this in addition to the new kernel installation?
If I use R3OPT, do I still have to load the support packages mentioned in 2)?
You can use the ways above as you described either installation and patching or R3opt or you could download a complete kernel from my website, where you just insert the CD into your drive and use LODRUN *OPT ... (whatever you prefer)
HTH & Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

How to automate SQL packages deletion prior to IPL to apply PTF's ?

Hi,
When PTF's need to be applied to the system to avoid trouble it is recommended to delete the SQL packages. The only way to do this that I know of is by using the R3MAIN menu to access the option to delete the SQL packages. As we have two instances on our system this is (to much) time consuming.
For this reason I would like to schedule a STOP of both SAP instances. Followed by some method to check if the SAP instance is down. If the SAP instance is down I would like to Delete the SQL packages and when this task completes I would like to send myself an e-mail confirming this deletion.
The pieces of the puzzle I am missing to achieve all this are:
1. How to check if SAP is done ?
2. How to delete the SQL packages for both instances in a program ?
Of course it would be perfect if it is possible to check for any active SAP users from a program also. I think I have the CL programming skills to write such a program and of course I want to share that information once the program has been tested and approved by me
Regards, Rudi van Helvoirt

Hi Rudi,
I would do it in QSTRUP after IPL, but that's a minor difference.
with an *ALLOBJ user:
CALL R3sid400/R3INLPGM
DLTR3PKG sid
As this sometimes fails, I would code the DLTR3PKG 3-5 times into the CL - the second and more ones are done within a second - so no problem )
You do this for each SID and should be happy - as you do not want this with every IPL I guess, you might want to use a DTAARA in order to control this.
Regards
Volker Gueldenpfennig, consolut.gmbh
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

When to delete SQL Packages

It's been a long time and I've forgotten: If a new cumulative fix pack is installed at the OS-level, do you need to delete SQL packages?
Thanks in advance,
Robert

Hi Bob,
YES !!!!!!
(as soon as you install 1 PTF only, you should delete all SQL packs!)
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Deploying only Acrobat XI Pro CC package w/ Enterprise Serial # - Still getting "Sign In Required"

Downloaded Creative Cloud Packager to create a serialized package of only Acrobat XI Pro. I further customize the deployment via Adobe Customization Wizard XI, but did not re-enter the serial number (as suggested). I am able to deploy from the Exceptions folder with the following cmd, msiexec /i "%inst%AcroPro.msi" PATCH="%inst%Updates\AcrobatUpd11006.msp" TRANSFORMS="%inst%Transforms\en_US.mst" /qn. Upon launching Acrobat, I receive the a pop-up message, "Sign In Required. Siging in with an Adobe ID and registering Creative Cloud Membership Enterprise is required within 32767 days otherwise it will stop working." I don't understand why the serial number and Adobe ID I enterred when packaging did not carry over. Any insight would be appreciated.

Downloaded Creative Cloud Packager to create a serialized package of only Acrobat XI Pro. I further customize the deployment via Adobe Customization Wizard XI, but did not re-enter the serial number (as suggested). I am able to deploy from the Exceptions folder with the following cmd, msiexec /i "%inst%AcroPro.msi" PATCH="%inst%Updates\AcrobatUpd11006.msp" TRANSFORMS="%inst%Transforms\en_US.mst" /qn. Upon launching Acrobat, I receive the a pop-up message, "Sign In Required. Siging in with an Adobe ID and registering Creative Cloud Membership Enterprise is required within 32767 days otherwise it will stop working." I don't understand why the serial number and Adobe ID I enterred when packaging did not carry over. Any insight would be appreciated.

Problems with Adobe creative cloud offline packages ( Windows )

Hi
When I try to install packages that are created with Adobe Creative Cloud Packager for Enterprise they start installing and then they roll-back in the middle of the process without returning any error.
Not really sure what can cause this as there are not many options to select from when creating the package itself...
Any ideas anyone?
thanks

i7 CPU Windows 7 64-bit 12GB ram
��=== Logging started: 11/06/2014 15:39:54 ===
Action 15:39:54: INSTALL.
Action start 15:39:54: INSTALL.
=== Logging started: 11/06/2014 15:39:54 ===
Action start 15:39:54: INSTALL.
Action start 15:39:54: SystemFolder.4DD41A07_A87A_4C19_8A8F_90FFA28335A0.
Action ended 15:39:54: SystemFolder.4DD41A07_A87A_4C19_8A8F_90FFA28335A0. Return value 1.
Action start 15:39:54: WindowsFolder.D369970D_84F1_4034_AD04_376E78EC4B9D.
Action ended 15:39:54: WindowsFolder.D369970D_84F1_4034_AD04_376E78EC4B9D. Return value 1.
Action start 15:39:54: SystemFolder.D369970D_84F1_4034_AD04_376E78EC4B9D.
Action ended 15:39:54: SystemFolder.D369970D_84F1_4034_AD04_376E78EC4B9D. Return value 1.
Action start 15:39:54: CommonFilesFolder.D369970D_84F1_4034_AD04_376E78EC4B9D.
Action ended 15:39:54: CommonFilesFolder.D369970D_84F1_4034_AD04_376E78EC4B9D. Return value 1.
Action start 15:39:54: WindowsFolder.04B9F3B6_9645_7658_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.04B9F3B6_9645_7658_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.04B9F3B6_9645_7658_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.04B9F3B6_9645_7658_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.1E507087_0819_45E0_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.1E507087_0819_45E0_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.1E507087_0819_45E0_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.1E507087_0819_45E0_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_OpenMP_x86.QFE.64B18C93_E25D_307C_92B8_FE071030349 9.
Action ended 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_OpenMP_x86.QFE.64B18C93_E25D_307C_92B8_FE071030349 9. Return value 1.
Action start 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_MFC_x86.QFE.E93BA752_0E7E_3018_A8EA_17549F4D5CC5.
Action ended 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_MFC_x86.QFE.E93BA752_0E7E_3018_A8EA_17549F4D5CC5. Return value 1.
Action start 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_MFCLOC_x86.QFE.2DBEC6C6_7602_3B08_A493_6758A8EA5AE B.
Action ended 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_MFCLOC_x86.QFE.2DBEC6C6_7602_3B08_A493_6758A8EA5AE B. Return value 1.
Action start 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_CRT_x86.QFE.C8AE193F_7C6D_330A_93C7_EBBC23C30DBF.
Action ended 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_CRT_x86.QFE.C8AE193F_7C6D_330A_93C7_EBBC23C30DBF. Return value 1.
Action start 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_ATL_x86.QFE.837D280F_4682_3A15_94E7_F335A8FECFAC.
Action ended 15:39:54: SystemFolder.30729.6161.Microsoft_VC90_ATL_x86.QFE.837D280F_4682_3A15_94E7_F335A8FECFAC. Return value 1.
Action start 15:39:54: WindowsFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2.
Action ended 15:39:54: WindowsFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2. Return value 1.
Action start 15:39:54: SystemFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2.
Action ended 15:39:54: SystemFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2. Return value 1.
Action start 15:39:54: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.D2730D3F_3C41_5884_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.74FD3CE6_2A8D_0E9C_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.68B7C6D9_1DF2_54C1_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.9BAE13A2_E7AF_D6C3_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.63E949F6_03BC_5C40_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.98CB24AD_52FB_DB5F_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.66332652_9C28_58B1_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: WindowsFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E.
Action ended 15:39:54: SystemFolder.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E. Return value 1.
Action start 15:39:54: AppSearch.
Action ended 15:39:54: AppSearch. Return value 1.
Action start 15:39:54: LaunchConditions.
Action ended 15:39:54: LaunchConditions. Return value 1.
Action start 15:39:54: CAHideCancelButton.
Action ended 15:39:54: CAHideCancelButton. Return value 1.
Action start 15:39:54: FindRelatedProducts.
Action ended 15:39:54: FindRelatedProducts. Return value 0.
Action start 15:39:54: ValidateProductID.
Action ended 15:39:54: ValidateProductID. Return value 1.
Action start 15:39:54: CA_WindowsFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2.
Action ended 15:39:54: CA_WindowsFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2. Return value 1.
Action start 15:39:54: CA_SystemFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2.
Action ended 15:39:54: CA_SystemFolder_x86_VC.1DEE2A86_2F57_3629_8107_A71DBB4DBED2. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_ATL_x86.QFE.837D280F_4682_3A15_94E7_F335A8FECFAC.
Action ended 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_ATL_x86.QFE.837D280F_4682_3A15_94E7_F335A8FECFAC. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_CRT_x86.QFE.C8AE193F_7C6D_330A_93C7_EBBC23C30DBF.
Action ended 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_CRT_x86.QFE.C8AE193F_7C6D_330A_93C7_EBBC23C30DBF. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_MFCLOC_x86.QFE.2DBEC6C6_7602_3B08_A493_6758A8EA5A EB.
Action ended 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_MFCLOC_x86.QFE.2DBEC6C6_7602_3B08_A493_6758A8EA5A EB. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_MFC_x86.QFE.E93BA752_0E7E_3018_A8EA_17549F4D5CC5.
Action ended 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_MFC_x86.QFE.E93BA752_0E7E_3018_A8EA_17549F4D5CC5. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_OpenMP_x86.QFE.64B18C93_E25D_307C_92B8_FE07103034 99.
Action ended 15:39:54: WindowsFolder.30729.6161.Microsoft_VC90_OpenMP_x86.QFE.64B18C93_E25D_307C_92B8_FE07103034 99. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_ATL_x86.QFE.26049623_7BE5_3723_8AE5_10 B1D0F5042A.
Action ended 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_ATL_x86.QFE.26049623_7BE5_3723_8AE5_10 B1D0F5042A. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_CRT_x86.QFE.ED5CDF42_FC23_3F0F_80FC_C1 38299ADCC4.
Action ended 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_CRT_x86.QFE.ED5CDF42_FC23_3F0F_80FC_C1 38299ADCC4. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_MFCLOC_x86.QFE.3DA05750_8DE0_3FF5_9348 _AD45AEBE0F36.
Action ended 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_MFCLOC_x86.QFE.3DA05750_8DE0_3FF5_9348 _AD45AEBE0F36. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_MFC_x86.QFE.E8E76D94_B943_3C4B_8DE2_5F FB3480CCB9.
Action ended 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_MFC_x86.QFE.E8E76D94_B943_3C4B_8DE2_5F FB3480CCB9. Return value 1.
Action start 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_OpenMP_x86.QFE.EF1548FC_5A85_3436_9873 _2CE14656F9F8.
Action ended 15:39:54: WindowsFolder.30729.6161.policy_9_0_Microsoft_VC90_OpenMP_x86.QFE.EF1548FC_5A85_3436_9873 _2CE14656F9F8. Return value 1.
Action start 15:39:54: CostInitialize.
Action ended 15:39:54: CostInitialize. Return value 1.
Action start 15:39:54: ResolveSource.
Action ended 15:39:54: ResolveSource. Return value 1.
Action start 15:39:54: FileCost.
Action ended 15:39:54: FileCost. Return value 1.
Action start 15:39:54: IsolateComponents.
Action ended 15:39:54: IsolateComponents. Return value 0.
Action start 15:39:54: CostFinalize.
Action ended 15:39:54: CostFinalize. Return value 1.
Action start 15:39:54: CAInstallMode.
Action ended 15:39:54: CAInstallMode. Return value 1.
Action start 15:39:54: SetODBCFolders.
Action ended 15:39:54: SetODBCFolders. Return value 0.
Action start 15:39:54: MigrateFeatureStates.
Action ended 15:39:54: MigrateFeatureStates. Return value 0.
Action start 15:39:54: InstallValidate.
Action ended 15:39:55: InstallValidate. Return value 1.
Action start 15:39:55: RemoveExistingProducts.
Action ended 15:39:55: RemoveExistingProducts. Return value 0.
Action start 15:39:55: InstallInitialize.
Action ended 15:39:56: InstallInitialize. Return value 1.
Action start 15:39:56: SxsInstallCA.
1: sxsdelca 2: traceop 3: 1256 4: 0
1: sxsdelca 2: traceop 3: 1257 4: 0
1: sxsdelca 2: traceop 3: 1258 4: 0
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: uplevel.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.6195.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.6195.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.89.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.96.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.94.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.93.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.89.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.99.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.98.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.93.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.95.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.97.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.94.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.95.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.96.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.100.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.104.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.97.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.3044.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.101.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.98.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.103.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.99.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.193.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.100.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.3069.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.101.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.103.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.1833.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.104.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.238.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4028.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.193.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.3051.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.238.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.3044.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4027.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4053.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.3051.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.3069.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4029.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.1833.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4052.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4027.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4045.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.6188.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4028.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4029.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4054.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.4407.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4045.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4052.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4053.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_payload.8.0.50727.762.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4054.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.4407.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.762.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.6188.97F81AF1_0E47_DC99_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: uplevel.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.6195.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.89.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.93.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0
1: sxsdelca 2: traceop 3: 1290 4: 0
1: sxsdelca 2: traceop 3: 1292 4: 0
1: sxsdelca 2: traceop 3: 1318 4: 0
1: sxsdelca: Skipping component 2: downlevel_manifest.8.0.50727.94.66332652_9C28_58B1_FF1F_C8B3B9A1E18E
1: sxsdelca 2: traceop 3: 1284 4: 0
1: sxsdelca 2: traceop 3: 1288 4: 0
1: sxsdelca 2: traceop 3: 1289 4: 0

Problems Downloading: Adobe Creative Cloud Enterprise-Package

I am a Adobe Creative Cloud Enterprise Administrator. I have gone through the steps of logging in, inputting our serial number, selecting the applications for the package and then downloading the package. The problem is that the download stops at 2%. I even left it running overnight and it is still at 2%. I've tried again this morning, deleted the cache and attempted to create a new package, same result stops at 2%. Does any one have a clue on how to fix this problem?
Packager Computer: Clean install from DVD of Windows 7 Enterprise SP1 x64, UAC disabled, Firewall disabled, no other applications installed other than the Adobe Creative Cloud Packager
Package: Windows 64bit

Hi JohnBNO,
Are you on a managed network. Please refer the kb: http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation-download.html.
Regards,
Romit Sinha

Introducing Creative Cloud Packager 1.0 | Creative Suite In The Enterprise | Adobe TV

Adobe Creative Cloud Packager makes it easy for you to create packages that contain Creative Cloud products and updates. These packages can then be deployed to the client machines of the members who are part of Creative Cloud for Teams in your organization.
http://adobe.ly/ZY84AY

I've just created a .pkg through CCP and tried installing directly on a local machine as well as through ARD and they both fail to install. I made sure that it ignores conflicting processes. When installing directly on the local machine it says "The Installer encountered an error that caused the installation to fail..."
Any help would be great as I've got to deploy this out to our company as soon as possible.

Support package / add on import error in DB2 V9.1 / windows 2003 system

Hi
I have installed ERP 6.0 IDES version in Windows 2003 server with DB2 LUW 9.1 / FP5.
I have selected "Row Compression" and "Deferred Table Creation" during installation.
Now when I am importing add on BI Content 7.03, I am getting error during Movename tabs phase.
Error in phase: IMPORT_PROPER
Reason for error: TP_STEP_FAILURE
Return code: 0008
Error message: OCS Package ALL, tp step "6", return code 0008
The error message in the file D:\usr\sap\trans\log\P090113.IDS is as follows,
2 ETP301
3 ETP361 "96" Shadow-Nametabs activated, DDL executed
2 ETP362 "6" Shadow-Nametab activations failed
2 ETP360 Begin: Act. of Shadow-Nametabs with DDL ("2009/01/13 02:57:51")
2 ETP363 End : Act. of Shadow-Nametabs with DDL ("2009/01/13 02:58:07")
2 ETP301
1 ETP172 MOVE OF NAMETABS
1 ETP110 end date and time : "20090113025807"
1 ETP111 exit code : "8"
1 ETP199 ######################################
I have read some notes it may be due to "Row compression" and "Deffered table creation" option in DB2. Please help me in resolving this issue if it is DB2 related.
Regards,
Nallasivam.D

Hi,
Please find the real error message which I found in the same log file. This is a new installation.
System configuration details:
ERP 6.0 IDES SR3 + Windows 2003 enterprise server SP2 + DB2 V9.1 / FP5
BASIS and ABAP support pack level: (700) 13.
Error message:
3 ETP399 INDEX IN "IDS#BTABI"
3 ETP399 LONG IN "IDS#BTABD COMPRESS YES"
3 ETP399
2WETP000 02:53:26: Retcode 1: error in DDL statement for "/OSP/T_REPINFO                " - repeat
2EETP345 02:53:38: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#BTABD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/OSP/T_REPINFO
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:05: Retcode 1: error in DDL statement for "/SAPPO/CMP_ASG                " - repeat
2EETP345 02:54:17: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CMP_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:17: error in DDL, nametab for "/SAPPO/CMP_ASG" not activated
3 ETP399 IN "IDS#POOLD"
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:17: Retcode 1: error in DDL statement for "/SAPPO/CSCRN_HDR              " - repeat
2EETP345 02:54:29: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/CSCRN_HDR
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:29: error in DDL, nametab for "/SAPPO/CSCRN_HDR" not activated
3 ETP399 INDEX IN "IDS#POOLI"
3 ETP399 LONG IN "IDS#POOLD COMPRESS YES"
3 ETP399
2WETP000 02:54:29: Retcode 1: error in DDL statement for "/SAPPO/F_ASG                  " - repeat
2EETP345 02:54:41: Retcode 1: SQL-error "-107-SQL0107N The name "IDS#POOLD COMPRESS YES" is too lo
2EETP345 ng. The maximum length is "18". SQLSTATE=42622" in DDL statement for "/SAPPO/F_ASG
2EETP345             "
2 ETP399 -
DB-ROLLBACK() -
2EETP334 02:54:41: error in DDL, nametab for "/SAPPO/F_ASG" not activated
Regards,
Nallasivam.D

Problem with flash in events packaged application

Hi,
I´v installed the Events packaged application.
On page 24 you can show some flash-reports. But I get an error: xml loading failed (flow_flash_chart_Rxxxxx).
What can be the reason? serverside or desktopside?
Any reaction will be appreciated.
Leo

Try the following
close all browser windows and open Windows Explorer
in the address bar type %appdata%\Adobe
delete the 'Flash Player' folder in there
in the address bar type %appdata%\Macromedia
delete the 'Flash Player' folder in there
Now try again to change any Flash Player settings.

Office 2013 app-v packages

In this article, http://blogs.windows.com/itpro/2013/12/02/announcing-mdop-2013-r2/   I see mention of an Office version called "Office 2013 ProPlus
App-V Package".    Is this a download? I don't see it available as one when I login to my VLSC site.
We plan to install Office 2013 pro plus VLA LOCALLY (on C:) in our vdisk for virtual machines, but will want to stream Visio,Project,Access 2013 to our users' VMs, using App-V.    (We used to use Citrix XenApp to stream them)
In the Citrix world, "streaming" is the opposite of Publishing or Hosting (running the app ON the server). Streaming means it copies over the files to the user's C: drive on their VM when they launch the appl.
Please advise.

Hi,
As far as I know, Microsoft Office 2013 App-V packages are created by using the Office Deployment Tool (ODT). The created packages may have Subscription Licensing or Volume Licensing.
You need to download Office applications through the ODT first, then convert it into an Office 2013 App-V package with ODT tool.
For more details, please refer to this KB article:
http://support.microsoft.com/kb/2915745/en-us
More reference:
Supported scenarios for deploying Microsoft Office as an App-V package:
http://support.microsoft.com/kb/2772509/en-us
Regards,
Ethan Hua
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.

Office 2013 VL App-V 5 packages

Hi,
We are currently assessing the possibility of deploying Office 2013 as an App-V package since support for VL was announced with MDOP 2013 R2. I would like to create three independent packages:
Office 2013
Project 2013
Visio 2013.
I have successfully created the three App-V packages and they can all be imported an published independently. When I deploy more than one package to the same machine the existing package is un-published and the new package published. The aim is to
be able to deploy the Office App-V package to everyone and only deploy Visio and/or Project to certain users. Currently I can only achieve this by creating multiple App-V packages all including Office (i.e. Office + Visio, Office + Project and
Office + Visio + Project). Is there a supported way to have independent packages of Office, Visio and project 2013 which can co-exist on the same machine (for example, could I use connection groups between the independent packages?)
Thanks.

You should be aware of a few things:
Office App-V Packages must be published globally due to the OS extension points some of which won't work if published to users. See this article for more details: http://technet.microsoft.com/library/dn481351.aspx
Office, Visio and Project in separate packages may impact the user experience
Volume License editions of Office are licensed per device, so targeting users may place the organisation in breach of the licensing agreement
Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This
can be beneficial to other community members reading the thread.
This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
Twitter:
@stealthpuppy | Blog:
stealthpuppy.com |
The Definitive Guide to Delivering Microsoft Office with App-V
Thanks for your answers guys. It does seem the only way to achieve this is to have a single App-V package and use multiple configuration files to determine which combination of applications are published. Far from ideal...

Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit)

Hello,
I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:
Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"
When I try to run this, I immidiatly get the following message:
"We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have
one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."
I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.
Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.
Thanks in advance,

Hello,
Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:
<Configuration>
<Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32"
Version="15.0.4631.1002" >
    <Product ID="ProPlusVolume">
      <Language ID="nl-nl" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Infopath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Powerpoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
    </Product>
</Add>
    <Updates Enabled="False" />
    <Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013_package.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

OS V6R1M0 cume package C8190610, ptf SF99354

Similar Messages

Maybe you are looking for