Error message when you try to view a SmartList object in Microsoft Dynamics GP: "You do not have security privileges to view all of the tables used in this SmartList”

To resolve this problem, verify the following based on the version of Microsoft Dynamics GP that you are using:

• Verify that the user has the security privileges that are required to view the SQL tables in a SmartList.
• Verify that the user has access to the table that is used for the object.

Microsoft Dynamics GP 10.0/ Microsoft Dynamics GP 2010

Create a new security task. To do this, follow these steps:

1. On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to System, and then click Security Tasks.
2. In the Security Task Setup window, in the Task ID box, type a task identifier (ID).
3. In the Task Name box, type a task name.
4. In the Task Description box, type a description.
5. In the Category list, click System.
6. In the Product list, click SmartList Builder.
7. In the Type list, click SmartList Builder Permissions.
8. In the Series list, click SmartList Builder. The Access List area displays the various permissions for SmartList Builder.
9. Click to select the check box next to View SmartLists with SQL Tables.
10. Click Save.
11. Close the Security Task Setup window.

SmartList Builder Security

1. On the Microsoft Dynamics GP menu, point to Tools, point to SmartList Builder, point to Security, and then click SQL Table Security.
2. On the left side, click the check box next to the database name for which you are receiving the error.
3. On the right side, click the check box next to the table/view name that is used by the SmartList Item.
   
   Note You can also click Mark All to mark all the tables in the company database.

Microsoft Dynamics GP 9.0

1. On the Tools menu, point to SmartList Builder, point to Security, and then click User Security.
2. In the SmartList User Security window, click User Security.
3. In the User ID list, click the user who is receiving the error message that is mentioned in the "Symptoms" section.
4. In the Roles area, click to select the check box next to the View SmartLists with SQL Tablesoption.
5. If you are using user classes, click User Class Security, and then repeat step 4.
6. Click OK to save the changes.

SmartList Builder Security

1. On the Tools menu, point to SmartList Builder, point to Security, and then click SQL Table Security.
2. On the left side, click the check box next to the database name for which you are receiving the error.
3. On the right side, click the check box next to the table/view name that is used by the SmartList item.
   
   Note You can also click Mark All to mark all the tables in the company database.
4. Repeat step 2 and 3 for views if you have a view used in the SmartList Builder object. 

How to uninstall Microsoft Dynamics GP 10.0 if you cannot uninstall it by using the "Add or Remove Programs" feature

INTRODUCTION

This article describes how to uninstall an existing Microsoft Dynamics GP v10 system if you cannot uninstall it by using the Add or Remove Programs feature (or Programs and Features in Windows Vista) in Control Panel. It is recommended that you verify that you cannot uninstall by using Add or Remove Programs first.

MORE INFORMATION
First, verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features)
To verify that you cannot uninstall Microsoft Dynamics GP by using Add or Remove Programs (or Programs and Features in Windows Vista), follow these steps.

For Windows XP or Windows Server 2003:
1. Click Start, click Run, type control appwiz.cpl in the Open box, and then press ENTER.
2. Click to select Microsoft Dynamics GP 10.0 product from the application list, and then click Remove.

For Windows Vista:

1. Click Start, type Programs and Features in the Search box, and then press ENTER.
2. Click to select the product to be uninstalled from the listing of installed products, and then click Uninstall/Change from the bar that displays the available tasks.

If you were able to uninstall Microsoft Dynamics GP 10.0 by using Add or Remove Programs, you are finished. If you were unable to uninstall Dynamics GP, you may have issues with the Add or Remove Programs dialog box, or some Dynamics GP components may not be uninstalled. In these cases, you may be unable to reinstall Dynamics GP and/or may end up with additional errors when attempting to install again.

If Add or Remove Programs does not uninstall Microsoft Dynamics GP 10, use this alternative method to uninstall
After you use this method, you can reinstall Microsoft Dynamics GP 10.

Note: You must be logged on to Windows with a user account that is a computer administrator to complete this method. If this is your personal computer, you are likely already logged on with an administrator account. If this is a computer that is part of a network, you might have to ask the system administrator for help. To verify that you are logged on to Windows with a user account that is a computer administrator, visit the following Microsoft Web site:

http://support.microsoft.com/gp/admin

