atg.repository.search.indexing.IndexingException

Error sending record atg.endeca.index.record.Record@18fbb4a9{dimval.spec=[homeStoreRootCategory.cat1 0016], dimval.qualified_spec=[product.category:homeStoreRootCategory.cat10016], dimval.prop.category.siteId=[mobileHomeSite, mobileStoreSiteUS, storeS iteUS, homeSite], dimval.prop.category.rootCatalogId=[homeStoreCatalog], dimval.prop.category.ancestorCatalogIds=[homeStoreCatalog], dimval.dimension_ spec=[product.category], dimval.parent_spec=[homeStoreRootCategory], dimval.display_order=[4], dimval.prop.category.repositoryId=[cat10016], dimval.pr op.category.catalogs.repositoryId=[masterCatalog, homeStoreCatalog], dimval.display_name=[Home Accents]} to record store "EndecaDemoen_en_dimvals", Ro ot cause: Input record does not have a valid Id.

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 web38

  • ], dimval.prop.category.repositoryId=[cat10016], dimval.pr op.category.catalogs.repositoryId=[masterCatalog, homeStoreCatalog], dimval.display_name=[Home Accents]} to record store "EndecaDemoen_en_dimvals", Ro ot cause: Input record does not have a valid Id.
  • via Oracle Community by Rohan Dekate, 1 year ago
    ], dimval.prop.category.repositoryId=[catFloorLamps], dimval.prop.category.catalogs.repositoryId=[masterCatalog, homeStoreCatalog], dimval.display_name=[Floor Lamps]} to record store "ATGen_en_dimvals", Root cause: Input record does not have a valid Id.+
  • via Oracle Community by 978972, 1 year ago
    ], dimval.prop.category.repositoryId=[catFloorLamps], dimval.prop.category.catalogs.repositoryId=[masterCatalog, homeStoreCatalog], dimval.display_name=[Floor Lamps]} to record store "ATGen_en_dimvals", Root cause: Input record does not have a valid Id.
  • Stack trace

    • atg.repository.search.indexing.IndexingException: Error sending record atg.endeca.index.record.Record@18fbb4a9{dimval.spec=[homeStoreRootCategory.cat1 0016], dimval.qualified_spec=[product.category:homeStoreRootCategory.cat10016], dimval.prop.category.siteId=[mobileHomeSite, mobileStoreSiteUS, storeS iteUS, homeSite], dimval.prop.category.rootCatalogId=[homeStoreCatalog], dimval.prop.category.ancestorCatalogIds=[homeStoreCatalog], dimval.dimension_ spec=[product.category], dimval.parent_spec=[homeStoreRootCategory], dimval.display_order=[4], dimval.prop.category.repositoryId=[cat10016], dimval.pr op.category.catalogs.repositoryId=[masterCatalog, homeStoreCatalog], dimval.display_name=[Home Accents]} to record store "EndecaDemoen_en_dimvals", Ro ot cause: Input record does not have a valid Id. at atg.endeca.index.RecordStoreDocumentSubmitterSessionImpl.submitRecord(RecordStoreDocumentSubmitterSessionImpl.java:313) at atg.endeca.index.RecordSubmitterSessionImpl.submitDocument(RecordSubmitterSessionImpl.java:187) at atg.endeca.index.AbstractRecordStoreAggregateSession.submitDocument(AbstractRecordStoreAggregateSession.java:329) at atg.repository.search.indexing.LoaderImpl.outputAndSubmitDocument(LoaderImpl.java:1132) at atg.endeca.index.RecordStoreBulkLoaderImpl.outputAndSubmitDocument(RecordStoreBulkLoaderImpl.java:142) at atg.repository.search.indexing.LoaderImpl.processItem(LoaderImpl.java:799) at atg.repository.search.indexing.threading.ProcessItemJob.invoke(ProcessItemJob.java:145) at atg.common.util.ThreadDispatcherThread.run(ThreadDispatcherThread.java:178) Caused by: com.endeca.itl.recordstore.InvalidRecordException: Input record does not have a valid Id. at org.apache.cxf.jaxws.JaxWsClientProxy.invoke(JaxWsClientProxy.java:141) at $Proxy162.writeRecords(Unknown Source) at com.endeca.itl.recordstore.RecordStoreWriter.doFlush(RecordStoreWriter.java:170) at com.endeca.itl.recordstore.RecordStoreWriter.write(RecordStoreWriter.java:108) at atg.endeca.index.RecordStoreDocumentSubmitterSessionImpl.submitRecord(RecordStoreDocumentSubmitterSessionImpl.java:308) ... 7 more

    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.