Windchill Diagnostic Utility

Guide
6.2.6, 7.0, 8.0, 9.x, 10.x, 11.x, 12.x
June 2021
Copyright © 2021 PTC Inc. and/or Its Subsidiary Companies. All Rights Reserved.

User and training guides and related documentation from PTC Inc. and its subsidiary companies (collectively
"PTC") are subject to the copyright laws of the United States and other countries and are provided under a
license agreement that restricts copying, disclosure, and use of such documentation. PTC hereby grants to the
licensed software user the right to make copies in printed form of this documentation if provided on software
media, but only for internal/personal use and in accordance with the license agreement under which the
applicable software is licensed. Any copy made shall include the PTC copyright notice and any other
proprietary notice provided by PTC. Training materials may not be copied without the express written consent
of PTC. This documentation may not be disclosed, transferred, modified, or reduced to any form, including
electronic media, or transmitted or made publicly available by any means without the prior written consent of
PTC and no authorization is granted to make copies for such purposes. Information described herein is
furnished for general information only, is subject to change without notice, and should not be construed as a
warranty or commitment by PTC. PTC assumes no responsibility or liability for any errors or inaccuracies
that may appear in this document.

The software described in this document is provided under written license agreement, contains valuable trade
secrets and proprietary information, and is protected by the copyright laws of the United States and other
countries. It may not be copied or distributed in any form or medium, disclosed to third parties, or used in any
manner not provided for in the software licenses agreement except with written prior approval from PTC.

UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN RESULT IN CIVIL

DAMAGES AND CRIMINAL PROSECUTION.

PTC regards software piracy as the crime it is, and we view offenders accordingly. We do not tolerate the
piracy of PTC software products, and we pursue (both civilly and criminally) those who do so using all legal
means available, including public and private surveillance resources. As part of these efforts, PTC uses data
monitoring and scouring technologies to obtain and transmit data on users of illegal copies of our software.
This data collection is not performed on users of legally licensed software from PTC and its authorized
distributors. If you are using an illegal copy of our software and do not consent to the collection and
transmission of such data (including to the United States), cease using the illegal version, and contact PTC to
obtain a legally licensed copy.

Important Copyright, Trademark, Patent, and Licensing Information: See the About Box, or copyright
notice, of your PTC software.

UNITED STATES GOVERNMENT RIGHTS

PTC software products and software documentation are “commercial items” as that term is defined at 48 C.F.
R. 2.101. Pursuant to Federal Acquisition Regulation (FAR) 12.212 (a)-(b) (Computer Software) (MAY 2014)
for civilian agencies or the Defense Federal Acquisition Regulation Supplement (DFARS) at 227.7202-1(a)
(Policy) and 227.7202-3 (a) (Rights in commercial computer software or commercial computer software
documentation) (FEB 2014) for the Department of Defense, PTC software products and software
documentation are provided to the U.S. Government under the PTC commercial license agreement. Use,
duplication or disclosure by the U.S. Government is subject solely to the terms and conditions set forth in the
applicable PTC software license agreement.
PTC Inc., 121 Seaport Blvd, Boston, MA 02210 USA
 Contents

Diagnostic Utility Guide Overview .................................................................................5

When to Run WinDU.............................................................................................7
Installing the WinDU Patch ....................................................................................7
How to Run WinDU .....................................................................................................8
Categories ...............................................................................................................13
Filtering and Dependencies........................................................................................17
Filtering .............................................................................................................18
Dependencies ....................................................................................................18
WinDU Diagnostic Tasks............................................................................................19
Index...................................................................................................................... 106

4 Windchill Diagnostic Utility Guide

 1
Diagnostic Utility Guide Overview
When to Run WinDU ...................................................................................................7
Installing the WinDU Patch...........................................................................................7

The Windchill Diagnostic Utility (WinDU) is a read-only utility that reports on

various aspects of the current state of a running Windchill or PTC FlexPLM
system. The set of reports generated depends on the current set of WinDU
diagnostic tasks (DTs) installed on the system.
Each diagnostic task reports on a different part of the system, and generates its
own output report (some generate no output if no data of interest is found). There
are three types of diagnostic tasks:
1. Information Only: These diagnostic tasks report on some aspect of the
system. Technical Support or another PTC department may request an
Informational diagnostic task be run to help make a decision about another
action.
2. Problem Identification: Identifies issues that need to be resolved before
taking some future action, such as upgrading to a new release. These often
involve some type of inconsistent or “dirty” data.
3. Problem Debug: Provides information used to debug a reported system issue.
These are likely to be executed at the request of PTC Technical Support to
identify the root cause of an existing problem.
Diagnostic tasks are shipped with major releases of Windchill products. They are
also shipped with maintenance releases, and some are available for download
from PTC’s Technical Support web site.

Supported Releases
WinDU is supported on the following Windchill suite product releases:

5
• R6.2.6 DSU 12 and later
• R7 M050 and later
• R8 M010 and later
• R9.0 FCS and later
• R9.1 FCS and later
• R10.0 FCS and later
• R10.1 FCS and later
• R10.2 FCS and later
• R11.0 FCS and later
• R11.1 FCS and later
• R11.2.0.0 and later
WinDU is also supported on the following PTC FlexPLM product releases:
• R9.2 M010
• R10.1 FCS and later
• R10.2 M030 and later

6 Windchill Diagnostic Utility Guide

When to Run WinDU
• Periodically to check for data issues that must be resolved
• Before an upgrade or migration to ensure that there are no data issues that
must be resolved to ensure successful completion of the upgrade
• After an upgrade, migration, or custom data load to ensure that no data issues
were introduced during the process
• After certain configuration or software updates, such as enabling security
labels or changing your data replication settings
• At the request of PTC

Installing the WinDU Patch

Download the Windchill Diagnostic Utility patch and follow the instructions in
the patch readme.
For more information, see:
• Windchill Upgrade and Migration Resource Page
• Windchill Diagnostic Utility and Windchill Repair Utility download page

Diagnostic Utility Guide Overview 7

 2
How to Run WinDU
Windchill server configured with Single Sign-On (SSO)
If the Windchill server is configured with Single Sign-On (SSO), you need to
update the wt.properties file before running WinDU. The
wt.properties file is located at <Windchill>/codebase.
Add the following values to the
com.ptc.windchill.upgrade.tools.windu.java.args property:
• -Dwt.httpgw.HTTPLogin.authPrefix=protocolAuth
• -Dwt.httpgw.HTTPLogin.enableAuthPrefix=true
Propagate the updates to the wt.properties file using xconfmanager utility.
The xconfmanager is a command-line utility that is used to add, remove, and
modify the properties in the Windchill property files and is located in the
<Windchill>/bin directory.
To add values to the property, run the following command: xconfmanager
--add <property_name>=<extra_property_value> -t
<property_file> -p
For example, xconfmanager --add
com.ptc.windchill.upgrade.tools.windu.java.args=
”-Dwt.httpgw.HTTPLogin.authPrefix=protocolAuth
-Dwt.httpgw.HTTPLogin.enableAuthPrefix=true” -t
codebase/wt.properties -p

8 Windchill Diagnostic Utility Guide

 Note
If the property files were updated by modifying the files directly, create a
backup of the related property files before executing the xconfmanager
command.

For running WinDU, instructions are the same for R6.2.6, R7, and R8; however,
there were some enhancements introduced starting with R7 which are outlined
below.
To launch WinDU, execute the WinDU script in a Windchill shell window.
• On WINDOWS this script is:
windu.bat

• On UNIX the script is:

windu.sh

• On LINUX you must edit the windu.sh file before running it. Perform the
following steps.
1. Open the windu.sh file in a text editor.
2. Change the following line:
#!/usr/bin/sh

to
#!/bin/sh

3. Save the file.

4. Enter the following command:
windu.sh

These scripts must be run from a Windchill shell running on the Windchill
installation's host. They cannot be run from a remote client. Your method server,
WebServer, and ServletEngine should be running to ensure the WinDU tasks
execute properly.
Running the commands listed above opens the first screen of the WinDU
application which offers a choice of diagnostic tasks to run under various
categories. Select the ones you would like to run (or deselect the ones you don't
want to run) using the checkboxes next to the names of the diagnostic tasks.

How to Run WinDU 9

Next, click Run, which will attempt to confirm that the WebServer, ServletEngine,
and method server are running. It will then prompt you to log into the Windchill
instance as an administrator. If this succeeds, the diagnostic tasks will run in
sequence.

10 Windchill Diagnostic Utility Guide

Once the diagnostic tasks complete, WinDU will inform you of the diagnostic
tasks which produced logged output, if any, and the paths to the log files.

How to Run WinDU 11

12 Windchill Diagnostic Utility Guide
 3
Categories
Diagnostic tasks will potentially appear in many categories. The All category
always exists. There may be additional categories created for ease of selection of a
group of diagnostic tasks.
The checkboxes located next to a category change whether all diagnostic tasks in
that category are selected or not. For example, you can select or clear all
diagnostic tasks by selecting or clearing the All category checkbox. Since
diagnostic tasks may appear more than once in the categorized list, if you change
the selected state of a diagnostic task, the change in selection is reflected on all
other list entries for that diagnostic task.

Note
Selecting and clearing the All checkbox is supported in releases prior to
Windchill 10.1.

13
Category Description Use
All All diagnostic tasks
Detailed Diagnostic Diagnostic tasks that Typically run only when
detect and identify a directed by PTC.
specific issue or set of
issues that do not apply to
other categories.
Information Only Diagnostic tasks that Run by an administrator
display information about to examine the Windchill
the Windchill system. installation or when
Tasks in this category requested by PTC.
typically do not have an
associated repair task.
Pre-Upgrade Mandatory Diagnostic tasks that Run on the source
detect corruptions or Windchill system
issues that would cause throughout the upgrade

14 Windchill Diagnostic Utility Guide

Category Description Use
upgrade failure or further process.
data corruption.
System Health Check Diagnostic tasks that Run on a production
verify the integrity and Windchill system on a
stability of a production regularly scheduled basis.
Windchill system. PTC recommends
running these tasks prior
to and after a system
upgrade.
Verification Suite Diagnostic tasks that Run on the target
detect corruptions on a Windchill system after an
Windchill system. upgrade, system
migration, or custom data
load.

Categories 15
Category Description Use
InService Post Upgrade Diagnostic tasks that Run only on the target
Validators verify that data in InService 6.0 system after
InService have been the upgrade from Service
migrated correctly from a Center 10.1 to InService
Service Center 10.1 to an 6.0.
InService 6.0 system.
Tasks in this category
ensure that EC3 data is
correctly referenced after
migration. The validator
will output valid results
only when executed
immediately after the
upgrade and before any
new carts, cart items,
orders, or order items are
created or migrated
objects are deleted.
Service Center 10.1 Diagnostic tasks that Run only on the
Validators verify the data in Windchill Service
Windchill Service Information Manager
Information Manager is system before executing
safe to be sent to the PETL process. The
Servigistics Service Servigistics Service
Center via the Publish Center Utilities Windchill
Extract, Transform, and Bulk Migrator Extractor
Load (PETL) process. must be installed and
Tasks in this category configured on the
check that the Windchill Windchill Service
Service Information Information Manager
Manager data conforms to system before any tasks
the Servigistics Service in this category can be
Center requirements. executed.

16 Windchill Diagnostic Utility Guide

 4
Filtering and Dependencies
Filtering ...................................................................................................................18
Dependencies...........................................................................................................18

17
Filtering
You can filter the list of diagnostic tasks that match a pattern by entering a string
or expression into the text field at the top of the list. Any string you enter will
automatically be surrounded with wildcards before elements are filtered. For
example, if you enter “foo”, the filtering will match all diagnostic tasks whose
string representation matches the expression *foo.*.

Note
Filtering does not exclude category names. All categories are always
displayed.

Dependencies
Some WinDU diagnostic tasks should only be run after one or more other
diagnostic tasks have been executed and the results show that no issues need to be
resolved. If a predecessor diagnostics task reports any issues, these must be
resolved before running the successor diagnostic task.
The following diagnostic tasks should only be executed after the successful
completion of one or more related diagnostic tasks:

Diagnostic Task Dependency Matrix

Predecessor Diagnostic Task Successor Diagnostic Task

Missing Master Domain Administered Objects Domain
Reference Check
Missing Master Null Container References Check

18 Windchill Diagnostic Utility Guide

 5
WinDU Diagnostic Tasks
A&D Part Instance Traceability Conformance Report
Diagnostic Task Description
The upgrade to Windchill Aerospace & Defense 9.1 consolidates the existing
(specialized) Configuration Management object model into standard object. The
new implementation strictly enforces conformance of allocated instances to the
appropriate traceability.
This task provides an informational report on any unallocated part instances that
do not conform to the default traceability defined on the base part. A&D Part
Instances called out in this report should be reviewed. There are two possible
scenarios for each A&D Part Instance: 1) when awaiting allocation into an
assembly and 2) when representing top level parts that will never be allocated
into an assembly. The primary focus of this report is to provide the means by
which the A&D Part Instances, representing top level parts, can be identified and
the default trace code corrected before upgrade and, after upgrade, only new
instances conforming to the default traceability can be created.
The A&D Part Instances listed in the report should be reviewed. Those A&D
Part Instances representing top level parts, which will never be allocated into an
assembly, represent the candidates for modification. If all the A&D Part
Instances are of the same traceability (e.g., serial numbered), then the base part
should be updated with the matching default trace code.
Intended Use
This diagnostic task should be executed:
• Before upgrading to Windchill Aerospace & Defense 9.1
Cabinet Based Data Container Alignment Conflict Report
Diagnostic Task Description
This diagnostic task reports all objects that are cabinet based but not foldered.
These objects are relevant to the migration because their cabinet references will

19
 Cabinet Based Data Container Alignment Conflict Report
likely be updated unless they are already located in the Default cabinet.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Cabinet Based Data Container Alignment Report
Diagnostic Task Description
This diagnostic task reports all objects that are cabinet based but not foldered.
These objects are relevant to the migration because their cabinet references will
likely be updated unless they are already located in the Default cabinet.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Cabinet Member Data Report
Diagnostic Task Description
This diagnostic task simply lists all the CabinetMember data in the system.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Case Table Cell Type Diagnostic Task
Diagnostic Task Description
This diagnostic task reports all CaseTable cells where the expression's type does
not match the parameter's type. Some CaseTables may have a type mismatch
where the cell is a String but should be an object. For example the String "123"
should be the number 123 and the NumberRange String "[1..100]" should be the
Interval [1:100].
Report all CaseTable cells where the column is null.
Report all CaseTable cells where the column is an invalid external reference. For
example, if it refers to “frontAxle. diameter” and there is no child part with
reference “frontAxle” or if there is such a child part and that part does not have a
parameter “diameter”.

20 Windchill Diagnostic Utility Guide

 Case Table Cell Type Diagnostic Task

Note
This diagnostic task is only relevant for Options and Variants functionality
within PDMLink.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Check Assigned Activity Template for WorkItems
Diagnostic Task Description
This diagnostic task reports if any workitems or tasks have assigned activities
that refer to a non-existent Assigned Activity template. It looks for data
corruption issues in WfAssignedActivityTemplate and
WfAdhocActivityTemplate tables. To fix the issues reported by this diagnostic
task, do one of following:
1. Restore missing activity template from database backup
2. Remove all processes of related workflow template
3. Terminate or delete existing processes from that template
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Check Change Status Indicator
Diagnostic Task Description
This diagnostic task detects if there are changeable objects that have a pending or
resulting change indicator but are not associated to any change object. It will
report in the DirectiveService logs if a changeable exists that needs to be
repaired, for example:
Tue 6/12/12 09:21:28: There are changeables whose pending and/or
resulting change indicator needs to be repaired.
Tue 6/12/12 09:21:28: Please run RepairChangeStatusIndicator task to fix
the issue.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

WinDU Diagnostic Tasks 21

 Check Change Status Indicator
Diagnostic Task Description
This diagnostic task detects if there are changeable objects that have a pending or
resulting change indicator but are not associated to any change object. It will
report in the DirectiveService logs if a changeable exists that needs to be
repaired, for example:
Tue 6/12/12 09:21:28: There are changeables whose pending and/or
resulting change indicator needs to be repaired.
Tue 6/12/12 09:21:28: Please run RepairChangeStatusIndicator task to fix
the issue.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Check Name Conflict In Reports From R9 to R10
Diagnostic Task Description
Checks for probable report name conflict between customized reports in 9.0 and
OOTB reports for 10.0. The winDU will report if an existing report will have
name conflict with the new 10.0 OOTB reports. A problem report will be logged
to advice the customer to rename or remove this report from the existing system
before upgrade.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Checked Out CAD Documents Check
Diagnostic Task Description
This diagnostic task checks if:
1. Any CAD documents are checked out
2. Any newly created CAD documents exist in personal folders
3. Any newly created objects exist in workspace

Note
CAD documents are required to be checked in for the upgrade to be
successful.

