cancel
Showing results for 
Search instead for 
Did you mean: 

Batch Processing Sm37 only at active state(urgent)

sitiaishah_abdulfatah
Participant
0 Kudos
311

Dear Expert,

I need to run depreciation for October month for asset. But when I process in sm35 job to running background, the job only at active state until we check status and manually cancel. So I have failed to run the asset depreciation to post to GL.

Restart server have been done.

Fully shutdown also done.

Still same. It is happen In this Nov. And after that I see when I want to do physical stock count that using batch process also similar problem. I have search around check everywhere, I not sure what happen. So we are stuck to do asset depreciation and physical stock count.

If anyone can share how to solve is really appreciate.

Thank and urgent

Accepted Solutions (0)

Answers (4)

Answers (4)

sitiaishah_abdulfatah
Participant
0 Kudos

amo ntella,

yeah 4.0B sap. i see this article http://kmit4u.blogspot.com/2010/07/sap-basis-note-7676731169524-problem.html

it is exactly the same happen to us. but i dont know is it we need support package as the 4.0B no more? is it this is the problem whereby it is come to expire or what? 😞

amontella96
Active Contributor
0 Kudos

hi sitiaishah.abdulfatah

i see that the error is related to kernel, can you give me a bit of background? are you working a new system? OR did you (or your basis team) update anything lately that may have generated this issue

A

sitiaishah_abdulfatah
Participant
0 Kudos
sm37.jpg

So far we don't have BASIS team and we do not update anything suddenly come November to opening and finance want to do end month process this occur. our systems is SAP 4.0B R3. I have try to expand PSAPTEMP database and do many thing still same endup with the status in active and process no longer active that all.

former_member426482
Participant
0 Kudos

check any lock entry in SM12. Delete the lock entry and go to the job option in the menu and check status and cancel with core and restart the job again. I believe you dont have enough background process's available to run the job. Check any long running stuck jobs and cancel them to restart your job again.

Thanks

sitiaishah_abdulfatah
Participant
0 Kudos

hi Manohar,

yes sm12 also see no lock entry. and the job will no longer active within few second only. then the check status will ask to cancel manually. the motive now is not because job to cancel , but we want to process the job but failed. all the batch background process example from asset depreciation, physical count cannot go through after sm35 mission. no log no trace no abap runtime. but I saw invalid teamse name at sm50

regards

amontella96
Active Contributor
0 Kudos

Hi sitiaishah.abdulfatah

SAP 4.0B R3? WOW! it's vintage! 🙂

I'm thinking, do you have the error only for these couple of jobs or even for others (check in SM37), although the message would be different it maybe that you are requesting too much memory to the system? Can you run those jobs in small chunks ?

I understand that you don't have a basis team , what about operating system, can you get some support?

let us know!A

amontella96
Active Contributor
0 Kudos

hi sitiaishah.abdulfatah

np! what error did you see in disp+work? can you upload the trace file of that pid failed?

A

sitiaishah_abdulfatah
Participant
0 Kudos

Tq. here you go only from event viewer I can see

Event Type: Information

Event Source: Application Error

Event Category: (100)

Event ID: 1004

Date: 11/4/2021

Time: 7:34:09 AM

User: N/A

Computer: OCEPROD2

Description:

Reporting queued error: faulting application disp+work.EXE, version 0.0.0.0, faulting module kernel32.dll, version 5.2.3790.4062, fault address 0x0000bee7.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 64 69 73 ure dis

0018: 70 2b 77 6f 72 6b 2e 45 p+work.E

0020: 58 45 20 30 2e 30 2e 30 XE 0.0.0

0028: 2e 30 20 69 6e 20 6b 65 .0 in ke

0030: 72 6e 65 6c 33 32 2e 64 rnel32.d

0038: 6c 6c 20 35 2e 32 2e 33 ll 5.2.3

0040: 37 39 30 2e 34 30 36 32 790.4062

0048: 20 61 74 20 6f 66 66 73 at offs

0050: 65 74 20 30 30 30 30 62 et 0000b

0058: 65 65 37 ee7

amontella96
Active Contributor
0 Kudos

Hi sitiaishah.abdulfatah

im not sure writing "urgent" will take you anywhere, while posting any research and troubleshoot may help you for sure

are you a basis? if yes read below for start:

google troubleshoot background jobs AND

https://answers.sap.com/questions/9835515/what-action-needs-to-be-done-if-one-background-job.html

otherwise get a basis guy to help you, we all need a basis guy soon or later in sap life 😉

sitiaishah_abdulfatah
Participant
0 Kudos

Tq amo,

I did research and what have done same checking sm50 Sm37 all I check the only I see in the event viewer stated that the disp+work got error with the PID? Is it OS issues?. There is no abap runtime or log that I can see or maybe I can't find it.

It also can kill using sm50. But the purpose is not because of killing the process but I want the process operate to post the document.

Tq for your kind reply