A database error occurred while executing Stored Procedure “EDA_PUBLICATIONS_GETITEMSOFTYPE_83”












3















I have been trying to publish a Dynamic Component Presentation but for some reason it keeps on failing with the following error:



enter image description here



When I preview the same component in the CMS getting below error:




Execution Timeout Expired. The timeout period elapsed prior to
completion of the operation or the server is not responding. The wait
operation timed out




enter image description here










share|improve this question

























  • Can you run the sp_updatestats in CM database and then try again? also monitor is there any query running or taking longer to execute?

    – Velmurugan
    Feb 4 at 10:47













  • After running sp_updatestats in CM database publishing will work fine for one or two days after some days landing up again with same issue.

    – k951
    Feb 4 at 10:54











  • If that's the case, then you'll probably want to schedule this to run every 12 - 24 hours.

    – Jonathan Williams
    Feb 4 at 11:21











  • Are you up to date with hotfixes? You will find at least one hotfix relating to getitems SP's.

    – Dylan .. Mark Saunders
    Feb 4 at 11:44











  • We didn't go with any hotfixes for DB issue, if any hotfixes are available related to the above error please let me know

    – k951
    Feb 4 at 11:53
















3















I have been trying to publish a Dynamic Component Presentation but for some reason it keeps on failing with the following error:



enter image description here



When I preview the same component in the CMS getting below error:




Execution Timeout Expired. The timeout period elapsed prior to
completion of the operation or the server is not responding. The wait
operation timed out




enter image description here










share|improve this question

























  • Can you run the sp_updatestats in CM database and then try again? also monitor is there any query running or taking longer to execute?

    – Velmurugan
    Feb 4 at 10:47













  • After running sp_updatestats in CM database publishing will work fine for one or two days after some days landing up again with same issue.

    – k951
    Feb 4 at 10:54











  • If that's the case, then you'll probably want to schedule this to run every 12 - 24 hours.

    – Jonathan Williams
    Feb 4 at 11:21











  • Are you up to date with hotfixes? You will find at least one hotfix relating to getitems SP's.

    – Dylan .. Mark Saunders
    Feb 4 at 11:44











  • We didn't go with any hotfixes for DB issue, if any hotfixes are available related to the above error please let me know

    – k951
    Feb 4 at 11:53














3












3








3








I have been trying to publish a Dynamic Component Presentation but for some reason it keeps on failing with the following error:



enter image description here



When I preview the same component in the CMS getting below error:




Execution Timeout Expired. The timeout period elapsed prior to
completion of the operation or the server is not responding. The wait
operation timed out




enter image description here










share|improve this question
















I have been trying to publish a Dynamic Component Presentation but for some reason it keeps on failing with the following error:



enter image description here



When I preview the same component in the CMS getting below error:




Execution Timeout Expired. The timeout period elapsed prior to
completion of the operation or the server is not responding. The wait
operation timed out




enter image description here







publishing web8.5 database






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 4 at 10:44









Atila Sos

3,4122720




3,4122720










asked Feb 4 at 10:35









k951k951

1899




1899













  • Can you run the sp_updatestats in CM database and then try again? also monitor is there any query running or taking longer to execute?

    – Velmurugan
    Feb 4 at 10:47













  • After running sp_updatestats in CM database publishing will work fine for one or two days after some days landing up again with same issue.

    – k951
    Feb 4 at 10:54











  • If that's the case, then you'll probably want to schedule this to run every 12 - 24 hours.

    – Jonathan Williams
    Feb 4 at 11:21











  • Are you up to date with hotfixes? You will find at least one hotfix relating to getitems SP's.

    – Dylan .. Mark Saunders
    Feb 4 at 11:44











  • We didn't go with any hotfixes for DB issue, if any hotfixes are available related to the above error please let me know

    – k951
    Feb 4 at 11:53



















  • Can you run the sp_updatestats in CM database and then try again? also monitor is there any query running or taking longer to execute?

    – Velmurugan
    Feb 4 at 10:47













  • After running sp_updatestats in CM database publishing will work fine for one or two days after some days landing up again with same issue.

    – k951
    Feb 4 at 10:54











  • If that's the case, then you'll probably want to schedule this to run every 12 - 24 hours.

    – Jonathan Williams
    Feb 4 at 11:21











  • Are you up to date with hotfixes? You will find at least one hotfix relating to getitems SP's.

    – Dylan .. Mark Saunders
    Feb 4 at 11:44











  • We didn't go with any hotfixes for DB issue, if any hotfixes are available related to the above error please let me know

    – k951
    Feb 4 at 11:53

















Can you run the sp_updatestats in CM database and then try again? also monitor is there any query running or taking longer to execute?

