prointralink 3.4 e wildfire 4.0

[EmaLot]

Hello everyone, I have little experience in plm so I would need a hand.
what I have to do is install pro intralink 3.4 on a test machine and check that everything works well in perspective of a migration on windchill 10.
to do this I put on a virtual machine with windows 2000 servers sp4 (pro intralink has expressly requested win2000 as I know).
I installed and started the fileserver.
I installed oracle 9.2.0.1.0 then patched to 9.2.0.5.0
I installed the dataserver indicating the directory for the vault file.
I also installed the client with a license on the same machine.
I updated fileserver, dataserver and client with the service pack 3.4 m040

at this point it seemed all set up and I also installed wildfire 4.0 c000 (which is a version preproduction) specifying the pro intralink client settings. Similarly I remade the client setup and entered the wildfire settings in the client.

At this point I successfully logged into the client, created a workspace and from the client I opened wildfire signaling the created workspace. At this point I open a wf assembly and try to save it. the problem is here: whether I make 'know' that if I impose the car check-in wf4 crashes and disappears without giving any message to video.

I know that on many points I have not included great details, but is there any possible error or omissions I could make?
If the problem was in preproduction wf4, can I somehow check-in without passing for wf4?

please help me

 

[Parametric_Ozzy]

All right, what you did at the level of steps, but...

with intralink 3.4 m040 wf4.0 is not supported!

the first version of the wf4 supported in intralink is first of all the m030 but you must also upgrade with intralink at least to m060.

ps: then no matter what you never put a preproduction of the client under a pdm.

I hope I've been clear.
greetings

 

[EmaLot]

you have very reasonable, in fact with wf4.0 m040 crashes have not occurred anymore. Thank you very much.

One thing I still miss: Now from wf I can save assemblies and parts in the workspace, but if I synchronize with the commonspace then in fact nothing happens that in the commonspace there is no trace of the saved objects. have I forgotten (or more likely ignored) something?

 

[Parametric_Ozzy]

you have very reasonable, in fact with wf4.0 m040 crashes have not occurred anymore. Thank you very much.

One thing I still miss: Now from wf I can save assemblies and parts in the workspace, but if I synchronize with the commonspace then in fact nothing happens that in the commonspace there is no trace of the saved objects. have I forgotten (or more likely ignored) something?

mmm hard to say so... Anyway you updated how I even wrote intralink at least to m060?

 

[EmaLot]

mmm hard to say so... Anyway you updated how I even wrote intralink at least to m060?

Unfortunately at the moment I do not have patch m060... so the behavior I described is abnormal? normally after synchronization should I find data saved in the cs?

 

[Parametric_Ozzy]

Unfortunately at the moment I do not have patch m060... so the behavior I described is abnormal? normally after synchronization should I find data saved in the cs?

In theory yes, it is not enough to change the proe client, the compatibility matrix only works with the m060 up, so if you do not want to have problems that is the first thing you have to do.

 

[EmaLot]

All right, I think it was just my ignorance... I'm writing for someone who's going through here looking for the same thing: to save objects in the commonspace simply open the ws, select objects, click on the right button and select 'check-in'.
What super obvious, who knows what to look for... :