Page 1 of 3012345678910...202530...Last »

#GPPT GP Power Tools build 21 released

David Meego - Click for blog homepageI am pleased to announce that the next build of GP Power Tools for Microsoft Dynamics GP (GPPT) is now available for download.

GP Power Tools was previously known as Support Debugging Tool (SDT), which was discontinued in October 2014. If you are still using the previous product, please upgrade to the supported and much better GP Power Tools product.

This build adds support for Microsoft Dynamics GP 2016 as well as separating the product into three modules and adding a host of new features and enhancements to the tools. Details on the changes will be posted on this blog in an upcoming “What’s New” series.

Build 21 of GP Power Tools is available for the following Microsoft Dynamics GP versions:

  • Microsoft Dynamics GP 2010 (v11.0),
  • Microsoft Dynamics GP 2013 and GP 2013 R2 (v12.0),
  • Microsoft Dynamics GP 2015 and GP 2015 R2 (v14.0)
  • Microsoft Dynamics GP 2016 (v16.0).

GP Power Tools will now be sold as three modules which can be bought separately, with some standard features available when any module is registered. The three modules and their features are:

Administrator Tools

  • Resource Information, Security Information, logging and Analysis, Company Color schemes, and Usability enhancements, Automated Dex.ini configuration, Dictionary Control troubleshooting tool.

Developer Tools

  • Scripting for Dexterity, SQL Server, Visual C# and Visual Basic.Net. Triggers for both debugging and customisation. User interaction with scripts via Parameter Lists. Custom RW functions and custom Service Based Architecture web services.

Database Tools

  • Database Validation to check User and Company settings as well as Table structures. Export and Import of data via XML files.

The following System Module features are available when any module is registered:

  • Manual Logging, capturing screenshots, email and workstation Dex.ini settings

The primary new features for build 21 are improved Company Color scheme functionality, Parameter Lists for requesting information to be used in scripts from the users and the Security Analyzer tool. More details on these and other enhancements will be posted soon. The User Guide manual has grown from 257 to 275 pages.

Note: With the release of build 21 of GP Power Tools, the special introductory price offered since the release of build 20 has now finished.

Version History

Below is a summary of the changes made for releases 11.00.0021, 12.00.0021, 14.00.0021 and 16.00.0021, I have divided them into logical sections:

System Wide

  • Update Registration System to separate the product into modules.
  • Allow Preview Mode for windows when GP Power Tools system module is registered and additional modules are not.
  • Fixed issue where Menu and Area Page Navigation was not active immediately after install and required a restart of Dynamics GP.

Settings (Logging Settings, Email Settings and Administrator Settings)

  • Moved Email settings from Email 1 and Email 2 tabs of Administrator Settings window to new Email Settings window.
  • Moved Logging settings from Administrator Settings window to new Logging Settings window.
  • Re-organized settings on Administrator Settings windows to more logical tabs and improve visual layout.
  • Added “Disable logging of Security Errors and Warnings to the user/company log files” option to Administrator Settings window.
  • Added option to control how Settings Applied Message is displayed to Administrator Settings window.
  • Added “After Login warn user when password is due to expire (SQL Server 2008 or later)” option to Administrator Settings window. Based (with permission) on idea from Michael Johnson who used to work with Straight Arrow Consulting.
  • Added Field Background and Scrolling Window Background to Company Color Schemes in Administrator Settings window.
  • Added Automatic changing to Text color when backgrounds are dark to Company Color Schemes in Administrator Settings window.
  • Added additional Grey Themes and new Mid, Dark and Inverted Themes to Company Color Schemes in Administrator Settings window.
  • Added Red, Green, Blue and All color spinner controls with Selected checkboxes for easy color manipulation in Adminstrator Settings window.
  • Total built in themes for Company Color Schemes is now 92 themes.
  • Updated Administrator Settings window to support Custom Color Themes.
  • Added Custom Color Themes Setup window to allow creation and editing of custom color themes.

Dex.ini Settings

  • Improved Dex.ini Settings window to improve visual layout.
  • Updated Dex.ini Settings window to add fields for WindowMax, WindowPosX, WindowPosY, WindowWidth, WindowHeight Dex.ini settings.
  • Updated Dex.ini Settings window to add control of OLEClose Dex.ini setting, which can improve performance when exiting Dynamics GP.

