Skip to main content
J
JOES1-Visitor
1-Visitor
January 9, 2012
Question

.proi.log.999

  • January 9, 2012
  • 3 replies
  • 1090 views

The log files that Intralink creates in the startup folder, in our case c:/PRO, everytime you start Intralink & the amount of files can go as high as 999. At that point I discovered Intralink3.4 will not start! No error messages, nothing, just doesn't start.


It took a bit (most of the morning) to figure it out, but all I had to do was delete all the log files & all is well.I thought I would post this for an FYI (although everyone likely knows thisbut me). I told my IT department that opening Ilink 999 times entitles me to a new workstation.


Regards,


Joe S.


3 replies

L
lylebeidler1-Visitor
1-Visitor
January 9, 2012
I require our users to, every December, do the following steps:

1) Check in all work to Commonspace

2) Delete all Workspaces & exit intralink.

3) Delete Local.ddb

4) Delete all trail.txt.# files

5) Delete all proi.log.# files



This helps prevent corrupt workspaces & some of these other issues.



Good luck with getting a new workstation.



--



Lyle Beidler
MGS Inc
178 Muddy Creek Church Rd
Denver PA 17517
717-336-7528
Fax 717-336-0514
<">mailto:-> -
<">http://www.mgsincorporated.com>
D
DanielReid12-Amethyst
12-Amethyst
January 11, 2012
I discovered a similar problem with log files for ProductView publisher
workers connected to Windchill. I suspect it applies to a variety of
PTC applications that generate versioned files. The PV worker happened
to produce files very quickly and I hadn't set up an automated clearing
process at the time.



As Lyle suggests, we clear local WS files and database, though frequency
depends on the use. For some users, it had to be monthly or risk
corruption or a local.ddb that reached the 2GB limit.


M
mbrockman10-Marble
10-Marble
January 12, 2012

we added the purge command at beginning of the intralink startup bat file which cleans up the working directory on launch


@echo off
call purge_dir.bat
cd trail
call purge_dir.bat
cd ..


Here is the purge_dir.bat file


@echo off
C:\Ptc\proeWildfire64bit\x86e_win64\obj\purge.exe
del *.inf.*
del *.ger.*
del *.crc
del *.log
del *.bom
del *.dat
del *.err
del *.1st
del *.m_p
del *.tst
del *.crc.*
del *.log.*
del *.bom.*
del *.dat.*
del *.err.*
del *.lst.*
del *.m_p.*
del *.tst.*
del *.plt
del *.out
del *.pts.*


As well we set up a scheduled task of running the ldbcompactprogram everymorning.


Mark

Terms & ConditionsAccessibility statement