MYOB network cannot open after successful updates

[Luc_Munro]

It's possible the server installation is messing up the Windows firewall settings, and it may not clean them up during an uninstall.  We had the same issue as others here and the uninstall / reinstall process made no difference.  However, we discovered the Windows Firewall settings were incorrect.  There were 3 separate rules for each MYOB service, each with different conditions, and none of them matched our network environment.  We deleted all but one of each rule for each service, and configured that rule to have minimal conditions - allow all subnets, allow all policies (domain, private and public), etc.  Once we did that the clients were able to connect to the server, browse the library and open files.

[GlennH_WR]

Hi @Luc_Munro ,

Do you have screenshots of your firewall settings that work?

The Windows Server Log is suggesting that one or more components of the MYOB Service cannot be found.

The Installation log for the 2022.10 SE install shows that Windows Firewall settings were successfully updated.

Is there a firewall setting that is not even attempted to be updated by the 2022.10 SE installer, that is actually required?

[Luc_Munro]

I don't have a copy of what it looked like when it wasn't working, but I've attached a screenshot of what it looks like now.  Before the changes there were three copies of each of the MYOB rules, one for each profile, and some of them were disabled.

Essentially, the changes I made (from within the Windows Advanced Firewall Settings app, or whatever it's called on the different Windows versions) to the Inbound Rules were:

* On the Programs and Services tab, make sure the rule applies to all programs

* On the Scope tab, make sure the rule applies to any IP address for both local and remote IP addresses.  Some of the default rules had made incorrect assumptions about private IP address subnets.

* On the Advanced tab, make sure the rule applies to all the profiles (Domain, Private and Public).  Depending on your server network configuration, Windows might be classifying your network interface into profile the original rules were expecting.

No changes were made on the Protocols and Ports tab - the default ports are correct and specific to each service.

[Luc_Munro]

I think there might actually be two problems in 2022.10 - we originally got the "Unknown" version error after the auto-upgrade occured (as per the OP).  After performing a manual upgrade, along with several uninstall / reinstall cycles, that message went away but the client PCs were no longer able to connect to the server.  The firewall changes resolved the second issue and we're now back online.

Also, uninstalling wasn't trivial either.  Trying to uninstall from the control panel didn't work - it came up with an error related to not being able to run "upgrade.exe".  We had to manually run "upgrade.exe --uninstall" from the MYOB program files folder to uninstall it.

It's quite amazing how many issues each version MYOB brings with it.  I can't recall a single upgrade going smoothly for at last the last year or more.

[GlennH_WR]

Thank you @Luc_Munro for posting that.

I have all of those set as you except for 'Public'.  I would not advise allowing these to be enabled in the 'Public' profile. For security purposes you should keep "Public' disabled.

IMHO, previous versions of Server Edition have not required the 'Public' profile to be enabled for MYOB ports and I would discourage people from setting them.  

[DianeC]

On your server pc, when you look in services does it show any older server versions?

I had 4 older versions still showing, although they had been disabled. The MYOB version these related to had been unistalled, but it had not cleared the server files from services even though there was no longer had a file to link to. I have just done a registry fix on these and reinstalled 2022.10 and my issue has finally been resolved.

[RajeshS]

Hi DianeC,

Can you please tell me how to do the registy fix please. I tried re-installing and that did not work and prior to reinstalling I had all the previous versions running on services.

[Casacc]

Has anyone received a definitive answer from MYOB that they've even acknowledged this is a known bug? I note MYOB has not posted in any of the related topics.

We're not keen to edit the registry.  
We're not going to uninstall then reinstall again.

Rolling back to an older version is not a suitable solution.

Has anyone received a proper solution from MYOB?

Thanks!