With the new release of Microsoft Dynamics GP 2013 R2, we do want to make sure we are sharing any known issues that we run into with the upgrade of the new release so that you can be the most prepared for your upgrade.  We do have great documentation on the known upgrade issues list in the Microsoft Dynamics GP 2013 Upgrade Manual.  Please review our Upgrade Manual and Upgrade Hot Topic to prepare and make yourself aware of all known issues that may arise during your upgrade.  We do continually update this information!  Again, it is very important to review the known issues prior to upgrades as we have several pre-upgrade scripts for you to run.  Along with reviewing the known issues prior to upgrade, it is always recommended to perform a test upgrade to insure that you will have minimal downtime when it comes time for your production upgrade.

 We currently have the following known upgrade issues for Microsoft Dynamics GP 2013 R2 as of May, 2014:

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 Upgrade Guide 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 Upgrade Guide 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 R2 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!

Thanks,
Lance

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 Diagnostictool 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 R2 New Feature Blog Series Scheduleto learn more about the Microsoft Dynamics GP 2013 Upgrade!

Happy Upgrading!

Hopefully, at this point, you’ve looked at our prior Dynamics GP 2013 R2 Upgrade blogs that have been released beginning April 29^th, 2014:

--Lifecycle blog

--Upgrade Planning

--Known Upgrade issues

--Version Checks and Upgrades

If you haven’t already looked through these prior blogs, I would highly recommend it.

I would also recommend looking at the System Requirements for Microsoft Dynamics GP 2013 R2 page and the ‘Upgrading to Microsoft Dynamics GP 2013 R2’ hot topic as well, if you haven’t already done so.

***Note: This blog will be updated with links to the documentation and media once it becomes available to the public. Please return to this blog once Dynamics GP 2013 R2 is released, for links to the documentation and additional information.***

Database Upgrade - The Basics!

The upgrade to Microsoft Dynamics GP 2013 R2 is the same upgrade process that we’ve had in prior versions, in that 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/system database and all company databases.

4. Verify you are on the correct version/build of your current Microsoft Dynamics GP environment in order to upgrade to Microsoft Dynamics GP 2013 R2. 

**Note: The minimum versions for Microsoft Dynamics GP 10.0, GP 2010 and GP 2013 aren’t released at this time. This blog will be updated with this information as soon as it is released.

5. Obtain all the code and installs for your integrating products.

6. Download the latest DVD for Microsoft Dynamics GP 2013 R2.

7. Install Microsoft Dynamics GP 2013 R2 to include all modules that you currently have installed on your current version of Dynamics GP 2010 or GP 10.0.

         or

     If you’re currently already on Dynamics GP 2013 at a pre-R2 version/build, you’ll need to install the Dynamics GP 2013 R2 patch to update your current Dynamics GP 2013 system.  Refer to the Service Pack/Hotfix Download Page for Microsoft Dynamics GP 2013 for the R2 patch. 

9. Launch Microsoft Dynamics GP 2013 R2 Utilities and after the version check, it’ll detect that you have databases that need to be upgraded. Click Next through the wizard to first upgrade your DYNAMICS/system database and then select to upgrade all company databases, as needed.

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 ‘Modified Dictionary Upgrade’ being released on May 15^th, 2014 for information on upgrading your modified forms and modified reports.

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

**Note: The ‘’Upgrade Troubleshooting’ blog will be released on May 20^th, 2014, in which 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 R2 Utilities for the upgrade from the server or any workstation.  You are not required to install Microsoft Dynamics GP 2013 R2 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 slowdown 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.

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

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

Happy Upgrading!!!

Hello!

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!

Continue to check back with our Microsoft Dynamics GP 2013 R2 New Feature Blog Series Schedule to learn more about the Microsoft Dynamics GP 2013 Upgrade! for more upgrade blogs!!

Happy Upgrading!

Thank you!
Sarah Purdy
Microsoft Dynamics

HELLO ALL!

With the release of Microsoft Dynamics GP 2013 R2 fast approaching, you will want to think about the steps for upgrading the Web Client. At this point in time you do not have to upgrade the Web Client when you upgrade the Rich Client (Desktop Client) however we do always recommend being on the latest and greatest in regards to these releases since new features are added and previous issues are fixed. 

When upgrading the Web Client, you will want to verify whether you are in a single or multi server environment.  If you are running in a single server environment, you’re upgrading the Session Central Service and Session Service on one server.  If you are running a multi-server environment you will want to be sure that you are installing the Session Central Service update on the Session Central Server.  The same goes for the Session Service server.  Also, if you are running multiple Session Service Servers, you will want to be sure that you are upgrading both of them so that they are the same Web Client version.  Please see below for some quick instructions on how to upgrade a single server environment or a multi-server environment.  Please note, there are special instructions if you happen to be running Tenant Services.  You would want to refer to the Install and Administration Guide.

Please check back to this blog in the future for a link to the official upgrade documentation for both Web Client and Tenant Services.

Single machine upgrade

Preparing for the upgrade

Before you perform the upgrade for the Microsoft Dynamics GP web client, you must perform the upgrade for the database and the desktop client components. Use

Microsoft Dynamics GP Utilities to upgrade the system database and the company databases.  Refer to the procedures described in the upgrade documentation for Microsoft

Dynamics GP to complete this process.

You should verify that the desktop client is working properly before you continue with the Microsoft Dynamics GP web client upgrade. Resolve any issues before you continue.

Be sure that all of the users have signed out of the system before you start the web client upgrade process.

Installing the upgrade

To install an upgrade of the Microsoft Dynamics GP web client in the single machine configuration, complete the following procedure.

1. Run the WebClient.exe application found in the \AdProd\WebClient\ folder of the Microsoft Dynamics GP 2013 R2 installation media.
2. When the installation is complete, run the Dynamics GP Web Client

Configuration Wizard. You can access this from the Start menu.

1. At the Welcome screen, click Next.
2. Specify the type of authentication you want to use to connect to the SQL Server where the database for the Web Management Console is located. Click Next to continue.
3. Specify the type of authentication you want to use to connect to the SQL Server where the database for the Session Central Service is located. Click Next to continue.
4. Review the configuration actions that will be performed. Click Next to continue.
5. Click Exit.

Updating the online help
 
If a web client upgrade has updated help content, use the following procedure to install the updated help content.

1. Open the Programs and Features control panel.
2. Select Microsoft Dynamics GP Web Client Help, and then click Change.
3. Click Remove to remove the existing web client help. The process may take a few minutes.
4. Click Finish.
5. Start the installer for the updated help content. The installer has the following name: Microsoft_DynamicsGP12_GPWebClientHelp.msi.
6. At the Welcome screen, click Install. The installation process may take a few minutes.
7. Click Finish.

Client machine update steps 

1. To ensure that the updated Microsoft Dynamics GP web client is working properly, you should perform the following steps on each of the client machines that access the web client.
2. Clear the Internet Explorer browser cache. This helps to ensure that the updated application and help files are being used for the web client.
3. To clear the browser cache, open Internet Explorer. In the Tools menu, choose
4. Internet options. In the Browsing history group, click Delete.
5. In the Delete Browsing History window, be sure to remove the temporary
6. Internet files. Click Delete.
7. After the browser cache has been cleared, click OK.
8. In Internet Explorer, go to the Microsoft Dynamics GP web client site. Sign in to the web client.
9. If you watch closely, you should see a new Silverlight application is downloaded for the Microsoft Dynamics GP web client.
10. Look in the lower-right corner to verify the trust level for the web client. If you see the icon indicating that the web client is running in sandboxed mode, you have an additional step to perform.

The Silverlight application included with the updated web client may have been signed with a security certificate that is not available on the client machine. To get this certificate, you must run the DynamicsGPTrustedApp.msi that is included with the updated web client code.   Otherwise, you would want to provide a link to this document here.

Scale out upgrade

Preparing for the upgrade

The first step to performing the upgrade for a scale out installation is to upgrade for the database and the desktop client components for Microsoft Dynamics GP. Use

Dynamics GP Utilities to upgrade the system database and the company databases.

Refer to the procedures described in the upgrade documentation for Microsoft

Dynamics GP to complete this process.

You should verify that at least one desktop client installation is working properly before you continue with the Microsoft Dynamics GP web client upgrade. Resolve any issues before you continue.

Be sure that all of the users have signed out of the system before you start the web client upgrade process.

If you are using Tenant Services with your Microsoft Dynamics GP web client installation, you must apply the update to Tenant Services before you update the web client components.

