Unable to log into Service Desk after publishing schema changes using Web Screen Painter.

Products

• CA Service Management - Service Desk Manager
• ServiceDesk
• CA Service Desk Manager

Issue/Introduction

After schema changes were made using Web Screen Painter, no one can connect to Service Desk. Looking at the STDLOG, the following errors appear:

domsrvr:wsp        5816 ERROR majic.y    4033 D:\CA\SERVIC~1\site\mods\majic\wsp.mods (38) at "MODIFY" (parse error, expecting `'}'')

domsrvr:wsp        5816 ERROR majic.y    4033 D:\CA\SERVIC~1\site\mods\majic\wsp.mods (39) at "}" (parse error)

domsrvr:wsp        5816 FATAL domsrvr.c  680 Could not parse wsp.mods

domsrvr            6100 ERROR majic.y    4033 D:\CA\SERVIC~1\site\mods\majic\wsp.mods (38) at "MODIFY" (parse error,expecting `'}')

domsrvr            6100 ERROR majic.y    4033 D:\CA\SERVIC~1\site\mods\majic\wsp.mods (39) at "}" (parse error)

domsrvr            6100 FATAL domsrvr.c  680 Could not parse wsp.mods

Environment

Service Desk Manager 12.x, 14.x and 17.x
All Supported Operating Systems

Resolution

These errors are produced by syntax errors in the wsp.mods file.

When adding new tables or columns in Web Screen Painter, the "Advanced" tab should normally be left blank. 

Entering values in the "Advanced" tab without sufficient knowledge of Service Desk can lead to Service Desk not starting after the changes are published, due to the aforementioned syntax errors in the wsp.mods file.

If this happens, simply fire up Web Screen Painter, locate the erroneous text in the "Advanced" tab and remove it.  Re-publish the schema changes and this should restore Service Desk functionality.

Additional Information

How to Modify Schema Using Web Screen Painter - https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/business-management/ca-service-management/17-2/building/building-ca-service-desk-manager/web-interface-modifications/how-to-modify-schema-using-web-screen-painter.html