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; } } }

Help with 6.7.2 SP2 install

shougom

We have downloaded 2 files from autonomy.
software update1: InstMs.exe
service pack 2: IWOVts-win-6.7.2SP2-Build70044

The document refers to how to install IWOVts-win-6.7.2SP2-Build70044
But I am uncertain what the software update1 is even for its not referenced in the documentation to my knowledge.

Find more posts tagged with

Comments

Adam Stoller

We have downloaded 2 files from autonomy.
software update1: InstMs.exe
service pack 2: IWOVts-win-6.7.2SP2-Build70044

The document refers to how to install IWOVts-win-6.7.2SP2-Build70044
But I am uncertain what the software update1 is even for its not referenced in the documentation to my knowledge.

I have no idea what "software update1" is either, as I've never know Interwoven to provide what looks like a microsoft EXE for downloading (there is a patch for 672SP2, but that's IWOVts-win-6[1].7.2.2-P10208-Build70082.exe)

I assume you already have the base 6.7.2 (build 69626) installed (potentially with SP1 installed on top of it) - right? Because you cannot install the SP without having first installed the base version (despite the fact that most SPs are as large as [if not larger than] the base version.

shougom

Ok will ignore the software update 1 file.

Yes we have the base 6.7.2 installed.

Autonomy provided us with a download login that expires. Apparently there was a readme file that was also available for download. I didnt get that downloaded so I have no instructions. Now Im asking them to give me another temp login to the download files area so I can get that readme.

But im waiting waiting waiting. And have no clue how to proceed. So if anyone has a 6.7.2 SP readme file please share it with me. Thanks.

Hindi Text using Arial Unicode MS.rptdesign

Hindi Text using Arial Unicode MS.pdf

shougom

Ok big misunderstanding.

Our current version is 6.7.2 build 70044

Apparently there is a patch that we need to install. Ive no clue how to install a patch. We have a file for download named: InstMsiW.exe

No instructions on how to install it. Any tips appreciated.

nipper

There had to be something with the download. It is possible that is a self extracting ZIP file, but it does not seem familiar to me. Try to download again and see if there is a README or install instructions anywhere

shougom

Ok so the file were trying to install is this one:

IWOVts-win-6.7.2.2-P11304-Build70090.exe

But I didnt see any instructions.

nipper

That is *probably* a self extracting zip, run it and see.

shougom

Ok. Would be nice if they had the documentation for that though. But will do. Thank you. There probably is an assumption that I know its a self extracting exe with some docs in it.

shougom

The download file is this:
IWOVts-win-6.7.2.2-P11304-Build70090.exe

And here are the instructions just for FYI and in case anyone has any comments. BTW what do they mean by comment spars???

Update 11304 for TeamSite 6.7.2 SP2 for Windows
Build Date: 20100325
Build Number: 70090

Prerequisite
----------------

TeamSite 6.7.2 SP2 must be installed.
Please note, this update is not to be applied to ControlHub 3.0.0.0.

Caution: this update should not be applied over 6.7.2 SP2 Patch 1

Installation Instructions
---------------------------------

1. Log in as Administrator on the system where you want to install
this update

2. Copy the IWOVts-win-6.7.2.2-P11304-Build70090.exe file to a temporary
directory on a local drive.

Note: Do not copy the .exe file into a directory whose name contains
spaces, such as C:\Documents and Settings.

3. Comment spars in toolkits.xml which refers location from ‘Y’ drive
(for example comment foundation_spar:- )

4. From the temporary directory, double-click

IWOVts-win-6.7.2.2-P11304-Build70090.exe

A TeamSitePatch subdirectory is created, into which the contents of
the .exe file are expanded.

5. Navigate to the TeamSitePatch directory and double-click install.bat.

Post installation instruction:
After the Patch install reboot (please reboot if the install doesn't reboot), perform the following steps:

6. Un-comment the spars which were commented in step 3

7. Run iw-home/iw-perl/bin/iwperl iw-home/install/install_webapps.ipl –i –f content_center –remove_work_file

8. Run iwreset -ui

Note on LiveSite Runtime
1. The runtime build 70090 is a full installer and not a mere patch. The build may be installed as an upgrade to LS3102 RTX or as a new installation
2. If installed as an upgrade, the installer requests confirmation of DB values used for LS3102 RTX

Note on un-install:-
a) Please backup all runtime customization before un-installing LiveSite Runtime
b) Before un-install please comment the foundation_spar path in toolkits.xml
c) After uninstall perform the following 3 steps
c.1) Uncomment the foundation_spar and other spar paths pointing to Y: drive in toolkits.xml
c.2) Run iw-home/iw-perl/bin/iwperl iw-home/install/install_webapps.ipl –i –f content_center
c.3) Run iwreset -ui
d. Uninstalling 70090 on the runtime end removes the application completely, and thus does not cause the runtime system to revert to LS3102 RTX

