Adms 2008 Advanced Config Guide0

8/6/2019 Adms 2008 Advanced Config Guide0

1/71

AUTODESK

DATA MANAGEMENT SERVER 2008

Advanced Configuration Guide for

Autodesk

Data Management Server 2008


2/71

Contents

Introduction................................................................................................................................ 1Installing Autodesk Data Management Server 2008 ................................................................ 1Customizing your Autodesk Data Management Server 2008 installation ................................. 1Installing the Autodesk Data Management Server on a different web server port ................... 3Install MS SQL Server prior to installing ADMS 2008 ............................................................. 13

Reconfiguring SQL Logins................................................................................................... 15Managing a remote file store................................................................................................... 16

Moving the file store to a mapped drive or remote share .................................................... 17Create a new domain user account. ................................................................................ 17Create a remote share. .................................................................................................... 17Setting the new account in the ADMS Console ............................................................... 17Moving the vault file store ................................................................................................ 18

Reconfigure IIS Worker Process and Application Pool ....................................................... 18Content Indexing on a remote file store .............................................................................. 19

Installing ADMS 2008 on Microsoft Vista

............................................................................. 20Supported Vista Versions .................................................................................................... 20Configuring Internet Information Services (IIS) 7.0 ............................................................. 20User Account Control .......................................................................................................... 21

Configuring automatic backups with Microsoft Vista

............................................................ 22Setting up a remote backup location ....................................................................................... 23Configuring a remote Vault/Productstream connection using FQDN ..................................... 24Upgrading ADMS 2008 to Full SQL Server ............................................................................ 25

Upgrading MSDE to MS SQL 2000 Server ......................................................................... 26Upgrading MSDE to Microsoft SQL 2005 Express ............................................................. 29Upgrading MS SQL 2005 Express to Full MS SQL 2005 .................................................... 30Upgrading SQL 2005 Express SP1 to full SQL Server 2005 SP1 or higher. ...................... 35

Creating a SQL Maintenance Plan ......................................................................................... 36How to increase the timeout values on the ADMS server ...................................................... 43Running Autodesk Data Management Server with SSL ......................................................... 44

Configuring the DM Server machine ................................................................................... 44Configure the AutodeskDM Virtual Directory to require SSL Access .................................. 45Configuring Client Machines ............................................................................................... 46

Solution 1 - Add the CA root certificate to the Trusted Root Certification Authority storeon the client machine ....................................................................................................... 46Solution 2 - Check the expiration date of the certificate .................................................. 50Solution 3 - Verify the certificate name matches the name of the site ............................ 50


3/71

Login from client applications using SSL ............................................................................. 51Using Vault with a Proxy Server ............................................................................................. 52

Change the proxy settings in Internet Explorer 6.x ............................................................. 52Configure the proxy server to use a host name .................................................................. 52

Autodesk Data Management Server Log Files ....................................................................... 53Autodesk Data Management Server (ADMS) 2008 installation log files ............................. 53Autodesk Server Diagnostic Tool Log files.......................................................................... 53Vault server log files ............................................................................................................ 54Microsoft SQL Server log files ............................................................................................. 54DWG and DWF iFilter Log files ........................................................................................... 54Indexing Block Attributes (DWG files) ................................................................................. 55

Customize W3C Extended Logging ........................................................................................ 56Troubleshooting ASP Pre-Check failures. .............................................................................. 59Common 29001 Errors ............................................................................................................ 61Productstream Replication ...................................................................................................... 62

Scalability of Replication ...................................................................................................... 62Content Center in a Replicated Environment ...................................................................... 63Private Content Center Folder ............................................................................................. 63Shared Content Center Folder ............................................................................................ 65Seeding the Content Center Folders ................................................................................... 66Configuring a Shared Content Center Folder ...................................................................... 66

Revision History ...................................................................................................................... 68


4/71

ADVANCED CONFIGURATION GUIDE

Rev. 1.1 - 1 -

Introduction

The Advanced Configuration Guide contains additional information for setting up theAutodesk

Data Management Server 2008 (ADMS). The topics in this guide relate to the

Autodesk Data Management Server and can be used for both Autodesk Vault 2008 andAutodesk Productstream 2008 installations. As these topics cover advanced configurations,

some familiarity with IT procedures is assumed. For more information, refer to the AutodeskData Management Server Implementation and Managing Your Data guides.

Installing Autodesk Data Management Server 2008

For standard installation configurations, consult the Autodesk Data Management Server 2008Implementation and Managing Your Data guides.

Customizing your Autodesk Data Management Server 2008 installation

To customize your installation perform the followng:

1. When you get to the Review Configure Install section in the Installation wizard,

select the Configure button next to the product drop-down list.

2. In the next screen, select the Autodesk Data Management Server 2008 tab. Hereyou will have the option to change the Interactive mode for the ADMS System checkand change the destination folder for the ADMS application.


5/71


Rev. 1.1 - 2 -

3. Click the Next button and the following screen will give you the option to set the folderfor the location of the SQL installation and SQL database.

4. You will also have the option to set the SQL SA password during installation bychecking the box next to Use my SQL credentials.

5. Select the Configuration Complete button in the lower right corner of the dialog toreturn to the Review Configure Install dialog. This will then show you the currentsetting that will be used during the installation. Confirm your custom settings andselect Install to start the installation.


6/71


Rev. 1.1 - 3 -

Installing the Autodesk Data Management Server on adifferent web server port

The Autodesk Data Management software will usually coexist with other web applications inthe Default Web Site of IIS. However, there are certain applications that require exclusiveaccess to the website, different .Net Framework or different security settings. Theseinstructions illustrate how to install the ADMS software on another port and site to avoidconflicts. These instructions are based upon Microsoft Windows 2003 server software. Usersof Microsoft Windows 2000 server may be able to perform similar operations, but some of thescreens will be different.

1. Start the Internet Information Services (IIS) Manager in the Administrative Tools ofthe Control Panel.

2. Right-click on Application Pools and select New Application Pool.

3. In the Add New Application Pool dialog type AutodeskAppPlin the Application pool Idfield.

4. Click the OK button to close the Add New Application Pool dialog box.

5. Expand the Web Sites folder and right-click on the Default Web Site and selectProperties.


7/71


Rev. 1.1 - 4 -

6. Temporarily change the existing default web site to run on a different port, forexample 8080. If you have other application that are running on port 80 you will haveto temporarily change the port number those as well.

7. Right-click the Web Sites folder and then select New Web Site to create a new website.

8. This wizard helps you create a new web site for Autodesk DM Products.


8/71


Rev. 1.1 - 5 -

9. Type Autodesk Vault in the Description field.

10. By default, the ADMS installation looks for the site on port 80. Use the default settingof 80 in the IP address and Port Settings dialog.


9/71


Rev. 1.1 - 6 -

11. The actual directory for this website is not important. You should create a temporaryfolder and set the Path field to this location.

12. Use the following options in the Web Site Access Permissions dialog box.

13. Click Next and then click Finish to complete the creation of the new web site.


10/71


Rev. 1.1 - 7 -

14. Right click on the web site you just created and select Properties.

15. Open the Home Directory tab and select AutodeskAppPl in the Application Pool drop-down list.


11/71


Rev. 1.1 - 8 -

16. Open the ASP tab and select 2.0.50727 from the ASP.NET version drop-down list.

17. Use Notepad or another text editor to create a simple html file. It is necessary tocreate a file on the new website to pass some of the pre-checks on the ADMS Serverinstaller.


12/71


Rev. 1.1 - 9 -

18. Make sure that the new website works by opening Internet Explorer and typinghttp://localhostin the Address field.

19. Start the ADMS server installation and correct any errors reported by the pre-checks.

20. After the installation is complete, log into the vault from a client workstation and startthe ADMS Console to verify that it is working properly.

21. After you have confirmed everything is working properly, close the ADMS Consoleand log the client workstation out of vault.

