LiveSite migration problem

I updated my LS 2.1.0 installation to the 2.2.1 version.
After installing the software I run the migration.bat tool which fails reporting the attached error (java.lang.NullPointerException).

Now I'm not able to preview any component or page. When I try to edit a page or preview a component I receive the following error: "Unable to preview because no sites are available. Create a site and try the preview again". I created a new site, but nothing changed.

I also cannot edit any default.site file or create new components.

Is there anybody that can help me with this issue?

Thank you very much.

Find more posts tagged with

Comments

wscott

Sorry, you need to upgrade from 2.1 to 2.2 and then to 2.2.1.

mindy1

Hi All,
I am facing the same issues...

few bugs..

* Unable to create new pages in earlier livesites created in LS 2.1
* Unable to view sites created in LS 2.1:The error message is,'Page Rendering Failed. Contact your Administrator.'
* Unable to run the migration script on livesites created in LS 2.1
* Unable to view components/templates created in LS 2.1 under livesite backing store
The error message is:Unable to preview because no sites are available. Create a site and try the preview again.
* Unable to edit the components created in LS 2.1 under livesite backing store

error message is:
Component preview failed.
Could not load component XSL into XMLDOM.
com.interwoven.livesite.common.xml.ValidationError mColumn[74] mLine[26] mSystemID[null] mPublicID[null] mType[ERROR] mMessage[link is not allowed in this position in the stylesheet!]

any hints?

mindy1

another thing is ,it is not mentioned anywhere in installation guide or release notes that we need upgrade from 2.1 to 2.2 and then to 2.2.1.
It will be really helpful to do that so that people doing the upgrade in future are benefited.

magikandrea

Hi mindy, which is the OS where your TS-LS is running? I have a win 2003 Server and I had to upgrade it to the SP1.

Andrea

mindy1

same with me

wscott

Are you still seeing this problem, after upgrading from 2.1 to 2.2 to 2.2.1?

Also, we are improving our migration procedure to allow upgrades from 2.1 directly to 2.2.1, but I don't have an ETA for it yet.

mindy1

At least I am able to resolve all the issues with the help of IWOV engineer who visited us..

Thx...