| Sun Java System Content Delivery Server Error Messages |     |
| Sun Java System Content Delivery Server Error Messages | |
| C H A P T E R 3 |
|
Messages from Integrated Components |
The Content Delivery Server integrates with external components such as a subscriber database or DRM server. Messages received from these components or the adapters that integrate the components with the Content Delivery Server are written to the log file CDS.log in the $CDS_HOME/deployment/deployment-name/conf directory.
The following topics are presented in this chapter:
A subscriber adapter enables the Content Delivery Server to work with the data repository that contains subscriber information. The default adapter provides an interface between the Content Delivery Server and data stored in an Oracle database. An adapter is also provided that enables the Content Delivery Server to work with subscriber data that is stored in a directory based on the Lightweight Directory Access Protocol (LDAP) format.
This section describes the messages that are issued by the subscriber adapters that are provided with the Content Delivery Server. Messages are identified by a message number followed by the name of the class and the method that issued the message. If you are using your own subscriber adapter, you might see different messages that are not described here.
The following messages are written to the log file by the subscriber adapter for an Oracle database. All of the messages are categorized as severe. The messages are organized numerically.
[cds.UserManager] SEVERE <0100> SubscriberImplDAO.createUser: A user already exists with either Unique Device Id = unique-device-ID or Mobile Id = mobile-ID or User Id = login-ID
Description. A user with the same Unique Device ID, Mobile ID, or User ID already exists in the system.
Action. Either remove the current user from the system or choose a different Unique Device ID, Mobile ID, or User ID for the user that you are creating.
[cds.UserManager] SEVERE <0101> SubscriberImplDAO.createUser: Failed to create user
Description. An exception occurred while creating a user. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0102> SubscriberImplDAO.deleteUser: Failed to get CDSTransaction
Description. Cannot get the Content Delivery Server transaction for deleting a user.
Action. Make sure that the database server and connection are up and the database settings are correct in the database configuration file.
[cds.UserManager] SEVERE <0103> SubscriberImplDAO.deleteUser: Failed to delete user
Description. An exception occurred while deleting a user. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0104> SubscriberImplDAO.getUser: User ID cannot be NULL
Description. Cannot get a user when the User ID parameter is NULL.
Action. Report the error to your Content Delivery Server support representative.
[cds.UserManager] SEVERE <0105> SubscriberImplDAO.getUser: Failed to get CDSTransaction
Description. Cannot get the Content Delivery Server transaction for retrieving a user.
Action. Make sure that the database server and connection are up and the database settings are correct in the database configuration file.
[cds.UserManager] SEVERE <0106> SubscriberImplDAO.getUser: Failed to get user
Description. An exception occurred while getting user. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0107> SubscriberImplDAO.getUserByUniqueDeviceId: Failed to get CDSTransaction
Description. Cannot get the Content Delivery Server transaction for retrieving a user by the unique device ID.
Action. Make sure that the database server and connection are up and the database settings are correct in the database configuration file.
[cds.UserManager] SEVERE <0108> SubscriberImplDAO.getUserByUniqueDeviceId: Failed to get user by unique device ID
Description. An exception occurred while getting a user by a unique device ID. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0109> SubscriberImplDAO.getUserByMobileId: Failed to get CDSTransaction
Description. Cannot get the Content Delivery Server transaction for retrieving a user by a mobile ID.
Action. Make sure that the database server and connection are up and database settings are correct in the database configuration file.
[cds.UserManager] SEVERE <0110> SubscriberImplDAO.getUserByMobileId: Failed to get user by mobile ID
Description. An exception occurred while getting user by a mobile ID. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0111> SubscriberImplDAO.updateUser: User cannot be NULL
Description. Cannot update a user when the User parameter object is NULL.
Action. Report the error to your Content Delivery Server support representative.
[cds.UserManager] SEVERE <0112> SubscriberImplDAO.updateUser: A user already exists with either Unique Device Id = unique-device-ID or Mobile Id = mobile-ID or UserId = login-ID
Description. A user with the same Unique Device ID, Mobile ID, or User ID already exists in the system.
Action. Either remove the current user from the system or choose a different Unique Device ID, Mobile ID, or User ID for the user.
[cds.UserManager] SEVERE <0113> SubscriberImplDAO.updateUser: Failed to update user
Description. An exception occurred while updating user. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0114> SubscriberImplDAO.getAllUsers: Failed to get all users
Description. An exception occurred while getting all users. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0115> SubscriberImplDAO.getAllLikeInOrder: Failed to get all users like in order
Description. A exception occurred while getting all users like in order. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
[cds.UserManager] SEVERE <0116> SubscriberImplDAO.getCount: Failed to get count of all users
Description. An exception occurred while getting a count of all users. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the database server and connection are up.
The following messages are written to the log file by the subscriber adapter for an LDAP directory. All of the messages are categorized as severe. The messages are organized numerically.
[cds.LDAPUserManager] SEVERE <0004> Cannot get mapping for loginId field
Description. The mapping for the loginId field in your LDAP mapping file is not correctly mapped to a valid field in LDAP.
Action. Make sure that the loginId field mapped to a valid field in the mapping file.
[cds.LDAPUserManager] SEVERE <0012> LDAPUserManager.doIsAuthenticated: Unexpected exception while checking authentication
Description. An exception occurred while checking user authentication using LDAP. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the LDAP server and connection are up.
[cds.LDAPUserManager] SEVERE <0016> LDAPUserManager.doUpdateUser: Cannot update user
Description. An exception occurred while updating a user account in LDAP. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the LDAP server and connection are up.
[cds.LDAPUserManager] SEVERE <0029> LDAPUserManager.doEnableUser: User does not exist
Description. The user that you are trying to enable does not exist.
Action. Make sure that the user exists in LDAP.
[cds.LDAPUserManager] SEVERE <0030> LDAPUserManager.doEnableUser: Cannot enable user
Description. An exception occurred while enabling a user account in LDAP. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the LDAP server and connection are up.
[cds.LDAPUserManager] SEVERE <0032> LDAPUserManager.doAddUser: Cannot add user
Description. An exception occurred while adding a user account in LDAP. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the LDAP server and connection are up. Also, make sure that the user does not already exist in LDAP.
[cds.LDAPUserManager] SEVERE <0034> LDAPUserManager.doDisableUser: User does not exist
Description. The user that you are trying to disable does not exist.
Action. Make sure that the user you are trying to disable exists in LDAP.
[cds.LDAPUserManager] SEVERE <0035> LDAPUserManager.doDisableUser: Cannot disable user
Description. An exception while disabling user account in LDAP. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the LDAP server and connection are up.
[cds.LDAPUserManager] SEVERE <0037> LDAPUserManager.doRemoveUser: Cannot remove user
Description. An exception occurred while removing a user account in LDAP. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the LDAP server and connection are up. Also, make sure that the user exists in LDAP.
[cds.LDAPUserManager] SEVERE <0039> LDAPUserManager.doIsActive: User does not exist
Description. The user for which you are checking status does not exist.
Action. Make sure that the user for which you are checking status exists in LDAP.
[cds.LDAPUserManager] SEVERE <0100> LDAPListHelper.createUser: Error in parsing config XML file
Description. An exception occurred while parsing the mapping file. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the mapping file is syntactically correct and contains all required information.
[cds.LDAPUserManager] SEVERE <0101> LDAPListHelper.createUser: Error in creating user
Description. An exception occurred while creating user. The exception is also written to the log.
Action. The action to take depends on the exception reported. Make sure that the the LDAP server and connection are up. Also, make sure that the mapping file is syntactically correct and contains all required information.
To protect content using Open Mobile Alliance (OMA) DRM 1.0 methods, the Content Delivery Server works with the implementation of the OMA DRM 1.0 guidelines that you provide. Errors that are encountered during processing are written to the Content Delivery Server log.
For digital rights management, the Content Delivery Server provides support for SafeNet DRM Mobile. Errors that are encountered by DRM Mobile are written to the Content Delivery Server log. If you are using a different implementation of the Open Mobile Alliance (OMA) DRM 1.0 guidelines, you might see different messages that are not described here.
[cds.DRMMobile] SEVERE <0001> Failed to create usage profile usage-profile for edition id edition-ID
Description. The usage profile for Separate delivery protection of the edition could not be created. usage-profile is the profile being created and edition-ID is the edition with which the profile is associated.
Action. Verify that DRM Mobile is installed correctly and related configuration properties are set correctly.
[cds.DRMMobile] SEVERE <0002> HTTP request http-url to get rights for class id content-ID associated with pricemodel id pricemodel-db-pk failed
Description. The Separate delivery rights equivalent to the price model for the content could not be obtained. http-url is the request issued, content-ID is the content for which rights are requested, and pricemodel-db-pk is the price model associated with the content.
Action. Verify that DRM Mobile is installed correctly and related configuration properties are set correctly. Check that the corresponding entry for the content exists in DRM Mobile.
[cds.DRMMobile] SEVERE <0003> Could not connect to DRM Mobile host at http-url to get rights for content-ID
Description. An HTTP connection with DRM Mobile could not be established. http-url is the location to which a connection is requested. content-ID is the content for which rights are requested.
Action. Verify that DRM Mobile is installed correctly and related configuration properties are set correctly.
[cds.DRMMobile] SEVERE <0004> Failed to initialize the integration with DRM Mobile, please check the setup environment.
Description. The integration with DRM Mobile could not be initialized.
Action. Verify that DRM Mobile is installed correctly and related configuration properties are set correctly. Make sure that the host can be reached.
[cds.DRMMobile] INFO <0005> Initializing DRM Mobile integration module
Description. Initialization is in progress.
[cds.DRMMobile] INFO <0006> DRM Mobile integration module initialized successfully
Description. Initialization completed successfully.
[cds.DRMMobile] SEVERE <0007> Failed to protect content id content-ID
Description. The content binary could not be protected using one of the OMA DRM 1.0 methods. content-ID is the content to protect.
Action. Look for more details related to the error in log messages. Verify the DRM Mobile installation and related configuration properties.
[cds.DRMMobile] SEVERE <0008> Failed to store plain file at file-location
Description. The plain content binary could not be stored at file-location. The location is specified in the configuration.
Action. Make sure that the file location identified by file-location exists and the permissions are set correctly.
[cds.DRMMobile SEVERE] <0009> Failed to read protected file file
Description. The file could not opened for reading.
Action. Make sure that the file identified by file exists and the permissions are set correctly.
[cds.DRMMobile] SEVERE <0010> Failed to create rights. OMA Technology : delivery-mechanism and pricemodel id : pricemodel-db-pk
Description. The DRM Mobile equivalent usage-profile for the Content Delivery Server pricing model could not be generated.
Action. Deactivate the content until the issue is resolved. Verify that the content pricing model identified by pricemodel-db-pk and the requested delivery protection mechanism identified by delivery-mechanism are correct.
The following message is issued when a digital rights object cannot be delivered.
[cds.OMA] SEVERE <0001> Failed to send rights for content id content-ID to phone number phone-number
Description. The separate delivery rights could not be delivered to the subscriber after the purchase. content-ID identifies the content for which rights were requested and phone-number identifies the number to which rights are to be sent.
Action. Verify that DRM Mobile is installed correctly and related configuration properties are set correctly. Make sure the host can be reached. Look for any errors from the Messaging Service.
| Sun Java System Content Delivery Server Error Messages | 819-3214-10 | |
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.