Skip to Content
avatar image
Former Member

BO support tool- unable to get logs from server

Dear SAP,

We have installed BO support Version 2.1. We have configured and validated the agent successfully. but when we run the E2E trace collection, Tool is unable to get the logs from server using hostagent method.

We could see following logs-

=====Log Collection (Host Agent Method)=====
==Start Time==> Wed Dec 27 14:28:23 MSK 2017
==Starting Collection for Host==> XXXXXXXXXXX.sap.x5.ru
==Starting Collection for Host==> XXXXXXXXXXX.sap.x5.ru
==Log Collection Result for XXXXXXXXXXX.sap.x5.ru==> Failed
==Log Collection Result for XXXXXXXXXXX.sap.x5.ru==> Failed
==End Time Wed Dec 27 14:31:43 MSK 2017
Total Time for copy process: 3 min, 20 sec

BO support tool logs are also not showing any problem but collection are failing.

FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
ENCODING:UTF-8
RECORD_SEPARATOR:30
COLUMN_SEPARATOR:124
ESC_CHARACTER:27
COLUMNS:Location|Guid|Time|Tzone|Trace|Log|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text
SEVERITY_MAP: |None| |Success|W|Warning|E|Error|A|Assertion
HEADER_END
|8F785FF5A5924600A9A701ECAF8676C90|2017 12 27 12:11:43.177|+0300|Debug| |<<| | |BISupportTool|10316| 1|main | ||||||||||||||||||||||Enabling data retention policy...
|8F785FF5A5924600A9A701ECAF8676C91|2017 12 27 12:11:43.180|+0300|Debug| |<<| | |BISupportTool|10316| 1|main | ||||||||||||||||||||||Current Landscape Analysis retention setting: Older than 1 year
|8F785FF5A5924600A9A701ECAF8676C92|2017 12 27 12:11:43.180|+0300|Debug| |<<| | |BISupportTool|10316| 1|main | ||||||||||||||||||||||Current Landscape Definition retention setting: Never
|8F785FF5A5924600A9A701ECAF8676C93|2017 12 27 12:13:26.072|+0300|Debug| |<=| | |BISupportTool|10316| 17|validator | ||||||||||||||||||||||Querying 'http://XXXXXXXXXXX.sap.x5.ru:1128/SAPHostControl/?wsdl
|8F785FF5A5924600A9A701ECAF8676C94|2017 12 27 12:13:26.401|+0300|Debug| |<=| | |BISupportTool|10316| 17|validator | ||||||||||||||||||||||Checking that operations files are deployed
|8F785FF5A5924600A9A701ECAF8676C95|2017 12 27 12:13:26.771|+0300|Debug| |<=| | |BISupportTool|10316| 17|validator | ||||||||||||||||||||||Complete
|8F785FF5A5924600A9A701ECAF8676C96|2017 12 27 12:13:44.034|+0300|Debug| |<=| | |BISupportTool|10316| 20|validator | ||||||||||||||||||||||Querying 'http://XXXXXXXXXXX.sap.x5.ru:1128/SAPHostControl/?wsdl
|8F785FF5A5924600A9A701ECAF8676C97|2017 12 27 12:13:44.041|+0300|Debug| |<=| | |BISupportTool|10316| 20|validator | ||||||||||||||||||||||Checking that operations files are deployed
|8F785FF5A5924600A9A701ECAF8676C98|2017 12 27 12:13:44.407|+0300|Debug| |<=| | |BISupportTool|10316| 20|validator | ||||||||||||||||||||||Complete
|8F785FF5A5924600A9A701ECAF8676C99|2017 12 27 12:13:54.694|+0300|Debug| |<=| | |BISupportTool|10316| 23|validator | ||||||||||||||||||||||Querying 'http://XXXXXXXXXXX.sap.x5.ru:1128/SAPHostControl/?wsdl
|8F785FF5A5924600A9A701ECAF8676C9a|2017 12 27 12:13:54.700|+0300|Debug| |<=| | |BISupportTool|10316| 23|validator | ||||||||||||||||||||||Checking that operations files are deployed
|8F785FF5A5924600A9A701ECAF8676C9b|2017 12 27 12:13:55.039|+0300|Debug| |<=| | |BISupportTool|10316| 23|validator | ||||||||||||||||||||||Complete
|8F785FF5A5924600A9A701ECAF8676C9c|2017 12 27 12:14:08.207|+0300|Debug| |<=| | |BISupportTool|10316| 26|validator | ||||||||||||||||||||||Querying 'http://XXXXXXXXXXX.sap.x5.ru:1128/SAPHostControl/?wsdl
|8F785FF5A5924600A9A701ECAF8676C9d|2017 12 27 12:14:08.221|+0300|Debug| |<=| | |BISupportTool|10316| 26|validator | ||||||||||||||||||||||Checking that operations files are deployed
|8F785FF5A5924600A9A701ECAF8676C9e|2017 12 27 12:14:08.530|+0300|Debug| |<=| | |BISupportTool|10316| 26|validator | ||||||||||||||||||||||Complete
|8F785FF5A5924600A9A701ECAF8676C9f|2017 12 27 12:16:19.704|+0300|Debug| |<=| | |BISupportTool|10316| 29|validator | ||||||||||||||||||||||Querying 'http://XXXXXXXXXXX.sap.x5.ru:1128/SAPHostControl/?wsdl
|8F785FF5A5924600A9A701ECAF8676C910|2017 12 27 12:16:19.709|+0300|Debug| |<=| | |BISupportTool|10316| 29|validator | ||||||||||||||||||||||Checking that operations files are deployed
|8F785FF5A5924600A9A701ECAF8676C911|2017 12 27 12:16:20.012|+0300|Debug| |<=| | |BISupportTool|10316| 29|validator | ||||||||||||||||||||||Complete

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 03 at 02:46 PM

    Hi Abhimanyu,

    Thanks for reporting the issue. It would be helpful if you could collect the SAP Host Agent trace logs along with the full BIPST tracelog. Here's a guide to help you enable and collect the trace on the server side:

    https://wiki.scn.sap.com/wiki/display/ATopics/SAP+Host+Agent+Troubleshooting+Guide#SAPHostAgentTroubleshootingGuide-ChangingthedefaulttracelevelofSAPHostAgent

    Once the tracing is enabled, run the E2E Trace Wizard again to generate the traces. You can email me the BIPST tracelog and host agent logs to toby.johnston@sap.com. Don't forget to disable the SAP Host agent trace when you are done.

    I'd also be willing to work with you over a Citrix GoToMeetingsession to get this working. Please reach out to me if you want to go this route.

    Thanks
    Toby

    Add comment
    10|10000 characters needed characters exceeded