locked
Office 2013 Volume - Invalid product ProjectProVolume RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Trying to package Project 2013 Pro (Volume License)

    When I run setup /configure I get error "Invalid product ProjectProVolume specified"

    According to this KB http://support.microsoft.com/kb/2915745 ProjectProVolume is valid product ID.

    Any idea?

    Thanks,

    Vojin

    Monday, December 30, 2013 6:09 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Yes I am using Nov-25-2013 version.

    It appears that /configure step is not required for App-V Packaged version, however the package is not working after deployment. Office shortcuts appear for couple seconds and then all of them disappear.

    In event log there is event 19104 (Part or all packages publish failed) 1 package failed. There is no Configure/Publish event log error.

    • Proposed as answer by znack Wednesday, January 8, 2014 10:30 PM
    • Marked as answer by Brandon RecordsModerator Thursday, January 23, 2014 2:45 PM
    Tuesday, December 31, 2013 5:04 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Trying to package Project 2013 Pro (Volume License)

    When I run setup /configure I get error "Invalid product ProjectProVolume specified"

    According to this KB http://support.microsoft.com/kb/2915745 ProjectProVolume is valid product ID.

    Any idea?

    Thanks,

    Vojin

    Monday, December 30, 2013 6:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Are you using the most recent version of the Office Deployment Tool?

    Post the contents of your config.xml


    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

    Monday, December 30, 2013 10:50 PM
    Moderator
  • Question
    Sign in to vote
    1
    Sign in to vote

    Yes I am using Nov-25-2013 version.

    It appears that /configure step is not required for App-V Packaged version, however the package is not working after deployment. Office shortcuts appear for couple seconds and then all of them disappear.

    In event log there is event 19104 (Part or all packages publish failed) 1 package failed. There is no Configure/Publish event log error.

    • Proposed as answer by znack Wednesday, January 8, 2014 10:30 PM
    • Marked as answer by Brandon RecordsModerator Thursday, January 23, 2014 2:45 PM
    Tuesday, December 31, 2013 5:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Are you redirecting, to a remote share, the folders where VFS would be? That is,

    %APPDATA%\Microsoft\AppV\Client\VFS

    or

    %LOCALAPPDATA%\Microsoft\AppV\Client\VFS

    Event ID 19104 can occur if you are redirecting those paths.

    As Aaron said, please post your config XML file, so we can make sure that's okay.


    Wednesday, January 1, 2014 10:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No redirection of anything

    here is my config.xml:

    <Configuration>
	<Add SourcePath="c:\ODTK\Office\" OfficeClientEdition="32" >
    <Product ID="ProPlusVolume">
      <Language ID="en-us" />
    </Product>
    <Product ID="VisioProVolume">
      <Language ID="en-us" />
    </Product>
	<Product ID="ProjectProVolume">
      <Language ID="en-us" />
    </Product>
	<Product ID="SPDRetail">
      <Language ID="en-us" />
    </Product>
  </Add> 
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Name="OfficeSetup.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

    Thursday, January 2, 2014 1:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Drop the "SPDRetail" section from your XML file and run setup.exe again?

    Is SPDRetail supposed to work?

    Friday, January 3, 2014 9:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Nevermind, SPDRetail = SharePoint Designer.

    Friday, January 3, 2014 12:11 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    Exactly what is your issue?

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

    Sunday, January 5, 2014 10:47 AM