Mar 13, 2022

Just a few years ago, for the 2018 model year to be more precise, Mitsubishi introduced a new compact crossover utility vehicle to the world. Sliding into the lineup between the Outlander and Outlander Sport, this two-row compact crossover has certainly been turning heads since its introduction. For the new model year, the 2022 Mitsubishi Eclipse Cross has received its first mid-generation facelift, with significant changes coming to the inside and outside of the vehicle’s design, plus plenty of other exciting updates and enhancements.

[ SHOP NOW: Find Your New Mitsubishi Eclipse Cross Today! ]

What’s changed with the design of the 2022 Eclipse Cross?

2022 Mitsubishi Eclipse Cross Exterior Driver Side Rear Angle
2022 Mitsubishi Eclipse Cross Interior Cabin Rear Seating

Some exciting and pretty extensive changes have come to the all-new 2022 Mitsubishi Eclipse Cross as far as design is concerned. So much has changed that the vehicle is actually 5 inches longer than previous iterations, now with a total overall length of 178.9 in. Other exterior changes include a new bumper, the updated Dynamic Shield grille, new lighting, a redesigned rear hatch and window, plus more.

Of course, the overall length change affected the interior as well, increasing the vehicle’s cargo capacity up to 23.4 cubic feet or 50.1 cu. ft. with the rear seats folded. Other interior changes include a new light gray option for the leather seating that features contrast stitching for the first time, plus matching accents throughout the interior, among other updates.

Are there any new features and technologies?

Perhaps the most notable change in this regard comes in the form of a completely redesigned infotainment system, which now includes an 8” Smartphone-link Display Audio screen. New embedded navigation has been added to the system as well. The technology is called what3words and it is a global addressing system that should revolutionize the navigation experience. This marks an industry-first inclusion for the technology.

To find out even more about the 2022 Mitsubishi Eclipse Cross, don’t hesitate to get in touch with us right here at San Jose Mitsubishi today. We’d be happy to fill you in on any details you’re interested in, just give us a call at the sales desk.

FluentNHibernate.Cfg.FluentConfigurationException: An invalid or incomplete configuration was used while creating a SessionFactory. Check PotentialReasons collection, and InnerException for more detail. ---> Microsoft.Data.SqlClient.SqlException (0x80131904): Cannot open database "dealeron" requested by the login. The login failed. Login failed for user 'default'. at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.SqlClient.ConnectionPool.WaitHandleDbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 taskCompletionSource, DbConnectionOptions userOptions, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection) at Microsoft.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at Microsoft.Data.ProviderBase.DbConnectionClosed.TryOpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions) at Microsoft.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry, SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open(SqlConnectionOverrides overrides) at Microsoft.Data.SqlClient.SqlConnection.Open() at NHibernate.Connection.DriverConnectionProvider.GetConnection(String connectionString) at NHibernate.Connection.ConnectionProvider.GetConnection() at NHibernate.Tool.hbm2ddl.SuppliedConnectionProviderConnectionHelper.Prepare() at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.GetReservedWords(Dialect dialect, IConnectionHelper connectionHelper) at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.UpdateDialectKeywords(Dialect dialect, IConnectionHelper connectionHelper) at NHibernate.Tool.hbm2ddl.SchemaMetadataUpdater.Update(ISessionFactoryImplementor sessionFactory) at NHibernate.Impl.SessionFactoryImpl..ctor(Configuration cfg, IMapping mapping, Settings settings, EventListeners listeners) at NHibernate.Cfg.Configuration.BuildSessionFactory() at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory() ClientConnectionId:f5dac539-b1c9-4f0c-888f-daf04accf3bf Error Number:4060,State:1,Class:11 --- End of inner exception stack trace --- at FluentNHibernate.Cfg.FluentConfiguration.BuildSessionFactory() at SITESAA.Infrastructure.DataLayer.Contexts.DatabaseContext.LoadSessionFactory() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.DataLayer/Contexts/DatabaseContext.cs:line 37 at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode) --- End of stack trace from previous location --- at System.Lazy`1.CreateValue() at SITESAA.Infrastructure.DataLayer.Repositories.DealerHeaderRepository.GetDealerIdByHost(String hostname) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.DataLayer/Repositories/DealerHeaderRepository.cs:line 10 at SITESAA.Infrastructure.Services.Caching.Providers.RedisCacheProvider.<>c__DisplayClass21_0`1.b__0() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/RedisCacheProvider.cs:line 81 at SITESAA.Infrastructure.Services.Caching.Providers.RedisCacheProvider.Cached[T](String key, Int32 expirationInMinutes, Func`1 functionWithPayloadWhichWillBeCached, CachingType cachingType) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/RedisCacheProvider.cs:line 81 at SITESAA.Infrastructure.Services.Caching.Providers.MemoryCacheProvider.<>c__DisplayClass13_0`1.b__0() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/MemoryCacheProvider.cs:line 85 at SITESAA.Core.Helpers.Timer.Time(Action functionToBeTimed) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Core.Helpers/Timer.cs:line 21 at SITESAA.Infrastructure.Services.Caching.Providers.MemoryCacheProvider.Cached[T](String key, Int32 expirationInMinutes, Func`1 functionWithPayloadWhichWillBeCached, CachingType cachingType) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Infrastructure.Services/Caching/Providers/MemoryCacheProvider.cs:line 84 at SITESAA.Core.DomainServices.Caching.Providers.CacheProviderBase.Cached[T](String key, Func`1 functionWithPayloadWhichWillBeCached) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Core.DomainServices/Caching/Providers/CacheProviderBase.cs:line 37 at SITESAA.Presentation.Infra.WebRequestService.GetHostDealerId(String hostName) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Presentation.Infra/WebRequestService.cs:line 412 at SITESAA.Presentation.Infra.WebRequestService.GetDealerId() in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Presentation.Infra/WebRequestService.cs:line 192 at SITESAA.Module.CompositionRoot.ApplicationServices.<>c.b__4_0(IServiceProvider sp) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Module.CompositionRoot/ApplicationServices.cs:line 109 at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at ResolveService(ILEmitResolverBuilderRuntimeContext, ServiceProviderEngineScope) at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType) at lambda_method14(Closure, Object, HttpContext, IServiceProvider) at SITESAA.Presentation.Infra.Middleware.StaticDependencyInjectionShimMiddleware.InvokeAsync(HttpContext context, IDealerService dealerService, IDealerAddressService dealerAddressService, IDealerOrganizationService dealerOrganizationService, ILocationService locationService, ICustomizationService customizationService, IOemProgramService oemProgramService, IPrivacySettingsService privacySettingsService, IWebRequestService webRequestService, PlatformOptions platformOptions, IVehicleRefService vehicleRefService, CacheOptions cacheOptions, MemoryCacheProviderBase memoryCacheProvider, ICacheProvider cacheProvider, IConnectionMultiplexer connectionMultiplexer, ILoadDealerService loadDealerService, IRelayControl relayControl, IDealerFeatureRingProvider dealerFeatureRingProvider) in /home/ado-agent/agent/_work/3/s/SITESAA/Source/SITESAA.Presentation.Infra/Middleware/StaticDependencyInjectionShimMiddleware.cs:line 67 at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddlewareImpl.Invoke(HttpContext context) HEADERS ======= Accept: */* Host: prod-web-5.ashburn.edealertools.com User-Agent: Blog Loader X-Dealer-Hostname: prod-web-5.ashburn.edealertools.com