Error while opening SSP default page
I have page parser entry to web.config <PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" /> and i have added safe control entry to web.config <SafeControl Assembly="Microsoft.Office.Server.UI.SharedServicesAdminDefaultPage, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" Namespace="Microsoft.Office.Server.Internal.UI" TypeName="*" Safe="True" /> and i have set trust level to full. but still i am not able to open SSP default.page it is giving me fallowing error. The base type 'Microsoft.Office.Server.Internal.UI.SharedServicesAdminDefaultPage' is not allowed for this page. The type is not registered as safe. Can anyone help me please..
June 25th, 2010 10:40pm

Did you change something in master page for SSP admin site? Oleg
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2010 10:56pm

No i didnt Change anything in master page for ssp
June 25th, 2010 11:01pm

Try to reset SSP site to site defenition. Open http://server:port/ssp/admin/_layouts/settings.aspx and click Reset to Site definition or open http://server:port/ssp/admin/_layouts/reghost.aspx Remove safe entry from web.config Oleg
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2010 11:09pm

I tried this but still I am getting the same error..
June 25th, 2010 11:22pm

Can you give more information what you did before this issue? Oleg
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2010 11:25pm

I deployed som web part to GAC and added safe entry and added parser path <PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" /> and set trust level as full. after this i created ssp and when i try to open ssp default page I am getting above specified error.
June 25th, 2010 11:33pm

Did you run iisreset after http://server:port/ssp/admin/_layouts/reghost.aspx ? Oleg
Free Windows Admin Tool Kit Click here and download it now
June 25th, 2010 11:42pm

Yup..
June 25th, 2010 11:45pm

I can just suggest uninstall custom web parts, delete SSP and create it again after that install custom web parts. Oleg
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2010 12:04am

If i remove the page parser path entry ssp works fine but if i include, it gives same problem again..
June 26th, 2010 9:57am

The Physical path to the WebApp is stored in the Config_Db. Since you can't change the physical location in the Config_Db you can't move the web application path after the web application is in use. -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2010 10:13am

if I add this entry <PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" /> in web.config I am getting the fallowing error while opening ssp The base type 'Microsoft.Office.Server.Internal.UI.SharedServicesAdminDefaultPage' is not allowed for this page. The type is not registered as safe. Is it possible to deploy web parts without specifying pageparser entry in web.config
June 26th, 2010 10:20am

Hi Manjunath, You cant change the path of where the webApp is deployed or create exclusions <PageParserPath VirtualPath="/*" CompilationMode="Always" AllowServerSideScript="true" IncludeSubFolders="true" /> is modifying the the Physical Address space and it doesnt match the Config_Db and there will be all kinds of errors and this is only one... Inline code is disabled by default on any customized or uploaded Web page in a SharePoint site. It can be enabled on a per directory path basis, with children potentially inheriting the settings. This exclusion can be enabled through the specific Web site path that is included in the PageParserPaths collection in the web.config file. After the PageParserPath inline code exclusion is set, any page within that directory has the capability to execute any code that is embedded directly in the HTML content of the page if the script tag is set to run at the server. Because inline code can run with full trust on the server, it is possible for a developer to expose data from anywhere in the SharePoint environment by making a call to elevate the privileges of the code during run time. As a best practice, any inline code should therefore be reviewed for security implications before it is allowed to be installed and run on the server. The following support policies are recommended for inline code: Inline code in Site Definition based ASPX pages: Inline code is not recommended within a site definition due to the issues involved with the code no longer rendering as soon as the page is customized. Inline code in _layouts-based ASPX pages: Inline code is supportable if included on a page in the _layouts directory. Inline code enabled through PageParserPath exclusion: Inline code should not be allowed through the PageParserPath exclusion, except in extremely rare circumstances, because it can be modified without going through any review process. As a result, it represents a danger to the environment’s performance and security Inline code is enabled on any Web page installed on the file system of the server, such as within a site definition or in the _layouts directory. One problem with using inline code in a site definition is that the code will work inline as long as the page instance in a site is not customized to the file system. However, as soon as it is customized, the inline code will fail. Also, Inline code is enabled on any Web page installed on the file system of the server, such as within a site definition or in the _layouts directory. One problem with using inline code in a site definition is that the code will work inline as long as the page instance in a site is not customized to the file system. However, as soon as it is customized, the inline code will fail. Reference http://msdn.microsoft.com/en-us/library/bb862025(office.12).aspx -IvanIvan Sanders My LinkedIn Profile, My Blog, @iasanders.
Free Windows Admin Tool Kit Click here and download it now
June 26th, 2010 12:07pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics