Launcher License

REPLICATION GUIDE
SOLIDWORKS ENTERPRISE PDM 2014

Contents
Legal Notices.................................................................................................................4
1 Replication Overview..................................................................................................7
2 Setting Up Replication................................................................................................9
Setting Up the Primary Vault.............................................................................................................10
Installing the Enterprise PDM Software at the Remote Office...........................................................11
Setting Up Replication on the Main Server.......................................................................................12
Initiating Replication..........................................................................................................................14
Replication Settings Dialog Box........................................................................................................15
Testing Replication Connections.......................................................................................................17
Connection Test Failures.............................................................................................................17
Changing the Source Server Address...............................................................................................19
Configuring Replication Retries.........................................................................................................20
3 On-Demand Replication...........................................................................................21
What Are File Archives......................................................................................................................21
How On-demand Replication Works.................................................................................................22
4 Scheduled Replication..............................................................................................24
Defining Replication..........................................................................................................................24
New Replication Schema Dialog Box..........................................................................................26
Advanced Schema Settings Dialog Box......................................................................................28
5 Controlling Replication Performance........................................................................30
6 Determining Archive Replication Status...................................................................31

Archive Status Dialog Box.................................................................................................................31
Showing Files That Are Not Replicated.............................................................................................32
7 Enabling Archive Server Login Selection.................................................................33
8 Troubleshooting the Replication Setup....................................................................34

System Information for Troubleshooting ..........................................................................................35
Collecting Logs and Registry Settings...............................................................................................36
Increasing the Logging Level............................................................................................................37
Verifying SQL Authentication............................................................................................................37
Verifying the Communications Ports.................................................................................................38
2
Contents
Verifying Vault Database Replication Server Information.................................................................39

Verifying TCP Communication..........................................................................................................40
Ping on IP Address......................................................................................................................40
Ping on System Name.................................................................................................................40
Ping on Reverse Lookup IP Address...........................................................................................41
Verify Communication Stability....................................................................................................41
Verifying SQL Communication..........................................................................................................41
Check Which SQL Server Address is Used.................................................................................41
Run an ODBC Test......................................................................................................................42
ODBC Test Failure.......................................................................................................................42
Verifying Communications Port Settings...........................................................................................43
3
Legal Notices
1995-2014, Dassault Systmes SolidWorks Corporation, a Dassault Systmes S.A. company,
175 Wyman Street, Waltham, Mass. 02451 USA. All Rights Reserved.
The information and the software discussed in this document are subject to change without
notice and are not commitments by Dassault Systmes SolidWorks Corporation (DS SolidWorks).
No material may be reproduced or transmitted in any form or by any means, electronically or
manually, for any purpose without the express written permission of DS SolidWorks.
The software discussed in this document is furnished under a license and may be used or
copied only in accordance with the terms of the license. All warranties given by DS SolidWorks
as to the software and documentation are set forth in the license agreement, and nothing
stated in, or implied by, this document or its contents shall be considered or deemed a
modification or amendment of any terms, including warranties, in the license agreement.
Patent Notices
SolidWorks 3D mechanical CAD software is protected by U.S. Patents 5,815,154; 6,219,049;
6,219,055; 6,611,725; 6,844,877; 6,898,560; 6,906,712; 7,079,990; 7,477,262; 7,558,705;
7,571,079; 7,590,497; 7,643,027; 7,672,822; 7,688,318; 7,694,238; 7,853,940; 8,305,376;
8,581,902; 8,817,028, and foreign patents, (e.g., EP 1,116,190 B1 and JP 3,517,643).
eDrawings software is protected by U.S. Patent 7,184,044; U.S. Patent 7,502,027; and
Canadian Patent 2,318,706.
U.S. and foreign patents pending.
Trademarks and Product Names for SolidWorks Products and Services

SolidWorks, 3D ContentCentral, 3D PartStream.NET, eDrawings, and the eDrawings logo are
registered trademarks and FeatureManager is a jointly owned registered trademark of DS
SolidWorks.
CircuitWorks, FloXpress, PhotoView 360, and TolAnalyst are trademarks of DS SolidWorks.
FeatureWorks is a registered trademark of Geometric Ltd.
SolidWorks 2014, SolidWorks Standard, SolidWorks Professional, SolidWorks Premium,
SolidWorks Enterprise PDM, SolidWorks Workgroup PDM, SolidWorks Simulation, SolidWorks
Flow Simulation, eDrawings, eDrawings Professional, SolidWorks Sustainability, SolidWorks
Plastics, SolidWorks Electrical, and SolidWorks Composer are product names of DS SolidWorks.
Other brand or product names are trademarks or registered trademarks of their respective
holders.
COMMERCIAL COMPUTER SOFTWARE - PROPRIETARY
The Software is a commercial item as that term is defined at 48 C.F.R. 2.101 (OCT 1995),
consisting of commercial computer software and commercial software documentation as
such terms are used in 48 C.F.R. 12.212 (SEPT 1995) and is provided to the U.S. Government
(a) for acquisition by or on behalf of civilian agencies, consistent with the policy set forth in
48 C.F.R. 12.212; or (b) for acquisition by or on behalf of units of the Department of Defense,
4
consistent with the policies set forth in 48 C.F.R. 227.7202-1 (JUN 1995) and 227.7202-4 (JUN
1995).
In the event that you receive a request from any agency of the U.S. Government to provide
Software with rights beyond those set forth above, you will notify DS SolidWorks of the scope
of the request and DS SolidWorks will have five (5) business days to, in its sole discretion,
accept or reject such request. Contractor/Manufacturer: Dassault Systmes SolidWorks
Corporation, 175 Wyman Street, Waltham, Massachusetts 02451 USA.
Copyright Notices for SolidWorks Standard, Premium, Professional, and

