ingallspw
Mechanical
- Mar 17, 2009
- 178
We are running NX 7.5 & TC8.3 on a 4-tier client.
We run simulations (in native mode) quite often. Soon we will be storing those simulations in TeamCenter. These simulations run well over night and some actually take days.
I am one of those infidels who rarely logs out at night... GASP! Almost every morning when I return, I receive the following error:
Unable to access the Teamcenter server - please restart NX to reconnect.
TeamCenter is still running and accessible but it was assigned a new host. I cannot see where the server restarted a service, SOA manager seems stable, nor do I see it is hiccuping in any way... I've asked (rhymes with C-Jack but to remain nameless to protect the innocent) and they tell me to restart NX or log out before I leave. The all wise internet returns no results to help either. What is causing this? Is there a way to reconnect NX to TeamCenter without restarting NX?
It may be some internal network issue as our TC DB server is not local. We've noticed before where our ping times get stupid high and I think that doesn't help it. Is there a way to at least tell TC or NX to wait a lot longer before assigning a new host? (What exactly is it doing when it says that anyway?)
To me its annoying. I've only lost work twice because of it because I save often... with simulation this error is going to be a show stopper for TC.
We know this shouldn't happen and it seems like a rare issue so any help would be greatly appreciated!
Thanks!
We run simulations (in native mode) quite often. Soon we will be storing those simulations in TeamCenter. These simulations run well over night and some actually take days.
I am one of those infidels who rarely logs out at night... GASP! Almost every morning when I return, I receive the following error:
Unable to access the Teamcenter server - please restart NX to reconnect.
TeamCenter is still running and accessible but it was assigned a new host. I cannot see where the server restarted a service, SOA manager seems stable, nor do I see it is hiccuping in any way... I've asked (rhymes with C-Jack but to remain nameless to protect the innocent) and they tell me to restart NX or log out before I leave. The all wise internet returns no results to help either. What is causing this? Is there a way to reconnect NX to TeamCenter without restarting NX?
It may be some internal network issue as our TC DB server is not local. We've noticed before where our ping times get stupid high and I think that doesn't help it. Is there a way to at least tell TC or NX to wait a lot longer before assigning a new host? (What exactly is it doing when it says that anyway?)
To me its annoying. I've only lost work twice because of it because I save often... with simulation this error is going to be a show stopper for TC.
We know this shouldn't happen and it seems like a rare issue so any help would be greatly appreciated!
Thanks!