Sign In
The Sug > Blogs > Jennifer's SharePoint Blog
January 12
ASP.Net Setup Error
Today I was putting together a simple test SP farm so I could play around with some backup stategies. Since this is like my zillioneth sp installation, I assumed I had seen it all. Guess not. As soon as I kicked off the setup executable, it immediately returned the following error:  "This product requires ASP.NET v2.0 to be set to "Allow" in the list of IIS Web Server Extensions. Easy enough. But then I opened up the IIS Admin console and noticed the entire ASP.Net v2.0 entry was missing. Hmm...I know that SharePoint is picky about installation order, and since I did not prepare the base server myself, I immediately removed IIS and all instances of .Net, then reinstalled in the following order.

1.  .Net 2.0
2.  .Net 3.0
3.  .Net 3.5
4.   Ran Windows Update
5.   Added the IIS Server Role

Darn it, ASP.Net was still missing.
Luckily I found this Microsoft article, which provided a super easy solution below.

To run the 64-bit version of ASP.NET 2.0, follow these steps:
1. Click Start, click Run, type cmd, and then click OK.

2. Type the following command to disable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0


3. Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:


%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i


4. Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager.
January 09
Web Page taking forever to load?
I recently ran across a department site that took over 35 seconds to load. hmm...that's strange. I just migrated our SP farm to a new 64bit eight server platform, so I know there is enough juice behind the wheels to load a simple page with two photos, and a banner.

First things first, I decided to see how much time I could shave off by compressing the photos to a more web page appropriate size. Fired up SharePoint designer to make the picture adjustment when low and behold the true problem slapped me right in the face. Count them, fifteen unopened web parts sitting in the background that once deleted, brought the page load time down to 2 seconds.  : )  

It turns out the the administrator for this site was closing the web parts instead of going into Edit mode and deleted them properly. Easy mistake with an easy solution.


January 09
Web Part Maintenance

Sometimes, a corrupted web part can not only take down your page, but also prevent you from you from opening the page in edit mode. To circumvent this error, simply navigate directly to the Web Part Maintenance page for any site by appeading ?contents=1 at the end or the URL.

For example:
http://mysharepointsite/default.aspx?contents=1

From the Web Part Maintenace page, deleted the misbehaving web part, and all will be well again.

January 09
Enumerate Sites

Curious on how many sites on in your Site Collection? Try the following Stsadm command to enumerate an XML report: stsadm -o enumsites –url http://yoursharepointsite > c:\sites.xml

Make sure you run the command from the c:\program files\common files\microsoft shared\web server extensions\12\bin directory.

 

 About this blog

 
About this blog
Welcome to SharePoint Blogs. Use this space to provide a brief message about this blog or blog authors. To edit this content, select "Edit Page" from the "Site Actions" menu.