Workflow and ServiceDesk Community

Dear All,

When trying to deploy a project, I got this error message:

Publishing to 'Local SMP' (Managed Environment):

                Server 'ALTIRIS-01': Failure, Reason: A different project 'PasswordReset' version '1' is already deployed to directory 'PasswordResetting'. Please undeploy before deploying this project

Local SMP: Failure, Reason: A different project 'PasswordResetting' version '1' is already deployed to directory 'PasswordResetting'. Please undeploy before deploying this project

The timeline was this:

1) Transferred the Project to the new Production Server.

2) Had some errors with the project and fixed them on my Dev Server.

3) Deleted the existing Project on the Production Server using the information here: https://www-secure.symantec.com/connect/forums/deleting-workflow-project

4) Transferred the fixed Project to the new Production Server.

5) Checked the Project in.

6) Tried to deploy the Project and I get the error message above.

How do I fix this?

Kindest regards,

 

QuietLeni

Dear All, No comments? Would renaming the Project and re-importing it help? I don't want to do this, as I will have a different project on my Dev Box as opposed to the Production Box...! Kindest regards, QuietLeni

Hi,

 

Did you try to delete the file *.DEPLOYED inside the project directory on the production server?

 

Regards,

 

Cédric DUBIE

Besides removing the project, did you remove the top level directory (PasswordResetting) as well?

reecardo,

Yes, I deleted the PasswordResetting directory on the Production Server.

Nonos,

Yes, the project.DEPLOYED files went with the directory.

Is there something that tells Workflow that the project used to exist and I need to change it?

Kindest regards,

 

QuietLeni

Dear All,

I have turned back to this as a problem.

Can I change something about my new Workflow to allow it to be as a new workflow, rather than detecting that it has already been deployed?

Kindest regards,

 

QuietLeni

You can try 2 things:

1. New service ID

2. New Virtual Directory name on deploy

reecardo,

I tried using a different Service ID - that did not change things. I then discovered that I could change the Virtual Directory in the Deployment Wizard and that fixed things.

Thanks.

QuietLeni

Dear All, I found this out after I marked the over item as Solution... The server I was publishing to was a Managed Server and the Workflow was persisting in the Workflow Management section of the Altiris Comsole. I was then able to delete the Workflow properly in the Console. I would like to be able to see if I could try deleting my renamed Workflow and put it back to the original name and then rename it back to its original name, but it is now in Production. :-( Kindest regards, QuietLeni

I ran into this when I had some teams deploying a lot of workflows.  Deleting the published workflow from the SMP Workflow Management is the correct approach.  Renaming the virtual directory simply gives you another version... which is ok, but not what is desired in this situation.