Windows 7 - Exception conn to old Repository on ntwk svr

Monitor, diagnose and receive alerts to problems across your SQL Servers.

Moderators: eddie davis, david connell, dlkj, Colin Millerchip, priyasinha, Emma A

Windows 7 - Exception conn to old Repository on ntwk svr

Postby PDinCA » Sat Dec 19, 2009 1:52 am

Version 1.3.0.58

Machine is a fresh install of Windows 7 Ultimate over what was XP-Pro, using my original domain account et al, having used "Windows Easy Transfer" to port settings and all from XP to W7 via a USB Hard Drive.

SSMS can connect to the remore server. Remote Desktop is fine, too.

When I attempt to connect to the existing repository, I get a System.IO.IOException: The write operation failed, see inner exception. -->
System.ComponentModel.Win32Exception: The message or signature supplied for verification has been altered at System.Net.NTAuthentication.DecryptNtlm(Byte[] payload, Int32 offset, Int32 count, Int32 newOffset, UInt32 expectedSeqNumber)
followed by exception for System.Net.NTAuthentication.Decrypt
followed by exception for System.Net.Security.NegoState.DecryptData(... which is truncated in the "Alert Repository Setup" dialog.

HELP! The rebuilt PC is the Production Monitoring Machine...

If I remote to the repository machine, I can run SQL Response just fine...
PDinCA
 
Posts: 512
Joined: Mon Jul 25, 2005 11:42 pm
Location: Costa Mesa, CA, USA

Postby dlkj » Sun Dec 20, 2009 2:34 pm

We've had a similar issue here at Red Gate (and from a bit of searching around on the internet, SQL Response isn't the only software that's been hit with this)

Microsoft have issued a critical update to Windows Authentication via windows update which breaks comparability.

If the AR is hosted on a server that hasn't had the latest security updates applied, Windows 7 clients will not be able to connect it. This only affects only XP or server 2003 AFAIK.

We've found that applying the latest security updates to the server fixed the issue (you may need to reboot).

Let us know if this fixes the issue, or if we need to investigate further.

Cheers,
--
Daniel
dlkj
 
Posts: 151
Joined: Tue Aug 14, 2007 5:10 pm
Location: Red Gate Software, Cambridge

Postby PDinCA » Mon Dec 21, 2009 8:33 pm

Thanks, that cleared it up - only 33 patches to catch up on :lol:
PDinCA
 
Posts: 512
Joined: Mon Jul 25, 2005 11:42 pm
Location: Costa Mesa, CA, USA

Postby dlkj » Mon Dec 21, 2009 11:33 pm

Good to hear it.

Got to keep those servers patched :oops:
--
Daniel
dlkj
 
Posts: 151
Joined: Tue Aug 14, 2007 5:10 pm
Location: Red Gate Software, Cambridge

Postby aultmike » Mon Jan 25, 2010 2:36 pm

Hey Guys! Do we know the KB number of the patch that this needs?
aultmike
 
Posts: 26
Joined: Fri Jan 08, 2010 3:49 pm
Location: Canton, OH

Which patch?

Postby jasonmowbray » Thu Feb 03, 2011 11:05 am

Hi all,

I found further information on this problem here:
[url]http://social.msdn.microsoft.com/Forums/en/vststest/thread/37861b71-1613-436d-93dc-8e7a46d6f4d4[/url]

which suggests removing KB968389 and editing the registry followed by reboot.

Was there any conclusion on which patch to apply to fix this? I'd much rather move forward than uninstall an existing patch which may well break something else in future.

Regards,

Jason
jasonmowbray
 
Posts: 2
Joined: Fri Jan 21, 2011 3:45 pm

Postby dlkj » Thu Feb 03, 2011 11:29 am

Hi,

I think the problem here is when some machines have http://support.microsoft.com/kb/969083 installed and some don't. If you are seeing this issue, we'd recommend ensuring the hotfix is deployed on all machine you are using with SQL Response.

Cheers,
--
Daniel
dlkj
 
Posts: 151
Joined: Tue Aug 14, 2007 5:10 pm
Location: Red Gate Software, Cambridge


Return to SQL Response 1

Who is online

Users browsing this forum: No registered users and 0 guests