.NET Runtime version 4.0.30319.0 - Loading profiler failed.
COR_ENABLE_PROFILING was set properly, but COR_PROFILER was not.
COR_PROFILER must be set to the CLSID of the profiler to load. Process
ID (decimal): 2968. Message ID: [0x2500].
Related
I'm using Apache Ignite entity framework Nuget as a second level cache in an ApsNetCore 2.0 web application under IIS(as reverse proxy).
On my development machine (VS2017 Windows 8.1) everything works well. Wen i deploy to WindowsServer 2012 the Ignite crash at startup with :
An error occurred while starting the application.
IgniteException: Failed to load jvm.dll (Please specify IgniteConfiguration.JvmDllPath or JAVA_HOME.)
Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(string configJvmDllPath, ILogger log)
TargetInvocationException: Exception has been thrown by the target of an invocation.
System.RuntimeTypeHandle.CreateInstance(RuntimeType type, bool publicOnly, bool noCheck, ref bool canBeCached, ref RuntimeMethodHandleInternal ctor, ref bool bNeedSecurityCheck)
IgniteException: Failed to load jvm.dll (Please specify IgniteConfiguration.JvmDllPath or JAVA_HOME.)
Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(string configJvmDllPath, ILogger log)
Apache.Ignite.Core.Ignition.Start(IgniteConfiguration cfg)
Apache.Ignite.EntityFramework.IgniteDbConfiguration.GetOrStartIgnite(IgniteConfiguration cfg)
Apache.Ignite.EntityFramework.IgniteDbConfiguration..ctor()
I checked and re-chewed, installed the JDK , correct system variables....everything. The error don't goes away. What is interesting is the application run ok as console. When it runs under IIS(reverse proxy) it crashes at startup with the above error.
Any suggestions ?
Thank you
I managed to start the website. How ? Only with JDK 11 and explicit path to jvm.dll on app.config file:
If is not explicit in config then crashes.
The JAVA_HOME from system variable is correct set. Also the Path variable is
%JAVA_HOME%;%JAVA_HOME%\bin;%JAVA_HOME%\bin\server;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0;C:\Program Files\Microsoft\Web Platform Installer;C:\Program Files\dotnet;C:\Program Files (x86)\dotnet;C:\ProgramData\chocolatey\bin;C:\Program Files\Memurai;C:\Program Files\Java\jdk-15.0.1\bin\
Maybe is a conflict with C:\Program Files\Java\jdk-15.0.1\bin\ ? It carsh with jvm 15. But it works with jvm 11
Looks like the IIS worker process is running in 32-bit mode, so Ignite looks for a 32-bit JDK, which is not present.
And the console app runs in 64-bit mode, using 64-bit JDK, so it works.
Please check the app pool settings in IIS Manager -> Application Pools -> select the app pool you want and -> Advanced Settings.
Additionally, you can enable detailed logging to a file (since you can't see console logs in IIS) - Ignite logs all attempts to resolve the JDK path. For example, with Apache.Ignite.NLog package:
var nlogConfig = new LoggingConfiguration();
var fileTarget = new FileTarget
{
FileName = "/home/pavel/w/ignite_nlog.log"
};
nlogConfig.AddTarget("logfile", fileTarget);
nlogConfig.LoggingRules.Add(new LoggingRule("*", LogLevel.Trace, fileTarget));
LogManager.Configuration = nlogConfig;
var igniteConfig = new IgniteConfiguration
{
Logger = new IgniteNLogLogger()
};
Ignition.Start(igniteConfig);
I've checked the suggested points by Pavel Tupitsyn:
App pool aplication is 64bits (emable 32bits=false)
I've installed apache.Ignite.NLog
I'tested it on my machine and it logs well all java resolves.
I've deployed to windows server 2012 and under IIS i'm getting 'Process Failure'.
The log file looks like:
2020-12-07 19:39:38.3304|DEBUG||Starting Ignite.NET 2.9.0.50002
2020-12-07 19:39:38.3834|WARN||GC server mode is not enabled, this could lead to less than optimal performance on multi-core machines (to enable see http://msdn.microsoft.com/en-us/library/ms229357(v=vs.110).aspx).
2020-12-07 19:39:46.2534|DEBUG||Starting Ignite.NET 2.9.0.50002
so...just a warning (present on my machine too).
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info:
Apache.Ignite.Core.Common.IgniteException
at Apache.Ignite.Core.Impl.Unmanaged.Jni.JvmDll.Load(System.String, Apache.Ignite.Core.Log.ILogger)
at Apache.Ignite.Core.Ignition.Start(Apache.Ignite.Core.IgniteConfiguration)
at Nop.Web.Program.Main(System.String[])
well...adding apache.ingite.nlog throws PROCESS FAILURE
Hosting is virtual machine with Windows Server 2012 64bits
Any other ideas please....
The upgrade procedure is pretty simple and well documented. I have been upgrading jasperreports server since version 4 always using the same procedure (buildomatic).
Now, in 7.5 version I get
java.lang.RuntimeException: KeystoreManager was never initialized or
there are errors while instantiating the instance.
Failed to instantiate
[com.jaspersoft.jasperserver.crypto.KeystoreManager]: Please make sure
that create-keystore was executed;
Error creating bean with name 'keystoreManager': Invocation of init
method failed;
Error creating bean with name 'passwordEncoder': Unsatisfied
dependency expressed through field 'keystoreManager';
The keystore is in /root folder, as it should.
Have you tried the process mentioned in this link https://community.jaspersoft.com/wiki/encryption-jasperreports-server-75
"If the JasperReports Server cannot find the keystore files - maybe because of permissions as noted above, you will get an exception on server start like:
Failed to instantiate [com.jaspersoft.jasperserver.crypto.KeystoreManager]: Please make sure that create-keystore was executed; nested exception is java.lang.RuntimeException: KeystoreManager was never initialized or there are errors while instantiating the instance.
To fix this, you need to move the keystore files into a directory that is accessible by the user running the web app process. See Updating keystore files below."
I'm using Unity 2017.3.03f free personal edition, I've an application in unity that works normally in desktop and android platforms. However, When it's built for WebGL release (unchecked "development build" option") it gives this error in browser during loading splash screen:
> An error occurred running the Unity content on this page. See your browser JavaScript console for more info. The error was:
uncaught exception: abort(-1) at jsStackTrace (webgl-11B.asm.framework.unityweb:2:27460)
stackTrace (webgl-11B.asm.framework.unityweb:2:27631)
abort (webgl-11B.asm.framework.unityweb:4:33732)
_il2cpp_gc_disable (webgl-11B.asm.framework.unityweb:2:204426)
scripting_gc_disable() [vNc] (webgl-11B.asm.code.unityweb:10:1)
_main [eNc] (webgl-11B.asm.code.unityweb:10:1)
callMain (webgl-11B.asm.framework.unityweb:4:32097)
doRun (webgl-11B.asm.framework.unityweb:4:32800)
_String_Join_m2050845953 [run] (webgl-11B.asm.framework.unityweb:4:32986)
runCaller (webgl-11B.asm.framework.unityweb:4:31614)
removeRunDependency (webgl-11B.asm.framework.unityweb:2:34407)
processDataJob#file:.../Build/UnityLoader.js:1:17079
I've tried to enable the development option and apply the steps of this article:
https://community.gamedev.tv/t/webgl-debugging/54948
to enable debugging symbols and disable stripping code engine to see the errors in browser console. But the Development version works without error, but when I return to release build "unchecking the development option" again, the same error appears.
and the log of browser console contains the following message:
> IndexedDB is not available. Data will not persist in cache and PlayerPrefs will not be saved.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:124
unreachable code after return statement[Learn More]
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:4519
missing function: il2cpp_gc_disable
UnityLoader.js:1:8039
-1
UnityLoader.js:1:8002
-1
UnityLoader.js:1:8039
Use of the motion sensor is deprecated.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:54097
Use of the orientation sensor is deprecated.
a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:54097
uncaught exception: abort(-1) at jsStackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27460
stackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27631
abort#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:33732
_il2cpp_gc_disable#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:204426
vNc#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:10:1
eNc#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:10:1
callMain#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32097
doRun#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32800
run#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:32986
runCaller#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:31614
removeRunDependency#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:34407
processDataJob.../UnityLoader.js:1:17079
If this abort() is unexpected, build with -s ASSERTIONS=1 which can give more information.
154
UnityLoader.js:1:8002
154
UnityLoader.js:1:8039
uncaught exception: abort(154) at jsStackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27460
stackTrace#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:27631
abort#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:4:33732
Vxq#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:32:1
y7c#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:23:1
ynq#blob:null/036e0461-a7f5-4bf6-9bcd-65ad983ad95c:32:1
handlerFunc#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:57395
jsEventHandler#blob:null/a2ab4d2b-6621-459b-b13f-f9b816ecb2f8:2:53935
why does this error happen? is it because of using unity free edition, or because the application reads some text file from Resources folder at loading?
thanks in advance.
I am getting the error below when I attempt to run an asp.net 2.0 on Windows 8.1 (I think this is IIS 8.5)
Any ideas how to resolve this issue?
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
0x80070032
Config Error
The configuration section 'ACI.Template3' cannot be read because it is missing a section declaration
Config File
\\?\C:\inetpub\wwwroot\ACIWebSite\web.config
Requested URL
http://localhost:80/ACIWebSite
Physical Path
C:\inetpub\wwwroot\ACIWebSite
Logon Method
Not yet determined
Logon User
Not yet determined
Config Source:
180: -->
181: <ACI.Template3>
182: <Common section="Production"/>
The issue occurs when executing EF 6.1.2 code first migrations in an Azure Web Role (WS 2012 R2). The same migrations run fine locally, even if I point the connection string to the (Azure) Sql Database.
The StackOverflowException is thrown by Entity Framework code, and the first line of ANY of my migrations doesn´t even get hit.
I have tried running the migrations in three different ways:
DbMigrator migrator = new DbMigrator(configuration);
migrator.Update(); // Here the exception is thrown
second:
DbMigrator migrator = new DbMigrator(configuration);
pendingMigrations = migrator.GetPendingMigrations().ToList();
foreach (string pendingMigration in pendingMigrations)
{
migrator.Update(pendingMigration); // Here the exception is thrown
}
and using web.config:
<contexts>
<context type="Superb.WorkNextDoor.EFRepository.Context.WndDbContext, Superb.WorkNextDoor.EFRepository, Version=1.0.0.0, Culture=neutral">
<databaseInitializer type="System.Data.Entity.MigrateDatabaseToLatestVersion`2[[Superb.WorkNextDoor.EFRepository.Context.WndDbContext, Superb.WorkNextDoor.EFRepository], [Superb.WorkNextDoor.EFRepository.Migrations.Migrations.WndDbMigrationsConfiguration, Superb.WorkNextDoor.EFRepository.Migrations]], EntityFramework">
</databaseInitializer>
</context>
</contexts>
I see the StackOverflowException in Visual Studio when I´m remote debugging the web role. An error is recorded in windows event log of the web role (log info at the bottom of this post).
I have two migrations. I have tried running the first one from PMC and the second from the web role but no luck.
I have tried installing .Net 4.5.2 on the server, changing the VM size from XS to S and downgrading EF to version 6.1.1. Nothing worked. Also, I tried downloading the folder "E:\sites\0" from the web role to my local computer, installed the app on IIS and attached my VS Debugger and it doesn't throw that exception. There has got to be something different between my Windows 8.1 and that Windows Server 2012 R2.
I have spent a lot of time trying different things but I don´t want to give up on this and have to execute my migrations from package manager console.
Log Name: Application Source: Application Error Date:
1/11/2015 3:21:42 AM Event ID: 1000 Task Category: (100) Level:
Error Keywords: Classic User: N/A Computer:
RD0003FF508F5B Description: Faulting application name: w3wp.exe,
version: 8.5.9600.16384, time stamp: 0x5215df96 Faulting module name:
clr.dll, version: 4.0.30319.34014, time stamp: 0x52e0b86c Exception
code: 0xc00000fd Fault offset: 0x0000000000195499 Faulting process id:
0xc60 Faulting application start time: 0x01d02d4d77fdfb93 Faulting
application path: d:\windows\system32\inetsrv\w3wp.exe Faulting module
path: D:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report
Id: f5e4d6dc-9940-11e4-80bd-0003ff508f5b Faulting package full name:
Faulting package-relative application ID: Event Xml:
1000
2
100
0x80000000000000
467
Application
RD0003FF508F5B
w3wp.exe
8.5.9600.16384
5215df96
clr.dll
4.0.30319.34014
52e0b86c
c00000fd
0000000000195499
c60
01d02d4d77fdfb93
d:\windows\system32\inetsrv\w3wp.exe
D:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
f5e4d6dc-9940-11e4-80bd-0003ff508f5b
Easy steps to reproduce this error:
Download this sample project: http://www.asp.net/mvc/overview/getting-started/getting-started-with-ef-using-mvc/migrations-and-deployment-with-the-entity-framework-in-an-asp-net-mvc-application
Add a CloudServiceProject to the solution and add the web project as a web role
Publish it to azure
Browse the web site and go to students tab (this hits the database and the initializer tries to execute the migrations).
Happens the same.
This is identified as a bug in Microsoft Visual Studio 2013 Update 4. As a temporary work around disable "Lazy Initialization" under IntelliTrace Settings -> IntelliTrace Events. We are investigating fixing this bug in a future update for Visual Studio 2013.
The responsible for the StackOverflowException turned out to be IntelliTrace. I don't know the root cause of the issue between IntelliTrace and Code First Migrations that cause this behavior but when I downloaded the IntelliTrace logs I could see a lot of Sql exceptions:
I have already lost a lot of time with this so I won't investigate it further. The easiest workaround for me now is just disable IntelliTrace before deploying my Web Roles:
If somebody is curious, here are the IntelliTrace logs.
I hope this helps someone else solve such a problem without losing as much time as I did.