SP2.0 Toolbox Issue

[CADGemini]

We have upgraded to SP2.0 but now have an issue with tool box. I get the following error:

The database file is not the expected version (10.16)

Is there a way to manually update the database file? We have our toolbox on the network.



Best Regards,
Jon

Challenges are what makes life interesting; overcoming them is what makes life meaningful.

Solidworks 2006 SP0.0

 

[Theophilus]

Yeah, try searching this forum, especially for the "database file is not the expected version". There was a registry hack posted for this a few weeks ago (although not for SP 2.0).


Jeff Mowry

http://www.industrialdesignhaus.com

Reality is no respecter of good intentions.

 

[CADGemini]

I talked with my VAR and this is what fixed the issue.

If you have the toolbox on the server go to that location and go under the .../lang/english folder and find the file called "swbrowser.mdb". If you have Microsoft Office Access on your computer you can open the file and find the "VERSION" module. Double click on it and change the version to 10.16. Save and close.



Best Regards,
Jon

Challenges are what makes life interesting; overcoming them is what makes life meaningful.

Solidworks 2006 SP0.0

 

[CADGemini]

After fixing the issue with the version error we now have another major issue.

When inserting a fastener into an assembly it is great. Then when you go to insert a different fastener after that it crashes the system. This haapens on more than one computer. I have also tried this in a blank assembly and just inserted fasteners and it re-acts the same way. Has anyone else experienced this issue in SP2.0?

Best Regards,
Jon

Challenges are what makes life interesting; overcoming them is what makes life meaningful.

Solidworks 2006 SP0.0

 

[CADGemini]

Well the issue with toolbox has not been resovled by our VAR yet. Solidworks is still trying to work on this issue.

In the meantime, we are going to be rolling back to SP0.0 until they have a fix for us.

Does anyone else have this issue? If so, you should report it to your VAR so they can submit it to Solidworks.

Best Regards,
Jon

Challenges are what makes life interesting; overcoming them is what makes life meaningful.

Solidworks 2006 SP0.0

 

[EEnd]

I think the root of your problem is that the toolbox on the server did not get updated with the service pack. The problems that you are experiencing are likely the result of changing version on the database without actually updating the data in the database to that expected by SolidWorks.

I do not know of a way to manually upgrade the database. However, since you are at the point where you are going to roll back the service pack, maybe you can try this:

Roll back the service pack on one of the machines, and ensure that that machine is using the network location of the toolbox.

Edit the swbrowser.mdb and return it to the previous version. If you no longer know the previous version number, you can probably try accessing the toolbox from the rolled back computer and seeing what version it expects.

Reinstall the service pack keeping an eye out for toolbox location prompts and ensuring those reference the network location.

The service pack installer should update the toolbox database during the last step. But it really should have before.

The first cause of this that I can think of is that the service pack installer is not picking up the reference to the network toolbox. Correcting this might require a fresh install of the base 2006 SP 0.0 on one of the computers, followed by an upgrade to 2.0, making sure that the install and upgrade both have the network toolbox location.

The second cause that I can think of is some sort of version conflict on the database, and that the service pack installer is not updating the toolbox because the version of the database is not one that it knows how to update. You might want to check that you have the correct service pack file for the version jump that you really are making. There is a different file to upgrade from 0.0 to 2.0 than from 1.0 to 2.0. Having installed the early visibility version of 2.0 might be a potential cause.

 

[SBaugh]

I don't trust Rollbacks.. I would just uninstall and reinstall SP0.

Regards,

Scott Baugh, CSWP

http://www.scottjbaugh.com

faq731-376