SolidWorks Corporation 300 Baker Ave, Concord MA 01742, USA 1-800-693-9000 (US and Canada) +1-978-371-5011 (Outside the US and Canada) www.solidworks.com

1995-2006, SolidWorks Corporation 300 Baker Avenue Concord, Massachusetts 01742 USA All Rights Reserved U.S. Patents 5,815,154; 6,219,049; 6,219,055; 6,603,486; 6,611,725; 6,844,877; 6,898,560; 6,906,712 and certain other foreign patents, including EP 1,116,190 and JP 3,517,643. U.S. and foreign patents pending. SolidWorks Corporation is a Dassault Systemes S.A. (Nasdaq:DASTY) company. The information and the software discussed in this document are subject to change without notice and should not be considered commitments by SolidWorks Corporation. No material may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose without the express written permission of SolidWorks Corporation. The software discussed in this document is furnished under a license and may be used or copied only in accordance with the terms of this license. All warranties given by SolidWorks Corporation as to the software and documentation are set forth in the SolidWorks Corporation License and Subscription Service Agreement, and nothing stated in, or implied by, this document or its contents shall be considered or deemed a modification or amendment of such warranties. SolidWorks, PDMWorks, 3D PartStream.NET, 3D ContentCentral, eDrawings, and the eDrawings logo are registered trademarks of SolidWorks Corporation, and FeatureManager is a jointly owned registered trademark of SolidWorks Corporation. SolidWorks 2007 is a product name of SolidWorks Corporation. COSMOSXpress, DWGeditor, DWGgateway, Feature Palette, PhotoWorks, and XchangeWorks are trademarks of SolidWorks Corporation. COSMOS and COSMOSWorks are registered trademarks, and COSMOSMotion and COSMOSFloWorks are trademarks of Structural Research & Analysis Corporation. FeatureWorks is a registered trademark of Geometric Software Solutions Co. Limited. ACIS is a registered trademark of Spatial Corporation. GLOBEtrotter and FLEXlm are registered trademarks of Globetrotter Software, Inc. Other brand or product names are trademarks or registered trademarks of their respective holders. COMMERCIAL COMPUTER SOFTWARE - PROPRIETARY U.S. Government Restricted Rights. Use, duplication, or disclosure by the government is subject to restrictions as set forth in FAR 52.227-19 (Commercial Computer Software - Restricted Rights), DFARS 227.7202 (Commercial Computer Software and Commercial Computer Software Documentation), and in the license agreement, as applicable. Contractor/Manufacturer: SolidWorks Corporation, 300 Baker Avenue, Concord, Massachusetts 01742 USA Portions of this software 1999, 2002-2006 ComponentOne Portions of this software 1990-2006 D-Cubed Limited. Portions of this product are distributed under license from DC Micro Development, Copyright 1994-2006 DC Micro Development, Inc. All rights reserved Portions of this software 1998-2006 Geometric Software Solutions Co. Limited. Portions of this software are 1997-2002 Macromedia, Inc. Portions of this software 1986-2006 mental images GmbH & Co. KG Portions of this software 1996-2006 Microsoft Corporation. All Rights Reserved. MoldflowXpress is 2005 Moldflow Corporation. MoldflowXpress is covered by US Patent No. 6,096,088 and Australian Patent No. 721978.

iii

Table of contents Replication overview................................................................................................................... 1 Setting up a replicated file vault ................................................................................................... 3

Requirements ......................................................................................................................... 3 Step 1 Install PDMWorks Enterprise and set up the file vault....................................................... 3 Step 2 Set up file vault replication .......................................................................................... 4 Step 3 Configure the replication settings................................................................................ 10 Testing the replication connection............................................................................................ 11

On-demand replication.............................................................................................................. 17 What are file archives?........................................................................................................... 17 How does it work?................................................................................................................. 18

Scheduled replication................................................................................................................ 22 Replication performance setting .............................................................................................. 29

Archive replication status .......................................................................................................... 31 Show which file archives are not yet replicated.......................................................................... 32 Show which server has a file version replicated ......................................................................... 32

Archive server login selection..................................................................................................... 33 Troubleshooting the replication setup .......................................................................................... 35

Prerequisites ........................................................................................................................ 36 Collect logs and registry settings ............................................................................................. 37

1

Replication overview

PDMWorks Enterprise uses a database server and an archive server for hosting central data about files and activities in a PDMWorks Enterprise file vault. When a client connects to a PDMWorks Enterprise file vault through the file vault view and browses for files, views file data cards, searches for files, etc., the information is sent between the client and the database server. When a client retrieves physical files stored in a file vault (for example, drawings, documents, etc.) from the archive to the local file vault view (cache) by using functions such as Get or Check out, the files are retrieved from the archive server and sent to the client. The time it takes to transfer these files depends on the size and speed of the network. In a LAN environment, the files are normally transferred quickly since the archive server resides locally to the clients. If the PDMWorks Enterprise file vault is shared between multiple offices over a WAN connection, the performance will decrease and relies heavily on the speed of the connection. Both the information from the database server (which is speedy since only small text data is sent) and the physical files (which can take anywhere from seconds to hours depending on file size) are transferred over the WAN. The following image depicts a typical PDMWorks Enterprise WAN environment where all three offices communicate with the central PDMWorks Enterprise database server and archive server.

