honeywell tracetm · trace installation htdoc-x574-en-140.1a 13 iis server is halted. solution:...
TRANSCRIPT
HONEYWELL TRACETM
R 140.1
___________________________________
Troubleshooting Guide
___________________________________
HTDOC-X574-en-140.1A
July 2020
2
DISCLAIMER
This document contains Honeywell proprietary information. Information contained herein
is to be used solely for the purpose submitted, and no part of this document or its contents
shall be reproduced, published, or disclosed to a third party without the express
permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell
disclaims the implied warranties of merchantability and fitness for a purpose and makes
no express warranties except as may be stated in its written agreement with and for its
customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential damages.
The information and specifications in this document are subject to change without notice.
Copyright 2020- Honeywell International Sàrl
HTDOC-X574-en-140.1A 3
Table of contents 1 ABOUT THIS DOCUMENT .............................................................................................................................. 5
1.1 Revision history ....................................................................................................................................................... 5
1.2 Related documents ............................................................................................................................................... 5
2 TRACE INSTALLATION ................................................................................................................................... 6
2.1 Trace web application not working ................................................................................................................ 6
2.2 Trace Installation not progressing .................................................................................................................. 8
2.3 Installation of Honeywell Trace IAA Report Server appears to have failed ................................ 9
2.4 Data Collection user permission window does not pop up during Remote Node installation ................................................................................................................................................................. 9
2.5 Invalid_grant: user does not have a valid license to use this application ................................. 10
2.6 How to replace an existing license .............................................................................................................. 11
2.7 Invalid_grant: value cannot be null ............................................................................................................. 11
2.8 Data Collection page failed to load ............................................................................................................. 12
2.9 Trace Node login failed ..................................................................................................................................... 12
2.10 Unable to access Report page ...................................................................................................................... 13
2.11 Unable to view report packages on L3.5/L4 Trace Server post R121 to R140.1 migration.................................................................................................................................................................. 13
3 SYSTEM VALIDATION AND DATA COLLECTION ................................................................................ 14
3.1 Basic checks .......................................................................................................................................................... 14
3.1.1 IAA Report ................................................................................................................................................................ 14
3.1.2 Basic checks for TPS data collection from Trace ................................................................................. 14
3.1.3 Basic check for Experion ................................................................................................................................. 15
3.1.4 Basic check for Triconex .................................................................................................................................. 15
3.2 Agent didn't send any response for its activation. No heartbeat file created ....................... 15
3.3 Unable to connect to Remote Node ........................................................................................................... 18
3.4 Failed to read switch configuration ............................................................................................................ 19
3.5 Add Trace URL to Local intranet zone ...................................................................................................... 20
4 L3/L4 SYNCHRONIZATION ..................................................................................................................... 22
4.1 Check if connection between L3 and L4 Trace Servers is established .................................... 22
4.2 NextNine Relay Server ....................................................................................................................................... 23
4.3 Time zone and time format ............................................................................................................................. 24
4.4 Verify correct certificates are imported from L3 and L3.5/L4 ...................................................... 24
4.5 Verify the hosts file .............................................................................................................................................. 25
4.6 Verify that L3.5/L4 web URLs are accessible from L3 ..................................................................... 26
5 LICENSING ..................................................................................................................................................... 28
ABOUT THIS DOCUMENT
HTDOC-X574-en-140.1A 4
6 REPORTING .................................................................................................................................................... 29
7 ADMIN CONSOLE ........................................................................................................................................ 31
8 SQL TEMP DB CLEANUP OPERATION ............................................................................................... 32
8.1 Version R130 and above .................................................................................................................................. 32
8.2 Below version R130 ............................................................................................................................................ 32
8.3 Cleanup TempDB ................................................................................................................................................ 33
9 NOTICES.......................................................................................................................................................... 35
ABOUT THIS DOCUMENT
HTDOC-X574-en-140.1A 5
1 About this document
This document provides the information on how to troubleshoot the issues when you are
installing and using the Trace product. If you need any further help, raise a GTAC service
request, collect the logs as per the Trace Data Collection Guidelines Document and share
them with GTAC.
1.1 Revision history
Revision Supported Release
Date Description
A 140.1 July 2020 Initial release of the document for R140.1.
1.2 Related documents The following list identifies publications that may contain information relevant to the
information in this document.
Document Name Description
Prerequisites Guide This document provides instructions to help you plan a Honeywell
Trace installation.
Installation Guide This document provides instructions to install and configure
Honeywell Trace application.
User Guide This document provides instructions to use the Honeywell Trace
application.
Software Change
Notice
This document provides important information that must be read
prior to installing and working with Honeywell Trace R140.1.
TRACE INSTALLATION
HTDOC-X574-en-140.1A 6
2 Trace Installation
This chapter describes Trace installation related errors and fixes.
2.1 Trace web application not working 1. After installation, check if below folders are created:
C:\ProgramData\Honeywell\LSS-PT
C:\Program Files\Honeywell\LSS-PT
C:\Program Files (x86)\Honeywell (few files of Trace are deployed under this
folders as part of prerequisite)
2. Ensure below services are running; if not, run them in the listed order:
Sim Station
License Service
LSS-PT Data Collection Service
SQL Server Agent (MSSQLSERVER)
LSS-PT Data Synchronization
3. Check the IIS binding URL:
Open IIS Manager->Expand Sites -> Select Default Web Site and Choose To open
IIS: Open Run and type INETMGR
Your Trace Server should be added with certificate and port 443.
If Trace Server is not listed, check in MMS whether the certificate is created.
TRACE INSTALLATION
HTDOC-X574-en-140.1A 7
4. Check if the IIS components are enabled:
Open Server Manager and click Manage > Add Roles and Features. Click Next.
Select Role-based or feature-based installation and click next.
Cross check the enabled components under the Web Server (IIS) with the
following screenshot:
TRACE INSTALLATION
HTDOC-X574-en-140.1A 8
Enable if a component is missing and click next to install it.
2.2 Trace Installation not progressing Cause:
In Trace R140.1, installation may get stuck due to password not meeting Trace password
complexity requirements.
Solution:
Ensure you meet the following criteria:
a. Password length must be at least 8 characters and maximum 14.
TRACE INSTALLATION
HTDOC-X574-en-140.1A 9
b. Do not to use any special characters and use at least one upper case letter and
one number.
NOTE
In some cases, Trace installation may complete with passwords exceeding 14
characters, but the passwords will be truncated and Trace will not work properly.
2.3 Installation of Honeywell Trace IAA Report Server appears to have failed During Trace Server installation, you may get the following error message:
Cause:
Windows user used for installation is not part of Local Administrator Group.
Solution:
Login with the local administrator user created as part of the Windows OS installation,
right click on the Trace installer and select “Run as administrator”.
2.4 Data Collection user permission window does not pop up during Remote Node installation The following window does not appear during Remote Node installation in a workgroup
environment:
TRACE INSTALLATION
HTDOC-X574-en-140.1A 10
Cause:
The Remote Node is in a Public Network.
Solution:
Change to Private Network.
2.5 Invalid_grant: user does not have a valid license to use this application This error message appears while trying to log in the Trace Web Application.
Cause:
L4 Trace license has been issued for L3 installed Trace Server or the other way
around
Licensed Units are incorrect.
Solution:
Check the installed license from the Admin Console. If the Trace is installed in
Level 3, the license should not include below highlighted line. Request the Order
Management Team to disable the Level 4 option.
TRACE INSTALLATION
HTDOC-X574-en-140.1A 11
2.6 How to replace an existing license Perform the following steps to replace an existing license:
Delete the old *.license file from the below path in Trace Server node
C:\Program Files (x86)\Common Files\Honeywell\SimStation
Apply the new license (double click)
Restart the license service
Login to Trace Web Application
2.7 Invalid_grant: value cannot be null This error message appears while trying to log in the Trace Web Application:
Cause:
Web client user is not member of any LSS-PT Groups.
Solution:
Add the Web client user to any of the following group:
LSS-PT Engineers
LSS-PT Managers
LSS-PT Product admin
LSS-PT Report Users
TRACE INSTALLATION
HTDOC-X574-en-140.1A 12
2.8 Data Collection page failed to load Very rare cases, it may happen that the Data Collection page post R140 deployment will
show the following exception:
Cause:
Trace Services are not started automatically post installation.
Solution:
Go to the Service Manager and check if all the Trace services are running. If not, manually
start the services and reload the application.
2.9 Trace Node login failed Trace Node login fails and shows the following error:
Cause:
TRACE INSTALLATION
HTDOC-X574-en-140.1A 13
IIS server is halted.
Solution:
Restart the IIS server.
2.10 Unable to access Report page Users part of LSS-PT report may not be able to access Report Page post migration to
R140.1 from any previous release. To fix the issue, add all the users to LSS-PT Report
Users group.
2.11 Unable to view report packages on L3.5/L4 Trace Server post R121 to R140.1 migration
Post migration from R121 to R140.1, report packages may not be available on L3.5/L4
Trace Server. To fix this issue, check whether all the Trace services are running. If the
issue persists, contact the Honeywell Support Help Desk.
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 14
3 System Validation and Data Collection
This chapter describes system validation and data collection related errors and fixes.
3.1 Basic checks This section describes different types of basic checks.
3.1.1 IAA Report
Prerequisite:
SaRepository service should be up and running in Trace Server
SaWindows service should be up and running in Remote node
IAA data collection logs will be available in - C:\ProgramData\Honeywell\LSS-
PT\Logs\
IAA report generation logs will be available in - C:\ProgramData\Honeywell\SA
Scheduling a snapshot is mandatory to generate System performance report on an
Experion system. The snapshot must be scheduled 28 hours in advance. This is the time
required for System performance audit to be completed on the Flex node. This is done
so that when the scheduled snapshot time occurs, the System performance file is ready
to be picked by the Data Collection process of Honeywell Trace to generate the System
performance report.
To check if the IAA (System Performance) is running in the background, a text file should
be available in flex machine in the path C:\ProgramData\Honeywell\LSS-PT\IAA.
To check if the IAA files are available in Trace Server to generate IAA report, go to path:
C:\ProgramData\Honeywell\LSS-PT\AppData\IAA.
3.1.2 Basic checks for TPS data collection from Trace
1. Ensure that the remote node is configured with LVRLOG. GUS Display Runtime
license is required to install LVRLOG in EST station.
2. Ensure that file transfer is configured in remote node and it is working.
3. Ensure that the user that is given for data collection is part of engineers group.
4. Ensure that Data Server status is OK.
5. Ensure that no UCN nodes are in failed condition, if there are failed nodes then
LVRLOG will be in incomplete state.
6. Ensure that latest checkpoints for all the data owners are present in HM.
7. If remote node is GUS then before data collection the login user should be same as
the data collection user.
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 15
3.1.3 Basic check for Experion
1. All services of Experion should be running.
2. Quick builder should be closed else Data collection fails with following error
message: “Instance(s) of Quick Builder Project is opened. If data from QB Project is
required, please close all instance(s) before starting Data Collection.”
3. For Network view, make sure all Computers and Devices are added in Network
(CANE) of configuration studio.
4. Check point file to be created in CPBASE folder on \\EXP-SRVB.
3.1.4 Basic check for Triconex
1. Tristation should be closed in client machine.
2. Project should be built with zero errors and warnings.
ATTENTION
Refer to Prerequisites Guide for more information on prerequisites for data
collection.
3.2 Agent didn't send any response for its activation. No heartbeat file created This error appears after performing system validation.
Cause:
Username and password entered in Data collection system setting do not match the
data collection username and password specified during Remote Node installation.
The Trace Server cannot see the Remote Node in the network.
Firewall between L2 and L3.
\\<Trace Server IP>\Data shared folder is not accessible by the Remote Node.
No permission for http://schemas.microsoft.com/powershell/UniformaceTrace
HTTPS - TCP port 5986 is not open
Self-Signed Certificate is not valid or is not trusted. Refer to article REQ – 0005295.
Solution:
Open Trace application and navigate to data collection menu. Select the affected
system and open system setting. Ensure that the Data collection user name and
password is the same used during Remote Node installation and is part of the Local
Product Administrator Group (Or Domain DCS Administrators Group)
System Setting:
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 16
Remote Node Data Collection:
Ping both Trace sever and Remote Node with machine name. Machines should be
part of the Domain DNS or the Host files in case of Workgroup.
If there is Firewall between L2 and L3, the following ports must to be opened (TCP:
139, 445 and UDP: 137, 138)
Map the data folder from the Remote Node using “ptagentuser” user:
Select Map Network Drive
o In Folder field, enter \\<Trace Server IP>\Data
o Select “Connect using different credentials” checkbox
o Enter the following username: <Trace Server name>\ptagentuser and the
password
o This should connect to Data folder of Trace Server
Add Data Collection User permissions to
http://schemas.microsoft.com/powershell/UniformaceTrace
o In the Remote Node run PowerShell as administrator
o Execute the following command (Key sensitive):
Set-PSSessionConfiguration -Name UniformanceTrace –
showSecurityDescriptorUI
o Check if Read and Execute permissions are given to Data Collection user.
Check and Enable HTTPS Port 5986:
o In the Remote Node run PowerShell as administrator
o Execute the following command (Key sensitive):
winrm e winrm/config/listener
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 17
o You should see output with 2 entries (HTTP and HTTPS)
o If you do not see the HTTP listener, the node is a Public Network – Refer to
section Data Collection user permission window does not pop up during
Remote Node installation.
o If you do not see the HTTPS listener, perform the following steps.
o Execute the following command in PowerShell in order to get the
Thumbprint (Key sensitive):
ls cert:LocalMachine\m
o Copy thumbprint value and paste it in notepad
o Run Command Prompt (CMD.exe) as administrator
o Execute the following command. Yellow field must be replaced with the
actual values:
winrm create winrm/config/listener?Address=*+Transport=HTTPS
@{Hostname="FQDN";CertificateThumbprint="THUMBPRINT";port="5986"
}
o Run PowerShell as administrator
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 18
o Re-execute the following command (Key sensitive) and ensure HTTPS
listener is listed:
winrm e winrm/config/listener
Send the logs to Support Team:
Activity tool logs will be available in - C:\ProgramData\Honeywell\LSS-PT\Logs\
3.3 Unable to connect to Remote Node This error appears after performing system validation.
Cause:
IP address and Data Collection user credential.
Solution:
On Trace Server:
1. Verify IP address, Data Collection User & Password entered in Data Collection page
is correct.
2. Are you able to ping the IP address (of Trace Remote Node) from Trace Server?
On Trace Remote Node:
1. Is Data Collection user part of 'Log On As Batch'.?
Navigate to Security Policy(secpol.msc)-->Local Policies-->User Rights
Assignment-->Log On As Batch
2. The Network should be in Domain or Private but not on Public.
3. Check if registry key value in Experion Flex for
"HKEY_CLASSES_ROOT\CLSID\{B54F3741-5B07-11cf-A4B0-
00AA004A55E8}\InprocServer" is C:\Windows\System32\vbscript.dll
If this registry key value is not "C:\Windows\System32\vbscript.dll", this is due to a bug
in McAfee. When some components of McAfee are uninstalled/upgraded the Windows
VBScript registry is not reverted back.
For recovery steps, perform the following instructions:
1. Go to the McAfee Knowledge Bank to resolve registry issue.
2. Uninstall existing Trace Remote Node.
3. Run Clean Up Utility.
4. Reinstall Trace Remote Node.
Send the logs to Support Team:
Activity tool logs will be available in - C:\ProgramData\Honeywell\LSS-PT\Logs\
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 19
3.4 Failed to read switch configuration This error appears after performing snapshot data collection: Failed to read switch
configuration of <Switch IP>. Check switch configuration / Check RW Community String
provided in Global Settings is empty/incorrect.
Cause:
Switch is not added to CANE in configuration studio and loaded
RO community string and/or RW community is incorrect or not configured
SNMP not configured
Spanning Tree not configured.
Solution:
Ensure Switch is added under the CANE in the configuration studio and it is loaded
Ensure Read -Only community string in CANE settings is matching switch configuration
RW community string in global settings should be configured in the Switch
SNMP must be configured in Experion server and updated in the switch configuration
Top level Yellow and green switch spanning must be configured (For yellow it is 4096
for green 8192).
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 20
3.5 Add Trace URL to Local intranet zone Ensure that you a part of one of the following user groups to open the Trace application:
LSS-PT Engineers
LSS-PT Managers
LSS-PT Product admin
LSS-PT Report Users
However, you may still need to enter your username and password and add the Trace
application URL to Local intranet zone to access the application. Perform the following
steps to add URL to Local intranet:
1. Open Internet Explorer, and click .
2. Select Internet options, select the Security tab, select the Local intranet zone and
then click the Sites button.
3. Click Advanced.
SYSTEM VALIDATION AND DATA COLLECTION
HTDOC-X574-en-140.1A 21
4. In the Add this website to the zone field, enter the website and click Add.
5. Click Close.
6. Click OK.
7. Click OK.
Once you have added successfully, restart Internet Explorer.
L3/L4 SYNCHRONIZATION
HTDOC-X574-en-140.1A 22
4 L3/L4 Synchronization
This chapter describes L3/L4 Synchronization related errors and fixes.
4.1 Check if connection between L3 and L4 Trace Servers is established Perform the following steps to check if the connection is established between L3 and L4
Trace Servers:
Enable Telnet in Trace L3 serer through server manager -> Add roles and features-> In Features -> enable Telnet client.
After enabling Telnet client. Run “telnet Trace--L3-5-b3.lssptl4dc.local<FQDN of L3.5> 443” in Command prompt. Yellow field must be replaced with L3.5 Fully Qualified Domain Name
Once the connection is successful, the following window appears:
L3/L4 SYNCHRONIZATION
HTDOC-X574-en-140.1A 23
4.2 NextNine Relay Server Open the Relay Server IP/Proxy to confirm whether Proxy is running, otherwise contact
TAC.
After configuration of Proxy, open the L4 URL from L3 node:
L3/L4 SYNCHRONIZATION
HTDOC-X574-en-140.1A 24
4.3 Time zone and time format Time zone and time format is same for both L3 and L3.5 /L4 nodes. If time zone is
different for L3 and L3.5/L4 then time should be in Sync as shown below:
4.4 Verify correct certificates are imported from L3 and L3.5/L4 Swap the certificates as mentioned in the installation guide.
Verify the correct certificates are imported from MMC (L3 node) as shown below:
L3/L4 SYNCHRONIZATION
HTDOC-X574-en-140.1A 25
Verify the correct certificates are imported from MMC (L3.5/L4 node) as shown below:
4.5 Verify the hosts file Verify the hosts file is updated with L3.5/L4 node information correctly with FQDN name,
otherwise manually update it.
L3/L4 SYNCHRONIZATION
HTDOC-X574-en-140.1A 26
4.6 Verify that L3.5/L4 web URLs are accessible from L3 Verify if the following L3.5/L4 web URLs are accessible from L3:
https:// <<L3.5MachineName>> /EnterpriseDBSync/SqlWebSyncService.svc
https://<<L3.5MachineName>>/EnterpriseDataTransfer/DataTransfer.svc
After performing the above steps (4.1 to 4.7) if Sync does not work, please send the
following details/logs to Support team:
Sync failure details:
If synchronization using the Admin Console fails (indicated by a ‘Sync failed’ message
shown in red color on the Honeywell Trace Admin Console’s Database Operations tab), e-
mail the following details to Honeywell GTAC (Global Technical Assistance Center). This
helps Honeywell troubleshoot the issue and resolve it at the earliest.
1. On the L3 Computer, collect the following details and e-mail them:
a. The Honeywell.LSSPT.AdminConsole.exe.config file available at the location:
C:\Program Files\Honeywell\LSS-PT\AdminTool.
b. The Honeywell.LSSPT.DBSyncService.exe.config file available at the location:
C:\Program Files\Honeywell\LSS-PT\Bin.
c. Launch the Microsoft Management Console (MMC). Send a screenshot
displaying contents of the Certificates folder under the Trusted People folder.
d. Launch MMC. Send a screenshot displaying contents of the Certificates folder
under the Personal folder.
e. Open the Honeywell.LSSPT.AdminConsole.exe.config file available at
C:\Program Files\Honeywell\LSS-PT\AdminTool.
Copy the L3.5 URL (which will be in the format:
https://<<L3.5MachineName>>/EnterpriseDataTransfer/DataTransfer.svc) and
launch it using a web browser. Send a screenshot of the page that is displayed.
L3/L4 SYNCHRONIZATION
HTDOC-X574-en-140.1A 27
f. Open the Honeywell.LSSPT.DBSyncService.exe.config file available at
C:\Program Files\Honeywell\LSS-PT\Bin.
Copy the L3.5 URL (which will be in the format: https:// <<L3.5MachineName>>
/EnterpriseDBSync/SqlWebSyncService.svc) and launch it using a web browser.
Send a screenshot of the page that is displayed.
2. On the L3.5 Computer, collect the following details and e-mail them:
a. The Web.config file available at the location: C:\Program Files\Honeywell\LSS-
PT\Services\EnterpriseDataTransfer
b. The Web.config file available at the location: C:\Program Files\Honeywell\LSS-
PT\Services\EnterpriseDBSync
c. The Honeywell.LSSPT.AdminConsole.exe configuration file available at the
location: C:\Program Files\Honeywell\LSS-PT\AdminTool
d. Launch MMC. Send a screenshot displaying contents of the Certificates folder
under the Trusted People folder.
e. Launch MMC. Send a screenshot displaying contents of the Certificates folder
under the Personal folder.
3. On the L3 Computer, open the Control Panel, click System and security > Clock,
Language, and Region > Date and Time. Take a screenshot of the Date and Time
dialog box and e-mail it.
4. On the L3.5 Computer, open the Control Panel, click System and security > Clock,
Language, and Region > Date and Time. Take a screenshot of the Date and Time
dialog box and e-mail it.
5. Log files on the L3 computer available at: C:\ProgramData\Honeywell\Lss-
PT\Logs.
Log files on the L3.5 Computer available at: C:\ProgramData\Honeywell\Lss-PT\Logs
LICENSING
HTDOC-X574-en-140.1A 28
5 Licensing
For licensing related issues, raise a CLL ticket. There are 3 ways you can submit a CLL ticket:
1. Call “IT Service Desk” for Critical and High priority incidents. You can find IT Service desk
contact information by clicking on “Contact IT” in IT Direct Portal.
2. Send email to “[email protected]”
3. If you have service now access then you can log in to https://honeywell.service-
now.com/itdirect?id=hn_home and click on “Fix Something” for Incidents; “Order Something” for
service requests / enhancements. (Recommended)
Send the logs to Support Team:
Activity tool logs will be available in - C:\ProgramData\Honeywell\CommonLicense\Logs.
REPORTING
HTDOC-X574-en-140.1A 29
6 Reporting
Problem:
Trace UI shows error message ‘Unable to save Report package' during report creation.
Cause:
Report service is not in a Running state
DataSource creation process fails at the time of installation.
Solution:
Start the SQL server Reporting Services from services.msc
Perform the following steps:
o Copy the files DataSourceCreation.exe and DataSourceCreation.exe.config from C:\Program
Files\Honeywell\LSS-PT\AdminTool and place it in desktop
o Change the [COMPUTERFQDN] to the Trace Server fully qualified name and DomainAppUser to
LssPTWebPool username in DataSourceCreation.exe.config
o Open Command prompt as Administrator and follow as shown in the following screenshot:
Reporting logs will be available in:
C:\ProgramData\Honeywell\LSS-PT\Logs
C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\LogFiles
SQL server Reporting Services should be at Running state.
You can go to Report Manager to check whether the installation is fine:
https://[ComputerFQDN]:3000\Reports (Open IE as Administrator)
REPORTING
HTDOC-X574-en-140.1A 30
ADMIN CONSOLE
HTDOC-X574-en-140.1A 31
7 Admin Console
Prerequisite:
Admin Console should always be opened by the user who is part of Administrators group.
Admin Console logs will be available in - C:\ProgramData\Honeywell\LSS-PT\Logs\ LSS-
PT_Admin_Console.txt
Problem 1:
Admin Console fails while moving workgroup to domain.
Cause:
Admin Console logged in user not able to read the domain user details.
Solution:
Open Admin Console as domain user who is part of Local Administrator group while changing work group
to domain.
Problem 2:
Admin Console fails while moving domain to another domain.
Cause:
Admin Console logged in user not able to read the old domain user details as it would be the SID in user
management as the old domain has been changed.
Solution:
Delete the old user SID from Local Data Collection group and Local License group manually.
SQL TEMP DB CLEANUP OPERATION
HTDOC-X574-en-140.1A 32
8 SQL Temp DB Cleanup Operation
This chapter describes how to clean up SQL temporary database. If SQL TempDB size
has grown bigger (more than 1GB for each file) you can do cleanup to enhance
application performance.
8.1 Version R130 and above To check the TempDB file size, go to:
PC > OSDisk (C:) > Program Files > Microsoft SQL Server > MSQL14.MSSQLSERVER >
MSSQL >DATA.
8.2 Below version R130 To check the TempDB file size, go to:
PC > Local Disk (C:) > Program Files > Microsoft SQL Server > MSQL12.MSSQLSERVER
> MSSQL >DATA.
SQL TEMP DB CLEANUP OPERATION
HTDOC-X574-en-140.1A 33
8.3 Cleanup TempDB This task reduces the SQL temp DB size to free disk space and also it also clears the SQL
query plan cache. To clean up the temporary database, go to:
Honeywell Trace > Admin Console > Database Operations > Click “Temp DB Cleanup”.
SQL TEMP DB CLEANUP OPERATION
HTDOC-X574-en-140.1A 34
NOTICES
HTDOC-X574-en-140.1A 35
9 Notices
Trademarks
Experion®, PlantScape®, SafeBrowse®, TotalPlant®, and TDC 3000® are registered
trademarks of Honeywell International, Inc.
ControlEdge™ is a trademark of Honeywell International, Inc.
OneWireless™ is a trademark of Honeywell International, Inc.
Matrikon® and MatrikonOPC™ are trademarks of Matrikon® International. Matrikon®
International is a business unit of Honeywell International, Inc.
Movilizer® is a registered trademark of Movilizer GmbH. Movilizer GmbH is a business unit
of Honeywell International, Inc.
Trademarks
Experion®, PlantScape®, and SafeBrowse® are registered trademarks of Honeywell
International, Inc.
Trademarks
Experion® and SafeBrowse® are registered trademarks of Honeywell International, Inc.
PlantCruise™ is a trademark of Honeywell International, Inc.
Trademarks
Experion® is a registered trademark of Honeywell International, Inc.
ControlEdge™ is a trademark of Honeywell International, Inc
OneWireless™ is a trademark of Honeywell International, Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark
owner, with no intention of trademark infringement.
Third-party licenses
This product may contain or be derived from materials, including software, of third parties.
The third party materials may be subject to licenses, notices, restrictions and obligations
imposed by the licensor.
NOTICES
HTDOC-X574-en-140.1A 36
The licenses, notices, restrictions and obligations, if any, may be found in the materials
accompanying the product, in the documents or files accompanying such third party
materials, in a file named third_party_ licenses on the media containing the product, or at
http://www.honeywell.com/ps/thirdpartylicenses.
Documentation feedback
You can find the most up-to-date documents on the Honeywell Process Solutions support
website at:
http://www.honeywellprocess.com/support
If you have comments about Honeywell Process Solutions documentation, send your
feedback to:
Use this email address to provide feedback, or to report errors and omissions in the
documentation. For immediate help with a technical problem, contact your local
Honeywell Process Solutions Customer Contact Center (CCC) or Honeywell Technical
Assistance Center (TAC).
How to report a security vulnerability
For the purpose of submission, a security vulnerability is defined as a software defect or
weakness that can be exploited to reduce the operational or security capabilities of the
software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell products
and services.
To report a potential security vulnerability against any Honeywell product, please follow the
instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Support
For support, contact your local Honeywell Process Solutions Customer Contact Center
(CCC). To find your local CCC visit the website, https://www.honeywellprocess.com/en-
US/contact-us/customer-support-contacts/Pages/default.aspx
Training classes
Honeywell holds technical training classes that are taught by process control systems
experts. For more information about these classes, contact your Honeywell representative,
or see http://www.automationcollege.com.
HTDOC-X574-en-140.1A July 2020 © 2020 Honeywell International Sàrl
Honeywell Process Solutions
2101 CityWest Blvd.
Houston, TX 77042
Honeywell House, Skimped Hill Lane
Bracknell, Berkshire, RG12 1EB Building #1, 555 Huanke Road, Zhangjiang
Hi-Tech Park,
Pudong New Area, Shanghai, China 201203
www.honeywellprocess.com