Database Validation

  • Added Activity Log Report to Database Validation when the window is closed instead of writing to User/Company Log files.
  • Added Mark All and Unmark All buttons to lists on User & Company Fix and Tables Fix windows of Database Validation.
  • Added Option to remove SQL Logins from Database Validation window, so SQL Logins and Database Users can be recreated.
  • Added Initializing Database Validation Progress window to Database Validation.

SQL Execute

  • Added All Company feature to SQL Execute window to allow a single query to be executed against multiple companies in the system.
  • Added Export to File and Email option to the SQL Executer window to allow export of query results.
  • Added Resizing of SQL Execute and SQL Executer Column Widths to ensure Column Label is readable when data for the column is narrow.

Security

  • Added option to Display only Selected Users for the User and Company views in the Security Information window.
  • Added support for OData Security Objects to Resource Explorer and Resource Information windows for version 16.00 onwards.
  • Added support for OData Security Objects to Security Information, Security Profiler and Security Log windows for version 16.00 onwards.
  • Added Security Analyzer window to analyze application level security and provide data to administrators.
  • Added background processing to Security Analyzer window along with query filtering when double clicking.
  • Added a confirmation dialog to Security Analyzer window when the query will return more than 5000 rows.

Parameter Lists

  • Added Parameter Lists and Color Themes to Configuration Maintenance window.
  • Added Parameter Lists and Color Themes to Configuration Export/Import window.
  • Added Parameter Lists and Color Themes to Setup Backup and Restore window.
  • Added Parameter List Maintenance window to allow creation and editing of Parameter Lists.
  • Added Parameter List Placeholder Lookup window to allow select of placeholders to insert into scripts.
  • Added Parameter List functionality to Runtime Execute and Runtime Executer windows.
  • Added Parameter List functionality to SQL Execute and SQL Executer windows.
  • Added Parameter List functionality to .Net Execute and .Net Executer windows.
  • Added Parameter List functionality to Automatic Debugger Mode Setup window for non-logging Triggers.
  • Added Parameter List functionality to called sub scripts for Dexterity, SQL Server, Visual C# and Visual Basic.Net.

Miscellaneous

  • Allow Form Menu and Context Menu triggers to pull focus to ensure all change scripts are executed prior to the trigger script executing.
  • Improved information provided to dialogs and logs when compile time errors occur.
  • Added Menu Detail Expansion pane to Menu Explorer window to show Dexterity command details and custom menu names.
  • Added Security Filter for User and Company to Menu Explorer window when opened from Security Information window.
  • Added Additional Error message details to Send Email and the Email engine.

More Information

For more information and download links, please see the GP Power Tools Portal page:

You can also look at the GP Power Tools pages on the Winthrop Development Consultants and Mekorma sites:

Please post your feedback as comments on this article or using the GP Power Tools Feedback Survey on what you think of this build and what you would like to see in the future.

Thanks to everyone involved with this release, especially the team at Mekorma, the beta testers (including special thanks to Robert Cavill for putting the code through its paces) and the Microsoft Dynamics GP MVPs.

A final massive thank-you to my family who have put up with me being in “programming mode” for the last few months.

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: 2010, 2013, 2013 R2, 2015, 2015 R2, 2016, Dynamics, GP, GP Power Tools, Microsoft, News, Products, Support Debugging Tool Tagged: GP 2010, GP 2013, GP 2015, GP 2016, GP Power Tools, GPPT, News, SDT, Support Debugging Tool

Excerpt from:
#GPPT GP Power Tools build 21 released

July 1, 2016 · WinthropDC · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 37

Happy New Year 2016

To the GP Community:

Happy New Year 2016!

This year is slated with lot of interesting releases for GP impending. I am absolutely as excited as all of you.

Let’s wish this year be an excellent year for Dynamics GP and its success.

VAIDY

Filed under: #MSDYNGP, New Year, Off-Topic, Uncategorized

See the original post:
Happy New Year 2016

January 1, 2016 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 166

OFF-TOPIC: Windows 10 and Microsoft File Transfer Manager (FTM) Issues

