This is default featured post 1 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 2 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 3 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 4 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

This is default featured post 5 title

Go to Blogger edit html and find these sentences.Now replace these sentences with your own descriptions.This theme is Bloggerized by Lasantha Bandara - Premiumbloggertemplates.com.

Monday, September 29, 2008

VS 2008 and SharePoint 2007 Service Packs released

Most of you will already know this, but VS 2008 has been released. Experience all the new functionality by downloading it from here.

WSS 3.0 and MOSS 2007 service pack 1 has also been released. You can view the details here.

Just a word of advice, unless you have a critical need that is addressed by this release - wait to hear other people's upgrade experiences before jumping the gun on this one, especially in a production environment.

Error: The path specified cannot be used at this time.

Sometimes when doing application management tasks, you run into an error where the page stops creating your Web Application or other management task and instead throws this error:

Error: The path specified cannot be used at this time.

Upon digging a little deeper to ascertain the cause of the problem, I noticed that these 3 errors were being thrown on a consistent basis.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Event ID: 6398.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Event ID: 7076.

Attempted to read or write protected memory. This is often an indication that other memory is corrupt. Event ID: 6482.

I found this KB that related to this error, but I didn't want to install it on the server directly. So here are the things I did to resolve this.

1. Installed the latest critical updates from Windows Update on the servers.
2. Re-started the servers in the farm for those to take effect.

This fixed the problem temporarily. It came back a couple of days later so I restarted the SharePoint timer service. Since then, the error has not come back.

Share

Twitter Delicious Facebook Digg Stumbleupon Favorites More