Great Plains 2009 - Project No Locked

(1) Share

Report

Posted on by Community Member

A team member has attempted to process an invoice in the Billing Entry screen in GP 2009 and the following error arose:

The project is being used by another user. Please select another Project Number.
The project number is locked and the invocie is unable to be processed.

External IT support are suggesting to restart the SQL server where the Great Plains database sits on and this may unlock the project.

Are there any other options our company should consider as well as alternatives?

We're in the process of upgrading to a much new GP version.

Thanks

*This post is locked for comments

I have the same question (0)

All responses (9)

Answers (2)

Richard Wheeler 75,848 Moderator on at

Like (1)

Report

The standard IT advice of rebooting the server will not correct this. Please refer to this KB.

https://support.microsoft.com/en-us/kb/940834?sd=rss&spid=10479

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Richard

We found the exact same as well on the internet.

Our Great Plains partner recommended the same solution and advised for our IT support provider to follow this recommendation.

However they had no success and project is still locked.

Is the IT support provider the correct party to be doing this?

Anything else we could try or is this the correct & only suggestive approach to remedy when a Project No is locked?

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (1)

Report

Before you reboot the server or simply stopping and starting he SQL service would do the same thing I would run these in SSMS:

SELECT * FROM DYNAMICS..ACTIVITY

SELECT * FROM DYNAMICS..SY00800

SELECT * FROM DYNAMICS..SY00801

SELECT FROM TEMPDB..DEX_LOCK

SELECT * FROM TEMPDB..DEX_SESSION

Run these while no one is in GP. If any of these return records then

DELETE DYNAMICS..ACTIVITY

DELETE DYNAMICS..SY00800

DELETE DYNAMICS..SY00801

DELETE FROM TEMPDB..DEX_LOCK

DELETE FROM TEMPDB..DEX_SESSION

Let us know how it goes.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

Change the last two to

DELETE TEMPDB..DEX_LOCK

DELETE TEMPDB..DEX_SESSION

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Richard, I'll run your suggestion past our Great Plains and IT providers for guidance

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Richard, we got the locked project to clear with the help of your suggestions, thanks.

Was this reply helpful? Yes No
Verified answer

Irfan.Rasheed 717 on at

Like (1)

Report

Hi,

Use this script to company database.

Select * from PA000001, that brings which user open specific project.

From backend you can also remove that user from this project using

Delete PA000001 where userid='XXXXXXXX'

I hope it shall serve the purpose.

Regards.

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (0)

Report

Thanks Irfan for the feedback.

Was this reply helpful? Yes No
Suggested answer

Squishy Worms 15 on at

Like (0)

Report

Sadly, I see this all the time in our company. It's seems Microsoft Dynamics GP is dead set on keeping projects locked.

I have often just use: DELETE PA000001; since the majority of projects should not be locked.

Was this reply helpful? Yes No