MYOB Accountants enterprise System Release DAL event ID 6 in application log

A client who runs MYOB accountants enterprise had a problem whereby when they went to contacts, opened a client file, and then open the tax return of the current client from the toolbar an error was generated as shown below:

S6:\\SERVER\MSSQL\AETAX1\TAX\TA

S6:\\SERVER\MSSQL\AETAX1\TAX\TA not found error

Also in the event log every 2 minutes was the following erros:

Event Type: Warning
Event Source: System Release DAL
Event Category: None
Event ID: 6
Date:  13/02/2009
Time:  1:19:07 PM
User:  N/A
Computer: SERVER
Description:
The description for Event ID ( 6 ) in Source ( System Release DAL ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: System Release DAL, 0×4d4 from GetQueuedCompletionStatus in session (0.0.0.0 port 38267). , The network connection was aborted by the local system..

I found restarting the System Release DAL service resolved the problem.  Note the AE Tax Subscriber relies on this service and will shut down also, and need to be manually restarted after restarting System Release DAL.

System release DAL service

1 Comment »

1. Pressing the Moneybag will open the most recent AE Tax forms (tax return) that have been added into the Contact.

   AE Tax uses System Release on the workstation to connect to a service on the server called System Release DAL using TCP port 6606, System Release DAL then opens an ODBC connection to the Microsoft SQL Server instance.

   The first query that it run on the database is to locate the TA record from the AETAX1 database.

   If the workstation can’t connect to the System Release DAL at all, you will get a “TA is offline” error.

   If the workstation can connect to System Release DAL, but can’t access the SQL Database, you will get a “TA not found” error.

   The cause your “TA not found” error was probably because the SQL Server was restarted, which means that System Release DAL would need to be restarted to start the ODBC connection ODBC again.

   GetQueuedCompletionStatus and 0×4d4 (ERROR_CONNECTION_ABORTED) “The network connection was aborted by the local system.” seems to happen for no reason except to fill up your event log, highly annoying. There would be something coming from the SQL server returning this error, which in turn is logged by the System Release DAL that is connected to the SQL Server.
   Doing a bit of searching of these errors on Google suggests that it’s related to Winsock 2 in Windows, so I don’t know if it’s myobs fault or not.

   Comment by dolphin — 05/03/2009 @ 11:36 pm

RSS feed for comments on this post. TrackBack URL

Leave a comment

You must be logged in to post a comment.