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.

 

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


I'll be speaking tonight on the windows SharePoint API at the Philly Office Geeks April meeting.  I was supposed to speak back in February but due to weather the meeting got canceled.

I believe that I am to present at 7PM, before that though there is free PIZZA!!!! and also another presentation. 

 

All the slides and code samples can be found in my presentations section of my blog, download the presentation "The SharePoint front-end is for wimps, real men use the SharePoint API's".

 

Hopefully there is a good turnout.


Tony Testa posted on March 19, 2008 13:32

Ran across this issue the other day at a client.  I was setting up Forms Based Authentication for a SharePoint site collection and naturally created another Zone for it like I had a multiple times in the past.  Problem was, it turns out that we didn't want it to be like the typical multiple site collection (one with Windows Auth, and the other with FBA), so I was left with an extra zone DOH!

If there is a way to delete it through central admin then I must have missed it.  Below is the only command to my knowledge that will let you delete an extra Zone from your site collection.

 

stsadm.exe -o unextendvs -url http://yoursite:portNo -deleteiissites

 

Once again, stsadm.exe saves the day and gives me another reason to despise the Central Admin UI.


In my experience, the line between Dev. and DBA isn't always clear.  In the absence of a true DBA, guess who ends up being expected to enforce Database best practices?  Thats right, the Dev. is expected to know everything a DBA would be expected to know.

A few years back, the only thing I knew about databases was 3rd normal form, Primary Keys, Foreign Keys......that about sums it up.  I don't think I'm far off by assuming that most devs know about the same.  In the recent years though I've been fortunate enough to be throw at some more DBA type assignments and was able to learn more of the DBA roles' responsibilities.

In my more recent development projects, I find more and more that I'm asked, or expected to know more advanced database concepts.  Things like indexes, database integrity checking, truncating large log files, etc.

Luckily, SQL 2005 makes these more DBA tasks pretty easy to perform by way of a Database Maintenance Plan.  You can create a nightly job that will check your databases, shrink your logs, rebuild your indexes and backup your databases.  These simple tasks will help keep your databases performing optimally in addition to making you appear to know more about databases.

Bill Baer has put out a great MS white paper about Database Maintenance pertaining specifically to SharePoint.  It walks you through the steps that you should be doing to keep your SharePoint databases running at their best.

SharePoint aside, the white paper is just a good reference document about what you should be doing in general for your production databases, so I encourage any developer to read it.

 

Check out the white paper here.


Posted in: Sharepoint  Tags: ,
Disclaimer
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