22. Go back to the IIS Manager and choose Properties for the new web site.
http://localhost/http://localhost/http://localhost/


13/71


Rev. 1.1 - 10 -

23. Change the TCP port to an unused port number. Port 8081 is often available.

24. Open Windows Explorer and navigate to the \Autodesk\DataManagement Server 2008\ADMS Console directory.

25. Make a copy of the Connectivity.ADMSConsole.exe.Config file.

26. Open the Connectivity.ADMSConsole.exe.Config file with Notepad.

27. Find the following line: . Change this value to theport number that you set up for the vault web site. Save and close the file.

28. In Windows Explorer, navigate to the \Autodesk\Data ManagementServer 2008\Server\Web\Services directory.

29. Make a copy of the web.config file.

30. Open the web.config file with Notepad.

31. Find the following line: . Change this valueto the port number that you setup for the vault web site. Save and close the file.

32. In Windows Explorer, navigate to the \Autodesk\Data ManagementServer 2008\Server\Dispatch directory.

33. Make a copy of the Connectivity.WindowsService.JobDispatch.exe.config file.

34. Open the Connectivity.WindowsService.JobDispatch.exe.config file with Notepad.

35. Find the following line: . Change this valueto 127.0.0.1:port number. Save and close the file.


14/71


Rev. 1.1 - 11 -

36. Stop the Autodesk Vault website and then restart it.

37. Open the Services icon in the Administrative Tools of the Control Panel.

38. Find the Autodesk Data Management Job Dispatch service and Restart the services.


15/71


Rev. 1.1 - 12 -

39. Users accessing the vault need to add the new port number to the server name fieldwith the following format: Hostname:portnumber.

40. Open the properties of the original Default Web Site. Set the TCP Port back to 80

and then stop and restart the web site. You will have to perform this step on anyother web application that was also previously set to port 80.

Note: Hotfixes and service packs may not install in this configuration. You may have totemporarily change the port back to 80 to apply the hotfix or service pack.


16/71


Rev. 1.1 - 13 -

Install MS SQL Server prior to installing ADMS 2008

Autodesk Data Management Server 2008 installs the Microsoft SQL 2005 Express Edition ofSQL if it is unable to find an existing AutodeskVault Instance of Microsoft SQL alreadyinstalled. You can install Microsoft SQL 2000 Standard Edition with SP4, Microsoft SQL2000 Enterprise Edition with SP4, Microsoft SQL 2005 Workgroup, Microsoft SQL 2005Standard Edition or Microsoft SQL 2005 Enterprise Edition prior to installing the ADMS 2008so that you do not have to perform the upgrade at a later time.

Note: This installation process may require the server to reboot multiple times. Please besure you are able to perform the necessary reboots. Also, if you use a custom password forthe SQL SA account, you will need to specify this password during the installation of theADMS server. Please see theCustomizing your Autodesk Data Management Server 2008Installationsection in this document.

Use the following steps for Microsoft SQL 2000:

1. Start the installation process for Microsoft SQL 2000 Server.

2. Select any other components or tools which you would also like to include in theinstallation.

Note: During the installation, you can customize the location of the program anddatabase files. However, this version of the product does not support separating thedatabase files from the transaction log files.

3. You are prompted for the service account information. You can use the LocalSystem account. If you plan on performing backups and restores to remote locations,use a Domain User account. (seeSetting up a remote backup location)

4. In the Authentication Mode dialog, select Mixed Mode.

5. Set the SA login password. The default password used during a default installation isAutodeskVault.

Note: If you use a different SA password, you will need to use the use my SACredintials option in theCustomizing your Autodesk Data Management Server 2008Installationsection in this document.

6. In the Instance Name dialog, uncheck the Default check box and name the instanceAutodeskVault.

Note: If you install SQL without using this instance name, the ADMS installation willcreate its own instance of SQL Server called AutodeskVault.


17/71


Rev. 1.1 - 14 -

Use the following steps for Microsoft SQL 2005:

1. Start the installation process for Microsoft SQL 2005 Server.

2. The installation process installs any necessary prerequisites and begins running thepre-installation checks. Note any errors and take the necessary corrective actionsbefore continuing.

3. In the Components to Install dialog, select SQL Server Database Services. Tomodify the installation path, click Advanced.

a. In the Feature Selection dialog, you can expand the Database Servicesoptions and change the location of the data files directory.

4. In the Instance Name dialog, enter the name of the instances as Autodeskvault.

Note: If you install SQL without using this instance name, the ADMS installation willcreate its own instance of SQL Server called AutodeskVault.

5. In the Service Account dialog, specify the Local System account or if you plan onperforming backups and restores to remote locations, specify a Domain User accountfor the SQL Server.

6. In the Authentication Mode dialog, select Mixed Mode authentication and set the SApasswordThe default password used in during a default installation isAutodeskVault.

Note: If you use a different SA password, you will need to use the use my SACredintials option in theCustomizing your Autodesk Data Management Server 2008Installationsection in this document.


18/71


Rev. 1.1 - 15 -

Reconfiguring SQL Logins

If you dont have a domain password policy, you can skip this section. If your domain has apassword policy configured, you must use a password that complies with the policy. After theinstallation is complete, reset the sa password to AutodeskVault and uncheck the Enforcepassword policy check box. It is also necessary to create a SQL login account namedVaultSys. To create this account:

1. Open the Microsoft SQL Server Management Studio.

2. Expand the Security\Logins folder.

3. Right-click on the Logins folder and select New Login.

4. Type VaultSys for the login name.

5. Select SQL Server Authentication.

6. Type SuperMan769400006! for the password.

7. Uncheck the box for Enforce password policy.

8. Select the Server Roles page.9. Check the boxes next to the following roles:

dbcreator

processadmin

setupadmin

10. Click OK to create the account.


19/71


Rev. 1.1 - 16 -

Managing a remote file store

To move the location of your file store to a mapped drive or remote shared location:The vault supports two basic file store configurations:

1. File store located on the ADMS server.

2. File store located on a remote file server that has a shared folder.

A remote file server can be used for hosting the file store and/or backing up and restoringvault data. This section describes the steps required to configure a remote file store.


20/71


Rev. 1.1 - 17 -

Moving the file store to a mapped drive or remote share

For simplicity purposes, the computer hosting Autodesk Data Management Server is calledDMMachineand thecomputer hosting the remote file store is calledFSMachine. Thedomain name is MyDomain. We are also assuming that the server where ADMS is installedis a member server and not a domain controller.

If you have the ADMS server installed on a domain control, the AutodeskVault domainaccount is used and you can go the Moving the File Store section below.

Create a new domain user account.

1. Open the Active Directory Users and Computers and select an Organizational Unit(OU) to create the account in.

2. Create an account named AutodeskRemote. Set the password to match your domainpassword policy and set the password to never expire.

Create a remote share.

1. Open Windows Explorer on the FSMachine and create a directory called VaultData.

2. Right-click on the folder and select Properties.

3. Go to the Sharing tab and create a new share named VaultData.

4. Click Permissions and set the Everyone group to Full Control.

5. Click OK in the Permissions for Share dialog box.

6. Go to the Security tab and add the AutodeskRemote account and set it to Full Controlpermission.

Setting the new account in the ADMS Console

1. On the DMMachine, open the ADMS Console.

2. From the File menu, select Stop Web Service.

3. Select Tools > Advanced Settings.


21/71


Rev. 1.1 - 18 -

4. In the Advanced Settings dialog, change the User Name toMyDomain\AutodeskRemote and type in the selected password.

5. Apply the changes and then click OK.

Moving the vault file store

1. Select the vault which you would like to move to a different location.

2. Select Actions > Move File Store.

3. Set the New File Store Location field to\\FSMachine\VaultData.

4. Click OK.

Reconfigure IIS Worker Process and Application Pool

1. Open the Active Directory Users and Computers and select an Organizational Unit(OU) to create the account in.