Education Products
Portions of this software 1986-2014 Siemens Product Lifecycle Management Software Inc.
All rights reserved.
This work contains the following software owned by Siemens Industry Software Limited:
D-Cubed 2D DCM 2014. Siemens Industry Software Limited. All Rights Reserved.
D-Cubed 3D DCM 2014. Siemens Industry Software Limited. All Rights Reserved.
D-Cubed PGM 2014. Siemens Industry Software Limited. All Rights Reserved.
D-Cubed CDM 2014. Siemens Industry Software Limited. All Rights Reserved.
D-Cubed AEM 2014. Siemens Industry Software Limited. All Rights Reserved.
Portions of this software 1998-2014 Geometric Ltd.
Portions of this software incorporate PhysX by NVIDIA 2006-2010.
Portions of this software 2001-2014 Luxology, LLC. All rights reserved, patents pending.
Portions of this software 2007-2014 DriveWorks Ltd.
Copyright 1984-2010 Adobe Systems Inc. and its licensors. All rights reserved. Protected by
U.S. Patents 5,929,866; 5,943,063; 6,289,364; 6,563,502; 6,639,593; 6,754,382; Patents
Pending.
Adobe, the Adobe logo, Acrobat, the Adobe PDF logo, Distiller and Reader are registered
trademarks or trademarks of Adobe Systems Inc. in the U.S. and other countries.
For more DS SolidWorks copyright information, see Help > About SolidWorks.
Copyright Notices for SolidWorks Simulation Products

Portions of this software 2008 Solversoft Corporation.
PCGLSS 1992-2013 Computational Applications and System Integration, Inc. All rights
reserved.
Copyright Notices for SolidWorks Enterprise PDM Product

Outside In Viewer Technology, 1992-2012 Oracle
2011, Microsoft Corporation. All rights reserved.
Copyright Notices for eDrawings Products

Portions of this software 2000-2014 Tech Soft 3D.
Portions of this software 1995-1998 Jean-Loup Gailly and Mark Adler.
5
Portions of this software 1998-2001 3Dconnexion.
Portions of this software 1998-2014 Open Design Alliance. All rights reserved.
Portions of this software 1995-2012 Spatial Corporation.
The eDrawings for Windows software is based in part on the work of the Independent JPEG
Group.
Portions of eDrawings for iPad copyright 1996-1999 Silicon Graphics Systems, Inc.
Portions of eDrawings for iPad copyright 2003 2005 Apple Computer Inc.
6
1
Replication Overview
Clients connect to an Enterprise PDM vault through their local vault view. When they browse
for files or items, view data cards, or search for files, Enterprise PDM retrieves data from the
database server. When clients use the Get or Check out commands to retrieve physical files
(such as drawings and documents) to the local vault view (cache), the software retrieves the
files from the archive server.
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.
In a WAN environment, an Enterprise PDM vault that is shared between multiple offices relies
heavily on the speed of the connection.
In the following not-replicated Enterprise PDM WAN environment, two remote offices
communicate with a central Enterprise PDM database server and archive server located at the
Main office.
7
Replication Overview
The information from both the database server and the physical archive server is transferred
over the WAN. Calls to the database server are speedy because only small packets of data are
sent. File requests can take anywhere from seconds to hours depending on the file size.
You can use Enterprise PDM vault replication to balance the amount of data that is transferred
over a slow WAN connection by providing each office with a local archive server that hosts a
replicated copy of the vault archive. When remote clients work in the vault, they still receive
database information from the central database server, but the physical files are now retrieved
from the closest archive server with a copy of the archived file.
In the following replicated Enterprise PDM environment, each office communicates with the
central database server. In addition, each office has a local archive server hosting a replicated
copy of the file archive.
If the file archive has already been replicated, the file is 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 is automatically replicated when
it is initially retrieved by a client so that the archived file is then accessible on the local archive
server to all other clients in the same office.
8
2
Setting Up Replication
To set up replication:
1. In the main office, install SQL Server and the Enterprise PDM database and archive servers,
and create the primary vault.
2. In a remote location, install only an Enterprise PDM archive server.
3. On the main office archive server, set up replication by creating a vault that replicates the
remote vault. This also replicates the primary vault on the remote archive server.
The communications between the sites must meet these prerequisites:
The SQL server hosting the 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 must have a server (or workstation) with a hard drive large enough to install
the Enterprise PDM archive server and store all or some of the replicated vault archive.
If you use WAN communication, open the default TCP port 3030 between each archive server
system and the default TCP port 1433 to the SQL server.
If you use a named SQL instance instead of the default instance, MSSQLSERVER, the TPC
port for SQL communication may use a different port, typically port 1434.
If you use Windows login for the vault, both offices must have access to the domain users.
This is not required if you set up a domain trust so that the local Windows domain users
are correctly defined on the local domain controller. See the Microsoft TechNet library for
configuration information.
In the following procedures, the main office hosts the SQL server, database server, and archive
server (Archiveserver). A remote office hosts only a second archive server (Server2).
9
This chapter includes the following topics:
Setting Up the Primary Vault

Installing the Enterprise PDM Software at the Remote Office
Setting Up Replication on the Main Server
Initiating Replication
Replication Settings Dialog Box
Testing Replication Connections
Changing the Source Server Address
Configuring Replication Retries
Setting Up the Primary Vault

To set up the primary vault at the main office:
1. Install the SQL server, the Enterprise PDM database server, and the Enterprise PDM
archive server software.
See the Solidworks Enterprise PDM Installation Guide.
2. Install one or more Enterprise PDM client workstations.
10
3. From an Enterprise PDM client, use the Administration tool to connect to the archive
server and create and configure a new vault:
a) Open the Administration tool by doing one of the following:
On Windows 7 and Windows Server systems prior to Windows Server 2012, click
Start > All Programs > SolidWorks Enterprise PDM > Administration.
On Windows 8 and Windows Server 2012 or later, on the Apps screen, under
SolidWorks Enterprise PDM, click Administration.
b) In the top left corner of the SolidWorks Enterprise PDM Administration dialog box,
right-click the archive server and click Create new vault.
c) Complete the Create New Vault wizard.
The new vault is added under the archive server.
4. On the remaining clients that connect to the main office archive server, create a local
vault view of the new vault on the archive server:
a) Open the View Setup Wizard by doing one of the following:
Start > All Programs > SolidWorks Enterprise PDM > View Setup.
SolidWorks Enterprise PDM, click View Setup.
b) Complete the wizard screens.
Installing the Enterprise PDM Software at the Remote Office

