%3CLINGO-SUB%20id%3D%22lingo-sub-333148%22%20slang%3D%22en-US%22%3EMOSS%20SSP%20Unexpected%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333148%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3E%20First%20published%20on%20MSDN%20on%20Oct%2026%2C%202007%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CP%3EI%20ran%20into%20an%20issue%20where%20after%20deploying%20some%20custom%20solutions%20with%20a%20customer%2C%20the%20SSP%20site%20would%20not%20load.%20It%20would%20just%20display%20a%20message%20that%20said%20unexpected%20error.%20In%20the%20event%20logs%20we%20saw%20the%20following%20error.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Event%20Type%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Error%20%3CBR%20%2F%3E%20Event%20Source%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%20Windows%20SharePoint%20Services%203%20%3CBR%20%2F%3E%20Event%20Category%3A%20Runtime%20%3CBR%20%2F%3E%20Event%20ID%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%206610%20%3CBR%20%2F%3E%20Date%3A%26nbsp%3B%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2010%2F26%2F2007%20%3CBR%20%2F%3E%20Time%3A%26nbsp%3B%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%2010%3A26%3A31%20AM%20%3CBR%20%2F%3E%20User%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3BN%2FA%20%3CBR%20%2F%3E%20Computer%3A%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20MACHINENAME%20%3CBR%20%2F%3E%20Description%3A%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20Safe%20mode%20did%20not%20start%20successfully.%20Request%20for%20the%20permission%20of%20type%20'Microsoft.SharePoint.Security.SharePointPermission%2C%20Microsoft.SharePoint.Security%2C%20Version%3D12.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D71e9bce111e9429c'%20failed.%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20For%20more%20information%2C%20see%20Help%20and%20Support%20Center%20at%20%3CA%20href%3D%22http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2Fevents.asp%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2Fevents.asp%20%3C%2FA%3E%20.%3C%2FP%3E%3CBR%20%2F%3E%3CP%3EThe%20fix%20for%20this%20was%20to%20change%20the%20trust%20level%20in%20the%20web%20config%20from%20WSS_Minimal%20to%20WSS_Medium.%3C%2FP%3E%0A%20%0A%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-333148%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Oct%2026%2C%202007%20I%20ran%20into%20an%20issue%20where%20after%20deploying%20some%20custom%20solutions%20with%20a%20customer%2C%20the%20SSP%20site%20would%20not%20load.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-333148%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esharepoint%20server%202007%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Essp%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on MSDN on Oct 26, 2007

I ran into an issue where after deploying some custom solutions with a customer, the SSP site would not load. It would just display a message that said unexpected error. In the event logs we saw the following error.

Event Type:       Error
Event Source:    Windows SharePoint Services 3
Event Category: Runtime
Event ID:           6610
Date:                10/26/2007
Time:                10:26:31 AM
User:                 N/A
Computer:          MACHINENAME
Description:

Safe mode did not start successfully. Request for the permission of type 'Microsoft.SharePoint.Security.SharePointPermission, Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp .


The fix for this was to change the trust level in the web config from WSS_Minimal to WSS_Medium.