2. Create an account named AutodeskID. Set the password to match your domainpassword policy

3. Make the AutodeskID account a member of the IIS_WPG local group on DMMachine.

4. Give AutodeskID account Full Control permissions to the %SystemRoot%\Tempdirectory on DMMachine.

5. Give the AutodeskID account Full Control permissions to the\\FSMachine\VaultDataremote file store directory.

6. Open Internet Information Services (IIS) Manager and create a new Application Poolnamed AutodeskAppPL.
http://fsmachine/VaultDatahttp://fsmachine/VaultDatahttp://fsmachine/VaultDatahttp://fsmachine/VaultDatahttp://fsmachine/VaultDatahttp://fsmachine/VaultDatahttp://fsmachine/VaultDatahttp://fsmachine/VaultData


22/71


Rev. 1.1 - 19 -

7. Open the properties of the AutodeskAppPL Application Pool and go to the Identitytab.

8. Add the domain account AutodeskID, set the password and apply the changes.

9. Expand the Default Web Site and navigate to the AutodeskDM\Services virtualdirectory.

10. Right-click on the Services directory and go to the Directory tab.11. Change the Application Pool pull-down to the newly created AutodeskAppPL

Application Pool.

12. Apply the changes and close the properties of the Default Web site.

13. Close the IIS Manager.

14. Open a Command prompt and type IISRESET.

15. Add new files to the vault and verify that the properties are able to be indexed.

Content Indexing on a remote file store

Depending on your network environment, you may have to change the account that is being

used to perform the Content Indexing Service on the remote file store. These steps may berequired when you have the ADMS server installed on a member server.

1. On the server where the ADMS server is installed, open the Administrative Toolsfrom Control Panel and double-click Computer Management.

2. In the Computer Management dialog, double-click Services and Applications.

3. Open the Indexing Service folder.

4. There is a catalog starting with ADSK. Expand this folder and open the Directoriessubfolder.

5. The remote file store directory should be listed under the Directory column. If it is notlisted, look in the other ADSK catalog for the correct remote file store directory.

6. Double-click the directory.

7. In the Add Directory dialog, enter the AutodeskRemote user account and enter thepassword in the Password field.

8. Click OK.


23/71


Rev. 1.1 - 20 -

Installing ADMS 2008 on Microsoft Vista

Yes, you can install Autodesk Data Management Server (ADMS) on a computer runningWindows Vista. However, you will need to configure some Vista system settings beforeyou install ADMS.

Supported Vista Versions

The following chart shows the versions of Vista that ADMS is support inside of IIS and whichare supported with the Autodesk Web Server (AWS).

Operating System AWS IIS

Microsoft Vista Ultimate Yes Yes

Microsoft Vista Enterprise Yes Yes

Microsoft Vista Business Yes YesMicrosoft Vista Home Premium Yes No

Microsoft Vista Home Basic Yes No

Note: IIS 7.0 has a limit of 10 simultaneous requests on Vista Ultimate, Enterprise, andBusiness editions. When the connection limit is reached, the request is queued until thenumber of currently processing requests drops below the limit. Then IIS takes the firstrequest in the queue and starts to process it. Previous versions of IIS would return an Error403.9 Access ForbiddenToo many users are connected.

Configuring Internet Information Services (IIS) 7.0

If you will be using Microsoft Internet Information Services (IIS) 7.0 with Autodesk DataManagement Server, you must configure IIS 7.0 before you install ADMS. Once IIS 7.0 is

installed, follow the steps below to configure the system options:1. From the Windows Start menu select Settings > Control Panel.

2. In the Control Panel, double-click Programs.

3. In the Programs and Features group, select Turn Windows Features On or Off.

4. When you are prompted to allow the application to run, click Continue.

5. In the Windows Features dialog box, expand Information Services > WebManagement Tools > IIS 6 Management Compatibility.

6. Select the IIS Metabase and IIS 6 Configuration Compatibility check box.

7. Expand Internet Information Services > World Wide Web Services > ApplicationDevelopment Features.

8. Select the ASP.NET check box. Three other settings will also be automaticallyselected: .NET Extensibility, ISAPI Extensions, and ISAPI Filters.

9. Click OK.


24/71


Rev. 1.1 - 21 -

User Account Control

If you plan to schedule automatic backups using ADMS Console, the User Account Controlsettings in Windows Vista must be configured to allow applications to run without promptingfor administrator permission.

Note: Configuring the following settings will affect all of the applications on your computer. Allapplications will be run without prompting for administrator approval.

1. From the Windows Start menu, select Run.

2. In the Run dialog box, enter secpol.msc. Click OK.

3. When you are prompted to allow the security policy application to run, click Continue.

4. In the Local Security Policy dialog box, expand Security Settings > Local Policies >Security Options.

5. Locate the User Account Control: Behavior of the Elevation Prompt for Administratorspolicy and right-click it. Click Properties.

6. In the Properties dialog box, select Elevate without Prompting, and then click OK.

7. Locate the User Account Control: Run All Administrators in Admin Approval Modepolicy and right-click it. Click Properties.

8. In the Properties dialog box, select Disable, and then click OK.


25/71


Rev. 1.1 - 22 -

Configuring automatic backups with Microsoft Vista

To configure automatic backups in Microsoft Vista

perform the following steps:

1. Open the Task Scheduler in the Administrative Tools of the Control Panel.

2. Create a Basic Task and fill in the necessary information in the dialog box and select

the batch file you created for the backup.

3. When you get to the Summary dialog, check the box next to Open the Propertiesdialog for this task when I click Finish.

4. In the General tab of the task you just created, select the radio button next to Runwhether user is logged on or not.

5. Check the box next to Run with highest privileges.

The following is an example of a backup script you can use for a local SQL Server.

@ECHO OFFREM PROVIDING THE BEST RESULTS FOR BACKING UP THE VAULTREM DELETE B AND CASCADE A BACKUP SUBDIRECTORIESRMDIR /Q /S "C:\Backup\Vault\B"REN C:\Backup\Vault\A BREM CREATE A NEW DIRECTORY FOR THE BACKUPMKDIR "C:\Backup\Vault\A\"REM START THE BACKUP PROCESS (THIS IS ONE LINE OF TEXT)"C:\Program Files\Autodesk\Data Management Server 2008\ADMS

Console\Connectivity.ADMSConsole.exe"Obackup -B"C:\Backup\Vault\A" -VUadministratorVP-SNET STOP MSSQL$AUTODESKVAULTNET START MSSQL$AUTODESKVAULT

Note: Unlike previous versions of ADMS, you no longer need to stop the web servicesbefore you perform a backup. You can also use theDBSC switch in the ADMSConsole lineto exclude the standard content libraries from being backed up during this process.


26/71


Rev. 1.1 - 23 -

Setting up a remote backup location

If you plan to back up your vault data to a remote share, follow the steps in theCreating anew domain user account, Create a remote shareandSetting the new account in the ADMSConsolesections in this document. After that is complete, you will have to modify the SQLService to use a domain account using the following steps:

1. Double-click the Services icon in the Administrative Tools in the Control Panel

2. Double-click on the SQL Server (Autodeskvault) service and select the Log On tab.

3. Select the This Account radio button and enter a domain account in the form ofDomain_Name\Domain_account (with the correct password).

NOTE: If you change the services login credentials, you will be prompted to restartthe MS SQL Server service. Please do so for changes to take effect. In addition,ensure that clients are not using the ADMS server before restarting SQL Server.

4. Verify that the account specified has write access on the share to which you arebacking up.


27/71


Rev. 1.1 - 24 -

Configuring a remote Vault/Productstream connection usingFQDN

To configure the Vault or Productstream server to allow remote connections over theinternet using a Fully Qualified Domain Name (FQDN)

1. Create a DNS "A" or host record for your current FQDN with your ISP.2. Install Autodesk Vault Server or Autodesk Productstream Server on your server and

