Cancel
Showing results for 
Search instead for 
Did you mean: 

Re: Transient volume configuration with 2 pool managers

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
You've found the problem. You should not change the value of Transient_Volume_Installation_Location in tc_profilevars.bat as it should be set to %COMPUTERNAME%. That is why 04 is failing. When pool_b is started it is reading the value as 03 and then not able to find its own transient volume. You'll need to modify tc_profilevras.bat and restart your environment. Congrats!

The attached prefs.xml is for the whole site and not just the values listed from the text file. I didn't sift through them to find just the ones we wanted since the problem has already been identified. If you have further failures then we might relook at the prefs.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4

Re: Transient volume configuration with 2 pool managers

Solution Partner Pioneer Solution Partner Pioneer
Solution Partner Pioneer

Hi,ETIFFT!I have the same question and have you solved it?

Thanks in advance!

Re: Transient volume configuration with 2 pool managers

Solution Partner Phenom Solution Partner Phenom
Solution Partner Phenom
Yes, his problem was solved by changing the value of Transient_Volume_Installation_Location back to %COMPUTERNAME% in tc_profilevars.bat. He hard-coded the env var to a specific server name 03 so that it failed on 04. By changing the value back to %COMPUTERNAME% then it was able to resolve to 03 or 04 as required.

If you have the same question then how far did you make it through the debugging sequence? We can help if you provide your FMS Master, backup.xml for both servers, and the preference values.

Randy Ellsworth, Teamcenter Architect, Applied CAx, LLC
NX 11 | SW 2016 | Creo 4 | TcUA 11.4
Evaluating: AW 3.4