Pro/E History file?

[bbailey]

Hello Admins,

I am wrestling with an issue I've never seen before. We are getting ready
to roll out Pro/INTRALINK 3.4 (M030) clients on Windows XP SP2. The
existing Pro/E installs (WF 2.0 M200), currently running with
Pro/INTRALINK 3.3 (M021) clients, will be used. Only the proe1.bat and
proe1.psf files will be updated to point to the new ILINK client. We use
WinInstall to deliver the clients. A script uninstalls the 3.3 client and
installs the 3.4 client, plus updates the necessary files in the Pro/E
load. It also renames the folder holding the .proi dir. Processes
nmsd.exe, pro_comm_msg.exe and xtop.exe are killed, if running.

Worked great on the test machine. However a broader test showed up a
problem. All seems to go well, however, when one invokes Pro/E for the
bound to a 3.4 Workspace it hangs for a very long time, then returns a
dialog with the following error: Pro/INTRALINK launch command
"C:\ptc\intralink\proiclient\bin\proilink3.4.bat failed. The std.out has
the following:

Could not start IPC server: The Workspace file
C:\ProeData\ilink_ws\.proi\Local.ddb cannot be created. This may be
caused by trying to
overwrite an existing file, operating system file protection violations,
or lack of available disk space.
Error Stack:
Error 0:
Message: The Workspace file C:\ProeData\ilink_ws\.proi\Local.ddb cannot be
created. This may be caused by trying to
overwrite an existing file, operating system file protection violations,
or lack of available disk space.
Arguments:
0: C:\ProeData\ilink_ws\.proi\Local.ddb
1:

Now for the strangest part, all one has to do is kill the hung Pro client
and completely exit ILINK 3.4. After that all works as per spec.

Does Pro/E write some sort of history file that retains links to 3.3? Must
I search this down and remove it?

Thanks,

Ben

This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

[bbailey]

Hello Admins,

Turns out I'd found a "solution" within 30 minutes of my exploder query.
Rather than dealing with renaming the .proi folder itself, I was simply
renaming the folder directly above it. I figured that ILINK 3.4 would
create the necessary folder, which it did. However, if Pro/E was called
up on the first invocation of ILINK 3.4, the hanging behavior resulted.

Now, I make sure the full folder path for .proi exists, and things work
much better.

I have had one reply indicating that there is a history file written at:
C:\Documents and Settings\<user_id>\Application
Data\PTC\ProENGINEER\Wildfire\.wf\.Settings . I plan to test if that
affects app behavior at all.

Thanks,

Ben