locked
App-V 5.0 SP2 sequencing Visio / Project 2013 with setup.exe /packager fails RRS feed

  • Question

  • Hi @all,

    unsing the deployment tool this configuration.xml:

    <Configuration>
     <Add SourcePath="C:\office-appv\source\" OfficeClientEdition="32" >
         <Product ID="VisioProVolume">
    		<Language ID="de-de" />
    		<Language ID="en-us" />
        </Product>
      </Add>
    <Display Level="None" AcceptEULA="TRUE" />
    <Logging Name="OfficeSetup.txt" Path="%temp%" /> 
    <Property Name="AUTOACTIVATE" Value="1" />
    </Configuration>

    for Visio / Project VL (sources where downloaded with this configuration.xml as well)

    with this blog:

    http://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx

    Packager tells me that the package was created successfully, but no package was created.

    When I take a look in the logfile, it Shows me an error:

    Timestamp	Process	TID	Area	Category	EventID	Level	Message	Correlation
    02/26/2014 16:46:45.307	INTEGR~1 (0xeac)	0x5030		Click-To-Run	aqkhc	Medium	CmdLine:"C:\Users\bechtle1\AppData\Local\Temp\Microsoft Office 15\ClientX64\integratedoffice.exe" FLATTEN FLATTEN RERUNMODE config ".\configuration.xml" flattenedoutput "c:\office-appv\appv"	
    02/26/2014 16:46:45.307	INTEGR~1 (0xeac)	0x5030		Click-To-Run Telemetry	aqkhd	Medium	{"SessionID":"2e7c6873-7ef6-4ee4-bc2e-248c237f4bd9","GeoID":"94","Ver":"15.0.4569.1504","Bitness":"64","IntegrityLevel":"0x3000","SecuritySessionId":"5"}	
    02/26/2014 16:46:45.307	INTEGR~1 (0xeac)	0x5030		Click-To-Run Telemetry	aqkhe	Medium	{"SessionID":"2e7c6873-7ef6-4ee4-bc2e-248c237f4bd9","GeoID":"94","Ver":"15.0.4569.1504","OSVersion":"6.1","SP":"1","ProductType":"3","ProcessorArch":"9","Locale":"1031"}	
    02/26/2014 16:46:45.307	INTEGR~1 (0xeac)	0x5030		Click-To-Run	ap2kl	Medium	Args::Args - C2RClient IntegratedOffice.exe receives command line {FLATTEN FLATTEN RERUNMODE config ".\configuration.xml" flattenedoutput "c:\office-appv\appv".}	
    02/26/2014 16:46:45.307	INTEGR~1 (0xeac)	0x5030		Click-To-Run	ap2km	Unexpected	C2RClientCommandArgsFactory::CreateC2RClientCommandArgs - Not supported mode: FLATTEN	
    02/26/2014 16:46:45.307	INTEGR~1 (0xeac)	0x5030		Click-To-Run	ap2ko	Unexpected	::wWinMain - Error encountered starting IntegratedOffice.ext with command line FLATTEN FLATTEN RERUNMODE config ".\configuration.xml" flattenedoutput "c:\office-appv\appv". Exception: InvalidArgument (Not supported mode).	
    02/26/2014 16:46:45.307	INTEGR~1 (0xeac)	0x5030		Logging Liblet	aqc99	Medium	Logging liblet uninitializing.	

    Regarding to KB VL is fully supported.

    Has anyone the same issue?

    Regards,

    Bernd.

    Thursday, February 27, 2014 12:01 PM

Answers

All replies

  • I 'sequenced' this recently. The Volume License version too. I believe the only difference in what I did was that I didn't set any other languages. If you try with just the below, do you see the same results? Could try and play the process of elimination game

    <Configuration>
      <Add OfficeClientEdition="32" >
        <Product ID="VisioProVolume">
        <Language ID="en-us" />
        </Product>
      </Add>
    </Configuration>


    PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon

    Thursday, February 27, 2014 6:51 PM
  • Hello,

    If you add a unc-path instead of a local-path, does that make a difference?


    Nicke Källén | The Knack| Twitter: @Znackattack

    Thursday, February 27, 2014 7:06 PM
  • What is the ODT version you are using?
    Thursday, February 27, 2014 9:35 PM
  • Hi Rorymon,

    no luck with this config.

    Additionally I've forgot to say that we must use <Product ID="VisioStdVolume">

    Friday, February 28, 2014 8:33 AM
  • Hi Nicke,

    no luck as well...

    Friday, February 28, 2014 8:34 AM
  • Hi Ben,

    I've used this Versions, both without luck:

    15.0.4595.1000
    15.0.4535.1503

    Are there any better versions out here?

    Friday, February 28, 2014 8:37 AM
  • I meant the ODT version, not Office.

    Staring from somewere in October 2013 ODT supports the VL edition of Office 2013.

    I see that with Office 2013 SP1 a new version (2/25/2014) was released.

    Are you using the October 2013 version or the current 2/25/2014 version?

    Friday, February 28, 2014 9:00 AM
  • OK,

    Time stamps:

    Setup.exe (1): 2013/08/09 09:08 PM

    Setup.exe (2): 2014/02/08 11:02 PM


    Friday, February 28, 2014 10:20 AM
  • With the first ODT setup.exe you won't be able to use VL versions. The second version should be OK (I've only tested the October release of ODT the create a Visio package).

    I need to update my Visio 2013 package, I keep you posted.

    Friday, February 28, 2014 10:25 AM
  • OK, thanks for your investigation.


    Friday, February 28, 2014 12:27 PM
  • I have the same issue, except with ProPlusVolume of office 2013.  I had no issues doing this previously prior to SP1.  So wondering if this is an issue with MS's release?
    Monday, March 3, 2014 6:05 PM
  • Hello,

    Try to use the new Deployment tool;

    http://www.microsoft.com/en-us/download/details.aspx?id=36778


    Nicke Källén | The Knack| Twitter: @Znackattack

    • Marked as answer by Bernd Trampe Tuesday, March 18, 2014 10:16 AM
    Sunday, March 16, 2014 7:58 PM
  • Sorry for the delay.

    I just created a Visio 2013 package with the 25/2/2014 ODT release, no issues occured. Used "VisioStdVolume" as ProductID.

    Are you running ODT setup.exe as admin?

    • Proposed as answer by znack Monday, March 17, 2014 9:19 PM
    Monday, March 17, 2014 4:55 PM