Step 1: Remove any remaining Windows Installer packages for Microsoft Dynamics GP 10
1. Click Start, click Run, type installer, and then click OK. This process opens the %windir%\Installer folder.
2. On the View menu, click Details. Important To use the View menu in Windows Vista, you must press the ALT key first to display the menu bar, and then click the View menu.
3. On the View menu, click Choose Details.

4. Click to select the Subject check box then click OK. Note It may take several minutes for the subjects to appear next to each .msi file.
5. For Windows XP or Windows Server 2003, on the View menu, point to Arrange icons by, and then click Subject. For Windows Vista, on the View menu, point to Sort By, and then click Subject. In Windows Vista, a User Account Control dialog box may be displayed with the following warning:
An unidentified program wants access to your computer

Click Allow when you see this warning message.
6. Locate the "A cross-industry financial management solution for mid market segment businesses" installer package (b7d84e.msi file). Right-click and select uninstall.

7. Locate the "Dexterity Shared Components" installer package (8ab4386.msi file). Right-click and select uninstall.

Step 2: Remove any remaining Dynamic GP 10 installation folders

1. For Windows XP and Windows Server 2003, click Start, click Run, type %CommonProgramFiles%\Microsoft Shared in the Open box, and then click OK. For Windows Vista, click Start, click Start Search, type %CommonProgramFiles%\Microsoft Shared, and then press ENTER.

2. Delete the Dexterity folder

3. For Windows XP and Windows Server 2003, click Start, click Run, type %CommonProgramFiles% in the Open box, and then click OK. For Windows Vista, click Start, click Start Search, type %CommonProgramFiles%, and then press ENTER.
4. Delete the Microsoft Dynamics GP folder

5. For Windows XP and Windows Server 2003, click Start, click Run, type %ProgramFiles%\Microsoft Dynamics, and then click OK. Note On a computer that is running a 64-bit version of Windows XP, type %ProgramFiles(x86)%\Microsoft Dynamics, and then press ENTER.For Windows Vista, click Start, click Start Search, type %ProgramFiles%\Microsoft Dynamics, and then press ENTER.

4. Delete the GP folder

Step 3: Remove the registry subkeys for Microsoft Dynamics GP

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 - How to back up and restore the registry in Windows

1. Locate and then delete the registry subkeys for Microsoft Dynamic GP if they are present. To do this, follow these steps:
a. For Windows XP and Windows Server 2003, click Start, click Run, type regedit, and then click OK. For Windows Vista, click Start, click Start Search, type regedit, and then click OK.
b. Click the following subkey:
HKEY_LOCAL_MACHINE\Software\Microsoft\Business Solutions

c. On the File menu, click Export, type DeletedKey01, and then click Save.

d. On the Edit menu, click Delete, and then click Yes to confirm the deletion.

Step 4: Restart the computer
Restart the computer. If the uninstall was successful, you are finished and can now reinstall the Microsoft Dynamics GP if you want.

Removing stranded user sessions in Dynamics GP via SQL Server

SQL server maintains a record of active user sessions in the table SYSPROCESSES from the  MASTER  database, inside sysprocesses there is a column named “login name” and we  base  our  script  on  sysprocesses  to  clear  the  ACTIVITY  table from the DYNAMICS database. 

Once ACTIVITY table has  been  cleaned out we are ready to clean 2 tables from the TEMP database  first  we  clean  DEX_SESSION and then DEX_LOCK in order to eliminate locks and processes in temp tables. 

The next step is to clean batch activity (SY00800) and resource activity (SY00801) in order to have a valid session clean up. 

Here is the code: 

delete from DYNAMICS..ACTIVITY

  where USERID not in (select loginame from master..sysprocesses)

delete from tempdb..DEX_SESSION

  where session_id not in (select SQLSESID from DYNAMICS..ACTIVITY)

delete from tempdb..DEX_LOCK

  where session_id not in (select SQLSESID from DYNAMICS..ACTIVITY)

delete from DYNAMICS..SY00800

  where USERID not in (select USERID from DYNAMICS..ACTIVITY)

delete from DYNAMICS..SY00801

  where USERID not in (select USERID from DYNAMICS..ACTIVITY)

Note: Make  sure  you  have  a  backup  of  your  databases  when  running  scripts  that can modify your data. 

Also  I am including the KB’s published that show how to remove records from DEX_LOCK and DEX_SESSION that working together make the script I just provided. 

A batch is held in the Posting, Receiving, Busy, Marked, Locked, or Edited status in Microsoft Dynamics GP (KB 850289)

