SBS 2008 Error messages

I have looked high and low for resolutions for these error messages, but no luck
1) Event ID 2003-The configuration information of the performance library "C:\Windows\system32\sqlctr90.dll" for the "MSSQL$SBSMONITORING" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
2)  Event ID 16025- No DNS servers could be retrieved from network adapter ef17df30-b2e2-4078-a413-a8a720e7df0d. Verify that the computer is connected to a network and that the Get-NetworkConnectionInfo cmdlet returns results
3) Event ID 205- No DNS servers could be retrieved from network adapter 00000000-0000-0000-0000-000000000000. Check if the computer is connected to a network and Get-NetworkConnectionInfo returns any results.

In regards to the DNS errors, I have ran the fix my network wizard the first time it happened, and it fixed it, now it has happened again. When I ran the wizard, it did not find anything. Should I change the NIC card?
xzay1967Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PlusITCommented:
did you disable ipv6?
0
xzay1967Author Commented:
@PlusIT: Are you asking this in reference to the DNS errors? But to answer your question; no I have not. I did not know I was supposed to because I had not seen any literature that said I was supposed to. Per your advice, I will do that when I get back to the office today. Thanks for your input.
0
PlusITCommented:
no don't please... this things actually can happen when you disable ipv6, if never said to disable it :)

First thing to check then is bindings in DNS.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Learn SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

xzay1967Author Commented:
The issue resolved itself, but I am awarding the points because he is the only one that responded.
0
CCanuckCommented:
I have this exact same error message in my logs and I have not touched IPV6 at all.

If I run Get-NetworkConnectionInfo this is what I get

Name        : Intel(R) Gigabit ET Dual Port Server Adapter
DnsServers  : {10.0.33.6}
IPAddresses : {10.0.33.6, fe80::bea7:d517:b38a:5f03, fe80::745f:542f:5f7:c964}
AdapterGuid : 9714fb41-f514-4602-9285-408c95fb1582
MacAddress  : 00:1B:21:4A:B0:98

10.0.33.6 is my SBS 2008 and it is my dns and dns queries are working just fine. I have 6 NICs in my system and ALL except one are enabled. All other NICs are disabled and I am 100% certain of that.

So what is my problem? Well for one, Exchange is not reliable. After a few days I have to re-start it. Also when I enabled RRAS the other day, my server lost its static IP address in IPV4 so I had to go back in and re-enter my static info because DHCP stopped working and Exchange stopped sending mail to the outside world (it could receive though). When I ran the Exchange BPA it said the following:

"IPv6 Protocol Not Supported
Exchange Server is not capable of supporting Internet Protocol Version 6"

So I immediately went to the TCP/IP properties of my NIC and discovered that both IPV6 and IPV4 were on DHCP!!!??? It was set to static as I configured it initially. I think the RRAS service somehow did something. So all I did was reset IPV4 to static and I did not touch IPV6 (should I???). Once I did this, mail started to flow out again and all was good.

But my question is for anyone, what is this error message and what does it really mean and how do I make it go away. I have a strange feeling my SBS is somehow corrupted or a setting is off and it does not know how to report this correctly.

Let me know if anyone has any ideas about this.
0
CCanuckCommented:
After so much searching to get SBS 2008 to just behave properly I've decided to change two settings manually in the Exchange Management Console. Since SBS 2008 keeps forgetting that I have a static IP address and sometimes thinks it cannot find a DNS server I decided to tell it what the servers are.

Here's what I did. Open up Exchange Management Console (not the shell). Go to "Server Configuration". In the right hand pane, right click on your server and select properties. Go to the internal DNS Lookup and enter your server's static IP address in there. Click Apply. Next go to the External DNS Lookups tab and there, enter the DNS servers of your ISP. Click Apply.

I don't like doing this because if things change we usually forget these settings but I don't mind here because this is not an org with 100 servers. It's one server for SBS and a second one for SQL (I have premium). I know for a fact that I will never change the IP address of my DNS server and if I switch ISPs, well, I'll just have to remember this simple fact and I'm sure I will get an error like cannot contact DNS server xxx.xxx.xxx.xxx which will immediately point me in the right direction.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.