We have a similar problem that has just cropped up since Friday, Aug 22nd.
We get an invalid authentication error on a remote SQL server database (but
can connect to a local one with no problems). It appears to be related to a
recent Windows security update (installed one last week), as an IT buddy of
mine wasn't able to access his server or our remote one either, but WAS able
to do so from another server which didn't have the security patch installed
yet. Anyone else having this problem? Anyone know how to fix it?
Thanks,
Gene
<joe (AT) noemail (DOT) com> wrote
Quote:
For the past few days I have been getting errors in EM. When I try to
edit a table I get an ODBC communications link error. I get this from
a workstation and the server console. Also sometimes when I try to
browse tables I get "connection broken" errors. Am running SQL2K
Enterprise Ed. with SP2. No changes have been made recently other
than a reboot after adding new drive space for any expanding database.
SP3 was not considered an option because the forced MDAC upgrade
conflicts with a legacy ODBC driver. Any suggestions where to start
with this one would be appreciated. |