DNS error SBS 2008, error 1717 the interface is unknown

after rebooting the SBS 2008 Server
DNS does not start. get error 1717: the interface is unknown.
also noticed Event Viewer does not open either
any suggestions would be great.

Had this problem today with a 2008R2 DC after a power failure overnight.
Could not start windows event log service (access denied) or DNS Server Service (1717: the interface is unknown)
After looking at many suggestions on the Web that suggest either a permissions problems on "C:\Windows\System32\winevt\Logs"
or the Default Domain Controller GPO being corrupt (didn't make sense as our other 7 DCs were all working fine)
Found this suggestion, which solved the problem for us: 
The "C:\Windows\System32\Winevt\Logs" folder had the read only option checked. Unchecked the option and applied to all subfolders and files. Event Viewer and DNS now starting
and working fine.

Similar Messages

  • Accidently removed a mailbox on the SBS 2008 server during the migration from SBS 2003

    I accidently removed a legacy mailbox from the SBS 2008 server while still doing the migration from SBS 2003.  I meant to click on the Move Mailbox like the instructions said but clicked on the Remove option, then clicked the 'X' to close the box since
    I figured that would cancel what I did however it removed the mailbox from the SBS 2008 list.
    Please tell me that I can get it back.  It still shows up in the old SBS Exchange System Manager but now when an email is sent, it sends back a no delivery message.  It's like the account doesn't exist any more.
    Can it be recovered and if so, how?
    thanks,
    Jeff

    Hi Jeff,
    Would you please let us know current situation of this issue? Just check if above suggestions can help you.
    If any update, please feel free to let us know.
    In addition, please also refer to following article and thread, and then check if can help you.
    How
    to use a Recovery Storage Group in SBS 2008
    How
    to recover a deleted user and mailbox on SBS 2008
    Hope this helps.
    Best regards,
    Justin Gu

  • Can two servers running windows sbs 2008 be on the same network

    I have two HP proliant dl360 servers. We are trying to set up one as a file server. Can we install a copy of Windows sbs 2008 on both machines (we have the license) in the same network

    Hi
    Every one is quite right you can not install SBS2008 on both machines. Only 1 server on a network can have SBS on it.
    However all you need for the second file only server is Server 2008 (it doesn't need to be SBS)
    Things to investigate
    1. If you have a license for SBS2008 you may run Server 2008 on other servers with no additional client licenses (if you install server 2008R2 or higher on a second or more servers, you will need both SBS2008 and Server 2008R2 client licenses for each user)
    So client licenses are sorted
    2. If you already have 2 copies of SBS2008 for install, you may find you can downgrade SBS2008 to server 2008 (you will need to double check this, but generally means you can install Server 2008 without having to spend the extra money as you already have
    paid for the SBS2008)
    3. You may find a old retail copy of Server 2008 on ebay you can buy
    Generally the solution to this is, SBS2008 goes on the most powerful server, and is set up as the domain controller, exchange etc.... then on the second server you just install Server 2008 and join it to the domain to be controlled by SBS2008 server, you
    don't need to worry about extra CALS, as long as you stay Server 2008 or under
    You then set up this second server independently with backups, shadowcopies and shared folders
    Group policies for both are configured on the SBS box so you can set up predefined mapping etc
    The difficulty you will have is obtaining the old software
    If you uses SBS2011 you can use Server 2008R2 and before with no additional CALS
    CALS relate to the core OS used, in SBS2008 it is 2008 in SBS 2011 it is 2008R2
    Hope this helps
    Tris

  • SBS 2008 - SBS Console and AD errors after migration to new hardware

    Hi there,
    I'm trying to work out how to fix some of the errors and random behaviour I'm experiencing with the SBS 2008 console and AD related matters since I had to quickly migrate SBS 2008 to new hardware using Windows Server Backup after a failure of the old server.
    In my haste to get our email and ftp services back up and running (which use Smartermail and Filezilla respectively instead of Exchange etc) I overlooked the fact that the new server had 3 NICs installed and not one and so restored SBS 2008 and loaded up new
    drivers for those and other hardware that had changed (such as the graphics card and mobo. I have since removed the two additional NICs by disabling them on the mobo).
    Whilst I got the server up and running again with email and ftp services, even though I currently don't use any AD related stuff directly I have since noted that if I try to say view a list of users that I had previously created via the SBS console, more often
    than not it will show no users, and then randomly it will (but when you do see them you can't edit or delete them. I'm aware that I have probably broken a number of golden rules in doing this 'migration' but having a metaphorical gun to my head meant that
    I rushed things out of desperation. 
    Common errors that I experience generally will say things like 'Current security connect is not associated with an Active Directory domain or forest' if I try to list users, or DC not found for domain "xyz.local' etc. I have been searching the net and
    trying out some things to fix this but I'm like a dog chasing its tail as I'm not so clued up on server related issues as I am with workstation problems, so if anyone could at least point me in the right direction I would be very grateful. If you require any
    info from me (eg diag logs etc) I will be happy to provide them!
    Regards,
    Dave

    Hi Dave,
    Based on current situation, please run SBS BPA and fix all that it can find, then monitor the result. For more details, please refer to the following KB.
    Windows SBS Best Practices Analyzer (BPA)
    Meanwhile, please refer to the following article and repair SBS console.
    Repair the Windows SBS 2008 Console
    By the way, I noticed that you had got some error messages (such as: “DC not found for domain” and so on). Would you please let me know complete error messages? In addition, when you migrate SBS 2008 to the new hardware, had you done any preparation for
    that Source Server? For more details, please refer to the following article.
    Migrate Windows Small Business Server 2008 to New Hardware
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • Removing Exchange 2007 from SBS 2008 (In an Exchange 2010 Coexistance Scenario) - In order to remove 2007 Mailbox Objects from Active Directory and remove the SBS2008 server completely

    I'm trying to remove Exchange 2007 from an SBS 2008 server
    (Server 2008 Standard FE).  My ultimate goal is to completely remove the SBS 2008 Server from the network environment.
    We have an Exchange 2010 Coexistence Scenario and Mailboxes/Public Folders/etc have been moved over to the 2010 mail server, on Server 2008 R2.
    I have moved all Shares, FSMO roles, DHCP, DNS, etc over to their respective servers.  We have two full blown DC's in the environment.
    I'm ready to remove Exchange 2007 from SBS 2008 and DCPROMO the server.  I can NOT seem to find a TechNet article that shows me how
    to proceed in this kind of scenario.  I am trying to use the TechNet article:
    http://technet.microsoft.com/en-us/library/dd728003(v=ws.10).aspx
    This article references Disabling Mailboxes, Removing OAB, Removing Public Folder Databases, then uninstalling Exchange using the Setup Wizard. 
    When I go to Disable Mailboxes I get the following error:
    Microsoft Exchange Error
    Action 'Disable' could not be performed on object 'Username (edited)'.
    Username (edited)
    Failed
    Error:
    Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.
    OK
    I really don't see why I need to Disable Mailboxes, Remove OAB and Public Folder Databases since they have been moved to 2010.  I just want
    to remove Exchange 2007 and DCPROMO this server (actually I just want to remove any lingering Exchange AD Objects referring to the SBS 2008 Server, using the easiest and cleanest method possible).
    Can someone point me in the right direction?
    Thanks!

    Hi,
    Based on your description, it seems that you are in a migration process (migrate SBS 2008 to Windows Server
    2008 R2). Now, you want to remove Exchange Server and demote server. If anything I misunderstand, please don’t hesitate to let me know.
    On current situation, please refer to following articles and check if can help you.
    Transition
    from Small Business Server to Standard Windows Server
    Removing SBS 2008 –
    Step 1: Exchange 2007
    Removing SBS 2008 – Step 2:
    ADCS
    Removing
    SBS 2008 – Step 3: remove from domain / DCPROMO
    Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft
    does not guarantee the accuracy of this information.
    Hope this helps.
    Best regards,
    Justin Gu

  • SBS 2008 Mail Database missing after recovery. What to do?

    SBS 2008 went into the rebooting loop.... I've tried all I can to resolve it and had no luck. The last option was to recover which I did successfully except the mailbox database.
    After restoring the Server I looked at the DB and they were dismounted when I tried to mount them I got an error saying Can't find database Exchange can create a new one....
    I can access the old server in safe mode. Can I just take the db file and move it and mount it on the new recovered server? Or it's not as easy as move the DB and mount it?
    Thanks for the help.
    This topic first appeared in the Spiceworks Community

    Dear user13148231,
    You can check the SCN of the database but i think if the area that you store archivelogs for the standby database is full and the replication was stopped, you have lost the synchronization.
    Compare the SCN of the both databases and see if the standby database is up-to-date or not. If it is not, you have to take an incremental backup up to that SCN from the primary database and apply it to the standby database. The archivelog gap will be closed and the sync will continue to move on.
    Once the database can not have the archivelogs on the system, it can not apply them. However, if you still have the missed archivelogs on the primary database you may register them manually and the gap would be closed again.
    Please see the Oracle data dictionary views to have the necessary information.
    Ogan

  • Unrecognized certificate when Outlook 2010 tries to connect to Exchange 2007 on SBS 2008

    Hi all,
    I believe this is a security issue rather than a connectivity or configuration problem.
    Running Outlook 2010 on Windows 7 trying to connect to Exchange 2007 on SBS 2008, I receive the following error:
    "The name of the security certificate is invalid or does not match the name of the site"
    When I view the certificate I see that it was issued to "zx-server" by "zx". This is NOT my domain CA nor is it a certificate I recognize. I use a self-issued certificate (i.e. issued by the SBS box). I also receive this certificate error when I browse to
    the internal website (companyweb). No other computers on the network are seeing this behaviour.
    I have checked the certificate stores in certmgr and I can't find any such certificate or CA. I have also searched the entire hard drive with no luck. I have run Kaspersky AV, Malwarebytes and MS Security Essentials several times but I can't find any malware.
    I also recently installed Comodo Firewall (the problem began after this).
    I need to find and remove the certificate and prevent it from being presented to me every time I try to connect to the server. All help, advice and suggestions appreciated.
    Aide

    Hi,
    It’s really a common issue.
    This issue occurs if the following conditions are true:
    You replace the default self-signed Exchange Server 2007 or Exchange Server 2010 certificate with a different certificate.
    Note The Setup program in Exchange Server 2007 or in Exchange Server 2010 creates a default self-signed certificate when Exchange Server 2007 or Exchange Server 2010 is installed.
    The common name on the replacement certificate does not match the fully qualified domain name (FQDN) of the URL that is stored in the following objects:
    o   
    The Service Connection Point object for the Autodiscover service
    o   
    The
    InternalUrl attribute of Exchange 2007 Web Service (EWS)
    o   
    The
    InternalUrl attribute of the Offline Address Book Web service
    o   
    The
    InternalUrl attribute of the Exchange unified messaging (UM) Web service
    By default, the URL that is stored in these objects references the NetBIOS name of the server. For example, a URL that resembles the
    following URL is stored:
    https://NetBIOS_name.contoso.com/autodiscover/autodiscover.xml
    This may differ from the host name that is used in the FQDN of the replacement certificate. For example, the replacement certificate
    may have an FQDN that resembles the following FQDN:
    mail.contoso.com
    This issue causes a name mismatch error to occur. Therefore, you receive the security warning message when you try to connect Outlook
    2007 to the mailbox.
    For more detailed information about the procedures to fix the issue, please refer to the following KB article:
    Title: Security warning when you start Outlook 2007 and then connect to a mailbox
    that is hosted on a server that is running Exchange Server 2007 or Exchange Server 2010: "The name of the security certificate is invalid or does not match the name of the site"
    URL:
    http://support.microsoft.com/kb/940726
    Regards,
    James
    James Xiong
    TechNet Community Support

  • SBS 2008 & Forefront Exchange 2010

    Uninstalled the Forefront for Exchange that ships with SBS 2008 and installed the new Forefront 2010 for Exchange.  Everything works great but I have a problem with the SBS Console alert.  In Forefront Exchange 2010, the Forefront engine takes over the anti-SPAM function from Exchange and that is a good thing, but now the inherent SBS 2008 console has an error message under SECURITY for "Spam protection for E-Mail" as CRITICAL.  I know what the problem is but I do not know how to disable the alert.  Now that Excahnge is no longer handling anti-SPAM, the SBS server sees the function inactive and issues an alert sice it is unaware that that role is now filled by the Forefront 2010 anti-spam engine.  Is there a method do disable the SBS Consoel alert on the SECURITY tab?  Everything is working great with Forefront Exchange 2010 on SBS 2008 other than this little alert that is bugging me.
    Thanks to anyone out there that has any insight on this...

    GaryD9, on this thread:
    http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/67eea70a-5ed8-49ae-ba06-6abb2673f38e
    posted a detailed answer which worked for me, as far as the Console alert goes. It doesn't fix the emailed reports. I'll copy it here incase that thread becomes unavailable:
    the CAUSE of the error is that the MS Exchange "content filter" is turned off in favor of the forefront content filter when forefront is installed.  The SBS console is still looking at the Exchange filter status (which is now off) and is generating an
    error.  On my SBS 2011 server, the cause of this is a file named "E12AntiSpam.xml" in the "C:\Program Files\Windows Small Business Server\Data\SHExtensions" directory.  Within that file, there is probably a line such as
    $(Get-TransportAgent "Content Filter Agent").Enabled
    The fix can be as simple as changing the line to:
    $(Get-TransportAgent "FSE Content Filter Agent").Enabled
    (just inserting "FSE " in the front of the agent name)
     It should be noted that you can't edit this file unless you open it from Notepad after right clicking
    on the shortcut for Notepad and selecting "Run as Administrator". Also, you won't see any changes until you close and re-open the Windows SBS Console. 
    I'm a little concerned that removing the FSE.XML file (as proposed on the SBS forum) may stop ALL error
    reporting rather than just changing the source from the regular content filter to the Forefront version. This solution of editing the E12AntiSpam.XML file seems a safer bet.

  • WRT350N and MS SBS 2008

    I am trying to configure my WRT350 to work with SBS 2008.  I used single port forwarding setup in the router manually for ports 25, 80, 443, 987, 1723 to the IP address of my server.  (I have the router assigned to a static IP address).  SBS 2008 tells me it can't open those ports no matter how I try to forward them with router settings.  I even tried Port Range Forwarding and DMZ enabling for the server IP address to no avail.
    Anyone working with SBS 2008 using this router?

    Thanks.  I upgraded to firmware v1.03.7 and reset and reconfigured the router.  Still get the same warning error from SBS 2008 when running the "Set up Internet Address Wizard" - SBS 2008 cannot open ports 25, 80, 443,and 987to the IP address of the server.  In order to receive e-mail and other info over the Internet you must manually open the ports".  The router is configured with a static ip address with DHCP disabled (handled by the server).  I do have Internet access through the router. I have tried single port forwarding and port range forwading under the "application & Gaming" menu on the router to open the ports for email but still no success. 

  • Nss6000 will not join sbs 2008 domain

    I updated the firmware to the latest rev on the device & are their any docs. on the procedure to do this?
    Want to make sure it is not a syntax issue
    Thanks

    It would be exactly like the SBS2003 procedure. You would need to setup the SBS 2008 domain first, the procedure can be easily found on Miscrosoft web site. The release notes said: " No support for SBS 2008" but I found it is working fine with latest firmware V1.14. Here is the link to build the 2008 domain server:
    http://www.windowsreference.com/windows-server-2008/step-by-step-guide-for-windows-server-2008-domain-controller-and-dns-server-setup/
    Hope that 's helped.

  • SQL Server 2014 on SBS 2008

    Hi
    Is it OK to install SQL Server 2014 on SBS 2008 which is the only domain controller on the network and will not be demoted in normal circumstances?
    Thanks
    Regards

    Hi Y a h y a,
    SQL Server Setup will not block installation on a computer that is a domain controller.
    However, for security reasons, we recommend that you do not install SQL Server 2014 on a domain controller. There are some limitations as follows:
    • You cannot run SQL Server services on a domain controller under a local service account.
    • After SQL Server is installed on a computer, you cannot change the computer from a domain member to a domain controller. You must uninstall SQL Server before you change the host computer to a domain controller.
    • After SQL Server is installed on a computer, you cannot change the computer from a domain controller to a domain member. You must uninstall SQL Server before you change the host computer to a domain member.
    • SQL Server failover cluster instances are not supported where cluster nodes are domain controllers.
    • SQL Server Setup cannot create security groups or provision SQL Server service accounts on a read-only domain controller. In this scenario, Setup will fail.
    Reference:
    Hardware and Software Requirements for Installing SQL Server 2014
    Using SQL Server in Windows Small Business Server 2008 Premium Edition
    Thanks,
    Lydia Zhang
    If you have any feedback on our support, please click
    here.
    Lydia Zhang
    TechNet Community Support

  • SBS 2008 Licensing

    I will be migrating from SBS 2008 to Windows 2012 Standard R2 and Exchange 2013 on new equipment. 
    Once I have completed the migration and decommissioned the SBS 2008 server, would the SBS 2008 license cover the installation of Windows Server 2008 on the former SBS server?
    Thanks in advance.
    CC

    It wouldn't matter. The premium edition in 2008 and the premium add-on in 2011 are both tied to the existence of SBS on the domain. If SBS is retired then you cannot use the second windows licenses *or* the SQL licenses included as part of the premium offerings.

  • Migrate SBS 2008 to Server 2012 R2 Std

    Thank you for your reply. The Setup is a 2012 HV with three VM's = DC, Exchange and Terminal Server. The Exchange will be 2010. It was decided to stay with Emails on the Server by the company director, we don't require office 365
    I think the migration of 2008 to 2012 dc should be fine, but it was migrating the exchange 2007 to exchange 2010 that I was not sure about, my notes I have were actually for 2003 sbs's that were going to use office 365 so that's why I was enquiring after the email migration
    thanks

    Hello
    We have a SBS 2008 Server that is going to be migrated to Server 2012 R2. The 2012 has two virtual machines - one for the new Domain and the other is for email exchange. We have instructions for migrating a SBS 2003 Server to 2012 Server that we were told was successful - can I apply these same steps to a SBS 2008 Server? IT involves promotion 2012 to DC, migrating AD (FSMO, scheme master global catalog) and migrate dhcp.
    for the emails, is there a MS guide to migrating SBS 2008 mailboxes to the 2012 R2 email server?
    Thanks
    This topic first appeared in the Spiceworks Community

  • Error 0xE0000235 when trying to download a driver onto Windows SBS 2008 64-bit Standard FE.

    Unfortunately, Error 0xE0000235 occurs when trying to download a driver onto Windows SBS 2008 64-bit Standard FE.
    I am installing the GV 800 GeoVision 32/64Bit 16CH Video Capture Card onto the server.
    Please urgently assist.
    Answer in clear English. Cryptic answers not welcome. Yes...I know you are an intelligent, highly valuable expert on the world's leading edge technology.

    Hi, I'd like to inform you that the error code 0xE0000235 refers to "Error in WOW64". This can be caused by corrupted or incompatible driver of the Video Capture Card. Similar issue may also occur on other driver on other operating system and I don't think
    this can be caused by SBS2008 blocking the driver.
    I suggest you contact with GeoVision Technical Support (http://www.geovision.com.tw/english/4_0.asp) and see if their driver should work on SBS2008 and make sure that you have downloaded
    latest driver from their site:
    http://www.geovision.com.tw/english/5_2.asp
    Please Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
    Hope this helps!
    Sean Zhu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please contact
    [email protected]
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Global query block is causing a DNS server to fail a query with error code Name Error exists in the DNS database for WPAD

    Global query block is causing a DNS server to fail a query with error code Name Error exists in the DNS database for WPAD on a Windows 2008 server.

    The global query block list is a feature that prevents attacks on your network by blocking DNS queries for specific host names.  This feature has caused the DNS server to fail a query with error code NAME ERROR for wpad.contoso.com. even though data
    for this DNS name exisits in the DNS database.  Other queries in all locally authoritative zones for other names that begin with labels in the block list will also fail, but no event will be logged when further queries are blocked until the DNS server
    service on this computer is restarted.

Maybe you are looking for