Re: Failed to start Ignite.NET, check inner exception for details

Check the file date - the upper one is not 2.8, but some earlier version. Do you have a reason to mix NuGet with binary package? Normally they are mutually exclusive. On Thu, Apr 9, 2020 at 8:19 PM siva wrote: > now we are able to start ignite if we take Apche.Ignite.Core.dll from > downloaded i

Re: Failed to start Ignite.NET, check inner exception for details

now we are able to start ignite if we take Apche.Ignite.Core.dll from downloaded ignite binaries instead of Nuget Package. found dll size difference between from binaries and Nuget here is the image -- Sent from:

Re: Failed to start Ignite.NET, check inner exception for details

This is definitely a version mismatch between .NET and Java parts. Do you use NuGet packages together with binary release? On Wed, Apr 8, 2020 at 4:17 PM siva wrote: > Hi Thanks for the replay, > > I have already set IGNITE_HOME path pointing to 2.8 binary version, even > same exception > > > >

Re: Failed to start Ignite.NET, check inner exception for details

Hi Thanks for the replay, I have already set IGNITE_HOME path pointing to 2.8 binary version, even same exception -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to start Ignite.NET, check inner exception for details

While starting ignite server using version 2.8 in .net core getting this > exception > > * Failed to start Ignite.NET, check inner exception for details Invalid > header on deserialization. Expected: 9 but was: 33* > > Configuration setting through spring xml file. > > thi

Failed to start Ignite.NET, check inner exception for details

Hi, While starting ignite server using version 2.8 in .net core getting this exception * Failed to start Ignite.NET, check inner exception for details Invalid header on deserialization. Expected: 9 but was: 33* Configuration setting through spring xml file. this is the config file