– Velmurugan
Feb 4 at 10:47







Can you run the sp_updatestats in CM database and then try again? also monitor is there any query running or taking longer to execute?

– Velmurugan
Feb 4 at 10:47















After running sp_updatestats in CM database publishing will work fine for one or two days after some days landing up again with same issue.

– k951
Feb 4 at 10:54





After running sp_updatestats in CM database publishing will work fine for one or two days after some days landing up again with same issue.

– k951
Feb 4 at 10:54













If that's the case, then you'll probably want to schedule this to run every 12 - 24 hours.

– Jonathan Williams
Feb 4 at 11:21





If that's the case, then you'll probably want to schedule this to run every 12 - 24 hours.

– Jonathan Williams
Feb 4 at 11:21













Are you up to date with hotfixes? You will find at least one hotfix relating to getitems SP's.

– Dylan .. Mark Saunders
Feb 4 at 11:44





Are you up to date with hotfixes? You will find at least one hotfix relating to getitems SP's.

– Dylan .. Mark Saunders
Feb 4 at 11:44













We didn't go with any hotfixes for DB issue, if any hotfixes are available related to the above error please let me know

– k951
Feb 4 at 11:53





We didn't go with any hotfixes for DB issue, if any hotfixes are available related to the above error please let me know

– k951
Feb 4 at 11:53










3 Answers
3






active

oldest

votes


















6














This looks like a typical timeout issue and there are a lot of similar question on this topic. The first thing to check is whether you have regular database maintenance performed? If not, do one (and start doing it on a regular basis, if possible daily) and try again. Database maintenance (Tridion specific) described here.



You could increase the timeouts as described here, but in most cases that is just masking the problem.



Similar questions:




  • SDL Tridion 2011 GUI Performance for large components

  • How to remove the transaction time out error?

  • Unable to save Multimedia Component

  • Timeout Expired for DecommissionPublicationTarget Tridion 8.5






