SW 2006 to 2007 Migration issues...

[Phadreus]

Hi all, we recently made the switch over to SW 2007 SP3.0 I know, we're running a little late. B-( I used SW and a custom Batch Processor to open (migrate) all of my Library and Fastener files prior to our launch to insure best performance. Everything seemed to be fine, however I am noticing a decent number of my Library files that SW is no longer able to open and reports the files as "corrupt". I sent them on to my VAR, then on to SW for analysis. SW tells me there is nothing that can be done to fix the files. I never saw anything like this going from SW2004 to 05, then 05 to 06.

Has anyone else seen this anomaly and more importantly have any potential solutions?


M.B. Price CSWP

http://www.assembly-testww.com

Automated Assembly & Test Systems

 

[CorBlimeyLimey]

Use your backup copy of the files and just use the regular Conversion Wizard.

Umm ... you DO have backup copies don't you?


SW07-SP3.1
SW06-SP5.1

 

[Phadreus]

But of course I do. The reason I didn't use the Conversion Wizzard in the first place was the time it takes...it was entirely too slow to consider using on over 10K parts.

I'm really wondering if anyone has any idea of the root cause so I can avoid this problem in the future, that's all. (I know, the root cause was upgrading from 2006 to 2007)

M.B. Price CSWP

http://www.assembly-testww.com

Automated Assembly & Test Systems

 

[CorBlimeyLimey]

Can you not run the conversion overnight, or over several nights, or over the weekend? I have found the conversion to be relatively quick on a half-decent machine. I don't have actual numbers at hand, but several thousand files took just a few hours for me.


SW07-SP3.1
SW06-SP5.1

 

[Phadreus]

Well...it's a little more complicated than just running the utility overnight in my application...We are a corporation of five separate sites with over 100 SW users working multiple shifts, all sharing files which are synchronized using WAFS technology. I was forced to copy down small quantities of files to a local machine, migrate them, then send them back to the LFS. Doing this without causing conflicts with users working on designs was quite tedious, however went off without a hitch for the most part...The only real problem I saw was a single batch that became corrupt. I used the exact same process on the corrupt batch, there seems to be no reason for the issue that I can see. I found it surprising that SW couldn't repair the files nor offer any insight as to the cause of the problem.

I’ll simply have to recover from my backup and re-migrate those files and re-upload. Darn it! I guess I was most interested in if this was a known issue with a known sollution. Thanks for your input Cor!


M.B. Price CSWP

http://www.assembly-testww.com

Automated Assembly & Test Systems

 

[J-C]

Are you using a replication program to sync the files? If so...I bet that could be the source of the corruption. We had our replication software (Availl) corrupt alot of stuff on occasion......not too long ago, we basicaly had to total clear out the slave server's files...and re-replicate everything to clear up the problem. Basically no one had file access for a week.

Jason

UG NX2.02.2 on Win2000 SP3
UG NX4.01.0 on Win2000 SP3
SolidWorks 2007 SP3.1 on WinXP SP2

 

[rysep]

I had a very similar problem updating from 2001 to 2006. The issue was either a bad update CD or the CD we got was not SP0 it was SP3.0 or something. No one could figure out what the problem was. Finally my VAR gave me a 2006 SP0 CD and I installed it without absolutely no problems. I then upgraded online to SP3.0 and still fine. So its possible that if it wasn't 2007 SP0 then that could be an issue because Solidworks has certainly had their problems with SP's in 2007. Or you may have gotten a bad disc.

 

[Phadreus]

Jason, we are using Availl as well. We've had a really tough time getting started with it on the performance and stability side of things. We've been live with Availl for about a month now and I think we are almost through with the adjustments to allow best performance. It's been tough for sure...

I restored my files, re-migrated them and everythign si cool again. Thanks for the heads up on Availl!

M.B. Price CSWP

http://www.assembly-testww.com

Automated Assembly & Test Systems

 

[J-C]

We've had it for 3 years....and its never worked right. I mean, it works....but performance is horrbile, it doesn't replicate file attributes, it it occasionally corrupts files. Luckily, it has a nifty web interface and you can restore previous versions of files.

We're looking/hoping to go to a PDM with built in replication and finally drop Availl.

Jason

UG NX2.02.2 on Win2000 SP3
UG NX4.01.0 on Win2000 SP3
SolidWorks 2007 SP3.1 on WinXP SP2

 

[Phadreus]

Two questions for you Jason;

1. Can you more clerly defign "Slave Server" to make sure I'm understanding you?

2. What version of Availl are you running?

Thanks

M.B. Price CSWP

http://www.assembly-testww.com

Automated Assembly & Test Systems

 

[J-C]

I should have said "Client" instead of slave. We have one master server which is also running as a client. Then we had two other remote servers running the client software. So we are replicating to 3 client servers, though one is local to the master since it is the same server.

Not sure about the version....its farily current though since we had our meltdown not too longer ago and I think it was upgraded to the latest then.

Jason

UG NX2.02.2 on Win2000 SP3
UG NX4.01.0 on Win2000 SP3
SolidWorks 2007 SP3.1 on WinXP SP2