Skip to main content
Skip table of contents

Lodgment Manager homepage showing as blank

This support note applies to:

  • AO Tax (AU)
  • AE Tax Series 6 & 8 (AU)
  • AE Tax (AU)
Article ID: 38452

In MYOB Tax using PLS (CloudAuth), when accessing the Lodgment Manager homepage it may appear blank.

This is most commonly caused by duplicate Agent codes in Maintenance > Agents inside Tax. For example, Agent1 and agent1 will be accepted but are not unique. You'll need to check and correct this.

After correcting the Agent, if the issue persists, contact us and quote KB 38452.

 MYOB INTERNAL STAFF ONLY 

You could first try running the Tax core scripts to see if it fixes the issue
  1. From the desktop of your server or standalone, follow the menu path: Start > Programs > Microsoft SQL Server 20xx > SQL Server Management Studio
  2. Complete the fields as required and click Connect. The Microsoft SQL Server Management Studio screen appears.
  3. Open the C:\Program Files (x86)\MYOB\TaxCore folder. You’ll see two SQL queries, which you need to run.
  4. To run the first query:
    1. Double click tax install 01 – Tax_TaxYearTableType.sql. You will see the query displayed in SQL Management Studio.
    2. Make sure to select your Tax database name from the dropdown as marked in the picture and click the 
       button.

  5. To run the second query:
    1. Double click tax install 02 – Columns and Indexes.sql You will see the query displayed in SQL Management Studio. You will see the query displayed in SQL Management Studio.
    2. Make sure to select your Tax database name from the dropdown as marked in the picture and click the 
       button.


Please read the log file to see if there is anything in their causing it to fail. For example, corrupt returns will be listed with the ReturnCode. The log file sits in C:\ProgramData\MYOB\DbUpgrade.

For AE sites, check and ensure there is no duplicate tax ledger codes or, any tax ledger codes with symbols. Do not re-run the database upgrade.

If the issue is still not fixed:

  1. Check for duplicate return codes
  2. If there are no duplicate return codes, check for duplicate returns in the lodgment history.

1. To check for duplicate tax ledger codes

Run the query below in SQL Server Management Studio to check for duplicate return codes:

IF exists (Select * From dbo.sysobjects Where id = object_id(N'tempDuplicateReturns') and OBJECTPROPERTY(id, N'IsTable') = 1)

Drop Table tempDuplicateReturns
Go
create table tempDuplicateReturns
(Year int, ReturnCode varchar(10), Duplicates int)

 

if exists (select * from ds6tc812)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TC811
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tc712)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TC711
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tc612)
Begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TC611
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tc512)
Begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TC511
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tc412)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TC411
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA312)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA311
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA212)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA211
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA112)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA111
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA012)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA011
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA912)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA911
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA812)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA811
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA712)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA711
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
if exists (select * from ds6tA612)
begin
insert into tempDuplicateReturns
SELECT year, ReturnCode, COUNT(ReturnCode)
FROM DS6TA611
GROUP BY ReturnCode, year
HAVING ( COUNT(ReturnCode) > 1 )
end
select * from tempDuplicateReturns

IF exists (Select * From dbo.sysobjects Where id = object_id(N'tempDuplicateReturns') and OBJECTPROPERTY(id, N'IsTable') = 1)
Drop Table tempDuplicateReturns
Go

2. To check for duplicate returns in lodgment history

If there are no duplicate return codes, there may be duplicate returns in the lodgment history. Run the following query against the tax database to identify the duplicates:

select [return], Year, formid from tax_DZZTB011
group by concat([return], ' ', year, ' ', FormID), [return], Year, formid
having count(concat([return], ' ', year, ' ', FormID)) > 1

Once identified, these duplicates can be removed by resetting the lodgment history. For step-by-step instructions, refer to:

Insert PR#:

For Duplicate Agents: 141078284618

Duplicate Return Codes: 142452459269

Duplicate Lodgment History: 142647483404

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.