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)
Win2K SP4
intel
HI,
so our IT department installed Win 2000 Service Pack 4 without clearing it with us, and now the TeamSite GUI isn't working. Running perl scripts etc works fine but any browsing through the GUI can't be done.
Launching the GUI and clicking Workarea, say, will just give a page with the Teamsite version on it (which is Version: 5.5.2 Build 11020 Interwoven 20020823)
Of course, the immediate answer would be to uninstall SP4 and see if that makes a difference, but IT in their infinite wisdom didn't opt to back up files when installing, so thats not a possibility.
SP4 only came out last week, but I was hoping someone else on the forums might have had a similar experience, perhaps with other Microsoft upgrades.
Thanks for your help.
Jason
Find more posts tagged with
Comments
Migrateduser
We are looking at when we can test this new MS release. Interwoven Product Management is scheduling th is in the release planning. Regards,
lissa
mdang
checkout:
http://support.microsoft.com/default.aspx?kbid=821546
An experiment workaround according to the MS support article is to add the TSIMP_<machine_name> user to Impersonate a client after authentication and Create global objects rights.
The TSIMP_<machine_name> account is added when in TeamSite installation.
intel
Thanks mdang,
I had a play around with that, even going so far as to assign those rights to Everyone, but it didn't work.
oh, well
Migrateduser
Also tried this but to no avail. Anyone from Interwoven have an answer for this ? Our security policy means that we cannot run any of our Teamsite servers any more.
Edited by nichporter on 08/12/03 06:15 AM (server time).
mdang
I also tried different combinations of the security policy on Windows SP4, but it seems not able to get around the problem. Currently, TeamSite is not supported in Windows 2k SP4. As Lissa mentioned, we will need the official support release on Win SP4 to solve this issue.