Error Accessing Sql Data Microsoft Dynamics 10.0
365 for Enterprise Skype for business Microsoft Dynamics Microsoft Dynamics Sales Service Marketing Social Enterprise Resource Planning Small and Midsize Business Windows Windows 10 for business Windows 10 for Internet of Things Windows devices Data and analytics Data management and analytics Microsoft SQL Server Microsoft Power BI Microsoft Cortana Intelligence Suite Operations management Operations Management Suite System Center Sign in Search Microsoft Search Dynamics Community Participate Ask a Question Get Started Badges Earn Badges View Badges Leaderboards Compete on Leaderboards View Leaderboards Become an Expert Recommend a Blog Introduce Yourself Provide Feedback Communities Microsoft Dynamics AX Microsoft Dynamics CRM Microsoft Dynamics GP Microsoft Dynamics NAV Other Products Partner Community Dynamics Community Microsoft Dynamics GP Forum Blogs Videos Experts Support Dynamics Community Participate Ask a Question Get Started Badges Earn Badges View Badges Leaderboards Compete on Leaderboards View Leaderboards Become an Expert Recommend a Blog Introduce Yourself Provide Feedback Communities Microsoft Dynamics AX Microsoft Dynamics CRM Microsoft Dynamics GP Microsoft Dynamics NAV Other Products Partner Community Microsoft Dynamics GP Forum Blogs Videos Experts Support Error when running custom reports: Error Accessing SQL Data Sign In Share Twitter LinkedIn Facebook Email Print RSS kuroneko1313 My Badges Question Status Unanswered kuroneko1313 asked a question on 15 Mar 2010 12:18 PM Hello,We just upgraded to GP 10.0 from version 9.0. Today our users encountered an error when running custom report for Historical Orders. Custom report for Open Orders can be ran just fine.However when I try to run the Historical Orders custom report using SA login, I can run it just fine. Could this be a permission issue? If yes, how to modify it in the reports?I tried re-importing t
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Error accessing SQL data in Microsoft Dynamics 10.0 (Great Plains) Want to Advertise Here? Solved Error accessing SQL data in Microsoft Dynamics 10.0 (Great Plains) Posted on 2009-01-07 Tax / Financial Software MS Dynamics MS SQL Server 2005 1 Verified Solution 5 Comments 1,902 Views Last Modified: 2013-12-11 We are running Dynamics 10.0 https://community.dynamics.com/gp/f/32/t/31540 and upgraded to SP3. The upgrade went fine. Went into GP Utilities and started the update of the companies. It completed 4 companies fine and then utilities quit responding. I let it sit there for quite awhile hoping that it would start responding but never did. I closed the application and restarted the server. I deleted the lock files within SQL and started Utilities again. I never had any more problems and it upgraded all of https://www.experts-exchange.com/questions/24034080/Error-accessing-SQL-data-in-Microsoft-Dynamics-10-0-Great-Plains.html the companies without any errors. I did a backup before the upgrade and after. After everything was finished I updated one of the clients. She then proceeded to run through the checks to make sure everything updated fine. Everything checked out fine. She did a year end closeout of all the companies and everything went fine with no errors. She then tried to print out the year end wage report and we get an error accessing the SQL data. If you look up the wage data then everything looks fine but that report will not run. We also get the error when posting payroll. Payroll will post but the reports won't run. Everything seems to be fine with the data but some of the reports just don't want to run. We are in dire need of getting this working. PLEASE HELP US. Thanks in advance. 0 Question by:Wyandotte Facebook Twitter LinkedIn Google LVL 7 Active today Best Solution byJames Glaubiger We have seen issues with the SP3 for GP. It can corrupt the Modified Reports.dic file which contains all your modified reports. If you have a backup of your reports.dic from prior to the update, restore Go to Solution 5 Comments LVL 13 Overall: Level 13 MS SQL Server 2005 11 MS Dynamics 1 Message Expert Comment by:St3veMax2009-01-08 Look at permissions inside S
OptionsPost ReplyCreate New Topic Printable Version Translate Topic tracy5436 http://www.microsoftdynamicsforums.com/forums/forum_posts.asp?TID=4396&title=erropr-accessing-sql-data Members Profile Find Members Posts MicrosoftDynamicsForums.com Member Joined: August152009 Status: http://dynamicsgpgeek.blogspot.com/2009/10/dynamics-gpsql-database-user-disconnect.html Offline Points: 19 Post Options Post Reply Quotetracy5436 Report Post Thanks(0) QuoteReply Topic: Erropr accessing sql dataPosted: April132010 at 3:32pm I havea client who updated to the latest sp for GP and also upgraded to sql 2008. error accessing Since then , when they print a stock status report and restrict it omit zero quantities, they receive an "error accessing sql data" error. They do not receive this error for all sites, it only appears to be for large sites. This is not a modified report. I error accessing sql have recreated the reports dictionary, but receive the same error. Any ideas ? Sponsored Links Post Reply Tweet Forum Jump -- Select Forum -- GP - Installation and Administration GP - Customization and Integration GP - Web Applications GP - General SL - Installation and Administration SL - Customization and Integration SL - Web Applications SL - General FRx Management Reporter CRM - Installation and Upgrade Issue CRM - General Navision (NAV) Axapta (AX) Retail Management System (RMS) POS Forum Permissions You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot delete your posts in this forumYou cannot edit your posts in this forumYou cannot create polls in this forumYou cannot vote in polls in this forum Copyright 2013 microsoftdynamicsforums.com. All rights reserved. MicrosoftDynamicsForums.com is an independent non-Microsoft website. Email: contact AT microsoftdynamicsforums DOT com
data" "[Microsoft][SQL Native Client][SQL Server]The server principal "LESSONUSER2" is not able to access the database "TWO" under the current security context." "The user could not be added to one or more databases." "A get/change first operation on table 'SY_Users_MSTR' failed accessing SQL data" "[Microsoft][SQL Native Client][SQL Server]The server principal "LESSONUSER1" is not able to access the database "DYNAMICS" under the current security context." "[Microsoft][SQL Native Client][SQL Server]EXECUTE permission denied on object 'zDP_SY01400SS_1', database 'DYNAMICS', schema 'dbo'." Dynamics GP tracks users separately from SQL Server. However, there is a one to one relationship between a Dynamics GP user and a SQL Server login. Both the Dynamics GP user and corresponding SQL Server login have the same username. Additionally, when a user is granted access to a company, their SQL login is added as a SQL user in that company's database as part of the DYNGRP role. The SQL logins associated with Dynamics GP users also have an associated SQL database user in the DYNAMICS database also a member of the DYNGRP role. Problems happen when the Dynamics GP users and SQL logins get out sync. There are five situations when these get out of sync: The Dynamics GP user has been given access to a company in GP but the corresponding SQL login doesn't have access to that company. The Dynamics GP user doesn't have access to a company in GP but the corresponding SQL login does have access to the company. The Dynamics GP user doesn't have access to the DYNAMICS database. The Dynamics GP user's corresponding SQL login doesn't have access to the Dynamics database. The Dynamics GP user's corresponding SQL login isn't a member of the DYNGRP role in the databases it is supposed to have access to. First we'll look at each of these situations individually and how to individually resolve them. Then we'll look at a script that will clean up all of them at once. Dynamics User w/ Missing SQL User This is the case where a Dynamics GP user has been given access to a company in GP but the corresponding SQL login doesn't have access to that company. In this case, the user will receive the following error message when logging into Dynamics GP: Clicking on "More Info" returns the following: "[Microsoft][SQL Native Client][SQL Server]The server principal "LESSONUSER2" is not able to access the database "TWO" under the current security context." To resolve this error, go into SQL Management Studio and add the corresponding SQL login to the company database as a member of the DYNGRP role. SQL User in Company Database w/o Corresponding Dynamics GP