Hi.
I'm having a problem deploying from one environment to another in Lifetime.
The error that appears to me is the following:
Object not found: /UserActions.5G+DdljroEW0sU1+Icp3rQ (relativeTo: OJ4fuJLW20WO48MQPCdR0Q)Details : System.InvalidOperationException: Object not found: /UserActions.5G+DdljroEW0sU1+Icp3rQ (relativeTo: OJ4fuJLW20WO48MQPCdR0Q) at OutSystems.HubEdition.Compiler.CompoundKeyResolver.GetObject(CompoundKey key, AbstractObject relativeTo) at OutSystems.HubEdition.Compiler.CompiledAbstractObject.RequireFullCompilationOnReferers(Boolean propagateToChildren) at OutSystems.HubEdition.Compiler.ReferenceEntity.CompiledReferenceEntity.ProcessSkipCompilationRules() at OutSystems.RuntimeCommon.CollectionsExtensions.Apply[Type](IEnumerable`1 collection, Action`1 action) at OutSystems.HubEdition.Compiler.CompilationResult.ProcessSkipCompilationRules() at OutSystems.HubEdition.Compiler.ESpace..ctor(Oml oml, CompilationContext context, Boolean loadModelOnly) at OutSystems.HubEdition.Compiler.Compiler.LoadEspace(CompilationContext context, Oml oml, Boolean allowInvalid) at OutSystems.Server.Services.Build.Application.CompilerWrappers.OutSystemsCompilerWrapper.ForImpactAnalysis(IMessageBroker messageBroker, IResourcesInManifestCacheRepository manifestCacheRepository, Byte[] oml, String outputPath, String eSpaceName, Application applicationInfo) at OutSystems.HubEdition.DeploymentController.Compiler.cs#tjvcykyk(Byte[] dk, String dl, Int32 dm, String dn, Boolean dp)
If I try to publish that module, as a hotfix, with the same content, directly from service studio there are no problems, it allows me to do it and we have said version in the target environment.
The problem is that the next time I go to promote with Lifetime to that destination environment with problems it will give me an error (I have tried it and even having the same code in both, it gives me an error).
Is it possible that something is corrupted or inconsistent in the target environment? If so, what could I do to fix it?
Thanks and best regards,
Alex.
After opening support with OS, the steps to follow are as follows.
Open a Command Prompt (Run as Administrator) and run the following command:
"<path_to_service_studio>\ServiceStudio.exe" -recover <path_to_oml_file><oml_file_name>.oml
This will open a new instance of Service Studio and start the recovery process automatically.
Hello Alejandro,
Hope you're doing well.
It is indeed a strange behavior, it seems that there might be a compilation error or probably a corrupt file when compiling / distributing the code.
My suggestion is trying the other way around. If there are no problems when you publish directly in the target environment (hotfix), try to deploy backwards.
Let's say this error happens when you deploy from DEV to QUA. Try to apply the code changes in QUA and then deploy from QUA to DEV using LifeTime (just to allign both versions and force the code compilation all over again). Then change something in DEV and deploy DEV to QUA again just to see if the error persists.
If that doesn't work, I believe you should open a support case.
Kind regards,
Rui Barradas