22 Windchill Diagnostic Utility Guide

 Checked Out CAD Documents Check
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Check Package Base Data Status
Diagnostic Task Description
This diagnostic task checks if package base data is loaded. A repair task may
need to be run based on the result of this check.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Check Part List Diagnostic Task
Diagnostic Task Description
This diagnostic task appears only if the Windchill Service Parts module (sisipcia)
is installed. It checks to see if any Parts List objects exist. It instructs the
customer to contact Technical Support in order to discuss manual steps needed to
perform the upgrade.
Intended Use
This diagnostic task should be executed:
• Before upgrading to 10.1 M020 (or later) from 10.1 M010 or earlier
• When requested by PTC
Check Project Monitor Templates Diagnostic Task
Diagnostic Task Description
Detects if the (ProjectMonitor) Report Template takes care of a dummy entry in
the Plan Activity table.
Intended Use
This diagnostic task should be executed:
• After update
• When requested by PTC
Check Project Monitor Items Templates Diagnostic Task
Diagnostic Task Description
Detects if the (ProjectMonitorItems) Report Template takes care of a dummy
entry in the Plan Activity table.

WinDU Diagnostic Tasks 23

 Check Project Monitor Items Templates Diagnostic Task
Intended Use
This diagnostic task should be executed:
• After update
• When requested by PTC
Check uniqueLinkId Errors on EPMMemberLink
Diagnostic Task Description
This Diagnostic task detects if there is any data corruption with respect to
uniqueLinkID filed on the EPM Document Usage Link, which may result in the
incorrect BOM when used in build process.
Intended Use
This diagnostic task should be executed:
• After performing an upgrade, system migration, or custom data load
• When requested by PTC
ChoiceRule Number Uniqueness Diagnostic Task
Diagnostic Task Description
This information task reports all ChoiceRule objects (ChoiceConstraint,
ChoiceEnable, and ChoiceMapping) where the object number is not unique. A
uniqueness constraint was added in PTC Windchill 10.2
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Classification Checkout Health Status
Diagnostic Task Description
This diagnostic task will check for the status of classification structure, whether
it is checked-out in Counterpart or not.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Consolidation Access, Notification, and Index Rules Report
Diagnostic Task Description
The upgrade to Windchill Aerospace & Defense 9.1 consolidates the existing
(specialized) Configuration Management object model into standard object.
Rather than require a step after upgrade, the site must perform this activity before
upgrade as it will not negatively impact the production system.

24 Windchill Diagnostic Utility Guide

 Consolidation Access, Notification, and Index Rules Report
This task provides a report on any Access, Notification, or Index Rules upon
which action is required in the Policy Administrator. These rules must be
removed from the WTProduct or FADProduct definitions and consolidated into
the existing definitions at WTPart, removed from FADProductConfiguration and
moved to WTProductConfiguration, or removed from FADProductInstance and
moved to WTProductInstance2. As WTPart, WTProduct,
WTProductConfiguration, and WTProductInstance2 items could not exist in a
Windchill Aerospace & Defense system, there is no end user impact to this
consolidation before upgrade.
Rules defined explicitly on soft types of FADProduct do not require any
additional action. Rules defined explicitly on other types of WTProduct are
handled in accordance with the standard upgrade procedures.
Intended Use
This diagnostic task should be executed before upgrading to Windchill
Aerospace & Defense 9.1.
Note
It should be executed again, after completing any required action to ensure
no further action is required.
Consolidation Object Initialization Rules Report
Diagnostic Task Description
The upgrade to Windchill Aerospace & Defense 9.1 consolidates the existing
(specialized) Configuration Management object model into standard object.
Rather than require a step after upgrade, the site must perform this activity before
upgrade as it will not negatively impact the production system.
This task provides a report on any Object Initialization Rules, within a container
template or actual instances of Object Initialization Rules, upon which action is
required in the Object Initialization Rules Administrator. These rules must be
removed from the WTProduct or FADProduct definitions and consolidated into
the existing definitions at WTPart. As WTPart and WTProduct items could not
exist in a Windchill Aerospace & Defense system, there is no end user impact to
this consolidation before upgrade.
Rules defined explicitly on soft types of FADProduct do not require any
additional action. Rules defined explicitly on other types of WTProduct are
handled in accordance with the standard upgrade procedures.

WinDU Diagnostic Tasks 25

 Consolidation Object Initialization Rules Report
Intended Use
This diagnostic task should be executed before upgrading to Windchill
Aerospace & Defense 9.1.

Note
It should be executed again, after completing any required action to ensure
no further action is required.
Consolidation Soft Attribute and Constraint Report
Diagnostic Task Description
The upgrade to Windchill Aerospace & Defense 9.1 consolidates the existing
(specialized) Configuration Management object model into standard object.
Rather than require a step after upgrade, the site must perform this activity before
upgrade as it will not negatively impact the production system.
This task provides a report on any Soft Attribute or Constraint Definitions upon
which action is required in the Type Manager. These definitions must be
removed from the WTProduct or FADProduct definitions and consolidated into
the existing definitions at WTPart. The FADProductInstance definition is
reviewed for soft attribute and constraint definition consolidation into
WTProductInstance2. The FADProductUsageLink definition is reviewed for soft
attribute and constraint definition consolidation into WTPartUsageLink. As
WTPart, WTProduct, WTPartUsageLink, and WTProductInstance2 items could
not exist in a Windchill Aerospace & Defense Module system, there is no end
user impact to this consolidation before upgrade.
Once attributes and constraints have been reviewed as appropriate to move to
WTPart, the following Type Manager steps are recommended:
1. Check out the wt.part.WTPart type definition. This automatically checkouts
all child type definitions.
2. Using Edit mode on WTPart, add the appropriate attributes exactly as defined
on WTProduct or FADProduct.
3. Using Edit mode on WTPart, add the appropriate constraints exactly as
defined on WTProduct or FADProduct.
4. Using Edit mode on WTProduct or FADProduct, select the attribute and
apply the Delete action if it is available.
Note
An attribute that is both inherited and defined at the class will only show
once, but applying the available delete action will result in the removal of
the defined attribute definition and the inherited attribute definition will
remain

26 Windchill Diagnostic Utility Guide

 Consolidation Soft Attribute and Constraint Report
5. Using Edit mode on WTProduct or FADProduct, use the Show Constraints
action to display all associated constraints. Apply the delete action to all
defined constraints.
Note
The action is only available on the defined constraints.
6. Check in the wt.part.WTPart type definition. This automatically checks in all
child type definitions.

Note
If the Type Manager does not display any constraints that can be deleted, but
the WinDU task reports them, please contact Tech Support for advanced
clean-up steps required.
Soft attributes and constraints defined only as soft types of FADProduct do not
require any additional action. Soft attribute and constraint definitions inherited
from WTPart, WTProductInstance2, or WTPartUsageLink are handled in
accordance with the standard upgrade procedures.
Intended Use
This diagnostic task should be executed:
• Before upgrading to Windchill Areospace & Defense 9.1

Note
It should be executed again, after completing any required action to ensure
no further action is required.
Container Names with Double Spaces
Diagnostic Task Description
This diagnostic task reports all container names and their remote IDs of type
container team with multiple spaces.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Container Structure
Diagnostic Task Description
This diagnostic task reports the mapping between the system container, cabinet,
or folder structure and the system domain structure. The report is available in
both an .xgml format and a .csv format. It provides a good picture of the overall
system. The .xgml output can be viewed in a tool such as yEd.

