Dynamics GP Support and Services Blog

Upgrading to Business Portal 6.0 for Microsoft Dynamics GP 2013

Lucas Miller — Thu, 16 May 2013 14:00:00 GMT

Business Portal 6.0 is now available and it is time to start thinking about your Business Portal upgrade! Click HERE to download the Business Portal 6.0 Upgrade Guide!! We wanted to use this blog article to help you get prepared for that upgrade!

Business Portal 6.0 is available for Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010. We’ll be releasing Business Portal 6.1 for Microsoft Dynamics GP 2013 in the near future, which will add support for Microsoft SharePoint 2013, so keep an eye out for future articles on that release and its upgrade process.

The upgrade steps that you will take depends on what version of Business Portal you would like to upgrade from. We’ll go through each scenario below.

Regardless of what version of Business Portal you are going to be upgrading from you’ll want to perform certain pre-upgrade tasks:

1. Verify the account used to display reports in Reports Catalog
a. Reports Catalog is available only if you’re using Business Portal with SharePoint Foundation 2010.

2. Approve all open workflow items in the HRM Self Service Suite module

Upgrading from Business 4.0 for Dynamics GP 10.0 or Business Portal 5.0 for Dynamics GP 2010 on Microsoft Office SharePoint Server 2007 or Windows SharePoint Services 3.0

Business Portal 4.0 is only supported on 32-bit operating systems, so an upgrade to Business Portal 6.0 must involve a move to a 64-bit server as well as a SharePoint upgrade. The upgrade steps are contained in the following list:

1. First, you must upgrade Dynamics GP 10.0/Dynamics GP 2010 to Dynamics GP 2013.

2. Upgrade or install Web Services for Dynamics GP 2013

3. Backup your SharePoint Configuration and Content databases

4. You then need to upgrade to one of the following versions of SharePoint on a 64-bit server:
    a. Microsoft SharePoint Foundation 2010,
    b. Microsoft SharePoint Server 2010 Enterprise Edition
    c. Microsoft SharePoint Server 2010 Standard Edition

For detailed information about upgrading to SharePoint Foundation 2010, refer to the following topics in the SharePoint Products Technical Library on Microsoft TechNet.

Upgrading to SharePoint Foundation 2010	A guide to help you plan for and perform an upgrade from Windows SharePoint Services 3.0 to SharePoint Foundation 2010
Checklist for database attach (SharePoint Foundation 2010)	A checklist for the steps necessary to prepare for attaching databases, to perform the upgrade, and to perform post-upgrade steps.
Attach databases and upgrade to SharePoint Foundation 2010	An article that has information and procedures for attaching databases and upgrading to SharePoint Foundation 2010.arePoint Products Technical Library on Microsoft TechNet.

For detailed information upgrading SharePoint Server 2010, refer to the following topics in the SharePoint Products Technical Library on Microsoft TechNet.

Upgrading to SharePoint Server 2010	A guide to help you plan for and perform an upgrade from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010.
Checklist for database attach upgrade (SharePoint Server 2010)	A checklist for the steps necessary to prepare for attaching databases, to perform the upgrade, and to perform post-upgrade steps.
Attach databases and upgrade to SharePoint Server 2010	An article that has Information and procedures for attaching databases and upgrading to SharePoint Foundation 2010.

5. Once SharePoint has been upgraded you should still have you same Business Portal web application that can be browsed in Internet Explorer. While that site won’t be fully functional without a Business Portal install, being able to navigate to it after the SharePoint upgrade it is still a good test.

6. Having verified the site is valid you can then proceed with the Business Portal 6.0 installation.

Upgrading from Business Portal 5.1 for Dynamics GP 2010 on Microsoft SharePoint Server 2010 or Microsoft SharePoint Foundation 2010

Since both Business Portal 5.1 and Business Portal 6.0 will be installed to the same versions of SharePoint and both require a 64-bit server the upgrade is a matter of the following steps:

1. Upgrade from Dynamics GP 2010 to Dynamics GP 2013

2. Upgrade to Web Services for Dynamics GP 2013

3. Backup your SharePoint Content and Configuration databases

4. Uninstall Business Portal 5.1. You will not want to select the option to remove Business Portal data

5. Once the removal process is complete run the Business Portal 6.0 installer, pointing to the same SharePoint web application. It will detect that Business Portal previously existed in this environment and proceed with an upgrade.

Click HERE to download the Business Portal 6.0 Upgrade Guide for more detailed information!

Happy upgrading!

Business Portal 6.0 for Microsoft Dynamics GP 2013 is now available!

Kelly Youells — Fri, 10 May 2013 11:12:00 GMT

Hi Community,

Business Portal 6.0 for Microsoft Dynamics GP 2013 is now available!

Customers - Click HERE
Partners - Click HERE

Check out our awesome Business Portal 6.0 Documentation!!!

Business Portal 6.0 Upgrade Guide
http://www.microsoft.com/en-us/download/details.aspx?id=38835

Business Portal 6.0 Administrator's Guide
http://www.microsoft.com/en-us/download/details.aspx?id=38822

Business Portal 6.0 Installation Guide
http://www.microsoft.com/en-us/download/details.aspx?id=38824

Business Portal 6.0 Facts You Need to Know! - Check it out!
1. Business Portal 6.0 is x64 only.

2. Business Portal 6.0 is only supported on SharePoint Server 2010 or SharePoint Foundation 2010.

3. Business Portal 6.0 is currently only supported on Windows Server 2008 x64 SP2 or later & Windows Server 2008 R2 SP1 or later.

4. SharePoint 2010 is currently NOT supported on Windows Server 2012 until the release of Service Pack 2 for SharePoint 2010. Therefore, Business Portal 6.0 is currently not supported on Windows Server 2012.

5. Here are the upgrade paths to Business Portal 6.0. (NOTE: Coming from Business Portal 4.0 and 5.0 does also require upgrade to SharePoint 2010.)
a. Business Portal 4.0 SP2 to Business Portal 6.0
b. Business Portal 5.0 to Business Portal 6.0
c. Business Portal 5.1 to Business Portal 6.0

**Make sure to check out our Business Portal 6.0 Upgrade Guide!**

6. Business Portal 6.1 will be out later and will support SharePoint 2013. Business Portal 6.0 is not supported on SharePoint 2013.

Enjoy!!

GP 2013 – Business Analyzer application for Windows 8

Chris Bulson — Thu, 09 May 2013 17:50:00 GMT

If you're using GP 2013 and SSRS there is a great Business Analyzer App that you can use on Windows 8 (x86/x64/ARM) devices. By the time you are reading this blog there will have been a newly updated release of this app. If you've previously been using the Business Analyzer app and install the latest update you will have to reselect your reports.

I encourage you to download this app and check it out!
http://apps.microsoft.com/windows/en-US/app/microsoft-dynamics-business/a68e5f35-e5c3-4bf8-8427-2bfdfa01fd72

I don’t want to get into the details of using it or setting it up, you can go to the following site for that information:
http://technet.microsoft.com/en-us/library/jj899791.aspx

I do want to discuss a few points about the use of this application as it pertains to the support team and our partners. The biggest pain point I think we’ll see for partners who want to demo this is that you cannot run the Business Analyzer app and the instance of SSRS that you are connecting to on the same machine. So if you are planning to take your laptop to a customer site and demo Business Analyzer you may be limited by this. This is a security issue with Windows 8 and not something we can work around.

You can however set this up on a single machine in a domain environment by using Hyper-V. I currently have this solution up and running on my laptop and it is working fine. Windows 8 comes with Hyper-V built in to it which is a huge plus. So you will have the Business Analyzer application running natively on Windows 8, but you will be connecting to a Hyper-V instance on the same machine which is running SSRS.

If you’re not familiar with using Hyper-V on Windows 8 please look at the documentation found here: http://www.microsoft.com/en-us/download/details.aspx?id=36188

One of the new features in the latest release is the ability to connect to SSRS while you're "Off Domain". In the settings you will now be required to put in your credentials to connect to the SSRS server. This will allow the app to pass your credentials for authentication even when your machine is not "On the Domain". You do need to have an internet connection for this to work as it actually stores your password in the Windows Store vault, not local to the machine.

The last thing I will remind you of if you are running into problems getting this to connect to your SQL server is to open port 1433 on your firewall. :-)

Canadian Payroll ROE recent change Variable Best Weeks Reporting

Terry R Heley — Tue, 07 May 2013 14:00:00 GMT

Hello Canadian Payroll Enthusiasts!

Recently, Service Canada has sent out a notice to Canadian Payroll employers advising that you should provide Records of Employment in a weekly format for 53 weeks, no matter what the employees actual pay schedule is (bi-weekly, semi-monthly, etc.)

Microsoft Dynamics GP back in 2007 (yes, I'm aging myself) added ROE 53 week capability for versions 9.0 and beyond.

In my testing as well as speaking with Service Canada, what our system currently does is acceptable to them.
I also made sure the ROE did not stop at my current pay period per year.
Example, if my current pay period per year is 24, and I have worked for more than 24 pay periods, the ROE will create with additional periods.

At this point, Service Canada is only encouraging customers to report in this fashion.

I think this recent change was more for the paper ROE’s that are still the “older” way of reporting ROE.

Here is a bit more detail about how the ROE calculates in general:

The ROE amounts and hours will pull from the Payroll Employee Summary Expand – Canada window (click Cards, click Payroll – Canada, click Employee, and then click Calculated). The data needs to be listed in the Summary Expand window to generate the ROE. When the ROE is created it will also look at the Calculated field under the LY Calculated window as well (Inquiry | Payroll - Canada | Employee Last Year Information, and then click Calculated) to collect any LY information it needs to complete the ROE.

The following tables are used:
CPY30250 (Payroll Calculation MSTR File)
CPY50250 (Payroll Calculation MSTR File LY)

The ROE Total Insurable Earnings information will pull from the PEIInsEarnings24 field in the CPY30250/CPY50250.
The ROE Total Insurable Hours information will pull from the PEIInsHours field in the CPY30250/CPY50250.

Microsoft Dynamics GP will find all of the calculated records for the employee (one record per employee per batch). It finds the newest (by date) record that is not marked off (PMarkOff = 0).
It then finds all of the transactions that made up this batch and grabs the transactions with the highest date.
If this was unsuccessful, and the employee did not get paid in the current year or did not have enough pay periods in the current year, it will repeat this process with the history table (CPY50250).

Be careful of the mark off........ you can check the CPY30250 and CPY50250 to see if the transactions have been marked off (PMarkedOff=1).
The CPY30250 table holds current year information and the PMarkedOff column will be a '0' up until the ROE is generated.
The CPY50250 holds the historical information. When the ROE is generated, the PMarkedOff column will flip to a '1'. So if this is marked, it prevents the information from pulling onto another ROE.

If the transactions are marked off (PMarkedoff = 1) then they will not pull on the ROE and should be reset to 0 if you need them to pull.

Thanks
Terry Heley

New troubleshooting document available for Project billing

Pam Peterson — Thu, 02 May 2013 14:15:00 GMT

Hello everyone,

I wanted to make sure you were aware of a new, comprehensive troubleshooting guide we have available for Project Accounting billing issues. This document covers the following topics:

1. Data entry problems with billing invoices for Time and Material projects
2. Data entry problems with billing invoices for Cost Plus or Fixed Price projects
3. Data entry problems with billing invoices for projects that bill fees
4. Posting problems with billing invoices for Time and Material projects
5. Posting problems with billing invoices for Cost Plus or Fixed Price projects
6. Posting problems with billing invoices for projects that bill fees
7. The error message - You cannot enter a Batch ID that has unposted receivables transactions
8. The drill back from the inquiry window is incorrect

Also included in the Appendix is a SQL script that you can use to see all of the tables a specific billing document exists in. Simply enter your document # and run it against your company database. If you are not able to correct your issue, open a support case and send the file results to Support and we can take a look at it for you!

Find this guide and script using these links -

Customers - Click HERE
Partners - Click HERE

Enjoy!

Pam Peterson

Information regarding Encumbrance and Blanket Purchase orders

Angela Eckman Ebensteiner — Tue, 30 Apr 2013 14:00:00 GMT

Hi Everyone!

I wanted to share some information about Encumbrance and Blanket purchase order. There has been little information available on how Blankets work with Encumbrance and some confusion as to when/date the children will be encumbered.

When you enter a Blanket PO, the first line is a control line. Blankets (control line) always show the status as 2 (pre-encumbered) in the tables (ENC10111 for example). It inserts a line as a value of 2 (positive value) and as you add the children (in the blanket button on the PO entry window), the system removes the values for that line. It creates negatives for those lines. They come out with a status of 2.

You will see something like this in the table for the control line (ENC10111) after you add lines in the blanket.

PONUMBER POLNENUM POLNESTA ENCBSTAT ENCMBAMT

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

PO2076 16384 1 2 912.60000

PO2076 16384 1 2 -152.10000

In turn the children lines get added as a status of 1.

NOTE: Children are always a status of 1 (Encumbered). This will never change under any circumstances.

PONUMBER POLNENUM POLNESTA ENCBSTAT ENCMBAMT

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

PO2076 32768 1 1 152.10000

PO2076 49152 1 1 152.10000

PO2076 65536 1 1 152.10000

PO2076 81920 1 1 152.10000

PO2076 98304 1 1 152.10000

PO2076 114688 1 1 152.10000

NOTE: When you tab off the children, the children DO NOT validate against a budget of those period identified on the blanket. (Even if you are spanning multiple years). The system only validates against the blanket control line. If customers want it to or expect it to we ask that you enter a suggestion to have that built into the product.

Example:

Blanket Control line for quantity of 6 entered on 10/1/2012 for a total of $912.60

Blankets (Children)

QTY 1 on 10/1/2012 for $151.10

QTY 1 on 11/1/2012 for $151.10

QTY 1 on 12/1/2012 for $151.10

QTY 1 on 1/1/2013 for $151.10

QTY 1 on 2/1/2013 for $151.10

QTY 1 on 3/1/2013 for $151.10

In this example the system will validate the $912.60 total against the budget 2012 for period 10. It does NOT look at the children with dates into the next year (2013 even though the children span into that next year).

During the transfer, the system takes the amount remaining to liquidate for the children for the year you are in and liquidates those lines. The value is put into Period 12 and it then moves the remaining left to be liquidated from period 10, 11 or 12 to the next year (2013).

Hope this information is helpful with understanding how Encumbrance and Blanket Purchase Orders work.

Thanks,

Angela Ebensteiner

Microsoft - Technical Lead

Microsoft Dynamics GP 2013 - Value Cannot Be Null Error Navigating the Home Page

Kelly Youells — Fri, 26 Apr 2013 01:00:00 GMT

Hi Community!

We have taken a several calls where users are running into the error below when navigating the home page or area pages in Microsoft Dynamics GP 2013:

Value cannot be null.
Parameter name: titleValue

This issue is resolved with Service Pack 1 for Microsoft Dynamics GP 2013. Download and install Service Pack 1 today!

Customers - CLICK HERE
Partners - Click HERE

If you are currently on Microsoft Dynamics GP 2013 and cannot install Service Pack 1 immediately, refer to the Knowledge Base article below for workaround steps.

http://support.microsoft.com/kb/2843273

Enjoy!

Microsoft Dynamics GP 2013 Upgrade Paths - GP, Windows, SQL Server

Jonathan Fear — Tue, 23 Apr 2013 14:40:00 GMT

Do you have customers that are still on older version of Microsoft Dynamics GP or Microsoft Business Solutions and are looking to upgrade them, but you don’t know the upgrade path? Well you can exhale a sigh of relief because this can be done! Not only will we cover the upgrade path for Microsoft Dynamics GP or Microsoft Business Solutions, but we also will go over which version of SQL along with the version of Windows Server you will want to use. Please remember that before each upgrade you will want to review the upgrade manual along with any Hot Topic page to avoid any known issues.

Here are a few common scenarios we receive questions on:

eEnterprise 5.5/SQL 6.5/Windows 2000 to Dynamics GP 2013/SQL 2012/Window 2012
1. The first step you need to do is upgrade to eEnterprise 6.0.
2. Migrate from SQL 6.5 to SQL 2000 on your Windows 2003 Server. You can stay on your Windows 2003 Server until you are ready to upgrade to GP 2013.
3. Now being that we are on eEnterprise 6.0/SQL2000 you can upgrade to Dynamics 7.5/SQL 2000.
4. Upgrade from to Dynamics 7.5/SQL2000 to Dynamics 9.0/SQL 2000. You then will need to apply a hotfix for GP 9 so you can upgrade to GP 2010. I would recommend you apply Hotfix KB 971017 which will bring your databases to 9.00.0371. This is the minimum version required to upgrade to GP 2010. Click HERE to go to the GP 9.0 Download Page to grab the required patch.
5. Once your databases are on 9.00.0371 you will want to move your databases to SQL 2012 on Windows 2012. Refer to KB 878449 for move steps.
6. Next you will want to upgrade your databases to GP 2010 11.00.1914 or later since you are using SQL 2012. Click HERE to go to the GP 2010 Download Page to grab the required patch.
7. Last you will upgrade your databases to GP 2013.

eEnterprise 6.0/Dynamics 6.0/SQL 2000/Windows 2003 to Dynamics GP 2013/SQL 2012/Windows 2012
1. Being that you are on eEnterprise 6.0/SQL2000/Windows 2003 you can upgrade to Dynamics 7.5/SQL2000/Windows 2003.
2. Upgrade from to Dynamics 7.5/SQL2000 to Dynamics 9.0/SQL 2000. You then will need to apply a hotfix for GP 9 so you can upgrade to GP 2010. I would recommend you apply Hotfix KB 971017 which will bring your databases to 9.00.0371. This is the minimum version required to upgrade to GP 2010. Click HERE to go to the GP 9.0 Download Page to grab the required patch.
3. Once your databases are on 9.00.0371 you will want to move your databases to SQL 2012 on Windows 2012. Refer to KB 878449 for move steps.
4. Next you will want to upgrade your databases to GP 2010 11.00.1914 or later since you are using SQL 2012. Click HERE to go to the GP 2010 Download Page to grab the required patch.
5. Last you will upgrade your databases to GP 2013.

Dynamics 7.0/SQL 2000/Windows 2003 to Dynamics GP 2013/SQL 2012/Windows 2012
1. First you will need to upgrade from Dynamics 7.0 to Dynamics 7.5/SQL 2000/Windows 2003.
2. Next you will want to upgrade to Dynamics 9.0/SQL 2000/Windows 2003.
3. Once you are on Dynamics 9.0/SQL 2000 you then will need to apply a hotfix for GP 9 so you can upgrade to GP 2010. I would recommend you apply Hotfix KB 971017 which will bring your databases to 9.00.0371. This is the minimum version required to upgrade to GP 2010. Click HERE to go to the GP 9.0 Download Page to grab the required patch.
4. Once your databases are on 9.00.0371 you will want to move your databases to SQL 2012 on Windows 2012. Refer to KB 878449 for move steps.
5. Next you will want to upgrade your databases to GP 2010 11.00.1914 or later since you are using SQL 2012. Click HERE to go to the GP 2010 Download Page to grab the required patch.
6. Finally you will be able to upgrade to any specific build of GP 2013.

Dynamics 8.0/SQL 2000/Windows 2003 to Dynamics GP 2013/SQL 2012//Windows 2012
1. First, you can move your Dynamics 8.0 databases to SQL 2012 on Windows 2012. Refer to KB 878449 for move steps.
2. Next you will want to upgrade your databases to GP 2010 11.00.1914 or later since you are using SQL 2012. Click HERE to go to the GP 2010 Download Page to grab the required patch.
3. Finally you will be able to upgrade to any specific build of GP 2013.

Dynamics GP 9.0/SQL 2000/Windows 2003 to Dynamics GP 2013/SQL 2012/Windows 2012
1. The first step depends on the version of GP 9 you are on. If you are on 9.00.0371 or later you can upgrade directly to GP 2010, however if you are not then you need to upgrade to 9.00.0371. Click HERE to go to the GP 9.0 Download Page to grab the required patch. If you are on a build later than 9.00.371 your upgrade paths may vary. Please visit the Upgrade Hot Topic page.
2. Once you are on 9.00.0371 or later you will want to move your databases to SQL 2012 on Windows 2012. Refer to KB 878449 for move steps.
3. Next you can upgrade directly to any build of GP 2010, I would recommend GP 2010 SP 3 (11.00.2044) as this will allow you to upgrade to any build of GP 2013. Click HERE to go to the GP 2010 Download Page to grab the required patch.
4. Finally you will be able to upgrade to any specific build of GP 2013.

Dynamics GP 10/SQL 2005/Windows 2003 to Dynamics GP 2013/SQL 2008 R2/Windows 2008 R2
1. The first step depends on the version of GP 10 you are on. If you are on 10.00.1779 you can upgrade directly to any build of GP 2013. However if you are on a build before 10.00.1779 you will need to upgrade to that build in order to upgrade to GP 2013. Click HERE to go to the GP 10.0 Download Page to grab the required patch. Please note that if you are on a build later than 10.00.1779 you will want to check your upgrade path on the Upgrade Hot Topic page.
2. Before you actually upgrade to GP 2013 you will want to move your databases to your Windows 2008 R2 machine that you will need to install SQL 2008 R2 on. Refer to KB 878449 for move steps.
3. You then can upgrade to GP 2013 on your Windows 2008 R2 machine.

Dynamics GP 10/SQL 2005/Windows 2003 to Dynamics GP 2013/SQL 2012/Windows 2012
1. The first step depends on the version of GP 10 you are on. If you are on 10.00.1779 you can upgrade directly to any build of GP 2013. However if you are on a build before 10.00.1779 you will need to upgrade to that build in order to upgrade to GP 2013. Click HERE to go to the GP 10.0 Download Page to grab the required patch. Please note that if you are on a build later than 10.00.1779 you will want to check your upgrade path on the Upgrade Hot Topic page
2. Before you actually upgrade to GP 2013 you will want to move your databases to your Windows 2012 machine that you will need to install SQL 2012 on. Refer to KB 878449 for move steps.
3. You then can upgrade to GP 2013 on your Windows 2012 machine.

Dynamics GP 2010/SQL 2008/Windows 2008 to Dynamics GP 2013/SQL 2012/Windows 2012
1. The first step depends on the version of GP 2010 you are on. If you are on 11.00.1860 you can upgrade directly to any build of GP 2013. However if you are on a build before 11.00.1860 you will need to upgrade to that build in order to upgrade to GP 2013. Click HERE to go to the GP 2010 Download Page to grab the required patch. Please note that if you are on a build later than 11.00.1860 you will want to check your upgrade path on the Upgrade Hot Topic page.
2. Before you actually upgrade to GP 2013 you will want to move your databases to your Windows 2012 machine that you will need to install SQL 2012 on. Refer to KB 878449 for move steps.
3. You then can upgrade to GP 2013 on your Windows 2012 machine.

We have 1 blog left in our Upgrade Blog Series! Continue to check in with our Upgrade Blog Series Schedule!

Remember to check out the latest Upgrade Manual and Upgrade Hot Topic for Microsoft Dynamics GP 2013!

Happy Upgrading!

Service Pack 1 for Microsoft Dynamics GP 2013 is now available!

Kelly Youells — Fri, 19 Apr 2013 12:00:00 GMT

We are very excited to announce the release of Service Pack 1 for Microsoft Dynamics GP 2013!! Check it out today!!

Microsoft Dynamics GP 2013 Product Download Page - NEW DVD including Service Pack 1 is here!
Customers - Click HERE
Partners - Click HERE

Microsoft Dynamics GP 2013 Service Pack, Hotfix and Compliance Update Page - Download the Service Pack 1 Patch HERE!!
Customers - Click HERE
Partners - Click HERE

Check out the FIX LIST and installation steps for Service Pack 1 in the 12.0SP1_install_guide_enus.pdf!

Here are the version updates for Service Pack 1!

Microsoft Dynamics GP	12.00.1412
Dexterity	12.00.0232
Project Accounting	12.00.1392
Fixed Assets Management	12.00.1377
Manufacturing	12.00.1407
Human Resources	12.00.1410
Field Services	12.00.1376
Cashbook Management	12.00.1412
Scheduled Instalments	12.00.1412
Collections Management This is a separate MSI on the SP page	12.0.14
Safe Pay	12.00.1383
Electronic Reconcile	12.00.1373
SmartList	12.00.1384
Cash Flow Management	12.00.1417
Excel-Based Budgeting	12.00.1375
HRM Solution Series	12.0.7
Payment Document Management	12.00.1412
Business Activity Statement	12.00.1412
Purchase Order Enhancements	12.00.1385
Enhanced Intrastat	12.00.1412
CoperSeries	12.00.1372
VAT Daybook	12.00.1412
Analytical Accounting	12.00.1391
Encumbrance Management	12.00.1406
SmartList Builder	12.0.21
ML Checks	12.00.1412
Payroll Integration to Payable	12.0.7
Certification Manager	12.0.7
Employee Health and Wellness	12.0.7
Fixed Assets Enhancements	12.00.1412
Export Financial Data	12.00.1412
Dynamics Online	12.00.1399
Date Effective Tax Rates	12.00.1412
Direct Debits & Refunds	12.00.1412

Now that Service Pack 1 is out, it is time to upgrade to Microsoft Dynamics GP 2013!! Check out our Upgrade Hot Topic for all your upgrade needs!!!

Customers - Click HERE
Partners - Click HERE

Enjoy!

Microsoft Dynamics GP 2013 is Upgraded - What's Next?

Kelly Youells — Thu, 18 Apr 2013 19:00:00 GMT

Hello Community!

You now have the DYNAMICS database and all company databases and modified reports and forms upgraded to Microsoft Dynamics GP 2013, so what is next? Each of you have your own project plans for the upgrade, however, here are some tips for the game plan following the Microsoft Dynamics GP 2013 database upgrade. Enjoy!

1. Backup!
Once the databases are upgraded, always make a SQL backup of the databases before moving forward with any next step. It is a good idea to login to Microsoft Dynamics GP 2013 and export all modified reports and forms to package files as well now that they are upgraded. Click Microsoft Dynamics GP | Tools | Customize | Customization Maintenance.

2. Enter your new Microsoft Dynamics GP 2013 Registration Keys!
All Customers must work with their Partner to obtain new registration keys for Microsoft Dynamics GP 2013. Login to Microsoft Dynamics GP 2013 and go to Microsoft Dynamics GP | Tools | Setup | Registration and enter the new registration keys.

3. Third Party Products/Customizations
All third party products and customizations have already been identified during the pre-upgrade planning phase. Once Microsoft Dynamics GP is upgraded, you can then move forward and install/upgrade all third party products you use with Microsoft Dynamics GP. Please work with the ISV that provides the third party product for steps to upgrade. Don't forget about all the additional customizations as well! Work with the Developer who created the customization for you to obtain the upgrade steps.

4. Client Machines and Terminal Server
Install Microsoft Dynamics GP 2013 at all client workstations and Terminal Servers. Make sure to install the exact same hotfix or service pack for Microsoft Dynamics GP 2013 at the clients and Terminal Servers that you used for the Microsoft Dynamics GP 2013 upgrade. If a different patch is used you could run into version errors launching Microsoft Dynamics GP 2013. Click HERE to download the Microsoft Dynamics GP 2013 Installation Guide for the Desktop/Rich Client installation.

5. Web Services
If you currently use Web Services, Web Services must also be upgraded to Microsoft Dynamics GP. You can install Web Services from the Microsoft Dynamics GP 2013 DVD for the upgrade. You can install Web Services from the Microsoft Dynamics GP 2013 DVD. Once installed, run the GP Web Services Configuration Wizard to upgrade the Web Services components in the DYNAMICS and company databases. If you use Business Portal or Workflow, Web Services must be upgraded first before those products. If you have custom integrations with Web Services, test out all integrations following the upgrade. Click HERE to download the Web Services Guides.

6. eConnect
The eConnect database objects are automatically upgraded when the DYNAMICS and company databases are upgraded with Microsoft Dynamics GP 2013 Utilities. If you have custom Pre and Post eConnect procedures, make sure to create those again following the database upgrade. If you have the eConnect Runtime installed on any client or server, use the Microsoft Dynamics GP 2013 DVD to install the latest eConnect Runtime components. If you have custom integrations with eConnect, test out all integrations to ensure everything works successfully. Click HERE to download the eConnect Guides

7. Business Portal
If you currently use Business Portal 4.0 with Microsoft Dynamics GP 10.0 or Business Portal 5.0/5.1 with Microsoft Dynamics GP 2010, you can upgrade directly to Business Portal 6.0 for Microsoft Dynamics GP 2013. Business Portal 6.0 is supported with SharePoint 2010 only and will be available very soon! Keep in mind that if you are not on SharePoint 2010, you will also need to upgrade your Business Portal SharePoint content database to SharePoint 2010 first before upgrading Business Portal. Business Portal 6.1 will be supported with SharePoint 2013 and will release after Business Portal 6.0. Please stay tuned to the Microsoft Dynamics GP 2013 Product Download page for the Business Portal releases!

Customers
https://mbs.microsoft.com/customersource/downloads/servicepacks/MDGP2013_Release_Download
Partners
https://mbs.microsoft.com/partnersource/downloads/releases/MDGP2013_Release_Download

8. Workflow
If you currently use Workflow with Microsoft Dynamics GP 10.0 or Microsoft Dynamics GP 2010 you can upgrade directly to Workflow for Microsoft Dynamics GP 2013. Workflow for Microsoft Dynamics GP 2013 is currently supported with SharePoint 2010 only at this time. If you are currently using Workflow with an older version of SharePoint, keep in mind that you will need to upgrade the Workflow SharePoint content database to SharePoint 2010 first. You can install Workflow from the Microsoft Dynamics GP 2013 DVD. Click HERE to download the Workflow Installation & Upgrade Guide.

9. Microsoft Dynamics GP SQL Reporting Services Reports.
The Microsoft Dynamics GP SQL Reporting Services Reports are automatically upgraded during the database upgrade as long as the Windows user has access to your SQL Reporting Services Site and you are using SQL Server Reporting Services 2008 or later. We no longer support SQL Server Reporting Services 2005. If you need to redeploy the SQL Reporting Services Reports following the upgrade to Microsoft Dynamics GP, click HERE to download the SQL Reporting Service Administrator Guide for Microsoft Dynamics GP 2013.

10. Business Analyzer
If you currently use Business Analyzer Desktop Tool for Microsoft Dynamics GP 2010 to view your SQL Reporting Services Reports, you can upgrade to the latest Business Analyzer for Microsoft Dynamics GP 2013. You can install the latest from the Microsoft Dynamics GP 2013 DVD. Click HERE to download the guide for Business Analyzer.

11. Don't Forget the Microsoft Dynamics GP 2013 Software Development Kits!
The software development kits (SDKs) are great resources to find all the new changes in Microsoft Dynamics GP 2013! If you are a Developer, check out the new SDK's for Microsoft Dynamics GP 2013! You can install all SDK's from the Microsoft Dynamics 2013 DVD.

12. Integration Manager
If you currently have integrations through Integration Manager, you will need to upgrade your .MDB or .IMD database file to Microsoft Dynamics GP 2013. You can install Integration Manager from the Microsoft Dynamics GP 2013 DVD. Once upgraded, make sure to test out all integrations to ensure they work successfully. Click HERE to download the Integration Manager Guides.

13. Personal Data Keeper
If you currently use Personal Data Keeper, you will need to upgrade that install to Microsoft Dynamics GP 2013. You can install Personal Data Keeper from the Microsoft Dynamics GP 2013 DVD. The wizard will walk you through the very simple installation.

14. Word Templates
All Word Templates automatically upgrade with the databases in Microsoft Dynamics GP 2013 Utilities. If your Word Templates are based on modified reports, make sure the Reports.dic is upgraded before testing out the Word Templates. Most importantly, make sure you can print the Standard modified report without issue before trying the Word Template report. If users need to continue to make changes to the Word Template reports through Microsoft Word, install the Microsoft Dynamics GP Add-in for Microsoft Word from the Microsoft Dynamics GP 2013 DVD.

15. US Payroll Tax Updates
If you are a US Payroll Customer, check for the latest tax updates in Microsoft Dynamics GP 2013 under Microsoft Dynamics GP | Maintenance | US Payroll Updates | Check for Tax Updates.

16. Management Reporter
FRx is no longer supported with Microsoft Dynamics GP 2013. The migration to Management Reporter is another important step in your upgrade plan if you have not migrated already. Please make sure to test out all of your Management Reporter reports once the databases are upgraded to Microsoft Dynamics GP 2013. Click HERE for more information regarding Management Reporter. Click HERE to go to the Management Reporter Product Team Blog for great information!

17. User Acceptance and Testing
It is highly recommended to create checklists for the users to test out all modules in use. Users should walk through the checklists in both the test upgrade and live upgrade environment. Once all users feel comfortable with the tests, have them sign off for each module. User acceptance is so important to ensure their processes work correctly in the new Microsoft Dynamics GP 2013 environment. This includes testing all transaction entry tasks, reports, daily, monthly and yearly routines and processes.

18. Manage Database Size
During the upgrade, the size of the database does grow to a fairly large size. Please check the size of each of the company databases to ensure you are comfortable with the size of the database based on the space requirements in your environment. You can certainly leave the databases as is or remove the extra space if you desire. Please work with your Database Administrator for assistance removing the extra space if needed.

19. Thinking about Web Client?
If you are thinking about implementing Web Client with Microsoft Dynamics GP 2013, check out our Videos to learn more! Work with your Partner to learn more about the infrastructure involved with the Web Client installation.

20. Remove the Old Installations
Once Microsoft Dynamics GP 2013 is up and running smooth, you can go ahead and un-install the prior installation to cleanup the machines.

I hope the above helps you with the game plan following the Microsoft Dynamics GP 2013 database upgrade!

We have 2 blogs left in our Upgrade Blog Series! Continue to check in with our Upgrade Blog Series Schedule!

Happy Upgrading!

Microsoft Dynamics GP 2013 – Upgrade Troubleshooting

Kelly Youells — Wed, 17 Apr 2013 00:32:00 GMT

CONGRATS!! You have come a long way with us in the Upgrade Blog Series journey! You now know how to upgrade to Microsoft Dynamics GP 2013. Now let’s dig in and learn how to troubleshoot the upgrade if you happen to run into issues. The most common upgrade cases that we take on a daily basis include the following:

1. Version Check Issues – Check Out the Blog Again!
2. Reports and Form Upgrade Issues – Check Out the How To Blog Again!
3. Table Conversion Issues

Chris shared a great blog on version checks and Sarah shared a great blog on how to upgrade your modified reports and forms. Those blogs will get you on the right track for those areas. Check them out again for review!! In this blog, I will focus on the table conversion.

The table conversion is the step in the upgrade where a certain set of tables go through a conversion process for the required Microsoft Dynamics GP 2013 feature changes. The DU000010 table in the DYNAMICS database contains the list of tables that will be converted to Microsoft Dynamics GP 2013. You can run the script below to find the list of tables that are converted for each Microsoft Dynamics GP release:

Microsoft Dynamics GP 2013
Select fileOSName from DYNAMICS..DU000010 where CodeName = 'GP12'

Microsoft Dynamics GP 2010
Select fileOSName from DYNAMICS..DU000010 where CodeName like 'GP11%'

Microsoft Dynamics GP 10.0
Select fileOSName from DYNAMICS..DU000010 where CodeName like 'GP10%' or CodeName like 'Montego'

Click HERE to download the complete table conversion table list! You can also refer to the Microsoft Dynamics GP 2013 Software Development Kit (SDK) for detailed table changes from the prior release. The SDK can be installed from the DVD under the Tools\SDK folder.

If you are currently on Microsoft Dynamics GP 10.0 and are upgrading to Microsoft Dynamics GP 2013, the conversion scripts for both Microsoft Dynamics GP 2010 and Microsoft Dynamics GP 2013 will be run against your company database even though you are not installing the Microsoft Dynamics GP 2010 client application for the upgrade.

The key to troubleshooting the table conversion is to first understand what happens to each table. You can then trace those steps in the Dexsql.log. The Dexsql.log is a tracing tool that will log everything that Microsoft Dynamics GP 2013 is doing during the upgrade process. This includes the table conversion process itself. If a table fails during the table conversion, you can use the steps to find where the failure happened in the Dexsql.log.

Table Conversion Steps for Each Table

1. Table is Renamed: Key Word RENAME
The first step for every table that goes through the conversion process is a table rename. The current table must first be renamed before the new Microsoft Dynamics GP 2013 table is created. This is like making a “backup” of the table. The most common naming convention used to rename the tables is the following:

GL00100 >> G00100L
SOP10100 >> S10100OP

As you can see from the above, the tables that start with 2 letters have the second letter placed at the end of the table. Those tables with 3 letters, have the second and third letter placed at the end. **TIP**When opening up the Dexsql.log for the first time to search for a table failure, always search on the renamed table. For example, if the GL00100 failed, you would start your search with G00100L to get to the start of the conversion process for that table.

Dexsql.log Snip It – Rename Table

2. Primary Key is Renamed: Key Word RENAME
A new primary key is created with the new Microsoft Dynamics GP 2013 table, therefore, the current primary key is also renamed. This does not necessarily mean the primary key is different from the previous release.

Dexsql.log Snip It – Rename Primary Key

3. New Microsoft Dynamics GP 2013 table is created: Key Word CREATE
Microsoft Dynamics GP 2013 Utilities uses the Dynamics.dic to create the new table in the required structure for Microsoft Dynamics GP 2013. The primary key, secondary indexes, dexterity procedures and bindings are also created during this process.

Dexsql.log Snip It – Create Table

**NOTE**The create table process is a very long process. In the Dexsql.log, you will see the start of the process with the CREATE TABLE. The end of the table creation process will be several “Default bound to column” messages like the following:

4. Check structure of new table, old table and/or dependent tables if applicable: Key Word SELECT
During the table conversion, Microsoft Dynamics GP Utilities may run select statements against the old renamed table, the newly created table or even completely different tables that the table conversion depends on. The selects are to validate the table structure of one or more tables.

Dexsql.log Snip It – Select Table

**NOTE**The select statement can also be after the Insert statement as well

5. Records Inserted from Old Table to New Table: Key Word INSERT
Now that the new Microsoft Dynamics GP 2013 table is created, Utilities must insert your records from the old table. This is the most common point of failure during the table conversion due to table structure issues. For example, if the old table is not in the correct structure, the insert will fail. Also, if the new Microsoft Dynamics GP 2013 table is not in the correct structure, the insert will also fail.

Dexsql.log Snip It – Insert into new Table

6. Renamed table is dropped: Key Word DROP
Once the insert statement inserting all records into the new table from the old table is successful, the old renamed table is dropped.

Dexsql.log Snip It – Drop Table

Once a table upgrades successfully the Status is set to a 0 in the DU000030 table indicating the table was upgraded successfully

Dexsql.log Snip It – DU000030 insert indicating table upgrade success

The Beauty of the Upgrade – The db_status & Rollback! – You Don’t Need to Restore!

The best part of the upgrade is each step is tracked in the db_status column in the DB_Upgrade table. This allows Utilities to “remember” where it started and stopped. The db_status of 23 is the table conversion step. Since Utilities remembers where it left off, you do not need to restore the database if the upgrade fails. If the upgrade fails, you can close out of Utilities, fix the issue and launch Utilities again. Because of the number in the db_status column in the DB_Upgrade table, Utilities will pick right up where it left off. AWESOME!

Utilities also does a great job when individual tables fail. If a table fails to convert, Utilities will rollback the table conversion process and set the table in its original state. For example, if you are upgrading from Microsoft Dynamics GP 2010 and the GL00100 table fails to upgrade, the upgrade will rollback the process and place the GL00100 back to the 2010 version with all of your records intact. SUPER AWESOME! Again, this allows you to close out of Utilities, take the steps needed to fix the table and start Utilities again without restoring!!

Let’s Troubleshoot a Table Conversion Failure!

When the table conversion fails, the following window will appear in Microsoft Dynamics GP 2013 Utilities. Microsoft Dynamics GP Utilities will stop on the first company that fails. For example, if you mark to upgrade 15 companies and the 5^thcompany fails, Utilities will not continue to upgrade the remaining 10 companies.

Steps to Troubleshoot a Table Conversion Failure

1. Don’t Panic!!
The first step is to not panic when you see a Red X next to your company. Hopefully, you are running the test upgrade first so you have time to troubleshoot. If you are not running a test upgrade, this blog will help you get the issue resolve fast!

2. DO NOT Restore the company database
As mentioned above, Microsoft Dynamics GP Utilities remembers where it left off. All troubleshooting can take place at the point of failure and no restore is required.

3. Close out of Utilities
When the Red X appears next to the company, close out of Microsoft Dynamics GP Utilities to start the troubleshooting process.

4. Determine what tables failed
Run the script below in the SQL Server Management Studio to determine what tables failed. Pay particular attention to the errordes column. This column usually provides enough detailed information to start troubleshooting without even looking at the Dexsql.log.

SELECT b.fileOSName, a.fileNumber, a.PRODID, a.Status, a.errornum, a.errordes, c.CMPANYID, c.INTERID
FROM DYNAMICS.dbo.DU000030 a
JOIN
DYNAMICS.dbo.DU000010 b
ON a.fileNumber = b.fileNumber
AND a.PRODID = b.PRODID
JOIN
DYNAMICS.dbo.SY01500 c
ON a.companyID = c.CMPANYID
WHERE (a.Status <> 0 or a.errornum <> 0) and a.Status <>15

In this example, the following tables are failing:

5. Based on the results above, check the Known Upgrade Issues and Critical Upgrade Issues lists
Even if you checked the Known Issues List and Critical Upgrade Issues prior to the upgrade, it is a good idea to check them if tables failed during the table conversion.

Upgrade Manual - Known Upgrade Issues
Upgrade Hot Topic - Critical Upgrade Issues

6. Based on the results above start troubleshooting! If the issue is not a Known Issue or Critical issue, start troubleshooting!
The errordes column above can provide great direction to start troubleshooting. In this example, we are upgrading from Microsoft Dynamics GP 2010. Since the errordes column above references a table structure issue prior to upgrading, we know that we must investigate the table structure. Again remember, that each table is rolled back if it fails, therefore, right now the SOP10200, IV70500 and the GL00201 are set back to the Microsoft Dynamics GP 2010 version. All troubleshooting can take place right in the failed state. DO NOT restore the database!

CHECK OUT the VIDEO for the resolution to the table conversion failure above!!
The video will walk you through resolving the issue and provide the troubleshooting steps that you can then apply to all future table conversion issues you run into on any table!
Click HERE to download the sample scripts used in the Video.

Continue to check out our Microsoft Dynamics GP 2013 Upgrade Blog Series Schedule for the remaining blogs!

Enjoy and Happy Upgrading!

Resources
Microsoft Dynamics GP 2013 Upgrade Hot Topic
Microsoft Dynamics GP 2013 Upgrade Manual
How to create a Dexsql.log

Microsoft Dynamics GP 2013 - Modified Dictionary Upgrade

Sarah Purdy — Thu, 11 Apr 2013 14:00:00 GMT

Good Morning!

After upgrading your DYNAMICS and Company Databases, you need to remember that if you have any modified forms or reports.dic files, those need to be upgraded as well. Here are the steps that you need to take to upgrade your modified forms and reports.dic files.

1. Make a backup of each reports dictionary or forms dictionary prior to the upgrade. The name of the reports dictionary for Microsoft Dynamics GP is Reports.dic and the name of the forms dictionary for Microsoft Dynamics GP is Forms.dic. We recommend making a copy of the .DIC files as well as exporting the modified reports and forms to a package file under Microsoft Dynamics GP | Tools | Customize | Customization Maintenance.

2. Open the Microsoft Dynamics GP 2013 launch file (Dynamics.set) and verify that the paths to the modified reports and forms are correct. The paths must be the location of the reports dictionary and forms dictionary from the previous release. For example, if your modified dictionaries are located out on a network share, the paths would look like the following:

:C:Program Files(x86)/Microsoft Dynamics/GP2013/Dynamics.dic
//server/dictionary_share/FORMS.DIC
//server/dictionary_share/REPORTS.DIC

3. Launch Microsoft Dynamics GP 2013 Utilities and click Next to get to the Additional Tasks window. In the Additional Tasks window, select Update modified forms and reports and click Process. The Locate Launch File window appears.

4. Select the Microsoft Dynamics GP 2013 launch file (Dynamics.set) that you use to start Microsoft Dynamics GP on this client, then click Next. The Update Modified Forms and Reports window appears.

5. Select Microsoft Dynamics GP and any additional components whose modified forms and reports dictionaries you’re upgrading.

6. For each component, choose the Details button, if necessary, to open the Product Details window, where you can select the location of the original dictionary from the previous release, such as Dynamics.dic or HR.dic. For example, if you are upgrading from Microsoft Dynamics GP 2010, you would browse to the Dynamics.dic in the Microsoft Dynamics GP 2010 client folder for the Microsoft Dynamics GP dictionary upgrade. If you are upgrading the Human Resources modified dictionaries, you would browse to the HR.dic from the previous release. Click OK in the Product Details window.

7. In the Update Modified Forms and Reports window, click Update.

Your modified forms and reports dictionaries are upgraded, and a report named Update2013.txt is generated, which contains information about upgraded modified forms. Be sure to review the report, located in the \Data folder, to verify that your modified forms have been upgraded correctly.

8. Click Next. The Additional Tasks window reappears.

At this point in time, you should know if your modified reports and forms upgraded successfully or not but to be sure you can review the Update2013.txt and Update2013.log, for more information about the modified forms and reports upgrade. I hope that this helps to answer your questions in regards to the steps to upgrade your modified reports and forms dictionaries!

VIDEO!! VIDEO!!!! Check out a video demo of upgrading your modified Reports.dic and Forms.dic files - Demo Video!

Check back with our Microsoft Dynamics GP 2013 Upgrade Blog Series Schedule for more upgrade blogs!!

Happy Upgrading!

Thank you!
Sarah Purdy
Microsoft Dynamics

Microsoft Dynamics GP 2013 - The Database Upgrade

Derek Albaugh — Tue, 09 Apr 2013 15:50:00 GMT

At this point, you should’ve planned the upgrade to Microsoft Dynamics GP 2013, gone through the system requirements for Microsoft Dynamics GP 2013, reviewed the upgrade guide, the hot topic for upgrading to Microsoft Dynamics GP 2013 and the known upgrade issues and are ready to begin the upgrade process itself. Let's take a closer look at the database upgrade process for Microsoft Dynamics GP 2013!

Database Upgrade - The Basics!

The database upgrade does take place in Microsoft Dynamics GP Utilities. The Upgrade Manual outlines the step-by-step process for the upgrade. Here are the basics...

1. Setup your test environment to test out the upgrade first.
2. Review the Upgrade Manual and Upgrade Hot Topic for the latest Known Issues and Pre-Upgrade Scripts.
3. Backup your existing DYNAMICS database and all company databases.
4. Verify you are on the correct patch to upgrade to Microsoft Dynamics GP 2013. The minimum version for Microsoft Dynamics GP 10.0 is 10.00.1779 and minimum version for Microsoft Dynamics GP 2010 is 11.00.1860.
5. Obtain all the code and installs for your integrating products.
6. Download the latest DVD for Microsoft Dynamics GP 2013.
7. Install Microsoft Dynamics GP 2013 and install all features/products you currently use.
8. If a newer patch has released, install the latest patch currently available for Microsoft Dynamics GP 2013. Refer to the Service Pack/Hotfix Download Page for Microsoft Dynamics GP 2013. The patch just needs to be installed prior to launching Microsoft Dynamics GP 2013 Utilities.
9. Launch Microsoft Dynamics GP 2013 Utilities and click Next through the wizard to first upgrade your DYNAMICS database and then select to upgrade all company databases.
10. When the Additional Tasks Window appears, the database upgrade is complete and successful. If the Upgrade Company Window returns your company with a Red X, troubleshooting must take place. Stay Tuned for the Troubleshooting Blog on April 16!

Database Upgrade Tables

1. DU000010

The DU000010 table in the DYNAMICS database is the ‘Utilities Update Files’ table. This table contains a list of all tables that must be upgraded. Microsoft Dynamics GP Utilities uses these records and the versions on each record to know what tables get upgraded when you’re going from one version or build of Microsoft Dynamics GP to another.

2. DB_Upgrade

The DB_Upgrade table is also held in the DYNAMICS database and is the first table looked at when you launch Microsoft Dynamics GP Utilities. This is the main version table reviewed during the version check process discussed in the previous blog. Once the upgrade begins, Utilities will change the db_verMajor, db_verMinor and db_verBuild to the new version that you’re upgrading to. Not all products have the same version/build number. The db_status column in the DB_Upgrade table will also change as the upgrade of the database processes. It begins at zero and increases along with each database upgrade step. A db_status of 23 is at the table conversion process for that database. When Utilities has finished the database upgrade process and the entire process is successful, the db_status is set back to zero. The db_verOldMajor, db_verOldMinor and db_verOldBuild values are also set to match those of the db_verMajor, db_verMinor and db_verBuild for each product when the database upgrade process is complete and successful.

3. DU000020

The DU000020 table is another table that holds the versions of each feature/product installed for each database. The versions in the DU000020 will remain at the previous release until all tables in the database are upgraded successfully. When a user launching into Microsoft Dynamics GP following the upgrade, the version in the DU000020 is checked similar to how Microsoft Dynamics GP 2010 Utilities checks the version in the DB_Upgrade table.

4. duLCK

The duLCK table is used by Utilities to put a lock on a database while it is being upgraded. This prevents users from logging into the company database during the upgrade process. Once Utilities has finished the upgrade of the database, it will remove the record thus releasing the lock on the database. If Utilities is shut down or closed improperly, for example if the machine reboots or through Task Manager, this record may still remain in the duLCK table and when you re-launch Utilities, there will be a lock icon next to the database, so you won’t be able to select it in order to upgrade until you close Utilities and delete the record(s) in the duLCK table.

5. DU000030

Lastly, is the DU000030 table or ‘Utilities Fail List’ table. When Utilities starts upgrading the tables within the database, it looks at the DU000010 table, as mentioned previously, to see what tables get upgraded. For every table upgraded, a record is inserted into the DU000030 table with a Status for the upgrade. The ‘Status’ column shows which tables failed the upgrade and which tables were successful. Some common statuses that are seen in this table are:

0 - The conversion ran to completion without error
2 - The table being converted or deleted was not found
15 - The table was already converted since the table’s structure matches the destination table definition.
25 - The path to the table could not be determined
70 - Script Error. An error occurred while running a script
135 - An error occurred and the table was renamed back to its original name and it contains the original data

**Stay Tuned for the Upgrade Troubleshooting Blog due out on April 16!!! We will talk more about what to do when tables fail!

Server VS. Client - Where Should you Upgrade?

You can launch Microsoft Dynamics GP 2013 Utilities for the upgrade from the server or any workstation. You are not required to install Microsoft Dynamics GP 2013 at the SQL Server. The upgrade can be launched from a client if you choose to keep the SQL Server clean of all application installs. The only difference may be just a slight slow down as we talk back and forth between the SQL Server and the workstation. This does not add much overhead however.

Upgrading all companies at once or one at a time?

Upgrading all companies at the same time or one at a time doesn’t make much of a difference as far as Utilities is concerned, it will upgrade the databases in the same manner regardless. If you choose to upgrade all company databases at the same time, which is the default setting in the ‘Update these companies?’ window, Utilities will run through all company database’s upgrade process, one after the other, and won’t stop until either all company databases are upgraded successfully or an error occurs on one of the company databases.

If you choose to upgrade one company database at a time, Utilities will upgrade that company database and then once it completes successfully, it will go back to the ‘Additional Tasks’ window in Microsoft Dynamics GP Utilities and you would need to close Utilities and re-launch it in order to upgrade the remaining company databases. If the company database has an upgrade error, that will show just like if you selected all companies to upgrade at the same time. Usually, only upgrading one company database at a time is used more during troubleshooting of a specific upgrade error in the company database, but again, there isn’t any repercussions of doing the upgrade in this manner, other than you must close and re-launch Utilities for each company database upgrade if choosing one company at a time.

Microsoft Dynamics GP 2013 Utilities is Not Responding - What Should I do?

A common question we get asked is about Microsoft Dynamics GP Utilities turning to a "white screen" and losing focus during the upgrade of the databases and/or showing ‘Not Responding’. This is actually normal and when this is encountered with Utilities the recommendation is to just let the upgrade run. If you feel the upgrade is locked up, please enable a SQL Server Profile Trace to verify there is no database activity. You will more than likely continue to see activity since the upgrade is more than likely still running.

VIDEO!! VIDEO!!! Check out the walk through demo video of the Microsoft Dynamics GP 2013 upgrade!!

Continue to check back with our Microsoft Dynamics GP 2013 Upgrade Blog Series Schedule to learn more about the Microsoft Dynamics GP 2013 Upgrade!

Happy Upgrading!!!

Microsoft Dynamics GP 2013 - Version Checks & Upgrades

Chris Bulson — Thu, 04 Apr 2013 12:00:00 GMT

Good Morning Community!

Every time you launch Microsoft Dynamics GP Utilities a version check is run. This is how Utilities knows that you’ve applied a service pack/hotfix/compliance update or new version of Microsoft Dynamics GP and that the databases need to be upgraded. Utilities will use the Dynutils.set file to figure out which products you have installed and where the DU*.DIC files are located. It then compares the versions listed in the DYNAMICS database with the dictionary versions to make sure that they match. It even goes a step further and checks several different tables for the module in the company databases to make sure the version matches.

If the versions of the dictionaries do not match the versions found in the databases Utilities assumes an upgrade needs to be run. It verifies that you are on a supported upgrade path and then kicks off the upgrade. If Utilities finds any kind of problem during this process it will throw a version check error.

“There was a problem ascertaining product version information. Microsoft Dynamics GP Utilities will now exit. Please check the duinstall.log file for more information.”

You will find the duinstall.log file in the \Data folder of your GP code folder. This is typically found at C:\Program Files(x86)\Microsoft Dynamics\GP2013\Data (C:\Program Files on 32-bit operating systems). You can find various errors in here which will give you a pretty good idea of why you are running into a problem. Some examples are:

Error: Product 0 does not support upgrading from version 10.0.1193
Error: You are attempting to configure an older version of product 0. Database 12.0.1343 Code 10.0.1579

The duinstall.log will usually have several of the above errors listed over and over again. This is because it is giving you an error for each product ID in each company it is checking against. You could have a lot of errors at the end of the duinstall.log file. I will go over some of the most common reasons you will run into these errors below and the steps you can take to resolve them.

Old Company Data

One of the most common problems we see is also the easiest to resolve. If you have data from an old company in the DYNAMICS database you may run into errors when attempting to upgrade. This problem will usually manifest itself as a bunch of errors in the duinstall.log file showing old versions of modules you use. You can download the Clear Companies.sql script from the following link to clean this up. If you have not already previously run this script it should be your first step in troubleshooting this error. (Note – This script will remove data for any companies that exist in DYNAMICS. but do not have a corresponding company database in SQL). **Make a backup of the DYNAMICS database prior to running the script.**

Clear Companies.sql

Unsupported Upgrade Path

Another common problem is that you are simply not upgrading along a supported upgrade path. We have every supported upgrade path for Microsoft Dynamics GP 2013 listed at the following site: GP 2013 Upgrade Hot Topic

You should already be very familiar with this site if you are performing an upgrade since we list all of the known upgrade problems that you may run into. Make sure that you are taking note of the version listed in both the ‘Updating From’ column as well as the ‘Patch Requirement…’ column. You can’t upgrade from the latest version of GP 2010 to the RTM version of GP 2013 for example. The far right column of this table also contains links to each GP versions respective KB download page so that you can upgrade as needed.

Specific Product\Module Version Issue

Error: Product 309 does not support upgrading from version ##.#.####

Let’s say that you are getting an error in the duinstall.log file indicating that Product 309 does not support upgrading from its current version. It can be any product or even multiple product ID’s but I’m using 309 for this example. You look in the Dynamics.set file and find that Product 309 is Fixed assets. The main question here is whether or not this module is actually used in this GP environment. If it is not a module that is being used then you should uninstall it using ‘Control Panel’ > ‘Programs and Features’ (add\remove programs) so that it is removed from the .set files. Then you can launch Utilities again and it should attempt to upgrade that product.

If it is a module that you are using or you would like to begin using you will need to open a support case.

If you are still running into problems after checking on the above common problems you can also open a support case. When you open a support case with us for an upgrade problem please run the Diagnostic tool that you are referred to. This will usually help us to provide you with a solution much quicker.

CHECK OUT the video demo of troubleshooting the 3 above mentioned issues below!!! Enjoy!!

Demo Video!

Continue to check back with our Microsoft Dynamics GP 2013 Upgrade Blog Series Schedule to learn more about the Microsoft Dynamics GP 2013 Upgrade!

Happy Upgrading!

Microsoft Dynamics GP 2013 - Known Upgrade Issues

Kelly Youells — Tue, 02 Apr 2013 14:06:00 GMT

Good Morning Community!

As we work with all of you on upgrade cases we do want to make sure we are sharing any known issues that we run into with the upgrade. We have a wonderful Documentation Team that does a great job with the Known Upgrade Issues list in the Microsoft Dynamics GP 2013 Upgrade Manual. We also have the capability to post any critical notice within 1 hour on our Upgrade Hot Topic. Please review the Upgrade Manual and Upgrade Hot Topic to stay on top of all known issues we post. We continually update this information! It is very important to review the known issues prior to the upgrade as we have several pre-upgrade scripts for you to run. You can take care of the issue before you even start the upgrade!

We currently have the following known upgrade issues for Microsoft Dynamics GP 2013 as of April 2, 2013:

**NOTE**All scripts for the known upgrade issues can be downloaded here.

1. Account Framework Table Conversion: We convert several tables that have account framework information in them. If the account framework tables in the company database, do not match the SY003001 and SY00302 tables in the DYNAMICS database, the upgrade will fail. Please run the Account_Framework_Validation.txt script from the known issues script library to validate your tables prior to the upgrade. If results are returned, please work with your Partner or contact Technical Support to talk about the options for those tables. Here are the tables we convert:

GL10110
GL10111
GL70500
GL70501
GL00100
GL00201
IV70500

2. Human Resources and Payroll Suite (10.0 only): If you currently use the following Human Resources and Payroll Suite modules and are on Microsoft Dynamics GP 10.0, the January 2013 hotfix is required for the upgrade to Microsoft Dynamics GP 2013. The January 2013 hotfix or any later patch release must be installed prior to launching Microsoft Dynamics GP 2013 Utilities. Click HERE to go to the service pack/hotfix page for Microsoft Dynamics GP 2013.

Product ID 1911 - HRM Solution Series
Product ID 4522 - Payroll Integration to Payable
Product ID 4933 - Certification Manager
Product ID 4955 - Employee Health and Wellness

3. Collections Management: If you currently use Collections Management with Microsoft Dynamics GP 2010 and are on version 11.00.2164, a new MSI is required for the upgrade to Collections Management for Microsoft Dynamics GP 2013. The new Collections Management MSI, must be installed prior to launching Microsoft Dynamics GP 2013 Utilities. Click HERE to go to the service pack/hotfix page for Microsoft Dynamics GP 2013. Please refer to the Notes section to obtain the new MSI for Collections Management.

4. Database Compatibility: If you are moving to a new SQL Server in addition to the upgrade to Microsoft Dynamics GP 2013, you can restore your databases to the new SQL Server and start your upgrade. Please refer to KnowledgeBase Article 878449 for the steps to move to a new SQL Server. Once the databases are restored to the new SQL Server, you must change the database compatibility.

a. In the SQL Server Management Studio. right-click your database and click Properties.
b. Under Select a Page on the left, click Options.
c. Change the Compatibility Level to match the version of SQL Server you are running. SQL 2005 = 90, SQL 20082008 R2 = 100, SQL 2012 = 110.

5. Purchase Order Tables: If there are detail records in the POP10110 and the POP30110 that do not have a matching header record in the POP10100 and the POP30100, the upgrade may fail on those tables. Run the Invalid_Records_POTables.txt script from the known issues script library to validate all detail records have a header record. If results are returned, you can either remove the detail records or run checklinks in the current version you are running.

6. Server Drop Down List Blank: When launching Microsoft Dynamics GP 2013, the Server drop down list may be blank. The Server drop down is the OBDC DSN that Microsoft Dynamics GP needs to connect to your SQL Server databases. If the ODBC DSN is an older version or an x64 DSN, it will not show up in the list. Please make sure you have a 32-bit ODBC DSN created using either the Native Client 10.0 or Native Client 11.0 driver. Click HERE for the steps to setup an ODBC DSN.

7. Payroll Work Tables (10.0 only): If upgrading from Microsoft Dynamics GP 10.0 and you use payroll, run the Payroll_Work_Tables.txt from the known issues script library to clear the Payroll Work Tables. If records exist in those tables, the upgrade will fail on the UPR10*** tables.

8. Workflow Documents Must be Final Approved: If you use our Workflow for GL/PM/RM batches, Purchase Orders, Vendor Approvals, Credit Limit Overrides, Sales Quotes. Employee Onboarding, etc., all Workflow Documents must be final approved prior to the upgrade. No documents can be pending. The upgrade does check for this and will stop Utilities and provide a report showing what documents need to be approved.

9. Microsoft Dynamics Adapter Service: If you use the CRM Connector for Microsoft Dynamics GP and the Microsoft Dynamics Adapter Service is running on the server where you are performing the upgrade, please stop the service temporarily. Once the upgrade is complete, the Microsoft Dynamics Adapter Service can be restarted.

10. General Ledger Transaction History Record Count (10.0 only): If you are upgrading from Microsoft Dynamics GP 10.0, run the following script to get a feel for the record count in the GL30000 table.

select count(*) from GL30000

The GL30000 is the GL Transaction History table and can be very large. If you have millions and millions of transactions in the GL30000, please make sure to run a test upgrade to Microsoft Dynamics GP 2013. We do have a big conversion on the GL30000 that may slow down the upgrade. Running a test upgrade will allow you to benchmark the upgrade for your environment. Some tips!!! Make sure you have enough disk space on the drives where the MDF and LDF are located. Also, manually grow the size of your LDF to accommodate the size of the largest table. Grow the LDF of your company database and TEMPDB.

11. Microsoft Dynamics GP Utilities Stops Responding: When you launch Utilities for the upgrade, most of the processing is done on the SQL Server. If you happen to client away, Utilities may appear to stay white and show "not responding". Please do not close out of Utilities, the upgrade is still running. Please give the upgrade time to continue working. If you feel the upgrade is hanging or locked up, please start a SQL Server Profiler trace to review activity.

Please review the known issues above prior to your Microsoft Dynamics GP 2013 upgrade! Running the scripts above will for sure eliminate issues in the long run! Remember to always run a test upgrade first!

Continue to follow our Upgrade Blog Series! More blogs to come!

Happy Upgrading!

Microsoft Dynamics GP 2013 Upgrade Planning – Let’s Get Started!

Greg Willson — Thu, 28 Mar 2013 11:20:00 GMT

Are you thinking about upgrading to Microsoft Dynamics GP 2013 but not sure where to get started? You’ve come to the right place, so keep on reading and be sure to check back for the complete Microsoft Dynamics GP Upgrade blog series!

One of the first things you need to think about when planning your upgrade is; will your current hardware support the new version?

Make sure to check the system requirements for Microsoft Dynamics GP 2013 to see if your current hardware will still meet the minimum system requirements. Look at your client machines as well as the server recommendations. Here is the link to the “System Requirements for Microsoft Dynamics GP 2013” page.

If you use any of the Dynamics GP Web Applications (Workflow, Business Portal, Web Services, SSRS), here is the link to the “System Requirements for Microsoft Dynamics GP 2013 Web Applications” page.

Note: The Dynamics GP “Web Applications” are not to be confused with the “GP Web Client”. The GP Web Client has it’s own system requirements.

Often times with a major version upgrade (as opposed to a service pack update) it’s quite common to upgrade the server hardware at the same time as the upgrade. Many people have asked me, “Should I perform the upgrade on the existing server, then move to the new server? Or should I move to the new server first, then perform the upgrade?”

The answer to that question somewhat depends on what version you are upgrading from, however I always recommend whenever possible to perform your upgrade on the new server for one simple reason: You leave the current production environment alone! Another benefit when moving to new hardware is it’s very easy to do a Test upgrade first on the new server while business operations continue on the existing server. You will then be well prepared to handle any upgrade issues when performing the Live upgrade. Of course, we recommend to always plan on doing a test upgrade! The increased time/cost of doing a test upgrade is very easily outweighed by being down for an extra day or two if you encounter problems during a Live upgrade.

If you will be moving your GP databases to a new SQL server as part of your upgrade, you will want to bookmark this KB article: “How to transfer an existing Microsoft Dynamics GP, Microsoft Small Business Financials, or Microsoft Small Business Manager installation to a new server that is running Microsoft SQL Server ”.

The other thing to consider when planning your upgrade is what version of Microsoft Dynamics GP are you currently on?

Why is this important? Because depending on the version of GP that you are currently running, you may have to perform multiple upgrades to get to GP2013. GP upgrades support a two version jump. That means you can upgrade from 9.0 directly to 2010, or GP10.0 directly to GP2013, but you cannot upgrade directly from 9.0 to GP2013 because that is a three version difference; 10.0, 2010, 2013. You would have to do an upgrade to 10 or 2010 first to get to a supported upgrade path before making the move to GP2013. It’s also possible that you may need to apply a service pack to your existing environment so you can get to a supported upgrade path. Here is a link to the “Upgrading to Microsoft Dynamics GP 2013” page, also referred to as our “Hot Topics” page (each supported GP version has a “Hot Topics” page).

This page lists all the valid upgrade paths for upgrading to Dynamics GP 2013. As you can see from this example, you will note that in order to upgrade from GP10 to GP2013, you must be on at least GP10 build 10.00.1779 which is after GP10 SP5 (2011 US Payroll Year End update KB2599501).

If you are on GP 2010, you must be on at least build 11.00.1860 which is after GP2010 SP2 (2011 US Payroll Year End update KB2599505).

If your current GP 10 or GP2010 environment in on an older build, prior to build 10.00.1779 or 11.00.1860, then you will need to first apply a Service Pack to your existing environment before you will be able to upgrade to GP2013.

Also on the “Upgrading to Microsoft Dynamics GP 2013” page, we post critical update notes such as known upgrade issues to be aware of and links to important upgrade resources like system requirements, upgrade related documentation and upgrade specific blog articles from this blog. One thing I’d like to specifically point out is the link to the “Dynamics GP 2013 Upgrade Manual”. This manual contains an upgrade checklist, discusses system requirements, hard disk space considerations for the update process, data and system preparation and many other key elements of the overall upgrade process.

By reviewing this guide before your upgrade you can avoid a lot of surprises. More of the actual upgrade process will be discussed in future posts on this blog.

Check out our Upgrade Blog Series for future blog dates!

Happy Upgrading!

Microsoft Dynamics GP 2013 Upgrade Blog Series Schedule!!

Kelly Youells — Mon, 25 Mar 2013 08:30:00 GMT

Microsoft Dynamics GP 2013 has released and it is time to start planning your upgrade to Microsoft Dynamics GP 2013! Are you ready to upgrade to Microsoft Dynamics GP 2013?

The following Upgrade Blog Series for Microsoft Dynamics GP 2013 will provide you with the information you need to successfully upgrade to Microsoft Dynamics GP 2013! Check it out!!!

March 28 - Upgrade Planning - Let's Get Started!
April 2 - Known Upgrade Issues
April 4 - Version Checks & Upgrades - Check out the video!!!
April 9 - Database Upgrade – The Details! - Check out the video!!!
April 11 - Modified Dictionary Upgrade - Check out the video!!!
April 16 - Upgrade Troubleshooting - Check out the video!!!
April 18 – Microsoft Dynamics GP is Upgraded - What's Next?
April 19 - Service Pack 1 for Microsoft Dynamics GP 2013 is now available!!

***BONUS BLOG ARTICLES***

April 23 - Complete Upgrade Paths for Microsoft Dynamics GP, Windows and SQL Server- OLD versions included!
April 25 - Value Cannot Be Null - An Error When Navigating the Home Page or Area Pages - FIX provided!!

Stay tuned for the details you need to know for the upgrade to Microsoft Dynamics GP 2013 including step-by-step videos!

Happy Upgrading!

Last Chance to Come to the Convergence Support Help Desk!!!

Kelly Youells — Thu, 21 Mar 2013 12:55:00 GMT

Hello Convergence Attendees!

Thanks to all of you who have stopped by the Support Help Desk in the Microsoft Solutions Experience! We have had a great time hearing from all of you! Today is your last chance to stop on by the Help Desk!

Check out the Microsoft Dynamics GP 2013 What's New Guide!
http://www.microsoft.com/en-us/download/details.aspx?id=34664

Help Desk Hours:
Thursday, March 21 - 10:30AM - 3:00PM

Top 10 Reasons Why You Should Come to the Help Desk at Convergence!

1. Stop on over and chat with two of our Escalation Engineers, Jason and Aaron, to learn more about the NEW Web Client for Microsoft Dynamics GP 2013!

2. Sit down and visit with our resident Payroll and Human Resources Escalation Engineer, Terry, to learn more about the NEW Build Check File Exceptions Report and much more in Microsoft Dynamics GP 2013!

3. Got a Distribution question? Come on over and chat with our awesome Distribution Engineers, Maria, Deseree and Kelly, regarding the NEW Document Attach feature in Microsoft Dynamics GP 2013 and much more!

4. Do you have Project Accounting? Have a chat with our top Project Accounting Expert, Pam, for all your Project Accounting needs!

5. How about Financials? Come on down to the Help Desk and chat with our rockin' Financials folks, Ken, Andrea, Cheryl and Jennifer for all your Financial module needs!

6. Are you a Developer? Pull up a chair and have a chat with one of our Escalation Engineers, Lee, for all your Microsoft Dynamics GP Dev needs!

7. Is Manufacturing on your mind? Chat with our awesome Manufacturing Team, Becky and one of our Escalation Engineers, Tammy to get all your Manufacturing questions answered!

8. Are you ready to upgrade to Microsoft Dynamics GP 2013 or do you have questions regarding the install, Business Portal or Workflow? Our System Folks, Lucas, Sarah, Jonathan and myself are ready to help out with all your system related questions. Come and visit!

9. Do you currently have an ongoing Technical Support case and have questions? Come and find us for a quick chat regarding your Support cases!

10. Get to know our Technical Support Engineers! Even if you do not have any questions for Support, come and see us! Convergence is a great opportunity to connect and meet the Technical Support Team that you have worked with over the phone.

Safe travels back home to all of you and see you at the next Convergence!

Convergence 2013 - Come to the Microsoft Dynamics GP Help Desk!

Kelly Youells — Tue, 19 Mar 2013 11:20:00 GMT

Hey Community and Convergence Attendees!

We had a great first day of Convergence in New Orleans! The Microsoft Dynamics GP Technical Support Team is manning the Help Desk in the Microsoft Solutions Experience. Come and visit us today! We are excited and ready to answer your questions regarding Microsoft Dynamics GP 2013!

Check out the Microsoft Dynamics GP 2013 What's New Guide!
http://www.microsoft.com/en-us/download/details.aspx?id=34664

Help Desk Hours:
Tuesday, March 19 - 12:00PM - 6:00PM
Wednesday, March 20 - 8:00AM - 6:00PM
Thursday, March 21 - 10:30AM - 3:00PM

Top 10 Reasons Why You Should Come to the Help Desk at Convergence!

1. Stop on over and chat with two of our Escalation Engineers, Jason and Aaron, to learn more about the NEW Web Client for Microsoft Dynamics GP 2013!

2. Sit down and visit with our resident Payroll and Human Resources Escalation Engineer, Terry, to learn more about the NEW Build Check File Exceptions Report and much more in Microsoft Dynamics GP 2013!

3. Got a Distribution question? Come on over and chat with our awesome Distribution Engineers, Maria, Deseree and Kelly, regarding the NEW Document Attach feature in Microsoft Dynamics GP 2013 and much more!

4. Do you have Project Accounting? Have a chat with our top Project Accounting Expert, Pam, for all your Project Accounting needs!

5. How about Financials? Come on down to the Help Desk and chat with our rockin' Financials folks, Ken, Andrea, Cheryl and Jennifer for all your Financial module needs!

6. Are you a Developer? Pull up a chair and have a chat with one of our Escalation Engineers, Lee, for all your Microsoft Dynamics GP Dev needs!

7. Is Manufacturing on your mind? Chat with our awesome Manufacturing Team, Becky and one of our Escalation Engineers, Tammy to get all your Manufacturing questions answered!

8. Are you ready to upgrade to Microsoft Dynamics GP 2013 or do you have questions regarding the install, Business Portal or Workflow? Our System Folks, Lucas, Sarah, Jonathan and myself are ready to help out with all your system related questions. Come and visit!

9. Do you currently have an ongoing Technical Support case and have questions? Come and find us for a quick chat regarding your Support cases!

10. Get to know our Technical Support Engineers! Even if you do not have any questions for Support, come and see us! Convergence is a great opportunity to connect and meet the Technical Support Team that you have worked with over the phone.

Have a great Convergence!

Kelly

Collections Management Upgrade to Microsoft Dynamics GP 2013 Version 12.00.1343

Kelly Youells — Thu, 14 Mar 2013 19:54:00 GMT

Hi Community,

**Issue Resolved**See Steps Below!!

We just posted a new notice on the Microsoft Dynamics GP 2013 Upgrade Hot Topic regarding the upgrade of Collections Management to the January 2013 Hotfix for Microsoft Dynamics GP 2013 (Version 12.00.1343).

Customers: https://mbs.microsoft.com/customersource/support/selfsupport/hottopics/hot_topic_mdgp2013upgrade.htm?printpage=false

Partners: https://mbs.microsoft.com/partnersource/support/selfsupport/hottopics/hot_topic_mdgp2013upgrade.htm?printpage=false

If you currently use Microsoft Dynamics GP 2010 and have installed the January 2013 hotfix for Microsoft Dynamics GP 2010 (Version 11.00.2164), there is currently no upgrade path to Microsoft Dynamics GP 2013 for Collections Management.

If you attempt the upgrade, you will receive the following error when launching Microsoft Dynamics GP 2013 Utilities:

"There was a problem ascertaining product version information. Microsoft Dynamics GP Utilities will now exit. Please check the duinstall.log for more information"

If you go to the GP 2013\Data folder and open the duinstall.log, you will see the following error:

Error: Product 1157 does not support upgrading from version 11.0.26.

***This issue is now resolved*** See resolution steps below!

1. Close out of Microsoft Dynamics GP 2013 Utilities.
2. Click HERE to download the required MSI for the Collections Management upgrade to Microsoft Dynamics GP 2013 version 12.00.1343.
3. If Collections Management for Microsoft Dynamics GP 2013 is currently installed on the machine, go to Programs and Features and remove the installation.
4. Double-click the new updated MSI to install Collections Management for Microsoft Dynamics GP 2013.
5. Launch Microsoft Dynamics GP 2013 Utilities again for the upgrade.

Thanks!

Continuous "Loading Session Information" after logging into Dynamics GP 2013 Web Client

Jennifer Reinhardt — Thu, 14 Mar 2013 12:52:00 GMT

ISSUE: When logging into the Microsoft Dynamics GP 2013 Web Client a user enters their domain credentials on the Logon.aspx page then clicks Sign in. Users are expecting to see the Dynamics GP log in window, but instead users see “Loading Session Information” continuously and nothing happens.

CAUSE: In the Security tab of the Internet Options window the Internet Security Level for the zone was set to High or there have been Security Settings disabled for the user.

With the Security Level setting at high there are 2 Security Settings that are disabled that need to be enabled in order for the user to get into Web Client. In the Internet Options window click Custom Level, which will bring up the Security Settings window, below are the 2 settings that are disabled:

RESOLUTION: There are a few resolutions to address this issue which require edits to the users Internet Options. When providing these resolutions, make sure the user is selecting the appropriate zone (Internet or Local Intranet) to view/change the security settings. In my example I’m using the Local Intranet, but the user could be using the Internet zone.

Option 1:

Add the GP website to the list of Trusted Sites. In Internet Options click the Security Tab and click Trusted Site and then click the Sites button. Enter the GP website and click Add to add the site to the list of Trusted Sites.

Option 2:

Enable the “Active Scripting” and “Run ActiveX Controls and plug-ins” security settings. In the Internet Options window, click the Security tab, select the appropriate zone and then click Custom Level. Click to Enable “Active Scripting” and “Run ActiveX Controls and plug-ins”:

Option 3:

Set the Security Level for the zone to Medium-High or lower, instead of High. In the Internet Options window, click the Security tab, select the appropriate zone and then click Custom Level. Once in the Security Settings choose Medium-High to reset the custom settings to and then click the Reset button.

NOTE: If the company has a Group Policy Object (GPO) that pushes down internet settings to all domain machines these changes will be overridden with the Internet settings from the GPO. To prevent this, an admin would need to make one of these changes above to the GPO at the domain level which will roll down to the end users workstations.

Microsoft Dynamics GP 2013 .MSP Patch Files Removing Information from Dex.ini and Registry

Sarah Purdy — Wed, 13 Mar 2013 15:50:00 GMT

We have identified an issue with Microsoft Dynamics GP 2013 where the .msp files are removing registry entries and part of the Pathname= line in the Dex.ini when you RE-APPLY a patch. The first install of the patch works fine. The issue comes into play if you reapply the patch again on either a single instance or multi-instance. The Country and System Database Name get blanked out in the registry. The Pathname= line in the Dex.ini gets modified.

The current workaround when re-applying the .msp to a specific instance of GP 2013 is to do the following:

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry subkey:
Microsoft Dynamics GP 10.0 and later versions

32-bit environment
HKEY_LOCAL_MACHINE\Software\Microsoft\Business Solutions\Great Plains\1033

64-bit environment
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Business Solutions\Great Plains\1033

3. Expand the folder for the instance of Microsoft Dynamics GP you want to patch.

Note The DEFAULT folder is for the default installation. The Inst01 folder is for the second instance of Microsoft Dynamics GP. For example, if you want to patch the second installation, expand the Inst01 folder.

4. Click the SETUP folder, double-click the Product Code, and then copy the code.
5. Exit Registry Editor.
6. Open up a Command Prompt by right-clicking on it and selecting Run As Administrator.
7. To install the .MSP file, type the following, and then click OK:

C:\updatename.msp /n {E979C594-95F9-4E3A-985D-A1DFDF403227}

Note Replace "C:\updatename.msp" with the path to the .MSP file and the name of the .MSP patch file. Replace "{E979C594-95F9-4E3A-985D-A1DFDF403227}" with the Product Code that you copied in step 4.

The current workaround when re-applying the .msp to all instances of GP 2013 on a machine is to do the following:

1. Open up a Command Prompt by right-clicking on it and selecting Run As Administrator, type in the following:

msiexec.exe /p C:\updatename.msp

(Example: msiexec.exe /p C:\ MicrosoftDynamicsgp12-kb2799678-enu.msp)

Note Replace "C:\updatename.msp" with the path to the .MSP file and the name of the .MSP patch file.

2. Click OK.

Thank You!
Sarah

Microsoft Dynamics GP 2013 Web Client Causing Internet Explorer Crash?

Lucas Miller — Thu, 07 Mar 2013 19:38:00 GMT

Hello Community,

We’ve recently received a couple reports of users who have deployed the Microsoft Dynamics GP 2013 Web Client who see their web browse give the following error and crash upon login:

If you look at the details of the error you will see the following:

Problem signature:

Problem Event Name:                      APPCRASH
Application Name:                             IEXPLORE.EXE
Application Version:                          10.0.9200.16521
Application Timestamp:                   51207618
Fault Module Name:                         npctrl.dll
Fault Module Version:                      5.1.10411.0
Fault Module Timestamp:               4f851e71
Exception Code:                                c0000094
Exception Offset:                               0001d700
OS Version:                                        6.1.7601.2.1.0.272.7
Locale ID:                                           1033
Additional Information 1:                 0a9e
Additional Information 2:                 0a9e372d3b4ad19135b953a78882e789
Additional Information 3:                 0a9e
Additional Information 4:                 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:

C:\Windows\system32\en-US\erofflps.txt

The key here is that the faulting module is listed as “npctrl.dll”. Our research has discovered that this error points to a current compatibility issue between Silverlight 5 and VMware. This issue has been triaged by the Silverlight team and a fix is scheduled to be released soon.

If you need to access a Web Client installation that is hosted on a VMware machine you will need to log in from a machine that is not a VMware image. Please note that this may require you to reinstall the GP 2013 Web Client if you used a self-signed certificate as that would not allow you to log in from any other machine. If you did use a self-signed certificate you will need to reinstall using a certificate that can be trusted throughout your domain (e.g. Active Directory Certificate Services or a 3rd party certificate). The other workaround is to reinstall the GP 2013 Web Client on a virtual machine that uses Hyper-V, which has not displayed any compatibility issues.

Thanks!

Unlimited PDK users on GP 2013

Pam Peterson — Fri, 01 Mar 2013 03:00:00 GMT

Hi All,

With the new licensing changes rolled out for Microsoft Dynamics GP 2013, I wanted to clarify something that we have gotten some questions on in Support in regards to Personal Data Keeper (PDK).

PDK is not on the price list, and hasn’t been for many years. You receive it when you purchase “Project Time & Expense” which is actually the Business Portal portion of the product. This is now available with the Perpetual Starter Pack. With this you receive a set a registration keys for PDK that provide you with PDK users. In versions past you would be given a PDK user for each GP user plus 1. However, if you needed more users than that, you would need to purchase them either individually or as packs since the count was tracked on a named user (not concurrent) basis and was separate from the GP users. This could add up in a hurry depending on the number of people you had that wanted to enter remote timesheets and expenses!

So I am happy to say that on GP 2013 we are providing unlimited PDK users. After entry of the PDK registration key in the PDK – Registration window you will have 9,999 licenses to use. Should you need more than that, well, we will have to cross that bridge when/if it occurs.

One additional note - Project Accounting is not available unless you purchase the Perpetual Extended Pack so you really need it before you can take advantage of the PDK functionality offered in the Starter Pack.

I hope this helps clear up some confusion out there.

Have a good day!

Pam Peterson

Phasing out the Penny in Canada

Angela Melhus — Tue, 26 Feb 2013 15:00:00 GMT

The Government of Canada has announced it is going to phase out the penny from the Canada's coinage system.

Microsoft Dynamics GP has researched this situation and we are aware Canada is phasing out distributing new pennies. From what we have discovered at this time, we do not have to make any changes. Electronic payments can continue using pennies. Customers may want to evaluate their item pricing structure but that is also not required.

Here is an example of how you can set this up in Microsoft Dynamics GP:

Create an account for the penny difference in the Account Maintenance window (Cards > Financial > Account).

Assign the account to the Writeoffs account in the Customer Account Maintenance window (Cards > Sales > Customer > Accounts) or in the Posting Account Setup window (Microsoft Dynamics GP > Tools > Setup > Posting > Posting Accounts) for the Writeoffs account under Sales.

Enter an Invoice in the Sales Transaction Entry window (Transactions > Sales > Sales Transaction Entry) and post it.

Enter a Cash Receipt for the Cash payment in the Cash Receipts Entry window (Transactions > Sales > Cash Receipts) for the amount minus the penny/pennies and post it.

Apply the Cash payment to the Sales/Invoices document in the Apply Sales Documents window (Transactions > Sales > Apply Sales Documents). Enter the appropriate Writeoff amount in the Writeoffs field, and then click Post. Choose to print the Discounts/Writeoffs Journal report which prints the RM Apply Document Journal report as seen below.

Note: Another option would be to use the Write Off Documents Routine (Microsoft Dynamics GP > Tools > Routines > Sales > Write Off Documents).

For more information on phasing out the penny in Canada, you can click the following links: