extension failed with an exception, can not open APP

0
My APP can not be loaded by Studio Pro. an error message like " Extension Mendix.DataImporter.Extension failed with an exception" is reported when loading.  and same error message when open Committed Branch.  
asked
4 answers
1

The issue "Extension Mendix.DataImporter.Extension failed with an exception" pertains to the recent connector released by the platform connectors team, developed utilizing the extensibility API.

Problem is Studio Pro not being able to load the data importer extension.

Potential solutions:

  1. Review Studio Pro logs for comprehensive insights and reach out to support for assistance.

  2. Experiment with alternative versions of Studio Pro as this issue occurs due to issues with data importer extension binaries packaged within studio pro installer (refer binaries under SP folder> \modeler\extensions\dataimporter folder)

  3. While there are some makeshift solutions available, it's advisable to explore the aforementioned options initially.

 

answered
0

System.NullReferenceException: Object reference not set to an instance of an object.   at Mendix.Modeler.ExtensionLoader.ModelProxies.QualifiedNameProxy`1.ResolveIncludingExcluded(IIdentifier identifier, IHasContext context) in Mendix.Modeler.ExtensionLoader\ModelProxies\QualifiedNameProxy.cs:line 82   at Mendix.Modeler.ExtensionLoader.ModelProxies.QualifiedNameProxy`1.Resolve() in Mendix.Modeler.ExtensionLoader\ModelProxies\QualifiedNameProxy.cs:line 56   at Mendix.DataImporter.Implementations.CustomActivity.Import.ImportExcelMicroflowActionExtension.GetDefinedVariable(IImportExcelDataAction action) in /builds/platformcore/datahub-connectors/dataimporter/DataImporterAdvance/Implementations/CustomActivity/Import/ImportExcelMicroflowActionExtension.cs:line 19   at Mendix.Modeler.ExtensionLoader.MicroflowActions.ExtensionMicroflowActionBridge.GetDefinedVariable(MicroflowAction action) in Mendix.Modeler.ExtensionLoader\MicroflowActions\ExtensionMicroflowActionBridge.cs:line 149   at Mendix.Modeler.Microflows.VariableSourceUtil.GetVariableDefinition(Object obj) in Mendix.Modeler.Microflows\Common\VariableSourceUtil.cs:line 16   at Mendix.Modeler.Microflows.VariableSourceUtil.GetVariableDefinition(Object obj) in Mendix.Modeler.Microflows\Common\VariableSourceUtil.cs:line 16   at Mendix.Modeler.Microflows.ScopeAlgorithm.CalculateScopeVariables(IMicroflowObject obj, Dictionary`2 infos, IEnumerable`1 incomingScope) in Mendix.Modeler.Microflows\ScopeAlgorithm.cs:line 153   at Mendix.Modeler.Microflows.ScopeAlgorithm.CalculateScopeVariables(IMicroflowObject obj, Dictionary`2 infos, IEnumerable`1 incomingScope) in Mendix.Modeler.Microflows\ScopeAlgorithm.cs:line 165   at Mendix.Modeler.Microflows.ScopeAlgorithm.CalculateScopeVariables(IMicroflowObjectCollection collection, Dictionary`2 infos, List`1 currentScope) in Mendix.Modeler.Microflows\ScopeAlgorithm.cs:line 124   at Mendix.Modeler.Microflows.ScopeAlgorithm.CalculateScopeVariables() in Mendix.Modeler.Microflows\ScopeAlgorithm.cs:line 48   at Mendix.Modeler.Microflows.Microflow.Postprocess() in Mendix.Modeler.Microflows\Microflows\Microflow.cs:line 225   at Mendix.Modeler.Projects.Postprocessing.Postprocessor.<>c.<ApplyPostprocessRecursively>b__10_0(IPostprocess obj) in Mendix.Modeler.Core\Projects\Postprocessing\Postprocessor.cs:line 83   at Mendix.Modeler.Storage.TypeWalks.TypeWalk.CollectObjects(IStorageObject root, Func`2 shouldVisitChildren, Boolean skipExcludedObjects)+MoveNext() in Mendix.Modeler.Storage\TypeWalks\TypeWalk.cs:line 63   at System.Linq.Enumerable.CastIterator[TResult](IEnumerable source)+MoveNext()   at Mendix.Modeler.Storage.StorageUtil.ForEachStorageObjectDo[T](IStorageObject root, Func`2 work, Boolean skipExcludedObjects) in Mendix.Modeler.Storage\StorageUtil.cs:line 140   at Mendix.Modeler.Common.ResolveCache.TrackResolves(Action code) in Mendix.Modeler.Core\Common\Problems\ResolveCache.cs:line 100   at Mendix.Modeler.Projects.Postprocessing.Postprocessor.PostprocessDocument(IDocument document) in Mendix.Modeler.Core\Projects\Postprocessing\Postprocessor.cs:line 75   at Mendix.Modeler.Projects.Changes.ChangedDocumentsProcessor`1.<>c__DisplayClass6_0.<ProcessChangedDocuments>g__DoProcess|2(IDocument document) in Mendix.Modeler.Core\Projects\Changes\ChangedDocumentsProcessor.cs:line 90   at Mendix.Common.Util.EnumerableUtil.ForEach[T](IEnumerable`1 source, Action`1 action) in Mendix.Common\Util\EnumerableUtil.cs:line 51   at Mendix.Modeler.Projects.Changes.ChangedDocumentsProcessor`1.ProcessChangedDocuments(IProject project, ProjectChanges projectChanges, Func`2 processDocument) in Mendix.Modeler.Core\Projects\Changes\ChangedDocumentsProcessor.cs:line 84   at Mendix.Modeler.Common.ResolveCache.WithCache[T](IProject project, Func`1 action) in Mendix.Modeler.Core\Common\Problems\ResolveCache.cs:line 73   at Mendix.Modeler.ProtectedModules.ProtectedModulesUnlocker.ExecuteInContext[T](Boolean unlockImplementation, Func`1 code) in Mendix.Modeler.Core\ProtectedModules\ProtectedModulesUnlocker.cs:line 48   at Mendix.Modeler.Projects.Postprocessing.Postprocessor.PostprocessWithChanges(IProject project, ProjectChanges changes) in Mendix.Modeler.Core\Projects\Postprocessing\Postprocessor.cs:line 40   at Mendix.Modeler.ExtensionLoader.Build.ExtensionDeploymentWorker.CleanupAfterDeployment(IProject project) in Mendix.Modeler.ExtensionLoader\Build\ExtensionDeploymentWorker.cs:line 66   at Mendix.Modeler.ExtensionLoader.Build.ExtensionDeploymentWorker.DoWork(DeploymentPhase phase, IProject project, DeploymentSettings settings, IProgressInfo info) in Mendix.Modeler.ExtensionLoader\Build\ExtensionDeploymentWorker.cs:line 51   at Mendix.Modeler.Deployment.DeploymentProcessBuilder.ExecuteDeploymentWorkForPhase(DeploymentPhase phase, IProject project, DeploymentSettings settings, IProgressInfo info) in Mendix.Modeler.Deployment\DeploymentProcessBuilder.cs:line 184   at Mendix.Modeler.Deployment.DeploymentProcessBuilder.<>c__DisplayClass14_1.<AddFinalizeStep>b__1() in Mendix.Modeler.Deployment\DeploymentProcessBuilder.cs:line 165   at Mendix.Modeler.ProtectedModules.ProtectedModulesUnlocker.<>c__DisplayClass3_0.<Do>b__0() in Mendix.Modeler.Core\ProtectedModules\ProtectedModulesUnlocker.cs:line 22   at Mendix.Modeler.ProtectedModules.ProtectedModulesUnlocker.ExecuteInContext[T](Boolean unlockImplementation, Func`1 code) in Mendix.Modeler.Core\ProtectedModules\ProtectedModulesUnlocker.cs:line 42   at Mendix.Modeler.ProtectedModules.ProtectedModulesUnlocker.Do(Boolean unlockImplementation, Action action) in Mendix.Modeler.Core\ProtectedModules\ProtectedModulesUnlocker.cs:line 20   at Mendix.Modeler.Deployment.DeploymentProcessBuilder.<>c__DisplayClass14_0.<AddFinalizeStep>b__0(IFinalizeProgressInfo info) in Mendix.Modeler.Deployment\DeploymentProcessBuilder.cs:line 164   at Mendix.Modeler.UIFramework.Progress.ProcessRunner.RunStep(IStep step) in Mendix.Modeler.UIFramework\Progress\ProcessRunner.cs:line 163   at Mendix.Modeler.UIFramework.Progress.ProcessRunner.OnDoWork(Object sender, DoWorkEventArgs e) in Mendix.Modeler.UIFramework\Progress\ProcessRunner.cs:line 91   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)--- End of stack trace from previous location ---   at Mendix.Modeler.UIFramework.Progress.ProcessRunner.Run() in Mendix.Modeler.UIFramework\Progress\ProcessRunner.cs:line 57   at Mendix.Modeler.Deployment.Deployer.RunProcess(IProcess process, String what, Boolean isPackage) in Mendix

answered
0

It is referring to the Data Importer Module. Maybe there is a file conflict? You could check the userlib directory for outdated jar files (if you find the same file with a different version like checker-qual-2.5.2.jar and checker-qual-3.8.0.jar, you might want to remove the older version. Make sure to create a copy of the entire userlib directory before removing files so you have a backup in case you remove a file by mistake)

 

Did you use TortoiseGit to check for any errors? You could try to import (and overwrite the module).

answered
0

This issue is known issue and when SP launched Data Importer extension is not loaded. This will be fixed in SP 10.8.0 Release

answered