Because the remote office will host a replicated copy of the vault archive, you install only
the Enterprise PDM archive server software. You do not need to install an additional SQL
server or Enterprise PDM database server.
Obtain the settings used to install the archive server at the main office.
This includes the SQL user login name and password (typically, the sa account).
Ensure that TCP port 3030 is opened in any firewall between the remote office and the
main office.
For installation instructions, see the SolidWorks Enterprise PDM Installation Guide.
To install Enterprise PDM at the remote office:
1. Install the Enterprise PDM archive server, using the settings that were used to install
the archive server in the main office.
For example:
11
Use the SQL user name and password that are used on the SQL server installed in
the main office.
If you use the Windows login type on the primary archive server, all other archive
servers should use the same login type.
2. Install one or more Enterprise PDM client workstations.
Do not create vault views on the clients in the remote office until the vault has
been replicated.
Setting Up Replication on the Main Server

You use the main office archive server to create the replicated vault at the remote office.
When you configure servers for on-demand replication, a file added by a client attached
to the main office archive server can be retrieved by a client attached to the remote
archive server. At the same time, the archive is replicated to the remote server. See
On-Demand Replication on page 21.
To set up a scheduled recurring replication, configure a replication schema. See

Scheduled Replication on page 24.
A replicated vault uses only one centrally shared SQL database, so both vault nodes are
identical and you can administer either one. The only difference is that the replicated
vault uses the login/security settings of the source vault.
Before beginning:
Ensure that communications between the offices are set up.
The remote server is running.
TCP port 3030 is open.
The archive server service is started.
Obtain the login information of a user account with Attach access or Administrative
access in the remote archive server security settings.
The local administrator on the remote archive server system has this access by
default.
To identify user accounts with the correct settings:

1. On the remote server, open the SolidWorks Enterprise PDM Archive Server dialog
box by doing one of the following:
Start > All Programs > SolidWorks Enterprise PDM > Archive Server
Configuration.
SolidWorks Enterprise PDM, click Archive Server Configuration.
2. Right-click Tools and click Default Settings.
3. On the Security tab, view the group and user access.
12
To replicate the main office vault:
1. On an Enterprise PDM client attached to the main office archive server, open the
Administration tool by doing one of the following:
Start > All Programs > SolidWorks Enterprise PDM > Administration.
SolidWorks Enterprise PDM, click Administration.
2. In the Administration tool, click File > Add Server.

3. In the Add Server dialog box, for Server name, select the server in the remote office.
If the remote server name is not listed, type the name. This can occur if the server
is located on a WAN and the broadcast protocol has not been configured.
If the remote server is not running or the connection is blocked, you receive an
error message that Enterprise PDM could not connect to the archive server.
Ensure that the prerequisites are met and begin the procedure again.
4. Click OK.
5. When prompted, log in using a Windows user account with Attach or Administrative
access in the remote archive server security settings.
The remote server is listed in the left pane of the Administration tool.
6. Right-click the remote server name and click Add replicated vault.
7. If prompted, log in as a Windows user with administrative access.
8. When the replication wizard starts, click Next.
9. On the Select archive server source screen, for Archive Server, select the main
office archive server that currently hosts the file vault archive, and click Next.
In a WAN environment, use the IP address. Otherwise, use the DNS name to avoid
problems later if the IP address cannot be resolved to the correct server name.
10. On the Select source vault screen, select the vault to replicate and click Next.
11. If prompted, log in to the vault as the Enterprise PDM Admin user or as a user with
permission to replicate vaults.
The Admin user has this permission by default.
12. On the Select destination folder screen, select a root folder on the remote server
where the replicated vault archive should be placed.
If the archive server was installed using defaults, the root folder is Archives.
13. Click Finish.
The replication wizard creates settings and archive folders on the remote server.
The created folders are empty because files in the source vault are not yet
replicated.
The replicated vault appears under both servers in the Administration tool. If you do
not see it, right-click the server and click Refresh.
13
The Replication settings dialog box for the remote archive server tries to open.
14. If a login screen appears, log in as a user with permission to manage vault replication.
This login triggers replication of vault-specific security settings such as the admin
password and login type from the main office archive server to the remote archive
server.
The Replication settings dialog box appears, showing the connections between the
two systems. By default, the archive server names are used as connection addresses.
You can use this dialog box to test the connections. See Testing Replication
Connections on page 17.
If the connection between the servers cannot be made, a message appears.

If the port is open and you know that the remote server can reach the main server
correctly, restart the Administration tool and log in to the vault node under the
remote archive server again.
If the connection still fails, expand the replicated vault on the main office archive
server and double-click Replication settings to display the Replication settings
dialog box. Test the connections to identify the problem.
Initiating Replication
This procedure configures the main office and remote office servers for on-demand
replication. This means that a file added by a client attached to the main office archive
server can be retrieved by a client attached to the remote archive server. When the file
is retrieved, the archive is replicated to the remote server.
To set up a scheduled recurring replication, configure a replication schema. See

Scheduled Replication on page 24.
14
To initiate replication:
1. On an Enterprise PDM client connected to the main office archive server, in the
Administration tool, click the replicated vault for the remote archive server.
2. If a vault login appears, log in as a user with permission to manage vault replication.
The initial login replicates vault-specific security settings, such as admin password
and login type, from the main office archive server to the remote archive server.
3. If you see a message that you need to run the replication settings command on the
source server:
a) Click OK.
b) Close and reopen the Administration tool.
4. Log in to the vault on the main office archive server.
5. Double-click Replication settings .
The Replication settings dialog box lists the local and remote servers and lets you
test the connections.
6. In the Test column, check a target/source server pair and click Test.
7. In the Test Connections dialog box, view the connection Status.
8. If the status is not Succeeded, click Test.
9. If the connection still does not succeed, save the test results to a .csv file by clicking
Save.
10. Click Exit.
Replication Settings Dialog Box

The Replication Settings dialog box lets you test and change Enterprise PDM replication
configurations.
To open the Replication settings dialog box, in the Administration tool, expand a replicated
file vault archive and double-click Replication settings.
Connections
Lists source and target replication servers.
Test When selected, enables the Test button described below.