verify that it works properly.

3. On your server, open the Internet Information Services Manager and expand theWebsites folder.

4. Right-click on the website that contains the AutodeskDM virtual directory. ClickProperties.

5. In the Properties dialog box, click the Website tab.

6. On the Website tab, click Advanced.

7. In the Advanced Website Identification dialog box, under the Multiple identities for the

website, click Add.8. In the Add/Edit Web Site Identification dialog box, select the correct IP address that

will interact with the website.

9. Enter the TCP port you want to use. If this is not port 80, then your clients will have toadd ":" at the end of the FQDN in order for the connection to work.

10. In the Host Header value, enter the FQDN.

11. Click OK to close each dialog box.

Note: Additional settings may be required for your router or firewall. Check with your ITdepartment for the necessary changes.


28/71


Rev. 1.1 - 25 -

Upgrading ADMS 2008 to Full SQL Server

When upgrading to the full version of Microsoft SQL Server, it is assumed the appropriate ITand engineering staff required to allow access to the server and client systems, as well as toallow periodic system restarts are available. It is also recommended that you perform theupgrade in a test environment prior to performing the upgrade on the production environment.

The client side systems are needed to verify that the upgrade has been performedsuccessfully.

The server upgrade can be performed at anytime after Autodesk Data Management Serverhas been installed. The server may need to be rebooted one or two times during the upgradeprocess.

During the upgrade, the SQL server instance and the Autodesk Vault Server Services areshut down. Anyone logged into the vault at the time is automatically disconnected. Makesure all users are logged out of the Autodesk Data Management Server. The upgrade willnot affect the state of checked out files, nor will it modify the database structure, state of thefiles, or parent child relationships.

Before upgrading the SQL server, perform a backup from the ADMS Console application.For more information on backing up data, see the ADMS Console Help.


29/71


Rev. 1.1 - 26 -

Upgrading MSDE to MS SQL 2000 Server

1. From the MS SQL 2000 installation CD, launch the installer.

2. On the installer, select SQL Server 2000 Components.

3. In the Computer Name dialog box, select Local Computer and then click Next.


30/71


Rev. 1.1 - 27 -

4. In the Installation Selection dialog box, select Upgrade and click Next.

5. In the Instance Name dialog box, turn off the Default checkbox. This enables theInstance Name drop-down list. You can either type in the instance name or select itfrom the list. If the drop-down list does not become enabled or show theMSSQL$AUTODESKVAULT instance, your version of the Microsoft WindowsOperating System does not support the SQL Server 2000 Edition.

6. Click Next.


31/71


Rev. 1.1 - 28 -

MSDE 2000 can only be upgraded to SQL Server 2000 Standard or Enterprise Editions andMS SQL 2005 Express or Workgroup Edition.

The following operating systems do not support MSDE to SQL Server upgrades:

- Windows Server 2003 Web Edition- Windows XP Professional Edition (SQL Server 2000 editions)- Windows XP Home Edition

- Windows 2000 Professional- Windows NT 4.0 Workstation- Microsoft Windows Millennium Edition- Microsoft Windows 98- Microsoft Windows CE

The following operating systems support the MSDE to SQL Server upgrades:

- Windows Server 2003, Standard Edition- Windows Server 2003, Enterprise Edition- Windows Server 2003, Datacenter Edition- Windows 2000 Server- Windows 2000 Advanced Server

- Windows 2000 Datacenter Server- Windows NT Server version 4.0 with Service Pack 5 (SP5) or later- Windows NT Server 4.0, Enterprise Edition, with SP5 or later- Windows XP Professional Edition (SQL Server 2005 editions)

NOTE: Autodesk Data Management Server 2008 requires Microsoft SQL 2000 Service Pack4 or later to be applied to all SQL Server 2000 Editions prior to the upgrade.


32/71


Rev. 1.1 - 29 -

Upgrading MSDE to Microsoft SQL 2005 Express

If you are upgrading MSDE edition to MS SQL 2005 Express, you can use the version of MSSQL 2005 Express that is on your ADMS installation disc. This version can be found in theSupport\SQLExpress folder on your ADMS installation disc or you can download MS SQLExpress from Microsofts Web site and perform the following:

1. Before performing the upgrade, make sure you have performed a backup using theADMS Console application.

2. Once the backup is complete, close ADMS Console.

3. Open a Command prompt and type IISReset /Stop. This prevents users fromconnecting to a vault while you are performing the upgrade.

4. Start the installation of Microsoft SQL 2005 Express Edition on the server.

5. During the installation, you will be asked if you would like to upgrade a current SQLInstance. Select the Instance radio button the select AutodeskVault from the drop-down list.

6. Select the default options for the remaining questions and perform the upgrade.

7. Download and install MS SQL 2005 Express Service Pack 2 from Microsofts web

site.8. Open a Command prompt and type IISReset /Start.

9. Open the ADMS Console and log in.

10. Perform another backup from the ADMS Console.

11. Once the backup is complete, close the ADMS Console and your client computerswill be able to connect to the ADMS server.


33/71


Rev. 1.1 - 30 -

Upgrading MS SQL 2005 Express to Full MS SQL 2005

1. Insert your MS SQL 2005 installation disc into the drive and start the installationwizard. It installs the required pre-requisites first then begins the installation process.

2. Click Next. The wizard performs a system configuration check. Verify that all checkshave a status of Success and then click Next.


34/71


Rev. 1.1 - 31 -

3. In the Components to Install dialog, check the SQL Server Database Services andthen click Next.

4. In the Instance Name dialog, select the Named instance radio button and typeAutodeskVault or you can select the Installed instances button and select theAutodeskVault instance and then click Next.


35/71


Rev. 1.1 - 32 -

5. The Existing components dialog lists the SQL Server Database Services that aregoing to upgrade. Check the box next to the SQL Server Database and then clickNext.

6. The Upgrade Logon Information dialog prompts you for an account that will be usedto perform the upgrade. You should be logged in with an account that has localAdministrative privileges on the server. Select the Windows Authentication Modeand then click Next.


36/71


Rev. 1.1 - 33 -

7. In the Service Account dialog, select either a built-in System account or a domainuser account to run the SQL Browser. Click Next.

Note: If you were previously using a user account to run the SQL Server Service,select Use a domain user account radio button and fill in the required fields with thataccount.


37/71


Rev. 1.1 - 34 -

8. The Error and Usage Report Settings dialog displays optional settings that are notrequired by Autodesk.

9. On the Ready to Install dialog, click Install to begin the upgrade process.


38/71


Rev. 1.1 - 35 -

10. Download and install MS SQL 2005 Express Service Pack 2 from Microsofts website.

Upgrading SQL 2005 Express SP1 to full SQL Server 2005 SP1 or higher.

To upgrade a SQL Express 2005 SP1 installation to a full version of SQL 2005 SP1 or higher,

follow these steps:

1. Create a full backup of your vault using the ADMS Console.

Note: In later steps you will be deleting all of your vault databases. You shouldvalidate that this backup is able to be restored on a test server before proceeding.Do not continue if your test restore fails. Correct any problems you have with thebackup prior to continuing these steps.

2. After the test restore is successful, open the ADMS Console and delete all vaults andlibraries listed. Then select Detach Master Vault from the Tools menu.

3. Make sure all users are logged out of the vault.

4. Completely uninstall SQL 2005 Express. This includes the following applications in

this order:

a. Microsoft SQL Server 2005

Note: If you have more then one instance of SQL Express installed, be sureto only uninstall the AutodeskVault instance and DO NOT uninstall any otherpart of SQL after this step is complete.

b. MS SQL Server Native Client

c. MS SQL Server VSS Writer

d. MS SQL Server 2005 Backward Compatibililty

e. MS SQL Server Setup Support Files

5. Delete the SQL Express folders from Program Files (including data files). If yourVault databases are located on a different drive, be sure to delete the files in thislocation as well.

