IBM 51 User Manual
Page 196
If
resetting
the
GUID
failed,
or
the
problem
persists,
contact
customer
support.
BTC1050I
true
Explanation:
No
additional
information
is
available
for
this
message.
BTC1051I
false
Explanation:
No
additional
information
is
available
for
this
message.
BTC1052I
The
common
agent
successfully
renewed
its
security
credentials.
Explanation:
No
additional
information
is
available
for
this
message.
BTC1053I
The
common
agent
failed
to
renew
its
security
credentials.
See
the
common
agent
logs
for
details
about
the
problem.
Explanation:
No
additional
information
is
available
for
this
message.
BTC1054I
The
common
agent
successfully
renewed
its
certificate
revocation
list.
Explanation:
No
additional
information
is
available
for
this
message.
BTC1055I
The
common
agent
failed
to
renew
its
certificate
revocation
list.
See
the
common
agent
logs
for
details
about
the
problem.
Explanation:
No
additional
information
is
available
for
this
message.
BTC1056I
The
common
agent
successfully
reset
its
GUID
and
security
credentials.
Explanation:
No
additional
information
is
available
for
this
message.
BTC1057I
The
common
agent
failed
to
reset
its
GUID
and
security
credentials.
See
the
common
agent
logs
for
details
about
the
problem.
Explanation:
No
additional
information
is
available
for
this
message.
BTC1058E
The
common
agent
registered
with
the
agent
manager,
but
the
credentials
are
not
valid
because
the
common
agent
and
the
agent
manager
clocks
are
not
synchronized.
Explanation:
The
validation
dates
for
the
certificate
are
set
using
the
agent
manager
clock,
but
the
clock
on
the
common
agent
has
one
of
the
following
problems:
v
It
is
earlier
than
the
not
valid
before
date
in
the
certificate.
v
It
is
later
than
the
not
valid
after
date,
or
expiration
date
in
the
certificate.
System
action:
Without
valid
credentials,
the
common
agent
will
not
function
correctly.
Local
command-line
interface
commands
will
not
work.
Resource
managers
with
clocks
that
are
synchronized
with
the
agent
manager
will
be
unable
to
contact
the
common
agent.
Direct
interaction
with
the
agent
manager
might
also
fail.
Administrator
Response:
To
correct
this
problem:
1.
Verify
that
the
clock
on
the
agent
manager
server
is
correct.
If
necessary,
update
the
clock
and
restart
the
agent
manager.
2.
Stop
the
agent.
3.
If
the
agentKeys.jks
file
exists,
delete
it
from
the
cert
directory
on
the
common
agent.
4.
Change
the
clock
on
the
computer
where
the
common
agent
is
installed
to
match
the
clock
on
the
agent
manager
server.
Set
the
clocks
to
local
time.
Time
zones
are
not
important
because
the
values
are
compared
in
coordinated
universal
time
(UTC).
5.
Start
the
agent.
The
agent
will
register
again
when
it
starts.
BTC2003I
The
configurator
service
was
successfully
started
and
deployed.
Explanation:
No
additional
information
is
available
for
this
message.
BTC2004I
The
configurator
service
was
successfully
stopped
and
undeployed.
Explanation:
No
additional
information
is
available
for
this
message.
BTC2005I
The
system
is
updating
the
port
to
port_number.
The
listening
port
will
change
during
the
next
startup
of
the
common
agent
or
after
the
connector
is
restarted.
Explanation:
The
request
to
update
the
listening
port
has
been
processed.
The
new
port
will
be
used
the
next
time
the
common
agent
is
started
or
after
the
connector
is
restarted.
184
Tivoli
Intelligent
Orchestrator
Problem
Determination
and
Troubleshooting
Guide