ePO 5.10 Cumulative Update 15 fails with the RequestError: The multi-part identifier "pf.name" could not be bound
Last Modified: 2023-02-22 05:55:44 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
After December 1, 2024, please log in to the Thrive Portal for support, knowledge articles, tools, and downloads. For information about using the Thrive Portal, view the Trellix Thrive Portal User Guide.
ePO 5.10 Cumulative Update 15 fails with the RequestError: The multi-part identifier "pf.name" could not be bound
Technical Articles ID:
KB96323
Last Modified: 2023-02-22 05:55:44 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.10 Update 15
Problem
An upgrade from ePO 5.10 Update 9 to ePO 5.10 Update 15 fails. The errors below are recorded in the 2022-12-09T13:26:39.242Z - error: Error executing script file 5_ePO_Proc.sql 2022-12-09T13:26:39.242Z - info: SQL script execution failed 2022-12-09T13:26:39.242Z - info: Add update with id CU-15 to failed update list 2022-12-09T13:26:39.242Z - info: Total files processed : 633 success : 45 failure : 1 execution failed with error : RequestError: Invalid object name 'SYS.PROCEDURES'. 2022-12-09T13:28:56.423Z - error: Error executing script file 5_ePO_Proc.sql 2022-12-09T13:28:56.423Z - info: Rollback SQL script execution failed 2022-12-09T13:26:39.242Z - error: Failed to execute SQL --END EPO-9863 execution failed with error : RequestError: The multi-part identifier "pf.name" could not be bound. execution failed with error : RequestError: The multi-part identifier "pf.name" could not be bound. 2022-12-09T13:26:39.242Z - error: Error executing script file 5_ePO_Proc.sql 2022-12-09T13:26:39.242Z - error: Error executing script file 5_ePO_Proc.sql 2022-12-09T13:28:56.423Z - error: Failed to execute SQL --END EPO-9863 execution failed with error : RequestError: Invalid object name 'SYS.PROCEDURES'. execution failed with error : RequestError: Invalid object name 'SYS.PROCEDURES'. Cause
There's a collation mismatch between the ePO Core and Events database.
Solution
You need to run the SQL query to check the status of the
The results state To verify the collation names for the SQL Server, ePO Core, and Events database, run the following SQL script from the ePO Core database. SELECT[NAME] AS DatabaseName,[collation_name] FROM sys.databases WHERE [name] IN (DB_NAME(),DB_NAME()+'_EVENTS') NOTE: We support all the collation as per Microsoft standards. For details about the supported collation and Unicode types, see this Microsoft article. The query results can be any collation name. But, these collations might be supported as per Microsoft standards. You must make sure that the SQL script result matches with those of the SQL Server, ePO Core, and Events database. Example
Affected ProductsLanguages:This article is available in the following languages: |
|