"An Unexpected Error"

Oct 9, 2007 at 5:35 AM
I think I've got most of this demo running now, and the site provisioning "sorta" works, but when I try to open a newly created site, I get a generic error page with very little info:

Error
An unexpected error has occurred.
Troubleshoot issues with Windows SharePoint Services.

I can't find any evidence that an error actually occurred, though. IIS logs indicate a 200 response. Event log has nothing. Well, there were some DCOM errors, so I gave local launch permission to IIS WAMREG Admin to the service account that WSS is running under. The WSS trace log doesn't seem to have any errors either.

Anyone have an idea what might be causing this? Or do you know of other places to look for errors?

Thanks in advance,
Mike


Coordinator
Oct 22, 2007 at 9:41 PM
Hi Mike,
Sorry for the delayed response - I've been OOF.

Was the site actually created? verify with stsadm -o enumsites -url http://<servername>
Check SQL server database: aspnetdb to ensure that user was created.

Lisa


rdcpro wrote:
I think I've got most of this demo running now, and the site provisioning "sorta" works, but when I try to open a newly created site, I get a generic error page with very little info:

Error
An unexpected error has occurred.
Troubleshoot issues with Windows SharePoint Services.

I can't find any evidence that an error actually occurred, though. IIS logs indicate a 200 response. Event log has nothing. Well, there were some DCOM errors, so I gave local launch permission to IIS WAMREG Admin to the service account that WSS is running under. The WSS trace log doesn't seem to have any errors either.

Anyone have an idea what might be causing this? Or do you know of other places to look for errors?

Thanks in advance,
Mike




Oct 23, 2007 at 5:30 PM
Yes, the site gets created, but when you try to load the site in a browser, you get this error:

http://rdcpro.hopto.org/Photos/screenshots/CreateSiteError.jpg

stsadm enumsites produces this on a newly created site (along with the previously created sites, which I've left out of the snippet):

<Site Url="http://www.testsite1.com" Owner="aspnetsqlmembershipprovider:testuer1"
ContentDatabase="WSSContentWSS_Hosting" StorageUsedMB="1.3"
StorageWarnigMB="0" StorageMaxMB="0" />


The user gets created, but shows up twice in the database first two GUIDs are ApplicationId and UserId:

8eb39c18-f4dd-4d67-a62c-338fbe1e36f5 48acb5af-66e1-4515-8c30-ce408bd74941 TestUser1 testuser1 NULL False 10/23/2007 5:00:16 PM
821df51a-4881-4f38-b039-47e1add9ec1c 84e1178b-361a-45b3-897b-02988b2fa9eb TestUser1 testuser1 NULL False 10/23/2007 5:02:12 PM

I presume the first occurance is the user on the "StarterKit" site, and the second instance is the user as Admin of the newly created site, right? So the user is always scoped to the site? In the membership table, the first instance of testuser1 has the plain text password, and the second instance has the hashed value.

I'm wondering (assuming I ever get this working) whether password resets will reset the password on all sites?

Thanks for your help!
Mike


lisataka wrote:
Hi Mike,
Sorry for the delayed response - I've been OOF.

Was the site actually created? verify with stsadm -o enumsites -url http://<servername>
Check SQL server database: aspnetdb to ensure that user was created.

Lisa