Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
To SP or not to SP?
Maninder_IBM
We have recently been advised to install SP3 or SP4 over our 552 sp2b to enhance our performance as we have had slow response times and server crashes.
Any warnings? advice? anything to look out for? should we? shouldn't?
What do you think?
Find more posts tagged with
Comments
sajiddc
What kind of performance issues are we talking about? Also, have you identified the cause of the crashes? If so, did you double check and see if those issues have been addressed in the SP?
mdang
5.5.2 SP3+ has major performance improvement on DCR open/creation, and some improvement on job list.
For server crash, you need to provide more information on it. Is TeamSiter server crashed or Tomcat servletd?
StuFox
Another couple of things to consider is that there are a couple of bugs with SP3 and SP4 that make it not work with IE5.0, it works fine with IE 5.5 and IE 6.
Also currently you can only upgrade to IW 6 from SP3.
- Hope this helps
Stu
Maninder_IBM
hmmmmm... not work?? with IE5? Can you please expand?
Maninder_IBM
Stu can you expand please? Kinda waiting on this before installing. If you know of any issues or whether any formal bugs have been raised with interwoven regarding this please let me know.
Many thanks.
StuFox
HI
Sorry I should have been more specific - the main problem areas with the new SP3+ are related to templating. We have installed both in our testing environment and there are some changes to the code that means that "save & closing" of templates fail uder IE 5.0, (logged with IW) and users have reported that they can't open some DCRs that they use to, we just reset the extended attributes and the problem seems to go away.
- Stu
Maninder_IBM
Thanks for that Stu, most appreciated! I guess we'll just have to install it and see what happens.
Anyone else got any issues with 5.5.2 SP4.
Frederik
our system guys installed upgraded to 552 SP4 from 552 (base or sp1, dunno). This was on Solaris Unix.
They ran into a problem in the sense that the servlet deamon or so wouldn't start up, and as result, we didn't have the web interface running.
Now, they admitted that they might have reversed a step or so of the adviced procedure for upgrading. But the problem was that they found no way to back out of the mess any more. Even after an uninstall of SP4, the problem remained.
In the end, they wiped away that installation, and installed a fresh 552 SP4.
Luckily it was a development server, so there was no production impact.
As you can imagine, I'd advice you to test first :-)
Also, they (system guys) were adament about using SP4 and not SP3... guess the list of fixed bugs between SP3 and SP4 spooked them.
Btw : all this is based on my understanding of the story I heard from the system guys, so allow some inaccuracies ;-)
You may wish to read this earlier thread
http://devnet.interwoven.com/forums/cgi-bin/showflat.pl?Cat=&Board=PRODUCTS_TEAMSITE&Number=22261
Table_sum_demo.zip
Maninder_IBM
Thanks Frederik. Were using windows and are on SP2b. So hopefully we may not come across this problem. But I will certainly be looking out for it!
Maninder_IBM
Well it seems like we have hit our first SP4 problems.
When I log in as an author, the screen just continually refreshes and never comes up with a list of workareas and files.
Secondly, generating content to a specific area fails as the generate file doesn't allow for navigation through workareas.
Both problems are IE version independent. Have proved on 6.0 and 5.5. So far not looking good.
FontTypemanager.jpg
nipper
Is this for certain authors or all authors ? I have seen this happen with WebDesk since it is persistant and remembers where you were & what you were looking at. In our case it was look at my modified files when there are several thousand modified files to parse.
Try a new user for grins.
Andy
Maninder_IBM
Right it seemed the patch that needs to be applied over SP4 had not istalled successfully. We installed again. Seems to have solved the above problems. On with the testing!