Issue with 3.4M062

[ptc-941814]

Hi All,



We have an issue with INTRALINK 3.4M062. I shall first brief on the
current setup we have with 3.4M040. The SYSPOOL fileserver is located at
"ABC". The vault for the SYSPOOL is configured to
\\XYZ\prointralink\intralink_data\vault
<file: \\xyz\prointralink\intralink_data\vault="> (XYZ is a storage
space and fileserver cannot be installed). The access for
\\XYZ\prointralink <file: \\xyz\prointralink="> is provided only for
the account GLOBAL\USER1. This account alone has complete rights. And
the INTRALINK fileserver service was allowed to run as GLOBAL\USER1. as
shown below. This worked without any issues with INTRALINK 3.4M040. But
when I install INTRALINK 3.4M062 and configure the fileserver similarly
I receive an error "Error loading preferences". Any ideas on this will
be greatly helpful.











Thanks,
Giridhar

Engineering Data Management Group,

HTS Bangalore,

Phone: 91-80-26588360, Extn: 48564

[ptc-113113]

there is an old bug with ilsysprefs.txt in the syspool folder, might have to delete the file and recreate it after install?

should be able to find the article in ptc.com

also hopefully your url for prointralink\intralink data\ has no spaces in the path, Pro/INTRALINK hates spaces since its big Daddy was Unix.

[ptc-113113]

Dan
You are correct.
The issue is ptc software often fails when it encounters a space in a path or filename (primarily due to its heritage as a unix app).

not blaming unix, but its always been a best practice to avoid spaces in pathnames in unix, and this practice has frequently been turned into a "requirement" by PTC software. If you search the PTC KB on this topic, you'll see what I mean.

[ptc-941814]

Hi All,



Thanks for your responses. I missed to mention that I already attempted
switching the ilsysprefs.txt. I removed the old ilsysprefs.txt from
SYSPOOL vault and copied the new ilsysprefs.txt from
<dataserverloadpoint_m062>\intralink\syspref\usascii\ilsysprefs.txt to
the SYSPOOL vault. I received the same error "Error loading
preferences". Further the vault path
\\XYZ\prointralink\intralink_data\vault
<file: \\xyz\prointralink\intralink_data\vault="> does not have space
it has underscore.



Thanks,
Giridhar

Engineering Data Management Group,

HTS Bangalore,