Unable to open recently upgraded company file
Hi Everyone Products: AccountRight 2020.2 and later - offline company files Got a question about using the below tool? There is a second post on this thread that does answer commonly asked questions - scroll down to see that post or click here. We have seen a number of cases of offline company files that, following an AccountRight upgrade, are not opening or closing unexpectedly or generating a Something has gone wrong message. This article contains information on identifying if you are impacted and running the necessary tool required to repair that file to allow it to be opened: How do you determine you are impacted? Following an AccountRight upgrade, if you are not able to open an offline company file, or you are encountering a Something has gone wrong message. Do check out the diagnostic file for the application - this can be opened in NotePad or another similar application. If you are needing to run the following tool, thatdiagnostic file would contain traces of the wording "InvalidFingerPrint" Example line in diagnostic file would: MYOB.Huxley.UI.Decorators.DecoratorFaultProcessor,Error,1,Unhandled error. : MYOB.Huxley.API.HuxleyActivationException: (InvalidFingerprint): Running the Tool: If you do see cases of "InvalidFingerprint" in that diagnostic file, do look at completing the following steps: Close AcountRight Download the following tool: AccountRight Hotfix tool Having trouble accessing the download? Right-click and select Save Link as Navigate to where you have saved that file - typically the Downloads folder on your computer Find the Hotfix tool zipped file (Data Hotfix - Invalid Fingerprint error - AccountRight 2020.2.zip) and select to extract the data - typically right-click and Extract All... Once extracted, select to run the AccountRight_Hotfix.exe file. This will open the tool: Please note that depending on your IT setup you may need to be logged on as the Windows Administrator. Browse to the impacted file and select Open once located Indicate that you have a backup of the file and then Apply. Should you be successful you would encounter the following message: Once you have that message, close the tool and open the file in AccountRight as per normal. Note: You may be prompted to re-confirm upon opening but this can be done online using the Confirm Online function.AccountRight Timeout Extender
Please Read This Before Continuing: The Timeout Extender is simply entering a value into AccountRight's Configuration File and is only to be used if you are experiencing Timeout-based errors such as "Application Operation Timeout" or if it's at the request of MYOB Support. As this does involve modifying a key configuration file for the software on your computer we strongly recommendthat you get an IT Professional to assist you if you are unfamiliar with modifying these types of files. Any incorrectly configured files may cause AccountRight to crash further or simply not open at all. If the software begins to crash after a change was made to the config file we would ask you to either return the copy of the config file made, or uninstall and reinstall, then seek assistance from an IT Professional to continue further. Do note that these configuration files are specific to each computer & version, if you install the next version of AccountRight this configuration won't be brought across. If you are experiencing problems that require the Timeout Extender to be in place you will need to set this on each computer, and version, that you are using. Please note: That there are 9 steps in this process. If you are only seeing 4-5 steps, do refresh the page. 201X.X refers to the version of AccountRight you are using, not an actual folder named 201X.X Close out of AccountRight. LocateHuxley.Application.exe.config file. You can find this by right clicking the AccountRight icon on your desktop and choosing "Open File Location" to bring up the same folder. Select the fileHuxley.Application.exe.config, and make a copy of the config file before continuing, as incorrect changes can prevent AccountRight from opening Right click the config file, select copy. Then deselect the file, right click and choose paste. This will create a copy. We now need to modify theoriginal config filecalledHuxley.Application.exe.config. You will need to right-click and chooseopen, editoropen with. If open with, select the program notepad to open the file, as in the screenshots below. Once opened in Notepad find the<appSettings>section. (use search by pressingF3orCTRL + F, and search for<appSettings>) On the<add key="UserSessionTimeout" value="60"/>line, change the value to3600. Thisnumber is inseconds, and we want to extend the timeout to 60minutes. Next, add the line<add key="TransactionTimeoutMinutes" value="60"/>to the bottom of theappSettingslist as seen in this example: Once the setting have been updated, save it by going to File > Save. Then close notepad. Open AccountRight as normal. The new timeout session will now take affect. That should extend the timeout period for you and allow you to record transactions with large amounts of data. If you are getting any errors directly after saving this, delete the config file you edited and then rename the copy you made earlier to be: Huxley.Application.exe.config It may also be worth ensuring your AccountRight Files & folders are excluded from Real-time Virus Scans and also any automatically scheduled programs like auto-backups. You can find the relevant File & Folder paths in this support note: Speed and performance tips If the Timeout Extender is applied and you are still experiencing errors, please fetch the AccountRight Diagnostic Log and Start a New Post so that we can look into it. In the post please include: The Exact error that comes up The steps you are following to get to the error What you're trying to achieve in the softwareLodging your Business Activity Statement (BAS) or Income Activity Statement (IAS)
Hi everyone Australian businesses that are registered for GST or have employees need to regularly lodge activity statements, Business Activity Statement (BAS) or Income Activity Statement (IAS),with the ATO that contain GST, PAYG and other business information. If your turnover is less than $10 million you'll be eligible to lodge your BAS using Simpler BAS. This means that fewer GST fields will need to filled and you won't need to use as many Tax Codes. For more information on Simpler BAS please refer to the ATO website. Online lodgement From AccountRight 2016.3 onwards, if your company file is online you can lodge your BAS and IAS straight from your software. These help articles will guide you through setting up and lodging your activitystatements online: Get ready to lodge activity statements online Simpler BAS reporting Prepare your activity statement online Recording your ATO payment or refund BAS not reconciling with your AccountRight reports? The first thing to try is refreshing the online BAS statement by clicking on Update from ledger. If you've made any changes to the tax codes set up you will need to update the ledger for those changesto affect the current statement. If this doesn't resolve your issue, check the tax codes setup by opening the online statement, click on Settings and select Set up activity statement fields. Make sure that all applicable tax codes have been selected. Manual lodgement Your other option for lodging your BAS in AccountRight is manual lodgement. These help articles have detailed information on using BASlink: Prepare your activity statement manually BASlink FAQs Pay Liabilities and BASlink We hope you find this useful. As always, if you do need help please start a new post. Our team of MYOB technical support staff and the generous MYOB Community is always happy to help.Using Bank feeds
Hi Everyone Automatic bank feeds can be used for a variety of purposes in the day to day processing, some of them being easy transaction entry, getting updated banking information, and most commonly as a tool for reconciliation Once you have set up your Bank feeds these transactions will flow through to your MYOB Software available for you to action that transaction. There are two main actions that can be taken with a bank feed transaction; Match or Allocate Matchis when you have already recorded the bank transaction in your MYOB Software and you are looking at matching that bank transaction to that transaction. Click on the Find option next to the associated transaction, enter the desired search criteria if required, choose the already recorded transaction, and then select Match & approve The following links can be referred to understand the process: How matching works Approving a bank feed Matching a bank feed to multiple transactions Select the drop arrow to the right of the transaction, selecting Match transaction, and choose the desired transaction(s) before selecting Save. For more information on matching check out the following Help Articles and Forum posts: Matching bank transactions Matching multiple bank transactions to one payroll transaction. Allocateis used when you have yet to record that transaction in MYOB Software. In the Bank Feeds window, select an unmatched bank feed transaction, clickNewandselect the type of transaction you want to create, then match & approve. Click onAllocate Meand select the account against which you want to record the withdrawal or deposit. Allocating bank transactionsexplains this in detail. Can't find the answer to your question here? Take a look atBank Feed FAQ'sAlternatively, do please start a new post. Our team of MYOB Support Moderators and the MYOB Community is always happy to help.AccountRight Log Locations
Product: AccountRight 2018 and above There are 4 main Log Files that MYOB Support might look into, these are: The Diagnostic Log - The is a background log file that keeps track of what the software is doing The Migration Log - This is the log is created when you upgrade from V19 to 2019 to keep track of errors The Import Log - The log created whenever you import data to keep track of what records had problems The Error Log - This log is created whenever you get a "Something's gone wrong" error These are found in different locations on the computer, it can help to have the Log ready before posting on the Forum to save any extra time later to post again when requested. Click the section below for the Locations and Filenames for those logs: AccountRight logs the basics on what you do, if there are any problems the software is designed to write all exceptions into the Diagnostic Log. This can be extremely helpful to figure out why the software is behaving the way it is. Location: %localappdata%\MYOB\AccountRight\<version>\Diagnostics\ Filename:Huxley.Application_2018.4.21.6219.log How to get to it: 1.Open your Start Menu 2. Type: %localappdata% 3. Open the %localappdata% folder: 4. Open the MYOB Folder. 5. Open the AccountRight Folder. 6. Open the Version folder (E.g: 2018.4) Note: AccountRight 2021.1 or later versions will show as Current. 7. Open the Diagnostics Folder. The Diagnostic Log file would look like: Huxley.Application_xxxx.log file to your Desktop to get to it easier. You can usetheChoose filebutton at the bottom of the editor when writing on the Forum to add files to your post. The Migration Log is created whenever an AccountRight Classic (v19 or below) has been upgraded to the new AccountRight offline. If there were any errors/warnings in the Migration, these will normally be written to the Migration Log for those that can read to log to read and figure out what might have happened. Location:%localappdata%\MYOB\AccountRight\<version> Filename:MigrationLog.txt How to get to it: 1.Open your Start Menu 2. Type: %localappdata% 3. Open the %localappdata% folder: 4. Open the MYOB Folder. 5. Open the AccountRight Folder. 6. Open the Version folder (E.g: 2018.4) Note: AccountRight 2021.1 or later versions will show as Current. An Import Log is normally made at the end of the Import process to capture the results of the import, any failures are listed with the Error Codes at the bottom and each record having a specific code if there are any failures. Location: %USERPROFILE%\Documents\MYOB\AccountRight Filename: importlog.txt You can read more on the Import Log on this help article:Import error log The Error Log is created when there is a problem that causes AccountRight to crash and throw the Something's gone wrong and AccountRight needs to close error. The software would normally collect the reason for the crash and write them to this Log to help those who can read the logs to figure out why the software crashed. Location:%USERPROFILE%\Documents\MYOB\AccountRight Filename: errorLog.txt This can normally be found under your Documents, in the MYOB folder:
