Issue in upgrade from 7.4.1 to 8.1.0

shashwata

I am upgrading from TeamSite 7.4.1 to 8.1.0. It is always getting stuck at 48% for more than a hour. We didn't face any issues on Test environment. This was our production server. So, had to roll back to VM snapshot quickly and couldn't save any other log. I have already raised support case but yet to get anything definitive. Any poitners would be helpful. This is the portion where it got stuck 4 times.

 

2016-07-05 13:57:37,071 DEBUG com.interwoven.wcm.install.framework.InstallDocumentManager - InitializeUpgradeEnv completed
2016-07-05 13:57:37,071 INFO  com.interwoven.wcm.install.framework.DocumentCompositeTask - Executing: IWPerlMunge
2016-07-05 13:57:37,086 DEBUG com.interwoven.serverutils100.TProcessRunner - TProcessRunner:
2016-07-05 13:57:37,086 DEBUG com.interwoven.serverutils100.TProcessRunner - About to execute:
2016-07-05 13:57:37,086 DEBUG com.interwoven.serverutils100.TProcessRunner - C:\Interwoven\TeamSite\iw-perl\bin\iwperl.exe C:\Interwoven\TeamSite\install\iwperlmunge.ipl -verbose C:\Interwoven\TeamSite
2016-07-05 13:57:50,211 DEBUG com.interwoven.wcm.teamsite.install.tasks.perl.IWPerlMunge - estimated duration=26, progress=0, increment=14
2016-07-05 13:58:15,586 DEBUG com.interwoven.wcm.teamsite.install.tasks.perl.IWPerlMunge - estimated duration=26, progress=14, increment=3
2016-07-05 13:58:53,273 DEBUG com.interwoven.wcm.teamsite.install.tasks.perl.IWPerlMunge - estimated duration=26, progress=17, increment=3
2016-07-05 13:59:46,679 DEBUG com.interwoven.wcm.teamsite.install.tasks.perl.IWPerlMunge - estimated duration=26, progress=20, increment=3
2016-07-05 13:59:50,039 DEBUG com.interwoven.wcm.teamsite.install.tasks.perl.IWPerlMunge - estimated duration=26, progress=23, increment=3
2016-07-05 13:59:50,492 DEBUG com.interwoven.wcm.teamsite.install.tasks.perl.IWPerlMunge - estimated duration=26, progress=26, increment=3

 

Thank you.

nipper

Not a lot of options here. 

 

Hope support gets back to you.

 

But if  you want to debug yourself, this process goes through all the text files and uses regex to put proper values in there. No clue where it is at that point, but you may be able to run the process by hand and add some debug statements to the process and see where the issue occurs. 

 

Likely there is a file that is open by somehting else or for some other reason cannot be written to.  You need to figure out what that file is.