kentico 9 cmsdesk system error after admin login - kentico

This is a fun one. Just moved my build to the dev environment. I'm getting a system error when trying to access the CMS Desk. I can't see the event log to trouble shoot. How i can go about finding possible issues. I had admin access to the DEV VM, but not the SQL box.
I'm currently on hot fix 30, and my local dev is fine.
I've noticed that the Kentico CMS Health Monitor and Scheduler services didn't start. Manualy starting these gives an error.
When i attempted to login in from the VM, i get this error.
Server Error in '/' Application.
Compilation Error
Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.
Compiler Error Message: CS0433: The type 'CMSAdminControls_Basic_OrderByControl' exists in both 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\a8d48e58\742913f6\assembly\dl3\864636c6\8ed0e2be_5525d201\CMSApp.DLL' and 'c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\a8d48e58\742913f6\App_Web_orderbycontrol.ascx.cffe6b5c.9lvruqx-.dll'
Source Error:
Line 87:
Line 88:
Line 89:
Line 91:
Source File: c:\inetpub\wwwroot\Kentico9\CMS\CMSAdminControls\UI\UniGrid\Controls\AdvancedExport.ascx Line: 89

Try to clean (delete) content from that temporary folder.

Looks like Kentico was setup as a Web Site, rather than a Web Application. Just as easy to nuke, and reinstall.

Related

VS2019-project is unloaded, csproj <UseIISExpress> was changed somehow,

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.

kentico upgrade issue from version 10 to 11

