The file '/SFPageService/6665FFF2-6B04-481C-B4E5-1339DA7

Posted by Community Admin on 04-Aug-2018 13:29

The file '/SFPageService/6665FFF2-6B04-481C-B4E5-1339DA707C2D_39_Basic.aspx' does not exist.

All Replies

Posted by Community Admin on 14-Nov-2011 00:00

Hi there,

After deploying our Sitefinity 4.2.1733 to our Windows Server 2008 R2 the site doesn't load at all.

In the Sitefinity error log we getting the following error:
----------------------------------------
Timestamp: 11/14/2011 12:14:49 PM

Message: HandlingInstanceID: 9fafe06b-c014-429a-a73b-01c2061c05e4
An exception of type 'System.Web.HttpException' occurred and was caught.
------------------------------------------------------------------------
11/14/2011 14:14:49
Type : System.Web.HttpException, System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Message : The file '/SFPageService/6665FFF2-6B04-481C-B4E5-1339DA707C2D_39_Basic.aspx' does not exist.
Source : System.Web
Help link :
WebEventCode : 0
ErrorCode : -2147467259
Data : System.Collections.ListDictionaryInternal
TargetSite : System.Web.Compilation.BuildResult GetVPathBuildResultInternal(System.Web.VirtualPath, Boolean, Boolean, Boolean, Boolean, Boolean)
Stack Trace :    at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
   at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
   at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound)
   at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
   at Telerik.Sitefinity.Web.PageRouteHandler.BuildHttpHandler(RequestContext requestContext)
   at System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context)
   at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Additional Info:
MachineName : WIN-K15KR6JIU5M
TimeStamp : 11/14/2011 12:14:49 PM
FullName : Telerik.Sitefinity.Utilities, Version=4.2.1733.0, Culture=neutral, PublicKeyToken=b28c218413bdf563
AppDomainName : /LM/W3SVC/23/ROOT-1-129657444644184136
ThreadIdentity : Anonymous
WindowsIdentity : IIS APPPOOL\G.1) Avika.co.za (www)
Requested URL : http://www.avika.co.za/


Category: ErrorLog
Priority: 0
EventId: 90000
Severity: Error
Title:Enterprise Library Exception Handling
Machine: WIN-K15KR6JIU5M
App Domain: /LM/W3SVC/23/ROOT-1-129657444644184136
ProcessId: 8776
Process Name: c:\windows\system32\inetsrv\w3wp.exe
Thread Name:
Win32 ThreadId:4148
Extended Properties:
----------------------------------------

The error message itself is not useful at all and we've searched for errors related to SFPageService but nothing comes up that's of any use.

We've given Network Service, the AppPool Account, IUSr, IIS_Usr full permissions to the entire site (after adding it to app_data had no affect). Nothing.

We're not getting any closer to a solution either.

Anyone have any ideas?

Regards,
Jacques

Posted by Community Admin on 15-Nov-2011 00:00

Hi J.Hoventer,

Can you tell me what steps you followed for deploying the website? Have you tried building the solution and restarting it?

Greetings,
Victor Velev
the Telerik team

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 15-Nov-2011 00:00

Hi Victor,

Well we've managed to get the site running and it seems that the main problem was with setting the site as Precompiled.

Is there any reason why this would cause problems for Sitefinity?

Jacques

Posted by Community Admin on 16-Nov-2011 00:00

Hello J.Hoventer,

We have discussed a related issue in this topic. Please have a look at it, you may find it useful.

Greetings,
Victor Velev
the Telerik team

Do you want to have your say in the Sitefinity development roadmap? Do you want to know when a feature you requested is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items

Posted by Community Admin on 17-Nov-2011 00:00

Hi Victor,

We've managed to solve our problem by simply removing the precompile option. To have to go and mess further with the inner workings of Asp.net shouldn't be necessary and would probably increase the possibility of having more trouble further down the line.

Jacques

This thread is closed