Forum Discussion

Leeann69's avatar
6 years ago

Can MYBO get full?

We are having issues scanning documents to our AO clients accounts and they aren't showing up in AO - have tried several times.  Is this a IT issue, Printer issue - can MYOB get full and need to delete some files eg. 2011 and before (I assume you still have to keep files for 7 years?)

  • Hi Leeann69.,

     

    Thanks for your post and welcome to the MYOB Community!  we hope you find it a great resource!

     

    Let me apologise for the delay - our support teams have been inunndated with calls due to lodgement deadlines and the leadup to the new tax year.

     

    The short answer to your questions is no - MYOB AO Cannot get full.  However, there are a number of limitations that can cause issues when you have a large amount of data in your Database, or on your Document Manager FileStore.

     

    Having said that, we have yet to see an MYOB AO client ever get close to the limits imposed by Microsoft SQL Server Express (which AO uses).

     

    Note that Document Manager does not store the actual documents you are adding for clients in the Database - these are actually stored on disk in the DM FileStore (which is a location on your network) - so it is possible, if you cannot add any Documents to DM that the filestore location is full - but you should be seeing an error about that.

     

    If you can sometimes add documents, and other times you cant, then we would expect you to see some form of error when you attempt to add the document.

     

     

    So, that brings us to the questions - this will help us to get to the bottom of the cause :

     

    • Does this occur for every user or only a single user?
    • Does this occur only from a single workstation, or from multiple?
    • What is the exact error that occurs when you attempt to add the document?
    • What steps are being taken to add the document?
    • When did the problems start occuring?
    • Does this occur for every single document type? or only one?
    • What method are you using to scan the documents, to be added to Document Manager?

    Feel free to respond with the above info, and we can help you troubleshoot what is causing this.

     

     

  • Hi Leeann69.,

     

    Thanks for your post and welcome to the MYOB Community!  we hope you find it a great resource!

     

    Let me apologise for the delay - our support teams have been inunndated with calls due to lodgement deadlines and the leadup to the new tax year.

     

    The short answer to your questions is no - MYOB AO Cannot get full.  However, there are a number of limitations that can cause issues when you have a large amount of data in your Database, or on your Document Manager FileStore.

     

    Having said that, we have yet to see an MYOB AO client ever get close to the limits imposed by Microsoft SQL Server Express (which AO uses).

     

    Note that Document Manager does not store the actual documents you are adding for clients in the Database - these are actually stored on disk in the DM FileStore (which is a location on your network) - so it is possible, if you cannot add any Documents to DM that the filestore location is full - but you should be seeing an error about that.

     

    If you can sometimes add documents, and other times you cant, then we would expect you to see some form of error when you attempt to add the document.

     

     

    So, that brings us to the questions - this will help us to get to the bottom of the cause :

     

    • Does this occur for every user or only a single user?
    • Does this occur only from a single workstation, or from multiple?
    • What is the exact error that occurs when you attempt to add the document?
    • What steps are being taken to add the document?
    • When did the problems start occuring?
    • Does this occur for every single document type? or only one?
    • What method are you using to scan the documents, to be added to Document Manager?

    Feel free to respond with the above info, and we can help you troubleshoot what is causing this.