Journal entry # has been entered in another window

[Aman]

While importing GL history data for a new company, we ran into an
issue with a journal entry number. Possibly another user was in at the
same time, but even after everyone is out and all windows are closed
we still get the same message: "Journal entry 5 has been entered in
another window". We could always use a new journal number to enter the
transaction but how to we delete/void this particular JE ?

[Aman]

From KnowledgeBase Article ID: 863850

1. Exit out of Dynamics.

2. Rename, do NOT delete, the GL Transaction Work file, GL10000.*, in
the Finance folder for your company.

3. Launch Dynamics and go to Transactions - Financial - General. Do a
look up on Journal Entry number. Your journal entry will now be
available.

4. Select the Journal Entry you are trying to post. Click on Post and
close the Transaction Entry window. Print the Posting Journals.

5. Exit out of Dynamics again.

6. A new GL10000.* file will exist. Delete the new file and rename the
original GL Transaction Work file back to GL10000.*.

7. Launch Dynamics and go to Transactions - Financial - General. The
Journal Entry will now increment to the correct number.

--

What exactly is the GL Transaction Work file, GL10000? Is it the
GL10000 table?

[Leslie Vail]

This KB article dates back to when GP supported Btrieve (PSQL) and Ctree.
The files of then are the tables of today. the GL10000 table holds the
header record of unposted journal entries. The SQL table names are the same
as the 'file' names of old.

[Aman]

I changed the table name to GL10000.* but I can't seem to log into the
company now!

---
Error: [Microsoft][SQL Native Client][SQL Server]Invalid object name
'GL10000'.

The stored procedure smCleanupFilesBeforeLogin returned the following
results: DBMS: 208, Microsoft Dynamics GP: 0

Your login failed because of a database error. Contact your system
administrator for assistance.
---

I'm using the sa login.

[Leslie Vail]

Aman, unfortunately you can't follow the flat file instructions for SQL. The
flat file databases automatically created the 'file' if it was missing. SQL
doesn't do that and as you can see, you get errors. Instead you'll need to
backup that table (or just export all of the data). Complete the procedure
and then import that data back in. The procedure is explained in Accolade's
book 'MS-SQL for Dynamics Consultants'. I 'd go through it here, but I
recommend getting your VAR involved to help out. It's a short procedure and
shouldn't take very long.

www.accoladepublications.com

[Aman]

Leslie:

I'd really appreciate it if you could run through the short procedure.
I don't need to post it; just make the journal entry available and
delete it!

Thanks!