web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Quick MOs -> Close...
Microsoft Dynamics GP (Archived)

Quick MOs -> Close MO (Not privilaged to run this report)

(0) ShareShare
ReportReport
Posted on by Community Member

A user account which has nearly all Manufacturing related tasks, as well as inventory and sales related tasks, receives an error when closing a quick MO (Not privileged to run this report.)

I can't tell if this is a problem or not, i.e. the error message doesn't say which report it didn't run. When run with a power user account there simply is no error or report.

 How do I find out which privilege this user is missing?

 

*This post is locked for comments

I have the same question (0)
  • Richard Whaley Profile Picture
    Richard Whaley 25,195 on at

    One way is to run a Dex SQL log and see what window or report the system is attempting to open/run just before the error is being thrown.  Manufacturing has some hidden windows that need to "open" at certain times.  You might look into manufacturing security under windows for the Hidden window (yes, it is named Hidden) and make sure this user has rights to that window.

     

    BTW, these kind of security related issues (including the fix above) are included in our new Dynamics GP Security Handbook.  Visit our web to order a copy.

  • Community Member Profile Picture
    Community Member on at

     Thanks, I added the hidden window. Alas, it didn't fix the problem.

     Could you explain a little more how to run a Dex SQL log? I'm sort of new to GP.

     Thanks again

  • Richard Whaley Profile Picture
    Richard Whaley 25,195 on at

    On the workstation where the test is to be conducted, open the Dex.ini file found in GP\Data folder.  There are 3 lines that refer to SQL Logging that are always found together in the INI and are normally set to FALSE.  Set them to TRUE.

    Open GP and browse to the point where the error is displayed and stop.  Open the windows explorer and browse to the GP/Data folder.  You will find a SQL Log file with the current date and time.  Rename it immediately.  Any name will do, you just want to capture this log.

    Exit from GP, reset the INI settings to FALSE then look in your renamed log.  Near the end will be some calls to windows.  Make sure the user has rights to these resources.

     

  • Community Member Profile Picture
    Community Member on at

    It created 83,000 lines in the couple minutes it took to get to the point where the problem occurs.

    Do errors create any special lines? e.g. here is an error I see around line 81,000. But nothing really stands out for me.

    /*  Date: 10/20/2009  Time: 12:54:43
    SQLSTATE:(00000) Native Err:(207) status(41):*/
    SWSTATUS DUMP*/

  • Richard Whaley Profile Picture
    Richard Whaley 25,195 on at

    If you stopped working with GP at the point where the error was displayed, look in the last dozen or so lines for a window or report name.  Post those lines if you need to

  • Community Member Profile Picture
    Community Member on at

     This stands out to me. But there are literally hundreds of other declarations done in just the last second of the log.

    /*  Date: 10/20/2009  Time: 14:33:56
    stmt(19031232):*/
    DELETE FROM SNDBX.dbo.MOP1410 WHERE ( MANUFACTUREORDER_I = 'MO0000024' )

    /*  Date: 10/20/2009  Time: 14:33:56
    stmt(19020216):*/
    DROP PROC ##zDP_0325633S_1, ##zDP_0325633N_1, ##zDP_0325633F_1, ##zDP_0325633L_1, ##zDP_0325633SI, ##zDP_0325633SD

    /*  Date: 10/20/2009  Time: 14:33:56
    stmt(19020216):*/
    DROP PROC ##zDP_0325633S_1, ##zDP_0325633N_1, ##zDP_0325633F_1, ##zDP_0325633L_1, ##zDP_0325633SI, ##zDP_0325633SD
    /*
    /*  Date: 10/20/2009  Time: 14:33:56
    SQLSTATE:(S0002) Native Err:(3701) stmt(19020216):*/
    [Microsoft][SQL Native Client][SQL Server]Cannot drop the procedure '##zDP_0325633S_1', because it does not exist or you do not have permission.*/

     That last item is repeated a couple times and then:

     /*  Date: 10/20/2009  Time: 14:33:56
    SQLSTATE:(00000) Native Err:(3701) stmt(19020216):*/
    */
    /*
    /*  Date: 10/20/2009  Time: 14:33:56
    SQLSTATE:(00000) Native Err:(3701) status(56):*/
    SWSTATUS DUMP*/

     

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.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans