Auditor is a simple background process that has no noticeable effect on performance. During data entry and processing, users cannot type fast enough to slow any processing of audits. In rare cases, if an audit is set up to track changes to records that are being batch processed, such as posting, you may see up to a 5% slowdown in the process. For instance, if it takes 10 minutes to post a batch of records, with Auditing you may see that process take an additional 30 seconds.

One potential slowdown that could be encountered is a server slowdown should the audit log fill up and overtake a SQL server. Basic planning and system maintenance of the audit log will prevent any issues arising from the audit log growing too large.

Crystal Integration is a product designed to launch Crystal Reports directly out of Great Plains Dynamics or eEnterprise. Many businesses using Great Plains tap into the reporting power of Crystal Reports. Before Crystal Integration, users had to launch separate reports outside of the Dynamics or eEnterprise environment. Now, users can launch Crystal reports from within Dynamics or eEnterprise. To the user, the integration is seamless -- which means they need less training or awareness of Crystal Reports because the reports appear to be part of the accounting system.

Note:  Dynamics Report Manager (DRM) replaced Crystal Integration in 2006.

1. Start at a workstation that has Crystal Reports and Crystal Integration both installed.
2. Open up the report in Crystal Reports. Preview the report with actual data you know is in your Great Plains system. Check that the ODBC connection is correctly set up, and that you are using an ODBC connection which is separate from the Great Plains login. Make sure the "Save Data With Report" option (under the File menu) is unchecked. Save the report, and note where on the network you saved it.
3. In Crystal Integration, look at the system settings (Reports >> Crystal Reports >>System Setup). Make sure the physical path is indeed the path you just saved the above report to.
4. In Crystal Integration, open the report in Report Maintenance (Reports >> Crystal Reports >>Report Maintenance). Verify the report physical name is the name you saved above. Also check that the parameters set up in Crystal Integration match the report definition. For testing purposes, choose the "Ask Each Time" option.
5. In Crystal Integration, select the report you set up (Reports >> Crystal Reports >>Print Reports). Enter the SAME parameters you used above. Print the report to screen. It should print.
6. Now go to a different workstation that has Crystal Integration installed, but does NOT have Crystal Reports installed. Try step 5 again. If you have problems at this workstation, the most likely cause is that the ODBC connection is not set up on this workstation identical to the setup on the first workstation. Also, make sure you are able to map to the network drive specified in step 3.

1. Optionally enter part of the beginning of the Customer ID in the Customer ID field.
2. Press the Looking Glass icon.
   
3. A new lookup window displays, sorted by Customer ID, with the optionally entered partial Customer ID from step one beginning the sort at the top.
4. Scroll, search, and find the customer desired.
5. Press Select and the Customer ID is returned to the window.

1. Type "C" into the Customer ID field. Immediately "CAB001" will fill into the field, with your cursor between the "C" and the "A". The first portion will be white as typed; the last portion will be reversed black-on-white to let you know it was auto-filled. If you press TAB, the entire value will be typed into the field.
2. Continue typing an "A" into the field. The same value will stay, but the cursor will move between the "A" and the "B".
3. Continue typing an "R" into the field. The field will now change to "CAR001", with the cursor after the "R". You can continue typing additional characters to change the ID, or press TAB to select what is auto-filled.

1. Type "Bakery" into the Customer ID field. Note we are entering the NAME into the ID field.
2. Press TAB. Immediately "Bakery" is replaced with "MAIN001".

Here are some things to check to ensure that Omni Price is setup correctly:

1. Make sure that the Omni Price dictionary is installed, Omni Price must be installed on a workstation for it to be able to work on that workstation.
2. Go to Omni Price Setup (Cards >> Omni Price >> Omni Price Setup) and check that "Activate Customer Pricing System" is checked, "Do not log details when Customer Pricing System is used" is unchecked and "User Customer Pricing even if Special Price is higher" is checked.
3. Then use the Price Check window and inquiry windows to test your contracts and filters.

The Inactivity Timeout uses a small macro file which it creates and executes "on-the-fly" to replicate the user selecting File >> Exit. This macro file was written into the application folder, the latest builds from version 7.50 onwards will now use the current user's temp folder.

If you have denied write permission to the application folder with the earlier builds it can prevent the Inactivity Timeout from exiting as it is unable to create the macro file it needs. The latest builds of version 7.5 onwards will also log the issue or failing to create the macro file, if the WDC_Debug setting in the Dex.ini file is set to LOG.

Also, it is possible that the permissons were corrupted. This can happen when a user installing Omni Tools is not logging into GP as 'sa' or a user with 'sa' rights. Run the Grant.sql script against the Dynamics database. Omni Tools Inactivity Timeout feature should begin functioning correctly.

The Automatic Check facility doesn’t take effect until the next login into GP. So, if Users did not log out of GP and back into it, the Automatic Check facility is not able to process.
 
Lastly, if the terminal session (or Citrix) times out, and that actually stops the running of the GP session, then the inactivity timeout feature would not work.  Since GP would not be running anymore, Omni Tools would not be either, so it would have no chance to do anything.

This error message can indicate a connection issue, a need to increase memory or that reports were created on a Crystal Reports version prior to version 9.0.

Recommendations;

1. Verify your DSN is set up with a SQL Server driver instead of SQL Native Client driver.

2. If the Override Report Credentials option is being used in the Dynamics Report Manager Global Reports Defaults window check to see if the Crystal Report connection was created using a SQL direct connection. If the report was created using a Trusted Connection it will need to be updated to use a SQL direct connections.
a. Open the report you are working with in Crystal Reports
b. Go to Database |Set Datasource Location
c Click to expand the properties

If you see Trusted Connection:1 listed under properties this indicates the connection was created using a Trusted Connection.

To change the connection double click on Trusted Connection and change it to Trusted Connection:0. After updating the connection make sure to Verify Database or reconnect to the SQL data source within Crystal Reports before printing the report using DRM

3. Test the ODBC DSN connection to make sure it is testing successfully.

4. Verify the DSN, username and password information in the Global Report Default settings is correct (Admin View |Global Report Defaults | Listed under Crystal Global Connections Settings).

5. If you have chosen to override the Global Report Default connection settings, verify the DSN settings for the specific report. Under Admin View, select this report and open the Connections tab. Verify the DSN, username and password information is correct here as well. Note if the Override Global Connections checkbox is unmarked then disregard this step.

6. If the report was created using a SQL commands in Crystal Reports make sure it is pointing to the correct database.

7. If you are using the Data Stream or Mass Reports feature and the process starts, but fails before finishing, check your workstation memory. It may need to be increased to handle the quantity of reports that you are processing.

8. This error message could also indicate the reports were created on a Crystal Reports version prior to version 9.0. Reports created on Crystal Reports version 8.5 will not work in DRM. If the reports were created on an earlier version of Crystal Reports they will need to be resaved in a more resent version. Please contact our technical support staff for further questions regarding this item.

Great Plains does not need to be installed in order to use DRM to print reports. Dynamics Report Launcher, however, will need to be installed.

Great Plains will need to be installed on at least one workstation to configure the reports.

Please see the "Steps to print DRM reports from workstations without" FAQ for detailed steps on how to set up the desktop shortcut.

Reports can be launched from the regular shortcut bar using the Shortcut Bar Launch Point option.

Setup Steps:

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Point
4. Select Desktop Shortcut as the Launch Point Type, enter a New Launch Point ID and click OK
5. Click on the Reports tab and select the report you would like to print.
6. Check the Access tab to ensure access is set correctly
7. Click on the Actions tab, then click the plus (+) sign. Add the action Launch all reports
8. Under the Settings tab click on Create Shortcut, then click on the Save button
9. Exit and then re-enter GP in order to refresh the Shortcut Menu and see your shortcut

Example:
The following is an example of how to print a report using a Shortcut Bar Launch Point.

1. Click on New Launch Point Launch Point Type = Shortcut Bar New Launch Point ID = Commissions Report
2. Reports tab: Click (+) and browse to my Commissions report and click Select
3. Check the Access tab to ensure access is set correctly
4. Click on the Actions tab, then click the plus (+) sign. Add the action Launch all reports
5. Settings tab: Click the Create Shortcut, then click on the Save button

Explanation:
Reports can be launched from the regular shortcut bar using the Shortcut Bar Launch Point option.

Setup Steps:

1. Log into Great Plains as a user who is set up as a DRM Report Administrator
2. Under the Admin View in DRM select Launch Points
3. Click on New Launch Point
4. Select Shortcut as the Launch Point Type, enter a New Launch Point ID and click OK.
5. Click on the Reports tab and select the report you would like to print.
6. Check the Access tab to ensure access is set correctly
7. Click on the Actions tab, then click the plus (+) sign. Add the action Launch all reports
8. Under the Settings tab click on Create Shortcut, then click on the Save button
6. Exit and then re-enter GP in order to refresh the Shortcut Menu and see your shortcut

Example:
The following is an example of how to print a report using a Shortcut Bar Launch Point.

1. Click on New Launch Point
Launch Point Type = Shortcut Bar
New Launch Point ID = Commissions Report
2. Reports tab: Click (+) and browse to my Commissions report and click Select
3. Check the Access tab to ensure access is set correctly
4. Click on the Actions tab, then click the plus (+) sign. Add the action Launch all reports
5. Settings tab: Click the Create Shortcut, then click on the Save button

 

Yes, if you want the full functionality. If you don't install on all workstations, the functionality listed below for the different modules will NOT work on the workstations where the chunk is not installed.

• Omni Password: All functionality will not work.
• Omni Menu: Cannot use interface where not installed.
• Omni Work: Cannot use interface where not installed.
• Omni Reset: Cannot use interface where not installed.
• Omni Palettes: All functionality will not work.
• Omni Login: All functionality will not work.
• Omni Notify: All functionality will not work.

The installation of Omni Tools on your Great Plains SQL versions system has not been successfully completed. The Automatic Granting code has failed for some reason. Just run the GRANT.SQL or GRANT7.SQL script from the SQL Enterprise Manager Query Analyser.

Your install may be out of date as the issue which may have caused this has been fixed. Please download the latest build located under Products | Omni Tools | Downloads.

The installation of Omni Price on your Great Plains SQL versions system has not been successfully completed. The Automatic Granting code has failed for some reason. Run the GRANT.SQL or GRANT7.SQL script from the SQL Enterprise Manager Query Analyser.

Your install may be out of date as the issue which may have caused this has been fixed. Please download the latest build located under Products | Omni Price | Downloads.

1. The Site Name, Number of Users, Site Type, Authorised Phone Number and Great Plains versions must match. The Site Name is case sensitive and must be character perfect, check for case, spaces or period (full stop) characters. This information is normally validated against the Microsoft Business Solutions VOICE database to ensure accuracy.
2. The Dates and Modules selected must be entered correctly. The AEP Renewal Date is normally 1 or more years minus 1 day into the future from the Initial Registration Date. The Registration Period dates should be blank unless using a trial period. If trial keys were previously used and now permanent keys are being entered, don't forget to remove the old trial Registration Period dates.
3. Omni Tools is sold as series so make sure all modules listed under the Active Modules section are marked.
4. A typing error was made entering the keys, please recheck. The keys are in Hexi-decimal so they will only contain the characters 0-9 and A-F. You will receive a warning if entering any other characters in the latest builds.

1. The Site Name, Number of Users, Site Type, Authorised Phone Number and Great Plains versions must match. The Site Name is case sensitive and must be character perfect, check for case, spaces or period (full stop) characters. This information is normally validated against the Microsoft Business Solutions VOICE database to ensure accuracy.
2. The Dates and Modules selected must be entered correctly. The AEP Renewal Date is normally 1 or more years minus 1 day into the future from the Initial Registration Date. The Registration Period dates should be blank unless using a trial period. If trial keys were previously used and now permanent keys are being entered, don't forget to remove the old trial Registration Period dates.
3. Omni Price is sold as series so make sure all modules listed under the Active Modules section are marked.
4. A typing error was made entering the keys, please recheck. The keys are in Hexi-decimal so they will only contain the characters 0-9 and A-F. You will receive a warning if entering any other characters in the latest builds.

Please follow these steps:

1. BEFORE upgrading, we recommend that you ensure you are running on the latest build for your current version. Please check the build number on our download page (Products | Omni Tools | Downloads). If you are not running the latest build, please install it on one workstation and say "Existing" and log into each company to automatically perform any table updates needed.
2. Make sure you have Registration Keys for your new version. You must notify us if any registration details (Site Name, Site Type, User Count) have changed.
3. AFTER completing your Great Plains upgrade download and install the latest code for the new version from the our download page (Products | Omni Tools | Downloads). Install the chunk onto one workstation on your system and say "Existing" and log into each company as a user with DBO privileges (usually 'sa'). This will ensure any table upgrades that might be needed will be run automatically.
4. Next install on the second workstation and say "New Install". If now running version 8.0 you just need to login into any company and run the wizard for one company only. If now running a version 7.X, you must run through the wizard logging into each company in turn. This will ensure that the menus are updated for the new Great Plains version. In version 8.0 menus are system based when in prior versions they were company based and needed to be updated in each company.
5. All other workstations need the chunk installed and "Existing" selected when asked. There is no need to log in. Alternatively the dictionary from the previous workstations can be copied to the application folder.

Please follow these steps:

1. BEFORE upgrading, we recommend that you ensure you are running on the latest build for your current version. Please check the build number on our download page (Products | Omni Tools | Downloads). If you are not running the latest build, please install it on one workstation and say "Existing" and log into each company to automatically perform any table updates needed.
2. Make sure you have Registration Keys for your new version. You must notify us if any registration details (Site Name, Site Type, User Count) have changed.
3. AFTER completing your Great Plains upgrade download and install the latest code for the new version from the our download page (Products | Omni Tools | Downloads). Install the chunk onto one workstation on your system and say "Existing" and log into each company as a user with DBO privileges (usually 'sa'). This will ensure any table upgrades that might be needed will be run automatically.
4. Next install on the second workstation and say "New Install". If now running version 8.0 you just need to login into any company and run the wizard for one company only. If now running a version 7.X, you must run through the wizard logging into each company in turn. This will ensure that the menus are updated for the new Great Plains version. In version 8.0 menus are system based when in prior versions they were company based and needed to be updated in each company.
5. All other workstations need the chunk installed and "Existing" selected when asked. There is no need to log in. Alternatively the dictionary from the previous workstations can be copied to the application folder.

Version 9.00 of Dexterity introduced more complex version checking for the including of Dexterity Chunks. These checks prevent a chunk file from one version extracting into a system which already has a dictionary of a different version. So, attempting to install the v9.00 chunk on top of a v8.0 dictionary will fail.

The solution is to delete the OMNITOOL.DIC and/or OMNIPRCE.DIC file and re-install the v9.00 chunks. They will install successfully now.

When Great Plains SQL versions are upgraded, the standard upgrading code will drop ALL the Dexterity Auto Stored Procedures from the databases. It then recreates the these zDP stored procedures for its own tables, but leaves them missing for Third party products, including the Winthrop products. These stored procedures are used to gain a 300% performance improvement. Without them the code will still run, but be much slower.

To fix, download and install the very latest builds and say "new install" to force the installation wizard to recreate the missing stored procedures for each company. Alternatively you can go to the About window and click the install button, then click the Advanced button to enable the advanced features of the classic installation window and then use the recreate buttons for both System and for each company.

Yes Omni Password works with Great Plains version 9.0. Omni Password can be used with GP 9.0 and SQL 2005 password policies to extended the functionality.

You can even have Omni Password work along side the functionality offered by Dynamics GP 9.0 with SQL Server 2005, Windows Server 2003 and Active Directory. This would provide an additional level of password control.

Also, there are a number of additional features like Inactivity Timeout and System Maintenance Lockout available with Great Plains 9.0 as well.

Note: The Additional Feature option to store passwords without encryption is not available on v9.0 onwards due to the password security changes made in the core application.

The Security Auditor Registration window is accessible in one of these ways, depending upon what you opted when you first installed Security Auditor:

1. Go to Help | About Microsoft Dynamics GP … From the Extras menu, choose Additional | About Security Auditor. Then choose the Register button.
2. Go to Tools | Setup | Security Auditor | Security Auditor Setup. From the drop-down, choose Registration and choose the Process button.
3. Go to Tools | Utilities | Security Auditor | Security Auditor Setup. From the drop-down, choose Registration and choose the Process button.

No. Whomever has Security access to the Auditor Group Maintenance window can add create new Form and Table groups or edit existing groups. To create a SQL Table audit the user will need at least enough SQL access to create SQL Triggers.

NOTE:
Auditor will only appear on the Great Plains menus for sa or DYNSA. Other users will need to add the Group Maintenance window to their Shortcut Bar.

Yes. Set up Auditor to track this information by tracking when the tables involved in those transactions are updated or added. Generally, when a user adds transactions, they are adding records to the tables in the system referred to as "WORK" tables. When they post, they would be adding to "OPEN" (or possibly "HIST") tables.

Example:
You would like to track which users are entering and posting Journal Entries. You can create a Table Audit to track the adds and edits to the Transaction Work (GL10000) and Year-to-Date Transaction Open (GL20000) table. The Last User field will track which user saved and/or posted the transaction.

The "Please Enter Password" dialog box cannot be audited because it is not an actual window. You can however, create a Forms audit to track when the Approval check box is being marked.

Setup Steps:

1. Create a Forms audit to audit the specific batch window you are working with
2. Mark the Batch Number as the Key Field
3. Mark to Audit (with or without Notes) the Approval check box

Auditor will track the approval once the user has checked the Approval box, entered the password, clicked OK in the Password dialog box and has either tabbed off the Approve fields or clicked on Save in the Batch Entry window

To upgrade from one version to another you will need to:

1. Upgrade your current Great Plains install, which would include Auditor
2. Copy the Auditor .cnk file, which corresponds with the GP you upgraded to, into the GP directory
3. Log into GP as sa
4. Select to install new code
5. Run the Install/Upgrade process
   

When you install Auditor, you will be offered three options from which to access Auditor windows. You can choose to install on the System Setup menu, or the Utilities menu, or not to install to any menus at all. If you choose the latter option, you can add any Auditor window to the Shortcut Bar using the procedure described below:

1. Open the Shortcut Bar
2. From the Shortcut Bar, press the Add button. Choose Other Window… from the drop down.
3. Select Auditor in the Add Window Shortcut window. Navigate to the window that you want to access and then press the Add button.
4. Press the Done button.
   

Yes, you can change the menu location of Auditor after it has been installed by following these steps:

Steps:
1. Log out of Great Plains
2. Open the Dex.ini with Notepad
3. Locate the following line item: RSALocation
4. Change the number to:
     0 = None
     1 = System
     2 = Utilities

Depending upon where you would like the Auditor to appear on the menu
5. Save the changes
6. Log back into Great Plains and the options will be in the location that you chose in step 4.

Note:  If you do not see the RSALocation line item in the Dex.ini file, this indicates that the user that installed the software was not logged into GP as 'sa' or DYNSA, which is required for GP 9 and GP 10 through build 10.0.15.  Starting with Auditor build 10.0.16, a user is not required to log into GP to install Auditor as 'sa' or DYNSA, but they MUST be logged in as a user who is either in the AUDITOR ADMIN or POWERUSER Security role for navigation to ever show up. In addition, they need to be a User that has permission to run the install process in order to get prompted for where to add the navigation, and SQL rights to create or update the tables.

You can audit if the payables check amount changes.

Example:

1. Go to Tools | Setup | Auditor Groups.
2. Enter a Group ID and Description.
3. Click the add button under the Forms section and select the Edit Payables Check form.
4. In the Auditor Form Maintenance window select Edit Payables Checks on the left .
5. Locate the Voucher Number and click on the Key Field.
6. Locate the Current Trx Amount and click on the Auditor or Audit w/note field.
7. Click Ok.
8. Click on Save to save the audit

The Security Auditor Registration window is accessible in one of these ways, depending upon what you opted when you first installed Security Auditor:

1. Go to Help | About Microsoft Dynamics GP … From the Extras menu, choose Additional | About Security Auditor. Then choose the Register button.
2. Go to Tools | Setup | Security Auditor | Security Auditor Setup. From the drop-down, choose Registration and choose the Process button.
3. Go to Tools | Utilities | Security Auditor | Security Auditor Setup. From the drop-down, choose Registration and choose the Process button.

Typically when an Audit is not tracking changes it is due to expired registration keys. There are a few other reasons why an Audit may not be tracking the changes, so you will need to verify and complete the steps listed below:

1. Verify the registration keys have been entered and are valid (Auditor Setup Window | Registration | Process).
2. Verify Auditor is installed on each workstation (or terminal server) and server
3. Run the Rebuild SQL Table Master process (Auditor Setup Window | Rebuild SQL Table Master | Process).
4. Run the Rebuild SQL Triggers process (Auditor Setup Window | Rebuild SQL Trigger | Process).
5. If the audit doesn't require a note, update the audit to require a note. Run a test to see if you are getting prompted to enter the note.
6. Auditor will stop tracking changes if the workstation build is out of sync. In other words, Auditor will not track changes on the client machine if the Server has build 22 installed and the client machine has a different build number (e.g., build 21) installed.
7. On Forms audits, users must tab off the changed field in order for Audit to capture the change.
8. On the Audit Group window  open your audit group and click on the Admin menu, then select Rebuild All Tables and Forms
9. The Audit Group window must be closed.

If after checking and/or completing the above steps the audit is still not tracking changes, please export the audit and send it to us at support@rocktonsoftware.com, with an explanation of your desired results.

Pressing the Print Button gives a print dialog with output options, and a choice of three reports:

1. Security Settings (current view): A quick listing of what you have selected in the Security Manager window
2. Exclusions with Segregation of Duties Conflicts: A list of users whose security settings violate each given Exclusion ID. Exclusions are set up in the Segregation of Duties Groups window.
3. User Segregation of Duties Conflicts: A list of violated exclusions listed by each user.

Only one company's security can be managed at a time. Choose the desired company from the Company drop-down list at the top of the window. Next, choose a Filter. Filters are how you tell Security Manager which objects to display.

For Filters that contain Roles, you can choose the level of detail that you want to see from the View drop-down at the upper, far right. You can choose to list only the Roles, or you can choose to see the Roles and the Tasks within each Role (organized by Category), or you can choose to see the Roles, the Tasks that make up each Role, and the Details (Security Operations) that make up those Tasks.

When viewing the z.ALT-MOD IDS default Filter, you can choose whether you want to see all Alternate and Modified versions of the objects listed, or only the Alternate versions or only the Modified versions.

By clicking the Select Users button you can select whether to view all users or just selected ones. By selecting specific users, you can wade through the clutter of viewing all of them at once. Note, however, that only Users that have access to the selected Company will be shown, regardless of which ones are chosen in the Select Users window.

This error message indicates the SQL Tables MSTR needs to be rebuilt.

Recommendation:

1. Log into GP as sa
2. From the Auditor Setup window select the Rebuild SQL Table Master and click Process
3. Next from the Auditor Setup window select to Rebuild SQL Triggers and click Process
4. Finally, from the Auditor Setup window select to Install/Upgrade and then click process again
   
   

Running the Reconcile process should eliminate this message if you are getting this message in error.

Recommendation:
Below are the steps you will need to take to clear this error message.

1. Open the Auditor Setup window.
2. Choose Reconcile from the drop-down and click Process.
3. On the Reconcile window, you can first choose the Integrity Check option, which will give you a list of the things that it finds that it can correct. Then, if this list looks OK, you can run the Remove Stranded Items option to actually clean things up
   
   NOTE: See the What does the Auditor Reconcile process do and The Integrity Check report prints errors. How do I fix them FAQs for further information on the reconcile process and the messages you may see after running the Integrity Check.
   
4. Try deleting the Auditor group and importing the Group again.

This message was added to recent builds of Auditor so users know why Great Plains is taking some time to initialize. Users will see this window any time Audit Groups are defined and active. This message indicates the audits (triggers) are being started.

Note:  This applies to only those Users that are Auditor Administrators on the Auditor System Settings window. Users who are not an Auditor Administrator will not see the initializing message when logging into Dynamics-GP.

In order for Auditor to track the changes it is necessary for the users to have access to the following items, which are all under the Product Auditor, Type Windows, Series System.

For GP 9:
  Auditor Progress
  Auditor Note Maintenance
  Auditor Dummy Window
  Auditor Explorer Background

For GP 10 and 2010:
  Approval Inquiry
  Approvers
  Auditor Note Maintenance
  Code
  Enter Approver Password
  E-Sign Approval Needed
  E-Sign Approvals
  E-Sign Pending Approval Requests
  Register Rockton Products

In addition, under the Product Auditor, Type Windows, Series 3rd Party, they will need access to the following item.

For GP 10 and 2010:
  About Auditor

You can safely remove access from the following Auditor windows and still have auditor track the changes the user makes.

Product - Auditor
Type - Window
Series - System
Windows - Auditor Inquiry and Auditor Groups

Product - Auditor
Type - Window
Series - 3rd party
Windows - Auditor Registration and Auditor Setup

The spSmartFill.sql file is a template for a SQL Stored Procedure that can be used to add functionality to your lookups that could not otherwise be done through the SmartFill windows. For instance, if you want to search using a complex series of JOINs to several different tables, you could use this stored procedure to do it.

If you do use this stored procedure, you will also have to set the search type to Custom SQL on the Object Maintenance window in SmartFill.

This is a modification you can make to the Repository to get around this problem:

1. Close the Purchase Order Entry window.
2. Go To Tools > Setup > System > SmartFill Repository.
3. Select Vendors in the Objects drop-down.
4. Now search thru the list for the Repository entry for the Vendor ID field on the POP_PO_Entry form/window. Select this record; then click the Modify button on the right.
5. On the Modify Repository Record dialog, click the "Skip running change script for this field" box and click OK.
6. Click OK to close the Repository Maintenance window.

Now open the Purchase Order Entry window and try it again. This time it should bring back the vendor, but the Vendor ID field will still be editable, as if you just entered it manually. Tab off the field and it should now behave normally. You should only have to make this change once, from one workstation, and it should correct the problem for all workstations.

In order to update the PO status when printing the Crystal Report you will need to write a stored procedure that does two things and then create the PO using the stored procedure. First it will need to return the data for the report to run, and at the same time it runs an UPDATE on the flag. The stored proc should receive the PO Number as the parameter. Using it this way, the flag gets updated at the time you run the Crystal Report.

NOTE:  This script updates just the header. It is a sample ONLY and may not accomplish updating all the data that needs updating. If you need more updating you will have to write it, or you may contract it with Rockton Software to be written.

Example:
Here is an example Stored Procedure which will return the data for the report and then update the PO Status flag:

--run against company database
--EXEC spCrystalPO 'PO2076'
IF EXISTS(SELECT * FROM sysobjects WHERE NAME = 'spCrystalPO') DROP PROC spCrystalPO
GO
CREATE PROC spCrystalPO
(@PONumber CHAR(17))
AS
BEGIN
UPDATE POP10100 SET
LSTPRTDT = CAST (STR(MONTH(GETDATE())) + '/' + STR(DAY(GETDATE())) + '/' + STR(YEAR(GETDATE())) AS DATETIME),
POSTATUS = 2,
TIMESPRT = TIMESPRT + 1,
PO_Status_Orig = 1
-- UNSURE OF FIELDS ONORDAMT, ORORDAMT, AND PO_Field_Changes
WHERE PONUMBER = @PONumber
SELECT * FROM POP10100 WHERE PONUMBER = @PONumber
END
GO
GRANT EXECUTE ON spCrystalPO TO DYNGRP
GO

The first thing you will want to verify is the Parameter name.  The Parameter name in SRS must match the Parameter Name field in DRM. 

Next, check to see how the parameter was created.  When DRM creates the URL it will trim off any blank spaces in a parameter.  For example, say your parameter is SOP Number.  If the parameter was not created to trim nulls after the SOP Number when DRM passes the parameter, it will drop these null characters.  The result is DRM is passing the incorrect parameter values and a blank report is displayed.  In this case the parameter will need to be updated in SRS to trim null characters.

 Below is a list of items you will want to check:

1.  Verify you are on the latest build of DRM. Check out the Rockton Software website for updated version information.

2.  Verify you have the latest version of Dynamics Report Manager Launcher for Crystal installed and DRMCI11.exe file loaded in your Great Plains application folder.

3. Check the Windows Print settings for the printer used to print the report in question

If you still continue to have trouble, please do the following:

1.  Uninstall and reinstall the Launcher by going to your Start | Settings | Control Panel | Add or Remove Programs. Remove the Dynamics Report Manager Launcher for Crystal 11.5

2.  Go to the Rockton Software website and download the DRM Launcher for Crystal Reports Part 1 of 2, making sure it gets saved to your GP applications folder.

3.  Then download Part 2 of 2 where there is a DRMCI11.exe file.

4.  Copy the DRMCI11.exe file into the GP applications folder and click on Yes to replace existing file.

5. Then try printing your report in Landscape again.

Lastly, some .dll files from Crystal Reports version 8.5 or older, may cause issues with DRM. These files are loaded with older versions of Crystal Reports typically, but may also be loaded from other 3rd party products. Even if you have never had Crystal  Reports loaded on your machine, you may still have these files and will need to check their version information as they may have been loaded from another product.

If you find these two files you will want to check the version information for the files, which is normally found under the properties tab (right-mouse click on the file | Properties | Version).

cpeaut32.dll
crpe32.dll

Then you would need to determine which program installed the files. If you had Crystal Reports 8.5 installed then you would  need to use the Uninstall steps outlined below to manually uninstall it.  NOTE:  These steps are from Crystal Reports (Business Objects) and we STRONGLY RECOMMEND that you do a BACKUP prior to deleting the files. If another product installed the files then you would need to contact the other 3rd party company to see if there is an updated version of the product you can install. These files are outdated and developers shouldn’t be using them when developing products or updates to products anymore.

Uninstalling Crystal Reports 8.5
////////////////////////////////
Before getting started, uninstall CR by launching the Setup.exe file from the installation CD or by using the 'Add/Remove Programs' command. If either of these methods fail to remove all of CR's directories, files and registry keys, then continue with the resolution of this article.

==========
WARNING:
This resolution can be applied if Crystal Reports is the only software installed on the computer that uses the Seagate Software directories, files and registry keys.

For example, Seagate Info, Seagate Analysis, Crystal Analysis, Crystal Enterprise are applications that may share the same directories, files and registry keys.

Removing these directories, files and registry keys may cause other software to function incorrectly.
==========
1. To manually uninstall Crystal Reports 8.5, delete the following
directories:
* C:\WINNT\Crystal
* C:\Program Files\Seagate Software\Crystal Reports

