nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

applyExtAttr is specified for sourceFileSystem

ProfessorX

Hi

Im deploying from a TS OD Dev to a TS OD Prod. Both have
TS 6.7.2 SP1
OD Version 6.2.0.0.0 Build 68916 Interwoven 20071109

I have an OD config that works fine seperatly (see attached) menaing if I comment one the other works by itself and vice versa

But running them together in the OD Admin GUI gives me
Failed converting config file c:\iwov\OpenDeployNG\conf\myodconfig.xml. Error : CONFIG_FILE. Details: applyExtAttr is specified for sourceFileSystem

Also both work together if I set applyExtAttrs="no" /> in the one definition

I have teamsite.version: 6.7.0 set in the deploy.cfg file on both dev and prod OD bases.

You think this is a bug? Or am I doing somehting wrong?

Find more posts tagged with

Comments

Firenze

I validated your XML against DTD and ran into some validation errors.

First with with targetTeamSite, DTD expects:

There are some other minor issues with your transferRules and logRules at the wrong location but nothing like the above missing elements.

ISCBorisB

I validated your XML against DTD and ran into some validation errors.

First with with targetTeamSite, DTD expects:
<pathSpecification>
<path name=""></path>
</pathSpecification>

There are some other minor issues with your transferRules and logRules at the wrong location but nothing like the above missing elements.

Professor has it as:

   <pathSpecification>
      <path name="."/>
   </pathSpecification>

By XML syntax it is semantically equivalent to:

   <pathSpecification>
      <path name="."></path>
   </pathSpecification>

'logrules' is a sub-tag of 'deploymentConfiguration', it can be placed anywhere right under deploymentConfiguration, at the beginning, at the end or in the middle.
Similarly, 'transferRules' is a sub-tag of 'target', etc. In short, there is nothing syntactically wrong with the XML itself.

Adam Stoller

Hi

Im deploying from a TS OD Dev to a TS OD Prod. Both have
TS 6.7.2 SP1
OD Version 6.2.0.0.0 Build 68916 Interwoven 20071109

I have an OD config that works fine seperatly (see attached) menaing if I comment one the other works by itself and vice versa
<EXECDEPLOYMENTTASK useDefinition="d1" />
<EXECDEPLOYMENTTASK useDefinition="d2" />

But running them together in the OD Admin GUI gives me
Failed converting config file c:\iwov\OpenDeployNG\conf\myodconfig.xml. Error : CONFIG_FILE. Details: applyExtAttr is specified for sourceFileSystem

Also both work together if I set applyExtAttrs="no" /> in the one definition

I have teamsite.version: 6.7.0 set in the deploy.cfg file on both dev and prod OD bases.

You think this is a bug? Or am I doing somehting wrong?

First of all - element names are case-sensitive so "execDeploymentTask" is valid, while "EXECDEPLOYMENTTASK" is not - however that's probably moot, as your posted configuration file has it correct.

I am confused however about the error message which does not seem to jive with the config file. The error message, according to your post, says "applyExtAttr is specified for sourceFileSystem", however in the posted config file, the only instance of applyExtAttrs is associated with targetTeamsite, not sourceFilesSystem.

Can you confirm this contradiction? Or did the error occur when you made a change (not shown) to your config file - and actually placed the directive in the wrong place?

CRB

Hi

Im deploying from a TS OD Dev to a TS OD Prod. Both have
TS 6.7.2 SP1
OD Version 6.2.0.0.0 Build 68916 Interwoven 20071109

I have an OD config that works fine seperatly (see attached) menaing if I comment one the other works by itself and vice versa

But running them together in the OD Admin GUI gives me
Failed converting config file c:\iwov\OpenDeployNG\conf\myodconfig.xml. Error : CONFIG_FILE. Details: applyExtAttr is specified for sourceFileSystem

Also both work together if I set applyExtAttrs="no" /> in the one definition

I have teamsite.version: 6.7.0 set in the deploy.cfg file on both dev and prod OD bases.

You think this is a bug? Or am I doing somehting wrong?

did you create this config using UI Admin or you copied it from old configs to use with OD 6.2?
i would suggest using Admin UI to recreate deployment configs for OD 6.2 instead of migrating them from old versions.

screen.png

ProfessorX

my bad...Heres the one I used...I also used that one and it gave the same or simliar error

ProfessorX

did you create this config using UI Admin or you copied it from old configs to use with OD 6.2?
i would suggest using Admin UI to recreate deployment configs for OD 6.2 instead of migrating them from old versions.

I tried it with both ways and same result

ProfessorX

Ok after speaking with a very smart person he suggested I change the sequence of the execDeploymentTask calls.

He suggested I call the one that deploys outside the area of the store (sourceFilesystem, useDefinition="d2") first and then call the one that deploys to the store with applyExtAttrs="yes" (,, useDefinition="d1") second.

By a simple switch from
execDeploymentTask useDefinition="d1"
execDeploymentTask useDefinition="d2"

to
execDeploymentTask useDefinition="d2"
execDeploymentTask useDefinition="d1"

The deployment worked...I also did due dilgence in making sure EA's were applied correctly on the target.

He/We deduced that theree may be some sort of variable being set globly that tries to interpret d2 (or any following deployment definations for that fact) as having the applyExtAttrs attribute.