I found a very cool utility this week that has saved me some precious time. I'm working on a SharePoint 2007 project running on Windows 2003 Server and I needed to adjust a feature of the application to send some confirmation emails. My first inclination was to setup an SMTP server for testing. As usual, I started with a search on Google and fortunately for me I accidentally stumbled across Papercut as an alternative to doing my email testing. No need to setup an SMTP server. No need to constantly jump into my email and check for the confirmation. For those times when you do need to see the email in an email client (when you need to check HTML rendering) you can forward captured emails.
I've been working in Internet Explorer land lately. This is primarily due to contract work on a SharePoint project where the client really only cares about IE working well. (at least for now) So for all of you Firefox users out there who (like me) are use to have Firebug at your finger tips it can be a little mind numbing to be without a way to see the HTTP traffic in all it's glory. That's where Fiddler comes in to play! In fact, it might just replace Firebug altogether for me. I like the stand alone process approach. So far Fiddler is footing the bill. If you're looking for a good Web debugging Proxy that is free then you should give it a try.
I was working on a project today and ran across a painful delay. I have Windows 2003 Server with Microsoft SharePoint 2007, SQL Server 2005, and IIS 6.0. I was finally to the point (actually long past it) where I should have setup SSL for some testing. Naturally I hit the search engines to find the easiest way to setup a self signed certificate under IIS. That is when I ran across this post on SelfSSL which is part of the IIS 6.0 Resource Kit Tools. Unfortunately, that's where my trouble began. I followed the instructions installing just SelfSSL and the log analyzer tool. Then I proceeded to use the SelfSSL to create certificates for my SharePoint site(s). Installing the certificates using the tool was painless. No errors, it just went smoothly. I have form based authentication and I was able to connect via SSL but something weird was happening with AD site and it was preventing me from actually working. Since I couldn't afford to be delayed on some of this work I decided to revert the system back to non-SSL state and keep working figuring that I would get back to this when I had more time to spare on solving whatever issue was keeping things from truly working. That's when all the fun began. I removed the certificates using IIS manager and then restarted the server thinking I'll get a clean start to ensure it would be working again. I was indeed wrong. When the system came back up I wasn't able to connect to the SQL Server instance.
The first indication came from my SharePoint AD site with the message
"Cannot connect to the configuration database."
I received a slightly different (and much longer) message from try to connect using SQL Server Management Studio. Here's the important parts.
"error occurred during the pre-login handshake ... No process is on the other end of pipe"
Naturally I was confused as to why uninstalling SSL certificates would affect my SQL Server connection but it did. As it turns out, SQL Server uses a certificate to encrypt the login information even if your not going to use a secure connection. In the absences of an assigned certificate SQL server will create a self signed server certificate to use. Unfortunately, if there are certificates available then SQL Server will "apparently" grab a certificate to use providing it meets certain criteria which apparently my discarded SelfSSL certificates did. After reading numerous posts to understand what was happening I was able to clean it up on my system. See below for some of the more useful posts I found on this topic.
What must I do to fix this?
Make sure you have the same problem. Apparently there are a few ways to get these same error messages from SQL Server so unless you have recently installed or un-installed self signed certificates on IIS where IIS is on the same box as SQL Server 2005 you might find this fix won't do anything for you.
Even though I used IIS Manager to remove the certificates there were still around on the system and SQL Sever was still finding them. So, I basically did the following:
1. Click the Windows Start button and ran MMC to get the Microsoft Management Console.
2. Choose File --> Add / Remove Snap-in... from the main menu.
3. Click the "Add" button on the Standalone tab.
4. Choose "Certificates" and click the Add button.
5. Choose "Computer account" and click the Next button.
6. Choose "Local computer" radio button and clicked Finish.
7. Click the "Close" and "OK" buttons on the previous two dialogs.
8. In the list I navigated to "Certificates (local computer) -> Personal -> Certificates"
NOTE: Your self signed certificates might be some place else but they're most likely here.
CAUTION: Be sure you SELECT the right certificates in the next step!!!
9. Click on certificates to select them and use the option to delete. BE SURE TO get the self signed ones. There could be others here!!!
After I did this my SQL Server 2005 instance was all good again. I was able to connect.
Hopefully find this post helpful and it save you some of the 2 hours I lost on this little expedition.
This is my blog and an attempt to try and contribute a bit of information for all those who have a life developing software. Hopefully you'll find something useful on this blog, I hate to think I'm wasting time.
Have something you need done and done right? I've been creating software for over 24 years and there probably isn't very much I haven't seen. I can create something from scratch or jump in and try to recover a project gone south. Contact me if you would like some help creating or fixing software.