Error message when you try to save a new General Ledger account in Microsoft Dynamics GP: "This record has been created since your attempt to create it"

• If you are using SQL Server 2005, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
• If you are using SQL Server 2008, click Start, point to All Programs, point to Microsoft SQL Server 2008, and then click SQL Server Management Studio.
• If you are using SQL Server 2008 R2, click Start, point to All Programs, point to Microsoft SQL Server 2008 R2, and then click SQL Server Management Studio.
• If you are using SQL Server 2012, click Start, point to All Programs, point to Microsoft SQL Server 2012, and then click SQL Server Management Studio.

Resolution 1

1. Open SQL Server Management Studio.
2. Run the following scripts against the company database to verify how many records exist in the GL00100 Account Master table and the GL00105 Account Index Master table.

   Select count (*) from GL00100

   Select count (*) from GL00105
   

3. Use one of the following scenarios, based on your findings from the count scripts.

1. In Microsoft Dynamics GP 10.0, Microsoft Dynamics GP 2010, and Microsoft Dynamics GP 2013, point to Maintenance on the Microsoft Dynamics GP menu, and then click Check Links. In Microsoft Dynamics GP 9.0 and earlier versions, click File, point to Maintenance, and then click Check Links.
2. In the Series list, click Financial.
3. In the Logical Tables list, click Account Master, and then click Insert.
4. Click OK to run the Check Links process. You can print the error log to the screen to check whether the account index was updated.
5. Close the report.
6. Run the count scripts from step 2 again to verify that the tables have the same number of records, and then test again.

1. Open SQL Server Management Studio.
2. Copy the script, and then execute it against the company database to view the additional index records in the GL00105 table that do not exist in the GL00100 table. If you find any additional records, delete them by using the following script:
   
   

   Select * from GL00105 where ACTINDX not in (select ACTINDX from GL00100) 
   
   Delete GL00105 where ACTINDX not in (select ACTINDX from GL00100) 

3. Run the count scripts from step 2 again to verify that the tables have the same number of records, and then test again.

Resolution 2

1. Run the following scripts in SQL Server Management Studio against the company database to verify how many records are in each table.

   Select count (*) from GL00100

   Select count (*) from GL00105

   Select count (*) from AAG00200

2. If the GL00105 Account Index Master table has more or fewer records than the GL00100 Account Master table, see Resolution 1.
3. For the AAG00200 Account Master table, use one of the following scenarios, as appropriate.
   
   Scenario 1
   
   If the AAG00200 table has more records than the GL00100 table, run the following script to delete any account indexes that do not exist in the GL00100 Account Master table:
   

   Delete AAG00200 where ACTINDX not in (Select ACTINDX from GL00100)

   
   Scenario 2
   
   If the AAG00200 table has fewer records than the GL00100 table, you must delete the AAG00200 table and then re-create it.
   
   Note When you take this action, the link between the General Ledger account and Account Class is removed in Analytical Accounting. Therefore, before you begin, you may want note the accounts that are linked to each class ID in Analytical Accounting.
   1. In SQL Server Management Studio, run the following script against the company database to delete the AAG00200 table:
      

      Delete AAG00200

   2. Run the following script to re-create the AAG00200 table:
      
      

      Insert into AAG00200 (ACTINDX,aaAcctClassID,aaChangeDate,aaChangeTime) select ACTINDX,0,convert(char(10),getdate(),111),convert(char(12),getdate(),114) from GL00100 where ACTINDX not in (select ACTINDX from AAG00200)

   3. Click Cards, point to Financial, point to Analytical Accounting, and then click Accounting Class Link.
   4. Enter the class ID, mark the appropriate accounts to link, and then exit the window.  
4. Run the count scripts again in step 1 to verify that all three tables have the same number of records, and then test again.

Resolution 3

sp_helptrigger GL00100

• FRx_Chart_Delete
  
• FRx_Chart_Insert
  
• FRx_Chart_Update
  

1. Back up the company database.
2. Run the following scripts in the Support Administrator Console or in SQL Server Management Studio against the company database:

   Drop trigger FRx_Chart_Delete 
   

   Drop trigger FRx_Chart_Insert 
   

   Drop trigger FRx_Chart_Update

3. Test again.

Resolution 4

1. Back up the company database.
2. Run the following script in the Support Administrator Console or in SQL Server Management Studio:  

   Select * from frl_acct_code where acct_id not in (select ACTINDX from GL00100)

3. In the results that are returned, determine whether the account number that you want to add or save is already listed.
4. Run the following script to remove additional accounts from the frl_acct_code table:

   Delete frl_acct_code where acct_id not in (select ACTINDX from GL00100)

5. Verify that all three tables now have the same number of records:
   

   Select count (*) from GL00100
   Select count (*) from GL00105
   select COUNT (*) from frl_acct_code

6. Log on to Microsoft Dynamics GP, and try to add the account again.

Resolution 5

1. Click Start, point to Programs, point to Microsoft SQL Server, and then click SQL Server Management Studio.
2. Expand the company database.
3. Expand Tables.
4. Right-click GL00100, and then click Design if you are using SQL Server 2008. (If you are using SQL Server 2005, click Modify.)
5. Under Column Name, click DEX_ROW_ID.
6. In the Column Properties window at the bottom, scroll down, and then expand Identity Specification.
7. Make sure that Yes is selected in the Identity Specification field. Also, make sure that 1 is selected in the Identity Seed field and in the Identity Increment field.