Toolbox database version error

[macPT]

Hi all

Just found that one of the reasons that causes the error "database file is not the expected version" is the access previleges to the c:\programs\sheared files folder.

If you have full read/write access (administration access)it's OK (it will be the case of the majority of SW users). But if you have limited access (like in companies where the IT guys limit access to users), the error occurs.

I guess it's another case of MS meaningful error messages!


Regards

 

[CADGemini]

macPT,

Do you see this on 2006 SP0.0? We have a different toolbox issue that could be related to access privileges. We have to continue to run SP0.0 until solidworks finds a fix for the issue.

The issue is as follows:

If we upgrade 2006 SP0.0 to any SP that is currently available we see an error with the toolbox parts. When adding one toolbox fastener to an assembly and then immediatly after trying to insert a completely different toolbox item it decides to crash the sytem. (It does not matter what fastener is inserted) Also tried this with a empty assembly just inserting different toolbox items and it always freezes and dies upon trying to insert the different fastener.

I think I will try talking to our IT department to see what access privledges each of us has. It may be related and maybe not.

Good find either way!!



Best Regards,
Jon

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

Solidworks 2006 SP0.0

 

[macPT]

This error never occurred to me.

I was installing SW2006 on a new PC. SW need to be installed with administrator previleges. Although I'm not an IT guy, they give me these previleges while installing SW.

After installation (SP3.4), SW was tested, with administrator login, and everything was OK.

After login as a regular user, the error ocurred. Some repetitive testing was done, and the conclusion is that if you have limited access previleges to the shared files folder (where the toolbox database is installed) toolbox will fail with that error message.

For now I don't kown if this error is also related with a certain version of SW or Toolbox:
1 - there's no guarantee that the configuration of this new PC (done by the IT guys) is the same as the previous PC (that is, on the previus PC I could have the correct previlegies and, for that reason, never detected this behaviour).
2 - the tests where done with SP3.4 installed. SP0.0 could cause a different behaviour

And you must consider this as one cause. Unfortunately there can be many others.

Good Luck

 

[macPT]

To complete the information, Toolbox didn't crash SW or the system. Only failed to load or access database (the Design Library pane would show empty space under Toolbox selection).

Regards

 

[EEnd]

We ran into this when the server where our toolbox resides was upgraded. I agree that the message was misleading at best. Because the server had just changed we focused on that. Some fiddling with the permissions on shared folder resolved it. We are using 2006 SP 1.0.

Eric