6. Install the full version of SQL 2005 with an AUTODESKVAULT instance as in the"Install MS SQL Server Prior to Installing ADMS 2008" section.

7. Install Microsoft SQL 2005 SP1.

8. Restore the backup that you created in step 1 using ADMS Console.

If you have any difficulty removing the MS SQL Express instance, refer to MicrosoftKnowledgebase article 909967 to help manually remove this instance.


39/71


Rev. 1.1 - 36 -

Creating a SQL Maintenance Plan

Maintenance plans can be used to schedule maintenance tasks required to make sure thatthe database performs well, such as keeping database and transaction log file size small andchecking the database for inconsistencies.

1. Verify that the vaults have been backed up with the ADMS Console beforeproceding.

2. Make sure that all users are logged out of the vault server.

3. From the Control Panel, double-click Administrative Tools and then double-click theServices icon.

4. Locate the SQL Server Agent (AUTODESKVAULT) service.

5. Right-click on the SQL Server Agent (AUTODESKVAULT) and select Properties.

6. Change the Startup Type to Automatic and start the service.

7. Open the Microsoft SQL Server Management Studio and connect to the

AutodeskVault Instance.

8. Right-click on the KnowledgeVaultMaster database and properties.


40/71


Rev. 1.1 - 37 -

9. On the Options tab, change the Recovery Model to Simple and change the AutoShrink drop-down list to False.

10. Perform these same steps for all of the Vault databases.

11. Expand the Management folder and select the Maintenance Plan folder.

12. Right-click on the Maintenance Plan folder and select Maintenance Plan Wizard.


41/71


Rev. 1.1 - 38 -

13. In the Select a Target Server dialog, set the server and login information.

14. In the Select Maintenance Task dialog, check the following options:


42/71


Rev. 1.1 - 39 -

15. In the Select Maintenance Task Order dialog, set the order to the following

16. In the Define Database Check Integrity Task dialog, select All user databases fromthe databases drop-down list and check the box next to Include Indexes.


43/71


Rev. 1.1 - 40 -

17. In the Define Rebuild Index Task dialog, select All user databases from theDatabases drop-down list.

18. In the Define Reorganize Index Task dialog, select the All user databases from theDatabases drop-down list.


44/71


Rev. 1.1 - 41 -

19. In the Define Shrink Database Task dialog, select All user databases from theDatabases drop-down list.

20. In the Define Update Statistics Task dialog, select the following options.


45/71


Rev. 1.1 - 42 -

21. In the Define Cleanup History Task dialog, select cleanup options as needed.

22. In the Select Plan Properties dialog, click Change.


46/71


Rev. 1.1 - 43 -

23. In the New Job Schedule dialog, set the plan to run after an ADMS Console backuphas been completed. Depending on the size of your databases, this schedule mayhave to be run on a different day and time of the week. You may want to run thistask on a Saturday to determine the amount of time it will take to complete and thendeside the best day and time to run this job on a regular basis.

24. In the Select Report Options dialog, specify the location for the maintenance reports.

25. Click Next and then Finish.

How to increase the timeout values on the ADMS server

As the vault database increases in size, you may have to modify some timeout values on theserver to allow for the server to process more data.

Increase the timeout values for client and server functions:

1. Open Windows Explorer and navigate to the C:\Program Files\Autodesk\DataManagement Server 2008\Server\Web\Services directory.

2. Create a backup copy of the Web.config file.

3. Open the Web.config file with Notepad and look for the following line:

Note: these values may be different, depending on the size of the vault and thespeed of the server it is installed on. Higher values may be necessary.

4. Save the Web.config file.

5. Open a command prompt and type IISRESET.


47/71


Rev. 1.1 - 44 -

Running Autodesk Data Management Server with SSL

Setting up the Autodesk Data Management Server to use SSL (Secure Socket Layer) is atwo step process.

1. On the DM Server machine, install the certificate and setup the website SSLpreferences.

2. Verify that the clients can communicate properly with SSL.

Configuring the DM Server machine

It is outside of the scope of this document to instruct you how to setup SSL under IIS. Formore information, visit the following web resources. Note that some steps may be differentdepending upon the version of Windows that you are currently using.

Obtaining Server Certificates -http://technet2.microsoft.com/WindowsServer/en/library/86120d58-f2c2-4a1b-8b70-8bee6a5227981033.mspx?pf=true

* When creating the certificate, you will need to specify the Common Name for yourweb site. If your Vault will be accessible from the Internet, use the FQDN (FullyQualified Domain Name) as the common name (ex. vault.abccorp.com). If you areconnecting internally only, you can use the computer name of the DM server as thecommon name.

Installing the Server Certificate -http://technet2.microsoft.com/WindowsServer/en/library/36d88d14-7dad-4168-a342-58aee9b536021033.mspx?pf=true

By default, the ADMS installer does not configure the AutodeskDM Virtual Directory to requireSSL. After the certificate has been installed on the Default Web Site, users are able to loginto the Autodesk Data Management Server using both secured and unsecured connections.

Unsecured logins can be accomplished by using localhost, 127.0.0.1, machine name or IPaddress in the server field of the login dialog.

Secured logins must use the common name to which the certificate was issued.

If Productstream Explorer (Webclient) is installed on the server, clients will need to access itfrom their web browser with https://servername/AutodeskDM/Webclient.
http://technet2.microsoft.com/WindowsServer/en/library/86120d58-f2c2-4a1b-8b70-8bee6a5227981033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/86120d58-f2c2-4a1b-8b70-8bee6a5227981033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/86120d58-f2c2-4a1b-8b70-8bee6a5227981033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/36d88d14-7dad-4168-a342-58aee9b536021033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/36d88d14-7dad-4168-a342-58aee9b536021033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/36d88d14-7dad-4168-a342-58aee9b536021033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/36d88d14-7dad-4168-a342-58aee9b536021033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/36d88d14-7dad-4168-a342-58aee9b536021033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/86120d58-f2c2-4a1b-8b70-8bee6a5227981033.mspx?pf=truehttp://technet2.microsoft.com/WindowsServer/en/library/86120d58-f2c2-4a1b-8b70-8bee6a5227981033.mspx?pf=true


48/71


Rev. 1.1 - 45 -

Configure the AutodeskDM Virtual Directory to require SSL Access

NOTE: The following procedure uses the Internet Information Services Manager to configurethe AutodeskDM Virtual Directory to require SSL for access.

1. Log into the computer hosting the Data Management Server as a local or domainadministrator.

2. From the Start Menu, select Settings > Control Panel.

3. Double-click Administrative Tools, and then double click Internet InformationServices.

4. Click Web Sites under your server name.

5. Select the Default Web Site and expand it. This web site must have the certificateyou created installed to it.

6. Right-click the AutodeskDM virtual directory and click Properties.

7. Select the Directory Security tab.

8. Click Edit under Secure Communications.

NOTE: If the View Certificate button is unavailable, the certificate that you createdhas not been installed on the AutodeskDM Virtual Directorys parent web site. Installa certificate before continuing with the rest of this process.

9. Click Require secure channel (SSL). Clients browsing to this directory must now useHTTPS.

10. Click OK.

11. Click OK.

12. If the Inheritance Overrides dialog is displayed, click Select All and then click OK.The new security settings are applied to all subdirectories of the AutodeskDM virtualdirectory.

13. Close the Internet Information Services Console.


49/71


Rev. 1.1 - 46 -

Configuring Client Machines

To verify that the SSL client/server communication is properly setup, open Internet Explorerand browse to https://. If the connection is not working, the Security Alertdialog box is displayed.

Follow the solutions below if the Security Alert dialog box contains one or more of thefollowing warnings:

1. The certificate is not from a trusted authority.

2. The date on the certificate is invalid.

3. The name on the certificate does not match the name of the site.

