Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Martin and Associates

Error During GP 2013 Upgrade from GP 2010 or GP 10 about the system database not being found

Error During GP 2013 Upgrade from GP 2010 or GP 10 about the system database not being found

I recently ran into this issue when trying to start an upgrade from GP 2010 to GP 2013.  Here is the scenario:

  • A test server had been created, and copies of the live gp databases restored
  • A fresh install of GP 2010 was on the test server, and the companies could be accessed through the GP client.
  • A new install of GP 2013 was completed, with the latest service pack.  Rolled with the default to create a new data source, and to keep the system database name as DYNAMICS
  • Windows Server 2008 R2 and SQL 2008 R2

When running GP 2013 Utilities, it asked to create a new system database, which I thought was weird since a DYNAMICS database was already present on the server, and I specified during the install to use that name.  I clicked to create a Basic install, and then when it tried that, up popped this error message:

“A system database name was not supplied.  Run a repair of the Microsoft Dynamics GP installation.”

I could only hit OK and then Utilities closed.  Using my freshly gained knowledge at Convergence 2013, there is a new line in the Dex.ini file that keeps track of the system database name.  That line is called “Pathname”, and it should look like this:

Pathname=DYNAMICS/dbo/

Where DYNAMICS is the name of the system database.  However, it seems that after an initial install, that line reads Pathname=/dbo/ with no system database name.

After updating the file to read correctly (Pathname=DYNAMICS/dbo/) I was able to run GP 2013 Utilities and perform the update.

What fun!

Other Blog Posts

Intacct and Data Warehousing

If the business world were a social network, data would for sure be a trending topic, hashtag and all.  Due to the substantial role that data plays in corporate decision-making,

Non-profit Budgeting with Microsoft Dynamics GP

Budgeting is such an important process, regardless of whether you’re planning for your household or for an entire organization.  In fact, if you’re a not-for-profit (NFP) organization, budgeting could be

Let’s Talk about Management Reporter

Right at the beginning of this year, there seemed to be a lot of buzz around Management Reporter (MR) – both on the web and in conversation, in the Microsoft

WordPress Appliance - Powered by TurnKey Linux