I hit the "path specified cannot be used at this time. (Exception from HRESULT: 0x80070094)" error while I was trying to setup a simple blank site the other day.  I was banging my head against the wall for about an hour but after searching the web for a bit, I ran across a few solutions but none of them seemed to work, it was a combination of a few. 

Here are the steps that worked for me:

  1. IISRESET on all servers (WFE's and IDX server)
  2. Windows SharePoint Services Timer Service on all servers (WFE's and IDX server)
    • Administration Tools -> Services -> Windows SharePoint Services Timer Service (all the way at the bottom)
  3. Created a new application pool for your new web application in IIS on all servers
    • I used the Default App Pool template
    • Create the application pool with its own AD account
  4. IISRESET on all servers (WFE's and IDX server)
  5. Finally, go into your Central Administration and create a new web application and make sure to select the application pool you created.

I was doing my usual blog rounds and ran across Jeff Atwood's latest post entitled "PHP Sucks, But It Doesn't Matter".  I have to say, I can't agree enough with Jeff.  Jeff, as usual, lays out his argument pretty convincingly.  In general, most of the PHP code you'll run across is messy, unmaintainable and you'll wonder how it ever works.  On the flip side to that, some of the most widely used web sites out there run PHP (Digg, Facebook, etc.). 

What does all that mean then?  Lots of messy code, but lots of successful web sites, how does that happen?  Again as Jeff explains, great programmers can make great applications using a crappy language (don't take this as me saying PHP is crappy, I've used it, I like it, I see its place).  I certainly share Jeff's opinion on the matter.  Most of the PHP code I have seen from others is pretty messy, and that's putting it nicely.  BUT if it comes to a 1 page survey application that needs to be done in 2 hours from now, PHP will be my pick any day of the week over C#.  You have to look at the language and what they were intended for though.  PHP was a web scripting language, so naturally, it is something that you can whip out small web app in with little effort.

Based on that, it makes me want to try that much harder to make something worthwhile with my .NET skills.  I want to prove myself as not only a programmer, but a great programmer that can succeed no matter what language he works in.  My current challenge right now is SharePoint development.  I don't think I am stating anything mind blowing by saying SharePoint development is slow going.  Simple modifications end up taking 2x maybe even 3x to test and verify they are working.  So my ultimate goal is to bypass that hurdle and be more productive with my SharePoint development tasks.  Some possible solutions to this are writing small utlity apps that speed my development efforts, which I hope to release to CodePlex so that others can benefit.  Right now my current goal is to release a SharePoint log reader application, more details to come on that soon.


Update (05/23/2008): Just ran across another link listing some other great, successful PHP applications.

Posted in:   Tags:


Yesterday was yet again another great code camp.  Again, it was at DeVry  University (big thanks to them for letting us use the facility) which was the perfect place.  There were about 600 people that registered and I think roughly 550 or so actually showed up which is great! 

As for my presentation I think that things went really well.  Those who attended really seemed to get a lot of out it.  My demo application seemed to be of most interest because everyone wanted the source code, which really makes me believe that the attendees got a lot out of the presentation.  Thanks to those who attended, and I can't wait to see the reviews (which were web based this time, so hopefully we will get them a lot sooner).

Here is a link to the slides and the demo application as promised, PhillyDotNetCodeCampGUIAPIDemos.zip

It is a well know fact that the SPSite and SPWeb objects need to be properly disposed of when using them in your API coding.  MSDN and the SDK typically tells you that when you see anything referencing those 2 objects.  The reason is that behind the scenes they have a reference  to a SPRequest object which uses a SharePoint COM object which isn't automagically disposed for you.  All the examples on MSDN and in the SDK show how to use the "using" statement, or manually calling "Dispose()" on the objects, but they don't really offer any other info than that.

Today I ran across a few REALLY good blog postings about this topc.  The first, by Stefan Gobner, shows how to do some troubleshooting, which is DEFINETELY worth a read.  He shows how you can go into the ULS logs, find certain error messages, and really track down the code that you wrote to find where you might not properly be disposing of the suspect objects.  You can find that article here, I strongly suggest reading it.

The second article, written by Roger Lamb, is actually linked from Stefan's blog and goes into a LOT more detail about pretty much all the objects that need to be disposed, and shows a lot more than MSDN/SDK does.  You can find that article here.

Starting next week, May 20th, Microsoft along with a few SharePoint MVP's are having a series of webcasts geared toward SharePoint development for a .NET Developer.  I stumbled upon it over at Andrew Connell's blog, here.  Below is the line up

Date (all times EDT) Topic & Registration URL Presenter
Tues, May 20 : 12-1p Web Parts Rob Bogue
Wed, May 21 : 12-1p Data Lists Rob Bogue
Tues, May 27 : 12-1p Silverlight AC
Wed, May 28 : 12-1p Event Handlers AC
Tues, June 3 : 12-1p Site Branding AC
Wed, June 4 : 12-1p Workflow Rob Bogue
Tues, June 10 : 12-1p Web Services AC
Wed, June 11 : 12-1p Page Navigation AC
Tues, June 17 : 12-1p User Management Rob Bogue
Wed, June 18 : 12-1p Content Types Rob Bogue


It looks like a pretty good line up and if you miss any of them, they will have them recorded so you can download it and watch it at a later time.  I'll be sure to post my thoughts after the first one to let you know if they seem worthwhile.  Both presenters, Rob Bogue and Andrew Connell, know their stuff so I'm sure that they will be good web casts.

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2017 Tony Testa's World