Salesforce

SDL WorldServer - When trying to create a new project in Transport, the error 'Oops! An error occurred' or a blank page appears and no project can be created

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentSDL WorldServer 11.x
Symptoms/Context
When trying to create a new project in Transport - either in the Projects page or using the Create New Project Quick Link in the Home page - the error

Oops! An error occurred

appears and no project can be created. Sometimes just a blank page appears and nothing happens. In the WorldServer environment where this happens, the WSXI (New UI) has been disabled, but the new project creation wizard is enabled.
Resolution
The workaround for this error is for the Transport User to

1- Log in to Transport WorldServer
2- go to My Account in Transport and change the option next to Create Project and also to Create Quote from Wizard:

User-added image

to One page as displayed below and then click Save:

User-added image


Permanent resolution:

To make sure that only the Legacy Project Creation Wizard is always used (for instance in environments that do not use the new User Interface), on the application server,
  1. Go to \WorldServer\tomcat\webapps\ws-legacy\WEB-INF\classes\config  
  2. Identify the file transportconfig.properties and copy it in the \WorldServer\WS_CONFIG folder 
  3. Edit the file with a text editor (like Notepad) and change this property 
enable_new_create_project_wizard=true 

to 

enable_new_create_project_wizard=false 

4. Save your change and restart WorldServer (Idiom) service 

Once you have followed the steps above, in the transport UI, a User might still have the Wizard option selected under My Account, but it will not be taken into consideration and the project will be created using the Legacy project creation wizard. The error will no longer occur.
Root Cause
The WSXI (introduced with WorldServer 11) and the legacy UI are 2 different applications, so while you have the new User Interface disabled, creating projects using the wizard link is no longer accessible because the Wizard is set to use the new UI per default. 
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by