where you can test the connection from the Source Server
to the Target Server.
Target Server Specifies the server where files are replicated to.
Source Server Specifies the server where files are replicated from.
Source Server Address The DNS system name or IP address that the Target Server
uses to communicate with the Source Server.
Speed Specifies the current speed setting.
15
Test Opens the Test Connections dialog box, where you can test
the connection from the Source Server to the Target Server.
This button is only enabled when the Test check box for a
target/source server pair is checked.
Selected connection
IP address or DNS The IP address or DNS name of the selected source server.
name
In a WAN environment, use the IP address.
The archive servers communicate over TCP port 3030. Make
sure that port is fully opened in any firewall between the
servers.
Speed Balances the replication load between three or more servers.

Server connections with a higher speed rating take priority over
servers with a lower speed rating. If replicating between two
servers, select the highest speed rating (10 Mbit) regardless
of real connection speed.
For example, consider the case where a file version is replicated
on two 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 is prioritized.
The speed setting only affects the priority. It does not affect
the actual replication transfer speed in any way.
Replication schemas
Lists the replication schemas defined and the folders that are replicated for each schema.
New Schema Opens the New Replication Schema dialog box, where you can
select the folders to be replicated, the connections to replicate,
and replication intervals.
Edit Schema Opens the Edit Replication Schema dialog box for the selected
schema.
Remove Schemas Removes the selected replication schema.
16
Testing Replication Connections

To test that replication works correctly between two archive servers, use the connection
Test option. Test triggers an on-demand replication from the source server to the target
server, which verifies the connection.
To test replication connections:
1. Expand the vault you want to test and double-click Replication settings.
2. In the Replication settings dialog box, in the Test column, select the target/source
server pair to test.
3. Click Test.
The button is unavailable if you have unsaved settings. Click Save , and then
reselect the connection to test.
If you change the source server address, wait a short time for the connection to be
updated before testing it. See Changing the Source Server Address on page 19.
4. In the Test Connections dialog box, click Test.
If the connection is configured correctly, the result column returns Test successful.
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.
If the result is not Test Successful, an error code is returned.

5. To save the test results to a .csv file, click Save.
6. Navigate to the location for the saved file and click Save.
7. Click Exit to close the Test Connection dialog box.
Connection Test Failures

If the connection test does not return a successful result, something is incorrectly
configured. Refer to the troubleshooting section for tips on how to diagnose the problem.
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.
17
Changes to the source server address in the replication settings do not take effect if
the database server service is not working correctly. Restart the archive server service
on the target server to force a reload of the updated address.
The following table lists some of the warnings that are shown in the Results column of
the Test Connections dialog box when a replication test fails.
Problem Results Archive Server Log information

Message and
Error Code
Incorrect source The target server

server address cannot download
from the source
server!
0x80040422
Archive server The target server

service on the cannot download
source server is from the source
not running. server!
Archive server 0x8004041A
TCP port 3030 is
not open on the
source server.
Archive server Failed to connect

service on the to target server
target server is using address
not running. server_name on
port 3030 from
Archive server
client!
TCP port 3030 is
not open on the 0x8004041A
target server.
18
Problem Results Archive Server Log information

Message and
Error Code
Installed archive The target server

server software on cannot download
the source server from the source
is not of same server!
version as on the
0x8004041E
target server.
Changing the Source Server Address

Changes you make to the source server address are updated to the target server through
the Enterprise PDM database server service.
To change the source server address:
1. Expand the vault where you want to make the change and double-click Replication
Settings.
2. Click the connection with the Source Server Address you are changing.
3. Under Selected connection, type the new source server DNS name or IP address.
In a WAN environment, use the IP address. In other environments, use the DNS name
to avoid problems later if the IP address cannot be resolved to the correct server
name.
4. In the Administration tool toolbar, click Save .
5. After waiting a short time for the changed address to be updated on the target server,
test the connection by selecting it and clicking Test.
See Testing Replication Connections on page 17.
6. If your changes do not take effect, verify that the database server service is working
correctly and can connect to the target server.
If the database server service is not working, restart the archive server service on
the target server to force a reload of the updated source server name.
19
Configuring Replication Retries

You can configure how the software handles WAN scenarios where not all servers are
available at all times.
If the first attempt to retrieve a file fails, the archive server uses a lookup table to select
other servers from which to replicate the file. This table prioritizes servers based on the
speed settings you specify when you configure connections using the Replication Settings
dialog box. If each attempt to get the file fails, the archive server retries the operation.
By default, the replication server retries twice before it times out. You can change the
number of retries by creating a new DWORD key on the archive server called
RetriesCount.
The value you set for the RetriesCount keyword controls the number of retries. A value
of 0x00000001 causes one retry. A value of 0x00000002 causes two retries and so on.
To create the new DWORD:
1. Open the Registry Editor.

2. Expand the following key:
HK_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks Enterprise\
ArchiveServer\Vaults\vault_name
3. Right-click in the right pane and click New > DWORD Value.
4. For DWORD name, type RetriesCount.
5. Right-click RetriesCount and click Modify.
6. In the Edit DWORD Value dialog box:
a) For Value data, type the number of retries you want.
b) For Base, select Hexadecimal.
c) Click OK.
7. Exit the Registry Editor.
20
3
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 when the file is requested by a client connected to that
archive server. The on-demand replication always allows clients to retrieve files, whether its
file archive is available on the local archive server or not.
What Are File Archives

How On-demand Replication Works
What Are File Archives

All files in an Enterprise PDM 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 local vault
view. Instead, the archive server software uses hexadecimal ID names that are maintained
in the vault database. It is these archive folders that are replicated between the archive
servers when a vault is using replication.
The 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 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, such as .sldasm in the
example above.
21
*.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 The archive's index file contains information on each version of the
file and (in most cases) the filename.
How On-demand Replication Works

