Raisers Edge 7 - Crashing frequently during export from query

Options
Cammi Derr
Cammi Derr
Ancient Membership 100 Comments 25 Likes Photogenic
in Blackbaud Raiser's Edge NXT®: General Discussion
Has anyone else (hosted) been having issue with RE7 crashing when exporting data from a query to a local drive?  I have noticed this frequently occuring for at least a month now and since it is so sporadic, I am not even sure how to pinpoint what might be causing the problem.
Tagged:

Comments

  • Heather MacKenzie
    Heather MacKenzie
    Tenth Anniversary 1,000 Likes 1000 Comments Photogenic

    I have not been experiencing that personally, but I wonder if it's related to something a teacher told me one time in an in-person BB class.  She said the reason that all the support people tell us to export everything through the export module instead of straight from a query is that the data can actually become corrupt when you export directly from the query.  She is the first one to explain it with the "why" attached to it to me.  She's actually seen it happen herself.  I have no real suggestions, but check out exporting through the export module instead.

     

  • Cammi Derr
    Cammi Derr
    Ancient Membership 100 Comments 25 Likes Photogenic

    Heather MacKenzie:

     

    I have not been experiencing that personally, but I wonder if it's related to something a teacher told me one time in an in-person BB class.  She said the reason that all the support people tell us to export everything through the export module instead of straight from a query is that the data can actually become corrupt when you export directly from the query.  She is the first one to explain it with the "why" attached to it to me.  She's actually seen it happen herself.  I have no real suggestions, but check out exporting through the export module instead.

     

     

    I have noticed in several exports from the module that my data is not always correct.  It's always good to check any data that comes out, but my issue is more directly related to the hardware performance for hosted users

  • Heather MacKenzie
    Heather MacKenzie
    Tenth Anniversary 1,000 Likes 1000 Comments Photogenic

    Well, shoot.  Sorry I couldn't be more helpful.  Best of luck figuring this out!

  • Tim Hendrickson
    Tim Hendrickson
    Tenth Anniversary 25 Likes 10 Comments Photogenic
    I've experienced this sporadically on our locally hosted system.  I never figured out what was causing it, but for a few weeks last year it was happening on every export after the first per login.  I ended up coming up with an alternate way of getting this data out of my queries, if I recall correctly it was either through a proper export or exporting a report's results to manipulate in Excel.  It still randomly crashes periodically when doing these for various projects, but with much less frequency and regularity.  Hopefully this either resolves itself for you or you're able to figure out what might be causing it.
     

  • Cammi Derr
    Cammi Derr
    Ancient Membership 100 Comments 25 Likes Photogenic

    Tim Hendrickson:

    I've experienced this sporadically on our locally hosted system.  I never figured out what was causing it, but for a few weeks last year it was happening on every export after the first per login.  I ended up coming up with an alternate way of getting this data out of my queries, if I recall correctly it was either through a proper export or exporting a report's results to manipulate in Excel.  It still randomly crashes periodically when doing these for various projects, but with much less frequency and regularity.  Hopefully this either resolves itself for you or you're able to figure out what might be causing it.

     

     

    Unfortunatly it still occurs occasionally, like today for an save to file in a query.  I'm not waiting for an actual RE export to complete.  It should only have about 659 records, but I have been waiting for it to complete for about 45 minutes.  The export task completion bar looks as if it's done, but the message on the export status has not popped up yet.  I experience this frequently in my exports.  And since the "cancel" option never actually cancels anything, I guess I will go ahead and crash my instance so that I can restart it.  I really hate to since I forgot to save my export prior to running it and now I will have to go back and select all the columns I needed again.  Grrr... This gets so old not having access to the actual tables.  :(

  • Sara Ruzicka 2
    Sara Ruzicka 2
    Eighth Anniversary First Comment Facilitator Level 1 Praiser Level 1

    Cammi Derr:

    Tim Hendrickson:

    I've experienced this sporadically on our locally hosted system.  I never figured out what was causing it, but for a few weeks last year it was happening on every export after the first per login.  I ended up coming up with an alternate way of getting this data out of my queries, if I recall correctly it was either through a proper export or exporting a report's results to manipulate in Excel.  It still randomly crashes periodically when doing these for various projects, but with much less frequency and regularity.  Hopefully this either resolves itself for you or you're able to figure out what might be causing it.

     

     

    Unfortunatly it still occurs occasionally, like today for an save to file in a query.  I'm not waiting for an actual RE export to complete.  It should only have about 659 records, but I have been waiting for it to complete for about 45 minutes.  The export task completion bar looks as if it's done, but the message on the export status has not popped up yet.  I experience this frequently in my exports.  And since the "cancel" option never actually cancels anything, I guess I will go ahead and crash my instance so that I can restart it.  I really hate to since I forgot to save my export prior to running it and now I will have to go back and select all the columns I needed again.  Grrr... This gets so old not having access to the actual tables.  :(

     

    We're locally hosted. At some point in 2017, Microsoft pushed out an update to Office (we're on 2016/365) that started causing export to crash if you were exporting xls, xlsx. I'm guessing, depending on the version of Office you're on, the update pushed out affected people at different times through out the year? I think I began experience problems around September or October.


    The workaround is to export to a CSV. You can either change the default file type within the export or build a new export.


    I could still export from a query with no issue as that defaults to CSV--I've never had an issue with this or it corrupting data. And since exporting to only CSV, I haven't had an export crash. The only issue is trying to remember to save as an xls so tabs or hidden columns aren't deleted when after you've saved and closed a CSV.

Categories