Service Builder stopped working after upgrade to 3.1.3

Mikael Karlsson
Kilo Sage

Anyone else failing to use Service Builder when installing: Service Builder 3.1.3 and DPM 6.0.8.

 

When opening a service which is operational and attempting to submit we get the error from a validation script: Status can only move forward to retiring or retired or obsolete from operational.

I suspect this is only a symptom of another issue since we also see the following in the application log when opening a service in SB:

[ASB] Error while setting draft prefix for record name: [Draft] <ServiceName>

 

There is a new feature in that version which renames the draft with a prefix, and for some reason that fails in our environments.

1 ACCEPTED SOLUTION

Mikael Karlsson
Kilo Sage

Resolved by support and development team supplying three update set patches as a workaround until a permanent fix is in the product.

View solution in original post

6 REPLIES 6

Mikael Karlsson
Kilo Sage

The development team is working on a fix, ask your support rep to look into PRB1804842 and see if it fits your symptoms.

Mikael Karlsson
Kilo Sage

Resolved by support and development team supplying three update set patches as a workaround until a permanent fix is in the product.