2

By using the file vault replication feature in PDMWorks Enterprise, you can balance the amount of data that is transferred over a slow WAN connection by setting up a local archive servers in each office, hosting a replicated copy of the file vault archive. When clients in each office work in the file vault, the information is still sent from the central database server, but the physical files are now retrieved from the closest archive server hosting a copy of the archived file. If the file archive has already been replicated, the file will be retrieved from the local archive server in the WAN office. If the file has been added to an archive server in another office and has not yet been replicated to the local archive server, the file archive will be automatically replicated when the file is initially retrieved by a client so that the archived file is accessible on the local archive server to all other clients in the same office. The following image shows a PDMWorks Enterprise environment where each office communicates with the central database server and, in addition, has a local archive server hosting a replicated copy of the file vault archive.

3

Setting up a replicated file vault

The section describes how to set up and replicate a new file vault between two offices. You can replicate an existing file vault at any time by using the same procedures. In these instructions, Office A represents the main office hosting the SQL server and archive server Archiveserver, and Office B represents the second office hosting only a second archive server Server2. The two archive servers will host a replicated copy of the file vault archive. Requirements A central SQL server hosting the file vault database must be accessible from clients in both offices. If

the offices are connected over a WAN, the default TCP port 1433 for SQL communication must be fully opened both ways through any firewalls, preferably using a VPN connection for security.

Each office hosting a replicated vault must have a server (or workstation) with sufficient hard drive space to store the complete or parts of the replicated file vault archive and to host the PDMWorks Enterprise archive server software. If WAN communication is used, open the default TCP port 3030 between each archive server system and default TCP port 1433 to the SQL server.

If Windows login type is used for the vault, ensure that both offices have access to the domain users. Step 1 Install PDMWorks Enterprise and set up the file vault In Office A NOTE: This is the main office server hosting both the central SQL file vault database and file vault archive. 1. Install the SQL server, the PDMWorks Enterprise database server, and the PDMWorks Enterprise

archive server software. IMPORTANT: Make sure that the archive server TCP port 3030 and SQL server TCP port 1433 is opened in any firewall between office A and B.

2. Install one or more PDMWorks Enterprise client workstations. 3. From a PDMWorks Enterprise client, use the administration tool to connect to the archive server to

create a new file vault and configure it.

4. On the remaining clients, use the view setup wizard and create a vault view to the new file vault on

the local archive server (Archiveserver).

4

In Office B NOTE: Because this office will host a replicated copy of the file vault archive, you only need to install the PDMWorks Enterprise archive server software. You do not need to install an additional SQL server. 1. Install the PDMWorks Enterprise archive server on a system; use the same default settings as defined

for the archive server in Office A. NOTE: You must provide the same SQL user and password credentials as used in the main office (typically the sa account). IMPORTANT: Make sure that the TCP port 3030 is opened in any firewall between office B and A.

2. Install one or more PDMWorks Enterprise client workstations.

3. Do not create file vault views on the clients in Office B because the vault has not yet been replicated. Step 2 Set up file vault replication

In Office A 1. From a PDMWorks Enterprise client, start the PDMWorks Enterprise administration tool. 2. Connect to the second archive server by selecting File, Add Server.

3. Select the archive server name in Office B from the list. If the server is located on a WAN and the broadcast protocol is not configured, the archive server might not show up in the list. If so, type the system name of the archive server. Click OK.

NOTE: The remote archive server (in Office B) must be running and the archive server port (TCP port 3030) must be opened in order for this connection to work. If the remote archive server is not running or connection is blocked, the following error will show:

5

4. When prompted, log in as a Windows user account that is included in the Attach or Administrative access section in the archive server security settings (the local administrator on the remote archive server system is included there by default).

NOTE: You can verify this setting by viewing the Security tab in the default settings in the archive server configuration.

5. The attached server will now show up in the administration tool. Right-click the archive server (Server2) and select Add replicated vault.

6

6. If prompted, log in as a Windows user who is included in the Administrative access section in the archive server security settings (the local administrator on the remote archive server is included there by default).

NOTE: You can verify this setting by viewing the Security tab in the default settings in the archive server configuration.

7

7. The replication wizard starts. Click Next.

8. Select the first archive server (Archiveserver) in Office A that currently hosts the file vault archive

in the list. Click Next.

8

9. Select the file vault that you want to replicate. Click Next.

10. Log into the file vault as the PDMWorks Enterprise Admin user or as a user who has permission to replicate vaults (Admin has this permission by default).