This topic describes how on-demand replication works.
State/Action Result
Non-replicated One archive server hosts all physical files and versions that
environment. are placed in the vault.
The file archives are stored in the vault archive folder on the
first archive server. The archive root folder on the second
server does not contain any file archives.
The vault is replicated to The second archive server also hosts a copy of the vault
a second server. archives.
The vault archive folders are available in the archive root
folder of both servers.
Archives added on the first archive server can be replicated
to the second archive server.
Archives added to the second server can be replicated to
the first server.
A client that is attached to The physical file (and all versions of the file) are initially
the first archive server stored in the file archive of the first archive server.
adds a file in the local
The file archive folder on the first server contains all versions
vault view.
of the file. The file archive folder and its contents have not
yet been replicated to the second server and therefore do
not exist on the second server.
22
State/Action Result
A client that is attached to the second The second archive server tries to send the file
archive server retrieves a version of the from its file archive folder to the client.
newly-added file to the local vault view.
If the specified file version does not yet exist
Even if the archive server that the in the second server's file archive folder, an
client is attached to does not yet have on-demand replication is triggered and the
a replicated copy of the file archive, specified version is replicated from one of the
the client sees the file when browsing other archive servers that has the specified file
in the vault view because the archive.
information about the file comes from After the replication of the file is complete, any
the database server. The archive additional clients attached to the second
server only maintains the physical file archive server can retrieve that file version
content. directly from the second server's archive folder.
A client that is attached to the second The new version of the file is created in the file
archive server creates a new version of archive on the second archive server.
the file.
The new version is stored on the second
archive server until it is requested by a client
triggering an on-demand replication back to
the first archive server.
A client can only send and receive files that

are on the archive server it is attached to.
In Windows Explorer, a user can see which
server currently has the specified file and
version replicated by viewing the
Replicated to information on the Version
tab.
23
4
Scheduled Replication
The default method for replication in Enterprise PDM is on-demand replication. When a client
requests a file that has not yet been replicated, the client triggers a replication of the archive.
See How On-demand Replication Works on page 22.
To automate the replication process, you can set up replication schemas that run on selected
parts of the file vault, between specified archive servers that host the replicated vault archive,
at set intervals. With scheduled replication, a client always has speedy access to the files on
the local archive server the client is attached to.
You can define any number of replication schemas to balance the network load.
The database server service updates the replication schedules to each archive server. Before
you define replication schemas, ensure that the service is installed and running on the SQL
server system by checking the services for the SolidWorks Enterprise PDM database server.
Defining Replication
Defining Replication
1. In the Enterprise PDM Administration tool, expand the tree of a replicated vault.
2. Double-click Replication settings.
The Replication settings dialog box is displayed, listing all archive servers that replicate
the vault archive.
3. To create a new replication schedule, under Replication schemas, click New
Schema.
4. In the New Replication Schema dialog box, for Schema name, type a name for the
new replication schema.
5. Click Add Folder to select the parts of the vault to include in the replication schema.
6. In the Select Folder dialog box, do one of the following:
To replicate all files in the vault, select the top vault name.
All files, including subfolders, are scheduled for replication.
Ensure that you have sufficient storage space on each archive server in the schema
to host the full replicated archive.
24
If the vault you are replicating contains many existing files, the initial replication
process might take a while since all archives are replicated to the defined archive
servers.
To replicate only parts of the vault (for example, a specific folder), select that
folder in the tree.
All files in that folder and its subfolders are scheduled for replication.
This is recommended with large file vaults where folders with frequently updated
files are replicated on a schedule. For folders that are accessed less often, files
can be replicated on an as-needed basis by using on-demand replication.
Repeat steps 5 and 6 to add other specific folders.
7. To limit the files in the specified folders that should replicate when the schedule is
run, click Advanced and select one or more of the options described in the Advanced
Schema Settings Dialog Box on page 28.
8. Under Connections to replicate, select the servers between which replication should
be scheduled.
File archives are replicated to the Target Server from the Source Server.
You can set the same interval for multiple connections by pressing CTRL while
selecting connections.
9. For Predefined interval, select when 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 by selecting User defined schedule.
10. If you select a user-defined schedule, you must type an Interval string that defines
the times when replication should occur.
The format for the string contains three sections: Minute Hour Weekday
Minute 0 through 59 (0 is on the hour)
Hour 0 through 23 (0 is midnight)
Weekday 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.
Examples of predefined schedule strings:
00* 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
25
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
11. Under Connections to replicate, select the other server direction listed and set up
the schedule for when 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 files created on
the archive server in the second office are replicated back to the main office at 1:00
a.m.
Replication is triggered at the times you specify 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, replication will occur at midnight United States time.
12. Click OK to close the schema dialog box.
The new replication schema is now listed and will run at the defined intervals.
New Replication Schema Dialog Box

Use the New Replication Schema dialog box to define replication between archive servers
located in different time zones.
To display this dialog box:
Expand the tree of a replicated vault and double-click Replication settings. In the
Replication Settings dialog box, click New Schema.
Type the schema name.

Schema name
Folders included in the replication schema.

Folders that are part
of the schema
26
Add Folder Displays the Select Folder dialog box, where you select the parts
of the vault to include in this replication schema.
To schedule all files in the vault for replication, select the top
vault name. Ensure that you have sufficient storage space on
each archive server in the schema to host the full replicated
archive. If the vault being replicated contains many files, the
initial replication process might take a while because all archives
are replicated to the defined archive servers.
To replicate only parts of the vault such as the projects folder,
select that folder in the tree. All files in the folder and its
subfolders are scheduled for replication. Use this method for
large vaults: schedule replication for folders in which files are
often updated and use on-demand replication for less frequently
accessed folders.
Remove Folder Removes the selected folder from the list.
Connections to Select the servers between which replication should be

replicate scheduled. File archives are replicated to the Target Server
from the Source Server.
Replication interval for selected connection

Schedule the replication interval for each target server/source server pair in the
Connections to replicate list. To set the same interval for multiple connections, press
CTRL while selecting connections.
Predefined interval Schedule when replication should run between the selected
source and target servers. You can select a predefined schedule
or assign your own schedule by selecting User defined
schedule.
Interval string If you select a user-defined schedule, type an Interval string

to define when the replication should occur.
Define the format for the string:
Minute - Select from 0 through 59, where 0 is on the hour.
Hour - Select between 0 and 23, where 0 is midnight.
Weekday - Select between 1 and 7, where 1 is Monday.
Advanced Displays the Advanced Schema Settings dialog box, where you
limit the files in a folder that are replicated when the schedule
is run.
27
Advanced Schema Settings Dialog Box

