XML Content Upload Error - Failed to Find Handler

[Former Member]

Hi

I am trying to upload an xml file using the tools under system administration but when I start the import I get the error cannot find handler. There are no other error messages and the view report features do not work. The handlers xml file property is <b>content.handlers.xml</b>

I have found a few postings on this issue but the only solution I have seen said that you need 2004 s

I am using 2004s

<b>version=7.0.8.0.0

Implementation-Version=7.8.0.0.200606180650</b>

Can anyone help me to identify what is missing?

Many Thanks

Andy Irvine

[Former Member · Accepted solution]

Hi Andy,

what XML file did you try to upload. Usually, you download an XML file, modify the file and upload it again. Did you modify a previously downloaded file or do you try to upload a XML file created by yourself. If you tried to upload a previously downloaded file, then explain the changes you made.

Note: The modification of ids can lead to errors.

Best regards,

Martin

[Former Member · Accepted solution]

Hi Martin

I downloaded an xml file containing worksets. The purpose being to mass change the sort priority of a folder within the workset (used as an entry point).

I want to change the sort priority of the folder with id 'mywork' from 100 to 10. As there are many roles (100s rather than 1000s thankfully) I figured this would be the quickest/easiest solution. I used find & replace on a a large section of the my work section and changed only the section shown in the code below to be 10 instead of 100.

[code]

<Attribute name="com.sap.portal.navigation.Priority" type="string">

<AttributeValue value="10.0"/>

<Attribute name="administration" type="string">

<AttributeValue value=""/>

</Attribute>

[/code]

The head of the file is as follows

[code]

GenericCreator author="XML Creator" version="XML Automatic Creation" mode="clean,execute" report.level="success" createMode="3" default.locale="en" ignore="false">

<Property name="parent1" value="pcd:portal_content/com.burberry.content/Europe"/>

<Context name="worksets" objectClass="com.sap.portal.pcd.gl.GlContext" create_as="0" parent="$">

<Attributes>

[/code]

It errors out straight away which is what led me to believe that maybe this was an issue with the portal configuration rather than my xml file. Any suggestions?

Message was edited by:

Andy Irvine

[Former Member · Accepted solution]

Hi Andy,

that sounds very strange, indeed. You should have a look into the portal's log files. Chances are high, that you will find detailed information about the error in the log files.

Best regards,

Martin

[Dan_Wroblewski · Accepted solution]

Hi Andy,

I did what you said: Exported XML for a workset, only changed the 100.0 to 10.0, and uploaded it again, and all was OK.

Can you send the error message you get?

If you want, send the screenshot of the XML upload page and the XML itself to me, and the log file if you can, and I will check or show it to the developers here, if possible.

I am assuming there are no permission issues (can you manually change properties in the workset?) or locking issues.

Daniel

[Former Member · Accepted solution]

Thanks Daniel I have emailed you the file and a screenshot of the error.

[Dan_Wroblewski · Accepted solution]

Hi Andy,

The PCD object at location pcd:portal_content/com.burberry.content/Europe/worksets/r2r/treasuryReporting/mywork/applications/treasuryReporting/FTR_EDIT is being exported with a blank object class, which is causing the error.

The question is why.

Can you check this object and tell me what is its objectclass in the PCD?

Daniel

[Former Member · Accepted solution]

Thanks Daniel

The reason that the object class for

pcd:portal_content/com.burberry.content/Europe/worksets/r2r/treasuryReporting/mywork/applications/treasuryReporting/FTR_EDIT 

was blank was that there was a broken delta link in the workset.

This showed up in the xml file as

<Context name="FTR_EDIT" objectClass="" create_as="0">

Anyone else facing this issue may want to search for <b>objectClass=""</b> in their xml file. Once the broken delta link was fixed the import worked perfectly.

Thanks to Daniel, Martin and Jana for their assistance.

[jana_richter]

Hi Andy,

one thought about that when looking at your code sample:

<Attribute name="com.sap.portal.navigation.Priority" type="string">

<AttributeValue value="10.0"/>

<Attribute name="administration" type="string">

<AttributeValue value=""/>

</Attribute>

Did you close the first Attribute as well? (or might there be one </Attribute> missing?)

Moreover, did you check on the context's object class, whether this one is right as well?

Hope this helps, best regards

Jana

[Former Member]

The code is only cut from the original file. It was just to show the single value that I had changed so there should not be any issues with file structure or object class.

Thanks though.

[Former Member]

Hi Andy,

what XML file did you try to upload. Usually, you download an XML file, modify the file and upload it again. Did you modify a previously downloaded file or do you try to upload a XML file created by yourself. If you tried to upload a previously downloaded file, then explain the changes you made.

Note: The modification of ids can lead to errors.

Best regards,

Martin