Strange Intralink 9.1 issue

[bmills]

Hi everyone,

I have a strange problem that has popped up on a remote user. The user is running Intralink 9.1 M050 and WF4 M180 at a remote site that has a fileserver. His products are mastered on this server and there is a global library that is replicated to that site daily. When he starts Pro/E, checks out some files, and attempts to open on of the objects he gets a File Download dialog (see attachment) asking if he wants to open or saveobjectname.pha. If he clicks open the Pro/E object opens but any changes made and then saved seem take place but the Workspace does not record the object as Modified. Subsequently no check in can be done as Intralink does not recognize the object modification. I completely removed his workspace (removed .wf folder) and even had him try a different computer....no luck. Has anyone seen this issue.

Bob Mills

[IgorVarshavsky]

Hi Bob,

I guess that the user used for Intralink 3.x workflow that is different from Windchill.
It looks like the user first starts IE, logs into Windchill, checks out the file into the Server Side workspace and then uses the button to open in Pro/e.

The correct workflow is

1) Never start a stand-alone web browser

2) Start Pro/e

3) Use Server Manager to connect to Windchill and select a workspace

4) Using embedded browser do add to workspace or Open in Pro/e, modify and save to the workspace.
This will ensure that the file is downloaded to the proper workspace and then all modifications are saved into it, etc.

Best regards,
[cid:image003.jpg@01CD16FE.50C73830]

Igor Varshavsky
Senior Application Specialist

[bmills]

Designation: Non-Finmeccanica

Hi all,

We have found the solution to our "strange issue". Since we seemed to
stump everyone on this list (I didn't think that possible) I wanted to
let everyone know of a potential problem. With some help from PTC tech
support we were able to identify that the IE browsers "user agent
string" was corrupted. After some investigative work by one of our IT
gurus we identified the source of the "corrupted" string, Symantec
Endpoint Protection! At the location that was experiencing the problem
SEP version 12 had been pushed out and there is a setting called
"Enable stealth mode web browsing" that was enabled. This causes SEP to
modify the IE user agent string to a bogus value. Windchill does not
like this!



Beware of anti-virus updates.



Bob Mills

Engineering Software Administrator

Training and Control Systems, LLC

DRS Technologies, Inc

645 Anchors Street

Fort Walton Beach, Florida 32548

850-302-3241

bmills@drs-ds.com <">mailto:rmills@drs-ds.com> www.drs.com

[cjohnstone]

Bob -

We may be seeing a similar issue here related to the Symantec update except that the user's machine locks up and reboots. Was your issue fixed by disabling the 'stealth mode web browsing' option?

Thanks in advance -

Chrystal Johnstone

Red Dot Corporation