Use the Advanced Schema Settings dialog box to specify which files in the specified
folders should actually replicate when the schedule is run.
Click Advanced in the Schema dialog box.
Replicate only the latest Replicates only the most recent version if a file has
version multiple versions that are not yet replicated to a
server.
For example, if versions 5 through 10 are not yet
replicated to server B, enabling this option replicates
only version 10. Without this option enabled, versions
5 thru 10 are replicated when the schedule runs.
Replicate only files with Replicates the file versions that have an Enterprise
revisions PDM revision assigned.
For example, if version 4 has revision A and version
7 has revision B, enabling this option only replicates
versions 4 and 7 when the schedule runs.
Include children when By default, only files stored under the specified folders
replicating set up in the schema are replicated by the schedule.
Any files not under the specified folders are not
replicated automatically.
With this option enabled, the schedule also includes
all referenced files to a file stored under the specified
folder of the schema.
For example, consider a schema that is set to replicate
only files under \Projects folder. The vault contains
an assembly file that references two part files under
the \Library folder. 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 Includes only files that are currently in the specified
following states workflow states.
Select a workflow and state in the drop-down list and
click Add. Any file versions not in the specified state
are not replicated.
28
Stop replication after By default, once a scheduled replication starts it

processes all files and versions not yet replicated to
the server. The files are added to a queue and are
replicated until the queue is empty.
To stop the replication process after a set length of
time, you can enable this option and specify when the
replication should stop.
Any files not yet processed after that period are added
to the queue for replication the next time a schema is
set to start.
If a client retrieves a modified file before the next

time the schema runs, the file is replicated
immediately by on-demand replication.
29
5
Controlling Replication Performance
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
or too low and causes bandwidth issues, you can change the default setting to a number
between 1 and 64 using a registry value. The setting affects how many files the target server
receives 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 editor.

ArchiveServer
3. To create a new DWORD value, right-click ArchiveServer and click New > DWORD
(32-bit) Value.
4. For the DWORD Name, type ReplicationThreads.
5. Right-click ReplicationThreads and click Modify.
6. To specify how many files should be received at the same time, in the Edit DWORD Value
dialog box:
a) For Value data, type a number between 1 and 64.
b) Select Decimal as the Base.
c) Click OK.
The default is 10.
7. Exit the registry.
8. For the change to take effect, restart the archive server.
30
6
Determining Archive Replication
Status
From the Enterprise PDM Administration tool, you can use the Archive Status feature to:
Open the Archive Status dialog box, which shows totals and percentages of files that have
been replicated.
Create a list of files that have not yet been replicated.
In Windows Explorer, you can select a vault file and view the Version tab to see which server
has a replicated copy of the selected version.
Archive Status Dialog Box

Showing Files That Are Not Replicated
Archive Status Dialog Box

Use the Archive Status dialog box to monitor the replication process.
Right-click Archive Status and click Open.
Archive Server Select the archive server to monitor.

As files are replicated, the values and diagram
change in real time.
The file vault is replicated: Indicates whether the file vault is replicated.
Total number of files available The number of file versions that exist in the vault.
in this file vault
Number of files not yet The number of file versions that are not yet
replicated to this server replicated to the selected archive server. For
example, the vault may have five versions and the
archive server three versions.
31
Determining Archive Replication Status
Percent of files not yet The percentage of the total number of file versions
replicated to this server not yet replicated.
Existing files
Files that are available to users in the vault.
Deleted files
Files that have been deleted (but not yet purged)
in the vault. The Deleted Files tab under folder
properties still lists the files.
System files
Archives of system files in the vault such as card
images and add-ins.
Showing Files That Are Not Replicated

You can create a list of files that have not been replicated.
1. In the Administration tool, right-click Archive Status and click Show Missing Files.
2. When prompted, choose whether to limit the returned data to the first 99 files.
A comma-separated list opens, showing the files and versions that have not been
replicated.
The list includes the following information:
Type of data (usually File)
Name and path of file
Missing version
Latest version
Server the files are missing on
Whether the file has been Deleted
The internal ID of the files
32
7
Enabling Archive Server Login
Selection
This procedure requires access to the SolidWorks Enterprise PDM group policy. Before you
begin, insert the installation DVD, and copy \Support\Policies\PDMWorks Enterprise.adm
to a location on your system.
Typically a client is attached to the local archive server as defined when creating the local
vault view. If a vault is replicated and you want to have an option of which archive server to
connect to, you can enable this using the SolidWorks Enterprise PDM policy. This is useful if
you are using a laptop and working in both replicated locations.
1. In the SolidWorks Enterprise PDM Administration tool, expand Local Settings, right-click
Group Policies, and click Open.
2. In the Group Policy dialog box, under User Configuration, right-click Administrative
Templates, and click Add/Remove Templates.
3. In the Add/Remove Templates dialog box, click Add.
4. In the Policy Templates dialog box, navigate to the location where you copied PDMWorks
Enterprise.adm, select it, and click Open.
5. Click Close.
A new node, SolidWorks Enterprise PDM Settings, is added under Administrative
Templates.
6. Expand SolidWorks Enterprise PDM Settings and click Login Manager.
7. In the Login Manager dialog box, right-click Enable Alternate Servers and click
Properties.
8. In the Enable Alternate Server Properties dialog box, on the Settings tab, select Enabled,
and click OK.
9. Close the Group Policy dialog box.
When you log in, the login dialog box shows an Archive Server list containing the names of
the available archive servers hosting the replicated vault.
If automatic login is in use on the vault, the login dialog does not show. To disable automatic
login:
1. In the SolidWorks Enterprise PDM Administration tool, under Local Settings, right-click
Settings, and click Open.
2. In the Settings dialog box, for Vault, select the replicated vault.
3. Clear all check boxes, and click OK.
33
8
Troubleshooting the Replication
Setup
The three most common reasons that vault replication fails are:
System name lookup failure
By default, in a replicated environment the replicated archive servers contact each other
via the system name. It is very important that the DNS name lookup works 100% of the
time. In a WAN environment, the DNS lookup does not usually work.
Ensure that each server can ping the other servers, including the SQL server system, by
name and IP address. It is recommended that you update the local HOSTS file on each
server with the DNS names and IP addresses of the other servers.
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.
Enterprise PDM Database server not running
For changes to a replication schedule to take effect and trigger scheduled replication, the
Enterprise PDM Database server service must be running and correctly configured.
If it is not running, you must manually restart the archive server service on each server
after you create or modify a replication schedule.
System Information for Troubleshooting

