Workflow and ServiceDesk Community

Dear All,

I am running the upgrade of Workflow 7.1 to Worklow 7.5 and getting the following error:

Database integration strategy failed due to an error: The INSERT statement conflicted with the FOREIGN KEY SAME TABLE constraint "FK_PageDefinition_PageDefinition". The conflict occurred in database "ProcessManager", table "dbo.PageDefinition", column 'PageID'.
The statement has been terminated.
System.Exception: Database Configuration could not be installed correctly. Installation cannot be continued
   at Symantec.Workflow.Installer.InstallerManager.Run()
Installation Failed.
 

I cannot delete the contents of the table as there is a Foriegn Key and copying the table has not worked.

Has anyone else had this error and does anyone know what might be the fix?

Kindest regards,

QuietLeni

Hey Quietleni,

There  is not formal upgrade path from 7.1 to 7.5.  You still have to do a migration. Let me know if you have questions about what the migration entails...

BRING,

Are you saying that the upgrade from Workflow 7.1 SP2 to Workflow 7.5 is not an over-the-top upgrade, like 7.1 SP1 to 7.1 SP2? I am not talking about Service Desk 7.1 SP2 to 7.5.

My workaround was to remove Workflow 7.1 SP2 and then install Workflow 7.5, however, I have some "issues" with the Web Services now.

BRING,

Erm, according to the WF 7.5 Release Notes, you upgrade the SMP to 7.5 and then upgrade Workflow 7.5 manually, using the installer - no migration path.

Incidentally, I have mentioned an to do with the resultant upgrade in here as well. The Workflow\Web directory had disappeared.

In your Process Manager Portal, are there by any chance subpages for the Workflow built-in pages?

toomas,

Subpages for the Workflow built-in pages? Do you mean the Solution Center? I do have the Solution Center and it shows a number of Workflows available, yes.

I believe Toomas is referring to subpages within the Process manager portal (i.e. pages that are children of other pages)

reecardo,

The Portal seems to be working normally at the moment and the pages are all appearing normally. What might I be looking for, specifically?

I used the workaround of removing Workflow 7.1 SP2 and installing afresh Workflow 7.5 in this instance. I had to copy the Workflows as well off the old version off the server.

QuietLeni

I'm planning to do an upgrade from WF 7.1 SP1 to WF 7.5 as well and was also told that this supported. The server will still have active workflows on it so were your workflows affected after upgrading to WF 7.5?

Toomas,

as I recall, we have had the same error with our workflow upgrade (Rememeber EAP Bart Asnot ? ;-) )

At that time, you added a value in one of the fields of the process manager database that did the trick.

Aryanos,

We had issues upgrading our WF 7.1 SP1 to WF 7.5. (constraint error during the upgrade) which led to a full server restore.

After the restore, we first upgraded our WF to 7.1 SP2, altered a specific field in the PM database (with many thanks to Toomas;;-) ) and than upgraded WF 7.1 to 7.5.

After the upgrade there was a restart of IIS needed to get all the workflows (Workflow, web form, webservices) working again.

Best regards,

Bart

Thanks for the feedback on the issue and I wonder what field toomas had to alter as I'll probably have to do the same.

Asnotb, I think you may be right. I had forgotten about this.

The missing item in that case was page definition for the ProcessAutomation page. In a very interesting way, the files for that page were physically present in the install folder and that page definition itself seemed to be the only thing missing.

What fixed it was simply adding the ProcessAutomation page row into PageDefinition table (I just used one from my 7.1 SP2 test box). I would actually not recommend doing that at once - the error contained reference to what exactly it was looking for and that is what I would be looking for.

Quietleni, I would definitely recommend contacting Technical Support about this. We are interested in trying to find out what makes this happen. What is the Workflow version (including build number) that you are currently on?

After Asnotb's case, I did try upgrading several times in different combinations without running into this issue - 7.1 SP1 -> 7.5; 7.1 SP1 > 7.1 SP2 > 7.5; 7.1 SP2 > 7.5.

Thanks for the information toomas, I'll try a straight upgrade from 7.1 SP1 to 7.5 first and see if I enounter any issues.