Adam Stoller

The download file is this:
IWOVts-win-6.7.2.2-P11304-Build70090.exe

And here are the instructions just for FYI and in case anyone has any comments. BTW what do they mean by comment spars???

See further down...

Update 11304 for TeamSite 6.7.2 SP2 for Windows
Build Date: 20100325
Build Number: 70090

Prerequisite
----------------

TeamSite 6.7.2 SP2 must be installed.
Please note, this update is not to be applied to ControlHub 3.0.0.0.

Caution: this update should not be applied over 6.7.2 SP2 Patch 1

Hmm, that's interesting

Installation Instructions
---------------------------------
...
3. Comment spars in toolkits.xml which refers location from ‘Y’ drive
(for example comment foundation_spar:- )
...
6. Un-comment the spars which were commented in step 3

Autonomy Interwoven's ability to write clear and concise instructions is clearly not all that great.

Step 3 should probably say something like:[indent]Comment [color=red]out the spars entry(ies) in

IWHOME/local/config/lib/content_center/toolkits.xml

which references a location within the "Y" drive[/color][/indent]For example, changing:[indent]

[/indent]to:[indent]

[/indent]As I'm not on a system with SP/LS enabled, I don't see any such entries, but I assume from the way the text is written that there may be multiple such "spar" entries in the

toolkits.xml

file - and that all of them should be commented out in step 3 and then un-commented in Step 6.

shougom

Ok. Thanks for the pretty thorough explanation. I appreciate it.

grid.zip

shougom

Ok within the directions I have a question.

It says to comment out the foundation spar in toolkits.xml before running the update.

What about any of the other spars in toolkits.xml?

Adam Stoller

Ok within the directions I have a question.

It says to comment out the foundation spar in toolkits.xml before running the update.

What about any of the other spars in toolkits.xml?

Try re-reading the directions again - carefully - it says "spar" and it says that references the "Y" drive - none of the things you posted meet those two requirements for being commented out - including the one you did comment out.

Note - there might be a different toolkit.xml file somewhere - I was assuming it was the one I "documented" before - but perhaps it's a different one, specifically for SitePublisher / LiveSite ??

shougom

I did a search for all toolkits.xml on our server and there is only one and lives under d:\iwhome

Y drive is a logical drive not a physical one and also we DO NOT have livesite or sitepublisher so it probably wont make any difference.

shougom

Ok so I went through all the steps in the read me and when I startup content center it still says build 70040 vs 70090 when I click on about. But if I look at all the files that are in the changed section in the readme. Those particular files all have new dates. eg.
-------------

/bin/iwabort

/bin/iwaccess

/bin/iwaccessmigrate

/bin/iwaddtaskfile

/bin/iwaddtaskgroup

/bin/iwaddtaskuser

/bin/iwancestor

/bin/iwat

The above all have new datestamps. But the content center doesnt reflect the new build number...hmm weird.

Sans titre.png