Collecting Logs and Registry Settings
Increasing the Logging Level
Verifying SQL Authentication
Verifying the Communications Ports
Verifying Vault Database Replication Server Information
Verifying TCP Communication
Verifying SQL Communication
Verifying Communications Port Settings
34
Troubleshooting the Replication Setup
System Information for Troubleshooting

Prepare to troubleshoot replication problems by filling in as much of the following
information as possible. When performing the troubleshooting procedures, 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:
Enterprise PDM Version Installed:
Archive Server 1 Information
Operating System:
System Name:
IP Address:
Default Archive Server TCP Port:
Enterprise PDM Version Installed: Yes

No
Installed on Same Server as SQL: Yes

No
Archive Server 1 Information
Operating System:
System Name:
35
IP Address:
Default Archive Server TCP Port:
Enterprise PDM Version Installed: Yes

No
Installed on Same Server as SQL: Yes

No
Replicated File Vault Information
File Vault Name:
File Vault Database Name:
File Vault Login Type:
Collecting Logs and Registry Settings

When troubleshooting, the messages in the logs might indicate what is wrong.
1. To export registry settings:

a) Open the registry editor
b) Expand the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks
Enterprise\ArchiveServer
c) Right-click ArchiveServer and click Export.
d) Save the registry values to a file.
Rename the file to the server name for easy identification.
2. To save the archive server logs:

a) From an Enterprise PDM client, start the Enterprise PDM administration tool.
b) Right-click the archive server and click Show the Archive Server Log.
c) Click Copy log file (log toolbar).
36
d) Paste the copied log to a folder and rename it to the server name for easy
identification.
e) Repeat for any additional servers that replicate to the archive server.
You can also view the archive server log files in the event viewer on each server.
3. To save the Enterprise PDM client logs:

a) If a replication error is displayed on a client, open the Enterprise PDM administration
tool.
b) Expand Local Settings, right-click Log File, and click Copy.
c) Paste the log file to a folder and rename it to the client system name for easy
identification.
Increasing the Logging Level

You can increase the logging level on the archive server to include more detailed
information.
Every operation is logged.
1. Run regedit
ArchiveServer\
3. Right-click ArchiveServer and click New > DWORD Value.
4. For the DWORD Name, type EventLogLevel.
5. Right-click EventLogLevel and click Modify.
6. In the Edit DWORD Value dialog box:
a) For Value data, type FFFF.
b) For Base, select Hexadecimal.
c) Click OK.
Event logging now shows all events on the archive server.
To return to the normal level of event logging, remove the value of the EventLogLevel
DWORD.
Verifying SQL Authentication

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, open the SolidWorks Enterprise PDM Archive Server
dialog box by doing one of the following:
37
Start > All Programs > SolidWorks Enterprise PDM > Archive Server
Configuration.
SolidWorks Enterprise PDM, click Archive Server Configuration.
2. Click Tools > Default Settings.

3. In the Default Settings dialog box, under SQL login, click Change.
4. In the Change SQL User Login dialog box:
a) For SQL user login, re-type the SQL name used to access the database.
This is typically the sa user.
b) Retype the password in the Password and Confirm Password fields.
The password field is always shown empty, even if there is a password set.
c) Click OK.
5. Click OK to close the Default Settings dialog box.
6. To check the vault-specific properties, select the vault.
7. In the right pane, right-click the file vault name and click Properties.
8. In the Properties dialog box:
a) On the Login tab, review the SQL login section.
Use default SQL login must be selected for the initial replication to work.
b) If it is not, select it or click Change and provide the SQL user name and password
you specified in step 4.
c) Click OK.
9. Click Restart Server (SolidWorks Enterprise PDM Archive Server toolbar) to

restart the archive server service.
Verifying the Communications Ports

Because the archive servers and SQL server communicate over a defined TCP port, it is
important that no firewall is blocking these ports.
Between the two archive servers, default port 3030, or whichever port is designated in
the registry, must be open both ways.
From the replicated archive servers, default SQL port 1433 (or port 1434 for SQL instances)
must be opened to the SQL server system or to whichever port is designated.
Using Telnet, you can check whether the port is open to the remote servers.
To check whether the port is open:
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 IP_address_of_other_archive_server 3030
If the port is open, the Telnet screen should be blank and display a cursor.
38
3. Close the command prompt window.

4. Open another command prompt window and type:
TELNET Name_of_SQL_Server 1433
Use the SQL server name used in the registry and the applicable port.
If the port is open, the Telnet screen should be blank and display a cursor.
5. Close the command prompt window.
If the Telnet command fails, replication might fail. Check the following:
If the window shows Connection closed by foreign host, then the port is likely open,
but will not communicate with you.
It is also possible that the port on a firewall is open but the port on the internal machine
is closed.
If the window shows 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.
Verifying Vault Database Replication Server Information

The following procedure uses the management studio on the SQL server to ensure that
the file vault database contains valid archive server names.
It compares replication server information found in:
SQL Server Management Studio
The archive server registry
The Replication Settings dialog box (accessed from the Enterprise PDM Administration
tool)
1. Open Microsoft SQL Server Management Studio.

2. Connect to the server or instance hosting the replicated vault database.
3. In the left pane of the management studio dialog box, expand the vault database
and the Tables node.
4. Right-click dbo.ArchiveServers and click Edit Top 200 Rows.
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 receives a unique ID when you set it up to replicate the
vault.
5. Ensure that the system name of each server is entered in the ArchiveServerName
field.
The archive server system looks itself up by name in the table and tries to match an
entry. If no match is found, replication or login could fail.
6. If the system name is incorrect, edit the entry with the correct system name.
7. Exit Microsoft SQL Server Management Studio.
39
8. If you configured the setup to use IP-address-only communication (see the installation
guide), verify the name in the archive server registry:
a) Run regedit.
b) In the Registry Editor, expand the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\SolidWorks\Applications\PDMWorks
Enterprise\ArchiveServer
c) Right-click ServerName and click Modify.
d) Ensure that the ServerName Value data field contains the correct IP-address:
e) Close the Registry Editor.
The ServerName value must match the ArchiveServerName value in the

archiveservers table.
9. In the Enterprise PDM Administration tool:

