[OutDoc] Object reference not set to an instance of an object
Forge component by OutSystems R&D
Application Type
Traditional Web
Service Studio Version
11.11.2 (Build 43109)
Platform Version
11.7.3 (Build 7036)

I have installed the OutDoc from the forge it should be version 3.0.10 however in the description in the module it says 2.3

I face the following error when generating the doc

Object reference not set to an instance of an object.: System.NullReferenceException: Object reference not set to an instance of an object.    at ServiceStudio.CrashAPI.ExecutionExtensions.ExecuteWithSilentErrorHandling(ActionWrapper actionWrapper, String context, ExceptionType exceptionType, IExecutionContext executionContext)
at ServiceStudio.Model.AbstractObject.AssertValidReferers()
at ServiceStudio.Model.ModelExtensions.DoForSelfAndAllChildren(AbstractObject obj, Action`1 action)
at ServiceStudio.Model.AbstractObject.Delete()
at ServiceStudio.Model.AbstractEntity.DeleteEntityActionIfNeeded[ActionType]()
at ServiceStudio.Model.AbstractEntity.RefreshEntityActions()
at ServiceStudio.Model.ReferenceEntity.RefreshState(RefreshReason reason, Func`2 wasSet, Func`2 additionalDataGetter)
at ServiceStudio.Model.AbstractObject.<>c__DisplayClass297_0.<OnPropertyUpdate>b__0()
at ServiceStudio.Model.AbstractObject.InnerOnUpdate(Metadata metadata, UpdateReason reason, Metadata originalChangeMetadataForChildUpdatedReason, AbstractObject originalChangeMetadataOwnerForChildUpdatedReason, Action beforeParentNotification, Boolean ignoreChangeTracking)
at ServiceStudio.Model.AbstractObject.OnPropertyUpdate(PropertyMetadata metadata)
at ServiceStudio.Model.ReferenceEntity.SetHidden(Boolean value, SetReason reason)
at ServiceStudio.Import.ImportExtensions.RefreshStateAfterImport(ITopLevelReferenceElement self, Func`2 additionalDataGetter)
at ServiceStudio.Model.ReferenceEntity.InnerRefreshState(RefreshReason reason, Func`2 wasSet, Func`2 additionalDataGetter)
at ServiceStudio.Model.AbstractObject.RefreshState(RefreshReason reason, Func`2 wasSet, Func`2 additionalDataGetter)
at ServiceStudio.Model.AbstractType.RefreshState(RefreshReason reason, Func`2 wasSet, Func`2 additionalDataGetter)
at ServiceStudio.Model.AbstractEntity.RefreshState(RefreshReason reason, Func`2 wasSet, Func`2 additionalDataGetter)
at ServiceStudio.Model.ReferenceEntity.RefreshState(RefreshReason reason, Func`2 wasSet, Func`2 additionalDataGetter)
at ServiceStudio.Import.Importer.<>c__DisplayClass41_0.<FinalizeImportPart2>b__4(AbstractObject obj)
at ServiceStudio.Model.SSCollectionsExtensions.Apply[Type](ISSCollection`1 collection, Action`1 action)
at ServiceStudio.Import.Importer.FinalizeImportPart2(IImportTarget target, IImportAdditionalDataGetter importAdditionalDataGetter)
at ServiceStudio.Clone.ObjectCloner.RunPendingFinalizesAfterImportForSignatureGeneration(ESpace eSpace)
at ServiceStudio.Model.ESpace.SignatureManager.UpdateSignatures(IEnumerable`1 infos, Action`2 processSignature)
at ServiceStudio.Model.ESpace.SignatureManager.<>c__DisplayClass35_0.<UpdateSignatures>b__0()
at ServiceStudio.Common.Concurrency.ModelLockExtensions.<>c__DisplayClass2_0.<DoWriteOperation>b__0()
at ServiceStudio.Common.Concurrency.ModelLockExtensions.DoWriteOperation[T](IModelLock modelLock, Func`1 func)
at ServiceStudio.Model.ESpace.SignatureManager.UpdateSignatures(IEnumerable`1 keys)
at ServiceStudio.Model.ESpace.SignatureManager.<RegenerateAllSignatures>b__31_0()
at ServiceStudio.Common.Concurrency.ModelLockExtensions.<>c__DisplayClass2_0.<DoWriteOperation>b__0()
at ServiceStudio.Common.Concurrency.ModelLockExtensions.DoWriteOperation[T](IModelLock modelLock, Func`1 func)
at ServiceStudio.Model.ESpace.SignatureManager.RegenerateAllSignatures()
at ServiceStudio.Model.ESpace.Load(Stream stream, String initialLastSavePath, Boolean isUnregisteredESpace, Boolean readOnlyMode, Boolean recoverMode, ObjectKey newKeyForClone, String productKey, Nullable`1 forceModifiedFlag, IInformationForESpaceUpgrade informationForUpgrader, Predicate`1 isAvailable, Boolean skipUpgradesForForge, Nullable`1 isIsolated, Boolean needsDeterministicKeys)
at ServiceStudio.Model.ESpace.Load(Byte[] bytes, String initialLastSavePath, String productKey, Nullable`1 forceModifiedFlag, IInformationForESpaceUpgrade informationForUpgrader, Predicate`1 isAvailable, Boolean skipUpgradesForForge, Nullable`1 isIsolated)
at ServiceStudio.Model.ESpace.Load(Byte[] bytes, String productKey, IInformationForESpaceUpgrade informationForUpgrader, Predicate`1 isAvailable, Boolean skipUpgradesForForge)
at ServiceStudio.DocSaver.DocSaverWorker.GetDocumentation(Byte[] oml, String& xml, String& errorsXml)

at ssOutDoc.RssExtensionEspaceMetaModel.MssGetDocumentation(HeContext heContext, Byte[] inParamOml, String& outParamXml)
at ssOutDoc.Actions.ActionGetXML(HeContext heContext, Byte[] inParamFileContent, String& outParamXmlContent)
   at ssOutDoc.Actions.ActionDocumentation_GenerateEspaceDocumentation(HeContext heContext, Int32 inParameSpaceVersionId, String& outParamxml, String& outParamerror)

what i have tried is refresh the depencies but with no luck i still get the same error 



Hi Ammar,

  1. We were also getting the same error when launching the OutDoc component eSpace screen in our Environment.
  2. Outsystems proposed to minimize the weightage in the environment and they have reported this to OS R&D team for future improvements, so it will be included in future release notes. 
  3. In our case there was no impact in the application/Environments. Few applications document generation failed. 

Can you please let me know if this is impacting in generating the document or only an error is getting registered. 

Regards

Ajay A

it happens only when generating some modules doc while success on another

  1. This was the same case with us, publish the module from service center & try to generate the doc.
  2. Check if OutDoc needs an update from the bell icon in service studio in the top left.

Regards

Ajay A

Hi there,

May i know if there's any resolution for this issue. It happen with the latest version of outsystems and also the latest version of OutDoc. I'm having the same issue. 

I'm not sure if it's related to new catalog that we are using for our module and the global catalog for OutSystems entity like espace 

Hope that the OutSystems R&D will have some update on this issue.

Thanks,

Thang

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.