Home Quicken for Mac Errors and Troubleshooting (Mac)

Quicken for Mac 2017 Version 4.5.6 Hangs

2»

Comments

  • Unknown Member
    edited June 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    Hey Marcus, Will you be releasing an update for the App Store that gives us information about this?

    It would be good to call this out at the very top of the App Store update message.
  • Unknown Member
    edited June 2017

    Thanks to everyone reporting this issue in the forum and sending us in-product Report a Problem reports.  Because of your efforts, we've been investigating the issue since this morning and I think we've figured out what's happening.  We believe this is affecting only App Store customers that have set up a custom backup folder.  Basically, the App Store version of Quicken doesn't allow one to write to a backup folder outside of the sandbox container in our implementation and we always make a backup of your file before migrating to the new format.  Because we can't create a backup, we don't open the file.  We're still doing testing to make sure this is the issue but this is what we think is happening at this time.  I'll keep everyone posted as we learn more.

    I'm in the same boat. Have the issue, but bought from quicken. I hope quicken will be fixing this for us.
  • Randall GodfreyRandall Godfrey Member ✭✭
    edited June 2017

    Thanks to everyone reporting this issue in the forum and sending us in-product Report a Problem reports.  Because of your efforts, we've been investigating the issue since this morning and I think we've figured out what's happening.  We believe this is affecting only App Store customers that have set up a custom backup folder.  Basically, the App Store version of Quicken doesn't allow one to write to a backup folder outside of the sandbox container in our implementation and we always make a backup of your file before migrating to the new format.  Because we can't create a backup, we don't open the file.  We're still doing testing to make sure this is the issue but this is what we think is happening at this time.  I'll keep everyone posted as we learn more.

    I didn't have the App Store version either, but I let QM decide where it was going to keep its files instead of changing the defaults. 4.5.6 does open a little slower than 4.5.4 did, seconds not minutes, but it's not annoying.
  • Quicken MarcusQuicken Marcus Employee ✭✭✭✭
    edited June 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    Even better.  We have fixed this in the app store version 4.5.7.  We released this morning.
  • Quicken MarcusQuicken Marcus Employee ✭✭✭✭
    edited June 2017

    Thanks to everyone reporting this issue in the forum and sending us in-product Report a Problem reports.  Because of your efforts, we've been investigating the issue since this morning and I think we've figured out what's happening.  We believe this is affecting only App Store customers that have set up a custom backup folder.  Basically, the App Store version of Quicken doesn't allow one to write to a backup folder outside of the sandbox container in our implementation and we always make a backup of your file before migrating to the new format.  Because we can't create a backup, we don't open the file.  We're still doing testing to make sure this is the issue but this is what we think is happening at this time.  I'll keep everyone posted as we learn more.

    Steve, EY and Randall, have you tried the solution in https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc...?  If this doesn't fix the issue, then I'm not sure what is causing the issue you're seeing.  We will be shipping a version 4.5.8 probably tonight and tomorrow that incorporates the issues mentioned in the above link.  If this doesn't solve the issue, I'll reach out to you to see what we can figure out.  4.5.8 has fixes for all the things we're aware of.
  • Unknown Member
    edited June 2017

    Thanks to everyone reporting this issue in the forum and sending us in-product Report a Problem reports.  Because of your efforts, we've been investigating the issue since this morning and I think we've figured out what's happening.  We believe this is affecting only App Store customers that have set up a custom backup folder.  Basically, the App Store version of Quicken doesn't allow one to write to a backup folder outside of the sandbox container in our implementation and we always make a backup of your file before migrating to the new format.  Because we can't create a backup, we don't open the file.  We're still doing testing to make sure this is the issue but this is what we think is happening at this time.  I'll keep everyone posted as we learn more.

    Lets see. Last week 4.5.6.  Yesterday 4.5.7.  Tomorrow 4.5.8.

    Just saying. 
  • Unknown Member
    edited June 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    @Marcus, what about those of who bought directly from quicken and have this issue?
  • Unknown Member
    edited June 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    A couple weeks ago I upgraded to 4.5.6 and went 'dead-in-the-water' like so many others.  FINALLY, after multiple tries, uninstalled 4.5.6; and found 4.3.1 to reinstalled and got my file back. Keep getting popup ads for 4.5.6; but waiting for later version that hopefully fixes this.  Marcus, you say 4.5.7 is available but I can't find it.
  • Quicken MarcusQuicken Marcus Employee ✭✭✭✭
    edited June 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    Actually, we just shipped 4.5.8.  We held up 4.5.7 to pick up a crashing fix and then renamed it 4.5.8.  It has fixes for everything we're aware of.  If people continue to have issues, then I'll need to reach out to you directly so we can work together to figure out the issue.  
  • Unknown Member
    edited June 2017
    I purchased my 2017 version from Intuit (not Mac App store). I've been unable to open my data file after upgrading to 4.5.5, 4.5.6, 4.5.7 and now 4.5.8. App hangs on startup then I have to force quit and use Time Machine to go back to 4.5.4. I've tried all of the hacks from Intuit and users and even the RepairCorruptDatabase.app but still nothing works. My backup file used to reside in my Dropbox folder, but I have since moved it to the default location on my hard drive - same problem persists. I figured I'd go my account page on the Intuit site and re-download a fresh version of Q-17 and reinstall. However, my purchase from March 16 for Q-17 doesn't appear in the list of downloadable apps (all of my TurboTax purchases and Quicken purchases back to 2005 are listed and available for download, but not Q-17) I'm running a Mac Mini 2.5 GHz with OS 10.12.5
  • Unknown Member
    edited July 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    Hi. Once I try to open Quicken after upgrading to 4.5.8 (I have 4.5.4) it hangs and I have to force-quit and retrieve 4.5.4 from Time Machine. This has happened a number of times. I'm running 10.12.5.
  • Unknown Member
    edited July 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    You know what? Someone suggested that I leave the update run and don't force quit it. I did and it worked! I don't know why that is so. Normally, when it cycles and cycles and say it is not responding, I force quit it right away (habit, I guess). So, never mind.
  • Unknown Member
    edited July 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    Thanks for the tip Richard. I have had an impossible time upgrading from 4.5.4 and had the same issue where opening the file on the upgraded app, I would get the spinning beach ball and I would force quit when the app stopped responding and get 4.5.4 from Time Machine. After running the update (4.5.8) I still got the spinning beach ball, but after about 75 seconds, my Quicken file opened and seems to be working. I've quit and started the updated app several times without issue.
  • Unknown Member
    edited July 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    Glad I could help.
  • Unknown Member
    edited July 2017

    We've confirmed that anyone that has created a custom backup folder in the Mac App Store Version of Quicken will run into this issue.  The way we've implemented the backup feature doesn't work when using the Mac App Store version when trying to save outside of the Container folder on your Mac.  This is blocked by MacOS because of something called sandboxing.  It helps make using the app more secure since it doesn't let apps write files to anywhere on your machine without first explicitly getting approval from you.  This limitation doesn't exist for downloaded or retail versions of apps.  This is a bug that we need to fix.  

    If you've run into this issue, you will see an error message that looks like the following:
    image
    In the short term, the way to fix this is to go to quit Quicken first.  Then open Terminal and type the following:

    defaults delete com.quicken.Quicken.2017 BackupDirectoryPath
    This will revert your backup folder to the default location which does work.  Once you do this, you'll be able to open your file.  We'll make this easier in the next couple of days and will fix the core bug in a future update.

    We are aware of another issue while opening files which can be fixed using a script that we've created.  See https://getsatisfaction.com/quickencommunity/topics/resolution-quicken-mac-2017-4-5-4-fails-to-launc... for this solution.  

    Just to be clear, none of this is related to version 4.5.6 per se.  4.5.6 is NOT corrupting files.  The issue is that 4.5.6 needs to convert your current file to the new format which was changed because we added the new loan feature and when Quicken does this we make a backup copy of your file first, migrate your current database, and once we verify that it was done successfully, we delete the old database.  All of these issues are because Quicken can't complete that task for some reason.
    4.5.8 worked for me too so whatever was wrong with the 4.5.6 update seems to be fixed.
This discussion has been closed.