This is my first post from Perth, WA. It’s been an excellent journey and so far so good. More about my Perth life later.

This is something that I never experienced before. When you download any file from PartnerSource or CustomerSource, Microsoft would let you do that only through it’s File Transfer Manager program. If you have that installed already, any download initiation would first invoke this program and then let you set the path/folder to take in that download and etc.

However, when I tried to do that from my new Windows 10 machine, the FTM did not open. I tried to figure that out, but later remembered this same issue happening on my Windows 8.1 machine.

Basically, from Windows 8.1, for some reason, calling the FTM from Internet Explorer worked only on a 32 bit Internet Explorer.

Looks like Microsoft has not fixed that yet. If you are wondering why your FTM didn’t work, this is the reason. Open your IE 32 bit mode and then try to download the file that you wanted to.

VAIDY

Filed under: File Transfer Manager, FTM, Off-Topic, OS, Troubleshooting, Windows, Windows 10

Read the original:
OFF-TOPIC: Windows 10 and Microsoft File Transfer Manager (FTM) Issues

September 14, 2015 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 232

You receive "Could’n retrieve the list of available databases: The connection attempt failed" error when updating Management Reporter 2012

Hi everyone! I’m on the tail-end of upgrading a client to Microsoft Dynamics GP 2015 R2 and came up on an interesting issue when attempting to update Management Reporter 2012 CU6 to CU9.

Background

In order to create my client’s test environment for this upgrade, we cloned their production VMWare environment and went through all the usual server renames, static IP changes, SQL Server renaming, and so forth.

For the Management Reporter 2012 database server, we followed the applicable entries outlined in How to move Microsoft Management Reporter 2012 to a new server (CustomerSource access required), and in particular we removed the Application and Process services then ran the T-SQL script to re-create the certificate and symmetric key.

Once these portions of the configuration were in place, we proceeded to install Management Reporter 2012 CU9, first installing the Application and Process services – which also performed the overall ManagementReporter database update.

Next was to create the Data Mart database.

When we tried to connect to the Dynamics GP server to retrieve a list of the available databases to select the system database, we stumbled upon the following error: “Couldn’t retrieve the list of available databases. The connection attempt failed.

Configuration Console – Dynamics GP Connection information error when clicking on the Database drop-down list

When I checked the Event Viewer, the following entry could be seen:

The encrypted setting, Password, could not be decrypted.
— Exception Dump — 
Caught Exception: [System.Security.Cryptography.CryptographicException] Encrypted data was invalid and cannot be decrypted.
Stack trace:
   at Microsoft.Dynamics.Integration.DataAccessLayer.DataProtection.Decrypt(Byte[] data)
   at Microsoft.Dynamics.Integration.DataAccessLayer.DataProtection.DecryptSettings(XElement settings)

User: DomainMRAdmin
Machine: GPTOOLSTEST

Solution

Clearly, the data source information to the Dynamics GP database server wasn’t being adequately validated somewhere by the installer. Furthermore, the installer was attempting to decrypt the password I was passing in via Microsoft.Dynamics.Integration.DataAccessLayer.DataProtection.Decrypt() method which happens to be a part of the Dexterity Shared Components.

I then recalled that the Management Reporter Server installation process uses the Dexterity Shared Components to validate the connection to the system database. In reviewing the Dexterity Shared Components on the server, I found out that version 14 was installed — version 14 corresponds to the Dexterity Shared Components installed by Dynamics GP 2015. So, I was a bit puzzled. However, further analyzing this issue, I realized that CU9 predates the days of Dynamics GP 2015, so the version of the Dexterity Shared Components it must be looking for were those of Dynamics GP 2013 or earlier. It was a long shot, but I installed the Dexterity Shared Components version 12 from the Dynamics GP 2013 CD.

Once I fired up Configuration Console and attempted the configuration of Data Mart, I was then able to choose the system database from the Dynamics GP server and complete the process just fine.

Additional Notes

In doing some poking around into the ManagementReporter database tables, searching for a potential answer to this issue, I found that the dbo.ControlCompany table contains the GLEntityConnectionInformation column, which stores an XML document with some connection information. If your test environment is a result of cloning a VMWare or Hyper-V image, chances are the data stored in this column will contain the original server information and will need to be edited to reflect the current test environment server information. By simply right-clicking on the table and choosing to Edit the Top 200 rows option, you can edit the server name. The content of the XML document stored in this column looks something like this (server name in red):







