Clearing the AccountRight Cache
AccountRight caches some information that it loads so that it can be referred faster the next time it is needed. This also keeps hold of certain instructions used with reporting and some other operations with data entry or displaying information on the page. While this can make the operations faster the next time around there are times where this can become corrupted and cause odd behaviour in AccountRight such as missing information or incorrect information loading on some pages.A common troubleshooting step is to clear these cache files that AccountRight uses so that when you next open AccountRight it re-creates the cached information and can resolve some odd behaviour. Before continuing, please ensure that AccountRight is closed. Clearing the Cache while AccountRight is open may cause further unexpected behaviour. 1. Open your Start Menu 2. Start typing: %localappdata% 3. Open the %localappdata% folder when displayed: 4. Open the MYOB Folder 5. Open the AccountRight Folder. 6. Open the Version folder (E.g: 2019.2) Note: AccountRight 2021.1 or later versions will show as Current. 7. Open the Cache folder 8. Delete all files in this folder. Once these files are deleted, re-open AccountRight and try running the report, or performing the operation again.
Invalid Fingerprint Error
Hi Everyone Products: AccountRight 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 thediagnostic 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 AccountRight 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 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: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 softwarePayroll Activity Summary vs Payroll Register Summary report
Hi Everyone As it is the end of the payroll year we thought we do an overview of two key payroll reports that are great to use at the end of the payroll year. These can be used to ensure that you have the correct values ahead of preparing your payment summaries. If you go to Reports>>Payroll>>Employees you have two reports; Activity Summary and Register Summary. Both reports do appear identical but are drawing their information from two different locations. The Payroll Activity Summary report is looking at the actual Payroll transactions recorded in payroll, whereas the Payroll Register Summary report looks at the employee’s card – in particular, the Payroll History section of the Payroll Details tab. Ideally, both of these particular reports will match as the payroll transactions recorded will match up with the employee’s card. What if the Payroll Activity Summary and Register Summary reports don’t match? If these particular reports don’t match it is likely that the card history has been updated manually. To get them to match do follow the below instructions: Run the Activity Summary and Register summary on a per month basis, to narrow down the month(s) that the reports don’t match Once the month(s) have been determined where it doesn't balance, check the payroll transactions in those months to ensure that they have been recorded correctly When that has been checked navigate to the pay history section of the employee's card -Card File>>Cards Lists>>Employees>Select the relevant employee's card>>Payroll Details tab>>>Pay History (left-hand side) Select to Show pay historyfor that particular and overtype that value to be same as the payroll transaction recorded Rerun the relevant reports to ensure that they do match. Once you Activity Summary and Register Summary reports do match, you are in a great position to prepare your payment summaries.Print/Email Pay slips: Allow for PDF creation
Hi, I would like to have the ability to save a pay slip as a PDF as I do not send the payslip via email to employees from the MYOB platform. All payslips are saved to my CutePDF printer and emailed at a later time. Saving to the Cute PDF printer is time comsuming and fiddly. MYOB >> please enable this as you do with reports (export to PDF). anyone else have this issue? thanks Karen "Pay Slips as PDF's"
