BI 4.1 SP5 To SP7 -platform search fails on Jobserver

[former_member182373]

Guys,

Recently patched form SP5 To SP7.  Now any scheduling of the platform search fails  with the generic error message of

Object failed to run due to an error while processing on the Job Server.

The continuous crawling works ok  , and also similar job server scheduling jobs - such as Webi reports -work ok.

It just the scheduled platform search that cannot run on the jobserver.

Tried the usual restart of the server and same error.

Thanks

Tony

[former_member205064 · Accepted solution]

Stop the current job server and create a new one  with default service and then try the scheduling.

also create APS with separate Platform search service.

[bob_zenker3]

I had to restart the APS.Core also to get it run after rebuilding the APS.Search service

[JohnClark]

Bob, what services are running on your APS.Core?

[former_member198519]

Why dont you Split your APS services and stop the core service?

[bob_zenker3]

I don't know why any of these service would effect the issue but I'm just letting everyone know that I still received the error until I restarted the APS.Core service.  It contains (from the config wizard)

[JohnClark]

We have those same services in our APS.Core server except the Monitoring Service and TraceLog Service.  The TraceLog service is in our APS.Monitoring server so I assume it goes with the Monitoring Service.

It doesn't look like any of these services would impact it either but it could be the Monitoring Service.  We have our APS.Core shut down but our Monitoring Service is running on a separate APS.

Could be another "undocumented feature".

We don't have problems with Search in our non-production environments but we do in Production which is much larger.  I don't think it is related to this issue because everything runs except the last stage of Platform Search Content Store Merge Queue.  Everything is bottled up in that stage.

I'll be submitting a case to SAP on our issue next week.

[Former Member]

This is a bug in BI 4.1 and BI 4.2 version that is being investigate by development team. As a workaround, Delete the existing Search APS server. Create a new APS Search server and schedule the Search Program again. This should resolve the issue.

[former_member182373]

Thanks Farukh .I did that at the time and it fixed the issue.thanks for the suggestion.

Tony