Troubleshooting Twitter plug-in issues

To troubleshoot Twitter plug-in issues

1. Verify the configuration of the Twitter plug-ins.
   For more information, see the Twitter-User-Registration-plug-in-configuration and Twitter-Alert-Notification-plug-in-configuration.
   For more information about the AR System Administration: Plugin Server Configuration form and AR System Administration: AR System Configuration Generic UI form, see Configuring Java plug-in servers and Updating-configuration-settings-by-using-the-AR-System-Configuration-Generic-UI-form.
2. Troubleshoot common plug-in-related issues.
   For more information, see the General-approach-for-troubleshooting-plug-in-issues.
3. Make sure that Internet connectivity is available on the computer where Twitter plug-ins are installed and where the AR filters are running.
4. Check the logs for the following error codes:
   3226: User Already Registered.
   3227: Required fields have not been entered.
   3228: During Merge only Overwrite duplicate option is allowed.
   8753: consumer-key or consumer-secret or access-token or access-token-secret is null or empty. (In this case, verify entries in the AR System Alert Twitter User Authorization form).
5. If AR System server system clock is not synchronized with your time zone, you might receive the following error message:
   Error in plugin : 401:Authentication credentials (http://dev.twitter.com/pages/auth) were missing or incorrect. Ensure that you have set valid consumer key/secret, access token/secret, and the system clock is in sync. Failed to validate oauth signature and token Relevant d (ARERR 8753).
   To prevent this error, synchronize the system clock with your time zone.

6. If you receive the following error:
   

   Error in plugin: 410: {"errors": [{"message": "The Twitter REST API v1
   will soon stop functioning. Please migrate to API v1.1.https://dev/...
    

   Use the steps provided in Upgrade your Twitter4j API for BMC Remedy Twitter integration to correctly work to resolve the error.

7. To further investigate the issue, enable the following logs:
   • Server-side logs. For more information, see Enabling-server-side-AR-System-logs.
   • Plug-in specific logs. For more information, see To enable logs for the Twitter plug-in.

To enable logs for the Twitter plug-in

1. In a browser, open the AR System Administration Console, and select System > General > Plugin Server Configuration.
2. On the Plugin Server Configuration form, from the Plugin Server Instance list, select the instance for which you want to enable logs.
3. Go to the Plugin Server Configuration tab.
4. In the Logging Configurations area, from the Log Level list, select DEBUG.
5. Click Apply. 
   The arjavaplugin.log file generates the debug logs for the Twitter plug-in.