SQL Native clients stopped connecting to MSS 2008 R2 database from all Windows 7 64-bit clients.
Client/server app uses a UDL file on the clients for connection info. We changed to Ole DB Provider (using same connection info) and they work fine so that's the workaround (and perhaps should be the fix) but my CIO wants to identify the cause.
App has been running for years with this config. No changes to server, app, or config of which we're aware. No apparent changes except Windows updates were installed the night before.
Checked Windows updates for Windows server 2008 (64bit). Don't see anything related. Checked programs on the server and appears an update to Office 2003 Web Components was applied the night before (believe it's originally installed with MSS 2008 and is for Project Web). I don't see any others that could be related but we also have fixes pushed via other means "Bigfix". Or BES, for example as well as GFI Languatrd). Checked DNS, firewalls., etc even though it is connecting via ole db and thereby probably not related to these things. Confirmed via MSS Config Manager that ports are enabled. Checked Native files on server and they are an older date (not recently update).
Error is generic - can't connect to db. Since the ole db driver works, and the problem is with all clients, I assume the issue is specific to the Native on the server or an update that impacted the Native client specifically on all workstations.
Is there a way to see all updates in one place to ensure we haven't missed any MSS updates?
They are authenting to the server via NTLM (we only support NTLM 2 but we checked and see the NTLM connections) using Wndows authentication (db is integrated/mixed). MSS service account is Local System and has not changed (we know we need to change this to an account with lower privileges but want to resolve this first).
A friend suggested checking the SQL Native on the server. I think he was referring to an update possibly having been applied. But he wasn't specific. Can anyone explain how I do this (assume there is some way besides checking Windows updates)?
Any ideas what else we can try?