cancel
Showing results for 
Search instead for 
Did you mean: 

TREX WPC Help!!

Former Member
0 Kudos

I am having a problem with a index picking up the WPC content. I changed the hostname in the url generator, checked the properties, checked the trace logs... Still having problems. The index starts out with an idle status and then after about 1 minute goes to error and displays this error:

/wpccontent/Sites/Help Content/Web Pages/New Page/output.xml

Trex: Preparation failed: index operation

It is finding the content but wont index it. I haven't been able to find a fix for this error. Any suggestions?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Bridgette,

I'm afraid without a clear exception statement from your defaultTrace or a TRC file in your TREX trace directory it is not possible to say what is wrong. It would be necessary to access your system to have a closer look.

You could open an OSS ticket and give access to SAP support for additional help.

Best regards,

Robert

Former Member
0 Kudos

Hi, over the weekend I was able to get access to the Netweaver Administrator. Here is the error that itis giving me in the Traces. I realize it has something to do with the role but the WPC is setup exactly as it should be with a role created and then a folder created within that role that the external connector points to the WPC navigation.wpc

Here is the error:

URL does not point to an object of type INavigationConnectorNode: portal_content/administrator/super_admin/super_admin_role/com.sap.portal.system_administration/com.sap.portal.system_admin_ws/com.sap.portal.system_configuration/com.sap.km.AdminConfig/com.sap.km.AdminSystemIndexes/relatedItems/RelatedLinks

Former Member
0 Kudos

Hi Bridgette,

Do you have a cluster installation with multiple nodes?

You might want to check the KM Configuration -> Content Management -> Global Services -> Scheduler Tasks and there the configuration of the IndexServiceTaskQueueReader.

Make sure there is a system assigned.

See if this helps. If not, as mentioned before, access to the system would enhance the possibility to trouble shoot, so think about opening an OSS message.

Hope this helps,

Robert

Answers (2)

Answers (2)

Former Member
0 Kudos

We had this same WPC indexing issue on NW7 SP14 due to content being developed on one portal then moved via KM Transport with GUIDs to another portal. The wpc_wcm_trex_url property of the output.xml files associated with the Web Pages retained the full URL to the original server causing the indexing to fail on the new server. See [Note 1315079|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1315079] - How to edit wpc_wcm_trex_url property of a WPC page

We upgraded to SP18 patch 3 and the wpc_wcm_trex_url property has now been reformatted as a relative url but every Web Page created prior to the upgrade had to be republished in the target environment for the property to reset. Once the wpc_wcm_trex_url properties are reset to relative URLs the TREX indexing works perfectly.

Former Member
0 Kudos

Any Ideas?