RELEASE NOTES – LABEL ARCHIVE v2.07.00
02 October
2009
Table of Contents
Third Party Components and
Files
Compatibility with Other
TEKLYNX Software
Software Protection Mode and Data Execution
Prevention
The LABEL
ARCHIVE Server software protection mode requires the following configuration
before it can be run on systems supporting Windows Data Execution Prevention
(DEP) mechanisms.
All
following executable files must be added to the DEP list of exceptions.
Configuration Details
·
In
the Start menu, right-click My Computer
and select Properties.
·
Click
the Advanced tab, or on Windows
2008, the Advanced System Settings
task.
·
In
the System Properties window, click the Settings
button in the Performance section.
·
In
the Performance Option window, click the Data Execution Prevention tab.
·
Click
Add to add the following executable
files to the list of exceptions:
·
<Program
files>\<teklynx>\Label Archive
Server\Activation.exe
· <Program files>\<teklynx>\Label Archive Server\LA2_prv_setup.exe
· <Program files>\<teklynx>\Label Archive Server\LA2_SUpgrade.exe
·
<Program
files>\<teklynx>\Label Archive
Server\TkxCnxLAS.exe
Windows XP SP3, SP2 x32/x64
Windows Server 2003
Windows Vista SP2 x32/x64
Windows Server 2008 x32/x64
Microsoft .NET Framework 2.0
Installation requires
administrator’s privileges.
2.07.00
·
LABEL
ARCHIVE 2.07 adds performance improvements in handling large volumes of data.
Windows that display lists of records now use the paging mechanism. This
applies to the following lists: check-in, check-out, history, reprint and
versions.
2.05.00
·
LABEL
ARCHIVE 2.05 is now compatible with Windows Vista Service Pack 1 and Windows XP
Service Pack 3.
·
LABEL
ARCHIVE Server can be configured to store documents and historical data in a
compressed format inside the database.
This option can be used in certain cases to increase LABEL ARCHIVE
performance, reduce network traffic, and increase the communication speed
between the LABEL ARCHIVE Server and the database system. This option also greatly reduces the amount
of storage space used within the database.
To activate data compression between LABEL ARCHIVE Server and the
database system:
1.
Stop
the LABEL ARCHIVE service.
2.
Open
the <InstallDir>\Label
Archive Server\ TkxArv.server.config file in a
text editor.
3.
Search
for the useZipCompression
attribute and set the option to True.
4.
Restart
the LABEL ARCHIVE service.
·
The
LABEL ARCHIVE Client can be configured to exchange documents and historical data
with the LABEL ARCHIVE Server in a compressed format. This option can be used in certain cases to
increase LABEL ARCHIVE performance, reduce network traffic, and increase the
communication speed between the LABEL ARCHIVE Client and the LABEL ARCHIVE Server. To activate data compression between the
LABEL ARCHIVE Client and LABEL ARCHIVE Server:
1.
Close
all applications that could be connected to the LABEL ARCHIVE Server (for
example, CODESOFT, SENTINEL, LABEL ARCHIVE MMC console).
2.
Open
the C:\Documents and Settings\All
Users\Application Data\Teklynx\Label Archive Client\
TkxArv.client.config
file in a text editor.
3.
Search
for the useZipCompression
attribute and set the option to True.
·
LABEL
ARCHIVE history records now show who approved or denied a label (#9258).
·
The
information about the quantity of printed labels is now available in the LABEL
ARCHIVE print history records (#7294).
|
Version |
Ticket ID/ Defect ID |
Description |
|
|
|
|
|
2.07.00 |
|
|
|
|
Defect 15882 |
Reprint of a very large print history causes some
performance issues. |
|
|
Defect 16093 |
MMC snap-ins do not work correctly with last service
pack of windows XP : XP SP3 |
|
2.06.00 |
|
Note: 2.06 was a customer patch. It was not published
on the market. |
|
|
Defects
15826 and 15889 |
On Oracle, LAS service does not
automatically restart after a stop/start of Oracle service. It has to be
restarted manually. |
|
2.05.00 |
|
|
|
|
20086 -
13146 |
UMSS MSGS
Administration does not show messages regarding label approval. |
|
|
23430 - 13872 20073 - 13145 |
After
installing Windows XP SP3, the Administration console for the LABEL ARCHIVE
Client and LABEL ARCHIVE Server could not be opened. |
|
|
24818 - 14208 |
It was
possible to be prompted to approve a label twice. |
|
|
7677 - 11492 |
It was
not possible to delete an approval rule, even after having removed all
documents that had been validated with it along with all references to that
rule in the categories defined in LABEL ARCHIVE. |
|
2.04.00 |
|
|
|
|
14512 - 12270 |
Comments
entered during the approval process and for the validation of a label were
not visible to other users involved in the approval loop or at the end of the
process for the designer that submitted the label. |
|
|
17743 -
12782 |
Variable
values used at print time within the label could not be seen later in the
Print History records. |
|
|
12192 -
11808 |
It was not
possible to save on the local disk the validated version of the labels stored
in the LABEL ARCHIVE database from CODESOFT.
This limitation was designed for security reasons, but could cause
issues in instances where a backup solution was required for label printing
while the database system is down. An
external tool has been created that allows you to back up the full label
archive database on the local disk.
This tool must be copied into the LABEL ARCHIVE Server installation
directory to use the feature. |
|
|
19201 -
12966 |
It was possible to type in forbidden characters for file names when
checking a label in to LABEL ARCHIVE.
Forbidden characters include / \ : * ? "
< > |. This would cause CODESOFT
to crash when opening the label from the recent file list. |
|
|
4777 -
11259 |
After an automatic reboot of the Oracle after a backup, the LABEL
ARCHIVE Server became unresponsive and required a manual restart. This problem is now fixed, but it is
important to avoid any connection with the LABEL ARCHIVE Server while the
database is shut down. Note: Typically in server environments, when maintenance operations are done
on databases, it is important that all applications and ERPs
which rely on these databases are properly stopped and then properly
restarted in accordance and in coordination with the Application
Managers. If IT is not well
coordinated with Application Managers, an incident may occur, such as a
client performing label check-in or printing when the database is stopped by
IT. This could cause data integrity
loss. In some cases, an ERP or
application may be automatically restarted by IT before the Application
Manager could check that the production data is restored and approve the
application restart, and a user on the other side of the factory resumed
working with LABEL ARCHIVE without permission from the Application
Manager. This causes integrity risks
because the application could contain invalid data. |
·
E-mail
notifications can be sent to individual users only. Group notifications are not allowed by
e-mail.
·
When
working with an SQL server database that is located on a different PC than the
LABEL ARCHIVE Server, only the SQL authentication mode can be used during
installation. If the Windows
authentication mode is chosen, the LABEL ARCHIVE Server cannot connect to the
distant database and the application installation fails.
·
When
working with the reprint feature, it is possible to observe differences between
the original printout and the reprinted copy when working with multiple labels
across that have a defined Start At Label parameter
set to greater than 1 for the printout.
·
There
is no official Oracle support for Windows Server 2008 systems. Applications could be unstable on this
configuration.
The installation of LABEL ARCHIVE
Server and Client might update your system with third party components and
files.
These files are not yet Windows
Server 2008 logo compliant and might lack information such as company name or
version number, or they may be missing a digital signature. The files that could be added during LABEL ARCHIVE
installation are produced by Macromedia (InstallShield
items), and Microsoft (Visual C++ items).
InstallShield Files:
LABEL ARCHIVE Server:
·
C:\Users\Tester\AppData\Local\Temp\ipoyjyuj.dll
·
C:\Windows\Installer\{EC0A725A-2FE4-40A9-BFD5-0B85828F9C67}\ARPPRODUCTICON.exe
·
C:\Windows\Installer\{EC0A725A-2FE4-40A9-BFD5-0B85828F9C67}\NewShortcut1.11E5B349_BFDC_46DD_B595_0EB492AC2070.exe
·
C:\Windows\Installer\{EC0A725A-2FE4-40A9-BFD5-0B85828F9C67}\NewShortcut2.FA59A3F0_ACC9_4182_AEBF_36E1F4664D31.exe
·
C:\Program
Files (x86)\InstallShield Installation
Information\{EC0A725A-2FE4-40A9-BFD5-0B85828F9C67}\ISSetup.dll
LABEL ARCHIVE Client:
·
C:\Users\nik\AppData\Local\Temp\ldaz0taa.dll
·
C:\Windows\Installer\{E3E8D5FF-FE83-480B-A0A9-2325F5500D93}\ARPPRODUCTICON.exe
·
C:\Windows\Installer\{E3E8D5FF-FE83-480B-A0A9-2325F5500D93}\NewShortcut1.11E5B349_BFDC_46DD_B595_0EB492AC2070.exe
·
C:\Windows\Installer\{E3E8D5FF-FE83-480B-A0A9-2325F5500D93}\NewShortcut2_E3E8D5FFFE83480BA0A92325F5500D93.exe
·
C:\Windows\Installer\{E3E8D5FF-FE83-480B-A0A9-2325F5500D93}\NewShortcut3_E3E8D5FFFE83480BA0A92325F5500D93.exe
·
C:\Program
Files (x86)\InstallShield Installation
Information\{E3E8D5FF-FE83-480B-A0A9-2325F5500D93}\ISSetup.dll
Microsoft Files:
·
C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Web.Admin#\78e8d9b1530d09c7d61d5aec8ab6459a\Microsoft.Web.Administration.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Web.Manag#\3ae79d8ea6b1d9f3853b9237aba4052e\Microsoft.Web.Management.Iis.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Web.Manag#\46657cce282a8f237d918ba7b87b14d0\Microsoft.Web.Management.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Web.Manag#\6644f3153a02cc80e78471b931149be0\Microsoft.Web.Management.Remoting.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Web.Manag#\6fe0eeaa8b0e0d5be4155f02fdab0493\Microsoft.Web.Management.AspnetClient.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Web.Manag#\a0e3e27daf3a4ae8935707e9da8d9e01\Microsoft.Web.Management.IisClient.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_32\Microsoft.Web.Manag#\ac017096a8db62ef188b04bb02e3a90b\Microsoft.Web.Management.Aspnet.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.Web.Admin#\870aa5ddd374e0d922f7b7812c25b606\Microsoft.Web.Administration.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.Web.Manag#\6cb191a80131cd34b642d1882f8f0f0e\Microsoft.Web.Management.AspnetClient.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.Web.Manag#\9133a6ae346a31be125ad86ab3484a87\Microsoft.Web.Management.Aspnet.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.Web.Manag#\967ea05bd6757049e318cd52c4edc1d7\Microsoft.Web.Management.IisClient.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.Web.Manag#\d7a41896a8191ea93fa3825796809731\Microsoft.Web.Management.Iis.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.Web.Manag#\e4d9f0ac004d5167f32c6673b111b615\Microsoft.Web.Management.ni.dll
·
C:\Windows\assembly\NativeImages_v2.0.50727_64\Microsoft.Web.Manag#\f01aa0bdb24b10631e5a416031550b3b\Microsoft.Web.Management.Remoting.ni.dll
·
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8\msvcm80.dll
·
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8\msvcp80.dll
·
C:\Windows\winsxs\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.762_none_10b2f55f9bffb8f8\msvcr80.dll
·
C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_0c178a139ee2a7ed\mfc80.dll
·
C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_0c178a139ee2a7ed\mfc80u.dll
·
C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_0c178a139ee2a7ed\mfcm80.dll
·
C:\Windows\winsxs\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.762_none_0c178a139ee2a7ed\mfcm80u.dll
This version of LABEL ARCHIVE is compatible
with the following TEKLYNX software packages:
·
CODESOFT
8.51.02, and CODESOFT 9.0
·
LABELVIEW
8.20.03
·
SENTINEL
5.06
Copyright 2009 Braton Groupe sarl.
All rights reserved. TEKLYNX and
its products are trademarks or registered trademarks of Braton Groupe sarl or
its affiliated companies. All other
brands and product names are the trademarks of their respective owners.
This release notes document is for
informational purposes only. Product specifications are likely to change.