What is the downside of not Upgrading DST for TS

Andy,

Have you tried just upgrading the JVM instead of installing SP3? I decided not to "upgrade" to SP3 for several implementations because (1) I don't know if Interwoven is going to eventually charge customers for this patch, (2) I can't be certain of what the upgrade path limitations might be of upgrading to SP3 and (3) Interwoven just plain waited until just about the last minute to even come up with SP3, which was a real disappointment IMO.

Dave

Never thought of that, what did you do ?

Basically the same as OpenDeploy ?

Pretty much -- from the support site, they've published some nice documentation on TS fixes. Of course, they mention SP3 but they've also provided information on upgrading the JVM.

As I recall, it's basically a matter of downloading "tzupdater-1_0_1.zip" from Sun.

Making matters worse is that the error is still on the system even after uninstall of SP3. Our dev server is totally unusable.

Andy

Is it possible to uninstall SP3? I figure that Interwoven is more sensible than Microsoft, which forces you to go through hoops to uninstall anything of theirs and even sometimes then, it doesn't work.

Sorry if I sound bitter -- I have some recent issues with them.

Well, the uninstall worked, about TS reports 6.5 SP2. The problem is that the error is still showing up.

CC STD shoes a blank screen. CC Pro shows the top half, but when the browser is trying show branches, stores or files, you get the java.lang.NoClassDefFoundError

Workflow tag works, Admin tag partially, looks like it is having trouble reading files as well.

I am thinking uninstall SP2 and reinstall SP2.

nipper,
i am experiencing the exact same issues on w2k3 sp1...

did you reboot the box after uninstalling?

in my case, i installed sp3 on top of sp2, i had the same java error and changes in my interface, i uninstalled sp3, some errors were gone, but i still have changes in the interface, so i re-run make_toolkit.ipl, i also restored some of my folders like content_center from a backup i had before i installed sp3...

i hope you have back up of iw-home from before you installed sp3, it will help you to get back TS in good shape...

and yes i also saw in the documentation that iwov came out with that you can upgrade the jre in teamsite just like you did with opendeploy using tzupdater.jar from sun java

Picture-Of-Layout.bmp

Output.pdf

default_report.rptdesign.txt

an update from the support:
------------------------------
It seems like the tomcat cache was not cleared of SP3 stuff. Clear the cache by deleting the directory IWHOME\servletd\work\Catalina, then reboot.
When you restart TeamSite, the directory will be automatically recreated and re-populated.
--------------------------------------
i think i tried it before and it didnt work, but you can try and let us know how it goes...

Tbag

You're saying to clear the Tomcat cache in order to get your rollback to work, right?

Nice -- I'm glad it took Interwoven until March 1 to get this very important service pack out the door and it apparently *still* has problems.

Tbag

Now, now, Dave. Don't bite the hand that feeds you...lest IWOV make you their ruby-colored **** ;-)

i am sorry, no the update i got from interwoven is for sp3 to work... but yeah i think you should the same thing i fyou are rolling back....

actually this is the second time i roll back, this time teamsite is working properly but the interface doesnt wanna go back to how it was, it still shows "Ajuba brand name and image and other extra tabs that were added from sp3..."

Interwoven doesn't many anybody their ruby-colored **** anymore, dude. Have you seen their support site in the past couple of weeks? It's emerald-color **** all around.

IwovHeather

Hi,

For DST, all SP3 contains is an automatic updater for the JVM (in addition to other non-related bug fixes)- if you do not want to install SP3, you can follow the instructions to update it manually.

This is the expected impact of not performing the JVM upgrade:

For some product versions of TeamSite, the time displayed on the User Interface, such as creation or last modified time, will be off by one hour.

Dave...
We added in the bug fix for SP3 to update the jvm to make it easier for customers than upgrading their JVM. This was added to a pre-existing schedule for SP3, containing other fixes, which is why it was not released sooner. For customers on a tighter schedule, we released procedures for upgrading the JVM manually in early February. I personally would have preferred that Congress not change the Daylight Savings - but that's my own political slant.

Also - yes, Iwov is going green Smiley Very Happy

We'll start showing preferencial treatment to all our emerald members soon - and watch the language guys.

Hope that helps clarify some,

Heather

TestReport.rptdesign

Heather,

Is the JVM upgrade sufficient then for folks who would rather avoid SP3? That upgrade was entirely painless.

I don't mind having another 4 weeks of DST, personally. Then again, we're moving our clocks into summer mode in a few days and it's still %&@#-ing snowing.

Dave

IwovHeather

Hi Dave,

Yup you are right, I am glad to hear the JVM upgrade for you was painless. Customers can do either tha manual upgrade, or apply SP3 to do it for them, but they do not have to do both.

There are some good fixes to have in SP3, but we don't typically require an upgrade to service packs. In this case, it made sense to include the JVM update in the Service Pack because we knew that the other bug fixes contained in the service pack would be desirable for customers, and we wanted to save them the trouble of the manual update if they were also planning to install SP3 anyways.

It's nice and sunny out here in California. I don't mind having the extra hours of light, but I hate getting up earlier in the morning.

Heather

Heather,

Is the JVM upgrade sufficient then for folks who would rather avoid SP3? That upgrade was entirely painless.

I don't mind having another 4 weeks of DST, personally. Then again, we're moving our clocks into summer mode in a few days and it's still %&@#-ing snowing.

Dave

Working with support, we got it back up. We removed the catalina folder as Chris had mentioned, but also needed to rebuild the GUI with install_webapps.ipl -i -f -jsp_precompile

Andy

i rolled back to sp2 by rebuilding the interface using

iw-home/install/install_webapps.ipl -i -f content_center----

i also just updated the DLS with tzupdater from sun.

so to roll back:

uninstall sp3, reboot the box, delete catalina, run install_Webapps.ipl

darlomis

After installing TS SP3, we ran into the java.lang.NoClassDefFoundError as well. However, precompiling the JSPs (install_webapps.ipl -i -f -jsp_precompile) didn't help us. I am still working with support.

That is not good. It fixed the issue for SP2, I just loaded SP3 and am rebooting.

I will rollback and precompile again if I need.

System rebooted and still failed. We are uninstalling. Again. Smiley Sad

Andy

i tried 3 installation, 2 downloads, and make_toolkit and deleted catalina... but still no luck with sp3 so i had to roll back again to sp2... i hope nipper figures it out Smiley Very Happy

so he will sell the solution to iwov, i know he takes paypal...

Went from good to bad to worse.

When I uninstalled SP3, I was actually getting the NoClassDefFoundError in the uninstall DOS shell that popped up.

I thought, this is not good.

Uninstall completed. GUI will not start at all, servletD dies.

I hoped reinstall/uninstall SP3 again would work (thinking there was leftovers) Nope.

Basically my JVM is hosed.

\iw-home\tools>java\bin\java -version
Error occurred during initialization of VM
java/lang/NoClassDefFoundError: java/lang/Object

So the uninstall from SP3 removed the SP3 stuff, but did not restore the SP2 piece.

Ugly.

how is it going with this nipper? did you get sp2 working again? did you get sp3 working? support gave me some steps to get sp3 working, but i rolled back to sp2 and i will wait till somebody confirms the steps to have clean installation...

this is what i got from the support:
The below steps worked for another customer with your issue:

1. Rename the \servletd\work directory,(TeamSite will recreate this automatically upon startup)

2. Rename \httpd\webapps\content_center (TeamSite will recreate this automatically upon startup)

3. Recompile the webapps with -i -f -jsp_precompile.

4. Run make_toolkit.ipl.