How to remove all the inactive sessions from the DEX_LOCK table in the TempDB database when you use Microsoft Dynamics GP together with Microsoft SQL Server (KB 864411)  

How to remove all the inactive sessions from the DEX_SESSION table in the TempDB database when you use Microsoft Dynamics GP together with Microsoft SQL Server (KB 864413)

Description of the 64-bit operating systems that are supported together with Microsoft Dynamics GP

To run Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 9.0 on a 64-bit computer or on a 64-bit server, you must satisfy the following prerequisites:

Note Microsoft Dynamics GP only work with a 32-bit ODBC. When Microsoft Dynamics GP is installed on a 64-bit computer, the ODBC is automatically defaulted for 64-bit and the server list will be empty. In this case, a new 32-bit ODBC have to be created.

• You must use a 32-bit Open Database Connectivity (ODBC) Data Source Name (DSN) when you try to log in to Microsoft Dynamics GP. If you use a 64-bit ODBC DSN, the server list will be empty.
  
  Note To configure a 32-bit ODBC DSN, follow these steps:
  1. Right-click Start, and then click Explore.
  2. Locate the following folder:
     C:\Windows\SysWOW64
  3. Right-click the Odbcad32.exe file, and then click Create Shortcut.
  4. Right-click the shortcut file, and then click Rename.
  5. To rename the shortcut file, type Data Sources (ODBC) 32-bit.
  6. Right-click the shortcut file, and then click Copy.
  7. Expand My Computer, expand Control Panel, and then click Administrative Tools.
  8. Paste the shortcut file in the Administrative Tools folder.
  9. Close Windows Explorer.
  10. Click Start, click Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC) 32-bit.
  11. In the ODBC Data Source Administrator dialog box, create an ODBC data source.
      
      Note Rename the ODBC data source by using a name that clearly identifies this ODBC data source as the 32-bit version. For example, use the name "Dynamics32bit."
  12. Start Microsoft Dynamics GP.
  13. Select the ODBC data source that you created in step 11.
  14. Double-click the new shortcut to open it.
  15. Reference Microsoft Knowledge Base article 870416 to create an ODBC connection for Microsoft Dynamics GP. For more information about this article, click the following article number to view the article in the Microsoft Knowledge Base:
      870416  How to set up an ODBC Data Source on SQL Server for Microsoft Dynamics GP
  Note To clearly identify the names of the shortcut files of the ODBC data sources, rename the shortcut file of the 64-bit version as "Data Sources (ODBC) 64-bit."
• During installation, remove any information that is in parentheses from the default installation path. For example, the 64-bit ODBC DSN uses the following default path:
  C:\Program Files (x86)\Microsoft Dynamics\GP\
  In this case, you must change the installation path of the following path:
  C:\Program Files\Microsoft Dynamics\GP\
  Note The Field Service notification is incompatible with any x64-based server.

-----------------------------------------------------------------------------

To run Web Services on an x64-based operating system, you must use the following workarounds.

Web Services Runtime workaround

Windows Server 2003 x64 and Microsoft Dynamics GP 10.0 only

1. In Windows Explorer, locate the system drive, and then open the following folder:
   %SystemRoot%\Windows\Microsoft.NET\AuthMon\1.2 folder
2. Drag the Microsoft.Interop.Security.AzRoles.dll file into the %SystemRoot%\Windows\assembly folder.
3. In Windows Explorer, verify that you can see the Microsoft.Interop.Security.AzRoles.dll file in the %SystemRoot%\Windows\assembly folder.
4. Install the x64 Dexterity Common Components on the IIS server. To download the x64 Dexterity Common Components, visit the following Microsoft Web site:
   https://mbs.microsoft.com/fileexchange/?fileID=2a6324c4-ce09-440b-b93d-3541dc7074e9
5. Install Microsoft Dynamics GP 10.0 Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/mdgp10_patchreleases.htm?printpage=false
6. Download Web Services Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/webservicesformicrosoft+dynamicsgp10.htm?printpage=false
7. Browse the Web Services installation folder, and then double-click the DynamicsGPWebServices.msi file.
8. After Web Services is installed successfully, see the "Web Services Management Tools workaround" section.

Windows Server 2008 x64 or x86 and Microsoft Dynamics GP 10.0 only

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756  How to back up and restore the registry in Windows

