• 22Oct

    Error 25007. Error occurred initializing fusion. Setup could not load fusion with LoadLibraryShim().

    If you received this error I was able to resolve this issue by doing the following recommendation.

    Back up all relevant .NET files and removing .NET.  Then run the Windows update and Install the Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update.

    I have provided a link to Microsoft’s website find the correct version for your operating system and install it.

    It is important you install it with the Family Update because this will install the previous versions of .NET to your system correctly.

    – Harry Caskey

    Tags: , , , , , , ,

  • 22Sep

    If you are a hosting environment that is in more than one geographic location you will need to know DNS fail-over. This is a built in feature within DNS. Let’s say you are going to host a website, well you would configure your registrars DNS so that your A-Record’s (i.e. “www”, “@(no address)”) point to your hosting IP address, then from the host IP address you would be redirected to the appropriate header you specified for your domain (i.e. www.yourdomain.com). Now let’s say your company has gone global and you wanted redundancy for your site so that if one node failed your site wouldn’t be down because it would auto redirect to another IP Address. To do this all you would need to do it configure the same record with the different IP Address.

    – Harry Caskey

    Tags: , , , , , ,

  • 21Apr

    It is common practice to keep your server up to date. I came across this error while updating my Exchange Server 2007 to the next service pack. I found many different methods to fix this problem on the internet but none of them worked.

    Below was the error message I received when trying to visit the website.

    Outlook Web Access did not initialize. An event has been logged so that the system administrator can resolve the issue. Please contact technical support for your organization.
    Outlook Web Access was unable to access the Active Directory configuration settings for virtual directory “OWA” under Web site “owa”.

    Url: https://[OWA URL]:443/OWA/auth/error.aspx?replaceCurrent=1&url=https%3a%2f%2f[OWA URL]%2fOWA%2f
    User host address: [Client IP Address]

    Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
    Exception message: Outlook Web Access was unable to access the Active Directory configuration settings for virtual directory “OWA” under Web site “owa”.

    Call stack
    Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart(Object sender, EventArgs e)

    Inner Exception
    Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
    Exception message: Outlook Web Access was unable to access the Active Directory configuration settings for virtual directory “OWA” under Web site “owa”.

    Call stack
    Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor(ADSystemConfigurationSession session, String virtualDirectory, String webSiteName, ADObjectId distinguishedName, Boolean isPhoneticSupportEnabled)

    After attempting many different lines and lines of PowerShell commands that did not work I came across the best way to fix this problem. The fix I found was to remove all virtual directories under the OWA and recreating them using these commands from PowerShell interface:

    Remove-OwaVirtualDirectory “owa (Default Web Site)”
    ***(Default Web Site) may depend on what your directory name is. To find out what the correct directory names are use this the command: Get-OwaVirtualDirectory
    New-OwaVirtualDirectory -WebSiteName “owa”

    This re-synced the OWA Virtual Directory to the Active Directory and allowed OWA to be accessible again.

    – Harry Caskey


  • 06Apr

    I started thinking about this last night. I know the significance of DNS within my field and I thought I would blog about it today. DNS is such a power tool, the average user uses it all the time and probably doesn’t know it.

    DNS plays a huge role in connection everyone to everyone. It starts with your Local Network Connection, for any network connection to work you have to have at least these 3 different settings configured. 1) An IP Address, this is your unique identifier assigned to a media access control (MAC) address which is the hardware that is your device. 2) A Gateway, this needs to be defined so that when you request data it knows where to send it out and expect to receive. 3) DNS Servers, after you have your IP address assigned and Gateway you will need your DNS servers to do resolution requests for you such as….

    Let’s say you get your network card setup and want to go to “www.google.com” well your computer doesn’t automatically know where “www.google.com” is at. So it sends a request to a DNS server which holds that information. So you are at your computer you type the address in “www.google.com” the first query that gets asked is where is “.com.” at? The .com is part of what’s called a TLD which stands for Top Level Domain. These are typically government run servers by ICANN. At this level these domain names can not be purchased. Then your query request then looks for the record “google” under the TLD “.com.”. When it finds that record it asks for “www” under “.google.com.”? Then for each of these requests you have a Public IP address, these are assigned by your Internet service provider (ISP). So the final query that gets sent to your computer returns the value IP address with ( resulting in “www.google.com.”. Your computer then receives all of the information that is provided on the default port 80 at that IP address with that given host header value.

    It is vital as a Network Administrator to know that your network is configured correctly. This also is very important to know because when you need to troubleshoot something you will need to know how to solve the problem. If you If you are just learning about the Information Technology field or have an interest, it is very important that you know how DNS works and if there is an underlying issues within your zone records. So that when clients request access to certain sites you know where they are being sent to.

    One great thing about DNS that you can utilize is custom domain configuration you can make a domain name “blahdityda.blog” and tell your DNS server to point to this web server. When you control the DNS you can configure your local DNS to allow “blog” to be a TLD then under that record configure bladityda to point to the specific web server hosting the host header value. These are great for and commonly used in organizations that have internal portals, or intranets.

    If you learn DNS like that back of your hand it will make things easier for you and how you can manage your network. I would recommend that you utilize DNS to it’s full potential.

    – Harry Caskey