Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X
FYI,
The corruption issues are not fixed with this latest build. We have been using M060 with patches (that are now included in M061) for several weeks and continue to have corruption issues. PTC has provided us with additional patches last week to correct our problem. However, after installing these patches Friday we have already had a corruption. This is derailing our effort to roll out WF4, very disappointing.
WF2 M280, 3.4 M061+patches
FYI:
Our experience so far after rolling out Ilink 3.4 M060 back last Thanksgiving is that we have only had one or two instances of workspace corruption, other than myself. I've blown mine up 3 times since the start of the year: one time, just a single workspace was corrupt (and I was able to delete and start over), the others, all the workspaces were corrupt where I hade to renbame the .proi folder & create a new one.. (The corrupt workspaces were inaccessible & cause Intralink to crash.). It's kind of fortunate that the admin (me) is seeing the worst of it and not the users.. Fewer hassles 🙂
I have installed M061 and had one "corruption event", but I was using a .proi created by M060, which is advised against in the documentation. Since I've used anM061 created .proi, I've been OK (touch wood..). Hopefully I'll continue to run OK..
All our other users are still on M060 as I'm still testing M061, and with 40+ users we've not had much trouble..
We are now using WF4 M050 & M060 with Intralink 3.4 across the board..
Andrew Mansfield
KI, Green Bay, WI
I've had all mine with WF3 but nearly all our other users are now on WF4 with little trouble.
Our Intralink 3.4 m060 lifeline...
1. Updated from 3.4 M050 to M060. Started having corrupted Local.ddb files (using WF3 M180)
2. Updated from WF3 M180 to WF4 M061 and continued to experience corrupted Local.ddb files.
3. Rec'd interim Ilink 3.4 M060+ patch from PTC to help with corruption issue. Continued to have corrupted Local.ddb files.
4. Updated from Ilink 3.4 M060 to M061 and are continuing to experience corrupted Local.ddb files.
5. Rec'd another patch (Ilink 3.4 M061+) from PTC on Friday 02/27/2009. So far I have only installed this on 2 of my clients today. I won't know for a couple of days if this patch actually fixes anything or not.
So from my experiences you can say that:
a. the Local.ddb corruption happens on either WF3 or WF4
b. the Local.ddb corruption is not fixed in Ilink 3.4 M061
c. If you have made the upgrade to 3.4 M060/M061 then you just as well update to WF4 because that was your only reason to upgrade to 3.4 M060. Right???
d. Backup the users Local.ddb file every 15 minutes or 1/2 hour during working hrs.
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
PO Box 245
108 W 2nd
Assaria, KS USA 67416
email: -
Phone: 785-667-7763 x3440
Fax: 785-667-2695
------------------------------------------------------------------------
We are on WF4 M060 with Ilink 34 M060and have had workspace corruptions. I have a couple of people upgraded to the Ilink34 M061 client and they too have had corruptions. one just a few minutes ago. I had them start out with fresh .proi's.
I was wondering how PTC could you produce a fix for a problem they didn't fully understand, and now I have my answer.
Is this a good reason tomigrate to Windchill Intralink? I hope not.
Joe
Our Intralink 3.4 m060 lifeline...
1. Updated from 3.4 M050 to M060. Started having corrupted Local.ddb files (using WF3 M180)
2. Updated from WF3 M180 to WF4 M061 and continued to experience corrupted Local.ddb files.
3. Rec'd interim Ilink 3.4 M060+ patch from PTC to help with corruption issue. Continued to have corrupted Local.ddb files.
4. Updated from Ilink 3.4 M060 to M061 and are continuing to experience corrupted Local.ddb files.
5. Rec'd another patch (Ilink 3.4 M061+) from PTC on Friday 02/27/2009. So far I have only installed this on 2 of my clients today. I won't know for a couple of days if this patch actually fixes anything or not.
So from my experiences you can say that:
a. the Local.ddb corruption happens on either WF3 or WF4
b. the Local.ddb corruption is not fixed in Ilink 3.4 M061
c. If you have made the upgrade to 3.4 M060/M061 then you just as well update to WF4 because that was your only reason to upgrade to 3.4 M060. Right???
d. Backup the users Local.ddb file every 15 minutes or 1/2 hour during working hrs.
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
PO Box 245
108 W 2nd
Assaria, KS USA 67416
email: -
Phone: 785-667-7763 x3440
Fax: 785-667-2695
------------------------------------------------------------------------
What procedure or mechanism is used to backup the local.ddb file.
User invoked, Script, ScheduledTask, or command?
Joe
In Reply to Randy Jones:
Our Intralink 3.4 m060 lifeline...
1. Updated from 3.4 M050 to M060. Started having corrupted Local.ddb files (using WF3 M180)
2. Updated from WF3 M180 to WF4 M061 and continued to experience corrupted Local.ddb files.
3. Rec'd interim Ilink 3.4 M060+ patch from PTC to help with corruption issue. Continued to have corrupted Local.ddb files.
4. Updated from Ilink 3.4 M060 to M061 and are continuing to experience corrupted Local.ddb files.
5. Rec'd another patch (Ilink 3.4 M061+) from PTC on Friday 02/27/2009. So far I have only installed this on 2 of my clients today. I won't know for a couple of days if this patch actually fixes anything or not.
So from my experiences you can say that:
a. the Local.ddb corruption happens on either WF3 or WF4
b. the Local.ddb corruption is not fixed in Ilink 3.4 M061
c. If you have made the upgrade to 3.4 M060/M061 then you just as well update to WF4 because that was your only reason to upgrade to 3.4 M060. Right???
d. Backup the users Local.ddb file every 15 minutes or 1/2 hour during working hrs.
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
PO Box 245
108 W 2nd
Assaria, KS USA 67416
email: -
Phone: 785-667-7763 x3440
Fax: 785-667-2695
------------------------------------------------------------------------
In Reply to Richard Borders:
What type of hardware and what OS is being used
Sun hardware (variety of Blade 1000, Blade 2000, Blade 2500, and Ultra 45) running Solaris 10u6 (sparc)
In Reply to Randy Jones:Our Intralink 3.4 m060 lifeline...
1. Updated from 3.4 M050 to M060. Started having corrupted Local.ddb files (using WF3 M180)
2. Updated from WF3 M180 to WF4 M061 and continued to experience corrupted Local.ddb files.
3. Rec'd interim Ilink 3.4 M060+ patch from PTC to help with corruption issue. Continued to have corrupted Local.ddb files.
4. Updated from Ilink 3.4 M060 to M061 and are continuing to experience corrupted Local.ddb files.
5. Rec'd another patch (Ilink 3.4 M061+) from PTC on Friday 02/27/2009. So far I have only installed this on 2 of my clients today. I won't know for a couple of days if this patch actually fixes anything or not.
So from my experiences you can say that:
a. the Local.ddb corruption happens on either WF3 or WF4
b. the Local.ddb corruption is not fixed in Ilink 3.4 M061
c. If you have made the upgrade to 3.4 M060/M061 then you just as well update to WF4 because that was your only reason to upgrade to 3.4 M060. Right???
d. Backup the users Local.ddb file every 15 minutes or 1/2 hour during working hrs.
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
PO Box 245
108 W 2nd
Assaria, KS USA 67416
email: -
Phone: 785-667-7763 x3440
Fax: 785-667-2695
What procedure or mechanism is used to backup the local.ddb file.
User invoked, Script, ScheduledTask, or command?
I wrote a sh script that performs the backup. I then add a line in each users crontab file that runs this script every 1/2 hr from 6:00am to 4:30pm (their normal working hours). 1 hr to write and debug the sh script and then 5 minutes to add it to all (30+) users crontab files.
Joe
In Reply to Randy Jones:Our Intralink 3.4 m060 lifeline...
1. Updated from 3.4 M050 to M060. Started having corrupted Local.ddb files (using WF3 M180)
2. Updated from WF3 M180 to WF4 M061 and continued to experience corrupted Local.ddb files.
3. Rec'd interim Ilink 3.4 M060+ patch from PTC to help with corruption issue. Continued to have corrupted Local.ddb files.
4. Updated from Ilink 3.4 M060 to M061 and are continuing to experience corrupted Local.ddb files.
5. Rec'd another patch (Ilink 3.4 M061+) from PTC on Friday 02/27/2009. So far I have only installed this on 2 of my clients today. I won't know for a couple of days if this patch actually fixes anything or not.
So from my experiences you can say that:
a. the Local.ddb corruption happens on either WF3 or WF4
b. the Local.ddb corruption is not fixed in Ilink 3.4 M061
c. If you have made the upgrade to 3.4 M060/M061 then you just as well update to WF4 because that was your only reason to upgrade to 3.4 M060. Right???
d. Backup the users Local.ddb file every 15 minutes or 1/2 hour during working hrs.
------------------------------------------------------------------------
Randy Jones
Systems Administrator
Great Plains Mfg., Inc.
PO Box 245
108 W 2nd
Assaria, KS USA 67416
email: -
Phone: 785-667-7763 x3440
Fax: 785-667-2695
I keep putting off upgrading from Intralink 3.4 M050 to M060/61 even though it is holding back rolling out WF4, we are currently on WF2 M280 because I am concerned about introducing this workspace corruption to our users by upgrading Intralink. If you were facing the option of waiting for this issue to be resolved or taking the plunge would you implement? We have a fair amount of demand here for WF4. I've got about 22 users and it's very hard to say if the risk that we might be among the more affected is enough to continue to hold back on upgrading.
Ian Bagnald
System Support Analyst Sr.
"Pro/Intralink 3.4 M070 Available for Extended Support Customers"
"Pro/INTRALINK 3.4 M070 is scheduled for availability in March 2009 for Extended Support customers..."
a) Now with the imminent release of M070 for "Extended Support Customers" only (sic), this begs the issue - will this solve the 3.4 workspace corruption issues PTC?
b) For the past several days I too have been testing 64-bit WF4 M70 with our Intralink 3.4 M040 system and to date have not encountered any show stoppers. (My company is under business pressures to move to WF4 ASAP.)
So do I go all in with the company's CAD data by:
1) Rolling out WF4 and Intralink 3.4 M061?
2) Rolling out WF4 and keeping Intralink 3.4 M040?
3) Paying the $$$ and rolling out WF4 and Intralink 3.4 M070?
4) Wait and see if their is a M062?
I do not like CAD gambling....
~John F.
Just happened to be looking at the update adviser to see what was fixed in WF4.0 M080.
TAN 143517 was kind of interesting
https://www.ptc.com/appserver/cs/view/solution.jsp?n=143517
<u>Module</u>
Pro/E - Pro/I Interaction
<u>Title</u>
Pro/INTRALINK 3.4 M060 Workspace Data May Become Corrupt After Launching Pro/ENGINEER With A Linked Session.
Looks like WF4 M080 andProI3.4 M062may be the solutions to the corruption problems, Hopefully.
Joe