Solution 1 - Add the CA root certificate to the Trusted Root CertificationAuthority store on the client machine

1. Open an Internet Explorer window and browse to thehttps://machineName.
https://machinename/https://machinename/https://machinename/https://machinename/


50/71


Rev. 1.1 - 47 -

2. In the Security Alert dialog box, click View Certificate.

3. The Certificate dialog box describes the alert. If you trust this source, click InstallCertificateto launch the Certificate Import Wizard.


51/71


Rev. 1.1 - 48 -

4. In the Certificate Import Wizard, click Next. Click Place all certificates in thefollowing store and then click Browse and locate the Trusted Root CertificationAuthorities node.

5. Click Next and then Finish.

6. A dialog box is displayed indicating the certificate is successfully imported. Click OK.

7. Open Internet Explorer and go to Tools > Internet Options > Content tab.


52/71


Rev. 1.1 - 49 -

8. Click Certificates.

9. Select the Trusted Root Certification Authority tab and then locate the certificateissued to the server. If it is present, click Close.


53/71


Rev. 1.1 - 50 -

Solution 2 - Check the expiration date of the certificate

1. In the Security Alert dialog box, click View Certificate.

2. If the Valid from date range has expired or is not valid yet, contact your ITdepartment and notify the Web Server Administrator that the certificate has expiredand a new certificate request and installation from the Certificate Authorities are

needed.

Solution 3 - Verify the certificate name matches the name of the site

1. Ask your Web Server Administrator for the exact certificate name issued for the DMServer. Try the newly provided name again usinghttps://newServerNameand if thatdoes not raise the Security Alert message box, then use the new name in the VEclient applications login dialog when logging in securely to the DM Server.

When you have ensured that client web service requests/responses have clear passage toand from the server, you can log in from a client application using SSL.
https://newservername/https://newservername/https://newservername/https://newservername/


54/71


Rev. 1.1 - 51 -

Login from client applications using SSL

1. In the Log in dialog box, enter your user name, password, and the name of thedatabase.

2. For the name of the server, specify the machine name of the server with the prefix:https://. For example:

If you are using the default SSL port 443: https:// ServerName

If you are using a different SSL port: https://ServerName:XXX whereXXX is the SSL communication port number.

NOTE:The secured login depends on the certificate issued to the server machine. If it isissued for the machine name, then only https://ServerNamewill work. Otherwise, if thecertificate is issued for a dedicated IP, then onlyhttps://serverIPAddresswill work as a securevault login.
https://servername/https://servername/https://serveripaddress/https://serveripaddress/https://serveripaddress/https://serveripaddress/https://servername/


55/71


Rev. 1.1 - 52 -

Using Vault with a Proxy Server

This section describes setting up a proxy to enable successful Autodesk Client/Server datacommunication.

If a client machine connects to the web server through a proxy server, then all calls to theAutodesk Data Management Server from any Autodesk client will fail. To have a successfulAutodesk Client/Server communication, you need to bypass the proxy server.

Change the proxy settings in Internet Explorer 6.x

1. Open Internet Explorer.

2. From the Tools menu, select Internet Options.

3. Select the Connections tab.

4. Click LAN Settings.

5. If the "Use a proxy server for your LAN" check box is enabled, turn on the Bypassproxy server for local addresses check box.

6. Click the Advanced button next to the Port field.7. In the Proxy Setting dialog, add the server name and IP address into the Exceptions

field.

8. Click OK.

9. Click OK.

10. Click OK to close Internet Options.

All addresses without a period, for example: http://webserver, will bypass the proxy and beresolved directly.

If Internet Explorer continues to connect to the assigned HTTP proxy server, then the HTTP

proxy address may contain a period. If this happens, configure the proxy server to use a hostname.

Configure the proxy server to use a host name

1. Follow steps 1-5 above for changing the proxy settings in Internet Explorer.

2. If the Address field is http://webserver.domainname.com orhttp://10.0.0.1, thenchange it to http://webserver only.

3. Click OK and close Internet Explorer Options.

For more information on advanced proxy bypass configurations:

Read Microsoft Knowledge Base article 262981: "Internet Explorer Uses ProxyServer for Local IP Address Even if the 'Bypass Proxy Server for Local Addresses'Option Is Turned On"

Read the Microsoft document Working with Proxy Servers(http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asp)
http://webserver.domainname.com/http://webserver.domainname.com/http://webserver.domainname.com/http://10.0.0.1/http://10.0.0.1/http://10.0.0.1/http://webserver/http://webserver/http://webserver/http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/ierk/Ch13_d.asphttp://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://support.microsoft.com/default.aspx?scid=kb;en-us;262981http://webserver/http://10.0.0.1/http://webserver.domainname.com/


56/71


Rev. 1.1 - 53 -

Autodesk Data Management Server Log Files

This section shows you where to find the various log files and other files used fortroubleshooting potential problems with Autodesk Vault or Autodesk Productstream.

For the purposes of this section, we refer to the %temp% folder. This is the temp folder

location defined for the Windows user account that is logged in on the computer. By default,this folder is located in the following location:

C:\Documents and Settings\ACCOUNTNAME\Local Settings\Temp

In this example, ACCOUNTNAME is the name of your user account in Windows.

Autodesk Data Management Server (ADMS) 2008 installation log files

During the installation of ADMS there may be errors reported the by the diagnostic tool orduring the installation itself. These errors are recorded in log files.

Pre-check log:

%temp%Prechecks.xmlPrechecks.xsl

Autodesk Productstream 2008 client installation logs:

%temp%Autodesk Productstream 2008 Install.logAutodesk Productstream 2008 Setup.log

Autodesk Vault 2008 client installation logs:

%temp%Autodesk Vault 2008 Install.logAutodesk Vault 2008 Setup.log

Autodesk Data Management Server 5 installation logs:

%temp%Autodesk Data Management Server 2008 (Vault or Productstream).log

Productstream Explorer installation logs:

%temp%Autodesk Productstream Explorer 2008 Install.logAutodesk Productstream Explorer 2008 Setup.log

Autodesk Server Diagnostic Tool Log files

If you run the Autodesk Server Diagnostic Tool, the log files are located in the%temp%\EDMLog directory.

Autodesk Server Diagnostic Tool:

%temp%\EDMLogDiagTool.xmlDiagToolLog.xsl


57/71


Rev. 1.1 - 54 -

Vault server log files

There are primarily two different log files to look for in this location. Each of these is describedin full detail below.

Folder location and file names:

Microsoft Visa - c:\ProgramData\Autodesk\VaultServer\Filestore

Microsoft Windows XP and 2000 - C:\Documents and Settings\All Users\ApplicationData\Autodesk\VaultServer\FileStore

Vlog-YYYYMMDD.txt

Any server-side problems relevant to Check-in, Check-out, Get Latest Version, Undo Check-out, Advanced Search and other operations performed from within Vault Explorer or one ofthe supported product add-ins are written into these log files.

ADMSConsoleLog-YYYYMMDD.txtAny server-side problems relevant to backup, restore, re-index, purge or other operationsperformed within ADMS Console are written into these logs.

Microsoft SQL Server log files


C:\Program Files\Microsoft SQL Server\MSSQL$AUTODESKVAULT\LOG

Errorlog

Errorlog.1

Errorlog.2

Errorlog.3

The SQL logs are named sequentially with the most recent (current) file being named errorlogfollowed by errorlog.1 then errorlog.2 and so on.

DWG and DWF iFilter Log files

There are log files maintained by the various iFilters used when performing some Vaultoperations like re-index. These log files can be helpful when troubleshooting problems withblock attributes or properties not indexing as expected in Vault Explorer.


C:\Documents and Settings\ComputerName\ASPNET\Local Settings\Temp

DWFFilt.*.log

DWGFilt.*.log


58/71


Rev. 1.1 - 55 -

Indexing Block Attributes (DWG files)

When troubleshooting problems with DWG block attributes not indexing in a vault, you'll alsowant to find the FilterConfig.xml. This file is created when you index block attributes in theADMS Console and is found in the following location:

Folder location and file name:

C:\Program Files\Autodesk\Data Management Server 2008\Server\Web\Services

FilterConfig.xml


59/71


Rev. 1.1 - 56 -

Customize W3C Extended Logging

The W3C Extended log file format is the default log file format for IIS. It is a customizableASCII text-based format. You can use IIS Manager to select which fields to include in the logfile.[W3C Extended Log File Format]

1. From the Windows Start menu, select Control Panel > Administrative Tools > InternetInformation Services

2. In IIS Manager, expand the local computer, expand the Web Sites folder, right-clickthe Default Web site, and click Properties.

3. On the Web Site tab, select the Enable logging check box (if it is not alreadyselected).
http://technet2.microsoft.com/WindowsServer/en/Library/c9ae63eb-24da-4f19-80b9-2610b4e6dcab1033.mspxhttp://technet2.microsoft.com/WindowsServer/en/Library/c9ae63eb-24da-4f19-80b9-2610b4e6dcab1033.mspxhttp://technet2.microsoft.com/WindowsServer/en/Library/c9ae63eb-24da-4f19-80b9-2610b4e6dcab1033.mspxhttp://technet2.microsoft.com/WindowsServer/en/Library/c9ae63eb-24da-4f19-80b9-2610b4e6dcab1033.mspx


60/71


Rev. 1.1 - 57 -

4. In the Active log format drop-down list, select W3C Extended Log File Format andclick the Properties button.

(BEFORE)

NOTE: Before changing the extended properties, write down or take snapshots(Alt+PrintScrn) of currently selected W3C properties in case of wanting to go back to theoriginal state in the future.

5. On the Advanced tab (for Windows 2003 server) or Extended Propertiestab (forWindows XP), select logging ALL properties.

(AFTER)

6. Click OK and close IIS Manager.


61/71


Rev. 1.1 - 58 -

7. From the Windows Start menu, select Run. Type: iisreset and then click OK to restartIIS.

8. IIS logs are located in the following directories:

a. C:\WINDOWS\system32\LogFiles\W3SVC1 for the Default Web sitecommunication.

b. C:\WINDOWS\system32\LogFiles\HTTPERR for IIS errors logs.


62/71


Rev. 1.1 - 59 -

Troubleshooting ASP Pre-Check failures.

During this check, the ADMS installation is performing several tasks to check IIS and ASPprior to installation.

The pre-check installs a TestASP virtual directory in IIS and expects a return string. If itdoesnt get this string, the most common error returned is the Client found response contenttype of text/html".

The most common technical solutions used to fix this error are:

http://usa.autodesk.com/getdoc/id=TS1058061






Quick solutions:

Enable ASP .Net v2.0.50727 in the IIS Web Extensions

1. Open IIS Manager.

2. Select the Web Extensions folder in the right pane.

3. Set ASP .Net v2.0.50727 to Allowed.

Reset ASP .Net inside of IIS.Note: Do not perform these steps if you have another IIS application that uses a differentversion of the .Net Framework.

1. Open a command prompt.

2. Navigate to the %SYSTEMROOT%\Microsoft.Net\Framework\v2.0.50727 directory.

3. Type aspnet_regiis.exe i and press Enter.

4. After this is complete, perform an IISRESET from a command prompt and restart thepre-checks.

Reset ASP .Net inside of IIS on a specific web site.

1. Open a command prompt.

2. Navigate to the %SYSTEMROOT%\Microsoft.Net\Framework\v2.0.50727 directory.
http://usa.autodesk.com/getdoc/id=TS1058061http://usa.autodesk.com/getdoc/id=TS1058061http://usa.autodesk.com/getdoc/id=TS1054666http://usa.autodesk.com/getdoc/id=TS1054666http://usa.autodesk.com/getdoc/id=TS1056821http://usa.autodesk.com/getdoc/id=TS1056821http://usa.autodesk.com/getdoc/id=TS1051865http://usa.autodesk.com/getdoc/id=TS1051865http://usa.autodesk.com/getdoc/id=TS1068569http://usa.autodesk.com/getdoc/id=TS1068569http://usa.autodesk.com/getdoc/id=TS1069754http://usa.autodesk.com/getdoc/id=TS1069754http://usa.autodesk.com/getdoc/id=TS1069754http://usa.autodesk.com/getdoc/id=TS1068569http://usa.autodesk.com/getdoc/id=TS1051865http://usa.autodesk.com/getdoc/id=TS1056821http://usa.autodesk.com/getdoc/id=TS1054666http://usa.autodesk.com/getdoc/id=TS1058061


63/71


Rev. 1.1 - 60 -

3. Type aspnet_regiis.exe s W3SVC/#/ROOT and press Enter.Replace # with the web site Identifier that is found in the IIS Manager.

4. After this is complete, perform an IISRESET from a command prompt and restart thepre-checks.

Verify that ASP .Net v2.0.50727 is set for the Default Web Site.

1. Open the IIS Manager.

2. Expand the Web Sites folder

3. Right-click on the Default Web Site and select properties.

4. Go to the ASP .Net tab. (Note: this tab will not exist if ASP .Net 2.0 isnt installed.)

5. Make sure that ASP .Net v2.0.50727 is selected in the drop-down list.

6. If you change this setting, close the IIS Manager and perform an IISRESET from acommand prompt and restart the pre-checks.

Verify that another applications web.config file doesnt exist in the root of the Default WebSite.

1. Open the IIS Manager.

2. Expand the Web Sites folder.

3. Expand the Default Web site.

4. Check to see if a web.config file exists.

5. If it does exist, open Windows Explorer and go to the c:\inetpub\wwwroot directory, orwhere ever the root directory of the Default Web Site exists.

6. Rename the web.config file to a temporary file.

7. Re-run the pre-checks.


64/71


Rev. 1.1 - 61 -

Troubleshooting

1. Leave the pre-checks open with the error.

2. Open the IIS Manager and expand the Web Sites folder.

3. Open the Default Web Sites folder.

4. Look for a virtual directory called TestASP and select it.

5. In the right pane you will find a TestASPNet.asmx file. Right-click on the file andselect Browse.

6. An error dialog will appear. You should expect a web page with TestReturnString linkat the top.

7. Troubleshoot the error message or IIS error code.http://support.microsoft.com/default.aspx?scid=kb;en-us;318380

Common 29001 Errors

The error code 29001 is a generic message and can be attached to several different issues.When receiving this error it is important to read the full message that is displayed. This

information is what differentiates the errors.Technical solutions are currently available at theKnowledge Baseas the following:

TS1056747Vault Management Error: The operation has timed out.

TS1055799Vault management error: System.Web.Services.Protocols.SoapException: 130.

TS1054362Vault management error: Server was unable to process request. -->BadAuthenticationToken --> Performance Counters Not Registered!.

TS1051757Vault management error: Configuration Error.

TS1054666Vault management error. Failed to create file.

TS1054663Vault management error: Server was unable to process request.

TS1050262During installation of Autodesk Data Management Server 4.TS1052161Vault management error: Server Unavailable.

TS1056769 Unable to read data from the transport connection.

TS1053311Vault management error: The request failed with HTTP status 403: Forbidden.

TS1058339Vault Management Insufficient File permissions.