1. Refer to page 24 in the WebServicesInstallation.pdf file for the Windows Server 2008 roles and role services that must be enabled. To download the WebServicesInstallation.pdf, visit the following Microsoft Web site:
   https://mbs.microsoft.com/downloads/customer/WSInstallAdminGuide.pdf
2. Click Start, click Run, and then type REGEDIT.
3. Locate the following registry subkey, and then follow these steps:
   HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion
   1. Right-click the registry subkey, point to New, click Key, and then name the new key ADAM_Shared.
   2. Open the ADAM_Shared folder.
   3. Right-click the ADAM_Shared folder, point to New, and then click String Value.
   4. Name the new string value InstalledVersion, and then type 1.1.3790.2075 as the value data.
4. Install the x64 Dexterity Common Components on the IIS server. To download the x64 Dexterity Common Components, visit the following Microsoft Web site:
   https://mbs.microsoft.com/fileexchange/?fileID=2a6324c4-ce09-440b-b93d-3541dc7074e9
5. Install Microsoft Dynamics GP 10.0 Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/mdgp10_patchreleases.htm?printpage=false
6. Download Web Services Service Pack 3 or a later version. To do this, visit the following Microsoft Web site:
   https://mbs.microsoft.com/customersource/downloads/servicepacks/webservicesformicrosoft+dynamicsgp10.htm?printpage=false
7. Browse the Web Services installation folder, and then double-click the DynamicsGPWebServices.msi file.
8. After Web Services is installed successfully, see the "Web Services Management Tools workaround" section.

---------------------------------------------------------------------------

Web Services Management Tools workaround

This workaround is necessary for Microsoft Management Console (MMC) to work for Web Services:

1. The Microsoft Visual C++ 2005 SP1 redistributable package (x86) must be installed on the x64-based computer for the Management Tools to work correctly. To download and install the redistributable package, visit the following Microsoft Web site:
   http://www.microsoft.com/downloads/details.aspx?familyid=200b2fd9-ae1a-4a14-984d-389c36f85647&displaylang=en
2. The Web Services Management Tool installation must be started from the "Web Services" folder on CD2 or the Feature Pack DVD. Locate the Microsoft Dynamics GP 10.0 CD2 or the Feature Pack DVD, and then open the AdProd\WebServices folder. Double-click the DynamicsGPWebServicesManagementTools.msi file.

Recovering the System Menu Password in Dynamics GP

When you have logged into Dynamics GP, go to Microsoft Dynamics GP >> Tools >> Customize >> Report Writer and choose the product as Microsoft Dynamics GP. This will open GP in the Report Writer mode as shown below. Click on the Reports button in the Toolbar.
  
Click on the New button in the Report Writer window and enter the following details for the new report that you have decided to create.

Report Name	System Password Recovery
Series	System
Main Table	System Password Master
Using Key	SY_System_Password_Key1

The report definition window would look as shown below.

Now click on the Layout button. Add the Password field from the System Password Master table into the Body section of the report as shown below.
  
Close the report and choose Save on the prompt that shows up.
Click OK on the Report Definition window to close the report definition window as well. Now you should be noticing the new report that we had created in the Report Writer window as shown below.
  
Select the new report that we had created and click on the Print button. On the Report Destination window, choose to print the report on Screen and click on the OK button.
The report will print on the screen and it will display the decrypted system menu password on the report as shown below.

Dexterity Shared Components 10.0 installation Error

During the installation of MS Dynamics - Great Plains 10:
Component Installation window has everything marked off with a green check mark except the 
"Microsoft Dexterity Shared Components 10.0".  When I click the Install button, it tries to
install the "Microsoft Dexterity Shared Components 10.0" but it fails.
Error message pops up stating, "Initialization failed. Review the log file for more details: C:\DOCUME~1\Ramzy\LOCALS~1\Temp\log8.tmp".It says is 
"ERROR: One or more components failed to install correctly."
I researched it on the Internet, it says uninstall the Microsoft .NET FrameWork 2.0.
When I tried to uninstall the FrameWork2.0, I have this error: 
Microsoft .NET Framework 2.0 Service Pack 1 cannot be uninstalled 
because it will affect other applications that are installed. 
This error occurs when you have installed also the higher version of .NET FrameWork 
either version 3.0 or 3.5.
Before you can uninstall the .NET Frame Work 2.0 you should uninstall first 
from higher version down to lower version. 
e.g. from 3.5 then 3.0 then 2.0.
After uninstalling .NET Framework2.0 restart the PC.
Reinstall again the Great Plains.