OroCommerce Forums

Covering OroCommerce topics, including community updates and company announcements.

Forums OroCommerce demo installation fails on entity not found

This topic contains 6 replies, has 3 voices, and was last updated by Andrey Yatsenko Andrey Yatsenko 3 months, 3 weeks ago.

  • Creator
    Topic
  • #37970

    fatnassi.s
    Participant

    hellow!
    While trying to install demo data within OroCommerce Community Edition (release 3.0.0) , i get this error

    ” > loading Oro\Bundle\AlternativeCheckoutBundle\Migrations\Data\Demo\ORM\UpdateAlternativeCheckoutWorkflowStatus

    In WorkflowScopeManager.php line 107:

    Workflow Scope configuration error: Cannot find entity “Oro\Bundle\CustomerBundle\Entity\Customer” w
    ith id “4”. ”

    Am within ubuntu 14.04 (+apache 2.4).any idea?

Viewing 6 replies - 1 through 6 (of 6 total)
  • Author
    Replies
  • #37976
    Michael
    Michael
    Keymaster

    Hello fatnassi.s,

    How exactly are you trying to install the sample data?

    PS. Just checked that adding sample data during installation with the installer option works on 3.0.0 community without any errors:

    #37981

    fatnassi.s
    Participant

    hellow!
    am trying to install it within this command :
    php ./bin/console oro:migration:data:load –fixtures-type=demo –env=prod
    (the application has already been installed , as a second step am trying to execute that command to get the demo).

    and gettting this :
    Processing command “oro:cron:dotmailer:force-fields-sync”: setting up schedule..
    Processing command “oro:cron:dotmailer:mapped-fields-updates:process”: setting up schedule..
    Loading workflow definitions…
    > orocrm_contact_us_contact_request
    > task_flow
    > b2b_rfq_backoffice_default
    > b2b_rfq_frontoffice_default
    > b2b_flow_lead
    > b2b_flow_sales_funnel
    > opportunity_flow
    > b2c_flow_abandoned_shopping_cart
    > b2c_flow_order_follow_up
    > b2b_flow_checkout
    > b2b_flow_checkout_single_page
    > b2b_flow_alternative_checkout
    > b2b_quote_backoffice_approvals
    > b2b_quote_backoffice_default
    > quote_flow
    > commerce_opportunity_flow

    Please run command ‘oro:translation:load’ to load translations.
    [info] > process definition: “sync_email_flag_after_changed” – updated
    [info] > process definition: “schedule_integration” – updated
    [info] > process definition: “clear_user_email_origin_on_deactivation” – updated
    [info] > process definition: “clear_imap_email_folder_on_sync_enabled_change” – updated
    [info] > process definition: “analytics_channel_calculate_rfm” – updated
    [info] > process definition: “convert_mailbox_email_to_lead” – updated
    [info] > process definition: “magento_customer_creation” – updated
    [info] > process definition: “magento_customer_export” – updated
    [info] > process definition: “magento_customer_address_export” – updated
    [info] > process definition: “magento_analytics_customer_calculate” – updated
    [info] > process definition: “magento_analytics_customer_calculate_imported” – updated
    [info] > process definition: “magento_soap_schedule_integration” – updated
    [info] > process definition: “magento_rest_schedule_integration” – updated
    [info] > process definition: “expire_orders” – updated
    [info] > process definition: “expire_quotes” – updated
    [info] > process definition: “send_no_quote_alert” – updated
    [info] > process definition: “convert_mailbox_email_to_case” – updated
    [info] > process definition: “synchronize_marketing_list_item_for_mailchimp_member_activity” – updated
    [info] > process definition: “create_email_campaign_for_mailchimp_campaign” – updated
    [info] > process definition: “mailchimp_handle_member_state” – updated
    [info] > process definition: “schedule_mailchimp_segment_synchronization” – updated
    [info] > process definition: “dotmailer_email_campaign_creation” – updated
    [info] > process definition: “dotmailer_contact_activity_update” – updated
    [info] > process definition: “dotmailer_collect_marketing_activities” – updated
    [info] > process definition: “dotmailer_handle_contact_state” – updated
    [info] > process definition: “schedule_dotmailer_address_book_synchronization” – updated
    [info] > process definition: “dotmailer_handle_removed_address_book_contact” – updated
    [info] Process definitions configuration updates are stored into database
    [info] >> process trigger: analytics_channel_calculate_rfm [update] – updated
    [info] >> process trigger: clear_imap_email_folder_on_sync_enabled_change [update] – updated
    [info] >> process trigger: clear_user_email_origin_on_deactivation [update] – updated
    [info] >> process trigger: create_email_campaign_for_mailchimp_campaign [create] – updated
    [info] >> process trigger: dotmailer_collect_marketing_activities [create] – updated
    [info] >> process trigger: dotmailer_collect_marketing_activities [update] – updated
    [info] >> process trigger: dotmailer_contact_activity_update [create] – updated
    [info] >> process trigger: dotmailer_contact_activity_update [update] – updated
    [info] >> process trigger: dotmailer_email_campaign_creation [create] – updated
    [info] >> process trigger: dotmailer_handle_contact_state [create] – updated
    [info] >> process trigger: dotmailer_handle_contact_state [update] – updated
    [info] >> process trigger: dotmailer_handle_removed_address_book_contact [delete] – updated
    [info] >> process trigger: expire_orders [cron:10 * * * *] – updated
    [info] >> process trigger: expire_quotes [cron:1 * * * *] – updated
    [info] >> process trigger: magento_analytics_customer_calculate [update] – updated
    [info] >> process trigger: magento_analytics_customer_calculate_imported [create] – updated
    [info] >> process trigger: magento_customer_address_export [update] – updated
    [info] >> process trigger: magento_customer_creation [create] – updated
    [info] >> process trigger: magento_customer_export [update] – updated
    [info] >> process trigger: magento_rest_schedule_integration [update] – updated
    [info] >> process trigger: magento_soap_schedule_integration [update] – updated
    [info] >> process trigger: mailchimp_handle_member_state [update] – updated
    [info] >> process trigger: schedule_dotmailer_address_book_synchronization [update] – updated
    [info] >> process trigger: schedule_integration [update] – updated
    [info] >> process trigger: schedule_integration [create] – updated
    [info] >> process trigger: schedule_mailchimp_segment_synchronization [create] – updated
    [info] >> process trigger: schedule_mailchimp_segment_synchronization [update] – updated
    [info] >> process trigger: sync_email_flag_after_changed [update] – updated
    [info] >> process trigger: synchronize_marketing_list_item_for_mailchimp_member_activity [create] – updated
    [info] >> process triggers modifications stored in DB
    [info] >>> cron schedule [10 * * * *] oro:process:handle-trigger –id=13 –name=expire_orders – created
    [info] >>> cron schedule [1 * * * *] oro:process:handle-trigger –id=14 –name=expire_quotes – created
    [info] >>> schedule modification persisted.

    Administration setup.
    Application URL (http://localhost):
    Organization name (ORO): ss

    In AbstractQuery.php line 796:

    No result was found for query although at least one row was expected.

    oro:organization:update [–organization-name [ORGANIZATION-NAME]] [–organization-description [ORGANIZATION-DESCRIPTION]] [–organization-enabled [ORGANIZATION-ENABLED]] [-h|–help] [-q|–quiet] [-v|vv|vvv|–verbose] [-V|–version] [–ansi] [–no-ansi] [-n|–no-interaction] [-e|–env ENV] [–no-debug] [–disabled-listeners DISABLED-LISTENERS] [–current-user CURRENT-USER] [–current-organization CURRENT-ORGANIZATION] [–] <command> <organization-name>

    The command ‘/usr/bin/php7.1’ ‘./bin/console’ ‘oro:organization:update’ ‘default’ ‘–organization-name=ss’ ‘–env=prod’ terminated with an exit code: 1.

    #37982

    fatnassi.s
    Participant

    Sorry , i’ve transmitted the worng terminal , am getting this when executing ./bin/console oro:migration:data:load –fixtures-type=demo –env=prod
    Loading “demo” data fixtures (as i saéid before, the app is already installed , and am trying to get the demo datas as second step:

    php ./bin/console oro:migration:data:load –fixtures-type=demo –env=prod
    Loading “demo” data fixtures …
    > loading Oro\Bundle\TranslationBundle\Migrations\Data\Demo\ORM\LoadLanguageDemoData
    > loading Oro\Bundle\CustomerBundle\Migrations\Data\Demo\ORM\LoadCustomerGroupDemoData
    > loading Oro\Bundle\CommerceMenuBundle\Migrations\Data\Demo\ORM\LoadFeaturedMenuData
    > loading Oro\Bundle\ProductBundle\Migrations\Data\Demo\ORM\LoadBrandDemoData
    > loading Oro\Bundle\ProductBundle\Migrations\Data\Demo\ORM\UpdateBrandAttributeConfig
    > loading Oro\Bundle\CatalogBundle\Migrations\Data\Demo\ORM\EnableAllProductsDemoData
    > loading Oro\Bundle\CustomerBundle\Migrations\Data\Demo\ORM\LoadCustomerInternalRatingDemoData
    > loading Oro\Bundle\PaymentTermBundle\Migrations\Data\Demo\ORM\LoadPaymentRuleIntegrationData
    > loading Oro\Bundle\DemoDataBundle\Migrations\Data\Demo\ORM\LoadLeadSourceData
    > loading Oro\Bundle\PaymentTermBundle\Migrations\Data\Demo\ORM\LoadPaymentTermDemoData
    > loading Oro\Bundle\PricingBundle\Migrations\Data\Demo\ORM\LoadPriceAttributePriceListDemoData
    > loading Oro\Bundle\PricingBundle\Migrations\Data\Demo\ORM\LoadPriceListDemoData
    > loading Oro\Bundle\CatalogBundle\Migrations\Data\Demo\ORM\EnablePreviouslyPurchasedFeature
    > loading Oro\Bundle\SaleBundle\Migrations\Data\Demo\ORM\LoadSalesContactInfoData
    > loading Oro\Bundle\ZendeskBundle\Migrations\Data\Demo\ORM\LoadTransportData
    > loading Oro\Bundle\ShippingBundle\Migrations\Data\Demo\ORM\LoadShippingOriginConfigurationDemoData
    > loading Oro\Bundle\CatalogBundle\Migrations\Data\Demo\ORM\LoadCategoryDemoData
    > loading Oro\Bundle\CMSBundle\Migrations\Data\Demo\ORM\LoadPageDemoData
    > loading Oro\Bundle\DemoDataBundle\Migrations\Data\Demo\ORM\LoadBusinessUnitData
    > loading Oro\Bundle\LocaleBundle\Migrations\Data\Demo\ORM\LoadLocalizationDemoData
    > loading Oro\Bundle\DemoDataBundle\Migrations\Data\Demo\ORM\LoadGroupData
    > loading Oro\Bundle\DemoDataBundle\Migrations\Data\Demo\ORM\LoadChannelData
    > loading Oro\Bundle\DemoDataBundle\Migrations\Data\Demo\ORM\LoadEmbeddedFormData
    > loading Oro\Bundle\DemoDataBundle\Migrations\Data\Demo\ORM\LoadReportData
    > loading Oro\Bundle\WebCatalogBundle\Migrations\Data\Demo\ORM\LoadSegmentsForWebCatalogDemoData
    > loading Oro\Bundle\WebCatalogBundle\Migrations\Data\Demo\ORM\LoadWebCatalogDemoData
    > loading Oro\Bundle\ProductBundle\Migrations\Data\Demo\ORM\LoadProductDemoData
    > loading Oro\Bundle\ProductBundle\Migrations\Data\Demo\ORM\LoadProductUnitPrecisionDemoData
    > loading Oro\Bundle\ProductBundle\Migrations\Data\Demo\ORM\LoadRelatedProductDemoData
    > loading Oro\Bundle\ProductBundle\Migrations\Data\Demo\ORM\LoadUpsellProductDemoData
    > loading Oro\Bundle\CatalogBundle\Migrations\Data\Demo\ORM\LoadProductCategoryDemoData
    > loading Oro\Bundle\CustomerBundle\Migrations\Data\Demo\ORM\LoadCustomerDemoData
    > loading Oro\Bundle\CustomerBundle\Migrations\Data\Demo\ORM\LoadScopeCustomerDemoData
    > loading Oro\Bundle\CustomerBundle\Migrations\Data\Demo\ORM\LoadScopeCustomerGroupDemoData
    > loading Oro\Bundle\VisibilityBundle\Migrations\Data\Demo\ORM\LoadCategoryVisibilityDemoData
    > loading Oro\Bundle\VisibilityBundle\Migrations\Data\Demo\ORM\LoadProductVisibilityDemoData
    > loading Oro\Bundle\PaymentTermBundle\Migrations\Data\Demo\ORM\LoadPaymentTermToAccountDemoData
    > loading Oro\Bundle\PaymentTermBundle\Migrations\Data\Demo\ORM\LoadPaymentTermToAccountGroupDemoData
    > loading Oro\Bundle\PricingBundle\Migrations\Data\Demo\ORM\LoadPriceAttributeProductPriceDemoData
    > loading Oro\Bundle\PricingBundle\Migrations\Data\Demo\ORM\LoadPriceListToCustomerGroupDemoData
    > loading Oro\Bundle\PricingBundle\Migrations\Data\Demo\ORM\LoadPriceListToWebsiteDemoData
    > loading Oro\Bundle\PricingBundle\Migrations\Data\Demo\ORM\LoadProductPriceDemoData
    > loading Oro\Bundle\TaxBundle\Migrations\Data\Demo\ORM\LoadTaxTableRatesDemoData
    > loading Oro\Bundle\AlternativeCheckoutBundle\Migrations\Data\Demo\ORM\UpdateAlternativeCheckoutWorkflowStatus

    In WorkflowScopeManager.php line 107:

    Workflow Scope configuration error: Cannot find entity “Oro\Bundle\CustomerBundle\Entity\Customer” w
    ith id “4”.

    oro:migration:data:load [–fixtures-type [FIXTURES-TYPE]] [–dry-run] [–bundles [BUNDLES]] [–exclude [EXCLUDE]] [-h|–help] [-q|–quiet] [-v|vv|vvv|–verbose] [-V|–version] [–ansi] [–no-ansi] [-n|–no-interaction] [-e|–env ENV] [–no-debug] [–disabled-listeners DISABLED-LISTENERS] [–current-user CURRENT-USER] [–current-organization CURRENT-ORGANIZATION] [–] <command>

    #37992
    Michael
    Michael
    Keymaster

    There is not enough information to say what had gone wrong, but based on the output of the console commands that you posted, it seems that either the initial installation has not finished completely, or one of the things you tried after the installation brought the application data to an inconsistent state.

    I suggest you simply reinstall the application again, and let installer add the sample data automatically
    during installation by supplying --sample-data=y option to bin/console oro:install command.

    #37995

    fatnassi.s
    Participant

    hellow,
    When trying to reinstall the same application again (with –sample-data=y) , am getting the same output.

    #37997
    Andrey Yatsenko
    Andrey Yatsenko
    Moderator

    Hi,
    Before reinstall, please clear the database, or better remove and create an empty one.
    The above issue could appear when you are using the database with nonstandard configuration for autoincrement, or when you are installing the application on the existing database that already contains some data.

    Actually, the above migration is not crucial for demo data, this is only used by alternative checkout workflow. To don’t waste time on reinstalling, you could comment “up” method in the “Oro\Bundle\AlternativeCheckoutBundle\Migrations\Data\Demo\ORM\UpdateAlternativeCheckoutWorkflowStatus” migration and run
    oro:migration:data:load –fixtures-type=demo –env=prod command again.
    The application will work properly since this workflow even not active by default.

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

You will be redirected to [title]. Would you like to continue?

Yes No