I upgraded my kentico web application project from version 10 to 11 using upgrade installer and used the codeupgrade utility to detect the code issue and modify them.
compiled with
I got a message of successful upgrade.
When I accessed my website locally, got the error message below
`Server Error in '/' Application.
An item with the same key has already been added.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
Exception Details: System.ArgumentException: An item with the same key
has already been added.
Source Error:
Line 23:
Line 24: // Initialize CMS application. This method should not be
called from custom code.
Line 25: InitApplication();
Line 26: }
Line 27:
Source File: C:\compass_build\CMS\Global.asax.cs Line: 25
Could you please assist me to fix the issue, thanks
thanks kentico suppor email to point out that only one global.ascx.cs file allowed inside the project.
and my solution includes 2, so I removed one of the global.ascx.cs file.
then the issue solved.

how to debug error 500 Internal Server Error on an Azure App?

I got an "500 Internal Server Error - An error occurred while starting the application" after deploying my application: https://iidapp.azurewebsites.net/
I keep finding the following error message but I am unable to find out on msdn websites any information describing how I can specify the SAS URL
INFO: The app was working for a long period and I didn't have to set the SAS URL; I wonder why suddenly Azure is generating exceptions
INFO2: the app works perfectly on my local machine
Any help is welcomed as I couldn't find any solution by reading the related topics on stackoverflow
2017-04-05T18:51:32
System.ApplicationException: The trace listener AzureBlobTraceListener is disabled. ---> System.InvalidOperationException: The SAS URL for the cloud storage account is not specified. Use the environment variable 'DIAGNOSTICS_AZUREBLOBCONTAINERSASURL' to define it.
at Microsoft.WindowsAzure.WebSites.Diagnostics.AzureBlobTraceListener.RefreshConfig()
--- End of inner exception stack trace ---
An error was triggered by W3SVC-WP : {app name}02000780
I found out on eventid that the code 02000780 meant that a file was missing
I eventually found out that it was possible to log further information by enabling the stdoulog inside the web.config. Read When a .NET Core Azure App Service won’t start: 502.5 Process Failure
I opened the debug console and found out that a directory wasn't found https://{app_id}.scm.azurewebsites.net/DebugConsole
Voilà! I corrected the code and the app is up and running!

Server Error in '/DotNetNuke_Community' Application

I'm getting the following error when attempting to run DotNetNuke 7.1 from IIS.
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
Line 572: //first call GetProviderPath - this insures that the Database is Initialised correctly
Line 573: //and also generates the appropriate error message if it cannot be initialised correctly
Line 574: string strMessage = DataProvider.Instance().GetProviderPath();
Line 575: //get current database version from DB
Line 576: if (!strMessage.StartsWith("ERROR:"))
I've tried running it from Visual Studio 2012 after downloading and extracting the source code to a folder, then running, but I get the same error (also, VS loads about 13 instances of it's built in webserver which can't be correct).
Clearly, there is something wrong with the database. From what I've read in the past, there should have been a start up configuration page (for configuring settings the first time you run the project).
I did look at the local version of IIS (running on Windows 8) and it created the site fine there, however, for some reason the internal webserver attempts to run (and the option to run on an external IIS is greyed out).
Anyone run into this problem with DNN Community edition? I've tried running as admin and setting permissions with no luck at all.
Any way to fix this?
Ok, the key is to delete the Database.mdf file completely.
Then create a new empty database of your choice in SQL Server (2008 or greater).
Create a new user account with db_owner access (as it must be able to create tables, etc).
Change the connection strings in the release.config and development.config to connect to the database.
DELETE the web.config file.
RENAME either config file to "web.config"
Set the default project to the web project in VS
set the default page to default.aspx
Run
I made the erroneous assumption that running the app would rename the config file for me (not sure why I assumed that).
SOLVED!

classic .net app pool + iis 7.5 + compression modules

I have windows 2008 r2 installed on my server, so iis 7.5 is.
I am not able run any of the class.net applications on iis. one of the compression modules throws exception.
Detailed Error Information
Module DynamicCompressionModule
Notification SendResponse
Handler StaticFile
Error Code 0x8007007e
Requested URL http://localhost:8081/a.html
Physical Path C:\inetpub\TestWebSite\a.html
Logon Method Anonymous
Logon User Anonymous
i tried diferent logon methods, different sites even static html pages are not served. Error never changes.
sorry for poor english.
A quick bit of searching found this: http://forums.iis.net/t/1149768.aspx. Are you running a 64bit server? If so, is it possible you are (potentially inadvertently) mixing 32bit and 64bit code in the same application pool?
More information with slightly more detailed steps to resolve the problem found here: http://blogs.msdn.com/webtopics/archive/2010/03/08/troubleshooting-http-500-19-errors-in-iis-7.aspx (search down for error code 0x8007007e)
Error Message:
HTTP Error 500.19 - Internal Server
Error The requested page cannot be
accessed because the related
configuration data for the page is
invalid. Module
DynamicCompressionModule Notification
SendResponse Handler StaticFile
Error Code 0x8007007e Requested URL
http://localhost:80/ Physical Path
C:\inetpub\wwwroot Logon Method
Anonymous Logon User Anonymous
Reason:
Error Code 0x8007007e is:
ERROR_MOD_NOT_FOUND - The specified
module could not be found.
This problem occurs because the
ApplicationHost.config file or the
Web.config file references a module
that is invalid or that does not
exist. To resolve this problem: In the
ApplicationHost.config file or in the
Web.config file, locate the module
reference or the DLL reference that is
invalid, and then fix the reference.
To determine which module reference is
incorrect, enable Failed Request
Tracing, and then reproduce the
problem.
For above specific error (mentioned in
this example),
DynamicCompressionModule module is
causing the trouble. This is because
of the XPress compression scheme
module (suscomp.dll) which gets
installed with WSUS. Since Compression
schemes are defined globally and try
to load in every application Pool, it
will result in this error when 64bit
version of suscomp.dll attempts to
load in an application pool which is
running in 32bit mode.
This module entry looks like:
Hence to get rid of this problem:
Ø Remove/Disable the XPress
compression scheme from the
configuration using the command below:
%windir%\system32\inetsrv\appcmd.exe
set config
-section:system.webServer/httpCompression
/-[name='xpress']
OR
Ø Add an attribute of "precondition=
"64bitness" for this module entry so
that it loads only in 64bit
application pools
Refer this blog for more details on
Preconditions in IIS7
OR
Ø Use a 32bit version of suscomp.dll

Resources