Vault 2013 basic can no longer map folders

[cmclean]

I have and i believe installed the vault ADMS and clients successfully for Vault basic 2013, but when going to Vault Client basic and trying to map folders to other folders out side the Workspace, i get the message "Server is not Confgured to use that feature"

In all previous versions i have had the workspace installed and mapped to local c drives on user machines and the library files mapped to the server folders where they actually reside and all users have shared libraries from there.

I am finding in 2013 that the libaries are being forced into the workspace now. I have turned of Force folder from with in Vault Client and have looked on the server in the ADMS for an alternate switch but dont see anything.

It is acting like its been enforced some where and i dont know how to un inforce this. I have 12 years of libraries in libray folders on the server

I have Autodesk non related folders in my vault  for pdf docs etc and they are on the server. Their folders are also being forced to the workspace root.

So when i RMB> a folder under the root $ and select "Go to Working Folder" the client makes a folder on the c drive under workspace and when I RMB> Properties for any folder under root, it wont wont allow mapping to any other location and again pops up the message.

How do i relax this enforced condition or is this now how vault 2013 basic operates. Alternately, if this is not how 2013 is meant to operate and i have Enforced Folders turned off,  is there something possibly wrong with my install?

Thanks in advance for any help rendered

Colin

[cmclean]

I have and i believe installed the vault ADMS and clients successfully for Vault basic 2013, but when going to Vault Client basic and trying to map folders to other folders out side the Workspace, i get the message "Server is not Confgured to use that feature"

In all previous versions i have had the workspace installed and mapped to local c drives on user machines and the library files mapped to the server folders where they actually reside and all users have shared libraries from there.

I am finding in 2013 that the libaries are being forced into the workspace now. I have turned of Force folder from with in Vault Client and have looked on the server in the ADMS for an alternate switch but dont see anything.

It is acting like its been enforced some where and i dont know how to un inforce this. I have 12 years of libraries in libray folders on the server

I have Autodesk non related folders in my vault  for pdf docs etc and they are on the server. Their folders are also being forced to the workspace root.

So when i RMB> a folder under the root $ and select "Go to Working Folder" the client makes a folder on the c drive under workspace and when I RMB> Properties for any folder under root, it wont wont allow mapping to any other location and again pops up the message.

How do i relax this enforced condition or is this now how vault 2013 basic operates. Alternately, if this is not how 2013 is meant to operate and i have Enforced Folders turned off,  is there something possibly wrong with my install?

Thanks in advance for any help rendered

Colin

[Senthil_Kumar · Accepted solution]

Hi Colin,

Please install the following hotfix and then try properties.

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=18674074&linkID=9261341

[cmclean]

That fixed it .. thank you..

 I was almost ready to roll back to 2012 unfortunately that would have meant rolling back many workstations aswell.

Good job Autodesk Vault team

[scottmoyse]

I just came across this issue the other day when mucking about with Vault Basic. Cheers for sharing the solution on here. Now I know it's not because I was going mental.