Forum Discussion
John21,
I haven't tried the option you have suggested but it seems like it might work. I'm unsure whether there is anything stored in the data file that might specify it's come from an environment where it is installed on a file server or whether this sort of configuration information in in the AccountRight Server install application.
Make sure you have at least one backup of the data file and I would suggest testing using a copy, not the original data file.
My reason for suggesting Windows Server 2016 should work is because two of the security ciphers required to successfully connect to pay-event-publisher.payroll.prod.myob.com via a TLSv1.2 connection were introduced by Microsoft in Windows Server 2016 and Windows 10 v1507. They are not present in earlier Windows Server or desktop versions.
Make sure you have the latest updates to Windows 10 to ensure it has the latest Root and Intermediate certificates installed in the operating system certificate store. The important Root certificate is named ISRG Root X1.
Testing whether a secure connection can be made to the above web site using a browser such as Firefox will not confirm the Windows operating system certificate store has the correct Root Certificate as Firefox has its own certificate store (and TLS code).
I'm not sure whether the Microsoft Edge browser is similar or whether it uses the operating system certificate store and TLS code (Schannel).
My understanding is AccountRIght v2022 uses the operating system certificate store and Schannel code.
Regards
Paul
Update - work around to lodge your existing STP reports. Note this will not fix the issue but will send past reports to ATO.
For those running data file on a local server and make sure no one is using MYOB at the time
1 - Copy the data file from your server to a local PC running Win10
2 - Rename the file (I added "STP" in the name)
3 - Open the file from that PC (using the library to add the file in your list)
4 - Login and go to Payroll Reporting and you should find all the unlodged STP reports
5 - You can test send by sending one of the files. If successful continue
6 - Restore the "STP" named file to the server.
7 - Rename the existing file to something like "pre STP fix"
8 - Rename the copied and restored file to your desired name
9 - Login as per normal to the file restored onto the server and you can send all the remaining STP files
Note - I state again you will still get the error next time you run payroll.
In summary the problem appears to be with Server version 2012 but not sure if we can fix it or need to update to 2016. Waiting on MYOB to advise further as the costs to update to 2016 or later are significant.
Short term fix and I guess you can repeat the process until all is fixed somehow
- John212 years agoExperienced User
Hi Steven,
In relation to STP2 - Myob advised us that we only need to place the file online for the setup and then we can return to our server. They provided instructions in regards to this. Please check before providing advice that may not be correct.
For various reasons many customers prefer to store their files locally rather than online. Personally if we are forced to go online then we will most likely change to another software package.
- IhateMYOBupgrad2 years agoExperienced Cover User
Thanks John
I tried this and when I went into payroll reporting the last 4 payruns weren't showing at all.
I've processed a nil payrun and now the previous payruns are showing but the nil isn't.
I've sucessfully sent the oldest payrun (doing them one at a time in order to hopefully reduce any EOY issues)
As painful as this is, it is at least a work around. Thank you for doing what MYOB haven't been able to do ie come up with a work around and advise people of it ChrisMYOB Tracey_H
- Julie-G2 years agoExperienced Cover User
Hi all
This message thread has been going for weeks now and MYOB Support is annoyingly very quiet.
All server edition users operating on a 2012 Server are now at the decision point of:
- do we go to the expense of doing a Server Upgrade now to at least a 2016 Server; or
- are we being forced online for STP2 from 1 Jan 2023 anyway, which makes the Server Upgrade financial commitment a complete waste of money for the sake of 2 months?
Can MYOB please confirm to all Server Users ASAP:
- STP2 will only ever be available for MYOB Accountright files kept Online
- as such, all server editions of MYOB Accountright will be obsolete from 31 Dec 2022?
This is imperative information to enable many MYOB users to make a financial decision that needs to be made right now.
Thank you
Julie
- John212 years agoExperienced User
Update again. I am now back in Oz and finding this easier to do:
1 - Copy the data file from your server to a local PC running Win10
2 - Rename the file (I added "STP" in the name)
3 - Open the file from that PC (using the library to add the file in your list)
4 - Login and go to Payroll Reporting and you should find all the unlodged STP reports
4A - If you dont find the unlodged reports then just do a xero pay for one employee. This should list them all.
5 - You can test send by sending one of the files. If successful continue and wait till all files show "accepted"
6 - Restore the "STP" named file to the server.
7 - Rename the existing file to something like "pre STP fix"
8 - Rename the copied and restored file to your desired name
9 - Login as per normal to the file restored onto the server and you can see all the files sent and run your YTD verification (to date) to reconcile your payroll.
- PRF2 years agoExperienced Cover User
John21,
Well done!
To me a solution seems quite straightfoward. MYOB can change the configuration of the web servers serving, at least, https://pay-event-publisher.payroll.prod.myob.com and https://stp.payroll.prod.myob.com to allow a couple of other ciphers to be used when establishing secure connections from the AccountRight application when using TLSv1.2.
https://cdn-stp.payroll.prod.myob.com already has a number of additional ciphers enabled for TLSv1.2. I 'm pretty certain at least two of these are supported by Windows 7SP1, 8, 8.1 and Windows Server 2012R2.
According to https://learn.microsoft.com/en-us/windows/win32/secauthn/cipher-suites-in-schannel, these are supported by Microsoft when an application passes the SCH_USE_STRONG_CRYPTO flag.
I'm not a security expert so there may well be good reasons for not enabling these additional ciphers. On the otherhand, they are already enabled on some of their web servers.
Regards
Paul
- Steven_M2 years agoFormer Staff
Hi Everyone
As has been indicated earlier on in this thread, the Payroll Reporting Centre is not loading/encountering a "Something went wrong at our end" message is something that we have reported to the required teams for further investigationA workaround, while we do investigate, is to ensure that your company file is stored online and to use the web browser interface. While this is not involved in the situation and related to it, it is worth mentioning that for Single Touch Payroll (STP v2) reporting you do need to store the company file online. The deadline for Single Touch Payroll v2 is 1st January 2023 - which is coming up quickly.
For users impacted we do recommend ensuring that you are on an updated Operating System such as Windows 8.1 or 10 - see System Requirements for more information. As we have seen a number of users impacted by this situation are on older Operating Systems which don't have the latest security certificates.
- Smooth2 years agoExperienced User
Hi Steven_M
From my own recent experience (and others that have contributed to this thread), we found that Windows 8.1 was part of the problem. After we upgraded to Windows 10 the problem was resolved.
Maybe you should re-consider your recommendation about using Windows 8.1?
- PRF2 years agoExperienced Cover User
It's confusing when there isn't consistent information about whether the shift to AccountRIght online mode for STP2 on 1/1/23 is compulsory or whether it is possible to remain using offline mode somehow.
Thank you for the information. Is there a link to the information MYOB provided you about the installation step requiring online mode but the actual day to day usage can be offline?
Regards
Paul
- John212 years agoExperienced User
Hi Paul,
On the 8th April when I investigated updating for STP2 I logged a call with MYOB to discuss the requirement to move the file online.
At that time I was informed over the phone and the links provided to me that the online transfer was temporary.
Since then MYOB paused the STP2 rollout and when it recommenced it looks like they have changed their minds about us retaining a local file and are forcing us online by 1/1/2023.
All my links have been updated (wish I kept a copy) and now all I see is the below. Forcing us to go online is "better" - how?