Error deploying PandD package to SharePoint online


Badge +4


 

Symptoms


When attempting to deploy a PandD package from development to production, we saw the following error...

Exception has been thrown by the target of an invocation.
at SourceCode.SmartObjects.Client.SmartObjectClientServer.GetSmartObjectReader(SmartObject smartObject, ExecuteListReaderOptions options, Dictionary`2and propertyReference)
at SourceCode.SmartObjects.Client.SmartObjectClientServer.ExecuteListReader(SmartObject smartObject, ExecuteListReaderOptions options)
at SourceCode.Forms.AppFramework.FormsApiToXml.ToXmlList()
at SourceCode.Forms.AppFramework.FormRuntime.SmartObjectExecution(XPathNavigator nav, Boolean outputDependencies, SmartObjectClientServer svr)
at SourceCode.Forms.AppFramework.FormRuntime.WorkXmlToApi(String xml)
at SourceCode.Forms.Runtime.AJAXCall.ProcessRequest(HttpContext context...
 

Diagnoses


This is a known issue with blackpearl 4.6.9 and has been addressed in the PandD 4.6.9.3 rollup.
 

Resolution

We applied the rollup in the "test" environment and that resolved the issue there. Next, the rollup was applied in the "development" environment and the issue was resolved there. Finally, the rollup was applied in the production environment and there were a couple of issues with the "automated installer". We applied the roll-up manually and after that, all was working as expected.

Why the "patch installer" might fail...
Normally a production environment has "stricter" security policies in place when compared to "lower environments". Looking at the installer trace, we saw now errors or warming messages.

The theory is that when applying the fix, there might have been an assembly that might not have get replaced or GAC-ed, because the user performing the install, might not have had sufficient permissions. This might have caused assemblies on the file system and the GAC to get "out of sync" and this might have been the reason the "installer" did not "drop" what it needed to. When using the patch installer, it is always a good idea to confirm that the files has been replaced on the file system and the GAC.




 

0 replies

Be the first to reply!

Reply