Refer to the Tenant Services Installation and Administration Guide for information about updating Tenant Services.

Updating the web site and Session Central Service
 
To install the upgrade for the web site and the Session Central Service, complete the following procedure.

1. Log in to the machine that is running the web site and the Session Central

Service for the Microsoft Dynamics GP web client installation.

1. Run the WebClient.exe application found in the \AdProd\WebClient\ folder of the Microsoft Dynamics GP 2013 R2 installation media. The upgrade actions for the web site and the Session Central Service will be performed. If the Web

Management Console components are installed on this machine, they will be updated as well.

1. When the installation is complete, run the Dynamics GP Web Client

Configuration Wizard. You can access this from the Start menu.

1. At the Welcome screen, click Next.
2. Specify the type of authentication you want to use to connect to the SQL Server where the database for the Web Management Console is located. Click Next to continue.
3. Specify the type of authentication you want to use to connect to the SQL Server where the database for the Session Central Service is located. Click Next to continue.
4. Review the configuration actions that will be performed. Click Next to continue.
5. Click Exit.
   
   

Updating session host machines
 
To install the upgrade for each session host machine in the scale out installation, complete the following procedure.

1. Log in to the session host machine.
2. If you haven’t already done so, perform the update for the Microsoft Dynamics

GP desktop client components. Be sure that the desktop client on the session host machine is working properly before you continue this upgrade procedure.

1. Run the WebClient.exe application found in the \AdProd\WebClient\ folder of the Microsoft Dynamics GP 2013 R2 installation media. The upgrade actions for the Session Service and the Runtime Service will be performed.
2. When the installation is complete, run the Dynamics GP Web Client

Configuration Wizard. You can access this from the Start menu.

1. At the Welcome screen, click Next.
2. Specify the type of authentication you want to use to connect to the SQL Server where the database for the Session Central Service is located. Click Next to continue.
3. Review the configuration actions that will be performed. Click Next to continue.
4. Click Exit.

Updating the online help
 
If a web client upgrade has updated help content, use the following procedure to install the updated help content for the scale out installation. This procedure assumes that the help is installed in the default location, which is the same server that is hosting the web site.

1. Log in to the machine that is running the web site for the Microsoft Dynamics

GP web client installation.

1. Open the Programs and Features control panel.
2. Select Microsoft Dynamics GP Web Client Help, and then click Change.
3. Click Remove to remove the existing web client help. The process may take a few minutes.
4. Click Finish.
5. Start the installer for the updated help content. The installer has the following name: Microsoft_DynamicsGP12_GPWebClientHelp.msi.
6. At the Welcome screen, click Install. The installation process may take a few minutes.
7. Click Finish.

Verifying the services
 
When all of the components of the web client installation have been updated, verify

that the services are working correctly.

• On the machine that is hosting the web site for the web client installation, verify
  that the Session Central Service is running.
• On each session host machine, verify that the Session Service is running.
• In the Session Management snap-in for the Web Management Console, all of
  the session host machines should be listed. Be sure that each machine is set to
  allow new web client sessions.

At this point, you can allow users to sign in to the Microsoft Dynamics GP Web Client

Thank You!

Ross

Increase productivity and collaboration with Office 365

With the release of GP 2013 R2 there are 4 new Excel files that will be deployed with Excel reports in Microsoft Dynamics GP 2013.

Easily create executive dashboards and securely share those using Office 365. Click the image below for a quick demo of how Microsoft Dynamics GP and Office 365 work together to connect people, processes, and systems all from one place.

https://community.dynamics.com/dynamicbusiness/b/theedge/archive/2014/05/28/introducing-microsoft-dynamics-gp-2013-r2.aspx

Hello everyone!

This blog post is going to list out all the Table and Column changes for GP 2013 R2. This is a big release, with a lot of great new features, and subsequently has a lot of back end changes! I've included some links to help with navigating through this information, along with a "Back to Top" link at the end of each section. Take note that the columns listed in the New Columns section includes column changes to pre-existing tables, and new tables. The third section separates out the column changes to pre-existing tables.

If you have further questions about index, data type, and segments information, please review the SDK documentation for a more in-depth look into the changes.

New Tables

All New Columns

New Columns in Existing Tables

Deleted Columns

New Tables:

Back To Top

New Columns: