Chapter 4
4-27
4.4 Related Service Mode
4.4.1 Invalidating the License for Transfer to a Different Device (Level 2)
0020-5817
Service Mode Item Used to Invalidate a License for Transfer to a Different Device (Level 2)
Possible Situation
A license may be used on a different device through transfer, as when replacing the device at the end of a lease agreement. To do so, the user must first invalidate
the existing license by performing a set of steps referred to as "invalidation of a license" using service mode. At times, both source and target of transfer may be the
same device, and a license therefore may also be invalidated only temporarily. It is important to note that the user must contact the Sales Company to make a license
good regardless of whether it has been invalidated intentionally or inadvertently.
Invalidation Procedure
Invalidation consists in invalidating the license in service mode and generating an invalidation certificate that proves the completion of invalidation. Invalidation
may take place for individual optional functions, and a specific function becomes no longer available as soon as an invalidation certificate is issued. The user con-
tacts the Sales Company and provides the following: the invalidation certificate, the device serial number of the source of transfer, the device serial number of the
Check the server.
#872
The HTTP response is 405 (Method Not Allowed).
The resource indicated in the URI does not permit the use of the method.
Check the server settings.
#873
The HTTP response is 407 (Proxy Authentication Required).
The attempt for authentication with the proxy server has failed.
In user mode, check the proxy
settings.
Transmission has failed.
#875
The HTTP response is 411 (Length Required).
The server rejected a request without a defined content length.
It may also have rejected the use of chunk transmission.
In user mode, disable (OFF) the
following: 'use chunk division
transmission for WebDAV'.
Transmission has failed.
#876
The HTTP response is 413 (Request Entity Too Large).
The request entity is larger than that assumed by the server or is capable
of processing, thus causing the server to reject the request.
Check the server settings.
Transmission has failed.
#877
The HTTP response is 414 (Request URI Too Long).
The request URI is longer than that assumed by the server for intermediate
processing, thus causing the server to reject the request.
Check the server settings.
Check the server.
#878
The HTTP response is 500 (Internal Server Error).
The server has encountered a situation that prevents the execution of the
request and that it cannot predict.
HTTP response is 506(Variant Also Negotiates).
HTTP response is 510 (Not Extended).
Check the server settings.
Check the server.
#879
The HTTP response is 501 (Not Implemented).
The request needs a function that the server does not support yet needed
for execution.
Check the server settings.
Check the server.
#880
The HTTP response is 502 (Bad Gateway).
The proxy has received an illegal response from a server located upstream.
Check the server settings.
Check the server.
#881
The HTTP response is 503 (Service Unavailable).
The server has a temporary overload condition or is not capable of
handling a request because of maintenance.
Check the server settings.
Check the server.
#882
The HTTP response is 504 (Gateway Timeout).
The proxy has sent the request to the server located upstream, but has
failed to receive a response.
Check the server settings.
Check the server.
#883
The HTTP response is 505 (HTTP Version Not Supported).
The server does not support the HTTP protocol version used by the request
message, or it has rejected the support in question.
Check the server settings.
Check the server.
#878
The HTTP response is 506 (Variation Also Negotiates).
The HTTP response is 510 (Not Extended).
Check the server settings.
Check the server.
#884
The HTTP response is 507 (Insufficient Storage).
The server has failed to make available a specific amount of memory to
process the request.
Check the server settings.
Transmission has failed.
#885
The WebDAV server or the proxy has returned an unexpected status code. Check the address.
Check the proxy settings.
Check the server settings.
Check the address.
#886
The HTTP response is 400 (Bad Request).
There is a syntax error.
This response is indicated when chunk transmission is attempted to ISA in
non-SSL mode.
If it is a non-SSL communication
and is by way of a proxy, disable
(OFF) the following: transmission/
reception setup>transmission
setup.
Service Call error (E749-0003) E749-0003
E749-003 boot command in conjunction with an mAccele configuration
change
Reset the power (by turning it off
and then back on).
Summary of Contents for Color Universal Send Kit-Q1
Page 1: ...SERVICE MANUAL Color Universal Send Kit Q1 JANUARY 21 2009 ...
Page 2: ......
Page 6: ......
Page 9: ...Chapter 1 Specifications ...
Page 10: ......
Page 12: ......
Page 17: ...Chapter 2 Functions ...
Page 18: ......
Page 20: ......
Page 43: ...Chapter 3 Installation ...
Page 44: ......
Page 46: ......
Page 59: ...Chapter 4 Maintenance ...
Page 60: ......
Page 62: ......
Page 94: ......
Page 95: ...Jan 21 2009 ...
Page 96: ......