Severe error(s) occurred in phase MAIN_INIT/UVERS_CHK!

[Former Member]

Hello All,

I get this error  during in phase MAIN_INIT/UVERS_CHK!

Last error code set: RFC login to system PJ1 ashost dkrdssap342 nr 01 gwhost dkrdssap342 gwservice sapgw01 failed with code 2 key : Password must be changed.

Any Idea which RFC ai need to check, RFC for PJ1 system on PJ1 has no password?

Thanks for any help.

[Reagan · Accepted solution]

Hello Reza

Are you able to login to the system with the DDIC user ?

Regards

RB

[Former Member · Accepted solution]

Hello Reagan,

Thanks for reply,

Yes problem was DDIC password, now I get this error

2 ETQ373 parameter "JOBCOUNT" = "15530100"

2 ETQ373 parameter "IV_VERIFY" = " "

1 ETQ234 Call of function module "SUBST_CHECK_BATCHJOB" by RFC succeeded

4 ETQ010 Date & Time: 20140904155301 

2 ETQ373 parameter "JOBSTATUS" = "A"

2 ETQ374 parameter "RC_CHECK" = "0"

2 ETQ373 parameter "JOBENDDATE" = "20140904"

2 ETQ373 parameter "JOBENDTIME" = "155301"

2EETQ262 Batchjob "RDDIT008" aborted

1EETQ399 Last error code set is:

1EETQ204 Upgrade phase "BATCHCHK" aborted with severe errors ("20140904155301")

I can see on SM37 the Batchjob "RDDIT008" was canceled,

Job started

