Error in accesing pages created in completesharepoint.

Oct 22, 2009 at 8:45 AM
Edited Oct 22, 2009 at 8:58 AM

Hi ,

      i installed completesharepoint in my WSS. i created a sharepoint site . i deployed completesharepoint.net.web in my site (http://localhost/mysite) . I make all the changes in web.config which are mentioned in developer's guide. now i can open my site by using this URL . but problem in creating aspx publising pages . whenever i create any publiding page by Site Actions->create publishing page . my page is created in site's page but when i access that page(suppose i created mypage) using url http://localhost/mysite/pages/mypage.aspx i get the following error .

Server Error in '/' Application.

Value does not fall within the expected range

Exception Details: System.ArgumentException: Value does not fall within the expected range.

Stack Trace:
[ArgumentException: Value does not fall within the expected range.]
   Microsoft.SharePoint.SPWeb.GetWebRelativeUrlFromUrl(String strUrl, Boolean includeQueryString, Boolean canonicalizeUrl) +552
   Microsoft.SharePoint.SPWeb.GetWebRelativeUrlFromUrl(String strUrl) +41
   Microsoft.SharePoint.SPWeb.GetFile(String strUrl) +42
   CompleteSharepoint.NET.Services.<>c__DisplayClass1.<GetPageLayoutContent>b__0() +153
   Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state) +70
   Microsoft.SharePoint.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2() +392
   Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode) +152
   Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param) +345
   Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode) +86
   CompleteSharepoint.NET.Services.DefaultSiteService.GetPageLayoutContent(String absolutePath) +223
   CompleteSharepoint.NET.Web.PublishingPageFile.Open() +72
   System.Web.Hosting.VirtualPathProvider.OpenFile(String virtualPath) +28
   System.Web.UI.DependencyParser.ParseFile(String physicalPath, VirtualPath virtualPath) +123
   System.Web.UI.DependencyParser.GetVirtualPathDependencies() +169
   System.Web.Compilation.TemplateControlBuildProvider.GetBuildResultVirtualPathDependencies() +36
   System.Web.Compilation.BuildManager.GetVirtualPathDependencies(String virtualPath) +68
   Microsoft.SharePoint.ApplicationRuntime.SPVirtualFile.CalculateFileDependencies(HttpContext context, SPRequestModuleData basicRequestData, ICollection& directDependencies, ICollection& childDependencies) +769
   Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.EnsureDependencies(HttpContext context, SPRequestModuleData requestData) +834
   Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.EnsureCacheKeyAndViewStateHash(HttpContext context, SPRequestModuleData requestData) +1385
   Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.GetVirtualPathProviderCacheKey(HttpContext context, SPRequestModuleData requestData) +39
   Microsoft.SharePoint.ApplicationRuntime.SPDatabaseFile.GetEffectivePageParserSettings(HttpContext context, SPRequestModuleData basicRequestData, SafeControls& safeControls, String& cacheKeyParam) +389
   Microsoft.SharePoint.ApplicationRuntime.SPVirtualFile.GetEffectivePageParserSettings(String virtualPath, SafeControls& safeControls, String& cacheKeyParam) +132
   Microsoft.SharePoint.ApplicationRuntime.SPPageParserFilter.Initialize() +140
   System.Web.UI.PageParserFilter.InitializeInternal(VirtualPath virtualPath, TemplateParser parser) +33
   System.Web.UI.PageParserFilter.Create(PagesSection pagesConfig, VirtualPath virtualPath, TemplateParser parser) +8613159
   System.Web.UI.TemplateParser.ProcessConfigSettings() +224
   System.Web.UI.TemplateControlParser.ProcessConfigSettings() +13
   System.Web.UI.PageParser.ProcessConfigSettings() +17
   System.Web.UI.TemplateParser.PrepareParse() +141
   System.Web.UI.TemplateParser.Parse() +167
   System.Web.UI.TemplateParser.Parse(ICollection referencedAssemblies, VirtualPath virtualPath) +34
   System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() +85
   System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) +62
   System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() +199
   System.Web.Compilation.BuildProvidersCompiler.PerformBuild() +42
   System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) +8729531
   System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +261
   System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +101
   System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +126
   System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +62
   System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +33
   System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +40
   System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) +160
   System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +93
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155
 

kindly look into the issue .....

 

Coordinator
Oct 22, 2009 at 9:45 AM

Mahima,

You can't install CS.NET on a sub-directory. It has to be http://localhost and not http://localhost/site.

Tommy

Oct 22, 2009 at 10:19 AM

Hi,

Thanks alot for your quick reply . But why it is so ???

i mean we are just creating a collection of site , we can create it either way (with in  http://localhost/site or http://localhost )

what is exactly causes to error .........

Coordinator
Oct 23, 2009 at 10:33 AM

Mahima,

It was by design unfortunately because a public website normally starts at the root of the domain name.

Cheers,
Tommy