GPTOOLSTEST


DDM


TWO


false


sa


AOaPHTA9VkmLvkUcyA053AEAAABurN19cbBVL3sfs/UoYU4o3YPglXB4SSrzLzXjlavUpC+uSNKdDYDDEjS9MfKKlao=


false


So you maybe asking, “why not update from CU6 to CU13+Hotfix directly?”. As it turned out, I found out that this while technically possible, causes some very undesired results with very complex reports. More on this in a follow up post.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Excerpt from:
You receive "Could’n retrieve the list of available databases: The connection attempt failed" error when updating Management Reporter 2012

August 27, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 263

You receive "Could’n retrieve the list of available databases: The connection attempt failed" error when updating Management Reporter 2012

Hi everyone! I’m on the tail-end of upgrading a client to Microsoft Dynamics GP 2015 R2 and came up on an interesting issue when attempting to update Management Reporter 2012 CU6 to CU9.

Background

In order to create my client’s test environment for this upgrade, we cloned their production VMWare environment and went through all the usual server renames, static IP changes, SQL Server renaming, and so forth.

For the Management Reporter 2012 database server, we followed the applicable entries outlined in How to move Microsoft Management Reporter 2012 to a new server (CustomerSource access required), and in particular we removed the Application and Process services then ran the T-SQL script to re-create the certificate and symmetric key.

Once these portions of the configuration were in place, we proceeded to install Management Reporter 2012 CU9, first installing the Application and Process services – which also performed the overall ManagementReporter database update.

Next was to create the Data Mart database.

When we tried to connect to the Dynamics GP server to retrieve a list of the available databases to select the system database, we stumbled upon the following error: “Couldn’t retrieve the list of available databases. The connection attempt failed.

Configuration Console – Dynamics GP Connection information error when clicking on the Database drop-down list

When I checked the Event Viewer, the following entry could be seen:

The encrypted setting, Password, could not be decrypted.
— Exception Dump — 
Caught Exception: [System.Security.Cryptography.CryptographicException] Encrypted data was invalid and cannot be decrypted.
Stack trace:
   at Microsoft.Dynamics.Integration.DataAccessLayer.DataProtection.Decrypt(Byte[] data)
   at Microsoft.Dynamics.Integration.DataAccessLayer.DataProtection.DecryptSettings(XElement settings)

User: DomainMRAdmin
Machine: GPTOOLSTEST

Solution

Clearly, the data source information to the Dynamics GP database server wasn’t being adequately validated somewhere by the installer. Furthermore, the installer was attempting to decrypt the password I was passing in via Microsoft.Dynamics.Integration.DataAccessLayer.DataProtection.Decrypt() method which happens to be a part of the Dexterity Shared Components.

I then recalled that the Management Reporter Server installation process uses the Dexterity Shared Components to validate the connection to the system database. In reviewing the Dexterity Shared Components on the server, I found out that version 14 was installed — version 14 corresponds to the Dexterity Shared Components installed by Dynamics GP 2015. So, I was a bit puzzled. However, further analyzing this issue, I realized that CU9 predates the days of Dynamics GP 2015, so the version of the Dexterity Shared Components it must be looking for were those of Dynamics GP 2013 or earlier. It was a long shot, but I installed the Dexterity Shared Components version 12 from the Dynamics GP 2013 CD.

Once I fired up Configuration Console and attempted the configuration of Data Mart, I was then able to choose the system database from the Dynamics GP server and complete the process just fine.

Additional Notes

In doing some poking around into the ManagementReporter database tables, searching for a potential answer to this issue, I found that the dbo.ControlCompany table contains the GLEntityConnectionInformation column, which stores an XML document with some connection information. If your test environment is a result of cloning a VMWare or Hyper-V image, chances are the data stored in this column will contain the original server information and will need to be edited to reflect the current test environment server information. By simply right-clicking on the table and choosing to Edit the Top 200 rows option, you can edit the server name. The content of the XML document stored in this column looks something like this (server name in red):







