Salesforce

SDL WorldServer: After an SDL WorldServer upgrade, reference files/project attributes are no longer visible in active projects created before the upgrade

« Go Back

Information

 
Article TypeSolution Article
Scope/EnvironmentSDL WorldServer
Symptoms/Context
After a WorldServer upgrade and/or a migration to a new server, reference files/project attributes are no longer visible in active projects created before the upgrade. You might see these errors:

User-added image
Resolution
If the location of the Attributes folder has been changed and the folder has been moved to the new location, the absolute path must be changed in the Database as well

This is the SQL query to make the relevant change (oldpath and newpath need to be replaced with the actual values):

UPDATE attributeObjValues 
SET attributeObjValues.value = replace(attributeObjValues.value, 
'oldpath\attributes\', 
'newpath\attributes\') 
WHERE attributeId IN 

SELECT attributeId 
FROM attributes 
WHERE type IN (8,10) 

AND value LIKE 'oldpath\attributes\%'; 


If you need to find the value for [oldpath] and [newpath] in the Database, run these queries: 

SELECT * 
FROM attributeObjValues where value LIKE '%temp\attributes%' 

SELECT * 
FROM attributeObjValues where value LIKE '%\WorldServer\Attachment_Attributes\%' 

In case you have migrated from an AWS environment to a Windows server environment, you will neeed to adapt the Unix folder directory path to the Windows folder directory path:


UPDATE attributeObjValues
SET value = REPLACE(value , '/', '\')
WHERE value LIKE ('/worldserver/attributes%');


UPDATE attributeObjValues
SET value = REPLACE(value , '\worldserver\', 'W:\WorldServer\')
WHERE value LIKE ('\worldserver\attributes%');
Root Cause
The Attributes folder on the new server is on a different location than before the upgrade. If the location of the Attributes folder has been changed and the folder has been moved to the new location, projects created before the upgrade will still refer to the previous path and cannot find the reference file.
Reference
Attachment 1 
Attachment 2 
Attachment 3 
Attachment 4 
Attachment 5 

Powered by