Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations MintJulep on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!
"Check for Updates. . ." not working
- Thread starter Updraft
- Start date
CorBlimeyLimey
Mechanical
Are you sure the 'update' window isn't behind the SW window? It's supposed to pop-up in front, but sometimes doesn't.
Have you tried the Start > All Programs > SolidWorks Installation Manager > Check For Updates route?
Have you tried the Start > All Programs > SolidWorks Installation Manager > Check For Updates route?
- Thread starter
- #3
CBL,
To your first comment: nothing anywhere. I even individually minimized all open windows and the update window isn't there.
To your second comment: This worked just fine, but I should get the same result from the SWX Help -> Check for Updates route. It bugs me this isn't working from the Help menu and makes me wonder what else is going on (or not going on).
This is happening on both my work and my home machines. The Updates has always worked before from the Help menu. Any other ideas?
- - -Updraft
To your first comment: nothing anywhere. I even individually minimized all open windows and the update window isn't there.
To your second comment: This worked just fine, but I should get the same result from the SWX Help -> Check for Updates route. It bugs me this isn't working from the Help menu and makes me wonder what else is going on (or not going on).
This is happening on both my work and my home machines. The Updates has always worked before from the Help menu. Any other ideas?
- - -Updraft
CorBlimeyLimey
Mechanical
Have you tried running a SW Repair from the install disc?
Have you checked the SW knowledge Base for a possible solution?
Have you checked the SW knowledge Base for a possible solution?
Just Go to the SolidWorks Customer Portal to check for updates and see what fixes were implemented.
You can check sprs fixed list to see what's changed and if you need it.
If you are not waiting for any fixes or none have been implemented what's the point of updating. One place I worked someone updated to 2008 sp2.1 when the only thing fixed was a foreign language menu interface. What's the point of updating if you aren't experiencing problems other than PDM 2009 where you must be at same SP as Vasult which is BS in my opinion.
Michael
You can check sprs fixed list to see what's changed and if you need it.
If you are not waiting for any fixes or none have been implemented what's the point of updating. One place I worked someone updated to 2008 sp2.1 when the only thing fixed was a foreign language menu interface. What's the point of updating if you aren't experiencing problems other than PDM 2009 where you must be at same SP as Vasult which is BS in my opinion.
Michael
mjcole said:
That statement is incorrect. The requirement is that you must be at the same major version as the vault, i.e. 2009 vs. 2008. Individual SP's within the major release don't matter. If the vault is of a newer SP you can update your client without DL'ing anything. If the client is newer than the vault the system sees no difference.
Joe Hasik,
CSWP/SMTL/MTLS
SW 09 x64, SP 4.1
Dell T3400
Intel Core2 Quad
Q6700 2.66 GHz
3.93 GB RAM
NVIDIA Quadro FX 4600
RawheadRex
Mechanical
Joe,
Not to split hairs but when SP1 came out there was an issue retrieving files from an SP0 vault which required that the client and server both be at the same SP level. It's still an issue if you have a vault running at SP0. I just had to help someone with that problem yesterday. To resolve I had the download SP4.1 of the server software to match the clients. Maybe I could have gotten away with SP1 (or another SP) of the vault but why risk further complications?
Best regards,
Chris Gervais
Application Engineer
CSWP, CSWST
Not to split hairs but when SP1 came out there was an issue retrieving files from an SP0 vault which required that the client and server both be at the same SP level. It's still an issue if you have a vault running at SP0. I just had to help someone with that problem yesterday. To resolve I had the download SP4.1 of the server software to match the clients. Maybe I could have gotten away with SP1 (or another SP) of the vault but why risk further complications?
Best regards,
Chris Gervais
Application Engineer
CSWP, CSWST
Chris,
I'm pretty sure the Vault and Client must match for 2009 versions so your solution is probably correct. I think I may have spoken to you about this sometime this year.
Like Joe said, in 2008 the SP versions did not have to match between vault and client. In 2009 SolidWorks changed this most likely because of problems users were running into when using mismatched SPs.
If you are a user who runs the PDMW Vault Admin tool and you use the Installation Manager be sure to manualy update and check that the third option in PDMWorks+SolidWorks Explorer tab is selected or you may not be able to login as Vault Administrator. If you are missing the icon on the Shortcut or it's no longer in your start menu the auto install didn't mark it for update.
By saying the minor release versions need to match they can point to that being the cause of the problem and suggest installing the latest version.
For the 2010 release SolidWorks will not allow multiple SPs to be installed on the same machine. This will be inconvenient for me because I always used to leave the previous SP on my machine as a Safety in case there were any problems updating to the latest Service Pack. The 2010 Installation Manager is a lot smoother interface and should make changes easier and reduce the number of NEXT clicks.
Michael
I'm pretty sure the Vault and Client must match for 2009 versions so your solution is probably correct. I think I may have spoken to you about this sometime this year.
Like Joe said, in 2008 the SP versions did not have to match between vault and client. In 2009 SolidWorks changed this most likely because of problems users were running into when using mismatched SPs.
If you are a user who runs the PDMW Vault Admin tool and you use the Installation Manager be sure to manualy update and check that the third option in PDMWorks+SolidWorks Explorer tab is selected or you may not be able to login as Vault Administrator. If you are missing the icon on the Shortcut or it's no longer in your start menu the auto install didn't mark it for update.
By saying the minor release versions need to match they can point to that being the cause of the problem and suggest installing the latest version.
For the 2010 release SolidWorks will not allow multiple SPs to be installed on the same machine. This will be inconvenient for me because I always used to leave the previous SP on my machine as a Safety in case there were any problems updating to the latest Service Pack. The 2010 Installation Manager is a lot smoother interface and should make changes easier and reduce the number of NEXT clicks.
Michael
The SP 0 issue with items not being to be retrieved was a known issue fixed in SP 1, hence the update requirement. We ran a SP 1 vault all the way through client SP 3. We didn't update the vault until everybody moved to 4.1 and we never had a problem. Sounds like somebody is blowing smoke someplace it shouldn't be for you.
Joe Hasik,
CSWP/SMTL/MTLS
SW 09 x64, SP 4.1
Dell T3400
Intel Core2 Quad
Q6700 2.66 GHz
3.93 GB RAM
NVIDIA Quadro FX 4600
Joe Hasik,
CSWP/SMTL/MTLS
SW 09 x64, SP 4.1
Dell T3400
Intel Core2 Quad
Q6700 2.66 GHz
3.93 GB RAM
NVIDIA Quadro FX 4600
- Status
Similar threads