TS1058133Password Validation Failed, the password does not meet WindowsRequirements.
http://support.microsoft.com/default.aspx?scid=kb;en-us;318380http://support.microsoft.com/default.aspx?scid=kb;en-us;318380http://support.autodesk.com/enu/Homepage.asphttp://support.autodesk.com/enu/Homepage.asphttp://support.autodesk.com/enu/Homepage.asphttp://usa.autodesk.com/getdoc/id=TS1056747http://usa.autodesk.com/getdoc/id=TS1056747http://usa.autodesk.com/getdoc/id=TS1055799http://usa.autodesk.com/getdoc/id=TS1055799http://usa.autodesk.com/getdoc/id=TS1054362http://usa.autodesk.com/getdoc/id=TS1054362http://usa.autodesk.com/getdoc/id=TS1051757http://usa.autodesk.com/getdoc/id=TS1051757http://usa.autodesk.com/getdoc/id=TS1054666http://usa.autodesk.com/getdoc/id=TS1054666http://usa.autodesk.com/getdoc/id=TS1054663http://usa.autodesk.com/getdoc/id=TS1054663http://usa.autodesk.com/getdoc/id=TS1050262http://usa.autodesk.com/getdoc/id=TS1050262http://usa.autodesk.com/getdoc/id=TS1052161http://usa.autodesk.com/getdoc/id=TS1052161http://usa.autodesk.com/getdoc/id=TS1056769http://usa.autodesk.com/getdoc/id=TS1053311http://usa.autodesk.com/getdoc/id=TS1053311http://usa.autodesk.com/getdoc/id=TS1058339http://usa.autodesk.com/getdoc/id=TS1058339http://usa.autodesk.com/getdoc/id=TS1058133http://usa.autodesk.com/getdoc/id=TS1058133http://usa.autodesk.com/getdoc/id=TS1058133http://usa.autodesk.com/getdoc/id=TS1058339http://usa.autodesk.com/getdoc/id=TS1053311http://usa.autodesk.com/getdoc/id=TS1056769http://usa.autodesk.com/getdoc/id=TS1052161http://usa.autodesk.com/getdoc/id=TS1050262http://usa.autodesk.com/getdoc/id=TS1054663http://usa.autodesk.com/getdoc/id=TS1054666http://usa.autodesk.com/getdoc/id=TS1051757http://usa.autodesk.com/getdoc/id=TS1054362http://usa.autodesk.com/getdoc/id=TS1055799http://usa.autodesk.com/getdoc/id=TS1056747http://support.autodesk.com/enu/Homepage.asphttp://support.microsoft.com/default.aspx?scid=kb;en-us;318380


65/71


Rev. 1.1 - 62 -

Productstream Replication

This section addresses topics specifically related to the unique environments associated withreplicating data to multiple work sites.

Scalability of Replication

Productstream Replication uses a single database for all sites and replicates the file store toeach location. This architecture has distinct advantages in ease of implementation, end userexperience and the instantaneous nature of the information availability. This architecture isnot suited to multiple sites that are distributed over great distances or poor networks. It isrecommended that the replication environments are not distributed across multiplecontinents.

If you are unsure of the appropriateness of Productstream Replication in your environmentyou can easily estimate the performance. The performance can be gauged between tworemote sites by browsing a network share between the sites. If the responsiveness of theremote share is deemed acceptable for daily access Productstream Replication will also beacceptable. Productstream and Vault communicate via http which is more efficient than thedefault windows system which is observed when browsing a remote share.


66/71


Rev. 1.1 - 63 -

Content Center in a Replicated Environment

Introduction

Autodesk Inventor Standard Content is delivered in the form of library databases that arehosted by the Autodesk Data Management Server (ADMS). Users access these librarydatabases through Inventor to automatically create selected library components as Inventor

part files. Once instanced these components are stored in a folder defined by the Inventorproject file. When the assembly is then checked into Vault, the instanced Contentcomponents are also checked into Vault.

In a Replicated Autodesk Vault or Productstream environment we can tune the performanceof Content Center by altering the configuration of the Inventor project file. There are twobasic methods for which we can configure the Content folder; first is a local Content folder oneach client computer. Second is a shared Content folder for each geographical workgroup.

Assumptions

The following examples assume all software including the Content has been installed. Theseexamples also assume the reader has a functional understanding of how Content isinstantiated and referenced. If required please reference the Content Center help files.

The diagrams below show the SQL server as a separate computer for clarity. SQL Servermay be on a separate computer or on the ADMS, either case is supported and has no impacton the workflows detailed in this document.

Private Content Center Folder

The default configuration when using Inventor is for each client to have a private Contentfolder.

Advantages:

Suitable for assemblies that have a high volume of Content components byeliminating network traffic for existing local components.

Allows each user to have only the content they use in their Private Content Folder.

Disadvantages:

Consumes considerable disk space on the client

Each client must instantiate each referenced component in their Private ContentFolder


67/71


Rev. 1.1 - 64 -

Private Content Example

1. Client 1 creates an instance of a component from the Content Center database. Theinstanced part file is written to the Private Content Center folder located on the clientcomputer.

2. User checks in the instanced component as part of an assembly. The Content part iscopied into the Vault file store.

Note: Keeping the part file in the local folder will remove the delays, for this user, dueto instancing the part file or copying it from the file store.

3. Client 2 inserts the same component that Client 1 used. Since the part does not yetexist in the Private Content Center Folder for Client 2 it must be instanced from thedatabase.

4. Once instanced the assembly may be checked into Vault. Vault knows that thiscomponent already exists and will resolve the assembly with the existing component

in the file store.

5. During the scheduled replication at each ADMS the Content components will becopied to the local file store at each site.

6. Client 3 inserts the same component that Client 1 & 2 have previously used. Thecomponent must be instanced from the remote database. This is the same processas Client 2 in step 3 but the instantiation delay may be increased based upon thedistance and network latency between the client and the SQL Server.


68/71


69/71


Rev. 1.1 - 66 -

Note: Keeping this part in the shared folder will remove the delay, for all users at thatsite, due to instancing the part file.

4. Client 3 inserts the same component; it must be instanced once to create the file in

the Shared Content Center Folder at Site 2.

Seeding the Content Center Folders

The re-instancing of existing components can be avoided byperforming a Get Entire Folder from Vault Explorer orProductstream. This will seed the Content Center Folder withall instanced Content that has been checked into the Vault.This applies to both the Private and Shared Content CenterFolders. In environments where new content is createdfrequently it may be advantages to perform this operation onregular basis.

Configuring a Shared Content Center Folder

There are two methods to configure a Shared Content Center Folder. The first method is touse a mapped drive set to a local path for the users in each site. The second method requires

a unique project file for each geographical site.

Mapped Drive

Advantages:

One project file that is easy to update.

Disadvantages:

Every client using content must have the correct network path configured as a

mapped drive. This can be done manually on each client or pushed to the clients as

a policy.

Configure a single project file with the standard mapped Content Center Path. Then for eachclient at each site use the same share name to reference the site specific shared contentcenter folder. As an example in the project file well set the path: Content Center Files = W:\.

Next each client must create a share to the site specific shared folder using the samemapping. If we have two offices each site should have a local shared folder and all Inventorusers at each site must have the local share mapped:

New York W:\ =\\New123456\CCShare\

London W:\ =\\Lon123456\ContentShare\
http://new123456/CCShare/http://new123456/CCShare/http://new123456/CCShare/http://lon123456/ContentShare/http://lon123456/ContentShare/http://lon123456/ContentShare/http://lon123456/ContentShare/http://new123456/CCShare/


70/71


Rev. 1.1 - 67 -

Site Specific Project File

Advantages:

No client side configuration

Disadvantages:

Unique project file for each site. This can impose additional administrative overheadwhen ipj files require updates.

Create the first project file then make a copy for each site. Rename each copy to correspondwith the site names and modify the Content Center Files path to the shared content path.

As an example the site in New York might have a project file named: NewYork.ipj and theshared content folder is:\\New123456\CCShare\shown here:

All users in the New York site should use this project file. Users at another site would use aproject file where the Content Center Files path is set to the shared content path for that site.
http://new123456/CCShare/http://new123456/CCShare/http://new123456/CCShare/http://new123456/CCShare/


71/71


Revision History

Revision Coments Date

1.0 Initial Release May 7, 2007

1.1 Replaced image on page 37 step 9 May 8, 2007