a) Log in to the replicated vault.
b) Double-click Replication settings.
c) Verify that the system name or IP address entered for Source Server Address
is the same as the ArchiveServer name in SQL Server Management Studio.
Verifying TCP Communication

Perform the tests in this section between all replicated archive servers to ensure that
they can communicate over the network using correct addresses.
Ping on IP Address
1. Open a command prompt window.
2. Type PING IP_address_of_other_archive_server.
3. Verify that the other archive server replies.
4. Type PING IP_address_of_SQL_server.
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.
6. Verify the network setup.
Ping on System Name

2. Type PING Name_of_other_archive_server.
3. Verify that the other archive server replies and that the returned IP address is correct.
4. Type PING Name_of_SQL_server.
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.
6. Verify the DNS settings in the network or update the local HOSTS file.
40
Ping on Reverse Lookup IP Address

2. Type PING -a IP_address_of_other_archive_server.
3. Verify that the other archive server replies and that the returned name is correct.
4. Type PING -a IP_address_of_SQL_server.
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 it is using system names to communicate.
6. Verify the DNS settings in the network or update the local HOSTS file.
Verify Communication Stability

2. Type PING -t IP_address_of_other_archive_server.
This repeatedly pings the destination.
3. Click Ctrl+C to stop the pinging.
4. After some time, verify that the other archive server replies and there are no dropped
replies.
5. Type PING -t IP_address_of_SQL_server.
6. After some time, verify that the SQL server replies and there are no dropped replies.
If there are many dropped replies in the repeating ping, replication might fail or
become unreliable.
7. Verify the network setup and the cause of the network instability.
Verifying SQL Communication

Perform the tests in this section for both archive servers to verify that they can
communicate with the SQL file vault database. This should be tested from both archive
servers.
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:

2. Expand the following registry key:
ArchiveServer\Vaults.
3. Select the key with the vault name.
4. Check the Server value.
This is the name used to communicate with the SQL server.
41
Run an ODBC Test

1. Open the Control Panel and click System and Security > Administrative Tools.
2. Double-click Data Sources (ODBC).
3. In the ODBC Data Source Administrator, on the System DSN tab, and click Add to
create a new test source.
4. In the Create New Data Source wizard, select the SQL Server driver and click Finish.
5. In the first screen of the Create a New Data Source to SQL Server wizard:
a) For Name, type any name.
b) For Server, select the SQL server.
If the SQL server is not shown in the list, use the same name previously found in
the registry. The SQL server name is what the archive server uses to communicate.
c) Click Next.
6. On the second wizard screen:
a) Select With SQL Server authentication using a login ID and password
entered by the user.
b) Select Connect to SQL Server to obtain default settings for the additional
configuration options.
c) For Login ID and Password, type the SQL user (typically sa) and password that
was configured in the archive server settings.
d) Click Next to establish a connection to the SQL server.
7. If the connection succeeds, on the next screen:
a) Select Change the default database to.
b) Select the vault database name in the list.
c) Ensure that the following are checked:
Use ANSI quoted identifiers
Use ANSI nulls, padding and warnings
d) Click Finish.
8. On the ODBC Microsoft SQL Server Setup screen, click Test Data Source.
The SQL Server ODBC Data Source Test screen shows the test results.
9. Click OK to close the screen and click OK again to close the ODBC Microsoft SQL
Server Setup screen.
10. At the ODBC Data Source Administrator screen, you can remove or save the test
source. Click OK.
ODBC Test Failure

If the ODBC test fails, 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 Verifying Vault Database Replication
Server Information on page 39.
42
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 show an error code. Go to support.microsoft.com and search the
Knowledge base for a detailed explanation of the error.
Verifying Communications 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:

2. Expand the following registry key:
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).
4. If the values do not exist or are incorrect:
a) Create two new DWORD values.
b) Name them BroadcastPort and ServerPort.
c) Right-click each DWORD and click Modify.
d) For Value data, type 3030 and for Base select Decimal.
e) Click OK.
6. Restart the archive server service.
43

Launcher License

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Launcher License

Transféré par

Droits d'auteur :

Formats disponibles

REPLICATION GUIDE

SOLIDWORKS ENTERPRISE PDM 2014

5 Controlling Replication Performance........................................................................30

6 Determining Archive Replication Status...................................................................31

7 Enabling Archive Server Login Selection.................................................................33

8 Troubleshooting the Replication Setup....................................................................34

Verifying Vault Database Replication Server Information.................................................................39

Trademarks and Product Names for SolidWorks Products and Services

Copyright Notices for SolidWorks Standard, Premium, Professional, and

Copyright Notices for SolidWorks Simulation Products

Copyright Notices for SolidWorks Enterprise PDM Product

Copyright Notices for eDrawings Products

This chapter includes the following topics:

Setting Up the Primary Vault

Setting Up the Primary Vault

Installing the Enterprise PDM Software at the Remote Office

Setting Up Replication on the Main Server

To set up a scheduled recurring replication, configure a replication schema. See

To identify user accounts with the correct settings:

To replicate the main office vault:

2. In the Administration tool, click File > Add Server.

The Admin user has this permission by default.

If the connection between the servers cannot be made, a message appears.

To set up a scheduled recurring replication, configure a replication schema. See

The Admin user has this permission by default.

Replication Settings Dialog Box

Test When selected, enables the Test button described below.

Speed Specifies the current speed setting.

Speed Balances the replication load between three or more servers.

Remove Schemas Removes the selected replication schema.

Testing Replication Connections

If the result is not Test Successful, an error code is returned.

Connection Test Failures

Problem Results Archive Server Log information

Incorrect source The target server

Archive server The target server

Archive server Failed to connect

Problem Results Archive Server Log information

Installed archive The target server

Changing the Source Server Address

Configuring Replication Retries

1. Open the Registry Editor.

This chapter includes the following topics:

What Are File Archives

What Are File Archives

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

*.sldprt The latest version of a file is stored uncompressed with a version

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

How On-demand Replication Works

A client can only send and receive files that

This chapter includes the following topics:

00* 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

12. Click OK to close the schema dialog box.

New Replication Schema Dialog Box

Type the schema name.

Folders included in the replication schema.

Remove Folder Removes the selected folder from the list.

Connections to Select the servers between which replication should be

Replication interval for selected connection

0 /2 Run every other hour, every day