Windows Server

Anne-Marie · Guest

I am trying to create an area in the Portal and when I enter the details and
click ok I receive the below error message:

An error has occurred in the portal site. Contact the portal site
administrator for assistance.

I have checked security and rebuilt the indexes. What else could this be?

Thanks!
Anne-Marie

Iffin · Guest

Anne-Marie,

Today also, we are having this same error, the only thing I can see that has
change recently, is the installation SP2 for Web Services etc. nothing else
has changed.

Regards

Iffin

"Anne-Marie" wrote:

Anne-Marie · Guest

I think you might be on to something... We are having the following issues
today and it appears none of these happened on Wednesday. However, since the
install of the newest Sp2 for Webservices here is what we have found:

1. When creating a new subarea in the Manage Portal Site Link, we receive
the following error:
"An error has occurred in the portal site. Contact the portal site
administrator for assistance." However, if you check the back end folders, it
has indeed created the area. But when you check the gatherer log the indexed
returns this error for the newly created subarea even though it threw the
above error:
10/17/2005 5:44:08 PM Modify sts2://sharepoint/c13/test/webid=009/
The address could not be found, (0x80042616 - Error in the Site Data Web
Service. ) Item not found. If you click on the link for sts2:// it takes you
to the new area which one would have thought did not get created because of
the "An error has occurred in the portal site" was given.

2. When working with a Document Library, if you click on Modify Settings and
Columns, click on existing Column called Category. Add an additional choice
as its a multi-choice field and click ok. You receive the following error:
Cannot complete this action.
Please try again.

Weird. I am installing SP2 on another service with Sharepoint Portal
installed and will see if these issues happen there as well. Will keep you
updated. I may be calling Microsoft tomorrow. :)

THanks!
AM

"Iffin" wrote:

Iffin · Guest

Anne-Marie,

Unfortunately it looks like we are unable to remove this latest update, so
are unable to test if this fixes our problem.

As we only have one WSS server, we are having a bit of difficulty testing
for a work around.

And pointers or additional hot-fixes that are available would be appreciated.

Regards

Iffin

"Anne-Marie" wrote:

Anne-Marie · Guest

Also found that we cannot use a custom template that was uploaded. I had a
marketing template from MS that was loaded before the SP2 update and a site
was created from it. However, today when I go to create a new site and choose
the template, I get the following error:

The statement has been terminated.

Good news is that we have turned off automated updates on the server. :)

"Iffin" wrote:

Guest

I've found also that I cannot create any new areas or subareas in our
portal. The only thing that has changed is the application of SP2. It
appears as though the areas I'm trying to create are actually getting
added to the content database.

The error in the w3 process log looks like this:
10/19/05 14:11:51:359 UNK 00000000 00001698 Exception in
SPSSubweb.Create at
Microsoft.SharePoint.Library.a.a(String A_0, Object A_1) at
Microsoft.SharePoint.SPWeb.a(StringDictionary A_0) at
Microsoft.SharePoint.Utilities.SPPropertyBag.Update() at
Microsoft.SharePoint.Portal.az.a(SPSite A_0, PortalContext A_1, String
A_2,
String A_3, Int32& A_4)

I'm able to browse to the site by typing the url. However, it doesn't
appear to know where it should exist in the heirarchy of my other
portal areas.

Anne-Marie · Guest

I called Microsoft, we had to a stsadm force upgrade as the service pack 2
for wss did not install successfully.

Once we ran the stsadm force upgrade command it worked and fixed all of our
issues.

"pjirsa@winona.edu" wrote:

PJ - WSU · Guest

I just used this fix as well, and everything is back to normal!!!!
WOOHOOO!!
Now I just have to root around and figure out how to delete all those
orphaned sites that were created when I was trying to make portal
areas. I think I'll probably just code up a little windows OM app to
iterate the sites and delete the ones that shouldn't be out there.

joemoplata · Joined: 07 Nov 2005 Posts: 1

So what was the synatx for the STSADM.EXE command you ran for force upgrading? Any information on this particularly stupid bug would be extermely appreciated.

	Windows Server Forum Index -> Portal Server Development	All times are GMT
Page 1 of 1