Server is currently unavailable, do you want to switch to offline mode?

[bradlawrence]

We launched Creo 3.0 M100 about 2 months ago, we have Windchill 10.1 M040. 

While in Creo3, we receive the below offline error quite often, happens almost every day and is very sporadic.   We can access Windchill Server no problem in a standalone browser.  PTC says it is our network, our network staff says it is a PTC issue. 

Just wondering if anyone has faced this issue.

[dschenken]

PTC is probably right. The connection between the client and the server is a chatty one and seems to have some time sensitive component, so any glitches or short interruptions will cause the connection to appear to fail. Recent experience was in a company where one area had no problems and another glitched often.

You'll need to get a network specialist to see the short term events that are causing the problem to know what needs to be done.

[BineshKumar1]

I would leave a HTTP monitor  running in a laptop with enough disk space - either fiddler or wireshark. So as soon as you notice this issue you can look at logs to identify the problem.

Below is a screenshot from fiddler while we were having a DNS issue.

by the way, Do you have PSM installed?

[bmüller]

Hi!

could you solve the issue?

We have the same problem on connection from Europe to China. MPLS so it should not be a great-firewall issue too. But latency is an issue.

br Bernhard

[NathanSchiermey]

After struggling through this issue for the last 5 months, completely replacing the switches, the wiring, going to new Nutanix server, running 10gb NIC card and still having the issue.  We found our Barracuda web traffic filter was in the way.  Our traffic to the SQL server was routed through the Barracuda.  All we had to do was go into the Baracuda Web-filter and add exceptions into the incoming and outgoing connection by IP, to bypass the SQL server.   literally a 5 minute fix that we struggled with for 5 months costing huge downtime.  We had 2 different support tickets with PTC & Cisco wireshark and other packet sniffers, and no one could figure it out.