Tech Note 612 Upgrading DLL Version Mismatches Between CBM Solution and System Platform

Transcription

1 Tech Note 612 Upgrading DLL Version Mismatches Between CBM Solution and System Platform All Tech Notes, Tech Alerts and KBCD documents and software are provided "as is" without warranty of any kind. See the Terms of Use for more information. Topic#: C reated: June 2009 Introduction When you deploy the CBM Solution, a second installer called Wonderware Components copies all of the CBM Solution DLLs to a local folder on the System Platform Node. As a part of the CBM Solution implementation you then manually import the User Control into the designated Galaxy. Sometimes, when performing a CBM Solution upgrade, the DLLs from the previous install are not properly removed and can prevent the upgraded version from functioning correctly. This Tech Note describes the process to manually diagnose, delete and re- import the required new CBM DLL files from the System Platform server node. Application Versions Tasks System Platform 3.0 and 3.1 Condition Based Monitoring Solution (CBM) 2.0 This information lists a series of tasks that diagnose and fix the problem. Check the DLL Version Against the Product Version To check for a version mis-match after the upgrade, compare the existing DLL version with the Product Version. 1. Using Windows Explorer, browse to C:\Program Files\ArchestrA\. 2. Optional Step: Locate the Mtelligence.MIS.SystemPlatform.dll in this folder and note its Assembly Version. The version number to compare is the first 3 digits of the 5-digit number group shown in Figure 1 below. 1/5

2 FIGURE 1: MTELLIGENCE.MIS.SYSTEMPLATFORM.DLL PROPERTIES 3. From the CBM Configurator main menu, click Help/About and note the Product Version (Figure 2 below). Note: Depending on your deployment topology, CBM Configurator may be installed on a different server than your System Platform node. FIGURE 2: CBM SOLUTION PRODUCT VERSION 4. Compare the 3 digit number 242 from in the first line of the About...CBM Configurator panel (Figure 2 above), to the 3 digit number in the DLL version (Figure 1 above). 5. If there is a mismatch, complete the following tasks. Remove the Work User Control Element from the SmartSymbol To manually remove the related DLLs: 2/5

3 1. Open the IDE and then open the Mtelligence Work Control SmartSymbol. 2. Delete the Work User Control Element (Figure 3 below). FIGURE 3: DELETE THE WORKUSER CONTROL ELEMENT FROM THE WORK CONTROL ARCHESTRA GRAPHIC 3. Save the changes to the SmartSymbol. 4. From the Mtelligence Graphics Toolbox, delete the Work User Control. Delete the Mtelligence* DLLs 1. From the SMC, shutdown the IPWWViewEngine and the EngineGR engines. Also shutdown the IDE if it is open. 2. Using Windows Explorer, browse to C:\Program Files\ArchestrA\Framework. 3. Delete the Mtelligence*.dll files from this folder (Figure 4 below), and all the Galaxy folders under the FileRepository folder. IMPORTANT: DO NOT DELETE the Mtelligence.SystemPlatform.Extensions.dll file. 3/5

4 FIGURE 4: DELETE MTELLIGENCE*.DLL FILES AS SHOWN ABOVE 4. In the SMC, restart the IPWWViewEngine and the EngineGR Engines. Install the CBM 2.0 Wonderware Components This task explains installing the Wonderware Components that match the installed MIS 2.0 version. Before proceeding, make sure you install CBM Solution 2.0 Components for Wonderware System Platform from the CD to the System Platform Node. 1. From the IDE, connect to the target Galaxy. 2. On the main menu click Galaxy > Import Client Control. 3. Browse to C:\Program Files\Mtelligence\MIS\2.0\Custom\Wonderware\System Platform 3.x\User Control. 4. Point to Mtelligence.Mis.SystemPlatform.dll under this sub- folder and click OK. If prompted in the IDE, click Rename existing objects in Galaxy. 5. Ensure the Work User Control appears in the Graphics Toolbox. If the WorkUserControl appears in the root of the Graphic Toolbox for the Galaxy, move it into the Mtelligence Toolbox instead. 6. Open the Work Control Smart Symbol and click Embed Symbol. 7. Add the Work User Control back into the control, then do the following: Rename the new WorkUserControl1 to WorkUserControl. You must select the WorkUserControl in the WorkControl graphic object, then select Data Binding. For property ObjTagName set the data binding value to me.tagname. 8. Save and Close. You re good to go! Note: For questions about this Tech Note, Mtelligence Technical Support. Click the following icon to view this file in.pdf format: P. Rahilly Tech Notes are published occasionally by Wonderware Technical Support. Publisher: Invensys Systems, Inc., 4/5

5 26561 Rancho Parkway South, Lake Forest, C A There is also technical information on our software products at Wonderware Technical Support. For technical support questions, send an to [email protected]. Back to top 2013 Invensys Systems, Inc. All rights reserved. No part of the material protected by this copyright may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying, recording, broadcasting, or by anyinformation storage and retrieval system, without permission in writing from Invensys Systems, Inc. Terms of Use. 5/5