TeamSite 6.1 Upgrade WOES!

Well, we got our backup issues resolved. Got upgraded to Win2K SP4 today. TeamSite 6.0L was previously installed.

Shutdown all of the Interwoven Services (including OpenDeploy) and set them all to manual.
Rebooted
Checked that no RMIRegistry processes were running
Started Install

Install looked like it ran great. No errors reported.
Rebooted after Install.

Tried to hit the TeamSite server with browser. Nothin'. Checked for Y:... It's there.
Checked services... WHAT THE.... Missing Interwoven Web Daemon and Interwoven GRC DB. Where the heck did they go?!?! I want them back!!!

Anyone experience similar problems? I can add the Web Daemon manually, that's easy. Don't know what to do about the other one.

Any help would be appreciated (please don't say "File a support case." I'm already on it.)

- Jason

Find more posts tagged with

Comments

> please don't say "File a support case."

RTFM?

Just kidding - I know the manuals don't help.

Ha Ha.... HUGE HELP! Solved Everything... NOT! :-)

Ok... I played around some... Started the web service on the command line (can't get it to start in the services). Was able to bring up the login screen. Has no options in the "Content Center" drop down. Makes me think I need to rebuild the web apps. Anyone agree/disagree?

Was able to login, but no UI... I get the word "Base" instead of a UI. Although very simple to understand (don't think they'd need a manual to realize they have no functionality), not helpful for my users.

Anyone else seen any problems even remotely like this or am I alone in the woods?

- Jason

No I meant rebuild the fine machine.

Luckily, I've been told that we have a good backup from Tuesday. Don't need to worry about rebuilding.

Next thing you're going to tell me is it's because I didn't have my lucky rabbit's foot.

Side Note:
Remember the good ol' days when Interwoven installers would help you prevent **** up your server by making sure that services were shutdown and that RMIRegistry isn't running (if it's not supposed to be) and that you must reboot when you really have to reboot? I miss those days. Of course now upgrading is a lot more exciting.... Do I get to spend the next 2 to 3 days rebuilding my server???? Roll the dice. Even when you follow step by step with the manual, it still seems to be a roll of the dice... That's why I LOVE my job!

- Jason

I've seen this before. My recollection is that it can be caused by:
- bad iw_which_ui or session cookie - try deleting your cookies
- bad UI preference in EDB - try deleting EDB
- bad webapp munge - rebuild webapps

Todd

Dev. Mgr., CCS and UITK

Jason,

One other question. Did you make any customizations to the UITK XML files before applying TS 6.1? This problem could also arise when XML files are not well formed.

Thanks,
David Yun

Sr. Product Manager, TeamSIte
dyun@interwoven.com

I did make a couple of customizations to the UITK. Just added a couple of custom menu items. They were working fine in 6.0L.

- Jason

Ok. Assuming that there was something wrong with the UITK, which I don't think there was, what do I need to do to correct the problems?

- Jason

Hi Jason,

It doesn't sound like the UITK is the issue since the menus worked in TS 6.0L. I'd try out the steps that Todd Rein outlined in his other post:

I've seen this before. My recollection is that it can be caused by:
* bad iw_which_ui or session cookie - try deleting your cookies
* bad UI preference in EDB - try deleting EDB
* bad webapp munge - rebuild webapps

Hope that one of these works for you,
David Yun

Sr. Product Manager, TeamSIte
dyun@interwoven.com

Ok. I got the iwwebd to work as a service.

Rebuilt webapps, no luck (but was pretty quick).

Hate to sound ignorant, but please define EDB.

Thanks,

Jason

Ok. Guess that EDB means entity database, I rebuilt that. Not sure what that was supposed to solve. It is not a problem with one user on one system, it's all users on all systems. The UI that seems to come up is Base and I have no selection on the login screen.

Any further help would be appreciated,

Jason

Just thought of something... Would it be bad if the iw.cfg and some of the custom UI stuff was Read Only when I did the upgrade? I'm going to assume that the answer is yes.

Might want to be aware of this in the future.

- Jason

If readonly is a problem the installer (and all patchers) should check, unset and restore these attributes - a lot of shops make config and custom code files readonly as a reminder to edit, version and install from a branch rather than changing the live files directly.

John,

I completely agree. But it's just about the only customization that I can think of that may have caused this problem. I've been told by support that the experience I'm seeing is exactly the same as what happens when you try to run 6.0x on Windows 2000 SP4. Strange.

- Jason

According to Engineering, UI config and iw.cfg files being read-only will not cause any problems with the installer.

- Jason

With the help of DevNet and Support, this problem was resolved. It turned out that there were some tags in the application_custom.xml that shouldn't have been there. <iwov_ui> tags. Not sure where they came from or how they got there but once they were removed from both places (local/config and httpd/webapps) then the webapps were reinstalled, everything worked. Since the UI customizations worked in 6.0L, I'm really stumped as to how these stray tags suddenly showed up.

I've put in a feature request for better XML checking by install_webapps.ipl so that there's more information about where the problem lies.

Dave's instincts were right on. I should have checked the UI customizations right after you suggested it.

- Jason

I ran into similar problems when I tried a 6.0L installation a while back ago.

My issues were:

Proxy Didn't Start
Resolution
Run iwsessionkeygen from the command line

Web Daemon fails to install
Resolution
- Open regedit and find key "iwwebd" under HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\
- Delete this key
- Run from c:\iw-home\install the command "iwperl install_iwwebd.ipl"
- Goto services panel and rename to "Interwoven Web Daemon" and start this service

Just thought I'd list this tips in case any of you ran into these problems.

I'm really glad you posted this. I ran into a somewhat similar issue yesterday on a 6.1 TS box. I had to make some minor custom menu changes and as usual rebuild the webapps. When I logged into the UI, it threw an an error stating 'Unable to find link fs_navigate_to_parent'. I removed my changes and put back the original files and that didn't help. I remembered reading your devnet post and saw that my application_custom.xml also had <iwov_ui> tags.

We had backups of httpd and content_center prior to the 6.1 install and the application_custom.xml file there also had the <iwov_ui> tags. So my guess is that these are not stray tags. With the 6.1 install, I noticed a new directory customer_src_new with the usual .xml files present under etc\conf\customer. I replaced the application_custom.xml file from there to the customer_src folder. The application_custom.xml file did not have <iwov_ui> tags as in the 6.0L version but had an <applications> tag. I rebuilt the webapps with the modified application_custom.xml file and it worked.

Edited by cemman01 on 04/27/04 05:43 AM (server time).

Another issue I ran into when upgraded from 6.0L to 6.1:

Web application wouldn't compile because of improper toolkits.xml config
Resolution
The file \iw-home\local\config\lib\content_center\toolkits.xml still had the old customer source referenced like so:
<toolkit id="customer" path="c:\iw-home/local/config/lib/content_center/customer/"/> (I think that was it)

So after putting debug statements in the compile script I found out that the toolkit was wrong. I had to change this line to the following:
<toolkit id="customer" path="c:\iw-home/local/config/lib/content_center/customer_out/customer.tk.war"/>

I'm not sure if this was an installation issue or having it read-only made a difference. But after changing it the web app compiled.

To anyone who's yet to upgrade from 6.0* to 6.1--

Please please (please!) read pages 105-106 of the 6.1 UI Customization Guide (the section entitled "Migrating 6.0 or 6.0L Customizations"). It will save you lots of time and heartache!

Michelle Neuringer
Interwoven Engineer

I also had this issue with both installs of TeamSite 6.1. Luckily it told me exactly what was wrong when I tried to rebuild the webapps.

Just wanted to post that I've completed our production upgrade to 6.1 which went MUCH smoother than the DEV installation. I contribute a lot of that to lessons learned from the DEV install. The only issues I had with the production install were related to the strange tags in the application_custom.xml and the issue with the misconfigured toolkits.xml.

- Jason