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 during V8 Workspace Extensions vgnimport

Jesse_Estum

I'm in the process of installing the V8 Workspace Extensions and have successfully done the vgnimport of otm.zip but I am getting a failure when I try to vgnimport inlink.zip.

Any ideas on how to get around this would be greatly appreciated! Thanks!

The command I'm using looks like this:

vgnimport -f ./inlink.zip -u vgnadmin -p PASSWORD -h host:27110 -c conflictPolicy=overwrite

The command output looks like this:

Importing from file "./inlink.zip"...
Processed 15 of 22 objects.
Processed 18 of 22 objects.
...object failed during processing, stopping. (See '-c errorPolicy' for behavior options.)

date=Jul 14, 2011 level=INFO entries=1
1) type=contentType name=ImageWrapper ID=16bedb2b78e26210VgnVCM1000006450140aRCRD action=IMPORT status=FAILED start=15:01:44.430 duration=128
note=07/14/2011 15:01:44:557, Error 13 (MOCommitError), Message 026-132-0009: The name for the type is already in use: ImageWrapper.

Imports: succeeded=17 ignored=0 failed=1
Deletes: succeeded=0 ignored=0 failed=0
Total processed=18.

Find more posts tagged with

Comments

Mario_DAnna

Can't you read the error ? It says "The name for the type is already in use: ImageWrapper." This means that you already have a CT called ImageWrapper in your system. So remove that CT from the vgnimport package and restart the import.
M

From: eLink Entry: Discussion Group - Web Experience Management <v7webcontentmanagement@elinkkc.opentext.com>
To: eLink Recipient <devnull@elinkkc.opentext.com>
Sent: Fri Jul 15 15:47:44 2011
Subject: Error during V8 Workspace Extensions vgnimport

Error during V8 Workspace Extensions vgnimport

Posted byjesse.estum@securian.com (Estum, Jesse)On 2011/07/15 09:31

I'm in the process of installing the V8 Workspace Extensions and have successfully done the vgnimport of otm.zip but I am getting a failure when I try to vgnimport inlink.zip. Any ideas on how to get around this would be greatly appreciated! Thanks!The command I'm using looks like this:vgnimport -f ./inlink.zip -u vgnadmin -p PASSWORD -h host:27110 -c conflictPolicy=overwriteThe command output looks like this:Importing from file "./inlink.zip"...
Processed 15 of 22 objects.
Processed 18 of 22 objects.
...object failed during processing, stopping. (See '-c errorPolicy' for behavior options.)

date=Jul 14, 2011 level=INFO entries=1
1) type=contentType name=ImageWrapper ID=16bedb2b78e26210VgnVCM1000006450140aRCRD action=IMPORT status=FAILED !start=15:01:44.430 duration=128
note=07/14/2011 15:01:44:557, Error 13 (MOCommitError), Message 026-132-0009: The name for the type is already in use: ImageWrapper.

Imports: succeeded=17 ignored=0 failed=1
Deletes: succeeded=0 ignored=0 failed=0
Total processed=18.

[To post a comment, use the normal reply function]
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01

Jesse_Estum

Yes, I can read the error.

I've had quite a nightmare trying toget a successful VCM 8 upgrade which prompts the "ask first"approach before just pulling things out of the import package. Obviouslyremoving the item from the import package will get around this error messagebut will that cause problems with the inline links extension? I.e.,are there changes between the inline links extension in VCM 7.6 and 8.0that require me to import this new ImageWrapper ContentType? If so,what do I do with the existing instances of ImageWrapper?

In short--is it SAFE to pull the ImageWrapperCT out of the import without jeopardizing the integrity of the inline linksextension?

Alex_Sun

We had this error when we upgrade to V8.

The 7.6 image wrapper has a different guid id than v8 import package, that's the reason it cause a failure.

Jesse_Estum

Alex,

What did you do to get around it? Did you edit the import package to make the GUID match the one that was in the 7.6 import? Or ... ?

Thanks.

Alex_Sun

Can you do a compare between v7 and v8?

Just remember eighther content type guid or xml name inconsistent between v7 and v8.

We are luck because we don't have Constant insance of Imagewrapper, so we just delete the content type in VCM server and then import it.

Jesse_Estum

I ended up deleting the CTD in VCM andimporting over top of it. Before that I tried manipulating the packageso that the content management ID and VCM ID matched what was already inthe VCM but that did not work.

Thanks to all for the assistance.

Mario_DAnna

I had told you to remove it from the import package. Anyway, ifyou don't have problems anymore that's fine

ciao

-m

From: eLink Entry:Discussion Group - Web Experience Management[mailto:v7webcontentmanagement@elinkkc.opentext.com]
Sent: Friday, July 22, 2011 3:28 PM
To: eLink Recipient
Subject: Re Re Re Error during V8 Workspace Extensions vgnimport

Re Re Re Error during V8 Workspace Extensions vgnimport

Posted by jesse.estum@securian.com (Estum, Jesse) On 2011/07/22 09:26

I ended up deleting the CTD in VCM and importing over top of it. Before that I tried manipulating the package so that the content management ID and VCM ID matched what was already in the VCM but that did not work.

Thanks to all for the assistance.

[To post a comment, use the normal reply function]
Topic:	Error during V8 Workspace Extensions vgnimport
Forum:	Discussion Group - Web Experience Management
Livelink Server:	knowledge-wlweb01