I recently ran into an issue while assisting my company’s web developers with a site that would not load. The general error was HTTP 500 Internal Server Error.
The site in question, had recently been copied from a staging server to a production server. While it worked in staging, it did not load in production. I logged into the production server to get more detailed information by loading the page in IE. IE threw the following message:
This particular site runs on Server 2008 and the application was built for ASP.net 1.1. After doing some research and thanks to http://www.iis.net I found the answer. It was determined that the machine.config files did match up in staging and production.
Per IIS.net —
ASP.NET v1.1 will throw runtime exceptions out of the box if you have IIS configuration in the web.config files that are read by your ASP.NET v1.1 applications. To make ASP.NET v1.1 ignore IIS configuration sections, open the Framework v1.1 machine.config file (%windir%\Microsoft.NET\Framework\v1.1.4322\config\machine.config) and add the following section entry just above the bottom tag for the element:
<section name=”system.webServer” type=”System.Configuration.IgnoreSectionHandler,
System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ />
I added the aforementioned line to my machine.config file (C:\Windows\Microsoft.Net\Framework\v1.1.4322\Config) in production, the site now loads. Lesson learned. Always verify the machine.config files in both locations.
File this under tips and tricks:
You are an Office 365 subscriber and trying to launch the Lync or Skype for Business client application. When attempting to login you receive the following error…
This happens due to server authentication failure. But you can set the server settings manually. Go to Tools -> Options -> Personal -> Select Manual Configuration -> Enter: sipdir.online.lync.com:443 -> Click OK -> Click OK on the Options window.
Go back to the login screen and enter your credentials. Usually this is your email address.
Now you should be able to successfully login.
If you still encounter issues, try using the Microsoft Remote Connectivity Analyzer.
Earning certs can be time consuming and expensive. Here is a good article from ComputerWorld about five certs that won’t break the bank.
Thus far, I have not been a huge fan of Windows 8, so to troubleshoot or do testing, I keep a Windows 8 virtual machine handy. When the Windows 8.1 preview was released last week, I decided to upgrade my virtual machine. It was a very straight forward upgrade. No real glitches involved. Here are the steps:
1. Mount the Windows 8 Preview ISO file.
2. Launch setup.exe and choose whether or not to install updates.
3. Enter the license key. This can be obtained from the Microsoft site.
4. Accept the license terms.
5. Choose what to keep during the upgrade.
6. Performing some checks.
7. We’re ready to roll.
8. The installation begins.
9. The machine reboots.
10. Sticking with the fish theme I see.
11. Choose your Settings: Express or Custom.
12. Network discovery choices.
13. Choose your Windows update and Privacy settings.
14. Choose whether to share or not share info with Microsoft.
15. Setup continues.
16. And here we are at the login screen.
17. Enter your password.
18. And we’re at the desktop.
A very simple upgrade indeed. The only thing I did not see during setup was the choice to user either a Microsoft account or a Local account. Since this is a preview, I am guessing that this option will be included in the RTM release of the Enterprise version. But that’s it. Go to http://technet.microsoft.com to get your copy of the Windows 8.1 preview and see what you think.
We recently received a new Lenovo Carbon X1 Touch to setup for an employee. It arrived with the Home version of Windows 8 installed, so we proceeded to install Windows 8 Enterprise. First of all, if you haven’t seen the new Carbon X1 Touch, it is a beautiful, slim, touchscreen laptop. But it does not have a built in NIC card. You have to attach an ethernet dongle if you want to be hard-wired in to your network. This device does not allow for booting up to our Microsoft Deployment server. There is an additional driver required in order to do this. So, we decided to install the OS via USB. I created a bootable Windows 8 USB stick (Using ISO to USB; http://www.isotousb.com) and booted from the USB.
All seemed well until it came time to choose the partition on which to install Windows. I chose the OS partition and received this error:
“Windows cannot be installed on this disk. The selected disk is part of the GPT partition style.”
I started troubleshooting by choosing to format the OS partition. That did not work as I received the same error message. So what to do but start from scratch. I delete all of the other existing partitions, formatted again and attempted to install the OS. This did not work either:
I rebooted, chose Repair at the initial install screen, and opened the command prompt. I ran the following diskpart commands:
- list disk
- select disk “x” (this is the disk on which you want to install Windows)
- create partition primary
- format fs = ntfs quick
I rebooted and started the installation again. I chose the partition I needed and was able to install Windows 8. If you run into this error, just perform the diskpart steps above. That should resolve the issue.