Vitech Corporation CORE Enterprise 4.0 Server Service Pack 2 Released 15 March 2002 1. ABOUT THIS SERVICE PACK 2. SERVICE PACK SERVER COMPATIBILITY 3. SERVICE PACK CLIENT COMPATIBILITY 4. OBTAINING THE SERVICE PACK 5. INSTALLING THE SERVICE PACK 6. UNINSTALLING THE SERVICE PACK 7. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK 8. VITECH CORPORATION SUPPLEMENTAL END USER LICENSE AGREEMENT ______________________________________________________________________ 1. ABOUT THIS SERVICE PACK This service pack (SP2) is an update to CORE Enterprise 4.0 server. SP2 contains a series of changes for the CORE Enterprise server. Please see section 7, "DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK", for more information. There are separate versions of the service pack corresponding to CORE Workstation, CORE Enterprise client, and CORE Enterprise server. Please obtain the appropriate Service Pack (CORE Enterprise 4.0 Server Service Pack 2) from our website. See section 4, "OBTAINING THE SERVICE PACK", for further instructions. Service Pack 2 includes all changes from Service Pack 1 and can be installed either by itself or after Service Pack 1. The Service Pack contains the following files: File Target Directory ---- ---------------- SP4002n.sll \COREServer\HTTP\bin httpvtca.bnd \COREServer\HTTP\bin httpvtcc.bnd \COREServer\HTTP\bin SP4002.bat \COREServer\scripts SP4002.tpz \COREServer\scripts SP2Readme.txt \COREServer\scripts enterprise40.pdf \COREServer\doc SP2Readme.txt \COREServer\doc coreua.dll \COREServer\ualib ______________________________________________________________________ 2. SERVICE PACK SERVER COMPATIBILITY CORE Enterprise 4.0 Server Service Pack 2 is intended to be applied to a standard CORE Enterprise server installation. If CORE Enterprise 4.0 Server Service Pack 2 is installed after other server service packs, you may have to reinstall the other service packs unless their documentation explicity says it is safe to install CORE Enterprise 4.0 Server Service Pack 2 after them. Applying CORE Enterprise 4.0 Server Service Pack 2 multiple times on the same server will have no effects, either good or bad. Service Pack 2 includes all changes from Service Pack 1 and can be installed either by itself or after Service Pack 1. IF YOU REPLACE THE EXTENT WITH A CLEAN EXTENT, FOR EXAMPLE, WHEN RESTORING FROM A HOT BACKUP, YOU WILL HAVE TO REAPPLY THE SERVICE PACK TO THE NEW EXTENT. To determine what service packs are currently installed on a server, perform the following steps ON THE SERVER: 1. Open Windows Explorer via the Start >> Programs menu. 2. In Windows Explorer, locate and select the script subdirectory of the CORE Enterprise server installation (C:\COREServer\scripts by default) containing the two files SPReport.bat and SPReport.tpz. 3. Double-click on file SPReport.bat to run it. 4. The results of the operation are logged to SPReport.Out in the COREServer\logs directory. View this file by finding and selecting in Windows Explorer the logs subdirectory of the CORE Enterprise server installation (C:\COREServer\logs by default). 5. Double-click on file SPReport.Out to open it. 6. If prompted for an application in which to view the file, choose Notepad. ______________________________________________________________________ 3. SERVICE PACK CLIENT COMPATIBILITY CORE Enterprise 4.0 Server Service Pack 2 has a corresponding client- side service pack. Clients that do not have the client-side Service Pack 2 installed will not be able to use the server after this server- side Service Pack 2 is installed. Neither can clients to which Service Pack 2 has been applied use a server to which Service Pack 2 has not been applied. ______________________________________________________________________ 4. OBTAINING THE SERVICE PACK You can download the service pack from the support and product update section of the Vitech web site at: http://www.vtcorp.com/updates.html If you are having difficulty downloading a service pack, call us at: (703) 883-2270 Or email us at: support@vtcorp.com ______________________________________________________________________ 5. INSTALLING THE SERVICE PACK **************************************************************************** * WARNING: CORE2NET MUST BE SHUT DOWN AND ALL CORE ENTERPRISE USERS LOGGED * * OUT BEFORE APPLYING THIS SERVICE PACK TO THE SERVER. * **************************************************************************** NOTE: The COREStone and NetLDI51 services must be running for the service pack to be successfully applied. The installer will start them if they are not already running. To install CORE Enterprise 4.0 Server Service Pack 2, follow these steps: 1. Download the entserver40SP2.exe file and double-click on it to start the setup utility. 2. Select the "Next" button at the Welcome Dialog. 3. The next dialog will ask you to specify the directory where the service pack files should be unpacked. The main CORE Enterprise 4.0 Server directory must be specified to ensure the service pack is installed correctly. By default, this directory is "C:\COREServer". If a different directory was specified during the CORE Enterprise 4.0 Server installation, you will need to specify that directory here also. 4. The setup utility will then begin unpacking the files. If you are asked whether or not to overwrite any files during this process, please select the "Yes to All" button. 5. When the installer is finished extracting the service pack files, it will launch a batch program that executes a script on the server. The script loads changes into your CORE Enterprise repository and may take several minutes to finish. 6. The installation of the CORE Enterprise 4.0 Server Service Pack 2 is complete. Please click "OK" to finish the setup. 7. Use Windows Notepad to view the file \COREServer\logs\SP4002.Out. Peruse the file for errors and make sure the end contains the text: "CORE Enterprise 4.0 Server Service Pack 2 was successfully installed." NOTE: If you restore an archived or backup repository (extent0.dbf file) that was last used before the service pack was installed, you may have to reapply the service pack when the server is running with the restored extent. Do this by double-clicking on \COREServer\scripts\SP4002.bat. ______________________________________________________________________ 6. UNINSTALLING THE SERVICE PACK The following files should be removed: File Default Location ---- ---------------- SP4002n.sll \COREServer\HTTP\bin httpvtca.bnd \COREServer\HTTP\bin httpvtcc.bnd \COREServer\HTTP\bin SP4002.bat \COREServer\scripts SP4002.tpz \COREServer\scripts SP2Readme.txt \COREServer\scripts ______________________________________________________________________ 7. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK Restore Defaults button does not reset Maximum Sessions in CORE2net Monitor AR Number: CN.6 Description: In the CORE2net Monitor, the Restore Defaults button on the Settings tab does not reset the Maximum Sessions. Resolution: Apply CORE Enterprise 4.0 Service Pack 2. Error clearing HTTP Server field in CORE2net Monitor AR Number: CN.7 Description: In the CORE2net Monitor, an error--"'endsWith:' not understood"--occurs attempting to clear the HTTP Server field on the Settings tab after first saving a non-empty value there. Resolution: Apply CORE Enterprise 4.0 Service Pack 2. Cannot save settings twice in CORE2net Monitor AR Number: CN.8 Description: After saving changes in the Settings tab of the CORE2net Monitor, subsequent changes made in the same CORE2net Monitor may get lost, though they appear correct until a new CORE2net Monitor is opened. Or subsequent changes may appear to get lost, though they are actually saved. Resolution: Apply CORE Enterprise 4.0 Service Pack 2. No way to bind CORE2net to specific NIC AR Number: CN.9 Description: If a CORE2net server has multiple network interface cards, there is no way to bind CORE2net to only one of them. Rather, it always uses all of them, which can cause a problem if you want to run another web server on the same port on one of the adapters. Resolution: Apply CORE Enterprise 4.0 Service Pack 2. Now the HTTP Server field on the Settings tab of the CORE2net Monitor is a combo box. From the drop-down list, the user can select any dotted decimal IP address available on the CORE Enterprise server. The user can also manually enter either a dotted decimal IP address or a symbolic name. If the field is left blank, or if its value is '127.0.0.1' or 'localhost' (case-insensitive), then CORE2net binds to all IP addresses on the CORE Enterprise server. If a value from the drop-down list (or a symbolic name that resolves to one of them) is selected or entered, CORE2net binds only to the selected interface, and other services can bind to the same port number on other available interfaces. If a dotted decimal address or symbolic name of a host other than the CORE Enteprise server is entered, the CORE Enterprise server attempts to start CORE2net on the remote host. In that case, even if the remote CORE2net server has multiple network adapters, CORE2net will only use the specified one. Note that Micrsoft Internet Information Server conflicts with CORE2net if they are assigned to the same port, because IIS always uses all available IP addresses even if its web sites are assigned to specific addresses. CORE2net scripts cannot specify expiration time for their output AR Number: CN.10 Description: There is no way for a CORE2net script to specify the expiration time for its output. The expiration time is included in the header of the HTTP response rather than in the body. After the expiration time, a client browser should not refresh the item from its cache, but should request an updated version using the same URI with which it was originally obtained. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 2. An Expire Output script construct has been added. It accepts as a parameter or argument a String containing an HTTP-date (e.g. Thu, 01 Dec 1994 16:00:00 GMT). During execution, the construct will attempt to convert the contents of the input String to HTTP-date format if no valid HTTP-date is found within the String. An error will be generated if it is unable to do so. This time stamp will be used to expire the script output from CORE2net. The construct will do nothing when executed outside the CORE2net environment. Errors occur after closing inspector window with no element selected AR Number: CR.1207 Description: An element inspector window tracks the element selection of its parent window. If no element representation is selected in its parent, then the inspector is blank. When an inspector is closed while in this state, it is not unregistered, resulting in errors when the project is closed, when the user logs out, or when the saved image is restored. Resolution: Apply CORE 4.0 Service Pack 2. Cannot shift to database mode after renaming attribute in abstract class AR Number: CR.1209 Description: If an attribute definition is renamed in an element definition that has subclasses, then it is impossible to shift the project back to database mode. Resolution: Apply CORE 4.0 Service Pack 2. Problems using system font selected in User Preferences dialog AR Number: CR.1210 Description: When you set the CORE system font in your user preferences, not all database, schema, and user/group information appears in the new font. The item height in relation list panes is unaffected, and items begin to overlap at face sizes greater than or equal to 14 points. Resolution: Apply CORE 4.0 Service Pack 2. Duplicate element not added to same folders as original AR Number: CR.1211 Description: When duplicating an element, if the Duplicate Element command is selected from a menu bar, the duplicate is placed in the same folder as the original. However, if the command is selected from a popup menu, the duplicate is placed in the root folder associated with its class. When an element is duplicated, the duplicate should be added to all folders (and only those folders) in which the original is a member. Resolution: Apply CORE 4.0 Service Pack 2. Change to collection attribute in duplicated element affects original AR Number: CR.1213 Description: After duplicating an element with a collection attribute (such as the Fields attribute of an Item element), any changes made to the duplicate attribute also affect the corresponding attribute of the original element. Resolution: Apply CORE 4.0 Service Pack 2. Activating Project Editor changes project status AR Number: CR.1214 Description: After opening or closing a project using the Status radio buttons in the Project Editor and then reversing the status in the CORE Control Panel, returning to the Project Editor (without manipulating any controls there) will switch the state of the project again. A closed project will be opened and an open project will be closed. Resolution: Apply CORE 4.0 Service Pack 2. Exit CORE command cannot be added to toolbar AR Number: CR.1215 Description: The Exit CORE command is not available for adding to the Control Panel or to a toolbar. Resolution: Apply CORE 4.0 Service Pack 2. Cutting branch from FFBD construct doesn't break 'decomposed by' relationships AR Number: CR.1216 Description: Cutting a branch of a parallel or other FFBD construct does not properly break the 'decomposed by' relationships between the parent Function and any nodes on the removed branch. Resolution: Apply CORE 4.0 Service Pack 2. Cutting construct from FFBD doesn't break 'related to' relationships AR Number: CR.1217 Description: Cutting an iterate or replicate construct from an FFBD does not properly break the 'related to' relationship between the parent Function and the construct's DomainSet. Resolution: Apply CORE 4.0 Service Pack 2. Error creating and deleting target of new relation in ER diagram AR Number: CR.1218 Description: An error is produced by the following sequence: 1) Open an ER diagram. 2) Enable the Show All Relations toggle. 3) For a relation with no targets, select the dummy target. 4) Right-click and select Edit Targets. 5) Create a new target and click Ok. 6) Select the new node, right-click, and select Remove Target. Resolution: Apply CORE 4.0 Service Pack 2. Error saving Quick Filter that uses Number AR Number: CR.1219 Description: A walkback error, "A [Wild]HierarchicalNumber cannot be compared to a String," occurs when attempting to save a QuickFilterDefinition that uses the #number attribute. Resolution: Apply CORE 4.0 Service Pack 2. Create Relation toolbar button causes error AR Number: CR.1222 Description: Issuing a Create Relation command from a toolbar results in an error. Resolution: Apply CORE 4.0 Service Pack 2. Spurious errors due to invalid window handles AR Number: CR.1224 Description: A variety of errors occasionally crop up due to operations on invalid window handles. Resolution: Apply CORE 4.0 Service Pack 2. Steps have been taken to mitigate the effects of this problem, but their source remains unclear. Typo in Tip of the Day AR Number: CR.1225 Description: A Tip of the Day refers to Functions represented in a Physical Block Diagram, which represents only ImplementationUnits. Resolution: Apply CORE 4.0 Service Pack 2. Check Spelling command does not work on diagrams AR Number: CR.1226 Description: Adding the Check Spelling command to a diagram view toolbar causes an error. Resolution: Apply CORE 4.0 Service Pack 2. Note that the error has been eliminated only. It is not possible to check spelling in diagrams except for the attributes portion of the ERA view. Enterprise cannot import 2.0 RDT files AR Number: GS.144 Description: CORE Enterprise 4.0 cannot import .RDT files in 2.0 format (e.g., those generated by the Advanced CSV Parser script). Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. Can modify element locked by another Enterprise session AR Number: GS.145 Description: It is possible to renumber an element that is locked by another session (if that session is logged in to the same user account). It is similarly possible to rename an element and delete pieces of an FFBD structure. Resolution: Apply CORE Enterprise 4.0 Service Pack 2. Transform Element Class command fails in Enterprise AR Number: GS.146 Description: Using the Transform Element Class command in CORE Enteprise produces an error message "'accessControlList' not understood", and the element class is not transformed. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 2. Enterprise loses imported sort block definitions AR Number: GS.147 Description: Sort block definitions imported via the Import Settings command are lost on logout from CORE Enterprise. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 2. One broadcast update received by each client NIC AR Number: GS.148 Description: When a client uses the broadcast update mechanism (or when autodetection of the optimal update mechanism selects the broadcast update mechanism), the client receives and processes one copy of each update for each of its network interface cards. If the client has two network adapters, for example, an element creation will result in the element being listed twice. Resolution: Apply CORE Enterprise 4.0 Service Pack 2. Can modify collection attribute values of unlocked element AR Number: GS.149 Description: Items in a collection attribute list can be selected and removed from the list even if the element is not locked by the current user. Resolution: Apply CORE Enterprise 4.0 Client Service Pack 2. Inaccuracies in CORE Enterprise User Reference Guide AR Number: N/A Description: The CORE Enterprise User Reference Guide is out of date, lacking descriptions of new features, containing incorrect GUI images, etc. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. ______________________________________________________________________ Service Pack 2 includes the following changes from Service Pack 1. Project permission level not enforced on import of RDT files from old versions AR Number: CR.1174 Description: When importing an .RDT file from CORE 3.1 or an older version into a CORE 4.0 project, the permission level of the project may not be honored. That is, attribute access control lists in the .RDT file may be added to projects created with normal (element-level) and coarse (project-level-only) permissions, and element ACLs in the .RDT file may be applied in projects created with only project-level permissions. These ACLs cannot be viewed, modified, or deleted, but their presence can cause some errors (e.g., when attempting to duplicate an element with an attribute ACL in a normal or coarse project). Resolution: Apply CORE 4.0 Service Pack 1 or later. Attribute enhancement type property value always exported as string AR Number: CR.1178 Description: During a schema export, an attribute enhancement's type property value will always be exported as string even if the attribute's type is not string. Resolution: Apply CORE 4.0 Service Pack 1 or later. Cannot delete elements from projects with coarse access control AR Number: CR.1179 Description: An error is encountered deleting elements from projects created with coarse (project-level-only) access control. Resolution: Apply CORE 4.0 Service Pack 1 or later. Obtaining subfolders in COREscript yields bag AR Number: CR.1180 Description: The COREscript documentation states that the subfolders operator returns a set of folders, when, in fact, it returns a bag. Resolution: Apply CORE 4.0 Service Pack 1 or later. ReferenceSpec not output as link in RTF AR Number: CR.1181 Description: When COREsript outputs a ReferenceSpec to HTML, it generates a live anchor (hyperlink), but the same is not true when outputting in RTF format. Resolution: Apply CORE 4.0 Service Pack 1 or later. Deleted users and groups appear in ACLs AR Number: CR.1183 Description: If a user or group is granted permissions to an object (element, attribute, or project) and is subsequently deleted, it still appears in the object access control list. Resolution: Apply CORE 4.0 Service Pack 1 or later. Importing 4.0 RDT file in "full" format modifies ACL of target project AR Number: CR.1185 Description: This is by design. A full database export in CORE 4.0 .RDT file format now includes the access control list of the source project and applies it to the target project into which it is imported. The only problem arises when the importing user is not granted administrative permission to the project by the ACL. In that case, the importing user doesn't have permission to perform any of the commands executed by the rest of the import, resulting in a large conflict file and no data imported. Resolution: Apply CORE 4.0 Service Pack 1 or later. Now the importing user is never demoted by the import in terms of project permissions. Permissions level mismatch importing any 4.0 RDT file into coarse project AR Number: CR.1186 Description: Importing any CORE 4.0 .RDT file into any project created with coarse (project-level-only) access control generates a permissions level mismatch conflict when it gets to the project access control list in the .RDT file. Resolution: Apply CORE 4.0 Service Pack 1 or later. Users may lack permissions of groups in which they are members AR Number: CR.1187 Description: Users and groups are imported from .ACF files (automatically on launch in Workstation; explicitly through User/Group Manager in Enterprise). After import, though a group may list a user as a member, the user may not know it belongs to the group. Then the user may not obtain permission to an object that is granted to the group. This can happen when the user is imported before a new group of which the user is a member. When the user is finalized, the group ID is stripped, because it does not exist, yet. Resolution: Apply CORE 4.0 Service Pack 1 or later. Progress meter behaves strangely at end of .RDT file imports into Enterprise AR Number: GS.140 Description: At the end of .RDT file imports into CORE Enterprise 4.0, the progress meter, instead of showing completion, reverts to a semi-complete or even empty state. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. Names and comments of existing users and groups not updated on import AR Number: GS.142 Description: If two Enterprise servers have the same set of users and groups, a user or group is renamed or given a new comment in one system, and the users and groups are exported from that server and imported into the other, the changes are not reflected. Resolution: Apply CORE Enterprise 4.0 Service Pack 1 or later. Error parsing some floating-point numbers in RDT file AR Number: GS.143 Description: The algorithm used to convert a string to a floating-point number fails in CORE Enterprise 4.0 server when a string equal to '0' is parsed from an .RDT file. Resolution: Apply CORE Enterprise 4.0 Server Service Pack 1 or later. ______________________________________________________________________ 8. VITECH CORPORATION SUPPLEMENTAL END USER LICENSE AGREEMENT This service pack and the documentation updates, supplements, or replaces functionality of the CORE 4.0 software. As such, the service pack and its documentation are governed under the terms of the original license agreement. By installing this software, you acknowledge and agree to be bound by the terms of the existing license agreement. If you do not agree to the terms, promptly return the service pack and its documentation to the place you obtained them.