Forum Discussion
Hi MYOB
I have just spent hours with a client trying to solve this problem.
From my perspective the error appears to be associated with 2022.8 and a serial number for the company.
Here is my attempt to try to solve.
This client has 10 MYOB files but because I negotiated a contract price for them the 10 serial numbers for that contract is registered to me - but they remain owners (that is just fill in as I think this will be a problem if the client rings MYOB help - not withstanding the long wait and the 1000 questions they will be asked).
Of those 10 files - 2 are on line (because they run payroll) the 3rd - their main file is not online and is server based (but will be going online because of STP II) - but is connected to my 3rd party Job Costing which needs conversion to onliine access - due to be completed Nov 22). Again just fill in.
All their files are accessed via an RDP server with Server edition installed which now updates automatically.
Until Wed this week even though the server had updated to 2022.8 but they continued to use 2022.7
STP is still ver I.
They were able to access Payroll Reporting without problem - with their ownline files and their local file.
On Wednesday (coincidentally the client had a payroll question to do with fiures not balalncing with payroll and Payroll reporting) and at that stage they were still opening in 2022.7 but 2022.8 was installed.
I replied to the query - at at the same time asked them to use 2022.8 by selecting upgrade when they opened the file - this was done Wed afternoon - but since then - Payroll Reporting comes up with - "oops something went wrong".
Because payroll reporting is highly user specific I cannot open and check this with my logon.
So I logged onto their server as adminstrator - local file opened in 2022.8 and logged in as the payroll person and then with her on the phone she gave me her myob payroll logon credentials - and ther same error "oops something went wrong"
I then opened the online file from my own server (that I run my own company files from) - from which PAyroll reporting is STP II - and all works fine in 2022.8 with my company files.
I opened my clients ownline file using her logon and again her payroll reporting credentials "oops something has gone wrong".
And lastly (but I don't think this will work anyway (as I think the online ATO STP access uses tokens and an old file rolled back will cause an error) but I found a backup of the online file from Monday - restored it locally - opened it in 2022.7 - tried Payroll reporting "oops something happened".
I am out of options MYOB - but suspect it is 2022.8 somehow perhaps not using the correct tokens - but we cannot roll back as the ATO Payroll reporting is token and age controlled.
Help MYOB - ringing help line will be a mindless exercise of wait and being asked a 100 different needless questions.
The Doc
Hi ChrisMYOB
We have installed MYOB on a local clients machine (as 2 files are in online) - they are able now to get to payroll reporting (they are on STP I) but have advised them to upgrade to STP II soonest.
The other file is server bound as it connects to a 3rd party API - and client has resisted until now getting online. 3rd party needs upgrading so cannot go online yet.
Typically they do all work in business on server.
I am going to see if I can get the server bound file operating via the network to the desktop - this may circumvent this server problem for payroll reporting.
All other 2020.8 features including the api work fine.
Intenet explorers, Chrome, Moxilla have all been updated.
I have uninstalled and re-installed MYOB 2022.8 onto server. Works fine.
But cannot NOW access payroll reporting for this server bound file.
Error log attached.
The Doc
- ChrisMYOB2 years agoFormer Staff
Hello Everyone
Our team is currently investigating the cause of this issue.
Can you please check the version of windows you are on, if it isn't up to date, can you please update and then try again? Please let me know what version you were on, the version you upgraded to, and if it still gives you the error.
As a current workaround, you are able to put your file online and then log in using the browser version at app.myob.com and process the pay run.- The_Doc2 years agoUltimate Partner
Hi ChrisMYOB
Will the rollout of 2022.9 due 12 Oct fix this problem.
The problem with these rollouts - unfortunately it is the new way - constant rollout of 'Fixes'and 'Updates' - 'New Features' - however, to be The Devil's Advocate - the new features and fixes come with more problems than they fix.
I have just received notification of 2022.9 rollout for 12 Oct but there is no mention of fixing 'this problem'
I have no doubt that the problem is related to the Windows version - and updating desktop versions of Windows to at least Windows 10 is probably well worth it due to a whole lot of security considerations - but it is a whole lot more of a bigger problem to then try and force a big proportion of business users who are running on Server systems as old as Win 2012 R2 - a very very stable platform - or Win server 2016 - to now suddenly upgrade everything or get online.
Upgrading a desktop is not a big issue but upgrading an entire network server system is big bucks, big time worries and a whole lot of worry for a business - just because a single software package won't work on it!!!
Sounds like the proverb of a certain religious figure forcing a mountain to come to him for a meeting.
Grrr MYOB - please tell us you are fixing this problem - then we will undoubtedly bust our boilers to get our clients off the server and online for STP II.
The Doc
- Steven_M2 years agoFormer Staff
Hi The_Doc
As you have indicated we are working on AccountRight 2022.9 which will be released later this month. At this stage, we don't have any additional information that we can supply as to whether we would be able to include a fix for this particular situation in that release. However, as has been mentioned, this is something that our teams are aware of and are investigating.
Early indication does seem to indicate that the error does impact users in different ways based on their environment. As such we are asking for users to confirm that they are on a supported Operating System like Windows 8.1 or 10 so we can feed that information to our products team to help diagnose the situation.
- Rhianna2 years agoContributing Cover User
Hello,
Is this an issue with 2022.8? My computer is running Windows 10 Pro Version 10.0.19044 Build 19044 and all updates have been done.
Any assistance that can be provided would be greatly appreciated as we are about to process our third pay run that is yet to be delcared to the ATO.
Regards
- Julie-G2 years agoExperienced Cover User
We are having the same issue using Server Edition, not online files. We have two files not lodged, and not even showing in the Payroll Reporting Centre even though they are processed.
This must be an issue with 2022.8, but it is not feasible to load the file online to lodge these STP reports.
Hopefully MYOB comes up with a fix.
Thank you
- NardiaPlumbing2 years agoExperienced Cover User
Hi Chris
I have just updated to the STP Phase 2. Now when I access the Payroll Reporting centre via MYOB on the server it takes me straight to the web browser and I completed the required information there. I take it from that, this has to do with STP Phase 2 and the need to update our myobs immediately to STP Phase 2 or the error message will continue. All seems to be ok with us now.
- Lmcstack2 years agoExperienced User
Hi there,
As a work around we are accessing the MYOB files for both our companies online in order to submit the STP reports, but am I right in saying this issue is yet to be resolved from MYOB?
Also, since the most recent upgrade 2022.9 we are users on the server are now experiencing issues emailing sales invoices through Outlook. It seems to work for a period of time and then we get the following error:
Windows Security
Huxley.Application
connecting to xxx@buildingimpressions.com.au
We have spoken to our IT people and they have advised the following:
"The print operation through MYOB has issues and keep crashing both MYOB and Outlook applications.
As mentioned earlier, Microsoft depreciated its Basic Authentication method, I assume this might be affecting some operations on the MYOB end. As we see, it is prompting for an Admin mailbox password for email authentication.
Please lodge a case with MYOB and loop us in on the ticket. I can work with MYOB to further fix the problem."Can someone please help??
Is this another server issue?
Regards
Lynne