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; } } }

Error while creating new DCR

rutu

TeamSite 7.4.1, Win Server 2008

---------------------------------------------

When I am using "New Form Entry", I am getting error mesage

"A problem was encountered trying to read the datacapture.cfg file for type communication. Please contact your system administrator"

I checked in Content_Center.log and found following

2015-01-16 15:07:40,723 [http-0.0.0.0-8080-45] ERROR com.interwoven.ui.base.impl.command.CommandHandler () -
forward "WIZARD" not handled by descriptor iw.ccpro.create_form

What is this forward "WIZARD" and how can I solve this error ?

Find more posts tagged with

Comments

Rick Poulin

This can happen when TeamSite gets confused about where you are -- e.g. if you have multiple tabs open to different locations or if you're sharing a user account with someone else.

The action you're trying to do is in CCPro. I'll bet if you open a new tab to the root URL of your teamsite server, you'll find that you're elsewhere (admin console / TSUI / CCStd / CCPro but outside of a workarea). Navigate back to the right context and try the action again.

rutu

Few tabs were open.

I closed all the tabs and logged out. Logged in again and tried "New Form Entry".

But still when I do "New Form Entry", I get the same error

"A problem was encountered trying to read the datacapture.cfg file for type communication. Please contact your system administrator"

I checked in Content_Center.log and found following

2015-01-16 17:47:32, 723 [http-0.0.0.0-8080-45] ERROR com.interwoven.ui.base.impl.command.CommandHandler () -
forward "WIZARD" not handled by descriptor iw.ccpro.create_form

Adam Stoller

Are you sure you have access to he DCT?

Or perhaps the DCT uses an inline to load the actual XML code for he DCT and maybe you either don't have access to the inlined script, the file that the inline script might be reading, or there's a problem with the inline script in general.

Without knowing a lot more about the environment and the specifics of the setup it's difficult to tell - but I would investigate the permissions side of things...

rutu

There were few inline scripts. I had the same doubt like you. So I removed all inline scripts to check and left entire DCT with 2-3 text and textarea fields only. But same error.

As far as access to DCT is concerned. Before I was getting permision error. Once I set permision all the way from branch to workarea level, that permision error is gone. But now I am getting this error.

Another questiuon on permision. If I have master access, do I automatically get permission to access all files ? OR do I still need to add myself to groups who is owner to the branch and work area ?

AIRS IND2_V2.rptdesign

nipper

rutu wrote:
Another questiuon on permision. If I have master access, do I automatically get permission to access all files ? OR do I still need to add myself to groups who is owner to the branch and work area ?

You still need OS Level permissions to read and edit files. So yes, you need ot be in the appropraite groups.

rutu

I have admin level access on WS8 and Master acces to TeamSite741. DOes this grant me acces to all files OR Do I still need to be added to groups which have branch level access ?

nipper

OS level permissions still matter. Make certain you are a memeber of the group that owns the workarea and the underlying files.

rutu

nipper wrote:
OS level permissions still matter. Make certain you are a memeber of the group that owns the workarea and the underlying files.

I am member of the group that owns the WA OR has access to modify files in WA.

But I am still getting same error.datacapture.cfg is fairly sinmple as follows

<?xml version="1.0" standalone="no"?>
<!DOCTYPE data-capture-requirements SYSTEM "datacapture6.0.dtd">

<data-capture-requirements type="Content" name="Procedure">

	<ruleset name="Procedure">	

		<description>This DCT is used to capture Web </description>



		<container name="DocumentInformationContainer">

			<label>Document Information</label>

			<item name="Title">
				<label>Page Title</label>
				<text size="120" maxlength="500" required="t"/>
			</item>



				</container>

		<container name="Steps">

			<label>Steps</label>
			<description>The following section contains information that will be displayed</description>

			<item name="Title">
				<label>Display Title</label>
				<text size="120" maxlength="500" required="t"/>
			</item>


			<item name="displayTinyMCE_Body">
				<label>Content Preview</label>
				<textarea height="100" width="200" required="t" readonly="t" external-editor="tinymce" />	 
			</item>

		</container>

		<container name="AdditionalTab" min="0" max="unbounded" default="0">

			<label>Tabs</label>
			<description>Use this section to add additional tabs to your document.</description>

			<item name="Title">
				<label>Display Title</label>
				<text size="120" maxlength="500" required="t"/>
			</item>


			<item name="displayTinyMCE_Body">
				<label>Content Preview</label>
				<textarea height="100" width="200" required="t" readonly="t" external-editor="tinymce" />	 
			</item>

		</container>



	</ruleset>

</data-capture-requirements>

But I am still getting same error as follows

"A problem was encountered trying to read the datacapture.cfg file for type Procedure. Please contact your system administrator."

Adam Stoller

There's a problem with your DCT, and possibly with your templating.cfg file entry for the DCT (which you haven't [yet] posted).

The problem with the DCT is that you've defined it as using datacapture6.0.dtd, but the DCT code does not conform to that DTD, it conforms to datacapture5.0.dtd - whether or not this is enough to cause the error you are seeing is difficult to say for sure (I haven't tried reproducing the discrepancy) but it is something you should definitely fix (one way or the other).

If this is a brand-new DCT from which nobody has created DCRs - I'd recommend keeping the DTD and fixing the DCT-code. If this is an existing DCT from which folks have created DCRs (seems unlikely, but ...) - I'd recommend changing the DTD unless you're willing to spend the time to fix all potential issues surrounding the change to the DCT code that would be necessary to bring it up-to-date with the newer DTD.

rutu

<?xml version="1.0" encoding="utf-8"?>
<templating>   
  <category name="Portal-Content">
    <locations>
      <branch vpath-regex="/main/Intranet" />
    </locations>

    <data-type name="Procedure" dcr-type="iwov">
      <locations>
        <branch vpath-regex="/main/Intranet/Retail/Retail_PROCEDURES" />
      </locations>
      <viewoptions dcr-autonaming="t" actionlist="save;preview" replicant-render="normal" />
      <presentation>
        <template name="preview.tpl" extension="html">
          <locations>
            <branch vpath-regex=".*" preview-dir="/">
              <directory dir-regex=".*" />
            </branch>
          </locations>
        </template>
        <template name="out-of-context-preview.tpl" extension="html">
          <locations>
            <branch vpath-regex=".*" preview-dir="/">
              <directory dir-regex=".*" />
            </branch>
          </locations>
        </template>
      </presentation>
    </data-type>........

This is fragment of templating.cfg, that has been modified by myself. Rest of templating.cfg us as is

Adam Stoller

The templating.cfg defines the DCT as being of type "iwov" - which matches with the way the DCT appears to have been written - thus the mistake is the use of the datacapture6.0.dtd instead of datacapture5.0.dtd - so try changing that and see if your problem goes away (I'm not saying it will, but it will certainly be more "correct").

That being said, if this is a brand new DCT - you would be better off declaring it to be of type "xml" and [properly] using the datacapture6.0.dtd.

vishal11

Use

<!DOCTYPE datacapture SYSTEM "datacapture5.5.dtd">