org.pentaho.platform.api.repository.ContentException

CONTITEM.ERROR_0001 - There is no input available because this content item (9f032ccb-27a1-11e3-ad91-995056df0365) hasnt been written to.

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web4

  • via Pentaho BI Platform Tracking by Brandon Bruce, 1 year ago
    CONTITEM.ERROR_0001 - There is no input available because this content item (9f032ccb-27a1-11e3-ad91-995056df0365) hasnt been written to.
  • via Pentaho BI Platform Tracking by Brandon Bruce, 1 year ago
    CONTITEM.ERROR_0001 - There is no input available because this content item (9f032ccb-27a1-11e3-ad91-995056df0365) hasnt been written to.
  • via Pentaho BI Platform Tracking by Brandon Bruce, 1 year ago
    CONTITEM.ERROR_0001 - There is no input available because this content item (9f032ccb-27a1-11e3-ad91-995056df0365) hasnt been written to.
  • Stack trace

    • org.pentaho.platform.api.repository.ContentException: CONTITEM.ERROR_0001 - There is no input available because this content item (9f032ccb-27a1-11e3-ad91-995056df0365) hasnt been written to. at org.pentaho.platform.repository.content.ContentItem.getDataSource(ContentItem.java:152) at org.pentaho.platform.repository.subscription.SubscriptionExecute.emailContent(SubscriptionExecute.java:357) at org.pentaho.platform.repository.subscription.SubscriptionExecute.execute(SubscriptionExecute.java:263) at org.pentaho.platform.repository.subscription.SubscriptionExecute.execute(SubscriptionExecute.java:169) at org.pentaho.platform.scheduler.QuartzSubscriptionJob.execute(QuartzSubscriptionJob.java:34) at org.quartz.core.JobRunShell.run(JobRunShell.java:203) at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.