Prev: Thread Rolling in Titanium
Next: Error meassage
From: Aron (bacsdesign.com) on 13 Jan 2007 21:39 Hi, I just uninstalled SW2006, SP5.0 and installed SW 2007, SP0.0 (then updated to SP2.2) and have tried to open a few parts, and am getting the following errors... ----------------------------------------------------------------------- [SolidWorks] <-- message box with blue "cloud" exclamation point The following component configuration could not be found. Flush Stud_PMI-1: PEM FH-632-6 X--N Flush Stud_PMI-2: PEM FH-632-6 X--N Flush Stud_PMI-3: PEM FH-632-6 X--N Flush Stud_PMI-4: PEM FH-632-6 X--N If the configuration was renamed the same configuration will be used, otherwise the last active configuration will be substituted in each instance. [OK] ------------------------------------------------------------------------ I clicked OK, then got... ------------------------------------------------------------------------ [SolidWorks] <-- message box with blue "cloud" exclamation point (same type of message box as before) The following documents will be converted when saved: Bill Cover Front.SLDASM Bill Cover Front.SLDPRT [OK] ------------------------------------------------------------------------ Now, I know I have 4 Flush PEMs in the assembly (it was fine in 2006, SP5.0) and the assembly was made of the parts above... Bill Cover... Why is this happening, and how do I fix it? I have thousands of assemblies and parts here on my system, If Right Click, I cannot "Edit Toolbox Configuration" because it is grayed out... Help Please, this is a real problem I have drawings to get out early Monday and was trying to get a jump on things this weekend. Thank You for any assistance please, Aron
From: Bo on 14 Jan 2007 02:03 Aron, after listening to this group's problems with various SWks 2007 issues, I am convinced to stay with 2006 SP 5.1 for the foreseeable future. I think it is best to revert to backups or archives and use 2006 until there is verified good 2007 SPs and you have a definite need to go to 2007. I have not upgraded to a new "year" of SolidWorks until at least SP 4. My time is too valuable to do otherwise. The days of mindless hardware and software upgrades are over. VISTA as an OS is NOT AN OPTION for me. The early testers call it a dog, let alone other issues. Good Luck - Bo Aron (bacsdesign.com) wrote: > Hi, > > I just uninstalled SW2006, SP5.0 and installed SW 2007, SP0.0 (then updated > to SP2.2) and have tried to open a few parts, and am getting the following > errors... > > > Why is this happening, and how do I fix it? > > I have thousands of assemblies and parts here on my system, If Right Click, > I cannot "Edit Toolbox Configuration" because it is grayed out... > > Help Please, this is a real problem I have drawings to get out early Monday > and was trying to get a jump on things this weekend. > > Thank You for any assistance please, > > Aron
From: Zander on 14 Jan 2007 11:52 Hi Aron, When you installed 2007 did you designate a new location for the toolbox install? If you did, then it will have an empty database (mdb) file. If when you installed 2007 you specify the same toolbox path that 2006 used then it should update properly. I specified the same path and didn't have this problem, but I can't garuntee this is the answer for you. As a quick-fix to the problem you describe below ( The following component configuration could not be found.) Just open the toolbox and drag in the same pem stud that is noted as missing into the assembly, spec the same size etc. This will recreate the missing configuration in the toolbox database. Then delete the newly created pem stud. Zander Aron (bacsdesign.com) wrote: > Hi, > > I just uninstalled SW2006, SP5.0 and installed SW 2007, SP0.0 (then updated > to SP2.2) and have tried to open a few parts, and am getting the following > errors... > > ----------------------------------------------------------------------- > [SolidWorks] <-- message box with blue "cloud" exclamation point > > The following component configuration could not be found. > > Flush Stud_PMI-1: PEM FH-632-6 X--N > Flush Stud_PMI-2: PEM FH-632-6 X--N > Flush Stud_PMI-3: PEM FH-632-6 X--N > Flush Stud_PMI-4: PEM FH-632-6 X--N > > If the configuration was renamed the same configuration will be used, > otherwise the last active configuration will be substituted in each > instance. > > [OK] > ------------------------------------------------------------------------ > > I clicked OK, then got... > > ------------------------------------------------------------------------ > [SolidWorks] <-- message box with blue "cloud" exclamation point (same type > of message box as before) > > The following documents will be converted when saved: > > Bill Cover Front.SLDASM > Bill Cover Front.SLDPRT > > [OK] > ------------------------------------------------------------------------ > > Now, I know I have 4 Flush PEMs in the assembly (it was fine in 2006, SP5.0) > and the assembly was made of the parts above... Bill Cover... > > Why is this happening, and how do I fix it? > > I have thousands of assemblies and parts here on my system, If Right Click, > I cannot "Edit Toolbox Configuration" because it is grayed out... > > Help Please, this is a real problem I have drawings to get out early Monday > and was trying to get a jump on things this weekend. > > Thank You for any assistance please, > > Aron
From: Bo on 14 Jan 2007 12:21 Zander, I truly hope your suggestion below works for Aron. I have a single Mandatory Boy Scout Rule on upgrades & this applies to: A. Hardware: Leave the old hardware in place & functional, & install a new Hard Drive or Computer as needed without changing the prior OS/Hard Drive...(Guaranteed Reversion to 100% working condition) B. Software: Slightly less certain is to leave the old SWks-OS installation in place & intact & ready to go, & put "new" upgraded OS's or software applications on a new Hard Drive...(Not a 100% solution, as there is always a chance for screwing up a motherboard, Hard Drive controller, or whatever when firmware might be upgraded). Choice "A" is the ONLY way to avoid the slight chance of an inability to rapidly deliver design work when something crashes out. If I had a project with high complexity and/or a huge amount of parts and had to deliver designs in a week, I would NEVER upgrade anything, until I had a lull in work, and enough time to smoothly, carefully install, archive-backup and check things out in an organized manner. The cost of a whole new computer is nothing compared to the loss of delivering a key project to a valued customer. If you are billing for 100 hours work, but can't deliver because an upgrade screwed up the delivery, & you lost or delayed $5000 billings at least, because you wouldn't buy a new hard drive, what does that say? Bo Zander wrote: > Hi Aron, > > As a quick-fix to the problem you describe below ( The following > component configuration could not be found.) > > Just open the toolbox and drag in the same pem stud that is noted as > missing into the assembly, spec the same size etc. This will > recreate the missing configuration in the toolbox database. Then > delete the newly created pem stud. > > Zander
From: Zander on 14 Jan 2007 13:11
All good points! I was only addressing his toolbox issue and not his deadlines or backups. I too am very cautious with upgrades/backups etc. I still have a complete archive of all my projects prior to upgrading to 2007 and an older computer with 2006 installed. In fact with 4 computers in my office (including my laptop) - plus nightly backups to removable drives, intra-day zip files of projects on the go, pdm vault backups as well, online backup running 24/7, raid-5 arrays and offsite backup at my friends house you could even call me 'overly cautious'!!! If Aron ignores trying to 'fix' or 'upgrade' his toolbox and simply creates toolbox items that match his missing studs for now he will be able to get some work done. It's a pretty simple workaround as long as you assembly doesn't contain thousands of differnet toolbox parts.... Zander Bo wrote: > Zander, I truly hope your suggestion below works for Aron. > > I have a single Mandatory Boy Scout Rule on upgrades & this applies to: > > A. Hardware: Leave the old hardware in place & functional, & install > a new Hard Drive or Computer as needed without changing the prior > OS/Hard Drive...(Guaranteed Reversion to 100% working condition) > > B. Software: Slightly less certain is to leave the old SWks-OS > installation in place & intact & ready to go, & put "new" upgraded OS's > or software applications on a new Hard Drive...(Not a 100% solution, as > there is always a chance for screwing up a motherboard, Hard Drive > controller, or whatever when firmware might be upgraded). > > Choice "A" is the ONLY way to avoid the slight chance of an inability > to rapidly deliver design work when something crashes out. > > If I had a project with high complexity and/or a huge amount of parts > and had to deliver designs in a week, I would NEVER upgrade anything, > until I had a lull in work, and enough time to smoothly, carefully > install, archive-backup and check things out in an organized manner. > > The cost of a whole new computer is nothing compared to the loss of > delivering a key project to a valued customer. If you are billing for > 100 hours work, but can't deliver because an upgrade screwed up the > delivery, & you lost or delayed $5000 billings at least, because you > wouldn't buy a new hard drive, what does that say? > > Bo > > > Zander wrote: > > Hi Aron, > > > > As a quick-fix to the problem you describe below ( The following > > component configuration could not be found.) > > > > Just open the toolbox and drag in the same pem stud that is noted as > > missing into the assembly, spec the same size etc. This will > > recreate the missing configuration in the toolbox database. Then > > delete the newly created pem stud. > > > > Zander |