SR DAL Error 6522 - Solution

[SB_Systems]

Hi Community,

We have been seeing a spate of these errors on client sites, it seems to be a result of a recent .Net Framework security update, installing a new SystemMessaging.dll file. This file is required by the SRDAL to interact with the Tax database, in a VIZPOST scenario (sites without PM Plus). The issue presents with the following:

SR DAL data source server error (see server event log)

Assuming the SR DAL service is running and working correctly (and appropriate Windows firewall rules are in place), then the next thing to check is the event log error message. 

In the Event Log: Applications and Services Logs -> MYOB look for the following:

System Release DAL SQL error 6522: [Microsoft][SQL Server Native Client 11.0][SQL Server]A .NET Framework error occurred during execution of user-defined routine or aggregate "MSync_SqlMsmq2SendMSMQMessage":
System.IO.FileLoadException: Could not load file or assembly 'System.Messaging, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. Assembly in host store has a different signature than assembly in GAC. (Exception from HRESULT: 0x80131050) See Microsoft Knowledge Base article 949080 for more [SELECT CURSOR]

Once this is confirmed as the issue, you then need to confirm the current version of .Net and update the assembly security in the Tax database.

1. Open Windows Explorer

2. Browse to C:\Windows\Microsoft.NET\Framework

3. Confirm the folder with the highest number, this is currently v4.0.30319

4. Open SQL Management Studio and login as an administrator account

5. Ensure all users have exited MYOB AE and perform a backup.

6. Select the New Query button

7. Select your AETAX database from the drop down, please note this may not be called AETAX.

8. Enter in the following to the SQL Query, where the folder version number is the one confirmed in step 3. For this example, I will use the current version of 4.0.30319:

ALTER ASSEMBLY [System.Messaging]

FROM 'C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\System.Messaging.dll'

9. Press F5 or select the !Execute button to run the script

10. You should receive a message the change was made successfully.

11. Confirm Tax now opens and the data can be accessed.

Please note: for sites running Profiles, it is also possible to correct this issue by running the AETAXConfigUpdate.exe routine from the MYOB BIN folder. Just make sure all staff are out of MYOB AE and a backup has been performed.

As always, this information is provided "as is" and no responsibility will be taken for its misuse or damage caused by these steps. If you are do not understand what the above steps do, please do not attempt them. If in doubt, contact MYOB support

[Sandy_C]

Hi @SB_Systems 

Thank you so much for your time in posting the above. I'm sure it will be very beneficial for others when they encounter a similar issue!

Cheers,

Sandy
Client Support Representative