share|improve this answer































    1














    Timeout errors on a database pointing to lacking database maintenance, so first things I would recommend to look at is updating the database stats and rebuilding the indexes.



    Always make sure you do regular database maintenance or its performance will deteriorate over time.



    Ask your DBA team to schedule to run this sp_updatestats daily every 2hr or 3hr interval, Its'depends on your business how frequent CME used by the editor for content creation and editing.



    I hope it helps






    share|improve this answer































      1














      The components which were failing while publishing/previewing due to the database error was due to the Razor template which was taking more 90 to 200sec to execute that was causing the issue.



      To resolve the above issue:



      On the CMS and Publisher server went to the Programs > SDL Web > SDL Web Content Manager configuration in the Microsoft Windows Start menu.



      Navigate to the Timeout settings section



      In that we increased the timeout value from 50sec to 900sec for the Seconds before a timeout error is generated when executing a query.



      After increasing the timeout restarted COM+ and required services on both the server to ensure updated settings are used.



      With the above changes publishing was going smooth but it was taking more time at rendering phase and apart from these few more observations are:




      1. In the CMS DB when we checked the CPU usage was high sometimes it was reaching up to 99%.

      2. In the Publisher server when checked the Event Viewer in the application and server logs -> navigate to tridion when we are publishing template issues related components getting "n" no of warnings.


      After trying with multiple options we came to know that main culprit is "Razor Template".



      In the razor template we are calling function called "GetTemplateId("CPTest_CT") which was causing the issue.



      To resolve this issue as per time being wherever they are calling GetTemplateId passing the hardcoded id of component template. After doing this changes all the above issues got resolved.



      I'm explaining in detail if next time anyone encounter this issue it may help.



      enter image description here



      enter image description here






      share|improve this answer

























        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "485"
        };
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function() {
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled) {
        StackExchange.using("snippets", function() {
        createEditor();
        });
        }
        else {
        createEditor();
        }
        });

        function createEditor() {
        StackExchange.prepareEditor({
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: false,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        imageUploader: {
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        },
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19760%2fa-database-error-occurred-while-executing-stored-procedure-eda-publications-get%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        6














        This looks like a typical timeout issue and there are a lot of similar question on this topic. The first thing to check is whether you have regular database maintenance performed? If not, do one (and start doing it on a regular basis, if possible daily) and try again. Database maintenance (Tridion specific) described here.



        You could increase the timeouts as described here, but in most cases that is just masking the problem.



        Similar questions:




        • SDL Tridion 2011 GUI Performance for large components

        • How to remove the transaction time out error?

        • Unable to save Multimedia Component

        • Timeout Expired for DecommissionPublicationTarget Tridion 8.5






        share|improve this answer




























          6














          This looks like a typical timeout issue and there are a lot of similar question on this topic. The first thing to check is whether you have regular database maintenance performed? If not, do one (and start doing it on a regular basis, if possible daily) and try again. Database maintenance (Tridion specific) described here.



          You could increase the timeouts as described here, but in most cases that is just masking the problem.



          Similar questions:




          • SDL Tridion 2011 GUI Performance for large components

          • How to remove the transaction time out error?

          • Unable to save Multimedia Component

          • Timeout Expired for DecommissionPublicationTarget Tridion 8.5






          share|improve this answer


























            6












            6








            6







            This looks like a typical timeout issue and there are a lot of similar question on this topic. The first thing to check is whether you have regular database maintenance performed? If not, do one (and start doing it on a regular basis, if possible daily) and try again. Database maintenance (Tridion specific) described here.



            You could increase the timeouts as described here, but in most cases that is just masking the problem.



            Similar questions:




            • SDL Tridion 2011 GUI Performance for large components

            • How to remove the transaction time out error?

            • Unable to save Multimedia Component

            • Timeout Expired for DecommissionPublicationTarget Tridion 8.5






            share|improve this answer













            This looks like a typical timeout issue and there are a lot of similar question on this topic. The first thing to check is whether you have regular database maintenance performed? If not, do one (and start doing it on a regular basis, if possible daily) and try again. Database maintenance (Tridion specific) described here.



            You could increase the timeouts as described here, but in most cases that is just masking the problem.



            Similar questions:




            • SDL Tridion 2011 GUI Performance for large components

            • How to remove the transaction time out error?

            • Unable to save Multimedia Component

            • Timeout Expired for DecommissionPublicationTarget Tridion 8.5







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Feb 4 at 11:00









            Atila SosAtila Sos

            3,4122720




            3,4122720























                1














                Timeout errors on a database pointing to lacking database maintenance, so first things I would recommend to look at is updating the database stats and rebuilding the indexes.



                Always make sure you do regular database maintenance or its performance will deteriorate over time.



                Ask your DBA team to schedule to run this sp_updatestats daily every 2hr or 3hr interval, Its'depends on your business how frequent CME used by the editor for content creation and editing.



                I hope it helps






                share|improve this answer




























                  1














                  Timeout errors on a database pointing to lacking database maintenance, so first things I would recommend to look at is updating the database stats and rebuilding the indexes.



                  Always make sure you do regular database maintenance or its performance will deteriorate over time.



                  Ask your DBA team to schedule to run this sp_updatestats daily every 2hr or 3hr interval, Its'depends on your business how frequent CME used by the editor for content creation and editing.



                  I hope it helps






                  share|improve this answer


























                    1












                    1








                    1







                    Timeout errors on a database pointing to lacking database maintenance, so first things I would recommend to look at is updating the database stats and rebuilding the indexes.



                    Always make sure you do regular database maintenance or its performance will deteriorate over time.



                    Ask your DBA team to schedule to run this sp_updatestats daily every 2hr or 3hr interval, Its'depends on your business how frequent CME used by the editor for content creation and editing.



                    I hope it helps






                    share|improve this answer













                    Timeout errors on a database pointing to lacking database maintenance, so first things I would recommend to look at is updating the database stats and rebuilding the indexes.



                    Always make sure you do regular database maintenance or its performance will deteriorate over time.



                    Ask your DBA team to schedule to run this sp_updatestats daily every 2hr or 3hr interval, Its'depends on your business how frequent CME used by the editor for content creation and editing.



                    I hope it helps







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Feb 4 at 11:05









                    VelmuruganVelmurugan

                    3,822718




                    3,822718























                        1














                        The components which were failing while publishing/previewing due to the database error was due to the Razor template which was taking more 90 to 200sec to execute that was causing the issue.



                        To resolve the above issue:



                        On the CMS and Publisher server went to the Programs > SDL Web > SDL Web Content Manager configuration in the Microsoft Windows Start menu.



                        Navigate to the Timeout settings section



                        In that we increased the timeout value from 50sec to 900sec for the Seconds before a timeout error is generated when executing a query.



                        After increasing the timeout restarted COM+ and required services on both the server to ensure updated settings are used.



                        With the above changes publishing was going smooth but it was taking more time at rendering phase and apart from these few more observations are:




                        1. In the CMS DB when we checked the CPU usage was high sometimes it was reaching up to 99%.

                        2. In the Publisher server when checked the Event Viewer in the application and server logs -> navigate to tridion when we are publishing template issues related components getting "n" no of warnings.


                        After trying with multiple options we came to know that main culprit is "Razor Template".



                        In the razor template we are calling function called "GetTemplateId("CPTest_CT") which was causing the issue.



                        To resolve this issue as per time being wherever they are calling GetTemplateId passing the hardcoded id of component template. After doing this changes all the above issues got resolved.



                        I'm explaining in detail if next time anyone encounter this issue it may help.



                        enter image description here



                        enter image description here






                        share|improve this answer






























                          1














                          The components which were failing while publishing/previewing due to the database error was due to the Razor template which was taking more 90 to 200sec to execute that was causing the issue.



                          To resolve the above issue:



                          On the CMS and Publisher server went to the Programs > SDL Web > SDL Web Content Manager configuration in the Microsoft Windows Start menu.



                          Navigate to the Timeout settings section



                          In that we increased the timeout value from 50sec to 900sec for the Seconds before a timeout error is generated when executing a query.



                          After increasing the timeout restarted COM+ and required services on both the server to ensure updated settings are used.



                          With the above changes publishing was going smooth but it was taking more time at rendering phase and apart from these few more observations are:




                          1. In the CMS DB when we checked the CPU usage was high sometimes it was reaching up to 99%.

                          2. In the Publisher server when checked the Event Viewer in the application and server logs -> navigate to tridion when we are publishing template issues related components getting "n" no of warnings.


                          After trying with multiple options we came to know that main culprit is "Razor Template".



                          In the razor template we are calling function called "GetTemplateId("CPTest_CT") which was causing the issue.



                          To resolve this issue as per time being wherever they are calling GetTemplateId passing the hardcoded id of component template. After doing this changes all the above issues got resolved.



                          I'm explaining in detail if next time anyone encounter this issue it may help.



                          enter image description here



                          enter image description here






                          share|improve this answer




























                            1












                            1








                            1







                            The components which were failing while publishing/previewing due to the database error was due to the Razor template which was taking more 90 to 200sec to execute that was causing the issue.



                            To resolve the above issue:



                            On the CMS and Publisher server went to the Programs > SDL Web > SDL Web Content Manager configuration in the Microsoft Windows Start menu.



                            Navigate to the Timeout settings section



                            In that we increased the timeout value from 50sec to 900sec for the Seconds before a timeout error is generated when executing a query.



                            After increasing the timeout restarted COM+ and required services on both the server to ensure updated settings are used.



                            With the above changes publishing was going smooth but it was taking more time at rendering phase and apart from these few more observations are:




                            1. In the CMS DB when we checked the CPU usage was high sometimes it was reaching up to 99%.

                            2. In the Publisher server when checked the Event Viewer in the application and server logs -> navigate to tridion when we are publishing template issues related components getting "n" no of warnings.


                            After trying with multiple options we came to know that main culprit is "Razor Template".



                            In the razor template we are calling function called "GetTemplateId("CPTest_CT") which was causing the issue.



                            To resolve this issue as per time being wherever they are calling GetTemplateId passing the hardcoded id of component template. After doing this changes all the above issues got resolved.



                            I'm explaining in detail if next time anyone encounter this issue it may help.



                            enter image description here



                            enter image description here






                            share|improve this answer















                            The components which were failing while publishing/previewing due to the database error was due to the Razor template which was taking more 90 to 200sec to execute that was causing the issue.



                            To resolve the above issue:



                            On the CMS and Publisher server went to the Programs > SDL Web > SDL Web Content Manager configuration in the Microsoft Windows Start menu.



                            Navigate to the Timeout settings section



                            In that we increased the timeout value from 50sec to 900sec for the Seconds before a timeout error is generated when executing a query.



                            After increasing the timeout restarted COM+ and required services on both the server to ensure updated settings are used.



                            With the above changes publishing was going smooth but it was taking more time at rendering phase and apart from these few more observations are:




                            1. In the CMS DB when we checked the CPU usage was high sometimes it was reaching up to 99%.

                            2. In the Publisher server when checked the Event Viewer in the application and server logs -> navigate to tridion when we are publishing template issues related components getting "n" no of warnings.


                            After trying with multiple options we came to know that main culprit is "Razor Template".



                            In the razor template we are calling function called "GetTemplateId("CPTest_CT") which was causing the issue.



                            To resolve this issue as per time being wherever they are calling GetTemplateId passing the hardcoded id of component template. After doing this changes all the above issues got resolved.



                            I'm explaining in detail if next time anyone encounter this issue it may help.



                            enter image description here



                            enter image description here







                            share|improve this answer














                            share|improve this answer



                            share|improve this answer








                            edited Feb 14 at 5:03

























                            answered Feb 11 at 5:43









                            k951k951

                            1899




                            1899






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Tridion Stack Exchange!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid



                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.


                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19760%2fa-database-error-occurred-while-executing-stored-procedure-eda-publications-get%23new-answer', 'question_page');
                                }
                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                Human spaceflight

                                Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

                                張江高科駅