Page 1 of 9112345678910...2025303540...Last »

Upgrade from GP 2010 to GP 2013 R2

3d man with Q & A

Question: How do you upgrade from GP 2010 build 2390 to GP 2013 R2

Answer: The documentation from Microsoft that delineates the upgrade path from GP 2010 to GP 2013 R2 is missing the current build of GP 2010 (as of 3/16/2015). The document from Microsoft can be found here: https://mbs.microsoft.com/partnersource/northamerica/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade#UpgradePaths.

The line missing is how to upgrade to GP 2013 R2 from 11.00.2390. The answer is that you have to upgrade to 12.00.1826. The build numbers for both GP 2010 and GP 2013 R2 are achieved after installing the January 2015 Hotfix. Thanks go out to Paul Degneau, at Standard Process www.Standardprocess.com, for suggesting this to me.

Enjoy!

Leslie

Original post:
Upgrade from GP 2010 to GP 2013 R2

March 17, 2015 · Leslie Vail · No Comments
Tags: , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 18

Dynamics GP hosting – a great experience with RoseASP

I recently had a great experience that I would like to share. We have a client that was on a very old version of Dynamics GP (8.0), very old version of SQL (2000) a very, very old server (going on 10 years), and outsourced IT. Long story short, their server went down, they lost 2 out of the 3 […]

Read this article:
Dynamics GP hosting – a great experience with RoseASP

March 16, 2015 · Victoria Yudin · No Comments
Tags: , , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 24

You receive "You are not allowed to use Microsoft Dynamics GP. Please sign out and sign in with an authorized account" when accessing Web…

One of the cool things about Microsoft Dynamics GP 2015 is the new Web Client Identity Management feature. Having the ability to access Microsoft Dynamics GP with your Windows Directory or Windows Azure credentials without ever needing a SQL login account is just beautiful.

The Theory – Part 1: GP Utilities

The theory is fairly simple: you have a Microsoft Dynamics GP user account, which in turn is tied to a Windows Active Directory account or Windows Azure Active Directory account. User accounts are stored in the User Master table (dbo.SY01400) in the system database, which has been beefed up with a new column called Active Directory Object GUID (ADObjectGuid) to store the actual GUID of the directory or organizational account mapped to the GP user.

User Setup window

However, because Microsoft Dynamics GP continues to be dependent on SQL authentication for all intends and purposes, it continues to need a SQL login to be able to access the Dynamics GP database objects. This is where the new Web Client SQL Login user comes into play.

If you have done a new install of Microsoft Dynamics GP 2015, you would have noticed a new window called Manage Web Client SQL Server Login during the GP Utilities process. This window prompts for SQL credentials that will be used to access the SQL server database objects from Web Client.

Manage Web Client SQL Server Login window (GP Utilities)

If you are doing an upgrade, you will need to direct your attention to the drop-down list in the Additional Tasks window to find it — more on this later.

Additional Tasks window (GP Utilities)

When you enter the credentials in the Manage Web Client SQL Server Login window, the actual SQL Server security principal is created with the same password encryption at the database level. To understand more about this, read Why does Microsoft Dynamics GP encrypt passwords by David Musgrave over at Developing for Dynamics GP.

The Theory – Part 2: Web Client

When you are installing the Web Client itself, you are once again prompted to enter the Web Client SQL Server Login credentials. At this stage you MUST enter the same account information entered when you ran the GP Utilities.

This information is stored in the TenantConfiguration.xml file (in a single-machine instance) under the SessionCentral folder. The same information is used by the Service Based Architecture service (GPService service) to gain access to database resources, hence there’s also a TenantConfiguration.xml file (again, in a single-machine instance) under the GPService folder. These two folders can be located under your Program FilesMicrosoft DynamicsGP Web Components root folder.

Now that your AD or Organizational account is tied to your GP user account, when you launch the web client and your AD credentials are validated against IIS, a security token is created and passed on to Session Central service, which in turn spins up a runtime process passing on your AD account credentials in the GP Login window. The log in process itself will use the Web Client SQL Server login to access the system database and in particular the User Master table to validate the AD account GUID against the one stored in the table. If all matches, you are allowed access and from there on you go about your business.

The Problem

This brings us to the topic of this post…

As it turns out, during that handshake between Session Central and the Runtime service to pass off the AD credentials, I received the following error:

Further review of the Dynamics application and services log in Event Viewer, shows the following error:

System.Security.Cryptography.CryptographicException: Padding is invalid and cannot be removed.
   at System.Security.Cryptography.CapiSymmetricAlgorithm.DepadBlock(Byte[] block, Int32 offset, Int32 count)
   at System.Security.Cryptography.CapiSymmetricAlgorithm.TransformFinalBlock(Byte[] inputBuffer, Int32 inputOffset, Int32 inputCount)
   at System.Security.Cryptography.CryptoStream.FlushFinalBlock()
   at System.Security.Cryptography.CryptoStream.Dispose(Boolean disposing)
   at System.IO.Stream.Close()
   at Microsoft.Dynamics.GP.Web.Foundation.AesCryptographer.Decrypt(String value)
   at Microsoft.Dynamics.GP.Web.Services.Session.TenantServiceXmlHandler.ResolveTenantPasswords(Tenant tenant)
   at Microsoft.Dynamics.GP.Web.Services.Session.TenantServiceXmlHandler.GetTenantDetails(String identity, String tenantName)
   at Microsoft.Dynamics.GP.Web.Services.Session.Service.SessionCentralService.CreateSession(String tenantName, UserContext userContext)

Typically, any Crypto exception is directly related to credentials. So I traced back my steps after the upgrade and realized I had created the Web Client SQL server login account manually — after all, I had not seen the option in the GP Utilities drop down to do so. Of course, this would mean that the password was un-encrypted on SQL server and wouldn’t match the password stored in the TenantConfiguration.xml file. In retrospect, had I even used GP Utilities to setup the account and entered a different password from the one I entered during the Web Client install, I would have received the same error.

The Solution

Knowing that in essence what I had was a password mismatch between the value stored in TenantConfiguration.xml and the password at the SQL Server level, I decided to make things simple and removed the database user (sp_dropuser) corresponding to the security principal and the actual security principal (sp_droplogin) then re-launched GP Utilities and created the account once more, this time making sure the password matched what I had entered when installing the Web Client.

Once I launched the Web Client and entered my Windows credentials information, I was able to experience the beauty of single sign-on all the way to the company database I had selected as my default company.

Also, it is worthwhile to mention that Service Based Architecture was failing validation, but I will address this in my next article.

Acknowledgements

I want to thank Chris Rudolph with the Microsoft Dynamics GP Software Engineering team for his valuable insight into working through this issue. Chris also helped me with understanding some deep architecture stuff that I will be presenting in a future related article to this one.

Until next post!

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

Read More:
You receive "You are not allowed to use Microsoft Dynamics GP. Please sign out and sign in with an authorized account" when accessing Web…

March 12, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 33

Silverlight "ArgumentException: An item with the same key has already been added" when attempting to print a report

It’s been about 3 months now since working with Microsoft Dynamics GP 2015 in our production environment. To recap, at Intelligent Partnerships we run all our information technology infrastructure on Microsoft Azure. A big reason for this, of course, is the high degree of mobility required by our consulting staff and the ability to access demo environments and be able to enter timesheets and expenses from anywhere in the world they happen to be. In addition, we need to be able to run our business and access our financials and analytics without being constrained to a particular geographical location. As such we rely heavily on Dynamics GP’s Web Client and Business Analyzer to achieve these goals.

One of the issues we started noticing with Web Client recently is, when you attempt to print a report – Standard or Template – but cancel out the printing on the Report Destination window, then attempt to print the report once more, we would receive the following Silverlight error message:

Severity: Critical Summary: A server side exception of type “ArgumentException” has occurred. Details: ArgumentException: An item with the same key has already been added. at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource) at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add) at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.Hierarchy`1.Add(T ancestor, T item) at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.Implementation.WCDexRuntimeStateResourceManager.Register(DexUri parentId, IWCDexWindow window) at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.Implementation.Adapters.WCDexFormOpenStateChangedNotificationAdapter.Notifications_FormOpenStateChanged(Object sender, DexUriEventArgs`1 e) at System.EventHandler`1.Invoke(Object sender, TEventArgs e) at Microsoft.Dexterity.Runtime.Interop.DexNotification.OnFormOpenStateChanged(DexUri uri, DexFormOpenState value) at Microsoft.Dexterity.Runtime.Interop.Win32.NativeMethods.MsaCommandExec(Int16 tag) at Microsoft.Dexterity.Runtime.Interop.Win32.NativeMethods.<>c__DisplayClass26.b__25() at Microsoft.Dexterity.Runtime.Interop.Win32.NativeMethods.ExecuteMsaAction(Func`1 interopAction, String entryPoint) at Microsoft.Dexterity.Runtime.Interop.Win32.NativeMethods.MacroSystemCommandExecute(Int16 tag) at Microsoft.Dexterity.Runtime.Interop.DexMacroSystem.CommandExecute(Int16 tag) at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.Implementation.WCDexMessageProcessor.ProcessCommandExecuteInstanceResourceMessage(IWCDexMessage msg) at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.Implementation.WCDexMessageProcessor.Process(IWCDexMessage message) at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.DexRuntimeStateManager.SendMessage(IWCDexMessage message) at Microsoft.Dynamics.GP.Web.Services.Runtime.Dexterity.DexRuntimeStateManager.MainEventLoop()

This particular error was received attempting to print a sales order processing quote, but we have been able to reproduce from other windows. While I don’t claim to understand all these exceptions, this particular one seems to refer to an issue caused by a “key” being added twice to the same “Generic.Dictionary” collection. Since the action causing the error seems to be a second attempt at printing a report – the same report it seems – somewhere along the lines it would appear that some value isn’t being cleared out from the collection of reports being printed which would cause a duplicate key. Again, pure speculation.

Nonetheless, in speaking to the Dynamics GP development team, it seems to be this issue has been written up and may be solved in the upcoming hotfix release. This issue can be reproduced in Microsoft Dynamics GP 2015 build 14.00.0619 (January Hotfix).

Until next post!

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

Read the article:
Silverlight "ArgumentException: An item with the same key has already been added" when attempting to print a report

March 11, 2015 · Mariano Gomez · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 20

Considering an Upgrade from Dynamics GP to Dynamics AX?


Recently I’ve delivered Dynamics GP training to new users who came from a company using Dynamics AX.  In my own experience, other than the additional features that Dynamics AX offers over Dynamics GP (which are considerable) and getting accustomed to the ability to post a transaction initiated in the General Ledger backto a subsidiary module in AX, there is a lot of commonality in the User Interface (UI) between the two applications.  This is particularly important for companies that have perhaps outgrown Dynamics GP and are considering a move to a more full-featured ERP system such as AX.  Microsoft has done a commendable job of unifying their ERP system UI’s, which offers the client the benefit of quicker and easier user adoption when moving from one application to another.
Additionally, both applications are tightly integrated with Microsoft Office tools, further easing the transition to a new system.
The first image below is of the Dynamics GP 2015 Financial module, with the menu items arranged in basically the same sequence as the Dynamics AX 2012 R3 image below it.  Notice how the menus and the Navigation Pane layout are quite similar in both applications, albeit the AX UI is cleaner, in my opinion.  Maybe the GP development team can get together with the AX dev team on that one.
Based on their comments, my recent trainees report the same experience.  They’ve indicated that adapting to Dynamics GP from AX has been much quicker than they thought it would be, primarily because of the similarities between the two UI’s. 
 
In considering an upgrade from Dynamics GP to Dynamics AX, user adoption and performance ramp-up can be relegated to the bottom of the list of concerns.

More:
Considering an Upgrade from Dynamics GP to Dynamics AX?

March 3, 2015 · Frank Hamelly MCP-GP MCT MVP · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 25

Values for SY01402 – System User Defaults

I needed to research the settings in the System User Defaults table recently, so I took out my list of what the syDefaultType field translated to. The table below shows the value and its definition. These constants are from the GP2013R2 build


