Content vendor is not defined.

[Former Member]

Hi, all.

When I try to create a Delivery Unit from the Quick Launch in the Information Modeler, the following error message is shown:

Cannot create Delivery Unit as content vendor is not defined for this system.

Then, I found the 'content_vendor = UNDEFINED' in the indexserver.ini.

Could you please let me know how I can fix this problem?

Thank you very much,

-mamoru

[Vitaliy-R · Accepted solution]

Just double-click on content_vendor, type the name of the company and confirm. If you have no privileges - ask your admin to do that.

[Former Member · Accepted solution]

Thank you very much.

Can I use the following steps?

1. Open the Configuration tab in the Administration window in HANA Studio.

2. Double click on 'content_vender' under 'repository' in 'indexserver.ini'.

3. Type my company name (e.g. XYZ Inc.) in 'New Value', then click Save.

Regards,

-mamoru.

[Vitaliy-R · Accepted solution]

Yes, that's the way it goes. -VR

[Former Member · Accepted solution]

Thank you very much!!

[Former Member · Accepted solution]

when i am creating the Delivery Unit, i am unable to see it after saving it.

Did anyone faced this before?

Regards,

Shrikant

[Former Member · Accepted solution]

This message was moderated.

[Former Member]

Hey this solution is not working for me in SP06. The Dev_Guide says I should create a delivery unit in the Livecycle Manager(lm).

The System Vendor in the indexserver.ini is already set correcly.

If I try to create a delivery unit in the livecycle manager there is the following error message:

Has anayone a tip?

Greetings

David

[Former Member]

No Idea how, but we can set the content vendor in the Lifecycle manager now.

[dirk_marwinski]

Hi,

sorry for the late reply. This appears to be a sporadic problem after a vendor change. There is a workaround: trigger a ‘reconfigure service … ’ of the ‘xsengine’ service, after the vendor change.

Hope this helps,

Dirk Marwinski

[Former Member]

Same Problem, new System. Trigger a Reconfigure on the XS Service worked! Thanks for helping.

David