COMMAND in Config.xml not working

[Steven]

HI,

Following problem:

I install Office( Visio, Sharepoint same method) in English and German.
It works fine...except for the COMMAND . It does not execute the cmd file I
specify.

Here is an example of EN and ES for SPD 2007.
Am I doing something wrong?

<Configuration Product="SharePointDesigner">

<Display Level="basic" CompletionNotice="yes" SuppressModal="no"
AcceptEula="yes" /> -->

<Logging Type="Verbose" Path="C:\Temp\OfficeLogs" Template="Microsoft
Office SharePoint Designer Setup Install_ES(*).txt" /> -->

<!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> -->

<!-- <USERNAME Value="Customer" /> -->

<!-- <COMPANYNAME Value="MyCompany" /> -->

<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

<!-- <LIS CACHEACTION="CacheOnly" /> -->

<!-- <SOURCELIST Value="\\server1\share\Office12;\\server2\share\Office12"
/> -->

<!-- <DistributionPoint Location="\\server\share\Office12" /> -->

<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->

<!-- <Setting Id="Reboot" Value="IfNeeded" /> -->

<Command Path="C:\Temp\NoAdmin_End.cmd" ChainPosition="after"
Execute="install" />

<AddLanguage Id="en-us" ShellTransform="yes"/>

<AddLanguage Id="es-es" />

</Configuration>

 

[Jeremy]

HI,

Following problem:

I install Office( Visio, Sharepoint same method) in English and German.
It works fine...except for the COMMAND . It does not execute the cmd file I
specify.

I too had the same problem... Got no response.

 

[Bob Buckland ?:-\)]

Hi Steven,

Unlike a .bat file, I'm not sure that using a .cmd file on it's own will work from within the Config.xml file will work, you may
need to use it as part of a command line that calls the engine that runs the command.

See if something along the lines of this format work for you and let us know the results please. (this should all be one line)

<Command Path="%windir%\system32\cmd.exe" Args="<path>\filename.cmd" />

If you use a VB script file type rather than a .cmd filetype you may also want to use this approach.

<Command Path="%windir%\system32\wscript.exe" Args="<path>\filename.vbs" />

You may not need to use the
'ChainPosition' or
'Execute'

attributes in your config.xml file where both are set to values/actions which occur by default, but it shouldn't hurt anything and
does make checking things easier in review

==============
HI,

Following problem:

I install Office( Visio, Sharepoint same method) in English and German.
It works fine...except for the COMMAND . It does not execute the cmd file I
specify.

Here is an example of EN and ES for SPD 2007.
Am I doing something wrong?

<Configuration Product="SharePointDesigner">

<Display Level="basic" CompletionNotice="yes" SuppressModal="no"
AcceptEula="yes" /> -->

<Logging Type="Verbose" Path="C:\Temp\OfficeLogs" Template="Microsoft
Office SharePoint Designer Setup Install_ES(*).txt" /> -->

<!-- <PIDKEY Value="BCDFGHJKMPQRTVWXY2346789B" /> -->

<!-- <USERNAME Value="Customer" /> -->

<!-- <COMPANYNAME Value="MyCompany" /> -->

<!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> -->

<!-- <LIS CACHEACTION="CacheOnly" /> -->

<!-- <SOURCELIST Value="\\server1\share\Office12;\\server2\share\Office12"
/> -->

<!-- <DistributionPoint Location="\\server\share\Office12" /> -->

<!-- <OptionState Id="OptionID" State="absent" Children="force" /> -->

<!-- <Setting Id="Reboot" Value="IfNeeded" /> -->

<Command Path="C:\Temp\NoAdmin_End.cmd" ChainPosition="after"
Execute="install" />

<AddLanguage Id="en-us" ShellTransform="yes"/>

<AddLanguage Id="es-es" />

</Configuration> >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*

 

[Steven]

Hi Bob,

thanks, the idea is a good one, but it didn't work.
There isn't even an entry in the Install Log file. It seems to be jumping
over the COMMAND. Strange..maybe one reason could be the CMD file is on a
DFS share that is mapped to the Y:\ Drive. hmmm I will try to look more into
this and do some more tests.

Cheers,
Steven

 

[Bob Buckland ?:-\)]

Hi Steven,

Hmmm. It could be the mapping rather than using a UNC, but I might expect a 'file not found' entry in the log at some point, but
try putting the files locally and see what happens. I'm assuming that the MSOCache has already been setup?

Have you enabled verbose logging in the config.xml
<logging="Verbose"/>

Did you try it as a VBScript, a .BAT or just as the .CMD?

This is an article on using a batch file as a wrapper to the install set that you may want to try
http://support.microsoft.com/kb/928467/en-us?FR=1

What is the command line you're using to call the config.xml when you're running setup?

Can you paste or email your revised config.xml and the contents of the script and cmd file and log file?

=========
Hi Bob,

thanks, the idea is a good one, but it didn't work.
There isn't even an entry in the Install Log file. It seems to be jumping
over the COMMAND. Strange..maybe one reason could be the CMD file is on a
DFS share that is mapped to the Y:\ Drive. hmmm I will try to look more into
this and do some more tests.

Cheers,
Steven >>
--

Bob Buckland ?
MS Office System Products MVP

*Courtesy is not expensive and can pay big dividends*