"An available update may be requried for your computer...." Will not log on GP

(0) Share

Report

Posted on by Community Member

Good Afternoon!

One of our file servers crashed on us and we needed to migrate the data to a new server. After completing the data to the new server we are unable to log into Microsoft Dynamics GP 2010 and receiving the following error:

"An available update may be required for your computer, but the update process couldn't verify information. Contact your system administrator for additional information."

I am guessing there is a setting somewhere that points to the workstation to the server, but I do not know where that is or how to edit it. I have googled this same issue and most people say to delete SYUPDATE, but i am unable to locate that table as well.

Can someone please help me? We are dead in the water with the program.

Thank you!

Jason

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

KirkLivermont 5,985 on at

Like (0)

Report
Copy link

Link copied!

Hi David,

Are you using one of the previously functional GP Clients? If so did you reconfigure the ODBC connection for the new server and are you using the sa account to login?

Did you also verify the file paths in both the Dynamics.set and Dynamics.ini files?

Regards,

Kirk

Was this reply helpful? Yes No
Mick Egan 3,561 on at

Like (0)

Report
Copy link

Link copied!

The Table is located in the DYNAMICS Database, you might find the path no longer exists due to the Server change. Don't Drop the table, only clear the information.

Was this reply helpful? Yes No
Suggested answer

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

Like (2)

Report
Copy link

Link copied!

Hi Jason,This post is almost 3 days old, so I hope you could get out of your problem quickly..

However, 2 things you may want to consider the next time this happens :

1. Use a DNS alias to quickly re-route the request from your old server to the new one.. this way no changes are required on the GP client side or terminal servers, not even a password reset.

2. make sure you have the exact same release numbers (major & minor) for your new GP server, otherwise the clients may be out of sync and will not be able to launch due to a version difference.

Don't touch the SYUPDATE table unless specifically told to remove some entries...which would have to be adressed case by case.

Was this reply helpful? Yes No
Suggested answer

Bill Campbell 12 on at

Like (0)

Report
Copy link

Link copied!

Beat, while I tried everything I could think of to get past this exact same problem - invested 4 hours of my time - after reading this post I did everything else I could think of and nothing changed.

So, as a last resort, I made a backup of the SYUPDATE table, and then removed the only line in the Table and the Update worked immediately on all companies that only 2 minutes before it failed on each time.

While I am comfortable with the suggestion "Not to touch" I think maybe at this point, recommending a backup of that Table and then an edit of the content may be a # 3 option on your list.

It worked for me, when all else failed to make a difference.

Was this reply helpful? Yes No
Suggested answer

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

Like (1)

Report
Copy link

Link copied!

HI Bill,

Sorry, my confusion.. I was confusing SYUPDATE with some of the DUxxxxx tables that contains the module version entries for all the GP modules..

SYUPDATE is the table for the "Client Update" function in GP's Administration and this is populated by your own data.. I had sometimes to go back into this table from SQL because when I was testing the GP Web client, it would not login into GP claiming that there was a new software update to apply and would stop there (as this cannot be performed thru the Web Client)..

It took me some time to figure from where the message came, as none of the GP Full clients had any issues :-).. then I realized that one entry from the last service pack was still 'enabled', causing the error message on the Web Client side... Somehow the WC cannot check the current GP client version against the system version (at least it could not at the time I tested GP 2015R2).

Make sure none of the entries in SYUPDATE has the value 1 assigned in field POST (POST in the old PC days stands for Power-On-Self-Test :-) ... )

Was this reply helpful? Yes No
Suggested answer

Bill Campbell 12 on at

Like (1)

Report
Copy link

Link copied!

Beat, thanks for the clarification on this.

As to the DU Tables, I am fully in support of that comment - they are a problem but you should be getting guidance to making changes to them.

I am still not sure how the SYUPDATE got populated at this client site - we were doing a migration from GP2013 to GP2015 and moving to SQL 2012 R2. All was well until I tried to run GP 2015 on the first workstation and encountered this message.

By removing the 'only line in the SYUPDATE' I was able to complete the installation and update on all remaining workstations without issue.

Was this reply helpful? Yes No
Suggested answer

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

Like (0)

Report
Copy link

Link copied!

Yup..

As for the SYUPDATE, I'm not aware of any auto-magical entries happening there :-) The entries are solely populated thru the Client Updates form : Administration >> Setup >> System >> Client Updates

While it's nice to keep track of old entries, the danger is that the file path is pointing to non-existing locations anymore as time goes by and you do clean-up your server's distribution folders. The bad part is that this table has no field with a TimeStamp so you don't know how old the records inside of it are.. you can only guess by the SP or KB file that it refers to..

Best recommendation to avoid issues is to use it only as long as you need to deploy a new update to the clients and than get rid of it.

Was this reply helpful? Yes No