2. Find the following files and delete those that are Crystal Version 8.0, or previous (right-mouse click on the file | Properties | Version):
* cpeaut32.dll
* cpeaut32.dep
* crystl32.ocx
* crystl32.dep
* crystl32.oca
* crrun32.exe
* crpe32.dll
* crpe32.dep
* p2sodbc.dll
* p2bbnd.dll
* p2bdao.dll
* p2ctdao.dll
* p2irdao.dll
* p2sevt.dll
* p2smon.dll
3. Find and delete the following registry keys:
====================
WARNING:
Using the Registry Editor can cause serious problems that may require reinstalling the operating system. Business Objects is not responsible for any problems resulting from using the Windows Registry Editor. Use the Registry Editor at your own risk. It is recommended that you back up the registry before you edit it.
====================
* HKEY_LOCAL_MACHINE\SOFTWARE\Seagate Software
* HKEY_CURRENT_USER\Software\Seagate Software
* HKEY_USERS\S-#-#-##-...-####\Software\Seagate Software (The number signs
(#) represent a series of numbers that are different on each computer.)

This error message is generated when the Crystal Integration exe file is in the Great Plains application folder and is referenced in the Crystal Report Engine field of the Dynamics Report Manager System Settings window. 

Recommendation:

1. Remove the RSCI.exe file from the Great Plains application folder

2. Update the Crystal Report Engine field in the Dynamics Report Manager System Settings window to point to the DRMCI11.exe file

The Change Date pop-up message in Great Plains will stop DRM from printing reports after midnight.  DRM will wait to print the report until a user has completed one of the actions on the pop-up window. 

To get around this a user could create a macro to complete the process on the pop-up window.  Another option would be to use the following information found in Microsoft Dynamics Knowledge Base Article ID 859198 (Title: How to turn off the “ Would you like the user date to change” message that appears at midnight).

Microsoft Dynamics Knowledge Base Article ID 859198:

If you are using Microsoft Dynamics GP 10.0, 9.0 or Microsoft Great Plains 8.0, add the following line above the "[Install]" section of the Dex.ini file. If you are using Microsoft Great Plains 7.5, add the following line to the very bottom of the Dex.ini file: SuppressChangeDateDialog=TRUE

NOTE:  If you turn off the pop-up message the user date is not updated.  So if you are running a report which is date sensitive, this option may not work for you.

If you are on the latest build of Dynamics Report Manager (DRM), go to Tools>>Setup>>Dynamics Report Manager>>Dynamics Report Manager Setup. From the drop-down menu, select Show Floating Toolbar, then click on the Process button.

On older builds of DRM where the above option is not available, we track the coordinates of the window when it opens.  In this case the coordinates may be too high and are off the screen.  This could happen if the screen resolution changes from high-resolution to low.

You will need to check and update the DRM_System_Setting_Key values in the DRM001 table in the Dynamics database.

Steps to update the coordinates of the Toolbar:

1. Run the following script.

NOTE: The ToolbarHorz, ToolbarVert and ToolbarStickPin values are user-specific. These values will need to be updated to reflect the user who is experiencing this issue. To do this, change USERID in each of the SQL statements below to be the User ID of the user you are trying to correct (e.g., ToolbarHorzLESSONUSER1, etc.).

USE DYNAMICS

UPDATE DRM001 SET DRM_System_Setting_Value = '100' WHERE DRM_System_Setting_Key = 'ToolbarHorzUSERID'

UPDATE DRM001 SET DRM_System_Setting_Value = '100' WHERE DRM_System_Setting_Key 'ToolbarVertUSERID'

UPDATE DRM001 SET DRM_System_Setting_Value = '0' WHERE DRM_System_Setting_Key = 'ToolbarStickPinUSERID'

2. Back in Great Plains click on “Close All Windows” (Microsoft Dynamics GP | Close All Windows).

3. Check the Toolbar

Yes.  Make one more parameter in the report and make the last one.  Give your parameter a name and unmark the option “Pass this parameter” on the parameter options window.  Now this information can be used to create the output filename.

Example:  If you are printing an Invoice where the SOP number is setup as the only parameter and you would like to include the Customer Name in the filename.  Create a parameter called the Customer Name and unmark the “Pass this parameter”.  When creating the parameter you can also attach a lookup to make it quick for the end user to pull in the parameter values. Now when creating the output file name you can include the customer name.

Forms Printer uses a temporary table that fills with custom data when reports are run from the SOP Entry screen and other screens from where they are launched.  Launching a specific Forms Printer report from DRM can be done but will often yield no data because the underlying database tables are not populated with data the correct way.

In order to use a Forms Printer Crystal report, the report would need to be modified to not use custom ASI* tables, that is tables that start with ASI.  This can be done, but takes modifying of the report to not be based on ASI tables.

This will happen if the latest build wasn't installed on all workstations that currently have DRM installed.

Example: Let's say they just installed 10.0.5 on workstations A and B, but C is still on 10.0.3. When C logs in, they will get a message saying that they need to update because they server says they should be on build 5. So they run the Update, which sets the DRM001 record to build 3. Now, when A or B logs in, they will get the message asking them to update because the server says they should be on 10.0.3. So it bounces back and forth like this. So the solution is to install build 5 on C. Check the DRM About Box or Setup window to find all of the workstations that are not on the current build.

Recommendation: Install the latest build on all workstations. Check the DRM About Box or Setup window to determine which workstations currently don't have the latest build installed. You could also download and install our free Version Pro product.

Version Pro keeps track of each product you have installed at a system level - and takes the next step in ensuring that each and every workstation on your network is on the same version for every product. Contact our Sales or Support team for Version Pro registration keys (sales@rocktonsoftware.com or support@rocktonsoftware.com).

Typically there are four setting issues which cause the report not to launch. You will want to make sure:

1.  The Report Server is specified correctly in the SQL Reporting Server Virtual Directory field in the Dynamics Report Manager System Settings window. 

2.  Verify the Report Server specified in the SQL Report Server Virtual Directory field also matches  the Report Server information in your administrative panel by going to Start | Programs | Configuration Tools | Reporting Services Configuration.

3.  Verify the Report Technical Name is listed in the correct format (/Project/ReportName)

4.  Finally verify the parameter name on the report match the parameter name in DRM.

NOTE:  See the “I cannot get any SQL Reporting Services reports to work? Any ideas?” FAQ for additional information on setting DRM up to print SRS reports.

This error may be generated due to an incorrect report path in the Report Technical Name field in the Report Maintenance window, or from a SQL View or Stored Procedure used in the Crystal Report.

Recommendations:

1.  Verify the correct report path name is listed in the Report Technical Name field of the Report Maintenance window.  If the report is in a shared drive make sure the correct UNC path is listed.

2.  If the report was created using a SQL View or Stored Procedure try running a simple select statement in SQL Management Studio to pull the same data to see if you are getting error messages.  If you are getting error messages you will want to recreate the SQL View or Stored Procedure, so it is pulling the data correctly.

The Error 429 ActiveX message indicates the DRM Crystal report launcher is out of date.  The updated version of the launcher file will need to be installed. 

Recommendation :

Use the following steps to update your DRM Crystal Launcher

1.  Using Add/Remove Programs uninstall the Dynamics Report Manager Launcher for Crystal 11.5.

NOTE: Uninstalling the Launcher file will not remove any of your current DRM setup or settings.

2.  Download and install the Dynamics Report Manager Crystal Launcher for Crystal. This is labeled Part 1 of 2. The file downloaded will be titled DRMLauncherCR11SetupC.exe. This Installshield package will install the Crystal Components used for launching Crystal reports. It must be installed on every workstation or server where printing will occur. Make SURE you install it to the Great Plains installation directory.  

3.  Copy the DRMCI11.exe file from the DRM build you recently installed and paste it into the Great Plains application folder. Select Yes to overwrite the file you installed in step 2.

A: Yes, however actual passwords don’t show up in the Audit log.  The Audit log will list XXXXXXXX for the before value and YYYYYYYYY for the after value.

In order to track changes to the password an Audit will need to be setup for the Great Plains User Master Table (SY01400).  Then check the box in the Audit column for the Password field.

Here is a list of common things we see our customers setting up Groups to audit:

1. Vendor Check Name
2. PO Price
3. SOP Sales Price
4. Customer Statement Name
5. Multi-Currency Valuation Change
6. Changes to users and user permissions (Security Auditor can assist in this as well)

The setup time is going to depend on how well the user completing the setup is familiar with the Great Plains windows/tables.  The actual setup of an Audit only takes minutes.  The majority of the time will be spent preparing and understanding what you would like to Audit.
 
To be sure you have what you need to complete the Auditor setup and to help expedite the process, prior to setting up Auditor we recommend the administrator setting up the Audit Groups:

1. Knows what Audits they need to setup
2. Knows what types of Audits they would like to use (Form, Table and/or SQL Table)
3. Knows if they are going to use a specific method or grouping to create their Audit Groups (example: Accounting Group, Sales Group, Payroll Group, etc.)
4. Familiarizes them self with or researches the Form, Table and/or SQL Table information they will need to setup their Audits

This error is generated when a group contains SQL Table audits on tables or databases which no longer exist. During the install, it tries to rebuild all the SQL triggers and if the table or database doesn’t exist anymore it results in this error message.  If you only have a few Audit Groups defined look at all of the SQL Table audits to see if any of them no longer exist.  If you find any you will want to delete them and then run the install process again.

If you have a number of Audit Groups you can create a DexSQL.log during the install process to capture the error message and then send it to us at support@rocktonsoftware.com.

This will happen if the latest build wasn't installed on all workstations that currently have Auditor installed.

Example: Let's say they just installed 10.0.6 on workstations A and B, but C is still on 10.0.3. When C logs in, they will get a message saying that they need to update because the server says they should be on build 6. So they run the Update, which sets the RSAS003 record to build 3. Now, when A or B logs in, they will get the message asking them to update because the server says they should be on 10.0.3. So it bounces back and forth like this. So the solution is to install build 6 on C. Check the Auditor About Box or Setup window to find all of the workstations that are not on the current build.

NOTE:  Auditor will not track changes if the workstation build is out of sync. In other words, Auditor will not track changes on the client machine if the Server has build 6 installed and the client machine has a different build number (e.g., build 3) installed.

Recommendation: Install the latest build on all workstations. Check the Auditor About Box or Setup window to determine which workstations currently don't have the latest build installed. You could also download and install our free Version Pro product.

Version Pro keeps track of each product you have installed at a system level - and takes the next step in ensuring that each and every workstation on your network is on the same version for every product. Contact our Sales or Support team for Version Pro registration keys (sales@rocktonsoftware.com or support@rocktonsoftware.com).

To track changes to the User Access (SY60100) table you will need to setup a SQL Table Audit to track Adds and Deletes.  When a company checkbox is checked this will be tracked as an Add, and when a company checkbox is unmarked it will be tracked as a delete.  The Record Key will include the company ID information which is used to determine which company security was granted or removed from.

For additional information you can double click on the Audit information in SmartList. In Great Plains 10 you also drill into the Audit Reference Field window by clicking the blue arrow in the Record Key field of the Audit Inquiry window. Our Security Auditor product tracks user access automatically.  If you would like further information regarding Security Auditor please contact us at Sales@RocktonSoftware.com.
 

You can use the Lookup Creation Wizard to add SmartFill functionality to current objects.  Go to Tools | Setup | SmartFill | Repository | New to open the Lookup Creation Wizard.  The Wizard will walk you through updating the Repository with additional fields.  The Wizard allows you to browse to the specific window and field to which you would like to add SmartFill functionality.

Example: The following steps outline how to add SmartFill functionality to the Vendor ID field in the Return Transaction Entry window.

1. Tools | Setup | SmartFill | Repository | New and click Next
2. Select the Vendor Object and click Next
3. Browse to the Return Transaction Entry window and place your cursor in the Vendor ID field (Transactions | Purchasing | Return Transaction Entry)

4. Click Add Lookup
5. Click Finish in the Lookup Creation Wizard window to save your changes.

Yes.  You can also use the new Field Mapping feature in SmartFill to accomplish this. 

Field Mapping is available only for table fields (i.e., it is not available for constant
values). The only types of fields that can be mapped are ones that have a string
datatype, or a numeric datatype that is not a Currency type. For instance, Integers and
Drop-down List fields can use Field Mapping; Date fields and Currency fields cannot.

This error message is indicating there is a link missing in the Secondary Table setup of the Address Object. 

Recommended Steps:
1. Log into GP as sa
2. Go to Tools | Setup | SmartFill | Objects
3. Select to Edit the Address Object
4. Click on the blue arrow in the right of the Table Name field.  This will open the SmartFill Object Secondary Tables window.
5. Highlight the RM_Customer_MSTR table and click on the plus symbol under the Links section.
6. Under the Primary Table Field section select the Customer Number
7. Under the Secondary Table Field section select the Customer Number
8. Click Link, Ok and Ok to Save the changes and close the SmartFill windows.

This error is appears when there are a large number of Roles, Tasks & Details trying to be displayed, which is a known issue with Security Auditor 10 build 2 (10.0.2).  This issue has been addressed in build 3.

Recommendation:

Upgrade to the latest build of Security Auditor.

The setup time is going to depend on how well the administrator setting up the security is familiar with the Great Plains and what the security settings your organization needs setup. The actual setup may only take minutes.  The majority of the time will be spent preparing and understanding your organization’s security needs. 
 
To be sure you have what you need to complete the Security setup and to help expedite the process prior to setting up Security, we recommend the security administrator:

1. Determine if they will be using Segregation of Duties, and if so, outline how they would like to set these up.
2. Determine if they would like to create specific filters to help organize and manage security.
3. Have a good understanding of what the security settings will be before they start the setup.

This will happen if the latest build wasn't installed on all workstations that currently have Security Auditor installed.

Example: Let's say they just installed 10.0.3 on workstations A and B, but C is still on 10.0.2. When C logs in, they will get a message saying that they need to update because the server says they should be on build 3. So they run the Update, which sets the RSSA001 record to build 2. Now, when A or B logs in, they will get the message asking them to update because the server says they should be on 10.0.2. So it bounces back and forth like this. So the solution is to install build 3 on C. Check the Security Auditor About Box or Setup window to find all of the workstations that are not on the current build.

Recommendation: Install the latest build on all workstations. Check the Security Auditor About Box or Setup window to determine which workstations currently don't have the latest build installed. You could also download and install our free Version Pro product.

Version Pro keeps track of each product you have installed at a system level - and takes the next step in ensuring that each and every workstation on your network is on the same version for every product. Contact our Sales or Support team for Version Pro registration keys (sales@rocktonsoftware.com or support@rocktonsoftware.com).

Recommendations:

Everyone must be logged out of Microsoft Dynamics Great Plains on the terminal server.
Ensure the permissions on the folder containing the .cnk file are not read-only for the current user.
Make sure that the Dex.ini, dynamics.set and *.dic and *.cnk are not marked as read-only.
Log in as Admin to install and setup.

WARNING: Before uninstalling CE, make certain that any files you wish to retain have been backed up or moved to a new directory location. This is especially important if the computer stores Crystal Reports files as this method will remove all Crystal Decisions products.
===========

After using Add/Remove Programs to remove CE, complete the following steps to completely uninstall CE:

1. Open Windows Explorer and expand the %systemroot% directory. For Windows NT 4\2000 this is generally the Winnt folder.

2. Delete the \Crystal subdirectory and its contents.

3. Expand the \System32 subdirectory on Windows NT 4\2000. Find the following files and delete those that are Crystal Version 8.0, or previous (right-mouse click on the file | Properties | Version):

Crbas*.*
Crdb*.*
Crgup*.*
Crheapalloc.dll
Criadx*.*
Crinf*.*
Cror*.*
Crpaig80.dll
crpe*.*
Crsyb*.*
crutl*.*
Crxml*.*
Ebus-3*.*
Etc-1-*.*
Exlate32.dll
Htmlr*.DLL
nsclient.dll
OMNI*.DLL
p2bdao.dll
p2ctdao.dll
p2irdao.dll
p2sevt.dll
p2sodbc.dll
p3ddoen.dll
p3rdoen.dll
p3seven.dll
p3soden.dll
p3tdoen.dll
r3exlen.dll
STRINGres_en.DLL

4. Expand the Program Files folder and delete the Seagate Software subdirectory and its contents. If you installed to a different directory, remove that directory as well. (By default, some files will always be installed to the Program Files\Seagate Software directory.) If you are using Crystal Enterprise 8.5 you will also need to remove the Program Files\Crystal Decisions directory.

5. For Crystal Enterprise 8.0 you will need to delete the Seagate Software registry keys using the Windows Registry Editor as follows:
a. Click Start > Run, type "Regedit" and click 'OK'.
b. Expand HKEY_LOCAL_MACHINE\SOFTWARE. Delete the Seagate Software subkey.
c. Expand HKEY_CURRENT_USER\SOFTWARE. Delete the Seagate Software subkey.
d. Close the Registry Editor.

Crystal Enterprise is now completely uninstalled.

Also, ensure that you do not have multiple versions of the MSVBVM60.dll file existing. Please follow these steps: 

1.  Do a complete search on the workstation and server to find all of the MSVBVM60.dll files.
2.  Right-mouse click on each MSVBVM60.dll file in your search results to find the most recent version
3.  Overwrite the older MSVBVM60.dll files with the most recent version of the file.
4.  Copy the most recent version of the MSVBVM60.dll  to the GP Application folder

Steps:

1.  Open SmartFill objects
2.  Open customer object
3.  Click the blue arrow to the right of Table Name field
4.  Under Secondary Tables, click Plus+ to add new table
5.  Product: MS dynamics GP
6.  Series: Sales
7.  Choose RM _CUSTOMER_MSTR_SUM table, click on Select
8.  Fields (left side) select customer Number | Fields (right side) select Customer Number
9.  Click the Link button
10. Click on OK
11. Choose next available line in the Lookup Fields area
12. Choose Table RM_Customer_MSTR_SUM from the down arrow and Customer Balance from Field Name down arrow 13. Check the box to Display.
14. Adjust your width to equal a total of 100%

Recommendation:

Uninstall .NET 2 SP1 and .NET 3 SP1, then reboot.

It doesn’t matter for any of our software what machine you use to install our applications. However, since our products improve the GP application, our products should be installed everywhere the GP application is installed, provided the functionality is needed on every instance of the application.

In the case of Omni Tools, it simply must be installed on all workstations and/or servers where the functionality of Omni Tools is desired.  It is recommended to install the .cnk file on every workstation for consistency.  However, if you choose to not install Omni Tools on certain workstations, those workstations will not have the Omni Tools functionality.

For GP 10, to make the Omni Tools – Omni Login window not open when you open User Preferences, you need to remove access to this window from the DEFAULTUSER task:

1. Go To Microsoft Dynamics GP >>Tools >>Setup >>System >>Security Tasks
2. Select the DEFAULTUSER task
3. Select Product Omni Tools, Type Windows, Series System
4. Uncheck Omni Tools – Omni Login

This will remove access to this window for ALL Users.  If you still want to use any of the Omni Login features, then someone will need to have access to this window, so they can set it up. One way to do this is to allow access to the Omni Tools Administrators:

1. Go To Microsoft Dynamics GP > Tools > Setup > System > Security Tasks
2. Select the ADMIN_OMNITOOLS_01 task
3. Select Product Omni Tools, Type Windows, Series System
4. Check Omni Tools – Omni Login