	Product(s):	APM Implementation and Performance Management
	Version(s):	all
	Environment:	N\A
	Area:	N/A
	Subarea:	N\A

Problem

A user has created a new or made changes to a configuration and the configuration now results in a bad SQL statement and selecting the configuration causes the system to crash.

In cases where the altered configuration is an MCLB's default configuration, visiting the tab on which this MCLB is located will cause the system to crash.

Sometimes, APM displays an error message like;

Exception Type: Ivara.PL.Exceptions.InvalidActivityException

Message: ConfigurationDataAssembler::AssembleConfigurationDTO - pConfig is NULL...……….

Solution 1

The configuration must be either fixed or deleted.

If this is not the default configuration on the MCLB, the user can fix the configuration through the Organize Configuration option, double click on the configuration to open it and fix it, or

In 5.x, - go to Enterprise\Configurations View and find the configuration in question. Either delete or open to fix.

In 6.x – As Administrator user, go to Enterprise\Customization Center View, User Interface\Configurations tab. Ensure that Enterprise is checked out for Editing. RMBC on the configuration and select Open. Alter the configuration to remove the offending column. Administrator cannot delete Personal Configurations in R6.

In R7.x - As Administrator user, or owner of the configuration, go to Enterprise\Customization Center View, User Interface\Configurations tab. Ensure that Enterprise is checked out for Editing. RMBC on the configuration and select Delete to get rid of the configuration or Open to alter the configuration to remove the offending column.

If you are not able to fix or delete the configuration, let support know and we may need to provide a script to assist or assist via an interactive session

Solution 2

If the solution mentioned above does not work, then this is the another way to fix the crash.

Please execute the below mentioned SQL statement in database;

select uc.USERCONFIGURATIONOI, uc.SUBSCRIPTTYP, uc.CREATEDATE_DTTM, uc.USERCREATEDB, uc.LASTUPDATE_DTTM, uc.LASTUPDATEBY, uc.MCLBCONFIGUR_OI, c.*

from oq.USERCONFIG uc

left outer join oq.MCLBCONFIGURATION c on c.MCLBCONFIGURATIONOI = uc.MCLBCONFIGUR_OI

where CONFIGURATIO is null

After execution of the above mentioned SQL statement, please have a look at the results. You should see a row in the result and many columns. Now, copy the value of that row under the column USERCONFIGURATIONOI.

The next step is to execute the below mentioned SQL statement in database;

delete oq.USERCONFIG where USERCONFIGURATIONOI = XXX

(where, XXX = The value of the row under the column USERCONFIGURATIONOI which was copied from the results of the previous SQL statement)

Make sure that, this statement is executed successfully with result showing (1 row affected).

Now try to log in to APM and try visiting the view which was causing APM to crash.

You should be able to visit the particular view successfully.

Solution 3

An alternate way to fix this situation, if the user does not have a large number of personal configurations to loose, is to create a new login for him/her, and update the personnel profile to use the new login.

In Enterprise/Security, Locate the APM user that this employee is using. Change the login name on this record, Create a new user (add security profiles as per original user)
On Site/Employees, Go the Employee record, change the employee's login reference to the new one.
Once this is done, you should be able to delete the original user in Enterprise/Security which would in turn delete all the configurations associated with that APM user.
Please try this in a test environment first, if it is a suitable alternate resolution. If it works fine, then do the same in production.

Note:

Before executing any SQL statement, please make sure that all the clients are disconnected.
Bentley always recommend to test anything in QA environment and, if the tests are successful and you are confident about the changes, then proceed with changes in the PROD environment.
Bentley never recommend to do any changes directly in the PROD environment. Bentley will not take any responsibility about any damage that occurs to the PROD environment if you directly do any changes in PROD environment without testing it in QA environment.

Personal Configuration causing a crash

Problem

Solution 1

Solution 3

See Also