ePolicy Orchestrator 3.0.2a patch 6 has been released. Available via PrimeSupport. This addresses some of the problems that people have posted along with patching the vulnerability that was discovered. This is supposed to help with the System Compliance Profiler.
----------------------------------------------------
ePolicy Orchestrator 3.0.2a patch 6 release notes
Solution ID : NAI37252 Last Modified : 14JUN2004
Goal and/or Problem Description
ePolicy Orchestrator 3.0.2a patch 6 release notes
On rare occasions, when using the local or remote console and System Compliance Profiler is checked into the master repository, no deployment task for System Compliance Profiler appears.
In certain cases, individual System Compliance Profiler reports were not visible in the
console. Only the high-level name "System Compliance Profiler" was shown in the reporting tree.
In rare cases after a successful repository replication, some files in the operating system
folder were deleted.
When importing an agent policy from a Super Agent, the Super Agent repository was not listed as a repository.
In some cases, certain NAP files could not be checked into the master repository, and
replications to distributed repositories stopped working.
In certain environments it was necessary for the SQL Server Service to be stopped for correct ePolicy Orchestrator server operation, with the following error messages placed in the SERVER.log.
E NAIMSERV Connection cleared successfully.
I DAL About the attempt to connect to database
E DAL COM Error :80004005 in OpenConx
E DAL Meaning = Unspecified error
E DAL Source = Microsoft OLE DB Provider for SQL
On occasion, distributed and Super Agent repositories containing an EXTRA.DAT file would not replicate the latest version of the EXTRA.DAT file from the master repository.
When using the local or remote console to configure uninstall command-line parameters in the deployment task settings for any product, the command-line parameters are not stored.
If you configured an FTP replication task to use anonymous login, and you used the local or remote console to do this, if you edited the replication task the user name was blank.
Under certain circumstances, when using the local or remote console to perform the task
"Sort Computers by IP", after you accept the value in the wizard, the console closes.
--------------------------------------------------------------------------------
Problem Environment
McAfee ePolicy Orchestrator 3.0 SP2a
--------------------------------------------------------------------------------
Changes affecting this problem
Change information is not available for this solution
--------------------------------------------------------------------------------
Cause of this problem
Cause information is not available for this solution
--------------------------------------------------------------------------------
Solution 1:
RESOLVED ISSUES
1. ISSUE:
On rare occasions, when using the local or
remote console and System Compliance Profiler is
checked into the master repository, no
deployment task for System Compliance Profiler
appears.
RESOLUTION:
This issue was caused by invalid entries in the
database for System Compliance Profiler. The
invalid entries have been corrected.
2. ISSUE:
In certain cases, individual System Compliance
Profiler reports were not visible in the
console. Only the high-level name "System
Compliance Profiler" was shown in the reporting
tree.
RESOLUTION:
The console was looking in the incorrect
location for the System Compliance Profiler
reports. The console now looks in the correct
location for these reports.
3. ISSUE:
In rare cases after a successful repository
replication, some files in the operating system
folder were deleted.
RESOLUTION:
On certain versions of Microsoft Windows NT
operating system, if a temporary variable was
not set, it was reported to ePolicy Orchestrator
that the temporary directory was the Operating
System folder. This resulted in the cleanup
after a successful repository replication, where
extra files were deleted. ePolicy Orchestrator
no longer removes files from invalid temporary
directories that were passed to it by the
operating system.
4. ISSUE:
When importing an agent policy from a Super
Agent, the Super Agent repository was not listed
as a repository.
RESOLUTION:
This issue was caused by incorrect notification
during the policy import procedure, which
triggered the Super Agent to be added as a
repository. Now the agent policy import
correctly adds the Super Agent as a repository.
5. ISSUE:
In some cases, certain NAP files could not be
checked into the master repository, and
replications to distributed repositories stopped
working.
RESOLUTION:
This issue was caused by ePolicy Orchestrator
incorrectly handling products whose product
package included the product NAP file. The
ePolicy Orchestrator software now handles all
NAP files found in the master repository as part
of the product package.
6. ISSUE:
In certain environments it was necessary for the
SQL Server Service to be stopped for correct
ePolicy Orchestrator server operation, with the
following error messages placed in the
SERVER.log.
ENAIMSERV Connection cleared successfully.
IDAL About the attempt to connect to database
EDAL COM Error :80004005 in OpenConx
EDAL Meaning = Unspecified error
EDAL Source = Microsoft OLE DB Provider for SQL
RESOLUTION:
Reconstructing the SQL database connections for
various ePolicy Orchestrator database
transactions could cause this issue. The ePolicy
Orchestrator software no longer has this issue.
7. ISSUE:
On occasion, distributed and Super Agent
repositories containing an EXTRA.DAT file would
not replicate the latest version of the
EXTRA.DAT file from the master repository.
RESOLUTION:
This issue was caused by incorrectly determining
that the EXTRA.DAT file in the distributed
repositories was a newer version. The EXTRA.DAT
file in the master repository is now correctly
identified as the newer version.
8. ISSUE:
When using the local or remote console to
configure uninstall command-line parameters in
the deployment task settings for any product,
the command-line parameters are not stored.
RESOLUTION:
This issue was caused by incorrectly storing the
uninstall command-line parameters. The uninstall
command-line parameters are now stored
correctly.
9. ISSUE:
If you configured an FTP replication task to use
anonymous login, and you used the local or
remote console to do this, if you edited the
replication task the user name was blank.
RESOLUTION:
This issue was caused by the user interface
storing --but incorrectly displaying -- the user
login. The user login is now shown correctly.
10. ISSUE:
Under certain circumstances, when using the
local or remote console to perform the task
"Sort Computers by IP", after you accept the
value in the wizard, the console closes.
RESOLUTION:
This issue was caused by incorrectly handling
the data in the IP address properties. Now the
data in the IP address properties are handled
correctly.
11. ISSUE:
When using the local or remote console to run
the "Product Events by Severity" report, the
legend list may show a number instead of the
correct text replacement.
RESOLUTION:
In certain cases, the report was defaulting to a
number instead of getting the correct text
replacement. This report now retrieves the
correct text replacement.
12. ISSUE:
In rare cases, agents could not communicate to
the ePolicy Orchestrator server due to the
server passing the agents a SITELIST.XML file
that erased the server IP address or the
communication port, or both.
RESOLUTION:
This was caused by the ePolicy Orchestrator
server attempting to generate a new SITELIST.XML
file when the SITEINFO.INI file was in use by
other server processes. The ePolicy
Orchestrator server only generates a new
SITELIST.XML when SITEINFO.INI is not in use by
other server processes.
13. ISSUE:
Under certain circumstances, when using the
local or remote console running coverage
reports, "NO DATA FOUND" appears in the report.
RESOLUTION:
The branch node tables included orphaned
entries. These orphaned entries are now removed
to allow the coverage reports to run correctly.
14. ISSUE:
When using the local or remote console with ePO
authentication to log into reporting, an error
may occur, avimsnap pop-up error:
"Subquery returned more than one value. This is
not permitted when the subquery follows =, !=,
<, <=, >, >= or when the subquery is used as an
expression. The statement has been
terminated."
RESOLUTION:
A stored procedure was unable to handle
duplicate entries in the ReportVersionClient
table. The stored procedure now handles
duplicate entries correctly.
15. ISSUE:
Under certain conditions, NAIMSERV.EXE had
instability issues, which resulted in an access
violation error that could cause the server to
crash.
RESOLUTION:
NAIMSERV.EXE has been modified and will no
longer crash in these cases.
16. ISSUE:
When using an FTP repository on a Microsoft
Windows 2003 Server running Microsoft IIS
version 6.0 FTP services, and the banner started
with four or more blank spaces, replication
would fail due to a login failure.
RESOLUTION:
The four or more extra spaces were processed as
an FTP status code. The ePolicy Orchestrator
software now correctly determines FTP status
codes.
17. ISSUE:
When using localized clients to view disk space
and free disk space in the system section on the
Properties tab in the console, an incorrect
value would be shown instead of the true disk
space and free disk space.
RESOLUTION:
The ePolicy Orchestrator server was not
correctly parsing the localized language number
separators. The server now correctly parses the
number separators.
18. ISSUE:
After checking in the McAfee GroupShield 6.0 NAP
file to the repository, then using the console
to administer the McAfee GroupShield 6.0
product, the console would become
non-responsive.
RESOLUTION:
When the McAfee GroupShield 6.0 NAP file was
checked into the repository, Java Runtime
Environment (JRE) version 1.4.1 was installed.
The JRE 1.4.1 version experienced compatibility
problems with ePolicy Orchestrator. The ePolicy
Orchestrator software is now compatible with
version 1.4.1 of JRE.
19. ISSUE:
McAfee ePolicy Orchestrator may stop replicating
to repositories and may display the error "DAL
ePO 3.0 DAL exit" in the SITEMGR.LOG.
RESOLUTION:
This issue stemmed from two causes:
- NAREPL32.EXE used default DCOM permissions to
operate correctly. If default DCOM
permissions were altered, NAREPL32.EXE would
not function correctly. NAREPL32.EXE is now
registered with explicit DCOM permissions.
- The state in SITEMGR.INI set the task status
to a value that resulted in replication tasks
freezing when they were scheduled too close
together, which caused the running task to be
terminated by the scheduler without resetting
the status in the SITEMGR.INI file. This
would cause future tasks not to run. This
issue no longer occurs.
20. ISSUE:
When replicating to repositories using ePolicy
Orchestrator, replications may fail with the
message "Error occurred while verifying file
delta.ini" placed in the SITEMGR.LOG.
RESOLUTION:
On rare occasions, when repositories were being
replicated, it was possible that extra
characters were appended to the end of the files
in the repository. Repository replication no
longer appends extra characters to the end of
files in the repositories.
21. ISSUE:
The DAT version for Norton Antivirus was not
being reported correctly to ePolicy
Orchestrator; this resulted in incorrect
properties and reports.
RESOLUTION:
This patch places a new NAP file and plug-in for
Norton Antivirus in the repository that now
correctly formats the DAT version from the
Norton Antivirus products.
22. ISSUE:
This release addresses the ePolicy Orchestrator
Remote Command Execution Vulnerability;
vulnerability identifier: CAN-2004-0038.
RESOLUTION:
This vulnerability no longer exists.
23. ISSUE:
When the ePolicy Orchestrator server is busy,
the remote console login process may be slow.
RESOLUTION:
The console login and package check-in have been
changed so that they now process synchronously.
24. ISSUE:
In certain low bandwidth environments, the
ePolicy Orchestrator server did not process
socket I/O optimally, causing the HTTP
connections to reach the limit specified in the
server settings and start rejecting any
additional connections.
RESOLUTION:
The ePolicy Orchestrator server now handles all
socket I/O in blocking mode. Now when agent
connections come to the server, the worker
thread picks up the connection and waits on read
or write operations for 15 seconds. If data
doesn't come in during that period, the server
puts the socket back in the work queue and the
worker thread processes the next request.
ADDITIONAL INFORMATION:
There are now four new performance counters for
tracking socket read and write time-outs.
The following new performance counters have been
added:
- Number of socket read watches
- Number of socket read time-outs
- Number of sockets write watches
- Number of sockets write time-outs
25. ISSUE:
The time-out connection logic sometimes caused
the HTTP connections to build up over extended
periods of time.
RESOLUTION:
Now, if a value is defined for
"ConnectionTimeout=" in SERVER.INI, the time-out
for inactive sockets uses this figure.
Otherwise, 15 minutes is the time-out value.
ADDITIONAL INFORMATION:
To specify a connection time-out in SERVER.INI,
do the following:
1. In a text editor, open SERVER.INI. This file
is located in the DB folder in the
installation directory. The default
installation directory is:
C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\3.0.1
2. Type the following line in SERVER.INI, then
save the file:
ConnectionTimeout=NNN
Where NNN equals the number of seconds. For
example, ConnectionTimeout=900
3. In the "Service" dialog box, select the
"McAfee ePolicy Orchestrator 3.0.1 Server"
service, click "Stop," then click "Start" to
restart the service.
26. ISSUE:
Replication tasks using FTP would result in
partial or incomplete replications.
RESOLUTION:
Changes to the FTP communication subsystems make
them more reliable and fault tolerant in a
variety of environments.
27. ISSUE:
A limitation on the number of sites within the
directory tree caused the console to close when
someone clicked "Create user" or "Modify user."
RESOLUTION:
There is no longer a limit on the number of
sites in the directory tree.
28. ISSUE:
A duplicate path delimiter was being added
during the generation of all agent file paths,
which caused an entry in the sitemgr.log, such
as "Failed to verify file size for agent.ini".
RESOLUTION:
The agent file paths are generated correctly.
--------------------------------------------------------------------------------
Solution 2:
The patch listed above can be downloaded directly without contacting Technical Support. It is located at the following location: < You must be registered with Prime Support Service Portal and have a valid Grant number for this product to access the patch. If you do not have a valid Grant number, please contact Customer Service at 800-338-8754 As of the time of this posting, this patch was the latest patch available for the product and issues listed above. If this patch is no longer present, please check for a newer version.
----------------------------------------------------
ePolicy Orchestrator 3.0.2a patch 6 release notes
Solution ID : NAI37252 Last Modified : 14JUN2004
Goal and/or Problem Description
ePolicy Orchestrator 3.0.2a patch 6 release notes
On rare occasions, when using the local or remote console and System Compliance Profiler is checked into the master repository, no deployment task for System Compliance Profiler appears.
In certain cases, individual System Compliance Profiler reports were not visible in the
console. Only the high-level name "System Compliance Profiler" was shown in the reporting tree.
In rare cases after a successful repository replication, some files in the operating system
folder were deleted.
When importing an agent policy from a Super Agent, the Super Agent repository was not listed as a repository.
In some cases, certain NAP files could not be checked into the master repository, and
replications to distributed repositories stopped working.
In certain environments it was necessary for the SQL Server Service to be stopped for correct ePolicy Orchestrator server operation, with the following error messages placed in the SERVER.log.
E NAIMSERV Connection cleared successfully.
I DAL About the attempt to connect to database
E DAL COM Error :80004005 in OpenConx
E DAL Meaning = Unspecified error
E DAL Source = Microsoft OLE DB Provider for SQL
On occasion, distributed and Super Agent repositories containing an EXTRA.DAT file would not replicate the latest version of the EXTRA.DAT file from the master repository.
When using the local or remote console to configure uninstall command-line parameters in the deployment task settings for any product, the command-line parameters are not stored.
If you configured an FTP replication task to use anonymous login, and you used the local or remote console to do this, if you edited the replication task the user name was blank.
Under certain circumstances, when using the local or remote console to perform the task
"Sort Computers by IP", after you accept the value in the wizard, the console closes.
--------------------------------------------------------------------------------
Problem Environment
McAfee ePolicy Orchestrator 3.0 SP2a
--------------------------------------------------------------------------------
Changes affecting this problem
Change information is not available for this solution
--------------------------------------------------------------------------------
Cause of this problem
Cause information is not available for this solution
--------------------------------------------------------------------------------
Solution 1:
RESOLVED ISSUES
1. ISSUE:
On rare occasions, when using the local or
remote console and System Compliance Profiler is
checked into the master repository, no
deployment task for System Compliance Profiler
appears.
RESOLUTION:
This issue was caused by invalid entries in the
database for System Compliance Profiler. The
invalid entries have been corrected.
2. ISSUE:
In certain cases, individual System Compliance
Profiler reports were not visible in the
console. Only the high-level name "System
Compliance Profiler" was shown in the reporting
tree.
RESOLUTION:
The console was looking in the incorrect
location for the System Compliance Profiler
reports. The console now looks in the correct
location for these reports.
3. ISSUE:
In rare cases after a successful repository
replication, some files in the operating system
folder were deleted.
RESOLUTION:
On certain versions of Microsoft Windows NT
operating system, if a temporary variable was
not set, it was reported to ePolicy Orchestrator
that the temporary directory was the Operating
System folder. This resulted in the cleanup
after a successful repository replication, where
extra files were deleted. ePolicy Orchestrator
no longer removes files from invalid temporary
directories that were passed to it by the
operating system.
4. ISSUE:
When importing an agent policy from a Super
Agent, the Super Agent repository was not listed
as a repository.
RESOLUTION:
This issue was caused by incorrect notification
during the policy import procedure, which
triggered the Super Agent to be added as a
repository. Now the agent policy import
correctly adds the Super Agent as a repository.
5. ISSUE:
In some cases, certain NAP files could not be
checked into the master repository, and
replications to distributed repositories stopped
working.
RESOLUTION:
This issue was caused by ePolicy Orchestrator
incorrectly handling products whose product
package included the product NAP file. The
ePolicy Orchestrator software now handles all
NAP files found in the master repository as part
of the product package.
6. ISSUE:
In certain environments it was necessary for the
SQL Server Service to be stopped for correct
ePolicy Orchestrator server operation, with the
following error messages placed in the
SERVER.log.
ENAIMSERV Connection cleared successfully.
IDAL About the attempt to connect to database
EDAL COM Error :80004005 in OpenConx
EDAL Meaning = Unspecified error
EDAL Source = Microsoft OLE DB Provider for SQL
RESOLUTION:
Reconstructing the SQL database connections for
various ePolicy Orchestrator database
transactions could cause this issue. The ePolicy
Orchestrator software no longer has this issue.
7. ISSUE:
On occasion, distributed and Super Agent
repositories containing an EXTRA.DAT file would
not replicate the latest version of the
EXTRA.DAT file from the master repository.
RESOLUTION:
This issue was caused by incorrectly determining
that the EXTRA.DAT file in the distributed
repositories was a newer version. The EXTRA.DAT
file in the master repository is now correctly
identified as the newer version.
8. ISSUE:
When using the local or remote console to
configure uninstall command-line parameters in
the deployment task settings for any product,
the command-line parameters are not stored.
RESOLUTION:
This issue was caused by incorrectly storing the
uninstall command-line parameters. The uninstall
command-line parameters are now stored
correctly.
9. ISSUE:
If you configured an FTP replication task to use
anonymous login, and you used the local or
remote console to do this, if you edited the
replication task the user name was blank.
RESOLUTION:
This issue was caused by the user interface
storing --but incorrectly displaying -- the user
login. The user login is now shown correctly.
10. ISSUE:
Under certain circumstances, when using the
local or remote console to perform the task
"Sort Computers by IP", after you accept the
value in the wizard, the console closes.
RESOLUTION:
This issue was caused by incorrectly handling
the data in the IP address properties. Now the
data in the IP address properties are handled
correctly.
11. ISSUE:
When using the local or remote console to run
the "Product Events by Severity" report, the
legend list may show a number instead of the
correct text replacement.
RESOLUTION:
In certain cases, the report was defaulting to a
number instead of getting the correct text
replacement. This report now retrieves the
correct text replacement.
12. ISSUE:
In rare cases, agents could not communicate to
the ePolicy Orchestrator server due to the
server passing the agents a SITELIST.XML file
that erased the server IP address or the
communication port, or both.
RESOLUTION:
This was caused by the ePolicy Orchestrator
server attempting to generate a new SITELIST.XML
file when the SITEINFO.INI file was in use by
other server processes. The ePolicy
Orchestrator server only generates a new
SITELIST.XML when SITEINFO.INI is not in use by
other server processes.
13. ISSUE:
Under certain circumstances, when using the
local or remote console running coverage
reports, "NO DATA FOUND" appears in the report.
RESOLUTION:
The branch node tables included orphaned
entries. These orphaned entries are now removed
to allow the coverage reports to run correctly.
14. ISSUE:
When using the local or remote console with ePO
authentication to log into reporting, an error
may occur, avimsnap pop-up error:
"Subquery returned more than one value. This is
not permitted when the subquery follows =, !=,
<, <=, >, >= or when the subquery is used as an
expression. The statement has been
terminated."
RESOLUTION:
A stored procedure was unable to handle
duplicate entries in the ReportVersionClient
table. The stored procedure now handles
duplicate entries correctly.
15. ISSUE:
Under certain conditions, NAIMSERV.EXE had
instability issues, which resulted in an access
violation error that could cause the server to
crash.
RESOLUTION:
NAIMSERV.EXE has been modified and will no
longer crash in these cases.
16. ISSUE:
When using an FTP repository on a Microsoft
Windows 2003 Server running Microsoft IIS
version 6.0 FTP services, and the banner started
with four or more blank spaces, replication
would fail due to a login failure.
RESOLUTION:
The four or more extra spaces were processed as
an FTP status code. The ePolicy Orchestrator
software now correctly determines FTP status
codes.
17. ISSUE:
When using localized clients to view disk space
and free disk space in the system section on the
Properties tab in the console, an incorrect
value would be shown instead of the true disk
space and free disk space.
RESOLUTION:
The ePolicy Orchestrator server was not
correctly parsing the localized language number
separators. The server now correctly parses the
number separators.
18. ISSUE:
After checking in the McAfee GroupShield 6.0 NAP
file to the repository, then using the console
to administer the McAfee GroupShield 6.0
product, the console would become
non-responsive.
RESOLUTION:
When the McAfee GroupShield 6.0 NAP file was
checked into the repository, Java Runtime
Environment (JRE) version 1.4.1 was installed.
The JRE 1.4.1 version experienced compatibility
problems with ePolicy Orchestrator. The ePolicy
Orchestrator software is now compatible with
version 1.4.1 of JRE.
19. ISSUE:
McAfee ePolicy Orchestrator may stop replicating
to repositories and may display the error "DAL
ePO 3.0 DAL exit" in the SITEMGR.LOG.
RESOLUTION:
This issue stemmed from two causes:
- NAREPL32.EXE used default DCOM permissions to
operate correctly. If default DCOM
permissions were altered, NAREPL32.EXE would
not function correctly. NAREPL32.EXE is now
registered with explicit DCOM permissions.
- The state in SITEMGR.INI set the task status
to a value that resulted in replication tasks
freezing when they were scheduled too close
together, which caused the running task to be
terminated by the scheduler without resetting
the status in the SITEMGR.INI file. This
would cause future tasks not to run. This
issue no longer occurs.
20. ISSUE:
When replicating to repositories using ePolicy
Orchestrator, replications may fail with the
message "Error occurred while verifying file
delta.ini" placed in the SITEMGR.LOG.
RESOLUTION:
On rare occasions, when repositories were being
replicated, it was possible that extra
characters were appended to the end of the files
in the repository. Repository replication no
longer appends extra characters to the end of
files in the repositories.
21. ISSUE:
The DAT version for Norton Antivirus was not
being reported correctly to ePolicy
Orchestrator; this resulted in incorrect
properties and reports.
RESOLUTION:
This patch places a new NAP file and plug-in for
Norton Antivirus in the repository that now
correctly formats the DAT version from the
Norton Antivirus products.
22. ISSUE:
This release addresses the ePolicy Orchestrator
Remote Command Execution Vulnerability;
vulnerability identifier: CAN-2004-0038.
RESOLUTION:
This vulnerability no longer exists.
23. ISSUE:
When the ePolicy Orchestrator server is busy,
the remote console login process may be slow.
RESOLUTION:
The console login and package check-in have been
changed so that they now process synchronously.
24. ISSUE:
In certain low bandwidth environments, the
ePolicy Orchestrator server did not process
socket I/O optimally, causing the HTTP
connections to reach the limit specified in the
server settings and start rejecting any
additional connections.
RESOLUTION:
The ePolicy Orchestrator server now handles all
socket I/O in blocking mode. Now when agent
connections come to the server, the worker
thread picks up the connection and waits on read
or write operations for 15 seconds. If data
doesn't come in during that period, the server
puts the socket back in the work queue and the
worker thread processes the next request.
ADDITIONAL INFORMATION:
There are now four new performance counters for
tracking socket read and write time-outs.
The following new performance counters have been
added:
- Number of socket read watches
- Number of socket read time-outs
- Number of sockets write watches
- Number of sockets write time-outs
25. ISSUE:
The time-out connection logic sometimes caused
the HTTP connections to build up over extended
periods of time.
RESOLUTION:
Now, if a value is defined for
"ConnectionTimeout=" in SERVER.INI, the time-out
for inactive sockets uses this figure.
Otherwise, 15 minutes is the time-out value.
ADDITIONAL INFORMATION:
To specify a connection time-out in SERVER.INI,
do the following:
1. In a text editor, open SERVER.INI. This file
is located in the DB folder in the
installation directory. The default
installation directory is:
C:\PROGRAM FILES\NETWORK ASSOCIATES\EPO\3.0.1
2. Type the following line in SERVER.INI, then
save the file:
ConnectionTimeout=NNN
Where NNN equals the number of seconds. For
example, ConnectionTimeout=900
3. In the "Service" dialog box, select the
"McAfee ePolicy Orchestrator 3.0.1 Server"
service, click "Stop," then click "Start" to
restart the service.
26. ISSUE:
Replication tasks using FTP would result in
partial or incomplete replications.
RESOLUTION:
Changes to the FTP communication subsystems make
them more reliable and fault tolerant in a
variety of environments.
27. ISSUE:
A limitation on the number of sites within the
directory tree caused the console to close when
someone clicked "Create user" or "Modify user."
RESOLUTION:
There is no longer a limit on the number of
sites in the directory tree.
28. ISSUE:
A duplicate path delimiter was being added
during the generation of all agent file paths,
which caused an entry in the sitemgr.log, such
as "Failed to verify file size for agent.ini".
RESOLUTION:
The agent file paths are generated correctly.
--------------------------------------------------------------------------------
Solution 2:
The patch listed above can be downloaded directly without contacting Technical Support. It is located at the following location: < You must be registered with Prime Support Service Portal and have a valid Grant number for this product to access the patch. If you do not have a valid Grant number, please contact Customer Service at 800-338-8754 As of the time of this posting, this patch was the latest patch available for the product and issues listed above. If this patch is no longer present, please check for a newer version.
