Diffuser License Not Installed

If a Diffuser License is not installed you will get an error:

If the Diffuser Programs have not been created yet:

Reference System Error

If you have no ST03 data available:

You can follow SAP Note https://me.sap.com/notes/0002369736 and activate the SAP_COLLECTOR_FOR_PERFMONITOR job to be schedule in client 000 of your Reference system.

RFC Error

RFC destinations are language dependent, currently when using a German Chrome browser you get a Server Error 500 when RFC destinations are created in English. You need to align the language.

Truncate Initial Link Building Tables
You can truncate the following two tables to reset the Link Building process.

/BTI/TE_DI_OBJLK & /BTI/TE_OBJID

What if Automatic DIA link building fails to start

There are two possible ways to handle this error:

First possible way is performed in the ActiveDiscover UI:

1. Delete Source System
2. Settings -> Advanced Settings -> Turn on “Disable automatic DIA setup”

3. Perform the following steps manually:
Start the Initial Link Building by executing report /BTI/TE_REP_MDR_OBJECT_DI_LINK via SE38 on your Source System in the background using variant OBJLINKS

4. Settings -> Advanced Settings -> Turn off “Disable automatic DIA setup”
5. Add your Source System. ActiveDiscover will then validate your setup automatically

Schedule a new job on your central system.

Job Name: DI_LINKS_UPDATE_JOB_PX
Report: /BTI/PX_TIR_LINK_UPDATE
Note: This Report has no selection screens
Step User Personal Admin User or Background User with Role /BTI/PX_ADMINISTRATOR
Periodic Execution: 10 Minutes

Second possible way is performed in SAP GUI:
Turn it off by setting parameter AUTO_DIA_SETUP in table /BTI/PX_PARAMS to false (space), remove the system and re-add it, then do the setup manually as per this article.

What if Analysis run hangs

In the beta version, the error reporting for an analysis run has not been fully built, for example the UI won’t recognize if the process short dumped etc.
Planned to improve this by GA
Need to look at ST22 and SM50 in the central system

Browser Cache

After an upgrade of AD the browser cache can be maintained in the client and does not display the latest iteration of the browser version or landscape view. Refreshing the browser (F5) does not rectify this.
Test – open incognito mode tab in browser and log into same system – if issue is not seen then the browser cache is still being referenced and normal browser session should be closed and reopened.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment