Roxanne25
asked on
DB Mail and Maintenance Plans Stopped Working
Ack, please help! We have a SQL Server 2008 R2 server running on Windows Server 2008 R2
and it was running 100% wonderful up till this weekend when the Network Administrator installed windows service updates...
Now, my DB Mail doesn't work and my Maintenance Plan jobs are failing. :(
The DB Mail gives the following error:
Object Instance Not Set to an Instance of an Object.
The Maintenance Plans say:
Failed to acquire connection "Local Server Connection". Connection may not be configured correctly or you may not have the right permissions on this connection.
The SQL Agent starts up with a DOMAIN account that has Admin rights on the server.
I have tried deleting the Mail account and profiles and recreating them ...that did not fix the DB mail problem... I'm at a loss...
Does anybody know what windows updates would cause this problem? The network admin thinks it could be "a legacy .NET issue". But he's just guessing... Thanks!
and it was running 100% wonderful up till this weekend when the Network Administrator installed windows service updates...
Now, my DB Mail doesn't work and my Maintenance Plan jobs are failing. :(
The DB Mail gives the following error:
Object Instance Not Set to an Instance of an Object.
The Maintenance Plans say:
Failed to acquire connection "Local Server Connection". Connection may not be configured correctly or you may not have the right permissions on this connection.
The SQL Agent starts up with a DOMAIN account that has Admin rights on the server.
I have tried deleting the Mail account and profiles and recreating them ...that did not fix the DB mail problem... I'm at a loss...
Does anybody know what windows updates would cause this problem? The network admin thinks it could be "a legacy .NET issue". But he's just guessing... Thanks!
Peter Chan
Please check the relevant services of the DB instances have been started in the server.
ASKER
Yes, the services were started.
The issue was identified but we still need to figure out to fix it... the Network Admin restored .NET 1.0, 1.1 and 2.0 and the problem fixed itself.
However, .NET 3.5 and 4.0 are the only supported versions right now... so, I'm wondering why the change in .NET broke the SQL functions?
Did anybody else run into this problem on their servers? And if so.... how do we resolve it? Is this a SQL Server problem or a Windows problem?
The issue was identified but we still need to figure out to fix it... the Network Admin restored .NET 1.0, 1.1 and 2.0 and the problem fixed itself.
However, .NET 3.5 and 4.0 are the only supported versions right now... so, I'm wondering why the change in .NET broke the SQL functions?
Did anybody else run into this problem on their servers? And if so.... how do we resolve it? Is this a SQL Server problem or a Windows problem?
Please check it running with network service credentials.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to resolve the issue on my own.