Step 001 started (program RDDIT008, variant , user ID DDIC

Log cannot be written (existence? authorization?)

Job cancelled

I can see the DDIC user har sap_all and SAP_new rolles.

Any idea about this?

Thanks

[Reagan · Accepted solution]

Hello Reza

Can you provide the log BATCHCHK.LOG and BATCHCHK.ELG please ?

Check this SAP note if the logs contain errors mentioned in the note

1972214 - Error in Upgrade : batch job fails with this error "Log writer aborted with RC 1"

Regards

RB

[former_member182657 · Accepted solution]

Hi Reza,

Kindly follow SAP note  46305 - RDDIT008 terminates in phase BATCHCHK

Regards,

Gaurav

[divyanshu_srivastava3 · Accepted solution]

Hi Reza,

For this error,

Log cannot be written (existence? authorization?)

These are the reason for termination, in general

No write auth to the sub-directories of the upgrade directory (subdirectories bin, log, tmp, ...)
No freespace in the upgrade directory
The upgrade directory cannot be reached from the batch host specified.

Regards,

Divyanshu

[Former Member · Accepted solution]

Hello,

I had added to file, There is no .LEG file.

Thanks

Reza

BATCHCHK_SAV.txt.zip

BATCHCHK.txt.zip

[Former Member · Accepted solution]

Hello Divyanshu,

Thanks for reply,

There is more than 50 GB Space on upgrade directory.

Thanks

Reza

[Former Member · Accepted solution]

Hi Gaurav,

I had added this  DIR_PUT parameter on default profile befor I start Preprocessing Phase, should I add this on to instance profile too?

Thanks

Reza

[Former Member · Accepted solution]

Hello All,

I had restart server and tried again error is change to:

ERROR: Batchjob RSVBCHCK failed. Detected the following errors:

# F:\Reeje\SUM\abap\log\RSVBCHCK.PJ1:

       1 ETH010XRSVBCHCK: Check of open update requests

       2EETG050 Update records still exist - Please process

-------------------------------------------

4 EPU201XBEGIN OF SECTION BEING ANALYZED LASTOFFSET                  806 NOW BEGIN OF JOB_RSVBCHCK_PRE =========

1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

4 EPU202X====MARK ANALYZED SECTION==== END OF JOB_RSVBCHCK_PRE ======== BEGIN OF JOB_RSVBCHCK_PRE ==========

1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

4 EPU202X====MARK ANALYZED SECTION==== END OF JOB_RSVBCHCK_PRE ======== BEGIN OF JOB_RSVBCHCK_PRE ==========

1 ETH010XRSVBCHCK: Check of open update requests

4 EPU202X====MARK ANALYZED SECTION==== END OF JOB_RSVBCHCK_PRE ======== BEGIN OF JOB_RSVBCHCK2 =============

1 ETH010XRSVBCHCK: Check of open update requests

2EETG050 Update records still exist - Please process

4 EPU202XEND OF SECTION BEING ANALYZED END OF JOB_RSVBCHCK2 ================================================

Thanks

Reza

[Former Member · Accepted solution]

I had find to update records with error on SM13, I think it is the problem.

Reza

[former_member182657 · Accepted solution]

Hi Reza,

Clear all the error locks under SM13 and retry the phase again.

Regards,

Gaurav

[divyanshu_srivastava3 · Accepted solution]

Hi Reza,

Have a look at sap note - 67014.

That should solve your issue.

Regards,

Divyanshu

[Former Member · Accepted solution]

Hello

Yes I did and find another error , now I can continue.

Thanks for help

Reza

[Former Member · Accepted solution]

Hello,

I am during main_shdpreput/start_shd_preput and the Shadow instand can not start. dispatcher is stopes.

I had added DEVTRACE.log file and developer trace.txt, Is it some body had the same problem on shadow instance.

Thanks for any help.

DEVTRACE.txt.zip

developer trace.txt.zip

[divyanshu_srivastava3 · Accepted solution]

Hi Reza,

*** ERROR => [CreateOsShm] CreateFileMapping(73,58800 KB) failed with Err=1455 
              ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete. [shmnt.c      2263]

For the above error you can refer:

PXA_NO_SHARED_MEMORY - ABAP Development - SCN Wiki

Refer:

1518419 - Page file and virtual memory required by the SAP system

Adjust above part and try again by taking a restart.

Regards,

Divyanshu

[divyanshu_srivastava3 · Accepted solution]

You have uploaded one more dev_disp 

Can you share dev_ms and dev_w0 please.

Regards

[Former Member · Accepted solution]

Hello,

Thanks for reply.

I had add dev_disp and dew_0 , from SUM,

Thanks Again

dev_w0.zip

dev_w1.zip

dev_disp.zip

[divyanshu_srivastava3 · Accepted solution]

Hi Reza,

Same error -

I  *** ERROR => [CreateOsShm] CreateFileMapping(43,379755 KB) failed with Err=1455 
              ERROR_COMMITMENT_LIMIT: The paging file is too small for this operation to complete. [shmnt.c      2263]
I  *** ERROR => ShmCreate: Create (43,388869136,1) failed [shmnt.c      535]

How much of RAM how you have ?

Can you increase virtual memory and set paging file ?

Refer:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/300cc754-45a0-3010-79b9-f7a5395a2...

And the note that I have asked you to read.

The same note has one more linked note, have a look..

Regards

[Reagan · Accepted solution]

First try to reduce em/initial_size_MB to a smaller value.

At present it is set to 17199MB. If possible set it to 8 GB and restart SAP.

If that doesn't help then follow this SAP note

1997262 - The shadow instance won't start up. System dev_w* trace files highlight error message 1455...

Regards

RB

[Former Member · Accepted solution]

Hello Divyanshu,

Thanks for reply I had increse memury, But I cannot restatr server now, This is production server.

I will restart the server leater and come back with result

Thanks

Reza

[divyanshu_srivastava3 · Accepted solution]

Please check the reply from RB.

A further/correct tuning can be done from note referred by him.

Regards

[Former Member · Accepted solution]

Hello Reagan.

Thanks again

This is from main instsnce, Is it not ok?

[Former Member · Accepted solution]

Hello,

I will  refare in to 1997262 note now

Thanks aain

Reza

[Former Member · Accepted solution]

Hello,

Thanks for all helps, I did used this note and now shadow startet,

Thanks Again

Reza

[former_member182657]

Hi Reza,

Nice !! Kindly close the thread.

Regards,

Gaurav