Skip to main content


 

Symptoms


After upgrading from 4.6.7 to 4.6.10, I get the below error when attempting to package a solution.

SourceCode.Hosting.Exceptions.SCException: 30003 RuntimeService has encountered an error. RuntimeService has encountered an error. Object reference not set to an instance of an object.
at SourceCode.Hosting.Client.BaseAPI.BaseAPIConnection.RemoteCall(String TypeName, String MethodName, Objectt] Parameters, Booleann] NullList, MarshalMessageType CallType)
at SourceCode.Hosting.Client.BaseAPI.BaseAPI.RemoteCall(String TypeName, String MethodName, Objectt] Parameters, Booleann] NullList, MarshalMessageType CallType)
at SourceCode.Hosting.Client.BaseAPI.BaseAPI.RemoteSessionCall(String TypeName, String MethodName, Objectt] Parameters)
at SourceCode.Deployment.Management.PackageDeploymentManager.RemoteSessionCall(String TypeName, String MethodName, Objectt] Parameters)
at SourceCode.Deployment.Management.ClientSession.OnPackageItems(PackageItemOptions options)
at SourceCode.Management.Controls.AddItemCommandHandler.<>c__DisplayClass14.b__6()
at SourceCode.Management.Controls.Framework.AsyncTaskManagerService.ProcessAsyncQueue()
 

Diagnoses


Issue is pointing to custom SmartBox SmartObject. The SmartObject recently got renamed and was re-deployed via K2 for Visual Studio using PandD prior to the upgrade. Issue can be reproducible by just selecting the one SmartObject in question when creating the PandD package.
 

Resolution

Issue is resolved per suggested steps below:
i) Launch SmartForms K2Designer. Edit the SmartBox SmartObject and step through the wizards. This will ensure that the SmartObject definition file is sync-up correctly.
ii) Try to create the PandD package again.




 
Be the first to reply!

Reply