My Teamcenter Environment Manager installation is stuck in a recovery state.
When upgrading from NX8.5 to NX10, i'm told I need to have TeamCenter integration for NX installed as well. So i run tem.bat, click the checkbox for TeamCenter integration for NX and go to install it. Then it errored out. Now it won't let me change the directory or anything.
I close and restart tem, and it goes into a 'recovery mode' where it shows the folder where tem.bat is located, but it's grayed out, read-only. And it tries to continue where it left off and errors out again. I can't seem to do anything about it.
*An error has occurred during the operation. Review the problem description and suggested actions. If a failure requires some input, the fields will be displayed below. Click the following log file to some technical information which may be useful in troubleshooting the issue.
The tcexec task cannot find the TcDataComponent. Is an attribute missing?
Can i pass some variable to the tem.bat to reset the thing?
You cannot reset TEM using a variable but you can go back to a previous configuration.xml. You'll need to redo any changes you made between the old configuration.xml and the current one.
Rename configuration.xml to configuration.xml.bad
Rename a previous configuration<DATETIME>.xml to configuration.xml
Note DATETIME will look something like
Where the date time stamp is 06-28-2015 6:54 PM
Looked at another way
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4
Randy's suggestion is correct if you want to roll back TEM so it isn't in recovery mode the next time you run it.
If you want to try to determine where the problem is, in case you want to run TEM again in the future, you should look at the install_XXXXX_##########.log files in your $TC_ROOT/install folder (where "XXXX" is the configuration ID and "##########" is the timestamp per Randy's description of the configuration backup file's name).
The install log file will contain the error you saw and possibly some indication of where the problem is coming from, and maybe pointers to additional log files that will help you diagnose the problem.