nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Teamsite 6.7.1 SP1 Installation

drhaas

Has anyone upgraded from 6.7.1 to 6.7.1 SP1?

I'm curious as to how difficult the migration / installation is and how long it took you to do it.

I've looked through the documentation, but am confused as to whether or not we need to reconfigure the servers, add groups, etc... after the install.

Thanks -

Dave

Find more posts tagged with

Comments

nipper

My upgrade was pretty easy. However I have seen some changes in the way some of the OOTB workflows behave. I use the Default Submit WF for my config branch and it is not working (deployments) since SP1 was loaded. I have a support case open for it.

I hope you are planning to place this on a dev server and test the heck out of it.

Andy

Jeffc

I upgraded our Windows2003 dev box from TS 6.7.1 to 6.7.1 SP1. The installation is pretty straight forward however I still have outstanding support tickets. We ran into problems with the new tagging GUI and TinyMCE.

The readme suggests that not configuring the new taggui will cause it to use the old taggui; however this was not the case. Unless we create a new datacapture file using datacapture6.0.dtd format we get an error when attempting to tag a DCR. Since the new taggui only supports tagging of single files (tagging multiple files always reverts to the old taggui), maintaining both datacapture files would be necessary.

Although some fixes to TinyMCE were included with SP1, there is a new problem with adding images. If an image is added to a TinyMCE window, it is displayed as a red X. This does not affect the published output; however graphics cannot be displayed in the TinyMCE window. What really amazed me with this issue is that IW documented it as a known issue in the release notes!

Other minor issues include:
- "Saved Search" window is added to CCSTD. This can easily be removed with a change to the "portal_custom.xml"
- There is an inconsistency with the way domain users and groups are displayed in ContentCenter. In some cases the AD domain is used and in others the NetBIOS domain name is used. This does not seem to affect functionality
- Supported versions of OD and MT are 6.1.1 and 4.1.2 respectively. We are using 6.1.0 and 4.1.1 and they seem to work, however these versions have not been tested by IW.

In summary, we will not be rolling out SP1 any time soon.

Jeff

Hans

I am also looking for feedback on SP1 installation, specifically for solaris.

We currently have 6.7.1 on our dev machine and are considering SP1 before rolling out to production. This might not be a good idea.

Any difficulties encountered during installation? Afterward?

Important - any performance issues?

Many thanks for any comments or advice.

cheers,

Hans

ExplodeLargestPieSlice.rptdesign

nipper

My upgrade was pretty easy. However I have seen some changes in the way some of the OOTB workflows behave. I use the Default Submit WF for my config branch and it is not working (deployments) since SP1 was loaded. I have a support case open for it.

To follow up on the OOTB workflows, to use these new implementations of the WFs, you need to configure the deployment command to run via URL. It is described on page 39 of the 6.7.1 SP1 WF Dev guide. While this doc talks a great deal about how to customize the OOTB WFs, it does not mention this step as a requirement.

You can also load the 6.7.1 WFs without the URL commands.

Iysh

Hello All,

I installed TS 6.7.1 SP1 and facing issues in start up of TeamSite. It starts up only when manually started.

Let me know if any of you faced this issue.

Regards,
Iysh

Jot

We have the Same issue. Installing Teamsite on W2k3 SP1 on a HP DL580 Server fails, due to the iwserver.exe service crashes.

I didn't have this problem on another machine with W2k3 SP2.

regards
Jörn

nipper

We have the Same issue. Installing Teamsite on W2k3 SP1 on a HP DL580 Server fails, due to the iwserver.exe service crashes.

I didn't have this problem on another machine with W2k3 SP2.

regards
Jörn

Exactly what rev of TS ? 6.7.1 with or without SP1 ?

I have the issue with 6.7.1 (no SP) iwserver dies intermittently with
An unhandled win32 exception occurred in iwserver.exe [1608].

in the event viewer, nothing *at all* in any of the other logs.

Win 2K3 EE with SP2 here.

I have filed a case with support.

Jot

we have this problem directly after the reboot. The IIS Confgure Screen comes up, but dies when I press "OK".

When I close these windows it starts windows but the iwserver.exe crashes all the time.

All of this happens right after the TS 6.7.1 installation without SP1 I think it makes no sense to install the SP1 when the normal Version is not running correctly.

We also have W2k3 EE but only with SP1 because of the HP Server.

If you get any answer from Interwoven Support, please write that here.

Jörn