Error when Launching Creo View in windchill 11.1

[TF_11302689]

Hello All, 

I Have this message "Error Occurred communicating with Windchill ..." when I try to launch creo View in windchill 11.1 (M020) . I follow the CS415933 (https://www.ptc.com/en/support/article/CS415933)for using the TLS V1.2 in apache Config but it still doesn't work. 

Have you an idea ? 

thanks a lot

[avillanueva]

Is this a new problem or something that started after you switched to HTTPS?

[TF_11302689]

Hi, 

No I don't switch to https recently and it works before. I don't know since how many time, users are not always on creo view. 

But on our information system, people from network and security have made some change recently (new firewall restriction, new antivirus policies, new proxy rule,etc..) I think problem is here but where...

[rleir]

That article is for installations using SSO (Single Sign On).  Most installations don't use that. Do you use SSO with Windchill?

Your error message could be something to do with connections to the Publishing server (another server dedicated to Windchill Visualization).

As A.V. suggests, what has changed recently? Or have you always seen this error?

[TF_11302689]

Hi, error is new for sure, I used creo view I don't remember when. as I said before I think trouble is on our information system who have new restriction . On Windows 10 PC nobody has the trouble?  (It not the first time a KB do the sh***) 🙂

[vdegaonkar]

What is the version of Creo View are you using? I would recommend try validating it with Creo View 11.0 as there are improvement in regards with SSO authentication as well if your organization restrict IE usage then it can lead to failure in communication between Windchill & Creo View. New improvement in Creo View 11.0 uses MS Edge for authentication purpose. 

Refer Switch to Microsoft Edge for Authenticating with Windchill (ptc.com) 

NOTE: Creo View 11.0 and later is no more supporting Windchill version prior to 12.0.2.0 any more.  

[TF_11302689]

Hi, 

I Using CreoView 5.1

[TF_11302689 · Accepted solution]

I Find The solution with IT: CRL file was expired on our system.