We updated to GP 2013R2 last month
today the picklist shortage inquiry has stopped working??
even as sa...
anyone know where I can look to see whats up?
tami
*This post is locked for comments
Turn on Dynamics Logging (in Dex.ini)
or
Run a SQL Profiler trace
Turn on logging with the Support Debugging tool or GP Power Tools.
Tim
Hi there Tim
not sure what i am looking for/?
ran the SQL profiler...
You would need to run the profiler trace using the recommendations in
mbs.microsoft.com/.../MDGP_HOWTO_CreateSQLProfileTrace
If the process is truly "hung," the trace will stop. After you push the stop (red square) button then look at the last commands SQL tried to execute. If it doesn't stop, just hit the red button anyways and see if you can spot the repeated commends in the loop.
Don't leave trace running for long stretches (it slows SQL server down a lot).
One possible cause I can think of is a badly structured BOM.
Maybe Harry Lee (Redbeard) will have some thoughts as to causes.
Tim Foster
Hi Tammy,
Tim's suggestions are all valid however I recommend starting with his first regarding the dex logging (assuming you don't have the SDT or GPPT). This will let you see what is happening without having to sift through other connections to the SQL Server.
Close GP, enable logging in the Dex.ini file, start GP. Right before you run the inquiry delete the dexsql.log file, run the inquiry, open the log and scroll all the way to the bottom. This should give you some insight as to what is going on. Feel free to post a copy of the log here.
Regards,
Kirk
can I get specifics...searching customer source has no information on enabling logging in the dex.ini?
even a KB?
Hi Tami,
Here is a link support.microsoft.com/.../850996
/* Date: 09/09/2015 Time: 10:49:22
SQLSTATE:(S0022) Native Err:(207) stmt(58157992):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Invalid column name 'desSPRkmhBBCreh'.*/
/*
SQLSTATE:(00000) Native Err:(207) stmt(58157992):*/
*/
SQLSTATE:(00000) Native Err:(207) status(41):*/
SWSTATUS DUMP*/
stmt(58143600):*/
{ CALL DYNAMICS.dbo.zDP_SY02100SS_1 ( 1, 346, 6, 0 ) }
stmt(58157184):*/
BEGIN DECLARE @stored_proc_name char(41) DECLARE @retstat int set nocount on SELECT @stored_proc_name = 'BRLD.dbo.mmopBuildPicklistShortagesTables' EXEC @retstat = @stored_proc_name '', 'ÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞ', '', 'ÞÞÞÞÞÞÞÞÞÞÞ', '1900.01.01', '9999.12.31', '', 'ÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞÞ', 0, '##1913448', '##2352249', 0 SELECT @retstat set nocount on END
Does the issue occur on other workstations/GP Clients? You might have a corrupted GP install on the local machine.
Occurs all workstations..all users with permissions...worked last week fine
If it was working yesterday...An MO that was added today has some bad data in it.
Try running the report with a lower and upper limit on the MO number. See if it runs.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
