Thank you for visiting our Partner Zone. This area is an exclusive space for MYOB Partners. Find out how to Partner with MYOB.
Thanks for letting us know how you got on with installing the update, and how you overcome the issues that came up. I am sure our other forum users will find it quite helpful and I have shared your post with the relevant teams for their information.
An update - it gets worse
The nightmare continues - my solution was a stop gap and not the whole picture.
The whole picture now that I have upgrade 2 more servers and putting on hold a 3rd.
I think my solution given above was a stop gap that just worked in those circumstances.
Since then - upgrade another client - a mess - had to roll back and luckily I could - uses API this was also stuffed up - and took a while to get the right version back up and running for the file 2020.2.1 file. Successfully rolled back to 2020.2.1 (1st version) - however - after roll back ability to set Library location with MYOB tool didn't work - had to go into registry and install registry key - then it worked
2nd server - our own in our business - upgraded success 1st time - had knowledge base
Here is the problem I think - MYOB this is really messy and you are going to get mud on your face over this.
Common advise from MYOB is a remote server acting as Terminal server (but NOT acting as file server) uses the .msi installer
If Server is to Serve up MYOB files across network to a peer to peer network running MYOB then it needs to have the SE version installed.
However, the msi version doesn't have all the payload for a 1st time user of MYOB installation i.e CE SQL Server and .Net components (I think this is true)
Traditionaly updates can be installed as standalone without removal of the previous version i.e 2019.4, 2020.1, 2020.2 (these could all be left running on the machine as separate programs), however the latest patch (2020.2.2) was different
1. the original release late May was 2020.2.1 (but relased and labelled 2020.2 on the web)
2. This installed as a separate install to the prior version - and on a server you could use the SE install or the .msi if not serving up the file (this difference was part of a previous cascade of posts). (read on this has a nasty twist)
3. The latest patch 2020.2.2 was not so labelled and was just put on the MYOB web in the place of 2020.2.1 but labelled as 2020.2 (that is very messy MYOB).
4. Further 2020.2.1 had to be uninstalled completely (a total change from previous updates)
5. And the patch 2020.2..2 had to be reinstalled but still showed as 2020.2
Problem if you didn't uninstall the prior version completely the new install scrambled to 'Set Location Library' service and it wont start
And to add the final 'gotyou' to the problem - SE installs uninstalled completely and without problem through Control Panel and Remove programs - faultlessly.
.msi installs will not - they just will not uninstall !!!!!!!!!!!!!!!
You get the message
"Only administrators have permission to add, remove, or configure server software during a Terminal services remote session. If you want to install or configure software on the server, contact your network administrator"
This message doesn't occur with an SE or for that matter any other TS installed software - and I have been a domain/network administrator for these servers for yonks - ONLY .msi MYOB installs
And there is the problem - can't move forward or backwards - all methods to turn of this message - registry hacks etc does not work.
So OK no problem install the update SE version - (you can force an install of the .msi patch) but it scrambles the Set Library Location
You can install the SE version - and the Library Locator service just will not start.
And so you roll back and uninstall the SE version of the patch - the system lets you uninstall - but now the Library Locator for 2020.2.1 doesn't work (though thank fully the service is working) - and you can place this key in Registry
key = LibraryRoot type REG_SZ data = C:\........ [=path to library]
and this works
However I am stuck in limbo as I now have to manually remove these programs through the command line to move forward.
If MYOB could release a command line program removal release that would definately help - but I have until 1 July to do this myself
MYOB this is oh so messy and client's just don't give you browny points for these messy rollouts of patches.
And for the record - they do not make me feel warm and cuddly about you.
Thanks for all your feedback, I’ve passed it onto the relevant teams for their consideration.
You are correct with regards to the msi installer being a bit more lightweight what the regular installer with regards to things like SQL server and the .net components. However it is noted in the msi installation instructions that these are prerequisites for the msi installer. I can understand that as you’ve done a few of these your well familiar with them and wouldn’t generally need to check them.
I can’t speak to the development of a command line removal release, as this may be something that the team consider in the future. However Im afraid Im unable to provide any sort of timeline as to when that may potentially be happening.
Thanks for the reply - I would be happy with Techs doing a rush job on just some instructions regarding removing eveything so a new install works. This would have to be a command line job but just list of everything that needs removal in Registry and the Server.
The problem is the Service Library Locator - it gets confused and will not start for SE even though it says it is running.
I have 2 clients stuck on 2020.2.1 unable to move forward (they are big clients with 10 and 9 MYOB files) and 1 client 2 servers and 15 plus users
I have a tech going to the site of 1 client - and am hoping a direct logon may enable uninstall but not counting on it as I tried a console logon as administrator (and I am a domain administrator) and that wouldn't budge them.
Am preparing for a friday night vigil to attempt command line removal as MYOB tech is open Sat morning but running out of time to 1 Jul
Regards The Doc
I’ve passed your comments on. I’m afraid I cant provide any sort of timeframe on this though.
Unfortunately I’m not able to provide much insight into why that service is both running and apparently not running at the same time as a result of the complexity of terminal servers. It could be that something is causing a disconnect between the front and back end, delaying or stopping the service from running as expected, however it’s a shot in the dark.
Thanks for your comments - I have no further insights.
We however tried a brutal program removal yesterday on a client's server to remove a program and that worked however, that didn't include the SE version which has the service running.
We have a virtual full 2019 server (sandboxed) for testing viruses and it reboots every night at 4 AM back to an original build - so I can do anything in this to test installs and services - I will see if I can emulate the problem I have and will come back to you with an update - if I have any.
A further update and this is getting real messy.
I got local IT person to come in to clients Server 2016 and uninstall ALL old MYOB programs and APIs
I then decided to install the SE version not the MSI version (even though I was not serving to another computer).
Installation was straight forward.
However, here is the common problem which I have no answer forward.
Open MYOB and select Library icon top left - and a warning comes up - this service is not working - make sure the service is running.
The Set Library Location fails
The Registry key is still in their for the correct library location from the previous install.
However, in this case if I select one of the files showing in 'Recently Opened Files' on the right - they open correctly.
If I then install the .msi version - same message
If I uninstall SE version - the library location servivce works in the .msi - however - the SET Library Location doesn't
But the SE uninstall removes the library location key in Registry - so once I put it back - the .msi version works.
However, the API doesn't - I installed the API 2020.2.2 from an API install - it installs and shows the correct version 2020.2.2. 9058 if similar (this matches the MYOB version for 2020.2.2.
However - do a localHost:8080/AccountRight and the API finds all the files but if you logon to any of them you get - "WRONG API for file"
In this case (apart from the API) MYOB is working - the API is a problem because unitl now that has been working (I have a Job Costing package working on this server) - it no longer works -
We have another client with 2 servers (the client we did the update to last week and had to roll back) - they NEED a SE version to run as they have 2 servers -
Something in the SE install for 2020.2.2 is screwing the Library Locator Service
MYOB I really need an answer on this - this is critical - this client is livid and has 10 MYOB files - 2 AR Premier and 8 Standard running - most are payroll.
Finally found the problem we think and once I cleared this - install worked perfectly.
The problem is the Library locator Service after everything uninstalled remains and is in the sub-directory
C:\Program Files (x86)\MYOB\AccountRight\Servers
This contains the service 'MYOB AccountRight Library' service - which IS NOT uninstalled when you uninstall the SE or the .msi version.
And if you goto Task Maanger under processes there 4 services running
Uninstalling the SE version doesn't uninstall all the services or that directory - and the service continues - so that when you install the update 2020.2.2 it installs over the top it seems of that existing directory (which actually cannot be changed on installation) - only where the SE version goes - so if this directory is not cleared the install becomes corrupted and the Library Locator Service will show as running but it is running the wrong service or corrupted service.
So after the uninstall - you must ensure through task Manager each of these services are stopped (yes you can do it thorugh services) - but the Library Service if corrupted (can't be stopped that way).
Once you have stopped it go and delete that directory ...\AccountRight\Servers
The uninstall leaves logs and other small things - delete it all so th directory doesn't have anything in it.
A test of whether something is binding that directory - change the name of the directory - if you can it means nothing is running from it. Now Delete it.
Now do a full install of the SE version and the API.
And the Library works .
But the final problem is the Change Library Location utility doesn't work.
You can do a Registry hack to fix that - (this doesn't work if the service isn't running)
add a new string value key
LibraryRoot type REG_SZ Value = The full path of your library
And further if the API is installed as part of SE it is installed as a SERVICE hence the service running above.
If you install the .msi version you have to install the API using the .msi and it runs as an exe startup not a service.
After I installed the .msi and the correct API .msi installer - the API did not work - it said wrong version for file even though the ident version was identical with the MYOB.
I uninstalled these - and allowed SE to install its API as a service.
Voila - all working 100% perfectly both the SE and .msi versions installed and the API running perfectly.
Sorry MYOB I have to give you no brownie points for this patch - this cost me a lot of hours fixing and a lot of clients wondering what the heck.
I’m glad to hear that you’ve been able to find a resolution for everything and been able to get the patch installed properly on those computers.
I’ve passed all of your comments onto the relevant teams so they are aware of the solution that worked for you in this situation.