GPTOOLSTEST


DDM


TWO


false


sa


AOaPHTA9VkmLvkUcyA053AEAAABurN19cbBVL3sfs/UoYU4o3YPglXB4SSrzLzXjlavUpC+uSNKdDYDDEjS9MfKKlao=


false


So you maybe asking, “why not update from CU6 to CU13+Hotfix directly?”. As it turned out, I found out that this while technically possible, causes some very undesired results with very complex reports. More on this in a follow up post.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Excerpt from:
You receive "Could’n retrieve the list of available databases: The connection attempt failed" error when updating Management Reporter 2012

August 27, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 0

Microsoft Edge says “Hmm, we can’t reach this page.”

David Meego - Click for blog homepageI have finally taken the plunge and updated my primary machine, a Surface Pro 3, to Windows 10.

I delayed the installation of Windows 10 for a little while primarily because I wanted to get GP Power Tools released and did not want anything to mess up my development environments.

Then my friend Bill Marshall seemed to have some issues with Dexterity and Windows 10, so I did some testing on another Windows 10 machine to ensure that everything should work.

While doing some initial testing after the upgrade, I started receiving errors from new Microsoft Edge internet browser.

Error
Hmm, we can’t reach this page.

This would be expected if I did not have internet access, but I did. Internet Explorer worked fine and my mail worked perfectly via outlook.

While checking my settings on the Network and Sharing Center window, I noticed that my system had both a private and a public network showing. Even though my WiFi and Ethernet were connected to the same router.

I was able to solve the issue by cleaning up my network adaptors. I had a number of virtual drivers because I had been using a Hyper-V virtual machine to test the Windows 10 preview. Disabling the Hyper-V Virtual switch and making sure that the remaining Ethernet and WiFi adapters had all checkboxes selected on the Networking tab of propertues (except Microsoft Network Adapter Multiplexor Protocol and Hyper-V Externsible Virtual Switch) stabilised my connections.

Now both connections show as a Private connection to the same network and my internet connection is now fast and stable.

It seems that Microsoft Edge does not like it when there are both Private and Public networks at the same time.

Hope this helps.

David

This article was originally posted on http://www.winthropdc.com/blog.

Filed under: Microsoft, Windows Tagged: Exception, Microsoft Edge, Windows 10

Read the article:
Microsoft Edge says “Hmm, we can’t reach this page.”

August 13, 2015 · WinthropDC · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 1,081

You experience slow performance exiting Microsoft Dynamics GP 2015 on Windows 10

Today I ran across a very interesting partner forum post, in which the consultant described a slow performance issue when closing (exiting) Microsoft Dynamics GP 2015, which started happenning after his client upgraded their Windows workstations to the newly minted Windows 10 operating system.

A Microsoft support engineer acknowledge that “there have been a few people experiencing this issue“. The recommendation to bypass the slow application closing is to change or add the following Dex.ini setting to see if it resolves the issue on exit. The setting changes a Microsoft Dynamics GP global variable and avoids the pause that seems to be occurring during the exiting process.

OLEClose=FALSE

This Dex.ini setting controls whether the Microsoft Dynamics GP application checks for the OLE Container application being opened at the time of shutdown — a “shutdown” can occur if the user legitimately exits Dynamics GP or simply chooses to open either the Report Writer or Modifier tools. If the Container is open during the shutdown operation, Dynamics GP will attempt a graceful closure of it.

The default value of this setting is TRUE, whether the setting is present in the Dex.ini with a value of true or empty, or simply not present at all. This indicates to GP that it should always attempt to close down the Container if it is found to be open.

Given the fact that most customers are now taking advantage of Document Attachment (Doc Attach) and moving away from the Container application, there should be less and less dependency on Container, which would almost require that the default value for our flag is set to FALSE, rather than it’s current state.

As usual, you must apply these changes to your environment only if you are experiencing this issue.

Until next post!

MG.-
Mariano Gomez, MVP
Intelligent Partnerships, LLC
http://www.intelligentpartnerships.com/

Excerpt from:
You experience slow performance exiting Microsoft Dynamics GP 2015 on Windows 10

August 13, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , ,  · Posted in: Blogs I Follow Total Views: 311