Loading Intralink 3.4 on server 2003

[pperry]

I know I did this about three years ago and I ran into trouble, but that is when we had support on Intralink. I have tried running the disk and the process seems to stop at creating the database or synchronizing the table names. The error in the instal_ilink.log files seems to indicate that it cannot find a log name.I am not sure what log it is trying to find. I have tried doing it manually and still no avail.I currently have 7 log files from all the times I tried to laod the software. I have actually created a database using the install_ilink DATABASE ilnk SMALL c:\ptc\dataserver\intralink\dbs. Then I could not get past the Schema and I deleted everything. I am trying to use RDP to load this as the computer is in another city.

I am trying to create this server for two reasons. One is to create a backup server of our current production server to test some activities. Once I get the activities out of the way I wouls like to use this server as a migration server for preparation of moving this database to Windchill.

Any helkp will be greatly apprciated.

Patrick Perry

Lead Technical Support Analyst, ETS

T 713-867-1774 | C 281-814-8364 | -

BAE Systems, 5000 I-10 West Sealy, Texas USA 77474

www.baesystems.com

[RaySchussler]

Patrick;
Just a thought, but are you using exactly the same folder structure and install path for the test server as production?
I couldn't believe this either, but Intralink is quirky sometimes:

Here's a quick way to make an exact clone:

The applied technique we will use for our tesing is as follows, other techniques will be listed futher below.

Mass deployment specialist Jean-Louis from CAE found this method through a service call to PTC;

The technique that was provided by PTC is to replace the dbs folder in the dataserver. It goes as follows:

a.. Install the test Pro/Intralink dataserver under the same path as the production one.
b.. Shutdown the dataserver (dbshut_ilink).
c.. Replace the dataserver/intralink/dbs folder contents by the files from the production dataserver.
d.. Re-start the dataserver (dbstart_ilink).
Note that at this time the test dataserver points to the production fileserver and vaults. YOU CAN SCREW UP your production data if you don't fix this.


I remember going through a new install, and production was "Large", but for some reason the install couldn't make a "Large" database as a new install. I had to install it and create as "Small" and then resize it before importing the database dump.

It's been a while since I wrestled with Intralink, and the error messages are really bad...you have my sympathies.

Good luck;
Ray


Ray Schussler
Manager Engineering Systems
ITT Corp - Industrial Process
Seneca Falls, NY
315-568-7287

[JimAugeri]

Server 2003 should be OK, as is the RD access to the remote machine. (I have done this at least twice; I am in New Mexico and two my Pro/I servers (all 3.4) are in Delaware.)

What you don't mention is anything about a couple of obscure setup details.

The account installing the INTRALINK components must be a LOCAL account (NOT a Domain Acct) in the LOCAL administrators group on the machine. If you aren't following this (deeply buried) rule in the installation materials, your install is doomed to fail. That same account must also be part of the (local) group "ora_dba" (I think that is what it is named), but if you meet the requirements stated earlier, then the installer will take care of this for you.

There are a couple of other reasons these Pro/I installs can fail, but I would have to dig back deep into my now ancient notes to (re) discover what those were.

By the way, I have taken to using those "manual setup commands" as a matter of course when doing these.

Good luck.


--Jim Augeri
MCAD Tool Support - PLM EQT (NM75)
Honeywell Aerospace
9201 San Mateo Blvd. (MS B-3)
Albuquerque, NM 87113
Phone - 505.828.5808
Fax - 505.828.5500

"Never again will one generation of veterans abandon another."
Founding Principle of Vietnam Veterans of America

This e-mail message and any attachments are for the use of the intended recipient(s) and may be controlled by U.S. export control laws. Any unauthorized review, use, disclosure or distribution of this communication in whole or in part without the express written consent of Honeywell, or the U.S. Government as required, is prohibited. If you are not the intended recipient(s), please contact the sender by reply e-mail and destroy the original message and any copies of the message as well as any attachment(s) to the original message.