WinDU Diagnostic Tasks 27

 Container Structure
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Corrupt Family Table Check
Diagnostic Task Description
This diagnostic task finds problems with the Pro/ENGINEER family tables.
Intended Use
This diagnostic task should be executed when requested by PTC.
Corrupt Latest Iteration Report
Diagnostic Task Description
This diagnostic task checks for corruption in the latestiterationInfo column in
Iterated tables in the database. It reports the tables which exhibit this corruption.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Corrupt Share Access
Diagnostic Task Description
This diagnostic task identifies corrupt share access permissions resulting from
(1) residual share access permissions for shares that no longer exist and (2)
unspecified owner share access permissions (where the target container
pertaining to share access is not specified). These problems can be resolved by
running the Corrupt Share Access Repair Task.
Intended Use
This diagnostic task should be executed when requested by PTC.
Corrupt WorkItem Access Diagnostic Task
Diagnostic Task Description
This diagnostic task detects an issue dating back to creation of the WTAclEntry
table's "owner" column at Windchill 7.0. The owner field was not properly set
for some workitem-related permission. The permissions are still available to the
assignee, but don't get deleted when the work item is completed because the
owner field doesn't match the work item. Thus, the assignee continues to have
the permissions originally assigned by the work item forever. This diagnostic
task also finds any ad hoc permission (WTAclEntry's) which are affected by this
behavior. If corrupted entries are found, the customer should execute the

28 Windchill Diagnostic Utility Guide

 Corrupt WorkItem Access Diagnostic Task
CorruptWorkItemAccessRepairTask to correct the workitem owner fields.
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
Count Rows Per Table
Diagnostic Task Description
This diagnostic task reports the count of rows in each database table.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Note
If during an upgrade procedure it is necessary to contact PTC Technical
Support and they request upgrade logs, this report should be included
with those logs.
Count the number of usage links with the blank reference field
Diagnostic Task Description
This diagnostic task reports the number of usage links with a blank reference
field.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Dangling Export Record Check
Diagnostic Task Description
This diagnostic task finds all DangingExportRecords in the database (dangling: if
an ExportRecord has it’s reference to it’s Package as zero or nullified then the
ExportRecord is considered dangling). It then gives a list of ExportRecords that
are dangling.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

WinDU Diagnostic Tasks 29

 Dangling PBO Ref
Diagnostic Task Description
This diagnostic task is designed to check all workflow tasks (workitems) for any
references to a primary business object (PBO) that does not exist. The output of
this would be logged to a file <WinDU logs directory>\DanglingPBORef.log.
The output would list the ID, name, and status of every work item with a
dangling PBO reference, name, state, and ID of associated workflow process,
associated workflow template name, Object/Version reference of the missing
PBO object.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Dangling SyncInfo Diagnostic Task
Diagnostic Task Description
This diagnostic task identifies dangling SyncInfo records (SyncInfo records
which do not reference a ExportRecord). In some circumstances where a delivery
is removed, it may be possible for a SyncInfo record to exist without its
corresponding ExportRecord to exist (that is, the SyncInfo record is left
dangling) This diagnostic task identifies dangling SyncInfo records. The
DanglingSyncInfoRepairTask is the associated repair task to remove any
dangling records identified by this task.
Intended Use
This diagnostic task should be executed when requested by PTC
Database Index Utility
Diagnostic Task Description
This diagnostic utility analyzes database indexes to ensure that they are not too
long for database limitations. This data could then be used to prevent truncation
of data when column lengths are reduced.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Database Object Validity Check
Diagnostic Task Description
This diagnostic task lists out all the invalid database objects owned by the
Windchill Oracle user. To find out if an Oracle package reported by the Database
Object Validity Check WinDu task exists in the current Windchill release, check

30 Windchill Diagnostic Utility Guide

 Database Object Validity Check
the reported invalid packages against the following folder to evaluate if a
package has become obsolete:
db/sql/wnc/Foundation/nonmodeled/procedures/
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC

Note
This task does not need to run on SQL Server.
Deprecated Classes
Diagnostic Task Description
This diagnostic task detects deprecated classes in the system. For now, it only
looks for ConfigurationItem and if it contains any data, it suggests running the
Config2Master tool. This WinDU task is to make aware of the presence of the
data in ConfigurationItem and the existence of the Config2Master tool that
allows customer to convert the 8.0 Foundation objects into target release
compatible objects.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Access Policy Rules for SavedViewInfo Objects
Diagnostic Task Description
This task reports any access policy rules for SaveViewInfo objects in Site/
Default domain that was used by the "Relationship Explorer feature" which got
retired in Windchill 11.1
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Analysis Activities that are Orphans
Diagnostic Task Description
Generates a report of any orphaned analysis activities that includes their
associated affected data.

WinDU Diagnostic Tasks 31

 Detect Analysis Activities that are Orphans
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Change Tasks which have been Orphaned
Diagnostic Task Description
This diagnostic task finds out if there are any orphaned Change Tasks on the
system. An orphaned Change Task is a change task that is not related to a
Change Notice.
This diagnostic task will report the details about any orphaned Change Tasks. If
no orphaned change tasks are found, it will report that none are found. If there
was an orphaned change task found, it will look up all of the associated Affected
and resulting items that are associated with the change task. It will print off the
names of the Change Task that is orphaned along with all of the affected and
resulting items. This case was found to occur because there was a
reviseChangeActivities service API which existed in 9.1 and caused the
corruption.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Checked-out Objects to be Changed
Diagnostic Task Description
Generates a report of any objects to be changed that are checked out and
associated to a change object.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Checked-out Objects to be Promoted
Diagnostic Task Description
Generates a report of any objects to be promoted that are checked out and
associated to a promotion request.
Intended Use
This diagnostic task should be executed:
• After upgrade from 9.0 to a later release
• When requested by PTC

32 Windchill Diagnostic Utility Guide

 Detect Custom Percent QOM Data
Diagnostic Task Description
This diagnostic task detects custom Quantity of Measure (QOM) percentage data
that may conflict with Windchill 11 OOTB QOM percentage data. In Windchill
11.0 and later, the QOM percentage for graphical attributes is calculated using
the conversion coefficient 1/100. If you are upgrading to Windchill 11.0 or later
and have custom QOM percentage defined in your system, the attributes using
this percentage may show a different value due to conversion factor mismatch.
For example, if the QOM percentage was 90% earlier, based on the conversion
coefficient, after upgrade the QOM percentage changes to 9%.
By default, this task tries to locate the date when you upgraded to Windchill 11.0
or later. Based on this date, it calculates the data that needs to be repaired. If you
wish to override this date, you can provide the new date for the
Windu.QOMPercentDate property in dd-mm-yyyy format in the
wt.properties file before running this task.
Intended Use
This diagnostic task should be executed:
• After upgrade
Detect Deleted Sub Type Issues
Diagnostic Task Description
When a subtype definition is deleted through the Type Manager, Windchill
retains the instances of the deleted subtype. Before implementing a fix to SPR
2118451, the values of inherited standard or global attributes on the instances of
the deleted subtype, as well as entries in the table LWCColumnAllocation, may
get deleted from the database. This WinDU task will find deleted subtypes that
had inherited attributes and which may have been impacted by this SPR. If you
would like to salvage these instances, you can use this WinDU to identify
impacted types. However, it may identify false positives. It is up to you to
determine whether an identified issue is a false or true positive. If you need to
retain instances of no-longer-valid subtypes, the recommended approach is to
make these subtypes instantiable rather than deleting them.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Incorrect Domain Inheritance in DomainAdministered
Foldered Objects
Diagnostic Task Description
This task detects incorrect domains in foldered objects that should inherit their
domain from the parent folder.

WinDU Diagnostic Tasks 33

 Detect Incorrect Domain Inheritance in DomainAdministered
Foldered Objects
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Incorrect Parent Folder Settings in Foldered Objects
Diagnostic Task Description
This task detects incorrect parent folder information in foldered objects.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Invalid CounterPartIds
Diagnostic Task Description
This task is only applicable to sites with Windchill PartsLink installed.
This diagnostic task detects invalid CounterPartIds present in the Counterpart
content.xml file. The XML file is found in the master classification ZIP file that
is exported from the Counterpart. The XML file should be in the following
location: <Windchill>/temp/CounterPart. The task also reviews the
StringDefinition table and detects invalid internal names of attributes.
If invalid CounterPartIds are detected, the “Correct Invalid CounterPartIds”
repair task should be run. Invalid internal attribute names will be taken care of
automatically during the upgrade process.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Note
Uncheck this diagnostic task when Windchill PartsLink is not installed on the
server.
Detect Invalid SupportingDataFor Links
Diagnostic Task Description
This diagnostic task creates a report listing all invalid SupportingDataFor links.
A SupportingDataFor link is valid if the part or EPM document of the annotation
or mark-up is associated to a change object as an affected object.

34 Windchill Diagnostic Utility Guide

 Detect Invalid SupportingDataFor Links
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
Detect Issues in Specification / Requirement Types
Diagnostic Task Description
This diagnostic task verifies default subtype of Abstract Specification and
Requirement types that are present in Windchill. It also detects additional
subtypes available in Windchill which need to be converted for Integrity
integration.
Detailed instructions are listed in the Windchill Help Center under Integration
with Other Applications > Windchill Requirements Management > When
Upgrading From a Prior Release of Windchill.
Intended Use
Perform this task when upgrading from a prior release of Windchill where
Windchill Requirements Management is installed with either Windchill
PDMLink or Pro/INTRALINK
This diagnostic task should be executed:
• Pre-update and pre-upgrade
• Post-installation
Detect Missing Domains
Diagnostic Task Description
This diagnostic task detects missing domains referenced in queue entries.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Detect Missing or Duplicate Entries in IterFolderMemberLink Table
Diagnostic Task Description
This diagnostic task reports any IteratedFoldered objects that either don’t have
the required entry in the IteratedFolderMemberLink table or that have multiple
entries in the table. A valid IteratedFoldered objects has one and only one entry
in the IteratedFolderMemberLink table. For each IteratedFoldered sub-type, it
will first report any objects that lack an entry in the IteratedFolderMemberLink
table, or will write a message saying there are no objects of that type lacking an
entry. Then, for the same subtype, it will report any objects having multiple
entries in the IteratedFolderMemberLink table, or will write a message saying

WinDU Diagnostic Tasks 35

 Detect Missing or Duplicate Entries in IterFolderMemberLink Table
there are no objects of that type having multiple entries.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Detect Missing WfAssignedActivityTemplate for Change
Management WorkItems
Diagnostic Task Description
This diagnostic task find out all change management related workitems which
contain reference to WfAssignedActivity for which corresponding
WfAssignedActivityTemplate is missing in database.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Detect Missing Audits for Change Object Workitems
Diagnostic Task Description
The diagnostic task detects missing WfVotingEventAudit objects corresponding
to workitems for change objects in the system. The task will generate a report of
missing WfVotingEventAudit objects corresponding to workitems for change
objects in the system. This task will help to determine if the migrator
“MigrateProcessVariables” will be executed successfully during upgrade.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

Detect Orphan Default Value and Group Memberships

Diagnostic Task Description
This diagnostic task detects unwanted LWCGroupMembership,
LWCAttributeDefaultValue, LWCPropertyValue and
LWCLocalizablePropertyValue records
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

36 Windchill Diagnostic Utility Guide

 Detect Saved Searches and Histories Having Old LDAP Entries
(LDAP Domain or Base DN) OR WebApp Names
Diagnostic Task Description
Diagnostic task that detects saved searches and histories having old LDAP
entries (LDAP domain or Base DN) OR WebApp names which should be
modified so as not to impact the saved searches and histories having the principal
criteria. The following properties must be set or the task will not run, as the
utility reads the new and old domain values from these properties and updates
the saved search accordingly:
com.ptc.windchill.search. Synopsis:
sourceAdminBaseDn Defines the administrative Base DN
value for the source server when
executing specific WinDU tasks.
Description:
This property should only be used with
the following WinDU tasks:
• Detects saved searches/histories
having old LDAP entries (LDAP
domain or Base DN) OR WebApp
name.
Provide a value (in lowercase) for
administrative Base DN of the source
server. You can find this value from the
LDAP of the source server. This
property supports multiple values. In
cases with more than one value, use a
pipe symbol (|) to separate values. For
example, if the administrative Base DNs
are windchill_9.1 and
windchill_9.2, you can define them
as follows: windchill_
9.1|windchill_9.2.
com.ptc.windchill.search. Synopsis:
sourceEnterpriseBaseDn Defines the enterprise Base DN value for
the source server when executing
specific WinDU tasks.
Description:
This property should only be used with
the following WinDU tasks:

WinDU Diagnostic Tasks 37

 Detect Saved Searches and Histories Having Old LDAP Entries
(LDAP Domain or Base DN) OR WebApp Names
• Detects saved searches/histories
having old LDAP entries (LDAP
domain or Base DN) OR WebApp
name.
Provide a value (in lowercase) for
enterprise Base DN of the source server.
You can find this value from the LDAP
of the source server. This property
supports multiple values. In cases with
more than one value, use a pipe symbol
(|) to separate values. For example, if the
enterprise Base DNs are windchill_
9.1 and windchill_9.2, you can
define them as follows: windchill_
9.1|windchill_9.2.
com.ptc.windchill.search. Synopsis:
targetAdminBaseDn Defines the administrative Base DN
value for the target server when
executing specific WinDU tasks.
Description:
This property should only be used with
the following WinDU tasks:
• Detects saved searches/histories
having old LDAP entries (LDAP
domain or Base DN) OR WebApp
name.
Provide a value (in lowercase) for
administrative Base DN of the target
server. You can find this value from the
LDAP of the target server.
com.ptc.windchill.search. Synopsis:
targetEnterpriseBaseDn Defines the enterprise Base DN value for
the target server when executing specific
WinDU tasks.
Description:
This property should only be used with
the following WinDU tasks:

38 Windchill Diagnostic Utility Guide

 Detect Saved Searches and Histories Having Old LDAP Entries
(LDAP Domain or Base DN) OR WebApp Names
• Detects saved searches/histories
having old LDAP entries (LDAP
domain or Base DN) OR WebApp
name.
Provide a value (in lowercase) for
enterprise Base DN of the target server.
You can find this value from the LDAP
of the target server.
com.ptc.windchill.search. Synopsis:
sourceDefaultLdapAdapter Defines the default LDAP adapter value
for the source server when executing
specific WinDU tasks.
Description:
This property should only be used with
the following WinDU tasks:
• Detects saved searches/histories
having old LDAP entries (LDAP
domain or Base DN) OR WebApp
name.
Provide a value for default LDAP
adapter of the source server. You can
find this value from the LDAP of the
source server or from the
wt.properties file for the source
server. This property supports multiple
values. In cases with more than one
value, use a pipe symbol (|) to separate
values. For example, if the default
source adapters are
com.ptcnet.ptc.com and
com.abc.com, you can define them as
follows:
com.ptcnet.ptc.com|com.abc.
com.
com.ptc.windchill.search. Synopsis:
sourceEnterpriseLdapAdap Defines the enterprise LDAP adapter
ter value for the source server when
executing specific WinDU tasks.
Description:

WinDU Diagnostic Tasks 39

 Detect Saved Searches and Histories Having Old LDAP Entries
(LDAP Domain or Base DN) OR WebApp Names

This property should only be used with

the following WinDU tasks:
• Detects saved searches/histories
having old LDAP entries (LDAP
domain or Base DN) OR WebApp
name.
Provide a value for enterprise LDAP
adapter of the source server. You can
find this value from the LDAP of the
source server or from the
wt.properties file for the source
server. This property supports multiple
values. In cases with more than one
value, use a pipe symbol (|) to separate
values. For example, if the enterprise
source adapters are
com.ptcnet.ptc.com and
com.abc.com you can define them as
follows:
com.ptcnet.ptc.com|com.abc.
com.
Intended Use
This diagnostic task should be executed:
• After upgrade or after rehosting
Detect Workflow Processes Having Unresolvable PBO Ref
Diagnostic Task Description
Diagnostic task that detects all workflow processes that have references to a
primary business object (PBO) that does not exist in the database.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Domain Administered Objects Domain Reference Check
Diagnostic Task Description
This diagnostic task checks all Domain Administered objects for Domain
Reference and reports any Domain Administered objects with a missing domain.

40 Windchill Diagnostic Utility Guide

 Domain Administered Objects Domain Reference Check
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Note
Dependency: This diagnostic task should only be executed after the
Missing Master Discovery Tool Diagnostic Task has been executed
successfully.
Diagnose DomainAdministered Objects In Wrong Domain
Diagnostic Task Description
This diagnostic task will determine if there are any DomainAdministered objects
that are supposed to inherit their administrative (security) domain from their
parent folder, but are assigned instead to a different administrative domain. This
problem will occur only if the domain of a folder was changed using the Edit
Folder action in Windchill 10.0 FCS or 10.0 M010.
Intended Use
This diagnostic task should be executed:
• Before upgrade from Windchill 10.0 FCS or 10.0 M010
Note
This task is not available to customers using Windchill 10.2 M030 or
later. Customers who have Windchill 10.2 M030 or later should use the
“Detect incorrect domain inheritance in DomainAdministered Foldered
objects” diagnostic task instead.
• When requested by PTC
Diagnostic for Assembly Features for Representations
Diagnostic Task Description
This Diagnostic task will detect improperly migrated Representations. These
affected representations will produce slightly aberrant behavior when viewed. To
reproduce do the following: When viewing the Part Structure in the Windchill
Part Information page > Structure > Visualization tab, the unmodified part-level
Representations are displayed, instead of the modified Assembly-level
viewables. This issue is affecting parts structures with assembly-level
representation created at releases prior to Windchill 10.2 M030. Occurs when
viewing a Dynamic Part Structure that includes Assembly Level Features. For
more information, see CS238443.

WinDU Diagnostic Tasks 41

 Diagnostic for Assembly Features for Representations
Intended Use
The diagnostic task should be executed for systems having completed a
migration to releases Windchill 10.2 M030 and later.
Domain Policy Rule
Diagnostic Task Description
This diagnostic task reports all of the policy rules in each Administrative Domain
for the entire system.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Domain Structure
Diagnostic Task Description
This diagnostic task outputs the entire Administrative Domain structure for the
system.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Duplicate Change Links Diagnostic Task
Diagnostic Task Description
Customer reported duplicate links, and one of the root causes was a regression in
common components code. This diagnostic task detects duplicates of the
following links:
• wt.change2.ReportedAgainst
• wt.change2.RelevantRequestData2
• wt.change2.AffectedActivityData
• wt.change2.ChangeRecord2
• wt.change2.SubjectProduct
• wt.change2.ProblemProduct
• wt.change2.IssueImplementedBy
• wt.change2.FormalizedBy
• wt.change2.AddressedBy2
• wt.change2.HangingChangeLink
• wt.change2.SupportingDataFor

42 Windchill Diagnostic Utility Guide

 Duplicate Change Links Diagnostic Task
Intended Use
This diagnostic task should be executed:
• Before upgrade (recommended)
• After upgrade
Duplicate ChoiceMappableChoiceLink Diagnostic Task
Diagnostic Task Description
In PTC Windchill 11.0, ChoiceMappableChoice was changed from pointing to
the Choice to pointing to the ChoiceMaster. This diagnostic task reports all
ChoiceMappableChoiceLinks that have duplicates in the source system.
Intended Use
This diagnostic task should be executed:
• Before upgrade
Duplicate IBA Values Check
Diagnostic Task Description
This diagnostic task is used to detect CAD documents that contain duplicate IBA
values. Problem CAD documents can be fixed with the Delete Duplicate IBA
Values Repair Task.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Duplicate IDA2A2
Diagnostic Task Description
This diagnostic task reports duplicate IDA2A2's across the Windchill schema.
This diagnostic task can be used in combination with the ID Sequence Analysis
diagnostic task.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Duplicate OptionSetMemberLink Diagnostic Task
Diagnostic Task Description
In PTC Windchill 11.0, OptionSetMemberLink was changed from pointing to the
Choice to pointing to the ChoiceMaster. This diagnostic task reports all
OptionSetMemberLinks that have duplicates in the source system.

WinDU Diagnostic Tasks 43

 Duplicate OptionSetMemberLink Diagnostic Task
Intended Use
This diagnostic task should be executed:
• Before upgrade
Duplicate Recent Update Check Diagnostic Task
Diagnostic Task Description
This diagnostic task checks for duplicate entries in the RecentUpdate table.
Records in this table are duplicate if they have the same combination of "List
name", "Owner", and "Business object" fields.
Under certain conditions, the system erroneously allowed "duplicate" records to
be created in the RecentUpdate table. The source of the problem has since been
addressed, but these tools are provided to resolve any remaining data issues.
Duplicate entries can be problematic and must be addressed by running the
DuplicateRecentUpdateCleanupMigrator utility.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Duplicate Shares
Diagnostic Task Description
This diagnostic task reports the number of duplicate shares, which are shares of
the same object to the same target container.

Note
Upgrade fails at the Add Constraints step if duplicates are not resolved before
the upgrade.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Duplicate Table Column Data Check
Diagnostic Task Description
This diagnostic task will check a set of columns for the presence of duplicate
data. The list of tables and columns to check is loaded from a file on the
classpath located at wt/pds/DuplicateTableColumnDataCheck-DB.txt where DB
is replaced with Oracle or SQLServer depending on your currently configured
database connection.

44 Windchill Diagnostic Utility Guide

 Duplicate Table Column Data Check
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Duplicate Ufid Entries
Diagnostic Task Description
This diagnostic task checks for the duplicate entries present in
OwningRepositoryLocalObject and RemoteObejctInfo Tables. The diagnostic
task reports duplicate entries in OwningRepositoryLocalObject with the same
IDA3B5 pointing to different or same repository and also duplicate entries in
RemoteObjectInfo table with the same IDA3A3 value.

Note
Upgrade fails at the Add Constraints step if duplicates are not resolved before
the upgrade.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Duplicates in Control Branch
Diagnostic Task Description
This diagnostic task finds duplicates for the Control Branch.

Note
Upgrade fails at the Add Constraints step if duplicates are not resolved before
the upgrade.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
ECAD Application Data Report
Diagnostic Task Description
This diagnostic task finds ECAD documents that have content without an
assigned category. The task looks for ECAD EPM documents of the following
types: “ECAD-BOARD”, “ECAD-SCHEMATIC”, and “ECAD-CONTENT”.
After identifying the documents with an assigned category, you can run the
ECAD Application Data Repair Task to assign categories.

WinDU Diagnostic Tasks 45

 ECAD Application Data Report
Intended Use
This diagnostic task should be executed:
• After upgrade from a release prior to Windchill 10.0, but before opening the
Windchill Workgroup Manager client
• When requested by PTC
EPMDoc SubType Check
Diagnostic Task Description
This diagnostic task will determine the number of rows in the
EPMDOCUMENTMASTER table which needs to have the docSubType reset to
NULL This will happen for the following conditions:
1. The docSubType is OTHER and authoring application is PROE. This value
should have been NULL but was set as OTHER in earlier releases.
2. The authoringApplication is PROE, the docType is CADCOMPONENT, and
the docSubType is SOLID.
3. The authoringApplication is PROE, the docType is CADASSEMBLY, and
the docSubType is DESIGN.
The docSubType must be reset to NULL to work properly with the workgroup
manager. Issues can be fixed with the UpdateEPMDocSubtype repair utility. It
will report what it is checking (as listed in 1, 2, 3 from above), followed by the
number of rows that need to be corrected, if any.
Intended Use
This diagnostic task should be executed when requested by PTC.
ECAD Content Definition Report
Diagnostic Task Description
This diagnostic task reports any ECAD content definitions that need to be
decoded before upgrading from Windchill 10.1 to Windchill 10.2. Issues can be
fixed with the ECADContentDefinitionRepairTask utility.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
ECAD EPM Document Checkout Status Report
Diagnostic Task Description
This diagnostic task reports any ECAD EPM documents that are checked out.
These must either be checked in or an “undo checkout” must be performed
before the upgrade. If this is not done before the upgrade, an “undo checkout”

46 Windchill Diagnostic Utility Guide

 ECAD EPM Document Checkout Status Report
operation will be performed during the upgrade and any changes will be lost.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
ECAD Report Shared And PDM Checked Out
Diagnostic Task Description
This diagnostic task will report shared and PDM checked out ECAD EPM
documents.
The problems reported by this diagnostic task may cause upgrade failure or
malfunction. If meaningful objects, like boards or schematics, are included in the
report, it must be dealt with before upgrade. Components, conversely, will cause
garbage to be left by the upgrade, but it is not dangerous to the process. Such
garbage can be cleaned after upgrade as well, and an after upgrade version of this
task exists that would help to do it.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
ECAD Validate Data
Diagnostic Task Description
ECADValidateData will find and report several different issues:
1. A source document having no iterations
2. A board or a schematic that does not belong to an as stored configuration
3. As stored configuration that don’t have either board or schematic
4. Absent part usage links between assembly parts and board or schematic part
masters
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
• Whenever any issue is reported, an ECAD Repair Data WinRU must follow.
(ECAD Repair Data WinRU is available in 9.1 only; in earlier releases every
problem should be handled manually.)

WinDU Diagnostic Tasks 47

 Empty Table Report
Diagnostic Task Description
The upgrade to Windchill Aerospace & Defense 9.1 consolidates the existing
(specialized) Configuration Management object model into standard object
model that has been enhanced with new functionality. It is expected that a
Windchill Aerospace & Defense will not contain any WTPart, WTProduct,
WTProductConfiguration, WTProductInstance2, or WTPartUsageLink items.
This diagnostic task reports any of these items encountered as they will become
visible after the upgrade to 9.1.
Intended Use
This diagnostic task should be executed before upgrading to Windchill
Aerospace & Defense 9.1.
EPM Document Number Conflict Check
Diagnostic Task Description
In the current release, CAD document numbers contain all upper case characters.
This is consistent with WTParts and WTDocuments. Before Release 9.0, CAD
document numbers could contain any combination of upper and lowercase.
Conflicts can arise when the mixed case becomes uppercase. A tool is provided
that can detect these conflicts before upgrade.
Intended Use
This diagnostic task should be executed when requested by PTC.
EPM Document CAD Name Conflict Check
Diagnostic Task Description
The EPMDocCADNameConflictCheck checks for any conflicts on
EPMDocumentMaster CADName that could occur during upgrade. Conflicts can
occur due to the following changes of CADName during upgrade:
1. In 8.0, CADName is modified to be unique in a project or PDM. The
authoring application is not a uniqueness constraint. Therefore, CADName is
unique for all Authoring Applications. The option to enforce uniqueness
based on authoring application has been removed. A tool is provided for the
source system to detect conflicts before upgrade. Any documents that do not
have CADNames receive CADNames during the upgrade process.
2. In 9.0, CADName is modified to be unique irrespective of case. Some
CADNames will be changed during upgrade. For example, the CADName of
family table instances with authoring application Solidworks, will have the
extension from the generic appended.
3. Beginning in 9.1 M050, CADNames that were created in 8.0 without
extensions for UG NX, SolidWorks, CATIA V5, AutoCAD, and Inventor will
have extensions added. If the addition of the extension will cause the

48 Windchill Diagnostic Utility Guide

 EPM Document CAD Name Conflict Check
CADName conflicts or cause the CADName to be too long, an error is
reported.
Intended Use
This diagnostic task should be executed before upgrade.
EPMDocumentVerifiedColumnCheck
Diagnostic Task Description
This diagnostic task will determine the number of rows in EPMDocument table
which has ‘VERIFIED’ column value set to 0 (zero) and one or more of the
following conditions:
1. The authoringAppVersion column in EPMDOCUMENT table is NULL.
2. The authoringAppVersion column in EPMDOCUMENT table is 1 (one).
3. The idA3B10 column in EPMDOCUMENT table refers to the idA2A2
column of EPMAuthoringAppVersion having version name as J-01.
These rows correspond to the 3rd party CAD Documents migrated from pre-
Windchill 10.0 releases and Pro/Engineer CAD Documents migrated from pre-
Windchill 8.0 releases. The “verified” flag must be set to 1 (one) on these
documents so that the part associated to these document can be built.
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
ESI Schema Detector
Diagnostic Task Description
Reports the existence of ESI schema on the source server if the corresponding
tables exist in the database but no ESI installation exists. This report assumes
significance if an upgrade from a version before Windchill 10.0 (having no ESI)
to 10.0 or beyond is desired and ESI is to be installed on the target server.
Intended Use
This diagnostic task should be executed:
• During upgrade
The task is to be run only when upgrading from a version before Windchill
10.0 (that does not include Windchill Enterprise Systems Integration (ESI))
to 10.0 or beyond, when ESI is to be installed on the target server. In other
words, it should be run before running the PSI for installing ESI on the target
server.
• When requested by PTC

WinDU Diagnostic Tasks 49

 Export Strings for Type Conversion
Diagnostic Task Description
The upgrade to Windchill Aerospace & Defense 9.1 provides a new
implementation for CDRL/SDRL items with significantly enhanced product
capabilities. The App Code, DD 250 Required, and Frequency attributes will be
converted from free-form text strings to enumerated types. The Distribution
Statement Required attributed also will be added to the new implementation.
This task exports a single XML file, called CDRLStringToEnumTypeMap.xml,
into the WinDU logs directory of your installation:
Example on WINDOWS: %WT_HOME%\WinDU\logs
Example on UNIX: %WT_HOME%\WinDU\logs
Additional required instructions for this file can be found in the Windchill
Upgrade Guide.
Intended Use
This diagnostic task should be executed before upgrading to Windchill
Aerospace & Defense 9.1
External Cart Items Validator
Diagnostic Task Description
This diagnostic task ensures that all external cart items were successfully
migrated to the new InService 6.0 system. In Service Center 10.1, external cart
items are of type SCExternalCartItem. Starting in InService 6.0, external cart
items are of type SCEExternalCartItem. This task will output valid results only
when executed immediately after the upgrade and before any new external cart
items are created or migrated ones are deleted.
This task:
1. Validates that the number of external cart items of type SCExternalCartItem,
associated with shopping carts, is the same as the number of external cart
items of type SCEExternalCartItem, associated with shopping carts. A failure
message is logged if the counts do not match.
2. Validates that the number of external cart items of type SCExternalCartItem,
associated with orders, is the same as the number of external cart items of
type SCEExternalCartItem, associated with orders. A failure message is
logged if the counts do not match.
3. Checks for any external cart items in SCExternalCartItem that are not in
SCEExternalCartItem. A log is created of any external cart items that are not
found. If all external cart items are found, a success message is logged.
4. Checks for any records of SCEExternalCartItem that do not have the correct
class name: com.ptc.sce.cart.SCEExternalCartItem. If any
records are found, a log is created.

50 Windchill Diagnostic Utility Guide

 External Cart Items Validator
5. Checks for any external cart items of type SCEExternalCartItem, associated
with shopping carts, that do not have the classnamekecartReference
set to com.ptc.sce.cart.SCEShoppingCart.
6. Checks for any external cart items of type SCEExternalCartItem, associated
with orders, that do not have the classnamekeycartReference set to
com.ptc.sce.cart.SCEOrder.
7. Checks that the part numbers of migrated external cart items match the part
numbers of the corresponding source external cart items. If any mismatches
are identified, a log is created.
Intended Use
This diagnostic task should be executed:
• Immediately after upgrading to InService 6.0
• When requested by PTC
Extract Workflow Expressions
Diagnostic Task Description
This diagnostic task extracts all of the workflow expressions to a text file located
in the WinDU directory.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

Note
This diagnostic task should only be executed before upgrade when verifying
existing workflow expressions is needed, or when requested by PTC. Default
behavior extracts latest iteration of workflow expressions. To extract all
workflow expressions, set the property to:
wt.workflow.engine.ExtractWorkflowExpressionsDT.extractAll=true.
To extract all workflow expressions that are currently in process, set the
property to:
wt.workflow.engine.ExtractWorkflowExpressionsDT.extractInProcess=true.
Find all NavigationCriterias associated to a DerivedImage in which
the owner attribute is incorrect
Diagnostic Task Description
This repair task finds all navigation criteria associated with a derived image in
which the owner attribute is incorrect. The owner for the navigation criteria
should be the associated derived image, not a Windchill user. Once found, the

WinDU Diagnostic Tasks 51

 Find all NavigationCriterias associated to a DerivedImage in which
the owner attribute is incorrect
Repair all NavigationCriterias associated to a DerivedImage in which the owner
attribute is incorrect repair task can be run to correct the owner association.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Find any Orphan Representation NavigationCriterias
Diagnostic Task Description
This diagnostic task reports all orphaned representation navigation criteria. Once
found, the Delete any Orphan Representation NavigationCriterias repair task can
be run to remove the orphans.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Find Dangling EPMCheckpoint Objects
Diagnostic Task Description
This diagnostic task Identifies EPMCheckpoint object which no longer belongs
to a workspace. Issues found can be fixed with running "Delete Dangling
EPMCheckpoint" repair utility.
Intended Use
This diagnostic task should be executed when detecting EPM Workspace
corruption related to dangling EPMCheckpoint objects
Find IBAs for MPMLink objects for which the name has been
changed
Diagnostic Task Description
This diagnostic task lists global variable names include numbers in their values.
For example, Standard8Cost.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Find Invalid App Context Domains
Diagnostic Task Description
Before Windchill 9.0, new products, projects, and libraries with private access

52 Windchill Diagnostic Utility Guide

 Find Invalid App Context Domains
were created in the /Private domain. Products and libraries with public access
were created in the /PDM domain, and projects with public access were created
in the /Project domain. Beginning with Windchill 9.0, all application contexts
were created in the /System domain. In Windchill 10.1 M030, there is a new
property, wt.inf.container.preX10AppContextDomain , to control how domains
are assigned to containers when they are created . The property will be false by
default. If the property value is false, there will be no change in the assignment
of domains to application containers. When this property is true, then new
application containers will be created as they were before 9.0. if the property is
true the Find Invalid App Context Domains WinDU will find and report the
existing application contexts that need to have their domains changed to be as
they would have been before 9.0. If the property is false, the WinDU will exit
without analyzing any containers.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Find Missing ImportedBookmarks in PostingAttachmentLink Table
for Postings
Diagnostic Task Description
This diagnostic task checks if imported bookmarks against all postings in
PostingAttachmentLink table exist in ImportedBookmark table. It reports failure
in case any imported bookmark found missing in ImportedBookmark table
whose entry exists in PostingAttachmentLink table.
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
FindOrphanAdhocActivitiesDT
Diagnostic Task Description
This diagnostic task detects deleted WfBlocks during loop link of Adhoc-
Activities in workflow. It reports adhoc activities in system who that refer to
deleted WfBlock.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

WinDU Diagnostic Tasks 53

 FindPrivateWorkSpaceObjAssociatedToChange
Diagnostic Task Description
This diagnostic tasks will find any Private to workspace objects that are
associated with change objects. The association links are deleted that are linked
to change objects and private to workspace objects. This diagnostic task is used
to prevent errors during the execution of DeleteAllFromWS EPM tool.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Find Orphan ShadowCache
Diagnostic Task Description
This diagnostic task reports orphan shadow cache objects within the system.
Intended Use
This diagnostic task should be executed when requested by PTC.
Folder Name Mismatch
Diagnostic Task Description
This diagnostic task identifies folder name mismatches between WTDocument
and SubFolder tables..
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Generate Data Validation Reports
Diagnostic Task Description
This diagnostic task generates data files in various output formats for the tables
or columns that are specified. The customer would need to compare the data
created before and after the upgrade using tools of their choice and see if there
are any discrepancies. These discrepancies would need to be resolved or could be
ignored if they are expected. Output formats that are currently available are:
FixedColumnWidth, OneColumnPerRow, and CharacterDelimited. The format
of the property that needs to be added for each table (columns) to be compared
is:
com.ptc.windchill.upgrade.datavalidation.list.#=,,
separated list of columns to be compared
Sample Entry list:
com.ptc.windchill.upgrade.datavalidation.list.1=WTPart,ida2a2,classnamea2a2,
updatecounta2 com.ptc.windchill.upgrade.datavalidation.list.2=
WTDocument,ida2a2,classnamea2a2,
updatecounta2,createstampa2,updatestampa2

54 Windchill Diagnostic Utility Guide

 Generate Data Validation Reports
com.ptc.windchill.upgrade.datavalidation.list.2=Project2,ida2a2,classnamea2a2,
updatecounta2,createstampa2,updatestampa2,namecontainerinfo

Output Format to be specified:

com.ptc.windchill.upgade.datavalidation.outputformat=<Format Type>

This property will be used to find the output format for this diagnostic task.
Where <Format Type> = FixedColumnWidth or OneColumnPerRow Or
CharacterDelimited
When <Format Type> is specified as FixedColumnWidth, this will read the
following property to find the width of the column.
com.ptc.windchill.upgade.datavalidation.outputformat.columnwidth=<Integer Number>

When <Format Type> is specified as CharacterDelimited, this will read the

following property to find the delimiter to be used.
com.ptc.windchill.upgade.datavalidation.outputformat.delimiter=<character to
be used as delimiter>
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Gfx Content Check
Diagnostic Task Description
This diagnostic task determines the number of rows in the ApplicationData table
that need to have GFX Creo Elements/Direct Modeling content set to tagging
syntax. The tagging syntax is used to support rename.
Issues identified can be fixed with the Update Creo Elements/Direct Modeling
Gfx Content repair task.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Group Domain and Location
Diagnostic Task Description
This diagnostic task reports administrative domain and LDAP location for all
groups in the system. All groups in the system are added to the Classic library’s
container team during migration. The output of this task is a text file. This
diagnostic task is dependent on successful execution of Verify Source Internet
Domain and Null Container References Check diagnostic task.

WinDU Diagnostic Tasks 55

 Group Domain and Location
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
ID Sequence Analysis
Diagnostic Task Description
This diagnostic task checks that the next available ID sequence value is higher
than any already assigned IDA2A2 value to avoid future duplicate assignments.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Ida2a2 Analysis
Diagnostic Task Description
This diagnostic task reports duplicate IDA2A2's across the Windchill schema
and also reports if the current sequence value is less than Max Ida2a2 value
across the schema.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Inaccessible Replicated Content Report
Diagnostic Task Description
This diagnostic task determines if there is content on the replica that has become
inaccessible after a change of policy rules, security labels, or the Site Principal.
The report only prints out summary information about the number of
inaccessible items at each site.
To log filenames in the vault for all inaccessible objects in Windchill logs, set the
verboseObjects property to true. The property is found in the following file:
<Windchill>\codebase\wt\fv\
InaccessibleContent.properties
The following properties can be used to refine task behavior:

56 Windchill Diagnostic Utility Guide

 Inaccessible Replicated Content Report
• classList, set to comma separated list of classes, defaults to
wt.content.ContentHolder
• processAllFoldersAtOnce, set to true or false, defaults to true. Set
the property to false if there are too many replicated items and memory is
limited. Setting the property to false will impact performance.
• chunkSize, set to number, defaults to 10000. A larger value reduces the
number of database hits. The value should be reduced if memory is limited.
Intended Use
This diagnostic task should be executed:
• After a policy rule has changed
• After security labels have been set on objects
• If the Site principal has changed
Note
This task only applies to customers using file servers.
Inconsistent Create Stamps Report
Diagnostic Task Description
This diagnostic task detects and reports any iterations of an object that share the
same version and have a different create timestamps. The correct system
behavior is for all iterations in a version to share the same create timestamp, but
to have a different modify timestamp for each iteration. The timestamps can be
corrected by running the Inconsistent Create Stamps repair task.
Intended Use
This diagnostic task should be executed when requested by PTC.
Inconsistent Version ID
Diagnostic Task Description
In release 8.0 a form of data corruption was encountered for some customers
where the version ID of a control branch did not match the version ID of its
iterations. A healing script (update_ControlBranchVersionId.sql) was introduced
to fix this. This diagnostic task detects this problem.
Intended Use
This diagnostic task should be executed:
• Before upgrading to Windchill 8.0 MXXX
• When requested by PTC
Incorrect Promotion Preference Table View Name
Diagnostic Task Description
This diagnostic task determines if corrupt records exist with promotionRequest.

WinDU Diagnostic Tasks 57

 Incorrect Promotion Preference Table View Name
promotionPreference.table within TableView Descriptor.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Internal Cart Item Mapping Validator
Diagnostic Task Description
This diagnostic task ensures that all internal cart item references were
successfully mapped from the old Windchill references in Service Center 10.1 to
the new EC3 references in InService 6.0. This task will output valid results only
when executed immediately after the upgrade and before any new internal cart
items are created or migrated ones are deleted.
This task:
1. Validates that all unique context/topic combinations in SCDefaultCartItem
have entries in PCMContextAndTopicMap.
2. Validates that all unique list/part combinations in SCDefaultCartItem have
entries in PCMPartsListAndPartMap.
3. Validates that all SCEInternalCartItems have contexts that match the
corresponding entry in PCMContextAndTopicMap.
4. Validates that all SCEInternalCartItems have topics that match the
corresponding entry in PCMContextAndTopicMap.
5. Validates that all SCEInternalCartItems have parts lists that match the
corresponding entry in PCMPartsListAndPartMap.
6. Validates that all SCEInternalCartItems have parts that match the
corresponding entry in PCMPartsListAndPartMap.
7. Validates that all SCEInternalCartItems have part metadata that match the
corresponding entry in PCMPartsListAndPartMap.
8. Reports any dangling references found in SCDefaultCartItem.
Intended Use
This diagnostic task should be executed:
• Immediately after upgrading to InService 6.0
• When requested by PTC
Internal Cart Items Validator
Diagnostic Task Description
This diagnostic task ensures that all internal cart items were successfully
migrated to the new InService 6.0 system. In Service Center 10.1, internal cart
items are of type SCDefaultCartItem. Starting in InService 6.0, internal cart

58 Windchill Diagnostic Utility Guide

 Internal Cart Items Validator
items are of type SCEInternalCartItem. This task will output valid results only
when executed immediately after the upgrade and before any new internal cart
items are created or migrated ones are deleted.
This task:
1. Validates that the number of internal cart items of type SCDefaultCartItem,
associated with shopping carts, is the same as the number of internal cart
items of type SCEInternalCartItem, associated with shopping carts. A failure
message is logged if the counts do not match.
2. Validates that the number of internal cart items of type SCDefaultCartItem,
associated with orders, is the same as the number of internal cart items of
type SCEInternalCartItem, associated with orders. A failure message is
logged if the counts do not match.
3. Checks for any internal cart items in SCDefaultCartItem that are not in
SCEInternalCartItem. A log is created of any internal cart items that are not
found. If all internal cart items are found, a success message is logged.
4. Checks for any records of SCEInternalCartItem that do not have the correct
class name: com.ptc.sce.cart.SCEInternalCartItem. If any
records are found, a log is created.
5. Checks for any internal cart items of type SCEInternalCartItem, associated
with shopping carts, that do not have the classnamekecartReference
set to com.ptc.sce.cart.SCEShoppingCart.
6. Checks for any internal cart items of type SCEInternalCartItem, associated
with orders, that do not have the classnamekeycartReference set to
com.ptc.sce.cart.SCEOrder.
Intended Use
This diagnostic task should be executed:
• Immediately after upgrading to InService 6.0
• When requested by PTC
Internal Groups and pending Users Check
Diagnostic Task Description
Windchill ProjectLink 6.2.6 had two JNDI adapters, the InternalGroups and the
PendingUsers, which were removed in Windchill ProjectLink 7.0. This
diagnostic task reports whether there are any users still linked to these two JNDI
adapters in the database.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC

WinDU Diagnostic Tasks 59

 Invalid Container Templates
Diagnostic Task Description
This diagnostic task reports all the Container Templates that are not validating
with their release specific DTD.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Invalid Internal Principals with UFID
Diagnostic Task Description
This diagnostic task reports on Internal Principals with UFID. Internal Principals
are local to the System, they should not have a UFID (i.e. an entry in
RemoteObejctInfo, RemoteObjectId and OwningRepositoryLocalObject tables).
It also provides instructions to remove the UFID associated with the principal.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Invalid LDAP Entries
Diagnostic Task Description
The diagnostic task validates Principals present in LDAP and Windchill for
invalid characters (#, >, <, /, \) in the Name field and provides instructions for
fixing them. If extended validation for invalid characters is needed across other
principal attributes in LDAP, additional configuration must be provided in the
InvalidLdapEntries properties file. In this properties file, you must specify which
attributes and invalid characters the task should look for. The entries must be
separated by a semi-colon. For example,
RETURN_ATTRIBUTES=o; mail INVALIDCHARACTERS=#; /;

Before running this diagnostic task, the Principal Validator diagnostic task must
be run to ensure there are no disconnected entries.

Note
If the property
wt.org.principalNameIllegalCharCheckBypass is set to true
in wt.properties file, then invalid characters could be ignored.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

60 Windchill Diagnostic Utility Guide

 Invalid Series Values
Diagnostic Task Description
This diagnostic task validates the series values stored in the database for all
Versioned objects
Intended Use
This diagnostic task should be executed before and after upgrade to validate the
data is correct.
Invalid Phase Templates
Diagnostic Task Description
This diagnostic task validates the life cycle template to check if all states are
present in LC. One needs to delete this template if corruption is detected by this
diagnostic task.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Invalid Project Container Names
Diagnostic Task Description
This diagnostic task detects bad Project Container Names and reports those
invalid container names.
For example, “#mycontainer” in project container name would be reported as
invalid.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Invalid Workitems and Workflow Processes without PBOs
Diagnostic Task Description
This diagnostic task provides a list of Invalid Workitems and Workflow
Processes without Primary Business Objects in the source system. The report
will list the names and IDA2A2 of the workflow processes without Primary
Business Objects. These details are useful for deleting the invalid workflow
processes from the Windchill database. The task reports the Process ID, Process
Name, Context, Initiated On, Last Modified Time, Process Template Name,
Context and version.

WinDU Diagnostic Tasks 61

 Invalid Workitems and Workflow Processes without PBOs
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Invalid Workflow Tasks
Diagnostic Task Description
This diagnostic task lists all workflow tasks with invalid associated activity
template references or missing the associated activity objects.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

Note
This diagnostic task should be executed before upgrade in order to find the
Invalid change workflow processes, which should be fixed before executing
the upgrade. These workflow processes can be terminated using the process
manager interface, or when requested by PTC.
Iteration Attribute Alignment
Diagnostic Task Description
This informational task reports versions that have iterations in different cabinets
or domains or have differing ownership. It is not required that all iterations of a
version be aligned within the same cabinet or administrative domain or have the
same owner for a successful migration. However, before the data can be moved
to a different container after migration, all versions must be aligned under the
same cabinet or administrative domain and have the same owner.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
List Checked Out/Disabled Workflow-Lifecycle Templates
Diagnostic Task Description
This diagnostic task is designed to check any workflow or lifecycle templates
have checked out/disabled status. The output of this logged to a file <WinDU
Logs Directory>\ListCheckedOutWorkflowLifecycleTemplates.log. The output
will list the template name, template creator, context of the template, status of
template (Disabled/Checked Out) and last modified time.

62 Windchill Diagnostic Utility Guide

 List Checked Out/Disabled Workflow-Lifecycle Templates
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
List New Child Parts in Structure
Diagnostic Task Description
Lists all new child parts, not previously checked in, used by parent checked in
parent parts.
Intended Use
This diagnostic task should be executed:
• Quarterly
Locate Class References
Diagnostic Task Description
This diagnostic task scans the database for references (i.e. foreign keys) to
specified classes or nonexistent classes.
To locate references to specific classes, specify the list or pattern in the classes
field. To locate references to classes that do not exist, do not specify a list of
classes.
LocateEnumTypeReferences.txt - lists the number of references found in each
table and column searched
LocateEnumTypeReferences.log - verbose output will show all the SQL
statements that were executed by the task
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When analyzing usage of classes or packages
• When removing customizations
• When requested by PTC
Locate Dangling References
Diagnostic Task Description
This diagnostic task reports database references that do not exist. Some types of
dangling references are expected, so this diagnostic task should be used when
requested by PTC to help debug a preexisting issue.
Intended Use
This diagnostic task should be executed when requested by PTC.

WinDU Diagnostic Tasks 63

 Locate Enum Type References
Diagnostic Task Description
This diagnostic task scans the database for references to specified classes or
nonexistent Enumerated Types.
To locate references to specific Enumerated Types, specify the list or pattern in
the EnumeratedTypes field. To locate references to Enumerated Types that do not
exist, do not specify a list of Enumerated Types.
LocateEnumTypeReferences.txt - lists the number of references found in each
table and column searched
LocateEnumTypeReferences.rbInfo - lists the ET values that need to be added to
each bundle, to avoid runtime exceptions
LocateEnumTypeReferences.log - verbose output will show all the SQL
statements that were executed by the task
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When analyzing usage of EnumeratedTypes values
• When requested by PTC
Locate invalid authoring language
Diagnostic Task Description
This diagnostic task reports if there are any obsolete authoring language values
for translatable objects, such as WtPartMaster. In previous releases, the
java.util.Locale.toString() representation format was used for
authoring language values. For example, for United States English, the
java.util.Locale.toString() representation format is en_US. Starting
in Windchill 10.2 M022, the canonical BCP 47 language tag replaced the
java.util.Locale.toString() representation format. In this format,
the canonical BCP 47 language tag for United States English is en-US.
If any java.util.Locale.toString() format values are found, the
Repair Authoring Language repair task should be run.
Intended Use
This diagnostic task should be executed:
• After upgrade from Windchill 10.2 M010 to Windchill 10.2 M022
• When requested by PTC
Missing Container References for Notebooks and Discussion
Forums
Diagnostic Task Description
This diagnostic task checks an upgraded Windchill 8.0 system to find Discussion

64 Windchill Diagnostic Utility Guide

 Missing Container References for Notebooks and Discussion
Forums
forums and Notebooks whose container references are not set correctly.
Intended Use
This diagnostic task should be executed:
• After Windchill PDMLink upgrade to release 8.0
• When requested by PTC
MissingControlBranchCleanserDT
Diagnostic Task Description
This diagnostic task reports any missing control branches.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Missing IOPState Diagnostic Task
Diagnostic Task Description
This diagnostic task checks for improperly upgraded data for Windchill servers
that were upgraded from a release prior to Windchill 9.0.
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
Missing Master Discovery Tool
Diagnostic Task Description
This diagnostic task checks for Iterated objects that do not have Masters and
reports them.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Missing Name of Discussion Topic
Diagnostic Task Description
This diagnostic task reports discussion topics whose “name” value is null in the
database.

WinDU Diagnostic Tasks 65

 Missing Name of Discussion Topic
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Missing PreferenceCategory or PreferenceDefinition from
PreferenceCategoryDefinitionLink DT
Diagnostic Task Description
This WINDU reports missing PreferenceCategory or PreferenceDefinition from
PreferenceCategoryDefinition.
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
If this Windu reports any missing data, contact PTC Technical Support.
Missing Representables
Diagnostic Task Description
This diagnostic task reports all the missing Representables (currently WTParts
and custom parts), WTDocuments (custom WTDocuments) and EPMDocuments
for existing representations (currently DerivedImage).
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Missing URL and HOLDERTOCONTENT Reference for Bookmarks
Diagnostic Task Description
This diagnostic task reports corrupted ImportedBookmarks, such as having URL
value of NULL or ImportedBookmarks missing HOLDERTOCONTENT entries.
Intended Use
This diagnostic task should be executed when requested by PTC.
MPMLink Number Diagnostic Task
Diagnostic Task Description
Diagnostic task to diagnose any SequenceNumber and AllocationNumber
attributes that are 0 or null on the respective links in the database. Some
MPMSequenceUsageLinks may have a value of 0 for the SequenceNumber and
some MPMOperationToConsumableLinks may have a value of null for the
AllocationNumber.

66 Windchill Diagnostic Utility Guide

 MPMLink Number Diagnostic Task
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC

Note
This DT is only relevant for Windchill MPMLink functionality.
MPMLinkMissingSelfEquivalenceDiagnosticTask
Diagnostic Task Description
This diagnostic task identifies the upstream parts that are reused as is in the
equivalent downstream structures without creating equivalent links to self.
By default, this task searches for equivalent links for the root nodes across all
contexts. You can filter the search criteria to detect the missing self-equivalent
links for specific views and root nodes of the upstream and downstream
structure. Set the following properties in the wt.properties file located on
the path <Windchill>\codebase:
• com.ptc.windchill.mpml.missingselflinks.downstreamContext: Specify the
downstream view.
• com.ptc.windchill.mpml.missingselflinks.downstreamRootNumber: Specify
the downstream root number.
• com.ptc.windchill.mpml.missingselflinks.upstreamContext: Specify the
upstream view.
• com.ptc.windchill.mpml.missingselflinks.upstreamRootNumber: Specify the
upstream root number.
If any of these properties are set incorrectly or not set, the diagnostic task detects
the equivalent links for the root nodes across all contexts.
Note
If the Stop Structure Expansion By Criteria preference is set, the diagnostic
task detects self-equivalent links only for the parts that are displayed in the
trimmed structure.
Intended Use
The diagnostic task can be executed as many times as required. The task should
be executed:
• Before upgrade
• Before migration
• When requested by PTC

WinDU Diagnostic Tasks 67

 MPMLink: Updating Occurrence Positioning Diagnostic Task
Diagnostic Task Description
Occurrence positioning diagnostic task identifies and reports issues related to the
occurrence positioning of upstream and downstream structures.
To identify and report issues with the occurrence positioning of upstream and
downstream structures, you can add the
com.ptc.windchill.mpml.healOccPositions.contexts property
in the Windchill/site.xconf file and propagate it to Windchill/
codebase/wt.properties file by using xconfmanager -p command.
Restart the Windchill server after adding the property in the following format:
<Property name=
"com.ptc.windchill.mpml.healOccPositions.contexts"
overridable="true"targetFile="codebase/
wt.properties"value=
"upRootNumber1,downRootNumber1,upSavedNcNameXXX,downSa
vedNcNameXXX;upRootNumber2,downRootNumber2,upSavedNcNa
meXYZ,downSavedNcNameXYZ"/>
For example:
<Property name=
"com.ptc.windchill.mpml.healOccPositions.contexts"
overridable="true"targetFile="codebase/
wt.properties"value=
"upRootNumber1,downRootNumber1,upSavedNCName1,downSa
vedNCName1;upRootNumber2,downRootNumber2,upSavedNCNa
me2,downSavedNCName2"/>
In the property:
• upRootNumber1 is the part number of the root part in the upstream
structure.
• downRootNumber1 is the part number of the root part in the downstream
structure.
• upSavedNcNameXXX is the name of the saved filter in the upstream
structure. For example, Filter7, UpstreamFilter8etc.
• downSavedNcNameXXX is the name of the saved filter in the downstream
structure. For example, Filter123, DownstreamFilter7etc.
Considerations:
• Click ▶ Saved Filters ▶ Save Filter to save the name of the filter.
• You must ensure that the filter criteria have the correct version of the
upstream and the downstream assembly part including alternate BOM.
• If the property is not set or is set incorrectly, the diagnostic task does not

68 Windchill Diagnostic Utility Guide

 MPMLink: Updating Occurrence Positioning Diagnostic Task
identify, and report issues related to occurrence positioning of the upstream
and downstream structures.
• This diagnostic task identifies and fixes occurrence positions only for paths
whose Common Equivalent Context (CEC) is up to date. It skips out-of-date
common equivalent context paths.
• You can provide multiple structure or contexts by using the separator (;).
Intended Use
The diagnostic task can be executed as many times as required and must be
executed:
• Before upgrade
• Before migration
• When requested by PTC
NamespaceUniquenessCheckDT
Diagnostic Task Description
This diagnostic task does a preventative check on namespace managed objects
before the NamespaceCorrectionMigrator runs. Each namespace managed table
has a unique index on WTKEY, IDA3ORGANIZATIONREFERENCE, and
IDA3NAMESPACEREFERENCE. The NamespaceCorrectionMigrator updates
the IDA3NAMESPACEREFERENCE column, and may violate this unique
index. This diagnostic task identifies records which will violate the index during
the migration.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Notification Conversion of ProjectLink OwnerRefs
Diagnostic Task Description
This diagnostic task identifies if there are existing Windchill ProjectLink
notifications for OWNERS. If so, these need to be converted to referencing the
actual user in the database. If not done, this leads to a severe performance
degradation for notification. If any exist, they can be converted by running the
Notification Conversion OwnerRef Repair Task.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

WinDU Diagnostic Tasks 69

 Null Container References Check
Diagnostic Task Description
This diagnostic task checks all contained objects and ensures that each has a
reference to the container in which it resides..
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Null DerivedFrom Report
Diagnostic Task Description
This diagnostic task reports if there are derivedFrom fields that are null. This
problem can be resolved by running the NullDerivedFromCleanser.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Null Namespace Attribute Check
Diagnostic Task Description
This diagnostic task verifies that this namespace (The name space is part of the
unique identity of all objects that implement WTContainerNameSpace) is NOT
null and logs warning messages if it finds an object for which the corresponding
namespace is null. The namespace reference is stored on the semantic key table
that corresponds to the object which implements WTContainerNameSpace.
For example in the case of WTPart, the corresponding semantic key table is
WTPartMasterKey and this table has a column
IDA3NAMESPACEREFERENCE that holds a reference to the name space. The
diagnostic task will now verify that the value assigned to this column is not null.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Null Series Diagnostic Task
Diagnostic Task Description
This diagnostic task detects any master object with a null series value.

70 Windchill Diagnostic Utility Guide

 Null Series Diagnostic Task
Intended Use
This diagnostic task should be executed:
• Before upgrade
• As part of any regular maintenance set up on site
• When requested by PTC
Object Already Unlocked Diagnostic Task
Diagnostic Task Description
This diagnostic task finds EPMDocuments with a certain corruption involving
checked out objects. This corruption usually appears to the user when they try to
check in an object and causes a message that the "Object is already unlocked...."
to be displayed.
Intended Use
This diagnostic task should be executed when requested by PTC.
Object in More than One Lifecycle State
Diagnostic Task Description
This diagnostic task detects objects that reside in more than one life cycle state.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Object Initialization Rule Report
Diagnostic Task Description
This informational task reports all the object initialization rules within the
system, as well as the container in which they are located.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Object Initialization Rule Conflict Report
Diagnostic Task Description
This diagnostic task identifies where there are conflicts for object initialization
rules for the same type in both the Exchange container and the Classic library.
Customers should use the output of this report to merge the conflicting rules into
a single rule at the library level, or to delete on of the conflicting rules. The
migration cannot run until all of these conflicts have been resolved, and then it
will move all the object initialization rules from the Exchange container to the

WinDU Diagnostic Tasks 71

 Object Initialization Rule Conflict Report
Classic library. The output for this task is a text file. This task is applicable only
before running the migration.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
OptionChoice Number Uniqueness Report
Diagnostic Task Description
This information task reports all option and choice objects where the object
number is not unique. A uniqueness constraint was added in PTC Windchill 10.2.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
OptionSet Container Diagnostic Task
Diagnostic Task Description
This diagnostic task reports all OptionSet objects at the organization and site
level that need to be moved. In Windchill 9.0 and Windchill 9.1 releases,
OptionSet objects were stored at the organization and site level. As of Windchill
10.0, OptionSet objects are stored only in application containers (Product,
Project, and Library.)
This task writes a file <windchill>/loadXMLfiles/
OptionSetContainerMappings.xml. The file lists each OptionSet that
needs to be moved and lists the current container for that OptionSet. The user
must update the container tags in the file with the desired container for each
OptionSet identified in the report.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Order Exists Validator
Diagnostic Task Description
This diagnostic task ensure that all orders were successfully migrated to the new
InService 6.0 system. In Service Center 10.1, orders are of type SCCart. Starting
in InService 6.0, orders are of type SCEOrder. This task will output valid results
only when executed immediately after the upgrade and before any new orders are
created or migrated ones are deleted.

72 Windchill Diagnostic Utility Guide

 Order Exists Validator
This task:
1. Validates that the number of orders of type SCCart is the same as the number
of orders of type SCEOrders. A failure message is logged if the counts do not
match.
2. Checks for any orders in SCCart that are not in SCEOrder. A log is created of
any orders that are not found. If all orders are found, a success message is
logged.
3. Checks that all orders of type SCEOrders have the correct classnameA2A2.
A log is created of any orders that do not have the correct classnameA2A2. If
all orders have the correct class name, a success message is logged.
Intended Use
This diagnostic task should be executed:
• Immediately after upgrading to InService 6.0
• When requested by PTC
Organization and User Duplicates Check
Diagnostic Task Description
This diagnostic task should be executed to verify that there are no duplicate user
or organization names in the database. At 9.0, duplicate user or organization
names are not allowed. If a duplicate exists on the source system, it needs to be
resolved before upgrade. The diagnostic task will report warning messages if it
finds any duplicate user or organization names.
Intended Use
This diagnostic task should be executed:
• Before upgrade from a Windchill 9.0 or 9.1 system.
• When requested by PTC
Organization Owned Reference
Diagnostic Task Description
This diagnostic task should be executed to verify that the organization reference
is set correctly on all contained objects that are also organization owned (e.g.
WTPart, WTDocument, EPMDocument).
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

WinDU Diagnostic Tasks 73

 Orphaned Terminal Objects Diagnostic Task
Diagnostic Task Description
Task detects shares erroneously left behind after “Remove Contents” action was
performed on a project. Shares left behind after “Remove Contents” prevent
deleting the source object of the share and require the Orphaned Terminal
Objects Repair Task to remove them.
Intended Use
This diagnostic task should be executed:
• Any time a user finds objects they can’t delete because a share resides in a
deleted project that had “Remove Contents” action performed
• When requested by PTC
Owning Repository Validator
Diagnostic Task Description
This diagnostic task validates the following information:
• Principals in the database are linked to JNDI LDAP entries. Only external
groups (i.e. user-defined Site and Org level groups) are validated. Groups
directly under the default search base and under each Org node are queried.
Each distinguished name (dn) for a node in LDAP is matched to a
corresponding RemoteObjectID entry in the database. If the corresponding
RemoteObjectID does not exist, the task recommends that the Principal
Administrator cleans up the principal. If the corresponding RemoteObjectID
entry does exist, but the WTGroup entry does not exist, the task provides
SQL statements to clean up the RemoteObjectID from the RemoteObjectInfo
table and to clean up the group’s corresponding
OwningRepositoryLocalObject table entry.
• All repository references from the OwningRepositoryLocalObject table
resolve to entries in the Repository table. If there are dangling entries, the
task provides a SQL script to clean them up.
Intended Use

This diagnostic task should be executed:

• Before migration
• When requested by PTC

Personal Cabinet Data Report

Diagnostic Task Description
This informational task reports all data existing in personal cabinets that is not
checked into a shared location. Unlike standard upgrade, there is no requirement

74 Windchill Diagnostic Utility Guide

 Personal Cabinet Data Report
that personal cabinet data be checked in before running the migration. This
information is provided for tracking purposes in case a customer wants to check
the data before migration, or locate it after migration.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Personal Cabinet Owners Deleted Report
Diagnostic Task Description
This diagnostic task finds personal cabinets whose owners have been disabled or
removed. For each such cabinet found, reports the cabinet name, the ida2a2
value of the cabinet, and the user who owned the cabinet. If the user has been
removed, not simply disabled, the output will indicate the user has been
removed.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Post Upgrade Visualization Count
Diagnostic Task Description
This diagnostic task will determine how many ED files need to be converted.
Intended Use
This diagnostic task should be executed:
• After migration
• When requested by PTC
Pre 8.0M050 Invalid Series Values
Diagnostic Task Description
This diagnostic task validates the series values stored in the database for all pre-
Windchill 8.0 M050 Versioned objects and lists all invalid values and the objects
that are using those invalid values.

WinDU Diagnostic Tasks 75

 Pre 8.0M050 Invalid Series Values
Intended Use
This diagnostic task should be executed:
• Before or after upgrade
• When requested by PTC

Note
This version of the validation tool should be run only for Windchill releases
8.0 FCS through 8.0 M040.
Preferences Report
Diagnostic Task Description
This diagnostic task will generate a report to list all the preferences created out of
the box, values, and also any user preferences currently set.
Intended Use
This diagnostic task should be executed when requested by PTC.
Prepare Report of Objects Referencing Classic Plan Data
Diagnostic Task Description
This diagnostic task creates a text report of all objects referencing classic plans
that existed in your Windchill server. The objects include the following:
• Activity Tasks
• Action Items
• Discussions
• Notebook
• Subscriptions
• Bookmark
Intended Use
This diagnostic task should be executed:
• After upgrade
ProductView ED to PVS
Diagnostic Task Description
This diagnostic task reports information about ED files customers have on their
systems. It will display the total count of ED files, the total size of the files, and
if any vault content is found to be null.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

76 Windchill Diagnostic Utility Guide

 Report all Lifecycle Templates with One or More Missing Phases
Diagnostic Task Description
This diagnostic task checks if any life cycle template has missing phases.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Report All Organization Owned Namespace Objects in External
Organizations
Diagnostic Task Description
Reports all conflicting objects that are organization owned, from Products,
Libraries, Projects, Organizations, and Site. The report contains links to
individual reports for each type of object. Use the report to resolve the
conflicting objects. The conflicting objects are listed for Site and Organization
level uniqueness. Information contained in the report for an object include Object
Name, Number, Owning Organization, Owning Organization IDA2A2,
Container Class, Container Reference IDA2A2, and Container.
This task will run as part of the pre-upgrade mandatory WinDU task group. Use
this report to detect potential conflicts when merging several systems into one
(for example, when objects have the same part number and are associated with
the same vendor in several of the existing systems) to view reports from all
systems, identify conflicted objects, and consolidate them prior to upgradation.
To do this, it is recommended that in the resulting CSV file for each system
against which the WinDU task was performed, add a column to denote the
system name (for example, if two systems are being compared, one file would
have a “System Name” column with all entries denoting “System A” and the
second file would have a “System Name” column with all entries denoting
“System B”). This will ensure that once the files are merged, it is still possible to
know which system the objects in the combined file came from. Next, it is
recommended that the CSV files from the different systems then be merged into
a single Excel file, do a sort on the number column so all similar numbers are
together, and then use an Excel rule to identify duplicates where the number and
org name are the same.
Resolve the conflicts either by renumbering the objects or by changing the
object’s organization manually.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

WinDU Diagnostic Tasks 77

 Report Checked Out and Uploaded Family Tables
Diagnostic Task Description
This diagnostic task reports all Checked Out Family Table members in all
workspaces. It reports a list of Workspace Owner Name, Workspace Owner
email, Workspace Name and Names of checked out and new family table
members in this workspace.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Report Non Change Objects Processes With Missing Audits
Diagnostic Task Description
This diagnostic task is used to check the workflow processes (WfProcess) which
are missing the audits (WfVotingEventAudit) that contains the votes and
comments for the task completed. It displays the processes along with the
workitems (WorkItem) which are missing the audits on the server.
Intended Use
This diagnostic task should be executed when requested by PTC.
Report Registered Users in the System
Diagnostic Task Description
Report on the registered users in the system. The report excludes users who have
the disabled or internal flag set to true. This will also exclude users in a given
custom group which the customer uses to symbolically disable users. By default
the disabled user group is 'Deactivated Users'.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Required Soft Attribute Report
Diagnostic Task Description
The upgrade to Windchill Aerospace & Defense 9.1 consolidates the existing
(specialized) Configuration Management object model into standard object
model that has been enhanced with new functionality. Included in the enhanced
functionality is the promotion of the BOM Notes from an attribute on a product
structure usage link to a full-fledged object (a soft type of EPM Document)
associated with the product structure usage link.

78 Windchill Diagnostic Utility Guide

 Required Soft Attribute Report
This diagnostic task provides a report on the soft attribute, having a required
constraint, associated with EPMDocument. The required instructions before
upgrade, utilizing the information contained in this report, are documented in the
Windchill Upgrade Guide.
Intended Use
This diagnostic task should be executed before upgrading to Windchill
Aerospace & Defense 9.1.
Revision Label Corruption Report
Diagnostic Task Description
This task identifies cases where an object’s revision identifier or one-off
identifier that is stored in the latest iteration does not match the corresponding
identifier value stored in a control branch, non-latest iteration, or working copy
iteration. Contact PTC Technical Support if the task reports issues.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• During routine checks for data corruption
• When requested by PTC
Saved Search Constraint Violation Check
Diagnostic Task Description
This diagnostic task reports if the migration of saved search will run into any
SQLIntegrityConstraintViolationException. This is applicable when the source is
9.0/ 9.1 The output of the diagnostic task is a text file. If the diagnostic task finds
a potential problem with the saved searches on the source system, it will list the
names of the saved searches that will cause migration of saved searches to run
into SQLIntegrityConstraintViolationException. The report will make a
recommendation to delete or rename the specified saved searches in the
SavedQuery table.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• Before migration
• When requested by PTC
Saved Search Null Criteria Check
Diagnostic Task Description
Diagnostic task reports if there are any saved searches on the source system
containing null criteria, such saved searches will run into issues during Upgrade

WinDU Diagnostic Tasks 79

 Saved Search Null Criteria Check
and Migration.
The output of the diagnostic task is a text file. If the diagnostic task finds saved
searches on the source system containing null criteria, it will list the names of
these saved searches. These saved searches will cause the migration of saved
searches to run into NullPointerException. The report will make a
recommendation to either delete the specified saved searches from the
SavedQuery table or recreate them with valid search criteria.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• After upgrade
• Before migration
• When requested by PTC
Sequence Seed Conflict Diagnostic Task
Diagnostic Task Description
This diagnostic task finds sequences in SQL Server databases that were created
to replace old sequences but used created with an incorrect seed value that could
cause conflicts. It then recommends executing the repair task to fix the issue.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Series Sort ID Diagnostic Task
Diagnostic Task Description
This diagnostic task will detect 3 (three) distinct types of corruption:
1. Values in the Series Sort Value table that are incorrect with respect to the
series definition.
2. Iterations in the database that use the incorrect sort IDs detected in step one.
3. Iterations in the database that have sort IDs inconsistent with the value in the
Series Sort Value table.
If any of these corruptions are detected please contact Windchill R&D for a fix,
as this tool does not currently support fixing the bad data. Please note that this
means the “-update” option is currently unsupported. This diagnostic task will
report Number of cases of the above mentioned types of corruption.

80 Windchill Diagnostic Utility Guide

 Series Sort ID Diagnostic Task
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Service Information Manager AAD — Check S1000D ICN Lifecycles
to be reassigned
Diagnostic Task Description
Finds ICNs that are based on lifecycles generated by 4.0.1 and 4.1 specific
lifecycle templates:
• S1000D_4-0-1 ICN Lifecycle Template
• S1000D_4-1 ICN Lifecycle Template
These templates have been replaced by a single template:
• S1000D ICN Lifecycle Template
Existing ICNs must have their lifecycles reassigned
Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.
Intended Use
This diagnostic task should be executed:
• When updating an 11.1 F000 installation
• When requested by PTC
Service Information Manager AAD — Checks the S1000D Publication
Structures, Modules (and holders) that have lifecycles to be
reassigned
Diagnostic Task Description
Finds Publication Structures and Publication Modules (and holders) that are
based on lifecycles generated by 4.0.1 and 4.1 specific lifeceycle templates:
• S1000D_4-0-1 Publication Structure Lifecycle Template
• S1000D_4-1 Publication Structure Lifecycle Template
• S1000D_4-0-1 Publication Module
• S1000D_4-1 Publication Module
These templates have been replaced by a single template for each object:
• S1000D Publication Structure Lifecycle Template
• S1000D Publication Module

WinDU Diagnostic Tasks 81

Service Information Manager AAD — Checks the S1000D Publication
Structures, Modules (and holders) that have lifecycles to be
reassigned
Existing Publication Structures and Publication Modules must have their
lifecycles reassigned.
Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.
Intended Use
This diagnostic task should be executed:
• When updating an 11.1 F000 installation
• When requested by PTC
Service Information Manager AAD — Confirm Existence of the
S1000D Product Template "S1000D General SNS Sets Product"
Diagnostic Task Description
Finds the S1000D SNS Sets Product template named S1000D General SNS Sets
Product . This template has been renamed S1000D 4.0.1 & 4.1 General SNS Sets
Product.
Existing templates must be updated.
Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.
Intended Use
This diagnostic task should be executed:
• When updating an 11.1 F000 installation
• When requested by PTC
Service Information Manager AAD — Confirm Existence of the
S1000D Product Templates to be Updated
Diagnostic Task Description
Identifies the S1000D product templates that must be updated to include these
changes to 4.0.1/4.1 support:

82 Windchill Diagnostic Utility Guide

 Service Information Manager AAD — Confirm Existence of the
S1000D Product Templates to be Updated
• Single zip file containing 4.0.1 and 4.1 templates for ICN objects
These 4.0.1 and 4.1 specific zip files have been replaced:
○ /codebase/netmarkets/com/ptc/arbortext/windchill/
rules/schema/S1000D_4-0-1/samples/S1000D_4-0-1-
ICN-Templates.zip
○ /codebase/netmarkets/com/ptc/arbortext/windchill/
rules/schema/S1000D_4-1/samples/S1000D_4-1-ICN-
Templates.zip
A single zip file now includes ICN templates:
○ codebase/com/ptc/arbortext/windchill/rules/
schema/samples/S1000D_ICN-Templates.zip
• Centralized 4.0.1 and 4.1 ACL rules for a Publication Manager's permissions
on a Publication Structure
These files have been replaced:
○ loadXMLFiles/sisaad/s1000D/product/4-0-1/s1000D-
4-0-1-ACLs.xml
○ loadXMLFiles/sisaad/s1000D/product/4-1/s1000D-4-
1-ACLs.xml
Their permissions are now defined by the rule sis.s10000D.PsRoot, in
this file:
○ loadXMLFiles/sisaad/s1000D/product/S1000DACLs.xml
Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.
Intended Use
This diagnostic task should be executed:
• When updating an 11.1 F000 installation
• When requested by PTC
Service Information Manager AAD — Diagnose S1000D Service Parts
Diagnostic Task Description
Diagnoses the changes needed to add Windchill Service Parts - S1000D Module
functionality to existing S1000D products. Finds S1000D products which need
updates to their Default Parts List Type preference and access controls to support

WinDU Diagnostic Tasks 83

Service Information Manager AAD — Diagnose S1000D Service Parts
the Windchill Service Parts - S1000D Module.

Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.
Intended Use
This diagnostic task should be executed:
• After installing Windchill Service Parts onto an existing S1000D installation
which didn't already have Windchill Service Parts installed (all releases)
• When requested by PTC
Service Information Manager AAD — Find missing DML and DDN
templates and out-dated sample publishing rules
Diagnostic Task Description
Finds all S1000D products that do not have a full set of templates for creating
Data Module List (DML) and Data Dispatch Note (DDN) objects. Identifies all
S1000D products that contain out-dated sample publishing rules.

Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.
Intended Use
This diagnostic task should be executed:
• When upgrading from a version earlier than 11.0 M020
• When requested by PTC
Service Information Manager AAD — Find S1000D Products where
the preference 'Conflict for Out of date Secondary content upon
Checkin' is set to 'Yes'
Diagnostic Task Description
Identifies any existing S1000D products that have the Operation > Checkin
Operation preference 'Conflict for Out of Date Secondary Content upon Checkin'
set to Yes. The diagnostic task lists the products that have the preference set to
this value, and advises which can be updated to change the value to No. A value
of No for the preference ensures a smooth workflow when checking in Creo
Illustrate (.c3di) graphics.

Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.

84 Windchill Diagnostic Utility Guide

 Service Information Manager AAD — Find S1000D Products where
the preference 'Conflict for Out of date Secondary content upon
Checkin' is set to 'Yes'
Intended Use
This diagnostic task should be executed:
• After upgrade to 11.0 M030, if there is a business requirement to use Creo
Illustrate graphics as the content of illustrations in an existing S1000D
product
• When requested by PTC
Service Information Manager AAD — Find S1000D products without
Creo/IsoDraw templates
Diagnostic Task Description
Identifies any S1000D products that do not include templates that support Creo
illustrate (. c3di) and Servigistics Arbortext IsoDraw (. iso) graphics when
creating ICNs/illustrations. The diagnostic task lists the products that do not have
the templates, and advises how many templates can be added.

Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D module.
Intended Use
This diagnostic task should be executed:
• After upgrade to 11.0 M030, if there is a business requirement to use Creo
Illustrate / Servigistics Arbortext IsoDraw graphics as the content of
illustrations in an existing S1000D product
• When requested by PTC
Service Information Manager AAD — Find S1000D Structure Groups
without a View
Diagnostic Task Description
Identifies any S1000D structure parts that were not assigned a default view when
they were created. An S1000D structure part must have a view assigned to
ensure that end users are working on the correct version of the object. The
default view for objects in an S1000D structure is Service.

Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D module.

WinDU Diagnostic Tasks 85

 Service Information Manager AAD — Find S1000D Structure Groups
without a View
Intended Use
This diagnostic task should be executed:
• After upgrade to 11.0 M020
• Whenever S1000D structure parts may have been created without a view
assignment for releases prior to 11.0 M020
• When requested by PTC
Service Information Manager AAD — Identify outdated Country
Codes and Language Codes
Diagnostic Task Description
Finds the S1000D product/library templates where country code and language
code support does not conform to these standards:
• ISO 3166-1: Code for the representation of names of countries and their
subdivisions - Part 1: Country codes (Issue/Version 2006, 2007, 2008)
• ISO 639-1: Codes for the representation of names of languages - Part 1:
Alpha-2 code (Issue 2002)
This task is optional.
Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.
Intended Use
This diagnostic task should be executed:
• When updating an 11.1 F000 installation (optional)
• When requested by PTC
Service Information Manager AAD — Update Creo View
Configurations for S1000D Publishing Rules Report
Diagnostic Task Description
Identifies any existing S1000D products that do not include sample publishing
rules that support the inclusion of secondary content (. pvz or . cgm) for
illustrations based on Creo Illustrate (.c3di) or Servigistics Arbortext IsoDraw (.
iso) graphics in Servigistics InService A&D and PDF output. The diagnostic task
lists the products that do not include the publishing rules, and advises which
products that can be updated.

Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.

86 Windchill Diagnostic Utility Guide

 Service Information Manager AAD — Update Creo View
Configurations for S1000D Publishing Rules Report
Intended Use
This diagnostic task should be executed:
• After upgrade to 11.0 M030, if there is a business requirement to maintain
secondary content of Creo View or Servigistics Arbortext IsoDraw
illustrations in an existing S1000D product
• When requested by PTC
Service Information Manager AAD — Verify OOTB Product OIRs to
Update
Diagnostic Task Description
Lists all OIRs that can be updated if they are present in an S1000D product:
1. OIRs whose default content has been updated in 11.1 M010
• S1000D Data Module
• S1000D Cage Based Information Control Number
• S1000D Model Based Information Control Number
• S1000D Publication Module
• S1000D Publication Module Content Holder
• S1000D Publication Structure
2. OIRs whose default content has not changed in 11.1 M010
• S1000D Data module Content Holder
• S1000D Cage Based Information Control Number Content Holder
• S1000D Cage Based Information Control Number Content Holder
This WinDU will list all OIRs of these names that appear in an existing S1000D
product. You can run the associated repair task (WinRU) Service
Information Manager AAD - Update OOTB Product OIRs to update
the OIRs automatically.
Note
Take care if any of your existing OIRs (including content holder OIRs)
contain customizations. These will be overwritten if you run the
recommended WinRU. PTC recommends that you update existing OIRs
manually if they contain customizations. For more information, see S1000D
Object Initialization Rules in the Windchill Help Center.
Note
This diagnostic task only applies to installations with Windchill Service
Information Manager – S1000D Module.

WinDU Diagnostic Tasks 87

 Service Information Manager AAD — Verify OOTB Product OIRs to
Update
Intended Use
This diagnostic task should be executed:
• After any update/upgrade to 11.1 M010, if the named OIRs exist at product
level (without customizations)
• When requested by PTC
Service Information Manager — Identify Duplicate Service Effectivity
Records
Diagnostic Task Description
Identifies any duplicate service effectivity records.
Intended Use
This diagnostic task should be executed:
• When service effectivity is imported from releases prior to 11.1 F000
• When requested by PTC
Service Information Manager — Identify Service Product Hierarchy
Layouts
Diagnostic Task Description
Identifies layouts that are specific to service product hierarchy.
Intended Use
This diagnostic task should be executed:
• After upgrading or updating to Windchill 11.1 M010 or later
• To use service product hierarchy features that are added in Windchill 11.1
M010 release
• When requested by PTC
Service Information Manager — Identify New Access Control Lists
(ACLs) to be added for Service Information Manager Roles
Diagnostic Task Description
Identifies new Access Control Lists (ACLs) to be added for Service Information
Manager roles.
Intended Use
This diagnostic task should be executed:
• After updating to Windchill 11.1 M010 or later
• When requested by PTC.
Shopping Cart Exists Validator
Diagnostic Task Description
This diagnostic task ensures that all shopping carts were successfully migrated to

88 Windchill Diagnostic Utility Guide

 Shopping Cart Exists Validator
the new InService 6.0 system. In Service Center 10.1, shopping carts are of type
SCCart. Starting in InService 6.0, shopping carts are of type SCEShoppingCart.
This task will output valid results only when executed immediately after the
upgrade and before any new carts are created or migrated ones are deleted.
This task:
1. Validates that the number of shopping carts of type SCCart is the same as the
number of shopping carts of type SCEShoppingCarts. A failure message is
logged if the counts do not match.
2. Checks for any shopping carts in SCCart that are not in SCEShoppingCart. A
log is created of any carts that are not found. If all carts are found, a success
message is logged.
3. Checks that all shopping carts of type SCEShoppingCart have the correct
classnameA2A2. A log is created of any carts that do not have the correct
classnameA2A2. If all carts have the correct class name, a success message is
logged.
Intended Use
This diagnostic task should be executed:
• Immediately after upgrading to InService 6.0
• When requested by PTC
SQLServer Uniqueness Constraint Violation Report
Diagnostic Task Description
This diagnostic task detects violations of uniqueness constraints defined in the
introspection data for each class.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
System Configuration Replication Security Diagnostic Task
Diagnostic Task Description
This diagnostic evaluates your Windchill configuration to discover any security
risks. If a risk is detected, a message displays with instructions for fixing the
possible vulnerability. If no risk is detected, a confirmation message displays.

WinDU Diagnostic Tasks 89

 System Configuration Replication Security Diagnostic Task
Intended Use
This diagnostic task should be executed:
• After configuring security labels
• After expanding replication to sites outside of the United States
• Before upgrade
• When requested by PTC
Team_Org Group Validator
Diagnostic Task Description
This diagnostic task validates that the shared team's _ORG group is a member of
the associated local team's _ORG group.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Type Name and Logical Identifier Invalid Characters Report
Diagnostic Task Description
This diagnostic task validates type’s name and logical Identifier. It reports any
type’s name or logical Identifier if it contains invalid characters.
Intended Use
This diagnostic task should be executed before upgrade.
Types Checkout Status Report
Diagnostic Task Description
This diagnostic task detects and reports any WTTypeDefinition in checkout state.
If a checked out WTTypeDefinition is found, the task will fail. To resolve this,
the checked out WTTypeDefinition should either be checked in or an “undo
checkout” operation should be performed.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Unreferenced Files Report
Diagnostic Task Description
This diagnostic task lists the unreferenced content files in the Windchill System

90 Windchill Diagnostic Utility Guide

 Unreferenced Files Report
and total filesize consumed by them. Unreferenced content files are the result of:
1. Failed upload
2. Deletion of Business Object from UI
Following verbose in wt.properties file should be enabled in order to generate
detailed logging:
wt.fv.master.log.enabled=true wt.fv.replica.log.enabled=true
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC

Note
This diagnostic task can also be run frequently to check the Windchill system
health from disk storage perspective and hence plan for repairing the data
accordingly.
Update Count A2
Diagnostic Task Description
This diagnostic task will determine the tables that have the column
UPDATECOUNTA2 values set to 0 (zero). Value should never be 0 (zero),
otherwise the objects will be marked as non-persisted when retrieved by the
POM, and cause problems when trying to access or modify objects. This should
be run after the upgrade is complete.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Upgrade Constraints Check
Diagnostic Task Description
This diagnostic task reports on data that will cause the AddConstraints phase of
the UpgradeManager to fail.
For this diagnostic task there is a property that needs to be set in
<Windchill>\codebase\windu.xconf for this task to be successful.
The property is:
com.ptc.windchill.windu.testwindufortargetversion

The value should be set to the upgrade target release level.

WinDU Diagnostic Tasks 91

 Upgrade Constraints Check
Example: When running WinDU on R8 before upgrading to R9, the value should
be set to “9.0”. The default value of the property is null and it will fail if a digit
value has not be entered.
After the value has been set you need to save the file and propagate. To
propagate it you need to run xconfmanager –p from the Windchill shell.

Note
At 6.2.6, this property does not exist and does not need to be set.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Upgrade Property Viewer
Diagnostic Task Description

Note
Previously, this task was called Upgrade Property Collector.
Gathers information about the system into a file called <Windchill>/
ReviewedSourceUpgrade.properties, which can be copied and
renamed to an upgrade target system at <Windchill>/Upgrade/
UpgradePhases/GatherUpgradeProperties/
upgradeUser.properties to pre-populate many fields in Upgrade
Manager. This can simplify the process of gathering system configuration
information needed for upgrade.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
User and Personal Cabinet Report
Diagnostic Task Description
This diagnostic task reports the AdministrativeDomain of users, the
corresponding LDAP node for each user and also the AdministrativeDomain of
the user's Personal Cabinet. The output of this task is a text file.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC

92 Windchill Diagnostic Utility Guide

 Validate Attributes And Soft Types
Diagnostic Task Description
This task will run as part of the pre-upgrade mandatory WinDU task group. The
purpose of this task is to identify and report data that would cause an EPM
migrator to failure during an upgrade. This gives the customer the ability to
cleanse the data before starting the upgrade process. This task detects if certain
attributes are present with a correct data type. If certain attributes present in the
system have a different data type than expected, then the WinDU task will fail.
Similarly, if certain soft types are already in the system that are not expected to
be present, then this WinDU task will fail.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Validates All wfprocesses for Valid Workflow Template Reference
Diagnostic Task Description
This diagnostic task searches all processes in the system and reports if a process
has an invalid WfProcessTemplate Reference.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Validate Context Groups and User Defined Groups in DB and in
LDAP (Context Validator)
Diagnostic Task Description
This diagnostic task will:
• Validate the existence of the AdministrativeDomain object of each
WTPrincipal object
• Validate the existence of WTGroup objects for all the context groups and that
they are all associated to one and only one context
• Confirm LDAP entry exists in appropriate adapter for each WTGroup in the
database
• Confirm that all LDAP internal groups have a corresponding WTGroup
object in the database
• Validate dangling application context nodes in LDAP that don’t have a
corresponding entry in the database

WinDU Diagnostic Tasks 93

 Validate Context Groups and User Defined Groups in DB and in
LDAP (Context Validator)
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Validate ECAD R10.1 Data Types
Diagnostic Task Description
This diagnostic task will check if new (for 10.1) ECAD subtypes are installed
and valid.
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
Validate EPM Soft Type Name
Diagnostic Task Description
This diagnostic task checks and reports any out-of-the-box EPM soft types that
have been renamed on source system. From Windchill 10.0 onwards users will
not be allowed to rename out-of-the-box EPM subtype name.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Validate Family Table Data
Diagnostic Task Description
This diagnostic task reports possible problems with family tables. It checks all
family table members in the database against these possible problems.
Intended Use
This diagnostic task should be executed when requested by PTC.

94 Windchill Diagnostic Utility Guide

 Validate Principals in the DB and in LDAP (Principal Validator)
Diagnostic Task Description
The validator mainly tests 5 different cases:
1. Checking that all external groups defined in JNDI adapters exist in the
database.
• Validates only users and organizations
• Queries WTUser or WTOrganization table linking it with the
RemoteObjectInfo table
• Validates that RemoteObjectId is associated to an existing repository
• Checks to see if a disabled principal has the Mark for Delete column set
instead of the disabled column. If so, provides sql scripts to disable it
correctly.
• Checks to see if a disabled principal has its corresponding
RemoteObjectInfo and OwningRepositoryLocalObject entries (ufid
entries) deleted. If not, provides sql scripts to do so.
• Checks to see if a principal is enabled but is missing ufid entries. If so,
suggests to use the principal administrator to clean up the principal.
• If principal is enabled and has the ufid entries, then it checks to see if the
principal exists in LDAP. If it does not exist, it suggests to use the
principal administrator page to delete or update the principal.
2. Checking all principals in DB for linkage to JNDI LDAP entries.
• Validates only external groups (i.e. User defined Site and Org Level
groups)
• Queries groups directly under the default search base and under each org
node in
• Matches the distinguished name (dn) for the node in LDAP to a
corresponding RemoteObjectId entry in the database
• If RemoteObjectId entry does not exist, it suggests to use Principal
Administrator to clean up the principal.
• If WTGroup entry does not exist, but RemoteObjectId exists, it provides
sql statements to clean up RemoteObjectId from RemoteObjectInfo table.
Also, cleans up the group’s corresponding
OwningRepositoryLocalObject table entry.
3. Checking that all Repository references from OwningRepositoryLocalObject
resolve to real objects

WinDU Diagnostic Tasks 95

 Validate Principals in the DB and in LDAP (Principal Validator)
• Validates that all repository references from
OwningRepositoryLocalObject table resolve to an entry in the Repository
table. If there are dangling entries, it provides sql scripts to clean them
up.
4. Checking that all Principal references from OwningRepositoryLocalObject
resolve to real objects.
• Validates that all local object references from
OwningRepositoryLocalObject table resolve to entries in the
corresponding tables i.e for WTUser, WTGroup and WTOrganization. If
there are dangling entries, it provides sql scripts to clean them up
5. Checking all principals in DB for linkage to corresponding domains entries
in the DB.
• Validates all principals existing in the database have a corresponding
domain. If a corresponding AdministrativeDomain entry does not exist
for a given principal, then it logs this as data corruption.
• For each principal type, if there is at least one entry with a missing
domain, it provides the appropriate sql script to associate the principals to
the unaffiliated domain.
Intended Use
This diagnostic task should be used to analyze principal data associated to
container. Log any corrupted data and ways to resolve the issue.
Validate Sub Folder Name
Diagnostic Task Description
The diagnostic task reports on SubFolder and SubFolderLinkConstraint records
with a space in the name.
Intended Use
This diagnostic task should be executed:
• When leading or trailing spaces in the SubFolder name, which has been
known to cause problems in the SubFolderLinkConstraint migrator. This
extra space was caused by a bug in Windchill, which has been subsequently
fixed, that allowed for the extra space in a SubFolder name. During migration
when this extra space wouldn’t get cleaned up, a uniqueness exception can be
thrown.
• Before upgrade
• When requested by PTC

Note
This diagnostic task is not dependent on any other diagnostic task.

96 Windchill Diagnostic Utility Guide

 Validate the quality of Information Structure data prior to publishing
from SIM to SC
Diagnostic Task Description
This diagnostic task validates information structure objects. It reports invalid
data associated with information structure objects and validates the following
attribute characteristics:
• product_family is a non-empty PHRoot
• IS and PHRoot have the same organization reference
• Bundle Version is a non-empty value in format x.x.x or x.x.x.x
• Bundle Volume ID is non-empty and unique among IS/PS
Intended Use
This diagnostic task should be executed:
• Before PETL
• When requested by PTC
Validate the quality of Publication Structure data prior to publishing
from SIM to SC
Diagnostic Task Description
This diagnostic task validates publication structure objects. It reports invalid data
associated with publication structure objects and validates the following attribute
characteristics:
• product_family is a non-empty PHRoot and is also a product_family value of
an existing information structure root
• Bundle Version is a non-empty value in format x.x.x or x.x.x.x
• Bundle Volume ID is non-empty and unique among IS/PS
Intended Use
This diagnostic task should be executed:
• Before PETL
• When requested by PTC
Validate the quality of Part List data prior to publishing from SIM to
SC
Diagnostic Task Description
This diagnostic task validates the quality of part list data on Windchill Service
Information Manager prior to sending to Servigistics Service Center via the
Publish, Extract, Transform, and Load (PETL) process. This task reports any part
lists that are in an invalid state.
The task currently validates that every part list has a related documenting part.

WinDU Diagnostic Tasks 97

 Validate the quality of Part List data prior to publishing from SIM to
SC
Intended Use
This diagnostic task should be executed:
• Before PETL
• When requested by PTC
Validate the quality of Product Hierarchy Root data prior to
publishing from SIM to SC
Diagnostic Task Description
This diagnostic task validates the quality of product hierarchy root data on
Windchill Service Information Manager prior to sending to Servigistics Service
Center via the Publish, Extract, Transform, and Load (PETL) process. This task
reports any PH Roots that are in an invalid state.
The task currently validates that every PH Root is a top-level part.
Intended Use
This diagnostic task should be executed:
• Before PETL
• When requested by PTC
Validate the quality of Product Hierarchy Node data prior to
publishing from SIM to SC
Diagnostic Task Description
This diagnostic task validates the quality of product hierarchy node data on
Windchill Service Information Manager prior to sending to Servigistics Service
Center via the Publish, Extract, Transform, and Load (PETL) process. This task
reports on any PH Nodes that are in an invalid state.
The task currently validates that every PH Node has only one parent PH Root or
PH Node.
Intended Use
This diagnostic task should be executed:
• Before PETL
• When requested by PTC
Validate the quality of Product Hierarchy Structure data prior to
publishing from SIM to SC
Diagnostic Task Description
This diagnostic task validates the quality of product hierarchy structure data on
Windchill Service Information Manager prior to sending to Servigistics Service
Center via the Publish, Extract, Transform, and Load (PETL) process. This task
reports on any PH Nodes that are in an invalid state.

98 Windchill Diagnostic Utility Guide

 Validate the quality of Product Hierarchy Structure data prior to
publishing from SIM to SC
The task currently validates that every descendent node in a PH Root is a PH
Node.
Intended Use
This diagnostic task should be executed:
• Before PETL
• When requested by PTC
Validate the quality of Product Instance data prior to publishing from
SIM to SC
Diagnostic Task Description
This diagnostic task validates the quality of product instance data on Windchill
Service Information Manager prior to sending to Servigistics Service Center via
the Publish, Extract, Transform, and Load (PETL) process. This task reports any
product instances that are in an invalid state.
The task currently validates the following:
• Every product instance is a top-level part
• Every product instance has no more than one child part that is PH Node
Intended Use
This diagnostic task should be executed:
• Before PETL
• When requested by PTC
Validate the quality of Service Effectivity data prior to publishing
from SIM to SC
Diagnostic Task Description
This diagnostic task confirms that service effectivity data has the appropriate
attributes prior to publishing fromWindchill Service Information Manager to
Servigistics Service Center. The target object of the service effectivity must be an
information element, such as a document, parts list, or dynamic document. The
context of the service effectivity mush be a product hierarchy root, product
hierarchy node, or product instance.
Intended Use
This diagnostic task should be executed:
• Before using the Publish, Extract, Transform, and Load (PETL) process
• When requested by PTC
Validate Users, Groups and Organizations in the DB and in LDAP
Diagnostic Task Description
This diagnostic task validates that there are no referential integrity issues for

WinDU Diagnostic Tasks 99

 Validate Users, Groups and Organizations in the DB and in LDAP
Users, Groups and Organizations between the Windchill database and the JNDI
adapters that the system is configured to use.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
VariantSpec Cabinet/Container Diagnostic Task
Diagnostic Task Description
Reports all VariantSpec objects where the object’s container does not match the
object’s cabinet’s container. This is the same query as the
CabinetBasedDataContainerAlignmentDT except it is specific for VariantSpec
objects.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
• This diagnostic task is only relevant for Options and Variants functionality
within Windchill PDMLink
Verify All Principals Domain
Diagnostic Task Description
This diagnostic task checks if principals are in the default domain. The result it
reports for external principals is for informational purposes, and updates are not
mandatory. Internal principals, however, are required to be in the default domain
and problems reported are required to be addressed
Intended Use
This diagnostic task should be executed:
• Before upgrade
• Before migration
• When requested by PTC
Verify Source Internet Domain
Diagnostic Task Description
The diagnostic task checks whether the source (i.e. the organizations) has a valid
internet domain or not. The domain should not have the ‘_’ character in it. This
diagnostic task lists all the organizations with their internet domain having ‘_’ in
them.

100 Windchill Diagnostic Utility Guide

 Verify Source Internet Domain
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Verify Information Resource Table
Diagnostic Task Description
This diagnostic task finds Deliverables which are partially broken with its
Subject object. If the diagnostic finds any entries, Project ->Folders page which
contains Subject objects (Docs/Parts) with deliverables will throw exception
while rendering.
Intended Use
This diagnostic task should be executed:
• Before and after upgrade
• When requested by PTC
Verify Property Settings WinDU Task
Diagnostic Task Description
This diagnostic task checks and reports if property “wt.access.enforce” is not set
to true after upgrade.
Intended Use
This diagnostic task should be executed after upgrade.
Verify That All Lifecycle Templates Have a Final Phase
Diagnostic Task Description
This diagnostic task reports life cycle templates that do not have a final phase.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Verify There are No Checked-Out Container Templates
Diagnostic Task Description
This diagnostic task verifies that there are no checked out container templates,
and reports any that are checked out so that they can be checked in before
starting an upgrade to 9.0.

WinDU Diagnostic Tasks 101

 Verify There are No Checked-Out Container Templates
Intended Use
This diagnostic task should be executed:
• Before upgrading to 9.0
• When requested by PTC
Verify workflow Processes are Readable
Diagnostic Task Description
This diagnostic task reports all workflow processes in unreadable state. It reads
all context data or workflow variables (from database blob) and reports processes
that have readable blob content. One should check for customization on target
systems related with Roles or LC states and customized classes.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Version Attribute Alignment
Diagnostic Task Description
This informational task reports masters that have versions in different cabinets,
domains, or that have differing ownerships. It is not required that all versions be
aligned within the same cabinet or administrative domain or have the same
owner for successful migration. However, before the data can be moved to a
different container after migration, all versions must be aligned under the same
cabinet, administrative domain and have the same owner.
Intended Use
This diagnostic task should be executed:
• Before migration
• When requested by PTC
Validates All wfprocesses for Valid Workflow Template Reference
Diagnostic Task Description
This diagnostic task finds all workflow processes in the system which don’t have
Valid Process Template references. It gives a list of workflow processes.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

102 Windchill Diagnostic Utility Guide

 Work Package Cabinet Report
Diagnostic Task Description
Packages migrated from version 9.1 may contain cabinets with package-private
content located in them (documents, links, bookmarks). This diagnostic task
identifies the contents of cabinets of work packages migrated from version 9.1 so
that they could optionally be upgraded by running the corresponding WinRU
task.
Intended Use
This diagnostic task should be executed:
• After upgrade
• When requested by PTC
Workflow Process Referring to a Non-Existent Team
Diagnostic Task Description
This diagnostic task checks for all processes referring to a missing team.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Workflow Process Report
Diagnostic Task Description
This diagnostic reports context data for workflow processes in system. It will
read all context data or workflow variables (from db blob) and reports processes
having readable blob content. One should check for customization on target
system related with Roles/LC states and customized classes.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC
Workspace Baselines Check
Diagnostic Task Description
Baselines will not be seen in workspace listings. Please run WinRU “Add to
Workspace Repair” Task to fix these errors.
Intended Use
This diagnostic task should be executed when detecting EPM Workspace
Baseline corruptions.

WinDU Diagnostic Tasks 103

 WPC CWP Permissions Diagnostic Task
Diagnostic Task Description
This diagnostic task would find out the CAD Documents that are under
ownership transfer to the other site. The Customer is required to complete the
ownership transfer before Upgrade. Otherwise the ownership transfer deemed
cancelled and CAD Documents will continue to be owned by this site. A report
will contain the name of the CAD Documents under ownership transfer.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

Note
This task should be executed only if Windchill PLM Connector is installed
WPC Owning Repository Local Object Links
Diagnostic Task Description
This diagnostic task will list all CAD documents whose ownership is accepted
from the other site but still contains Remote Links. It will list all CAD Document
names meeting above criteria along with their version and iteration.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

Note
This diagnostic task should be executed only if Windchill PLM Connector is
installed
Identify Workspace New Parts in Personal Cabinet
Diagnostic Task Description
This diagnostic task will capture all the new workspace parts in your Personal
Cabinet. When found you can delete the corrupted data manually and later run
the Repair Utility to check in the new parts to commonspace.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

104 Windchill Diagnostic Utility Guide

 Option and Choice Information Multiple Consecutive Spaces Report
Diagnostic Task Description
This diagnostic task provides a report of existing options, choices, option groups,
and alias expressions containing more than one consecutive spaces in the name
or number.
Intended Use
This diagnostic task should be executed after upgrade.
Detect Duplicate Choices on Option Filter
Diagnostic Task Description
This diagnostic task detects any duplicate links present between an Option Filter
and a choice.
Intended Use
This diagnostic task should be executed after upgrade.
Checkout Consistency Report
Diagnostic Task Description
This task provides a report on the consistency between information used by
“checkin” and “checkout” operations. The information is used to manage the
checkout status, the association between versions, and the exclusive ability to
modify a version. Inconsistencies may prevent users from performing a
checkout, checkin, or undo checkout action.
Intended Use
This diagnostic task should be executed:
• Before upgrade
• When requested by PTC

WinDU Diagnostic Tasks 105

 Index

A ChoiceRule Number Uniqueness

Diagnostic Task, 24
A&D Part Instance Traceability
Classification Checkout Health Status,
Conformance Report, 19
24
Consolidation Access, Notification,
C and Index Rules Report, 24
Consolidation Object Initialization
Cabinet Based Data Container
Rules Report, 25
Alignment Conflict Report, 19
Consolidation Soft Attribute and
Cabinet Based Data Container
Constraint Report, 26
Alignment Report, 20
Container Names with Double Spaces,
Cabinet Member Data Report, 20
27
Case Table Cell Type Diagnostic Task,
Container Structure, 27
20
Corrupt Family Table Check, 28
Check Assigned Activity Template for
WorkItems, 21 Corrupt Latest Iteration Report, 28
Check Change Status Indicator, 21-22 Corrupt Share Access, 28
Check Name Conflict In Reports From Corrupt WorkItem Access Diagnostic
R9 to R10, 22 Task, 28
Count Rows Per Table, 29
Check Package Base Data Status, 23
Count the number of usage links with
Check Part List Diagnostic Task, 23
the blank reference field, 29
Check Project Monitor Items
Templates Diagnostic Task, 23
Check Project Monitor Templates D
Diagnostic Task, 23
Dangling Export Record Check, 29
Check S1000D ICN Lifecycles to be
Dangling PBO Ref, 30
reassigned, 81
Dangling SyncInfo Diagnostic Task,
Check uniqueLinkId Errors on
30
EPMMemberLink, 24
Database Index Utility, 30
Checked Out CAD Documents Check,
Database Object Validity Check, 30
22
Deprecated Classes, 31
Checkout Consistency Report, 105
Detect Access Policy Rules for
Checks the S1000D Publication
SavedViewInfo Objects, 31
Structures, Modules (and holders)
Detect Analysis Activities that are
that have lifecycles to be reassigned,
Orphans, 31
81

106 Windchill Diagnostic Utility Guide

Detect Change Tasks which have been Domain Policy Rule, 42
Orphaned, 32 Domain Structure, 42
Detect Checked-out Objects to be Duplicate Change Links Diagnostic
Changed, 32 Task, 42
Detect Checked-out Objects to be Duplicate ChoiceMappableChoiceLink
Promoted, 32 Diagnostic Task, 43
Detect Custom Percent QOM Data, 33 Duplicate IBA Values Check, 43
Detect Deleted Sub Type Issues, 33 Duplicate IDA2A2, 43
Detect Duplicate Choices on Option Duplicate OptionSetMemberLink
Filter, 105 Diagnostic Task, 43
Detect Incorrect Domain Inheritance in Duplicate Recent Update Check
DomainAdministered Foldered Diagnostic Task, 44
Objects, 33 Duplicate Shares, 44
Detect Incorrect Parent Folder Settings Duplicate Table Column Data Check,
in Foldered Objects, 34 44
Detect Invalid CounterPartIds, 34 Duplicate Ufid Entries, 45
Detect Invalid SupportingDataFor Duplicates in Control Branch, 45
Links, 34
Detect Issues in Specification /
E
Requirement Types, 35
Detect Missing Audits for Change ECAD Application Data Report, 45
Object Workitems, 36 ECAD Content Definition Report, 46
Detect Missing Domains, 35 ECAD EPM Document Checkout
Detect Missing or Duplicate Entries in Status Report, 46
IterFolderMemberLink Table, 35 ECAD Report Shared And PDM
Detect Missing Checked Out, 47
WfAssignedActivityTemplate for ECAD Validate Data, 47
Change Management WorkItems, 36 Empty Table Report, 48
Detect Orphan Default Value and EPM Document CAD Name Conflict
Group Memberships, 36 Check, 48
Detect Saved Searches and Histories EPM Document Number Conflict
Having Old LDAP Entries (LDAP Check, 48
Domain or Base DN) OR WebApp EPMDoc SubType Check, 46
Names, 37 EPMDocumentVerifiedColumnCheck,
Detect Workflow Processes Having 49
Unresolvable PBO Ref, 40 ESI Schema Detector, 49
Diagnose DomainAdministered Export Strings for Type Conversion, 50
Objects In Wrong Domain, 41 External Cart Items Validator, 50
Diagnostic for Assembly Features for Extract Workflow Expressions, 51
Representations, 41
Domain Administered Objects Domain
Reference Check, 40

Index 107
F Invalid Container Templates, 60
Invalid Internal Principals with UFID,
Find all NavigationCriterias associated
60
to a DerivedImage in which the
Invalid LDAP Entries, 60
owner attribute is incorrect, 51
Invalid Phase Templates, 61
Find any Orphan Representation
Invalid Project Container Names, 61
NavigationCriterias, 52
Invalid Series Values, 61
Find Dangling EPMCheckpoint
Invalid Workflow Tasks, 62
Objects, 52
Invalid Workitems and Workflow
Find IBAs for MPMLink objects for
Processes without PBOs, 61
which the name has been changed, 52
Iteration Attribute Alignment, 62
Find Missing ImportedBookmarks in
PostingAttachmentLink Table for
Postings, 53 L
Find Orphan ShadowCache, 54
List Checked Out/Disabled Workflow-
FindOrphanAdhocActivitiesDT, 53
Lifecycle Templates, 62
FindPrivateWorkSpaceObjAssociated-
List New Child Parts in Structure, 63
ToChange, 54
Locate Class References, 63
Folder Name Mismatch, 54
Locate Dangling References, 63
Locate Enum Type References, 64
G Locate invalid authoring language, 64
Generate Data Validation Reports, 54
Gfx Content Check, 55 M
Group Domain and Location, 55
Missing Container References for
Notebooks and Discussion Forums,
I 64
Missing IOPState Diagnostic Task, 65
ID Sequence Analysis, 56
Missing Master Discovery Tool, 65
Ida2a2 Analysis, 56
Missing Name of Discussion Topic, 65
Identify Workspace New Parts in
Missing PreferenceCategory or
Personal Cabinet, 104
PreferenceDefinition from
Inaccessible Replicated Content
PreferenceCategoryDefinitionLink
Report, 56
DT, 66
Inconsistent Create Stamps Report, 57
Missing Representables, 66
Inconsistent Version ID, 57
Missing URL and
Incorrect Promotion Preference Table
HOLDERTOCONTENT Reference
View Name, 57
for Bookmarks, 66
Internal Cart Item Mapping Validator,
MissingControlBranchCleanserDT, 65
58
MPMLink Number Diagnostic Task,
Internal Cart Items Validator, 58
66
Internal Groups and pending Users
MPMLink: Updating Occurrence
Check, 59
Positioning Diagnostic Task, 68

108 Windchill Diagnostic Utility Guide

MPMLinkMissingSelfEquivalence- Pre 8.0M050 Invalid Series Values, 75
DiagnosticTask, 67 Preferences Report, 76
Prepare Report for Count of Objects
Referencing Classic Data, 76
N
ProductView ED to PVS, 76
NamespaceUniquenessCheckDT, 69
Notification Conversion of ProjectLink
OwnerRefs, 69 R
Null Container References Check, 70 Report all Lifecycle Templates with
Null DerivedFrom Report, 70 One or More Missing Phases, 77
Null Namespace Attribute Check, 70 Report All Organization Owned
Null Series Diagnostic Task, 70 Namespace Objects in External
Organizations, 77
Report Checked Out and Uploaded
O
Family Tables, 78
Object Already Unlocked Diagnostic Report Non Change Objects Processes
Task, 71 With Missing Audits, 78
Object in More than One Lifecycle Report Registered Users in the System,
State, 71 78
Object Initialization Rule Conflict Required Soft Attribute Report, 78
Report, 71 Revision Label Corruption Report, 79
Object Initialization Rule Report, 71
Option and Choice Information
Multiple Consecutive Spaces Report,
S
105 Saved Search Constraint Violation
OptionChoice Number Uniqueness Check, 79
Report, 72 Saved Search Null Criteria Check, 79
OptionSet Container Diagnostic Task, Sequence Seed Conflict Diagnostic
72 Task, 80
Order Exists Validator, 72 Series Sort ID Diagnostic Task, 80
Organization and User Duplicates Service Information Manager —
Check, 73 Identify Duplicate Service Effectivity
Organization Owned Reference, 73 Records, 88
Orphaned Terminal Objects Diagnostic Service Information Manager —
Task, 74 Identify New Access Control Lists
Owning Repository Validator, 74 (ACLs) to be added for Service
Information Manager Roles, 88
Service Information Manager —
P
Identify Service Product Hierarchy
Personal Cabinet Data Report, 74 Layouts, 88
Personal Cabinet Owners Deleted Service Information Manager AAD —
Report, 75 Confirm Existence of the S1000D
Post Upgrade Visualization Count, 75

Index 109
 Product Template "S1000D General U
SNS Sets Product", 82
Unreferenced Files Report, 90
Service Information Manager AAD —
Update Count A2, 91
Confirm Existence of the S1000D
Upgrade Constraints Check, 91
Product Templates to be Updated, 82
Upgrade Property Viewer, 92
Service Information Manager AAD —
User and Personal Cabinet Report, 92
Diagnose S1000D Service Parts, 83,
86
Service Information Manager AAD — V
Find missing DML and DDN Validate Attributes And Soft Types, 93
templates and out-dated sample Validate Context Groups and User
publishing rules, 84 Defined Groups in DB and in LDAP
Service Information Manager AAD — (Context Validator), 93
Find S1000D Products where the Validate ECAD R10.1 Data Types, 94
preference 'Conflict for Out of date Validate EPM Soft Type Name, 94
Secondary content upon Checkin' is Validate Family Table Data, 94
set to 'Yes', 84 Validate Principals in the DB and in
Service Information Manager AAD — LDAP (Principal Validator), 95
Find S1000D products without Creo/ Validate Sub Folder Name, 96
IsoDraw templates, 85 Validate the quality of Information
Service Information Manager AAD — Structure data prior to publishing
Find S1000D Structure Groups from SIM to SC, 97
without a View, 85 Validate the quality of Part List data
Service Information Manager AAD — prior to publishing from SIM to SC,
Update Creo View Configurations for 97
S1000D Publishing Rules Report, 86 Validate the quality of Product
Service Information Manager AAD — Hierarchy Node data prior to
Verify OOTB Product OIRs to publishing from SIM to SC, 98
Update, 87 Validate the quality of Product
Shopping Cart Exists Validator, 88 Hierarchy Root data prior to
SQLServer Uniqueness Constraint publishing from SIM to SC, 98
Violation Report, 89 Validate the quality of Product
System Configuration Replication Hierarchy Structure data prior to
Security Diagnostic Task, 89 publishing from SIM to SC, 98
Validate the quality of Product Instance
T data prior to publishing from SIM to
SC, 99
Team_Org Group Validator, 90
Validate the quality of Publication
Type Name and Logical Identifier Structure data prior to publishing
Invalid Characters Report, 90 from SIM to SC, 97
Types Checkout Status Report, 90

110 Windchill Diagnostic Utility Guide

Validate the quality of Service
Effectivity data prior to publishing
from SIM to SC, 99
Validate Users, Groups and
Organizations in the DB and in
LDAP, 99
Validates All wfprocesses for Valid
Workflow Template Reference, 93,
102
VariantSpec Cabinet/Container
Diagnostic Task, 100
Verify All Principals Domain, 100
Verify Information Resource Table,
101
Verify Property Settings WinDU Task,
101
Verify Source Internet Domain, 100
Verify That All Lifecycle Templates
Have a Final Phase, 101
Verify There are No Checked-Out
Container Templates, 101
Verify workflow Processes are
Readable, 102
Version Attribute Alignment, 102

W
Work Package Cabinet Report, 103
Workflow Process Referring to a Non-
Existent Team, 103
Workflow Process Report, 103
Workspace Baselines Check, 103
WPC CWP Permissions Diagnostic
Task, 104
WPC Owning Repository Local Object
Links, 104

Index 111