/scripts/ahub.form.attachments.js
0

​Promotion job failed when promoting with windows AD account

Feb 17, 2017 at 07:47 AM

119

avatar image

Hi All,

Initially we are doing promotion with enterprise account only as we faced some issues with windowsAD.

Currently ,we are doing some testing for "promotion with windows AD account" over the entire Landscape.

Promotion with windows AD Testing::

To promote the content with windows AD , below command needs to be added on Source and Destination System mandatorily under Command Line Parameters across all the nodes having AJS

Command :: For example , Djava which includes .conf and krb5.ini

Process
Log on to CMC
Navigate to Servers
Add the above command under Command Line Parameters across all the nodes having AJS.
For example, system name >AJS>Properties>Command Line Parameters>Add the above command .
Restart the server
Start the promotion.

We successfully promoted the content from QA to SB and vice versa i.e., success on Non Prod systems.

But we are getting issues ,when we promote from QA to Prod and vice versa , error message is just "Failure" and failure don't have message.

Please do the needful

Thanks

Ram

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

3 Answers

Jyothirmayee A Feb 17, 2017 at 04:06 PM
0

Hi,

Check the firewall between QA and Prod environments.

if it is more than 1 clustered environment, verify the servers in CMC and check if the hostname server is updated with the host file.

Also, try restarting the QA/Prod servers.

Thanks,

Jothi

Show 4 Share
10 |10000 characters needed characters left characters exceeded

Hi Jyothi,

Thanks for your inputs

You mentioned three inputs here ,but we are not sure where do we check the below input ?

"If it is more than 1 clustered environment, verify the servers in CMC and check if the hostname server is updated with the host file" ,please provide some navigation here.

Moreover , you wanted us to check firewall between QA and Prod systems, that means 'Is fire wall will be in off or on state ?

One thing Jyothi, When we do the promotion from QA to Prod ,sometimes it is showing as success and sometimes failure ?

Please do the needful.

0

Hi,

Did you restarted both AdaptiveJobServer and AdaptiveProcessingServer?.

What does your CMC logs says when the instance is failed?.

When you see a promotion success, check CUID of each report that are failed?. I feel there must be corrupted Instance.

Hope you have followed all the steps mentioned below..

https://blogs.sap.com/2012/10/25/promotion-management-in-bi40/

Also, try these as mentioned in the link:

https://archive.sap.com/discussions/thread/3474238

1. Go to instance manager and check whether there are any schedules in pending state.

2. If there are pending schedules kindly check whether your promotion job is there in pending.

3. If yes, go to servers and bounce your job servers one by one after disabling them. Once they are up and running, enable them.

4. After that you need to go to instance manager to see if the jobs are running.

5. If the schedules in pending are now running your promotion job will also go through as per its priority in the job queue.

Thanks.

Jothi

0

Hi Jyothi,

Thanks for your inputs.

We are promoting the content (Users and Groups ,connections, universes and reports) from environment to environment with enterprise account successfully with out any issues since so many days.

We done lot of complete project folder promotion with enterprise and we are aware of promotion concept.

But now ,users requested us to find some solution that why we are unable to promote the content with windows AD.

0

Run and End to End trace as suggested by @Denis Konovalov

Thanks,

Jothi

0
Jawahar Konduru Feb 17, 2017 at 04:22 PM
0

Can you confirm if promotion works with Enterprise authentication?

Show 1 Share
10 |10000 characters needed characters left characters exceeded

Jawahar,

Yes , Promotion works with enterprise account successfully.

0
Denis Konovalov
Feb 21, 2017 at 06:43 PM
0

Run end to end trace and see what the problem is (KBA 1861180)

Share
10 |10000 characters needed characters left characters exceeded
Skip to Content