tomhr
asked on
Stop Report Schedule window opening on login
This is a pretty interesting one. Client called and said that a user is getting an error on login. The error message said "You don't have security privileges to open this window." The window pop-ed up before the homescreen finished loading. The user can click OK and move on.
I followed a blog post (http://blogs.msdn.com/b/developingfordynamicsgp/archive/2008/11/17/how-to-resolve-security-errors-on-login.aspx) and discovered the cause: The user did not have access to the Report Schedule window. I granted the user the task and now when they log in they do not get an error but the Report Schedule window.
However, they are not supposed to have access to this window. I cannot seem to find how to surpress it on login. I've looked through the documentation and it does not mention "login" or "pop-up" or anything of that nature.
I followed a blog post (http://blogs.msdn.com/b/developingfordynamicsgp/archive/2008/11/17/how-to-resolve-security-errors-on-login.aspx) and discovered the cause: The user did not have access to the Report Schedule window. I granted the user the task and now when they log in they do not get an error but the Report Schedule window.
However, they are not supposed to have access to this window. I cannot seem to find how to surpress it on login. I've looked through the documentation and it does not mention "login" or "pop-up" or anything of that nature.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Got it, it was not showing up in her Startup folder but it was in the database (DYNAMICS..SY01990). Deleted the record and the window no longer pops up. Thanks for the help, Steve.
Hi,
Good find! I wouldn't have thought to check for a record in the database in lieu of the shortcut.
Glad that solved the problem.
Thanks,
Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified IT Professional
Good find! I wouldn't have thought to check for a record in the database in lieu of the shortcut.
Glad that solved the problem.
Thanks,
Steve Endow
Dynamics GP Certified Trainer
Dynamics GP Certified IT Professional
ASKER