Factory Software Blog l AVEVA News

Hinweis zu neuer Nummerierung von TechNotes & TechAlerts

Geschrieben von Peter ROSENBERGER | 08.08.2022 22:00:00

Migration Best Practices - Tech Notes & Alerts – SP 2020 R2 SP1

Vor kurzem hat AVEVA die Tech Notes und Alerts neu nummeriert. Zwar sind diese noch unter der alten Doc-ID erreichbar, aber die Legacy-Nummerierung ist entfernt worden. Es ist möglich nach der alten Legacy Doc-ID„TN570“ zu suchen, alternativ nach der neuen Nummer „TN000022901“ (zwingend mit 0en!). In der Auflistung finden sich beide Varianten.

Mindestens für Tech Alerts bietet es sich grundsätzlich an, diese zu abonnieren, um hier auf dem neuesten Stand zu bleiben (siehe Screenshot). Über die Kachel „Email Subscription“ lässt sich u.a. die Häufigkeit der erhaltenen Mails einstellen.

Grundsätzlich rate ich immer den Download explizit zuzulassen (unblocken) und den Install Guide und die Readme zu lesen, hier wird schon einiges geklärt.

Allgemein

Legacy Doc ID  Doc ID Content
TN10225 TN000032382 New Accounts and Security Groups in System Platform 2017 U3 and later
TN10297 TN000032436 Managing Service Accounts with Group Policy for System Platform 2017 U3 (and later)
TN10402 TN000032526 Ports required for System Platform 2017 Update 3
TN10567 TN000032662 System Platform 2020 Antivirus exclusions
  TA000032813 System Platform Issues with Microsoft Update KB5004442 – DCOM Hardening
TN10463 TN000032572 Cannot connect to the IDE because ASB Conf. Service fails to start (Port Conflict Intel Graphics)

InTouch

Legacy Doc ID  Doc ID Content
TN216 TN000022559 Rebuilding a Corrupted InTouch Managed Application (for versions 10.0 SP2 and later)
Note: Use second procedure most of the time!
FAQ2850 FAQ00008957 Error: „Invalid reference or unknown OCX method when converting application.“
TN669 TN000022986 IDEA Toolkit Application Hangs on PTAccInit() on 64-bit OS (WWHeap errors)
TN10618 TN000032702 InTouch Runtime: Popup windows are cut off on the right and botton on a migrated app
Note: Ask Tech Support for a hotfix.

Application Server

Legacy Doc ID  Doc ID Content
TN530 TN000032798 Application Server Clean-Up Guide (Galaxy Scrubber Download 2014 R2)
TN10704 TN000032767 Galaxy Migration gets stuck at 66%
TA533 TA000022338 Upgrading / migrating to SP 2020 R2 SP1 might break applications that depend on VC++ redistributable and GAC files
TN954 TN000023256 Migrating the UDAs and Field Attributes to WSP 2014 R2 (FAQ000021472)

Historian Server

Legacy Doc ID  Doc ID Content
TN10569 TN000032660 Installing MS SQL Server 2019 (Collation Type should be identical to version before)
  TN000033303 Methods to import and export a large amount of tag data in Historian via CSV (FastLoad)
TN676 TN000023002 Moving Historian Runtime Database to Another Machine
TN3066 TN000025261 Migrating Historian Runtime Database to Historian 2017
TN2863 TN000025119 Migrating InSQL 9.0 and later to Historian 2014 R2 SP1 on a new machine.
Notes: Migration from InSQL V9.0 and below requires upgrading to Historian 2012 (V10.0) first. Migration to Historian 2017 from Historian 2012 (V10.0) requires upgrading to Historian 2014 R2 SP1 first.
TN10141 TN000032314 After migrating Historian server to version 2017.x some History Blocks cannot be read.

Device Integration

Legacy Doc ID  Doc ID Content
TN10211 TN000032369 Migrating Device Integration Object-based DAServers to Operations Interation Servers
    Path to configuration files, e.g. SIDIR (C:\ProgramData\Wonderware\OI-Server\$Operations Integration Supervisory Servers$\OI.SIDIR\OI.SIDIR)