Rolling back update on Ms windows server 2008 r2

Thanks for reviewing this.

My server auto updated asp. Net framework and a bunch of other stuff KB4041681.

As. Net 2.0.50727.0 and myself 6.1.3601.17514 throws out errors consistent with client query activity..

Error [HY000] [MySQL] [ODBC 5.1 Driver] [mysqld-5.5.12] Deadlock found when trying to get lock; try restarting transaction

The windows apication error log references the application server and there are no other direct error references, though there are a few windows system errors in the log but it seems best to start with the obvious one.

As a direct or indirect result a legacy app using but coded over 5 years ago is running up errors in cost report totals other functions seem normal.

The timing of the error is consistence with the windows update.

Any advice or pointers greatly appreciated.. Specifically I'm wondering if it's possible to simply roll back that update, though there had been 3 minor ones since it doesn't necessary guarantee the libraries and other files will be restored to the same state prior to the error, so not sure if other problems might occur unless the specific files updated causing the error can be identified.

Once again thanks for reading..
Adam BellAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Big MontyWeb Ninja at largeCommented:
here's a really good detailed tutorial on how to roll back windows updates, as it outlines how to go into Add/Remove Programs and get rid of it there:

and it was unclear in your question if you wanted to roll back WINDOWS updates or .NET FRAMEWORK updates. If it's the latter, have a look here:

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David FavorLinux/LXD/WordPress/Hosting SavantCommented:
Before you do a rollback, first trying manually stopping all processes accessing database + then stop all related database instances (if your running multiple masters or slaves).

Then manually startup one database instance at a time. After all instances are running, then startup one database application at a time.

Sometimes a manual stop/restart will fix update problems. Not always + worth a shot.

Sometimes the auto-update process, which database applications are running can end up in a complex mess.

I run 100s of LXD containers each with MariaDB (fast + stable MySQL) running.

My only database user is Apache + PHP + WordPress, so when I have to update MariaDB, I usually take down Apache first to end all database transaction.

The do the MariaDB update + run mysqltuner to ensure all's well + then restart Apache.

Likely overkill for WordPress sites. For custom database applications though, I'd absolutely shutdown all database applications before any database code upgrades.
David FavorLinux/LXD/WordPress/Hosting SavantCommented:
One other random thing to try also, before reverting...

After your restart MySQL + before you restart your database applications, try manually running mysql_upgrade while tailing... camping on your system logs (where ever Windows spews MySQL log data).

If all's well with your upgrade (from the MySQL standpoint), you should see no output.

If you get errors or if you can repeatedly run mysql_upgrade + get continual messages about the same tables being updated in the same ways, then search for answers about how to fix these individual problems first.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Adam BellAuthor Commented:
Thanks to all for this relevant and very helpful information, the combination of which addresses the foreseeable issues in this circumstance I will feedback on how it goes as I think this is a useful reference for dealing with legacy applications in the ever changing Windows environment.
Tomas Helgi JohannssonCommented:

You could also investigate what is causing the deadlock.
If you set
innodb-print-all-deadlocks = TRUE

Open in new window

in my.cnf and restart the server you will see in the error.log what transaction is causing the deadlock and from there make necessary adjustments to either the code or database/tables involved.

     Tomas Helgi
Adam BellAuthor Commented:
Many thanks to all...the result was a successful rollback of both .net and Windows updates, elimination of the underlying ODBC error for transaction deadlocks, and ID of the precise nature of the deadlocks.  All in all a definitive solutions.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.