Object reference not set to an instance of an object when deploy project ( K2 Studio / Visual Studio)

  • 10 October 2016
  • 0 replies
  • 5 views



 

Symptoms

 


Hello, We had an abnormality on the deployment of all processes on (K2 Studio and Visual Studio) DEV environment. The deployment is not performed correctly and displays the following error: "Object reference not set to an instance of an object" (Please see PJ). The permissions have not been changed since the last deployment workflow. (Creating only an empty project with some activit?es, the workflow does not deploy).
 

 

Diagnoses

 


Bonjour, Nous avons eu une anomalie sur le d?ploiement de tout les process sur OSE "Company" (K2 Studio et sur visual Studio) environnement DEV. Le d?ploiement ne s'effectue pas correctement et affiche l'erreur suivante: "Object reference not set to an instance of an object" (Merci de voir la PJ). Les permissions n'ont pas ?t? modifi?es depuis le dernier d?ploiement du workflow. (En cr?ant uniquement un projet vide avec quelques activit?es, le workflow ne se d?ploie pas non plus). Cordialement, Nawfal
 

 

Resolution

Dear Customer, Please find below the actions made in order to fix your issue : -Reinstallation of the Framework 4.6 rather the framework 4.6.2 who was not compatible with the 4.6.11. (Framework probably deployed by their security patch as ?KB? format.) -Grant on the role ?securityadmin? re-added on the SQL database, in order to choose the repair option taken with the ?Installer?, in order to fix an issue related with 3 dll?s not properly installed -Under the Workspace the Template section using the ?Default template? was with the ?False? value rather ?True? by default. -Several Variables under the ?Field Management? was duplicated and many of them have an empty value and we renamed It in order to fix the problem. -A very strange behaviour was occurred on the development environment because no variables under the section ?Field Management? have a value. -We deleted ?Development? under the section ?Environment Management? and kept production and renamed as ?DEV?. With the query provided by OCH we noticed that the ?Workflow Management Server? have the value at false. -After the modification of this last value everything works perfectly, we?ve been able to deploy whatever project under VS and K2 Studio as before ?. (for us the problem is mainly due by a mistake by someone, who changed this value). Thanks you and best regards, Nasser

 

 



 

0 replies

Be the first to reply!

Reply