Elvis 4 Drive - troubleshooting

Note: With the discontinuation of support for Adobe Drive, the Elvis Drive has been made obsolete.

Before troubleshooting Elvis Drive installations, make sure to check the known issues and limitations.

Note: Make sure you have updated your Creative Suite applications and Adobe Drive to the latest available version.

Check the log files

Elvis Drive has its own logging configuration for connected clients, you can set it to the following levels:

• ERROR - only logs errors (**default**)
• WARN - also logs warnings
• INFO - also logs general information

You can modify the level of logging by adding the following to the config.properties.txt of the server:

driveLoggingLevel=ERROR

ERROR messages are added to the default Drive log, CS<version>ServiceManager_java.log, so CS5ServiceManager_java.log for example. When the level is set to WARN or INFO messages will not be added to the standard CS<version>ServiceManager_java.log, but to an additional log file:

• ElvisDrive_java.log

These logs can be found at:

• Windows: %APPDATA%\Adobe\CS<version>ServiceManager\logs
• Mac OS X: ~/Library/Application Support/Adobe/CS<version>ServiceManager/logs

Clean the Adobe Drive database

In some cases, the local Adobe Drive database on a client machine can get corrupted. If this happens you will experience unexpected behavior and see a lot of errors in the Drive logs.

To reset and clear the local Adobe Drive database, use the following steps:

Stop the following processes using the Windows Task Manager or OS X Activity Manager:

• AdobeDriveCS<version> (.exe)
• CS<version>ServiceManager (.exe)

Browse to:

• Windows: %APPDATA%\Adobe\CS<version>ServiceManager
• Mac OS X: ~/Library/Application Support/Adobe/CS<version>ServiceManager

Delete the following folders:

• database
• diskcache