LiveSite Install 2.2.1: There are no components available.

TeamSite 6.5 SP2
LiveSite 2.2.1
Windows Server 2003 Enterprise SP1

Another department installed LiveSite and it seems to work;however, when I go to add component to a page I get this in the pop-up:

"There are no components available."

Same with Templates:

"There are no templates available."

Did the components/templates FAIL to install?

Where should I look (log files?)?

Can I just reinstall LiveSite to fix this or will it require an UnInstall/ReInstall?

Many thanks!

Find more posts tagged with

Comments

wscott

Some possibilities:

1. Components failed to install
Check "/livesite/main/component/WORKAREA/Installed Components" and "/livesite/main/component/STAGING" and see if there are any component files in there. There should be some. If there aren't, then they must have failed to install.

This problem is usually caused by having LiveSite installed by a user that doesn't have permission to create branches, or if the branches already exist, they don't have permission to write the files into them or submit them.

You can correct it by running livesite-install-dir/livesite/component_import.bat and pointing it at the components (which I think are zipped up as base_components.zip). The component_import.bat file contains its own instructions, so you should open it before you run it. Be sure to run it as a user who has "Master" role and also file-level permissions to the branches/directories involved.

2. Your user doesn't have permission to read the components
Even if you're Master, you need to have file-level Read permission to all the components in "/livesite/main/component/STAGING" for them to show up in the pop-up when you click "Add Component."

You can fix this by making sure your user is part of a group that has Read access to "/livesite/main/component/STAGING." If your TeamSite instance is only going to be used for LiveSite development, it's probably best to just make that branch readable by everyone. You may want to make all the workareas beneath it accessible to everyone too, or you could have a step in the submit workflow so that whenever a file is submitted to that area its ownership changes to everyone. (I think this is a standard part of the default workflow.)

3. Some other error
If there is some internal error, it will show up in the log file at iw-home/local/log/iwui/servletd_out.log. If you see a bunch of stack traces (a block of indented lines beginning with "at com.something.something" and ending with "(Something.java:1234)"), or really just see the word "error" anywhere, it could indicate a problem.

RichDiaz

Thanks Will,

It seems that the "LiveSite installed by a user that doesn't have permission" is the issue:

Ok, I looked at component_import.bat and I have a question on:

set COMPONENT_DIR=C:\temp\ComponentExport

The "C:\temp\ComponentExport" directory doesn't exist (no surprise there)

But "D:\interwoven\LiveSite\livesite\base_components" DOES exist and its filled with .component files. This is the directory to use, correct? (base_components.zip is not present)

RichDiaz

ok I ran the above and it worked. I can see and add components to my LiveSite pages.

However, all the component image links are broken and a JavaScript file (ajaxRequest.js) is missing for the Ajax File Explorer component.

I looked on the server and found the files in

\interwoven\LiveSite\livesite\base_components\resources
but shouldn't these resources just be referenced from THAT directory?

e.g. this is where the LiveSite Site Map component is looking for its graphic (i.e the broken link).

http://SERVER/iw-cc/livesite/common/img/clear.gif

all guidance appreciated!

wscott

LiveSite can't read that directory -- it contains installation data but isn't used at run-time. Everything that LiveSite reads is contained on the Y: drive somewhere (except for a few config files that are under iw-home).

The resources need to be copied into your workarea for the component to read them. Just copy everything under the resources directory (not the resources directory itself, though; just everything within it) into the workarea where your sites and pages are. Because javascript and image files are "just files" to LiveSite, there's no special import script needed.