This always happens. It’s an idea that gets my creative juices flowing…an idea that I think I can tackle with the technology that I already know. The exact technology that I plan to use is of no consequence…just know that that to make my idea a reality, I will need to use technology. Technology beyond your basic remote control…we’re talking code here. I sit down and hack it out. I think I’m making great progress until I hit a stumbling block. I figure that issue one out and move on. Ain’t no stoppin’ us now!!! I’m getting close to making my idea a reality…and then it happens. A wall so palpable that you can smell the bricks. Is there way around this wall? Hmm. Not that way. How about…no…that wouldn’t work. What the heck is wrong here? The wall in front of me happens to be the one undocumented, tiny f*cking piece of information that I need to complete what I’m trying to do.
SharePoint Stand Alone Install
I had this great idea that if I had a standalone SharePoint image that I could then copy and re-use in Virtual PC, then I could quick create proof of concepts quickly and easily. Okay, so let’s build a standalone SharePoint virtual. Enter Martin Kearn:
http://blogs.msdn.com/b/martinkearn/archive/2007/03/28/how-to-install-sharepoint-server-2007-on-a-single-machine.aspx
Martin gives an excellent series of steps on how to get a standalone server setup. His instructions are not geared towards my specific situation so I don’t fault him for the problem that I would eventually have. If you are like me and trying to setup SharePoint in VirtualPC, you might want to setup the DNS Host (A) records as the loopback (127.0.0.1) since your image’s IP address could change based upon your location.
This one minor derivation cost me…to the tune of hours of time trying to figure out why in the hell I couldn’t log into my SharePoint sites (Intranet, MySite or Intranet) in the end. I received a security dialog prompting me to login at which point I used my SharePoint service account which had Administrator access. You know you’ve got a problem when it keeps returning for you to specify your credentials…until you get the inevitable:
HTTP Error 401.1 – Unauthorized: Access is denied due to invalid credentials
This is when I start to groan…technology bites me again. What the Mother-Loving ‘F’ (I have young kids so I’m trying to stop swearing). But this is not the coup de grâce moment…no, that is saved for later...like that most tragic of movie endings that leaves you decimated. I spend a bit more time…I’ve phoned a friend, I’ve prayed to the Google gods…and there it is:
http://www.jppinto.com/2009/06/you-receive-an-http-error-4011-error-when-accessing-a-moss-sharepoint-2007-site-on-a-web-front-end/
Who in the hell is JP Pinto, Seasoned IT Dude? I have no idea, but he mentions something that makes me think that it might just fix my problem. Specifically this statement:
I have noticed that this happens on Windows 2003/2008 Server SP1/SP2/R2 when using Host Headers and Alternate Access Mappings on a web application in MOSS 2007. If you can access the site from remote machines and cannot access the site from the server itself, then this might be your issue.
Did you catch that? ‘I have noticed…’ That’s what we are reduced to anymore in technology. I just lost days of my life looking for an answer and JP Pinto is telling me that the only reason that I’m not jumping out a window at this point is because he’s paying attention.
The long and the short…I try Option #2 which is changing the registry…CHANGING THE REGISTRY…and my SharePoint virtual is working perfectly.
I almost couldn’t believe it…so much so that I had to create another virtual with a different OS to see if this worked there too…and it did!
I should be happy, right? My problem is solved…I can move on! Why should I view this as a moment of grief? Why…because this is all too commonplace. Because it was painful. And because it took me two days to find the answer.
My wife asks me how would I have solved this problem before the Internet…I must say I have no idea. Call support? But the complexity of systems anymore outright DEMANDS full Internet access (blogs especially) in order to solve technology problems. I must say that I giggle when I hear that an organization that I’ll be working with has web filtering in place that will restrict my access to the Internet. That’s like outlawing hammers on a home construction site.
My #1 destination when I’m trying to figure out a technical issue is blogs anymore. Unfortunately, finding the specific answer to the problem I’m having leads me far and wide and it’s the techniques that I employ in that process that determine how soon I’ll resolve my issue. And for those blog posts that do solve someone’s issue, you find comments at the bottom like:
‘You’re the man, this solved my problem.’
‘Thank you thank you thank you’
etc.
So, thank you, JP Pinto…you are not only a Seasoned IT Dude, but for today you are my SharePoint god for the simple fact that you kept your eyes peeled and added something to your blog so the rest of us jabroni’s can benefit from your awareness.
It turns out that, yes, this is documented amidst the THOUSANDS of other documented issues out there in the vast technology landscape…in case anyone wants to read Microsoft verbiage on this, realize that this relates to IIS 5.1 and later:
http://support.microsoft.com/kb/896861