Finance | Project Operations, Human Resources, ...

Install of database TWO failed! Microsoft Dynamics GP Utilities will now shut down.

(0) Share

Report

Posted on by Sureshn07

702

Dear All,

I am getting the below error while running the GP Utilities for TWO company creation.

GP Version is GP 2018, SQL Server Version is SQL Server 2016 SP2 Standard Edition

"Install of database TWO failed! Microsoft Dynamics GP Utilities will now shut down".

Please help, what could be wrong here.

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (9)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (1)

Report

You can delete the TWO database using SSMS and then run the ClearCompany script. Once you have done this try to create the TWO company again.

Was this reply helpful? Yes No
Suggested answer

Justin Sutton on at

Like (0)

Report

Richard's idea is great in that starting over isn't a bad idea.

Outside of this, you can run a SQL Trace or a DEXSQL.log to see what error is occurring on the backend.

Was this reply helpful? Yes No
Bill Campbell 12 on at

Like (0)

Report

Question - is this a new install of GP 2018 on this SQL Server? or are you doing an update from a prior version?

From this error message I would be guessing that the TWO database already exists or did exist in this installation of DYNAMICS - so somewhere in the Dynamics database there is a reference to the TWO database. Once encountered, it is tough to get rid of, however, Richard has provided a great way to deal with it.

Good luck, and post back to the community on what caused and what solution solved your problem.

Was this reply helpful? Yes No
Sureshn07 702 on at

Like (0)

Report

Hai All,

Thanks for your replies, I tried all the above mentioned, nothing resolved the issue. This is a fresh installation of GP 2018 18.2.1013 on SQL Server 2016 Standard Edition 64 bit. While utility runs for creating TWO database (sample company), this issues pops up. But no idea why this is happening. In the SQL Profiler it says "Login failed for user 'DYNSA'. Reason: Password did not match that for the login provided" repeatedly , but not showing as error, just Profiler entries.

Was this reply helpful? Yes No
Justin Sutton on at

Like (0)

Report

Hello Suresh,

That is an odd error to get out of nowhere.

What account are you running GP Utilities as?

Are you using DYNSA for this?

Was this reply helpful? Yes No
Sureshn07 702 on at

Like (0)

Report

Hi Justin,

I am using "sa" credential only.

Was this reply helpful? Yes No
Suggested answer

Beat Bucher GP Gee... 28,058 Moderator on at

Like (0)

Report

It might look like you already had a previous SQL users account called DYNSA on that instance.. I'd simply start from scratch by deleting that DYNSA user from the SQL security and make sure no other GP related Databases are present on that SQL instance.

Run GP utilities again and try installing a new GP instance and a new demo 'Fabrikam' company (TWO).

That should work.

Was this reply helpful? Yes No
Suggested answer

Bill Campbell 12 on at

Like (0)

Report

When you connect to the SQL Server via SQL Studio Manager - what login do you use? if SA, then under Security, what other logins do you see?

If this is a fresh installation, and you are at the point on creating the TWO database for the first time, the DYNSA and SA users should be all that you have. If you have restored an other DYNAMICS database onto the installation and then tried to create the TWO database then the user DYNSA may already exist.

In this case, can you or have you created your operational company database yet?

If not, I would start from blank. Delete the databases, uninstall SQL and make sure all the files and folders are removed. Then start fresh and go simple - get through the install and create of the TWO database without stopping.

Keep posting and we will keep on replying.

Was this reply helpful? Yes No
Darryl Turner 22 on at

Like (0)

Report

I am having this issue on an Azure VM. It previously had an old version of Dynamics GP (GP 2015) and SQL. I was getting this error so I removed Dynamics GP and SQL Server and SSMS.

I installed SQL Server Standard 2022 and Dynamics GP 18.6

It fails installing TWO. I tried to reinstall so it defaults to TWO01 (which has never existed on this server before) and I still get the error.

There are no SQL users other that sa, DYNSA, LessonUser1 & LessonUser2 (all from this new install, never used before). My windows user was added as an admin in SQL Server.

I have no idea why this would be happening.

Anyone have ideas?

Was this reply helpful? Yes No