11. Select a root folder on the target archive server (Server2) where the replicated file vault archive

should be placed (typically the root folder is identified as Archives). Click Finish.

9

12. The replication wizard will now create settings and archive folders on the second server. NOTE: This step only creates empty folders for the replicated archive. If the file vault contains files, these have not yet been replicated.

13. The file vault that has been replicated will now show up under both archive servers in the

administration tool.

NOTE: A replicated vault still uses only one centrally shared SQL database, so both vault nodes are identical and you can administer any of them. The difference is that it will use the login/security settings of the archive server that host the vault node you are expanding and logging in to.

14. The replication settings dialog will try to open up in the vault node under the remote archive server.

A vault login may show, log in as a user that has permission to manage vault replication (Admin has this permission by default). This initial login will actually trigger a replication of vault security settings (admin password, login

type etc.) from the initial archive server in Office A to the remote archive server in Office B.

10

If the login fails, replication from Office A to Office B is being prevented for some reason. The following warning will show if port 3030 is blocked to the archive server in Office A:

If the port is open and you know that the remote server in Office B can reach the server in Office

A correctly restart the administration tool and try logging in to the vault node under the remote archive server again. If it still fails, log in to the vault node under the first archive server (in Office A) instead and then use the test option in the replication settings dialog to troubleshoot the failure (see more below)

15. If the login succeeded, the replication settings dialog will show, listing the server names and

addresses hosting the replicated vault. By default, the archive server system names are used as connection address.

Step 3 Configure the replication settings If you want to change any of the default replication settings, select a row in the Connections list and modify the appropriate option.

11

Test Mark the Test checkbox and then press the Test button to test the replication connection from the Source server to the Target server.

Source Server Address

You must enter a valid DNS system name or IP address that the Target Server can use to communicate with Source Server. In a WAN environment, you should use the IP address here. The archive servers will communicate over TCP port 3030, so make sure that port is fully opened in any firewall between the servers.

Speed The speed option is used to balance the replication load between three or more servers. Server connections with a higher speed rating will take priority over servers with a lower speed rating. If replicating between two servers, it is recommended to select the highest speed rating (10 Mbit) regardless of real connection speed. The speed setting does not affect the actual replication transfer speed in any way, only priority. For example, if a file version is replicated on 2 servers and a third server requests that file version for replication since it exists on both remote servers, the connection that has the highest speed setting defined will be prioritized.

The servers are now configured for on-demand replication. This means that a file added by a client attached to the first archive server (in Office A) can be retrieved by a client attached to the second archive server (in Office B) and at the same time have the file archive replicated to that server. To set up a scheduled recurring replication you must configure a replication schema. You can now create file vault views in Office B (to the local archive server that is now hosting a replicated copy of the vault archives) Testing the replication connection To test that replication works correctly between two archive servers, you can use the connection test option.

12

1. Mark the checkbox in the Test column for the connections you wish to test.

2. Press the Test button.

If the button is grayed out you have made some changes in the replication settings that require saving. Saving the settings will enable the Test button again.

If you make changes to the Source Server address, please wait a short period before using the test button to allow the changed address to be updated and used on the target server. If you run the test too quickly after updating the name, the target server might still use the old address in the connection test.

Note that any changes made to the source server address will be updated to the target server via the PDMWorks Enterprise database server service. If your changes to the source server address do not take effect, verify that the database server service works correctly and can connect to the target server. If the database server service is not working correctly, restarting the archive server service on the target server will force a reload of the updated source server name as well.

3. The Test Connections dialog will show which connections will be tested. Press the Test button to

run the replication test. This will trigger an on-demand replication from the Source server to the target server. If the connection is configured correctly, the result column will return Test successful.

NOTE: If the replication connections are blocked or not working, the test can take some time to complete or time out. Wait until you get a result.

Failed connection test If the connection test does not return a successful result, something is incorrectly configured for replication to work between the two archive servers. Refer to the troubleshooting section for tips on how to diagnose the problem.

13

NOTE: If a connection returns a failed test result, no file archives can be replicated from the source server to the target server for that specific connection. The most common reasons a replication connection fails between two systems are:

Blocked TCP port 3030 on the source server verify the archive server port is open. Failed DNS name lookup from the target server to the source server using the source server

address verify that the server can be reached by ping command. Database server service not running verify that the database server service is started and can

reach the target servers by name over TCP port 3030. Any changes to the source server address in the replication settings will not take effect if the database server service is not working correctly. Restarting the archive server service on the target server will force a reload of the updated address.

The following are some of the warnings that may show when a replication test fails: Test result when incorrect source server address is used:

The target archive server log contains information about the incorrect address used as well:

14

Test result when the archive server service on the source server is not running, or if the archive

server TCP port 3030 is not open on the source server:

The target archive server log contains information about the address and port used as well:

15

Test result when the archive server service on the target server is not running, or if the archive

server TCP port 3030 is not open on the target server:

Test result when the installed archive server software on the source server is not of same version as

on the target server:

16

The target archive server log contains information about the address and port used as well:

17

On-demand replication

When two or more archive servers are replicating a file vault, all versions of a file stored in that file vault will be available to each archive server using so called on-demand replication. On-demand replication is always in effect allowing a file archive that is not yet replicated to the archive server to be replicated (i.e. copied) when the file is requested by a client connected to that archive server. The on-demand replication will always allow clients to be able to retrieve a file, regardless if its file archive is available on the local archive server or not. What are file archives? All files in a PDMWorks Enterprise file vault have their own file archive folder (file store) that is managed by the archive server service. Inside each file archive folder, all versions of a file are stored. The files are not stored using the same folder structure as seen by a user in a file vault view, but instead uses hexadecimal ID names that are maintained in the file vault database. It is these archive folders that are replicated between the archive servers when a file vault is using replication. The file vault archive folder contains 16 subfolders (named 0-F), where each file in the vault is assigned a unique archive folder. To find the archive folder of a file vault, check the following registry key on the archive server: HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\Vaults\VAULTNAME\ArchiveTable The following image shows an example of a file archive:

The following files can usually be found in an archive folder:

*.sldprt The latest version of a file is stored uncompressed with a version number (00000006) and a file extension (i.e., sldprt in this example).

*.gz Older versions of the file are normally compressed on a recurring nightly schedule.

*.img For files that support thumbnails, a thumbnail image is stored for each version created.

Index.xml An index file for the archive containing information on each version of the file and (in most cases) the filename.

18

How does it work? In a non replicated environment, one archive server hosts all physical files and versions that are placed in the file vault.

The file archives are stored in the file vault archive folder on the first archive server (archiveserver). The archive root folder on the second server (server2) does not contain any file archives.

When the file vault is replicated to the second server, that archive server will now also host a copy of the file vault archives.

The file vault archive folders are now available in to archive root folder of both servers. Any file archives added on the first archive server (archiveserver) can be replicated (i.e. copied) to the second archive server (server2) and file archives added to the second server can be replicated to the first server.

When a client that is attached to the first archive server (archiveserver) adds a file in the file vault view, the physical file (and all versions of the file) will initially be stored in the file archive of the attached archive server (i.e. archiveserver).

19

The file archive folder (00000002) on the first server (archiveserver) contains all versions of the file. The file archive folder and its contents have not yet been replicated to the second server (server2) and will therefore not exist on that server.

When a client that is attached to the second archive server (server2) retrieves a version of the above file to the local file vault view (by using Get, opening the file, previewing the file etc.) the attached archive server (server2) will try to send the file from the file archive folder to the client. If the specified file version does not yet exist in the file archive folder, an on-demand replication will trigger and the specified version will be replicated (i.e. copied) from one of the other archive servers that has the specified file archive. NOTE: Even though the archive server that the client is attached to do not yet have a replicated copy of the file archive, the client will still see the file when browsing in the file vault view since the information about the file comes from the database server the archive server only maintains the physical file content.

20

The file archive (00000002) and the specified version (version 3, i.e. 00000003.doc) requested by the client have now been replicated (copied) to the second archive server (server2) via the on-demand replication. Any additional clients attached to the second archive server will from now on retrieve that file version directly from the archive folder (it is only the initial client that triggers the on-demand replication if the requested file archive does not yet exist.

When a client that is attached to the second archive server (server2) creates a new version of the above file, that version (version 5) will be created in the file archive on the attached server. NOTE: A client will only send and receive files to the archive server it is attached to. A user can also see which server is currently having the specified file and version replicated by viewing the Replicated to information in the version tab.

The new version (00000005.doc) is stored on the second archive server (server2) until it is requested by a client triggering an on-demand replication back to the first archive server.

21

22

Scheduled replication

Files in PDMWorks Enterprise are by default replicated on-demand, meaning that when a client requests a file or file version from the archive server that the local vault view is attached to and the archive of that file version has not yet been replicated to the server, the client will trigger a replication of the archive from the closest archive server that is currently hosting it. Once the file archive is replicated, it will exist on the local archive server when further attempts are made to retrieve it. To automate the replication process, you can set up replication schemas that at set intervals will synchronize selected file parts of the file vault between specified archive servers hosting the replicated vault archive. This way, a client will always have speedy access to the files on the local archive server it is attached to. You can define any number of replication schemas to balance the network load. To define replication between archive servers located in different time zones: 1. Start the PDMWorks Enterprise administration tool and expand the tree of a replicated vault. 2. Double-click the item called Replication settings.

3. The Replication Settings dialog box is displayed, listing all archive servers replicating the file vault

archive. To create a new replication schedule, click the New Schema button.

4. The New Replication Schema dialog box is displayed.

23

5. Type a name that identifies the new replication schema.

6. Click the Add Folder button to select the parts of the file vault that should be included in this

replication schema.

24

o If you want to replicate all files in the entire file vault, select the top file vault name. All files, including subfolders, will then be scheduled for replication. Ensure that you have sufficient storage space on each archive server (in the schema) to host the full replicated archive. Also, if the file vault you are replicating contains many existing files, the initial replication process might take a while as all archives will be replicated to the defined archive servers.

o To replicate only parts of the file vault (for example, only the projects folder), select that folder in the tree. All files in that folder, and its subfolders, will be scheduled for replication. This is recommended with large file vaults where folders in which files are often updated are replicated on a schedule, while other folders less accessed will have files replicated on a per-need basis when they are retrieved (i.e., on-demand replication).

7. In the Connections to replicate section, select between the servers between which replication

should be scheduled. File archives will be replicated (be retrieved) to the Target Server from the Source Server.

NOTE: You can select multiple connections and set the same interval for all selected connections by pressing the CTRL key while selecting connections.

8. Select in the Predefined interval list a schedule for when the replication should run between the source and target servers. You can select from several predefined schedules in the list or assign your own specific schedule select User defined schedule.

9. If selecting a user-defined schedule, you must type an Interval string that defines at what times

the replication should occur.

The format for the string is defined in three sections: Minute Hour Weekday

Minute You can use 0 through 59 (0 is on the hour) Hour You can use 0 through 23 (0 is midnight)

25

Weekday You can use 1 through 7 (1 is Monday)

The sections can contain a single number (1), a range of numbers (1-7), or a list of numbers (0,15,30,45). Separate each section with a space. You may use an asterisk (*) as a wildcard for the entire number range. Some examples of a predefined schedule string: 0 0 * Run every day at midnight 0 0 1-5 Run every Monday through Friday at midnight 0 * * Run every hour on the hour, every day 0 */2 * Run every other hour, every day 0,15,30,45 * * Run every 15 minutes, every day 0,30 * 1-5 Run every half hour, Monday through Friday 0 6-18 1-5 Run every full hour between 6:00 a.m. and 6:00 p.m., Monday through Friday

9. Select the other server direction listed and set up the same, or a specific, schedule for when the replication should occur (for example, you might want to balance the network load so that replication between the main office to the second office runs at midnight, and any new file archives created on the archive server in the second office is replicated back to the main office at 1:00 a.m.).

NOTE: The times you specify in the schedule will trigger based on the local server time of the Target Server. For example, if the Target Server is located in the United States and the Source Server is located in Sweden and you set the schedule to start at midnight, that replication will occur at midnight United States time. NOTE: It is also possible to multi-select several connections and set the interval string for all selected connections at the same time.

10. Click OK to close the schema dialog box.

26

The new replication schema is now listed and will run at the defined intervals.

NOTE: The updating of replication schedules to each archive server relies on the PDMWorks Enterprise database server service, so ensure that the service is installed and running on the SQL server system (check the services for PDMWorks Enterprise Database Server).

Using the advanced schema settings By using the advanced schema settings you can limit what files in the specified folders should actually replicate when the schedule is run. Press the Advanced button in the schema dialog to access the advanced settings.

The advanced schema settings will show.

27

Replicate only latest version If a file has multiple versions (which are not yet replicated to a server), this option will only replicate the only the most recent version. For example - if version 5 thru 10 is not yet replicated to server B, enabling this option will replicate only version 10. Without this option enabled, version 5 thru 10 will be replicated when the schedule runs.

Replicate only files with revisions

This option will only replicate the file versions that has a PDMWorks Enterprise revision assigned. For example If version 4 has revision A and version 7 has revision B, enabling this option will only replicate version 4 and 7 when the schedule runs.

Include children when replicating

By default, only files stored under the specified folders set up in the schema will be replicated by the schedule. Any files not under the specified folders will not be replicated automatically. With this option enabled, the schedule will also include all referenced files to a file stored under the specified folder of the schema. For example If the schema is set to replicate only files under \Projects, and there is an assembly file that references two part files under the folder \Library with this option enabled, those two part files will also be replicated when the schema is run (even though the \Library folder is not part of the replication schema.

Only replicate files in the following states

This option will include only files that are currently in the specified workflow states. Select a workflow and state in the drop list and click the Add button. Any file versions not in the specified state will not be replicated.

Stop replication

By default, once a scheduled replication starts it will process all files and versions not yet

28

replicated to the server the files are added to a queue and will be replicated (copied) until the queue is empty. If you wish to stop the replication process after a set amunt of time, you can enable this option and specify after how many hours and minutes the replication should stop. Any files not yet processed after that period will be replicated (added to the queue) the next time a schema is set to start (or when the file is retrieved and trigger an on-demand replication instead).

29

Replication performance setting By default, when file archives are transferred using a scheduled replication, up to 10 files are transferred at the same time between the source and target servers. If this setting is too high (uses too much bandwidth) or too low (does not use enough bandwidth), you can change the default setting to a number between 1 (file) to 64 (files) using the following registry value. The setting affects how many files the target server should allow to receive at the same time from each source server. To set the number of files transferred at the same time between source and target servers: 1. On the target archive server, open the registry using regedit and browse to this key:

HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer

2. Create a new DWORD value.

3. Name it ReplicationThreads and enter a decimal value between 1 64 to specify how many files

should be received at the same time (default is 10).

30

4. Restart the archive server service for the change to take effect.

31

Archive replication status

To help monitoring the replication process, open the replication status dialog by right-clicking Archive Status and selecting Open.

The archive replication status dialog box is displayed.

Select the archive server to monitor in the Archive server list. As files are replicated, the values and diagram will change in real-time.

Total number of files available in this file vault Lists how many file versions in total exist in the file vault.

Number of files not yet replicated to this server Lists the number of file versions that are not yet replicated to the selected archive server. This includes both files and versions. For example, a file may have five (5) versions in the vault, but on the selected archive server only three (3) versions are stored. This field will count the missing two (2) file versions as not yet replicated.

Percent of files not yet replicated to this server Shows the percentage of total file versions that are not yet replicated to this server.

32

Existing files Shows files that are available to users in the file vault. Deleted files Shows files that have been deleted (but not yet purged) in the file vault; i.e., they can be found in the Deleted Files tab under folder properties.

System files Shows archives of system files in the file vault (for example, card images and add-ins). Show which file archives are not yet replicated To get a list of file archives that has not been replicated to a server, right-click Archive Status and selecting Show Missing Files.

A comma separated list will open showing the files not yet replicated and on which server they are missing on.

Show which server has a file version replicated When viewing the version tab of a file in a replicated file vault, the Replicated to field will show which server has a replicated copy of the selected version.

33

Archive server login selection

Typically a client is attached to the local archive server as defined when creating the file vault view. If a file vault is replicated and you want to have an option of which archive server to connect to (for example, if using a laptop and working in both replicated locations), you can enable this using the PDMWorks Enterprise policy. To enable the PDMWorks Enterprise policy: 1. Open the group policy editor on the client. You can use the shortcut in PDMWorks Enterprise

Administration Tool, Local Settings, Group Policies.

2. Right-click on User Configuration, Administrative Templates and select Add/Remove

Templates.

3. Add the PDMWorks Enterprise policy, available on the install CD under

\Support\Policies\PDMWorks Enterprise.adm. A new node will show up under administrative templates.

34

4. Expand PDMWorks Enterprise Settings, Login Manager and open Enable Alternative Servers.

5. Select Enabled to enable the policy.

6. When logging in, the login dialog box will show an additional list containing the names of the

available archive servers hosting the replicated vault.

NOTE: If using automatic login on the file vault, the login dialog will not show. To disable automatic login, open PDMWorks Enterprise Administration Tool, Local Settings, Settings, Automatic Login. Select the vault in the list and ensure that none of the checkboxes are selected.

35

Troubleshooting the replication setup

Use the following steps to verify the server communication and replication setup if the on-demand or scheduled replication fails. Keep in mind that three most common reasons that can cause file vault replication to fail are: 1. System name lookup failing

The replicated archive servers contact each other via the system name by default in a replicated environment, so it is very important that the DNS name lookup works 100%. In a WAN environment, the DNS lookup will usually not work. Ensure that each server can ping the other servers (including the SQL server system) on name and IP. It is recommended to update the local HOSTS file on each server with name and IP to the other servers.

2. TCP port blocking The file archive replication process between archive servers uses TCP port 3030. Ensure that there are no firewalls, routers, switches etc. blocking this port. Port 3030 must be opened fully between servers (and clients).

3. PDMWorks Enterprise Database server not running In order for changes to a replication schedule to take effect and trigger scheduled replication, the PDMWorks Enterprise Database server service must be running and correctly configured. If it is not running, the archive server service on each server must manually be restarted after a replication schedule has been created or modified.

36

Prerequisites Prepare by filling in as much of the following information as possible before stepping through the troubleshooting steps. Use this information to match returned values in the tests performed.

SQL SERVER INFORMATION

SQL Server Version: Operating System: System Name: IP Address: SQL SysAdmin Username (typically sa): SQL SysAdmin Password: Number of SQL Instances (typically 1): Default SQL TCP Port: PDMWorks Enterprise Version Installed:

ARCHIVE SERVER 1 INFORMATION

Operating System: System Name: IP Address: Default Archive Server TCP Port: PDMWorks Enterprise Version Installed: Installed on Same Server as SQL: YES NO

ARCHIVE SERVER 2 INFORMATION

Operating System: System Name: IP Address: Default Archive Server TCP Port: PDMWorks Enterprise Version Installed: Installed on Same Server as SQL: YES NO

REPLICATED FILE VAULT INFORMATION

File Vault Name: File Vault Database Name: File Vault Login Type:

37

Collect logs and registry settings To assist troubleshooting, the messages in the logs may be useful as they may indicate what is wrong. To export settings and logs: A Export registry settings Perform this step on each archive server 1. Select Start, Run, regedit.

2. Locate the registry key called HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer.

3. Right-click the key and select Export.

4. Save the registry values to a file; rename the file to the server name for easy identification.

38

B - Save the archive server logs 1. From a PDMWorks Enterprise client, start the PDMWorks Enterprise administration tool.

2. Right-click the archive server and select Show the archive server log.

3. Click the Copy log button.

4. Paste the copied log to a folder and rename it to the server name for easy identification.

5. Repeat for the second archive server. NOTE: The archive server logs can also be viewed in the event viewer on each server.

C Save the PDMWorks Enterprise client logs 1. If there is a client where a replication error is displayed, open the PDMWorks Enterprise

administration tool.

2. Expand the Local settings and right-click on Log File and select Copy.

3. Paste the log file to a folder and rename it to the client system name for easy identification

39

Increase logging level To increase the logging level on the archive server to include more detailed information: NOTE: Every file operation will be logged. 1. Run regedit.

2. Locate this key: HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks

Enterprise\ArchiveServer\. 3. Create a new DWORD value. Name it EventLogLevel and assign the hex value FFFF to it.

The logging will now be more detailed and show all events on the archive server. To set the logging to the normal level, remove the EventLogLevel value.

Verify SQL authentication information on archive server The replicated archive server communicates with the SQL server using information entered in the archive server settings. To verify SQL authentication on the archive server: 1. On the failing archive server, select Start, Programs, PDMWorks Enterprise, Archive Server

Configuration.

2. In the Archive Server manager, select Tools, Default Settings.

3. Click the Change button in the SQL login section.

40

4. Re-type the SQL name and password used to access the database (typically the sa user) then click OK. NOTE: The password field is always shown empty, even if there is a password set.

5. Check the vault-specific properties by right-clicking the file vault name and selecting PDMWorks Enterprise.

41

6. Select the Login tab and check the SQL login section. Use default SQL login should be selected for the initial replication to work. If it is not, select it or click the Change button and provide the correct SQL user and password as in the default settings. Click OK to update the settings.

7. Restart the archive server service.

Verify the communication ports Because the archive servers and SQL server communicate over a defined TCP port, it is important that no firewall is blocking these ports. A Ensure the firewall is configured Between the two archive servers, default port 3030 must be opened either ways (or whichever port is designated in the registry). From the replicated archive servers, default SQL port 1433 (or port 1434 for SQL instances) must be opened to the SQL server system (or whichever port designated).

42

B Test the ports Using Telnet, you can check to see if the port is open to the remote servers. To check to see if the port is open on remote servers: 1. On the archive server, open a command prompt window.

2. Type the IP address specified in the replication settings and the applicable port (default is 3030):

TELNET 3030.

3. If the port is open, the Telnet screen should be blank and display a cursor. Close the command prompt window.

4. Open another command prompt window and type (use the SQL server name used in the registry and the applicable port): TELNET 1433

5. If the port is open, the Telnet screen should be blank and display a cursor. Close the command prompt window.

If the Telnet command fails, replication might fail. Check the following: If you get Connection closed by foreign host, then the port is likely open (but will not talk to you),

or perhaps the port on a firewall is open but the port on the internal machine is closed. If you get Connection refused, then the port is likely closed. Check the firewall settings. If it hangs forever, the port is likely closed. Check the firewall settings.

Verify vault database replication server information The following should be done using the management studio on the SQL server to ensure that the file vault database contains valid archive server names. 1. Start the management studio by selecting Start, Programs, Microsoft SQL Server 2005, SQL

Server Management Studio.

2. Connect to the server or instance hosting the replicated file vault database.

3. Expand the file vault database, Tables, right-click on the table called ArchiveServers and select Open Table.

43

4. The table contains all archive servers that are replicating the file vault. The entry with ArchiveServerID 1 is the initial server where the file vault was created. Each additional archive server will get a unique ID as they are set to replicate the vault. Ensure that the system name of each server is entered in the ArchiveServerName field. The archive server system will look itself up by name in the table and try to match an entry if no match is found replication or login could fail. Verify that the system name of the replicated server can be PINGed as described in the next section. If the system name is incorrect, edit the entry with correct system name.

If you have configured the setup to use IP-address only communication (see installation guide) ensure that the ServerName value has also been added in the corresponding archive server registry and that it contains the correct IP-address. NOTE! The ServerName value must match the ArchiveServerName value in the archiveservers table.

44

5. Also ensure that the correct Source Server Address (system name or IP) is entered in the replication settings node inside the administration tool.

Verify TCP communication Perform the following tests between all replicated archive servers to ensure that they can communicate over the network using correct addresses. A - Ping on IP address 1. Open a command prompt window. 2. Type PING .

3. Verify that the other archive server replies. 4. Type PING . 5. Verify that the SQL server replies. If one server does not reply, replication might fail as the current server cannot reach the other server. Verify the network setup. B - Ping on system name 1. Open a command prompt window. 2. Type PING . 3. Verify that the other archive server replies and that the returned IP address is correct.

45

4. Type PING . 5. Verify that the SQL server replies and that the returned IP address is correct. If one server does not reply on system name, replication might fail as the current server cannot reach the other server. Verify the DNS settings in the network or update the local HOSTS file. C Reverse lookup IP address 1. Open a command prompt window. 2. Type PING -a . 3. Verify that the other archive server replies and that the returned name is correct. 4. Type PING a . 5. Verify that the SQL server replies and that the returned name is correct. If the reverse lookup fails and does not return the correct system name, the replication might fail if using system names to communicate. Verify the DNS settings in the network or update the local HOSTS file. D Verify communication stability 1. Open a command prompt window. 2. Type PING -t . This will repeatedly ping the destination until stopped by Ctrl-C.

3. After some time, verify that the other archive server replies and that there are no dropped replies. 4. Type PING t . 5. After some time, verify that the SQL server replies and that that there are no dropped replies. If there are many dropped replies in the repeating ping, replication might fail or become unreliable. Verify the network setup and the cause of the network instability.

46

Verify SQL communication For replication to work, the replicated archive server must be able to communicate with the SQL file vault database. This should be tested from both archive servers. A Check which SQL server address is used The name of the SQL server can be found in the archive server registry. To check which SQL server address is used: 1. Select Start, Run. Type regedit.

2. Expand the following registry key and select the key with the file vault name: HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\Vaults\

3. Check the Server value. This will be the name used to communicate with the SQL server. Ensure that the

47

B Run an ODBC test 1. Open the Control Panel and step into Administrative Tools.

2. Double-click Data Sources (ODBC)

3. In ODBC Data Source Administrator, select the System DSN tab and click the Add button to create a new test source.

4. Select the SQL Server driver.

48

5. Type any name for the ODBC source, then select the SQL server in Server. If the SQL server is not shown in the list, use the same name previously found in the registry previously (because this is what the archive server will use to communicate). Click Next.

6. Select With SQL Server authentication using a login ID and password entered by the user.

7. Type the SQL user (typically sa) and password that was configured in the archive server settings (see next section). Click Next to establish a connection to the SQL server.

49

8. If it succeeded, select the file vault database name in the list and click Next.

9. Continue using the wizard and click the Test Data Source button.

50

A message will appear indicating if the communication was successful.

10. Close and save or delete the test ODBC source. If the ODBC test failed for some reason, replication might fail. Check the following: That the SQL server name indicated in the registry can be reached correctly and that the DNS

translates it to a valid IP address (see previous section). You could try updating the Server value in the registry to a valid IP address instead and retest ODBC using the IP address instead.

That the archive server has current MDAC drivers: version 2.7 or later, which you can obtain from download.microsoft.com.

That you are supplying the correct SQL user and password authentication. Most ODBC errors will show an error code. Go to support.microsoft.com and search the Knowledge

base for a detailed explanation of the error.

51

Verify Communication Port Settings The replicated archive servers communicate over the default port 3030. Ensure that the registry value on each archive server is correctly set. To verify port settings: 1. On the archive server, select Start, Run, and type regedit.

2. Expand the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\ArchiveServer\

3. Verify that the BroadcastPort and ServerPort values exist, are of DWORD type, and have a valid port for the archive server (3030 by default).

52

If the values do not exist or are incorrect: 1. Create two new DWORD values.

2. Name them BroadcastPort and ServerPort.

3. Type 3030 in Value data, select Decimal, and click OK.

4. Restart the archive server service.

Replication overviewSetting up a replicated file vaultRequirementsStep 1 Install PDMWorks Enterprise and set up the file vauIn Office B

Step 2 Set up file vault replicationIn Office A

Step 3 Configure the replication settingsTesting the replication connection

On-demand replicationWhat are file archives?How does it work?

Scheduled replicationReplication performance setting

Archive replication statusTotal number of files available in this file vaultNumber of files not yet replicated to this serverPercent of files not yet replicated to this serverExisting filesSystem files

Show which file archives are not yet replicatedShow which server has a file version replicated

Archive server login selectionTroubleshooting the replication setupPrerequisitesCollect logs and registry settingsB - Save the archive server logsC Save the PDMWorks Enterprise client logsIncrease logging levelVerify SQL authentication information on archive serverVerify the communication portsVerify vault database replication server informationVerify TCP communicationVerify SQL communicationVerify Communication Port Settings