Vitech Corporation CORE Enterprise 4.0 Server Service Pack 1 Released 8 February 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 (SP1) is an update to CORE Enterprise 4.0 server. SP1 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 1) from our website. See section 4, "OBTAINING THE SERVICE PACK", for further instructions. The Service Pack contains the following files: File Target Directory ---- ---------------- SP4001n.sll \COREServer\HTTP\bin httpvtca.bnd \COREServer\HTTP\bin httpvtcc.bnd \COREServer\HTTP\bin SP4001.bat \COREServer\scripts SP4001.tpz \COREServer\scripts SP1Readme.txt \COREServer\scripts SP1Readme.txt \COREServer\doc ______________________________________________________________________ 2. SERVICE PACK SERVER COMPATIBILITY CORE Enterprise 4.0 Server Service Pack 1 is intended to be applied to a standard CORE Enterprise server installation. If CORE Enterprise 4.0 Server Service Pack 1 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 1 after them. Applying CORE Enterprise 4.0 Server Service Pack 1 multiple times on the same server will have no effects, either good or bad. 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 1 has a corresponding client- side service pack. Clients that do not have the client-side Service Pack 1 installed will not be able to use the server after this server- side Service Pack 1 is installed. Neither can clients to which Service Pack 1 has been applied use a server to which Service Pack 1 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: Ensure all CORE Enterprise users are 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. NOTE: If CORE2net is running when the service pack is applied, it must be restarted for the updates to become effective. The installer will attempt to do this. Therefore, when the service pack is applied, all active CORE2net sessions will be logged out. To install CORE Enterprise 4.0 Server Service Pack 1, follow these steps: 1. Download the entserver40SP1.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 takes several seconds to finish. 6. The installation of the CORE Enterprise 4.0 Server Service Pack 1 is complete. Please click "OK" to finish the setup. 7. Use Windows Notepad to view the file \COREServer\logs\SP4001.Out. Peruse the file for errors and make sure the end contains the text: "CORE Enterprise 4.0 Server Service Pack 1 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\SP4001.bat. ______________________________________________________________________ 6. UNINSTALLING THE SERVICE PACK The following files should be removed: File Default Location ---- ---------------- SP4001n.sll \COREServer\HTTP\bin httpvtca.bnd \COREServer\HTTP\bin httpvtcc.bnd \COREServer\HTTP\bin SP4001.bat \COREServer\scripts SP4001.tpz \COREServer\scripts SP1Readme.txt \COREServer\scripts ______________________________________________________________________ 7. DESCRIPTION OF CHANGES INCLUDED IN SERVICE PACK This service pack supercedes and includes all changes in SP1 and SP2. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. ______________________________________________________________________ 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.