syDefaultType Definition
1 SCBARAUTOHIDE
2 SCBARWHICHSIDE
3 SCBARWIDTH
4 SCBARICONSIZE
5 SCBARAUTOOPEN
6 UNDERLINED_PROMPTS
7 COLORSCHEME
8 BACKGROUND
9 TOOLBARBUTTONS
10 MESSENGER
13 REMINDERS
14 MAPPOINT
15 FIELDSECURITY
16 COMMISSIONS
17 VENDORLISTSORT
18 VENDORLISTINACTIVECB
19 CUSTLISTSORT
20 CUSTLISTINACTIVECB
21 ITEMLISTSORT
22 ITEMLISTINACTIVECB
23 SOPITEMMISSINGCB
24 POPITEMMISSINGCB
25 EMPLISTSORT
26 EMPLISTINACTIVECB
30 AUTOCOMPLETE
31 PRINTONEPOPERADDRESS
40 HRVETSNAICSNUMBER
41 LISTWINDOWSIZE
42 NAVBAR_BIGBTNCOUNT
43 SOPMANAGESOPTYPE
45 CPRCONVERSION
46 SQLREPORTING_TARGETLOC
47 SQLREPORTING_RPTMGRLOC
48 SQMOPT
49 SHAREPOINTSERVERURL
50 LOCKEDTOOLBARS
51 REGKEY
52 HOMEPAGEMETRIC
53 HOMEPAGEREMINDERS
54 HOMEPAGEOUTLOOK
68 MFG_MODULE_ENABLED
69 REMINDERSCUES
70 REMEMBEREDCOMPANY
71 REMEMBERUSERENABLED
72 SHOWALLMETRICS
80 RPTTEMPLATES_ENABLED
82 RPTTEMPLATES_ALLOWSTDORTEMPLATE
83 POSITIONCONTROL
84 FACTBOX_ROTATIONFREQUENCY
85 FACTBOX_IMAGESIZE
90 ISSHAREPOINTONLINE
91 EMAIL_SERVER_TYPE
92 EMAIL_PROTECT_WITH_PASSWORD
93 EMAIL_PASSWORD_RADIO
94 EMAIL_PROTECT_PASSWORD
95 PHONEHOME
96 SLAHWINDOW
97 WEBCLIENTSQLLOGIN
1493 SMARTLIST
22001 MBS_DEXPROFILE
22002 MBS_SQL_LOG

Enjoy!
Leslie

More:
Values for SY01402 – System User Defaults

March 2, 2015 · Leslie Vail · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 21

How to disable "Checking for newer builds" message in Rockton software products

Given the well-deserved popularity of Rockton Software’s (http://www.rocktonsoftware.com/) products, such as ‘SmartFill’ and ‘The Dynamics GP Toolbox’, it has come to my attention that it checks for newer builds each time you sign in. Kind of like the ‘Welcome to Dynamics’ trill from years ago, this can get annoying. Fortunately, Rockton has addressed this issue and published the following KB article to address it.

Jim Moore, at Wesco Valve and Manufacturing Company (www.sswesco.com) was kind enough to send me the article below: 

Issue:
Disabling the “Checking for newer builds…” message. Note: This setting is user-specific.

Option 1.

To disable this feature, go through the following steps:

  1. Click on the Help icon in the upper-right corner of GP.
  2. Select Rockton Software Support at the bottom of the list.
  3. On the menu, click Settings >> Rockton Software Preferences.*
  4. Under the User-specific settings section, bring up the individual user for whom you want to change the setting.
  5. Unmark the Enable check for newer builds at the login for each user that doesn’t want to have that process run.

Note: These settings are stored in a table in the DYNAMICS database, so you don’t need to do this at each workstation.

*Step 3, the path may vary. It may be Rockton Software Support | Preferences | Rockton Global Settings.
Note: All users will be marked by default but the check for newer builds will only appear for PowerUsers and users assigned to the Administrator role for Rockton Software products within Security. If you use Auditor, then it is based on those users you marked as Admins. in the Auditor System Settings window.
Option 2.
To do a mass update on the table that the information is stored in, you can run the following script in SQL Management Studio.  You can then view what the values are for that particular setting in the RS_Global_Setting_Value column (1 = Enabled and 0 = Disabled)**. Be sure to have a backup made prior to running the script.

USE DYNAMICS

UPDATE RSIGLOBL SET RS_Global_Setting_Value = 0 WHERE RS_Global_Setting_Key = ‘EnableNewerBuildCheck’

More Information:
When you install any Rockton product after turning this off, you will receive a prompt at the end of the install to re-enable the setting if it has been disabled. 
**It is recommended that you leave at least one person enabled, so that they are notified when a new build is available.

Continue reading here:
How to disable "Checking for newer builds" message in Rockton software products

February 19, 2015 · Leslie Vail · No Comments
Tags: , , , , , , , , , ,  · Posted in: Blogs I Follow Total Views: 31