Error with GP Utilities when upgrading database on workstations

(0) Share

Report

Posted on by Ray-Man

We are upgrading from GP 2010 to GP 2015. There is a working test install on our server. After installing on a work station and running MicrosoftDynamicsGP11-KB2897368-ENU, GP2015 opens and wants to setup or upgrade the application as it normally does on a first run. Immediately it returns the following error message " Error message 35100 doesn't exist" the follow up error message is "Failed upgrading table DB_Upgrade" . Any guidance would be appreciated.

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (1)

KirkLivermont 5,985 on at

Like (0)

Report

Did you already run the database upgrade on the server? I will normally install the GP client on the server and upgrade the database from that client before connecting clients.

Regards,

Kirk

Was this reply helpful? Yes No
Ray-Man 25 on at

Like (0)

Report

Yes . We have a GP2015 client running on the server. It ran GP utilities on the first run with no errors. This only occurred when we installed on workstations.

Was this reply helpful? Yes No
KirkLivermont 5,985 on at

Like (0)

Report

I don't believe a workstation installation should cause any effect on the DB_Upgrade table. Are you sure the client is connecting to the test server (or test instance)?

Was this reply helpful? Yes No
Ray-Man 25 on at

Like (0)

Report

I agree. Especially since everything is great on the client installed on the server. The test instance has a unique name so I am fairly certain it's the same database.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

If you have already upgraded from GP 2010 to GP 2015 on the server, why are you applying a GP 2010 service pack to the client? On the server create a GP 2015 installation package an install on the workstations using that package.

Was this reply helpful? Yes No
Ray-Man 25 on at

Like (0)

Report

Sorry I copied the wrong update it is actually " MicrosoftDynamicsGP14-KB3122625-ENU" that I applied after installation. Sorry for the confusion. I did create an installation package on the server for deployment to the workstations. Still getting the same error on all 3 .

Was this reply helpful? Yes No
Ray-Man 25 on at

Like (0)

Report

Found this on the SQL Server Management Studio Events log " login failed for user 'NT SERVICE\SQLAgent$GP' Reason:Failed to open the explicitly specified database 'GP 2015'[CLIENT: <local machine>" . "Error: 18456 Severity:14 State 38"

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (0)

Report

I would start by creating a domain service account and drop it into the administrator group of the domain. Use this account to start all service related to SQL. Stop and start SQL. Then, as a test, drop the firewall on the server. Then try to fire up the GP 2015 client. If that works then you can turn the firewall back on only this time allowing the port 1433, or whatever port you are using for SQL.

Was this reply helpful? Yes No
Richard Wheeler 75,848 Moderator on at

Like (1)

Report

Also make sure you can ping the server by name if not use its IP address. Then test the ODBC connection that GP Utilities created. It sounds like you have a connectivity issue. Make sure you use the 32 bit ODBC administrator found in the C:\Windows\SysWOW64 folder.

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

Like (1)

Report

In addition to what Richard and Kirk have noted above, you might want to compare the DynUtil.set file on the client and the server to see if there is a difference on the number of modules that the SET file thinks are installed.

I have seen cases where the system runs great on the server, but the DynUtil.set on a workstation is messed.

I also think that if this is not the case, then Richard has you working down the right path and looking at the services and the ODBC connection on the worksation. Make sure that the name of the server you are accessing is named the same on the server as it is on the workstation, we have been seeing issues (tons of them) if these dont match.

Anyway. Just wanted to add my 2-bit to the conversation.

Was this reply helpful? Yes No