Problem You have installed Vault Server 201x on a 64 bit OS and let it automatically install SQL 2008 Express SP2 (32 bit) on a 64 bit machine.
Your end-state goal is 64 bit OS AUTODESKVAULT running in a 64 bit SQL 2008 Standard\Express\Enterprise (R2 or not R2) SQL instance.
Microsoft does not support cross platform upgrades from 32 to 64 bit. (See "Version and Edition Upgrades”This means that if you then manually install 64 bit SQL, it will not upgrade the exisiting 32 bit AUTODESKVAULT instance to a 64 bit instance.
Solution You will need to 1) Uninstall SQL Server 2008 (32 bit). (No need to uninstall Vault Server as well)
2) Manually install SQL Server 2008 (64 bit) (Standard, Express (R2 or not R2) as per the Advanced Configuration Guide.
3) Create and configure the VaultSys account as per the Advanced Configuration Guide
4) Create and configure the ADMS-<Computername> account.
Open the Microsoft SQL Server Management Studio.
Expand the Security -> Logins folder.
Right-click on the Logins folder and select New Login.
Type ADMS-* for the login name.(Where * indicates the NT Computer name) Example, if the computer name is MAINSERVER then the login name would = ADMS-MAINSERVER
Select SQL Server Authentication.
Enter the correct password. The correct password can be found web.config file here "C:\Program Files\Autodesk\ADMS Professional 2013\Server\Web\Services" on the "<siteSecurity generateUser" line.
Note: I am not allowed to publish passwords on this blog for security reasons, although I am allowed to write where to find them.
After installing Vault Server in one language, English for example, you would like to have a localised version of the web client displayed, German for example.
The language of the web client is dictated by the language of the Server and it cannot be changed. However, some supported web browsers allow translation addins to be installed so that text in the web page is automatically displayed in the desired language.
The image below is the Vault Professional 2012 Web client, logged into an English Language Vault Server, but the Chrome browser has the Google Translate add-in installed and is displayed in German.
Autodesk regularly publishes White Papers regarding frequently asked-for topics such as how something works, best practices and optimising performance. There is a wealth of topics covered on the Autodesk Vault White Paper website.
"Geographically dispersed teams using 3D for clear design communication may struggle to collaborate effectively because sharing data using common Microsoft Windows file directories can take too long. Autodesk® Vault helps solve this problem by improving access to the latest designs even across global, wide area networks (WANs). When WANs exhibit high latency, the combination of Autodesk Vault and Riverbed® WAN optimization technology utilizing Steelhead®, a powerful data store and deduplication appliance, provides an effective solution to help maintain fast and efficient design data access. Tests performed by Autodesk illustrate the value of this combination—the addition of WAN optimization may dramatically reduce file transfer by up to 99% without further requirements to upgrade or replace existing software or hardware"
When using Vault Workgroup, Collaboration, or Professional with AutoCAD Civil 3D, a configuration file must be imported into every Vault database which will be accessed from a Civil 3D client. The configuration file is named Civil3D_Vault_Configuration.cfg and can be found in these locations:
On 32-bit Operating Systems: C:\Program Files\Autodesk\ [ADMS Release] \Custom Configuration.
When Searching for files in the vault, you can see this message appear at the top of the Search Grid.
"The standard search results are incomplete because the property indexes are being created. Complete search results will be available once the file properties are fully indexed ."
This can happen for two reasons.
1) The administrator has recently initiated a "Rebuild Search Indexes" from the ADMS Console. In this case, in the Tools>Server Tasks Pull down menu, The "on-demand" "Search indexing" task will be running.
2) One or more users have recently checked in a large number of files that are still waiting to be indexed. The time it takes to process this will depend on the number of files to be processed, the current workload of the server itself and the hardware resources it has available.