I recently created a custom view in MOSS with a column using the Checkbox (Yes/No) data type. The view was filtering on that column (is equal to Yes).
I later changed the data type to Choice and provided Yes and No values. The view failed to render and displayed the error:
I modified the view (the filter was changed to "is equal to 1") to change the filter to Yes again and that fixed the issue.
I've never seen the render error before, so here you have it.
Wednesday, April 15, 2009
Thursday, April 02, 2009
Building My MOSS Farm: Part 1
Few months ago, I bought a serious Intel Core 2 Quad (4 cores, that is) with 2.83Ghz and 8GB of ram. It's a 64 bit machine with 120GB of 10,000 rpm for the C drive (makes all the difference, believe me) and additional 500GB drive. The plan? Not a nuclear bomb, but to build out a 4-server MOSS farm.
In these series, I'll chronicle the build and configuration process.
1) I will be using my MSDN subscription for the software.
2) I decided on installing Windows 2003 Enterprise Edition R2 (64 bit, of course).
3) I am going with SQL Server 2008 Enterprise edition.
4) MOSS 2007 SP1 + February update.
5) I will be using VMWare to host my farm. So why not Virtual PC 2007?
Reason 1: Although it's free, I was so disappointed that 64-bit guest machines are not supported. Are you kidding me?!
Reason 2: VMWare just rocks. You'll see why soon.
Approach
1) Build a base machine with all updates and patches + .NET framework 3.5 SP1.
2) Clone this machine for the 4 servers in the farm.
MOSS Farm
Server 1: App server, i.e central administration + indexing role
Server 2: Database server
Server 3: Web server 1 + query role
Server 4: Web server 2 + query role
To be continued...
In these series, I'll chronicle the build and configuration process.
1) I will be using my MSDN subscription for the software.
2) I decided on installing Windows 2003 Enterprise Edition R2 (64 bit, of course).
3) I am going with SQL Server 2008 Enterprise edition.
4) MOSS 2007 SP1 + February update.
5) I will be using VMWare to host my farm. So why not Virtual PC 2007?
Reason 1: Although it's free, I was so disappointed that 64-bit guest machines are not supported. Are you kidding me?!
Reason 2: VMWare just rocks. You'll see why soon.
Approach
1) Build a base machine with all updates and patches + .NET framework 3.5 SP1.
2) Clone this machine for the 4 servers in the farm.
MOSS Farm
Server 1: App server, i.e central administration + indexing role
Server 2: Database server
Server 3: Web server 1 + query role
Server 4: Web server 2 + query role
To be continued...
Labels:
MOSS,
MSDN,
SQL Server 2008,
Virtualization
MOSS: Deleting Web Application in Central Administration Fails
If you have a Web application in MOSS (or WSS) and you try to delete it from Application Management --> Delete Web Application, you get the following error:
This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again. at Microsoft.SharePoint.Administration.SPWebApplication.UnprovisionIisWebSitesThroughAdministrationService(Boolean deleteWebSites, String[] serverComments, String applicationPoolId) at Microsoft.SharePoint.Administration.SPWebApplication.UnprovisionIisWebSites(Boolean deleteWebSites, String[] serverComments, String applicationPoolId) at Microsoft.SharePoint.ApplicationPages.DeleteWebApplicationPage.BtnSubmit_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Reason? The user logged in is not an administrator on the Web server. Check out this KB article.
This operation uses the SharePoint Administration service (spadmin), which could not be contacted. If the service is stopped or disabled, start it and try the operation again. at Microsoft.SharePoint.Administration.SPWebApplication.UnprovisionIisWebSitesThroughAdministrationService(Boolean deleteWebSites, String[] serverComments, String applicationPoolId) at Microsoft.SharePoint.Administration.SPWebApplication.UnprovisionIisWebSites(Boolean deleteWebSites, String[] serverComments, String applicationPoolId) at Microsoft.SharePoint.ApplicationPages.DeleteWebApplicationPage.BtnSubmit_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Reason? The user logged in is not an administrator on the Web server. Check out this KB article.
Subscribe to:
Posts (Atom)