Page 1 of 7812345678910...2025303540...Last »

What?! Referential Integrity Checked on a Clear Data Table.

I learned something today from Lawrence Reid at ConexusSG that impacted the Clear Data file maintenance utility. They set up some National Accounts and then wanted to clear the Customer Master table. Once you create National Accounts, none of the customers with children will be cleared. After you run the utility you will get an error on your report that states:

You can’t clear data in the parent table RM Customer MSTR until you have cleared data in the child table RM National Accounts Master.

Wow! I’d never seen that before. It does delete all of the customers with no ‘child’ companies, but any customers with children are left intact.

Until next time,

Leslie Vail

See original article:
What?! Referential Integrity Checked on a Clear Data Table.

February 26, 2016 · Leslie Vail · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 73

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: 136

Changing SQL Server Collation After Installation

I had a necessity to change the collation of newly created SQL server instance from CI_AS to CP1_CI_AS.

To brief you about why this was needed, I wanted to test upgrade GP from version 2010 RTM to 2010 SP3. In order to that, I created a new SQL server instance with collation SQL_Latin1_General_CI_AS. I restored GP 2010 RTM backups on to this newly created server. But later realised that GP databases that I got for 2010 RTM was of collation SQL_Latin1_General_CP1_CI_AS.

There were two options. Either I must change the collation of databases to CI_AS or I must change the server collation itself to CP1_CI_AS. Later seemed to be a better option (for some reason, I wanted to retain the collation on the databases). I was left with changing the collation of server instance.

That’s when I got this link: Changing SQL Server Collation After Installation

I was worried about the whole process but this post saved me loads of time and sweat. Changing the collation was a breeze.

Anybody out there who is looking for the best possible method to change server collation, above is the post you would want to read.

VAIDY

Filed under: #MSDYNGP, Dynamics GP, SQL Server

Original post:
Changing SQL Server Collation After Installation

October 6, 2015 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 163

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

Originally posted on Dynamics GP – Learn & Discuss:

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…

View original 55 more words

Filed under: Uncategorized

See the original article here:
OFF-TOPIC: Windows 10 and Microsoft File Transfer Manager (FTM) Issues (UPDATE)

October 5, 2015 · Vaidyanathan Mohan · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 190

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: 199

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: 216

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