When things go wrong - Batches cannot be posted

Here's the scene. You're trying to post a batch of GL entries and you get the following error:

"Batches cannot be posted while the year-end close is in progress"

But, of course, the year-end closing process is not happening. What to do?

You need to change the system's mind about that closing process by running the following scripts:

First, and always, back up your system and company databases, and then:

USE DYNAMICS
GO
DELETE SY00800
DELETE SY00801

USE TEMPDB
GO
DELETE DEX_SESSION
DELETE DEX_LOCK

UPDATE:
Here's a post from David Musgrave that allows you to clear up the batch error with everyone still logged into the system:

http://blogs.msdn.com/b/developingfordynamicsgp/archive/2008/12/03/releasing-stuck-batches-and-transactions-without-exiting-all-users.aspx


Hope this clears it up for you.

Live the Dream!

Leslie

When things go wrong - Another user closing the year

You're trying to close the year and you get an error message:

"Sorry, another user is closing the year"

However, no other user is trying to close the year. What to do?

     Make sure everyone is logged out of Dyanamics GP

     Backup your company Database

     Run the scripts

     Use 'YourCompanyDatabase'
   Go
 
   Delete GL50100

When things go wrong - This batch is being posted by another user

You get this message even though nobody is logged in to the database so that it's impossible for the batch to be being posted by somebody else. What to do?

1.  Back up the DYNAMICS and company databases.
2. Change the batch status so that it no longer thinks it's being posted.

USE YourCompanyDatabaseName
GO

UPDATE SY00500 set BTCHSTTUS = 0 WHERE BACHNUMB = 'YourBatchNumber'

Depreciation - When things go Wrong

Sometimes we set up depreciation and the CPA firm decides it should have been done a different way. Of course, that information comes to us at least two years after we set it up. It's the nature of the beast; they're accountants, they can't help it.

The following scenarios will be covered over the course of four posts:

• Wrong 1st yr Convention
• Basis Reduction Required
• Wrong Depreciation Method - fully depreciated as of previous year end
• Wrong Depreciation Method - not fully depreciated as of previous year end

Stay tuned.

Until next post!

Leslie

Use PSTL without being 'sa'

https://connect.microsoft.com/dynamicssuggestions/feedback/details/762593/run-pstl-as-a-non-sa-user-create-a-pstl-user

Wouldn't it be nice to be able to perform PSTL activities without having to log in as 'sa'?

Vote for the above post if you agree. Now that we all have this tool, it's becoming more of an issue. With security being such an issue this day and age, casually asking for the 'sa' password so that we can change a Vendor ID seems rather extreme.

It's time to give the Controller the right to control the accounting system's details without the ability (and liability) to drop all of the company's databases.

This must be 'hard-coded' into the Dexterity script, let's vote to get that coding removed!

Live the Dream!
Leslie