Users getting the error below in some Windows but after clicking ok on the error message, they are able to move forward and access what they needed. I am a very new GP administrator and could use some pointers on where to get started.
Thanks!
*This post is locked for comments
Kirk,
Thank you so much for this entry. I have been looking for how to troubleshoot this error for a client and I do have the Debugger tool installed but couldn't figure out how to restart GP with the log.
I created the dexsql logs manually and did see this entry and was able to pin point the error to a 3rd party application.
My error looked like this:
{ CALL DYNAMICS.dbo.zDP_SY10000SS_1 ( 'JUDY', 1, 2595, 22001, 2 ) }
Found the cause to be Aatrix and I resolved the issue by creating a different launch file for my limited users without Aatrix, because Aatrix does not allow access to limited users in security.
Really just an annoying issue since the error would repeat 4 time and then the user could continue with their day as normal.
Thanks again,
Sheila
Hi,
Follow this link support.microsoft.com/.../857086
Article 857086.
I followed it to solve all my security issues. I worked fine.
Can you post the log file here?
Kirk
No
Thanks!
Jason,
Do you have something that looks similar to this above that?
{ CALL Dynamics.dbo.zDP_SY10000SS_1 ('User ID', 1 (This is the company), 346 (This is the module), 22492 (security ID), 2 (Object type (2 is a window)) }
Kirk
I see following in the delsql.log file after enabling:
/* Date: 08/24/2016 Time: 12:08:58
SQLSTATE:(S0002) Native Err:(3701) stmt(138503720):*/
[Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot drop the procedure '##zDP_1115659S_1', because it does not exist or you do not have permission.*/
We do not have either installed but I am looking at GP Power Tools for near future. I will follow steps and test today to see if this gives me some insights into where error is originating. Thanks!
Jason,
By any chance do you have the support debugging tool or Great Plains Power Tools? It makes figuring this type of thing out extremely easy.
If not enable Dex logging on the workstation, recreate the scenario and scroll to the bottom of the log. At the bottom of the log you should see the user id followed by some numbers and commas that will tell you the module, and which report or window is being denied. Let me know if you need more info and I can check my notes on this tomorrow for the error syntax.
Regards,
Kirk
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
