April 2, 2013 at 9:37 am
Hello everyone,
I'm wondering how everyone else is dealing with this issue or if our servers are just configured honkey...
We have a SQL 2008 R2 server running on Windows Server 2008 R2. Everything was hunky dorey up till this past weekend when the Network Admin installed the latest windows patches and updates.
Once he did this, my database mail stopped working and my Maintenance Plans stopped working (they were running under the SQL Agent start up account).
The DB Mail gave the following error:
Object Instance Not Set to an Instance of an Object.
The Maintenance Plans said:
Failed to acquire connection "Local Server Connection". Connection may not be configured correctly or you may not have the right permissions on this connection.
So, the fix for this was reverting back to deprecated .NET versions. When he did the updates, he got rid of .NET 1.0, 1.1 and 2.0 and upgraded to 3.5 and 4.0 ... this somehow caused the problems in my DB.
Once he put the old versions of .NET back, everything worked again... however, since the old versions of .NET are not supported anymore... they really want us to stop using them.
My question is... how does this relate to my database mail and my domain account that starts up SQL Agent? I don't understand why a .NET version caused these problems and I would assume that this would cause problems on other people's servers?
Is this a SQL Server problem or a Windows problem? And what is the remedy? Anybody know?
Thanks!
April 2, 2013 at 10:11 am
This may help: http://msdn.microsoft.com/en-us/library/bb822049.aspx
April 2, 2013 at 10:37 am
Hmmm no not really. 🙁 Unless I just don't understand what I'm reading. I don't understand how the .NET version impacts SQL Server and why upgrading to 3.5 and 4.0 broke those specific DB components... I can't figure out if we need to change something in the OS or if its DB related.
April 2, 2013 at 10:49 am
This is the key part when I read the article I pointed you to:
In general, you should not uninstall any versions of the .NET Framework that are installed on your computer, because an application you use may depend on a specific version and may break if that version is removed. You can load multiple versions of the .NET Framework on a single computer at the same time. This means that you can install the .NET Framework without having uninstall previous versions. For more information, see Getting Started with the .NET Framework.
April 2, 2013 at 10:58 am
Right, I agree and thank you for the reference... but I work for the Gov't and they are being mandated to remove depricated versions of software from machines. So, I'm trying to figure out how others out in the real world are dealing with this and if SQL Server itself requires a specific version of .NET or if this is a Windows issue. If I can justify that SQL Server 2008 "REQUIRES" .NET 1.0 (or 1.1 or 2.0 - I don't know which) then perhaps I can lobby for them to leave it...
But I need to understand first why SQL Server choked when we removed the old versions of .NET
Cause according to this article:
http://msdn.microsoft.com/en-us/library/ms143506(v=sql.100).aspx
1The following .NET Framework versions are required:
•
SQL Server 2008 on Windows Server 2003 (64-bit) IA64 — .NET Framework 2.0 SP2
•
SQL Server Express — .NET Framework 2.0 SP2
•
All other editions of SQL Server 2008 — .NET Framework 3.5 SP1
It says that SQL requires 3.5 .... so, I'm perplexed as to why removing 1.0, 1.1 and 2.0 broke DB Mail and the use of the domain account in my maintenance jobs.
April 2, 2013 at 11:14 am
Can't find anything, yet, directly from Microsoft but I did find this:
.NET Framework 4.0 is separate and independent from .NET Framework 2.0/3.0/3.5 (all one framework. 2.0 is the base, full, framework. 3.0 and 3.5 are extensions to 2.0.).
April 2, 2013 at 11:48 am
Hmmmm, that is indeed interesting. The part about them being extensions to 2.0 ... perhaps that is my culprit.
April 2, 2013 at 12:02 pm
From the 2008 R2 Requirements:
Note
Installing .NET Framework 2.0 SP2: .NET Framework 2.0 SP2 is not available as a separate download. You will need to install .NET Framework 3.5 SP1 which includes .NET Framework 2.0 SP2.
Even though it is not stated clearly that 2.0 SP2 is required - it is assumed because it is included in .NET 3.5.
I would not say any version of .NET is deprecated...rather, each version has a defined life cycle where mainstream support ends, then goes into extended support, etc...
Even though mainstream support for .NET 2.0 is passed - it is still under extended support and will still be supported as long as .NET 3.0/3.5 have dependencies on that version. You cannot install .NET 3.5 without also installing .NET 2.0 - so removing it after the fact will just break it.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
April 2, 2013 at 12:33 pm
Ah thank you! I think that's the piece I need...that may very well be why it broke. The Network guy removed 2.0 as well.
And I shouldn't have used "deprecated" sorry, they are trying to remove the software because they are saying that 1.0, 1.1 and 2.0 have vulnerabilities in them. I am not sure what these "vulnerabilities" are...but that is the reasoning.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply