About every 2 or 3 weeks all of my Dynamics users will experience GP to become frozen. When I log on the the SQL server I do not see anything abnormal for CPU and disk usage in task manager. Also if I try to login my session gets hung at right past the GP login screen. Any suggestions or ways I can troubleshoot this further?
Thank you,
Jonathan Alden
*This post is locked for comments
Harry's idea is a good one. I had several of those back in the GP 10 days! It was a bear to first find it. Having too many ideas is better than not having enough. Let us know how it works out.
Sorry EVRInfoTech - it does not appear as if you have the easily resolved issue related to the SY07110 table filling up with erroneous data, which is detailed here:
blogs.msdn.com/.../login-performance-issue-for-microsoft-dynamics-gp-10-0-sp5-and-gp-2010-sp1.aspx
My suggestion would be to start with Richard's advice above, he's top hand. If that doesn't fix the problem, then I would refer to the following Microsoft KB article;
support.microsoft.com/.../898982
I see about 1100 Records in the SY07110 table. for the select * FROM DYNAMICS.dbo.SY07110 WHERE CmdDictID = 6499 I get two results
There would be absolutely several possible reasons, I would start by looking in the Dex.sql log.
Let us know what's in there when Dynamics GP freezes. That would possibly limit down the number of possibilities.
By the way, as Harry Lee says, it's been a decade for me since I have heard of some freezing issue.
Your feedback is highly appreciated,
Your first port of call is to run:
select * from sys.dm_exec_requests
where blocking_session_id <> 0 -- Session_id is the session that is locked and block_sssion_id is the session doing the blocking
This will return the sessions that are being blocked, and the sessions that are blocking them.
Once you have these:
select * from sys.sysprocesses
where spid = (select blocking_session_id from sys.dm_exec_requests
where blocking_session_id <> 0)
Will give you more detail and :
DBCC INPUTBUFFER(XX) will give you the SQL statement being run.
If you really want to dig down you could have a look at sys.dm_tran_locks.
select * from sys.dm_tran_locks
You can also create an alert based on a SQL Server performance condition. Monitor the SQL Server:General Statistics object, Counter: Processes blocked
Finally you can check the DEX_SESSION and DEX_LOCK tables.
SELECT * FROM TEMPDB..DEX_SESSION
SELECT * FROM TEMPDB..DEX_LOCK
The problem most likely not with GP but with SQL. There are probably record or table locks in there someplace.
It's been awhile since I've heard of this kind of issue. When GP 2010 was initially released, there was a glitch with the feature that controls what the user interface. Here is a set of queries which can diagnose and solve this particular problem - start here first because it is easy, and effective. As is always prudent to have a BACKUP prior to running any Delete, Alter or Update query on your database.
select * FROM DYNAMICS.dbo.SY07110 WHERE CmdDictID = 6499
--DELETE FROM DYNAMICS.dbo.SY07110 WHERE CmdDictID = 6499
If you have a ton of records in the SY07110 table, GP will hang at the log in screen.
If this proves not to be your problem, there is a link to a more involved series of troubleshooting steps you may take to identify and resolve your speed issues below:
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,280
Super User 2024 Season 2
#2
Martin Dráb
230,214
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (