Error Code 335 OLAPExportHierarchy

Hi,

I am in the process of upgrading a customer from V11 to V12, and I am running through the OLAP to Relational Modelling process built by Kai Reischl.

I am on the stage "Fill Staging tables" and am getting the following error across every dimension:

Notify (Error) -> Calling function 'OLAPExportHierarchy' failed with this message: An exception was thrown to inform the client about error condition (FaultResponse).. Error code '335': An exception was thrown to inform the client about error condition (FaultResponse).

Notify (Error) -> Finished process with errors:
ERROR exporting dimension <CURR>, hierarchy <CURR>: Calling function 'OLAPExportHierarchy' failed with this message: An exception was thrown to inform the client about error condition (FaultResponse).. Error code '335': An exception was thrown to inform the client about error condition (FaultResponse).

I have tried changing all the attributes to String type, filling in all attribute values, keeping only the first attribute table and finally removing all attribute tables to no success.

Can anyone assist here?

This currency dimension named "Curr" has only one level with 12 elements and I can not see any issues with it.

Find more posts tagged with

Infor EPM Discussions

Comments

Peter Mayall

Have a look at the logs in the EPM Administration application. This should give you the information you need.

haider-razzak

Hi Peter,

Thanks I was not aware they appeared there. I get the following error across all the dimensions. Unfortunately not very descriptive.

"The hierarchy export for hierarchy 'Curr' failed to execute. An exception was thrown to inform the client about error condition (FaultReponse). Format of the initialization string does not conform to specification starting at index 53."

Peter Mayall

See if there is an earlier log record. Normally it is the first error message that is useful. Also be aware there is a 'Message' hyperlink at the bottom of the page. Click the hyperlink to display the details of the error,.

haider-razzak

Hi Peter,

Unfortunately that message is all that is provided, I passed the parameter for the dimension name and that exact same message appears.

haider-razzak

We resolved this with Infor Support, the issue was with the SQL user in the connection string communicating with the external SQL server. The SQL user is not allowed to have certain special characters in the password, such as "=". Removing this and updating the connection string solved the issue.

Matthew Nye

that seems like that could be a pretty persistent issue for almost every upgrade. I wonder, would you be willing to share your upgrade doc that you referenced in the OP? Im going through a similar upgrade now, though it doesnt involve upgrading d/EPM Cubes, and it might have some useful information.

Copyright © 2025 Infor. All rights reserved.