We are in the process of moving our functioning EPiServer 10 site to Azure.
After deploying our site to Azure, we get
[InvalidOperationException: This request has probably been tampered with. Close the browser and try again.]
EPiServer.Framework.Web.AspNetAntiForgery.ThrowForgeryException() +263
when edit interface is loaded.
Error message:
An unhandled error has occured in a background request.
Unable to load /EPiServer/cms/Stores/notification/ status: 500
The page may not function properly unless it's reloaded. Press the button below to reload the page now.
Screen shot of error message
The site seems to be working 'ok' in spite of error message.
If browser is reloaded, the same error message is shown.
We are running: EPiServer 10.5
Check this configuration setting:
<system.web><httpCookies requireSSL="true" /></system.web>
If you are using http, it should say "false".
Related
My web app has a service worker that was working fine before I added integration with Cloudfront CDN.
I'm registering the service worker on the client like so:
navigator.serviceWorker
.register('https://www.my-domain-name.com/sw.js')
.then(() => console.info('service worker registered.'))
.catch(error => {
console.log('Error registering serviceWorker: ', error)
})
I get this in the client console logs:
And Lighthouse is telling me this:
No matching service worker detected. You may need to reload the page,
or check that the scope of the service worker for the current page
encloses the scope and start URL from the manifest.
I've tried multiple URLs when registering the service worker, including:
"/sw.js"
"https://www.my-domain-name.com/sw.js"
"https://###.cloudfront.net/sw.js"
...but so far none have worked.
What am I missing?
UPDATES
I've learned a lot more but still have questions:
I got a great answer from
#JeffPosnick to my related SO post here. That explained the errors.
The URL for "failed to fetch" was the URL specified in my manifest "start_url". But I'm still getting a fetch error here, even outside of Lighthouse testing. Anybody know why?
I unchecked the Lighthouse "Clear Storage" checkbox. Now Lighthouse is saying my service worker is working.
Theory: when Lighthouse clears storage it blows away the service worker, explaining why I get a failing PWA score from Lighthouse when "Clear Storage" is checked. Is this theory correct?
Okay, I finally got this all working. In addition to the things I posted in the update to the original post, I also had to find a service worker that would work with React.
I went with this one.
Now if the network is offline, and I reload the page, I still see my React home page. Nice!
I had a problem and dell premium support ran some kind of upgrade or re-install of windows 10 while keeping my files in tack.
The next day, I was working on my MVC project in VS and it loaded ok and debugging got my application to the login page, which means it had to successfully read the Entity Framework Context with LINQ type stuff, and all of a sudden my project started having these errors about reading Entity Framework Context, but only in one method.
Then things got worse, I first tried to close VS and reopen VS. But this time, it said my project had been unloaded. I tried the option to reload the project, but now I was getting errors about "the operation could not be completed. the system cannot find the path specified" and errors having to do with not being able to find the current file highlighted at the top of the VS editor.
After looking up the unload issues in forums, I saw a suggestion to call up my Mbsa.csproj and change to false and to True. Then my project loaded ok - but why did this change? it was always false in my previous backups.
Then , when trying to run my project with VS Debugging, I started getting connection messages like these:
1 - C:\MBSSys\Mbsa\Mbsa 2020\Mbsa.csproj : error : The Web Application Project Mbsa is configured to use IIS. The Web server 'http://localhost:51700/' could not be found.
2 -The connection to 'localhost' failed.
Error: ConnectionRefused (0x274d).
System.Net.Sockets.SocketException No connection could be made because the target machine actively refused it 127.0.0.1:51712
3 - HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Detailed Error Information:
Module IIS Web Core
Notification BeginRequest
Handler Not yet determined
Error Code 0x80070021
Config Error This configuration section cannot be used at this path. This happens when the section is locked at a parent level. Locking is either by default (overrideModeDefault="Deny"), or set explicitly by a location tag with overrideMode="Deny" or the legacy allowOverride="false".
Config File \?\D:\MBSSys\Mbsa\Mbsa 2020\web.config
Requested URL http://localhost:51700/
Physical Path D:\MBSSys\Mbsa\Mbsa 2020
Logon Method Not yet determined
Logon User Not yet determined
Config Source:
163: <validation validateIntegratedModeConfiguration="false" />
164: <handlers>
165: <remove name="ExtensionlessUrlHandler-ISAPI-4.0_32bit" />
4 - Error message:
Server Error in Application "application name"
HTTP Error 500.19 – Internal Server Error
HRESULT: 0x80070021
Description of HRESULT
The requested page cannot be accessed because the related configuration data for the page is invalid.
Cause for HResult code 0x80070021
This problem can occur when the specified portion of the IIS configuration file is locked at a higher configuration level.
Resolution for HResult code 0x80070021
To resolve this problem, unlock the specified section, or do not use it at that level. For more information on configuration locking, see How to Use Locking in IIS 7.0 Configuration.
So I am wondering if anyone else has faced this particular issue,
or, if anyone can give me any appreciated advice here.
Thanks for your time and advice. If you need more clues, just ask.
The seems to happen after installing KB4568831.
https://superuser.com/questions/1575295/windows-updates-kb4568831-kb4562899-break-all-net-applications-hosted-in-iis
I could get rid of the 500.19 errors by manually re-installing some optional windows features that the update apparently removes (see below), but after I got auth-related errors instead. In the end I rolled back KB4568831 to resolve the issue for the time being. Hopefully this gets fixed soon.
I'm getting this error message
"Internal : AMI error occurred in WaitStart Stage 'Wait4' on page 'Navigate menu' - Not Connected" in relation to trying to perform the Blueprism sample project. (still a rookie, so please be gentle)
I have included an "attached action" on the business object page. The weird thing is when the process is ran only through Object it works fine. But when I try to connect the different actions in the process studio the error occurs after a couple of actions.
Launch works fine
Log-in works fine
Navigate (finding that menu seems not to work) When I spy nothing seems to be wrong.
So dear experts - where do I fail?
Error
The reason it fails for you is because you have the decision arrows switched. You should attach if you are not connected.
In the Wait Stage, Probably you are looking for an Element as Check Exists. Change it to Parent Document Loaded. It should work fine. Thank you
I'm following the guide at https://learn.microsoft.com/en-us/azure/app-service-mobile/app-service-mobile-xamarin-android-get-started-push (as well as the original Xamarin one that this appears to have cribbed from), but I'm running into a problem registering my client.
I am successfully logging a user in prior to setting up the push notification service.
Both GcmClient.CheckDevice(...) and GcmClient.CheckManifest(...) succeed, and my PushHandlerService is being called.
Push.RegisterAsync(...) in my PushHandlerService is throwing a MobileServiceInvalidOperationException because it received an HTTP 500 Internal Server Error from the service.
Looking at FREB logs, it appears that the "error" is actually supposed to be a success, and interestingly is somehow related to the EasyAuthModule:
NOTIFY_MODULE_COMPLETION ModuleName="EasyAuthModule_64bit", Notification="AUTHENTICATE_REQUEST", fIsPostNotificationEvent="true", CompletionBytes="297", ErrorCode="The operation completed successfully.
(0x0)" 05:51:01.092
Module_set_response_error_status
Warning ModuleName="EasyAuthModule_64bit", Notification="AUTHENTICATE_REQUEST", HttpStatus="500", HttpReason="Internal Server Error", HttpSubStatus="79", ErrorCode="Unspecified error
(0x80004005)", ConfigExceptionInfo="" 05:51:01.092
NOTIFY_MODULE_COMPLETION ModuleName="EasyAuthModule_64bit", Notification="AUTHENTICATE_REQUEST", fIsPostNotificationEvent="true", CompletionBytes="0", ErrorCode="The operation completed successfully.
(0x0)" 05:51:01.092
I take it the error is happening when you call client.GetPush().RegisterAsync()? This is currently an issue and we are deploying a fix on the Azure side to fix this. In the interim, you can see the fix for this here: https://adrianhall.github.io/develop-mobile-apps-with-csharp-and-azure/chapter5/android/
I am getting following error when I use pagination of view.
Unable to render the data. If the problem persists, contact your web
server administrator.Correlation
ID:c64a4e9d-64d2-3009-f658-7f1c8b0faebc
When I checked the Logs from ULSViewer I got these errors messages
Error while executing web part: System.ArgumentException: The
specified view is invalid. at
Microsoft.SharePoint.SPViewCollection.get_Item(Guid guid) at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.get_View()
at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.RenderListView()
at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.Execute(String
strCmd) at
Microsoft.SharePoint.ApplicationPages.InplaceViewEditor.OnLoad(EventArgs
e)
Forced due to logging gap, cached # 12/24/2015 10:59:32.88, Original
Level: Verbose] No data was found on the incoming client request
Proxy response returned error: 'The remote server returned an error:
(601).'
Could you please check and let me know what is the issue? I am not able to resolve it.
Thanks in advance.
Best Regards,
Manoj.
Have you added the custom web parts or add custom code?
For troubleshooting the issue, you could check things below:
Create a new list view to check if the same issue will occur.
Do an IIS reset to check if it can work.