Solved: saposcol on windows nt 5.2

Hi All,

On our SRM production server (Kernel 700, pkg lvl. 41, oracle 10.1, windows 2003), while calling transaction st06, we encounter the following message.

"saposcol not running? (shared memory not available)"

as a result of which, we are not geiing any data in the os collector. Please help.

Regards

Bais Team, OIL

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

goto st06 --> Operating system collector --> start it

or you can start the service from windows service manager SAPOSCOL service.

cheers,

-Sunil

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Sunil,

Thanks for quick reply. We have already tried that. Same message is appearing again and again. When we saw the logfile it says that "collector not running, process id not available). In our SRM Dev & Qas system, under the same platform saposcol is running properly.

Looking forward for more info.

Regards

Basis Team, OIL

try to start the saposcol from the os command prompt

saposcol -s :Displays the status of the collector

saposcol –l : starting the collector

saposcol -k : stoppiong the collector

if ay problem while starting the collector please paste the error log.

Cheers,

-Sunil

Hi suil,

We forgot to tell you that we have tried all those options. Onother thing is that, saposcol service is running under windows services. Please see the log below.

SAPOSCOL version COLL 20.89 700 - 20.52 NT 05/08/15, 32 bit, multithreaded, Non-Unicode

compiled at Sep 7 2005

systemid 560 (PC with Windows NT)

relno 7000

patch text COLL 20.89 700 - 20.52 NT 05/08/15

patchno 22

intno 20050900

running on SRMPROD Windows NT 5.2 3790 Service Pack 1 8x Intel 801586 (Mod 4 Step 1)

16:29:51 12.03.2007 LOG: Profile : no profile used

16:29:51 12.03.2007 LOG: Saposcol Version : [COLL 20.89 700 - 20.52 NT 05/08/15]

16:29:51 12.03.2007 LOG: Working directory : F:\usr\sap\PRFCLOG

16:29:52 12.03.2007 LOG: Allocate Counter Buffer [10000 Bytes]

16:29:52 12.03.2007 LOG: Allocate Instance Buffer [10000 Bytes]

16:29:52 12.03.2007 LOG: You can ignore :"Index of Title:[Disk Queue Length] not found" on Windows NT 4.0

16:29:52 12.03.2007 LOG: Shared Memory Size: 61722.

16:29:52 12.03.2007 LOG: Connected to existing shared memory.

16:29:52 12.03.2007 LOG: Reused shared memory. Clearing contents.

16:29:55 12.03.2007 LOG: Collector daemon started

16:29:55 12.03.2007 LOG: read coll.put Mon Mar 05 08:42:03 2007

16:29:55 12.03.2007 LOG: Collector PID: 10228

16:30:05 12.03.2007 LOG: Process Monitoring active.

16:30:05 12.03.2007 LOG: searching for Process Monitoring Templates in F:\usr\sap\PRFCLOG\dev_proc

16:30:05 12.03.2007 LOG: searching for Process Monitoring Templates in F:\usr\sap\PRFCLOG\procmon\

16:30:05 12.03.2007 LOG: The following processes will be monitored:

16:30:05 12.03.2007 LOG: Process: jlaunch-DSAPINFO=SRP_01_dispatcher* for user: SAPServiceSRP

16:30:05 12.03.2007 LOG: Process: jlaunch-DSAPINFO=SRP_01_server* for user: SAPServiceSRP

16:30:05 12.03.2007 LOG: Process: jlaunch-DSAPINFO=SRP_01_sdm* for user: SAPServiceSRP

16:33:04 12.03.2007 WARNING: WaitFree: could not set new shared memory status after 5 sec

16:33:04 12.03.2007 LOG: No Write Access to Shared Memory: Skip this interval.

16:33:19 12.03.2007 WARNING: WaitFree: could not set new shared memory status after 5 sec

16:33:19 12.03.2007 LOG: No Write Access to Shared Memory: Skip this interval.

16:33:34 12.03.2007 WARNING: WaitFree: could not set new shared memory status after 5 sec

16:33:34 12.03.2007 LOG: No Write Access to Shared Memory: Skip this interval.

16:33:49 12.03.2007 WARNING: WaitFree: could not set new shared memory status after 5 sec

16:33:49 12.03.2007 LOG: No Write Access to Shared Memory: Skip this interval.

16:34:04 12.03.2007 WARNING: WaitFree: could not set new shared memory status after 5 sec

16:34:04 12.03.2007 LOG: No Write Access to Shared Memory: Skip this interval.

Regards

Basis Team, OIL

Hi Basis,

It seems that this is window level permission/authorization issue. Check if SAPServiceSRP

has proper access to
host\saploc\prfclog. Give this access to SRPADM though it is SAPServiceSRP which is repsonsible for SAPOSCOL in you case.

If not then give the proper authorizations and then try.

Generically check if everything is fine with SAPServiceSRP.

Regards.

Ruchit.

Message was edited by:

Ruchit Khushu

Message was edited by:

Ruchit Khushu

what is the output when you execute the command

saposcol -s :Displays the status of the collector

Cheers,

-Sunil

Hi,

See the output of saoscol -s

C:\Documents and Settings\srpadm>saposcol -s

**************************************************************

Collector Versions :

running : COLL 20.89 700 - 20.52 NT 05/08/15

dialog : COLL 20.89 700 - 20.53 NT 05/11/30

Shared Memory : attached

Number of records : 579

Active Flag : active (01)

Operating System : Windows NT 5.2.3790 SP 1 SRMPROD 8x Intel 801586 (M

Collector PID : 10036 (00002734)

Collector : running

Start time coll. : Mon Mar 12 16:43:47 2007

Current Time : Mon Mar 12 16:53:35 2007

Last write access : Mon Mar 12 16:53:32 2007

Last Read Access : Mon Mar 12 16:49:55 2007

Collection Interval : 10 sec (next delay).

Collection Interval : 15 sec (last ).

Status : read

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Number of free Com. Records : 60

Resulting offset to 1.data rec. : 61

Trace level : 2

Collector in IDLE - mode ? : NO

become idle after 300 sec without read access.

Length of Idle Interval : 60 sec

Length of norm.Interval : 10 sec

Hello,

your SAPOSCOL is running, Start time coll. : Mon Mar 12 16:43, check your log which you have sent.

running : COLL 20.89 700 - 20.52 NT 05/08/15

Collector PID : 10036 (00002734)

Collector : running

could you please check the PID 10036 in your windows taskmanager?

Cheers,

-Sunil

Hello Sunil,

It is true that status of saposcol is 'running'. But, when you goto st06 it shows the message as we have mentioned. That is the reason why we have put this in the forum.

Regards

Basis Team

Answers (3)

Hi,

Just want to ask the status of your problem.

Have you resolved your problem? Do you get the OS logs in ST06 already?

I just wanted to get your answer because right now I am experiencing the same problem as yours. Hope your could help me with this. Thanks in advance.

Message was edited by:

Jaypee Alcala

Message was edited by:

Jaypee Alcala

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Try to adjust the buffer sizes and then properly configure pool sizes..

Regards,

Satish K.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Please visit this link and follow the steps given:

http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a6c9b505211d189550000e829fbbd/content.htm

please award points if the issue got solved.

Regards.

Ruchit.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Ruchit,

We got helpful info from the link. But the same problem.

Regards

Basis

Hi,

Please check under which user is SAPOSCOL registerd in you PF1 system.

Ideally it should be SAPServiceSRP generically speaking SAPService<sidY>.

Try using that option.

Check OSS note 436186 additionally.

Regards.

Ruchit.

Message was edited by:

Ruchit Khushu

Hi Ruchit,

It is running under the <sid>adm user. There is no problem with this user because:

a) it belong to the admin group

b) same thing is running in other system properly.

I am checking the said note and will come back to you.

Regards

Basis Team

Hi,

Yes you are right here is nothing wrong in running with <sid>adm but SAP itself recommends that sapservice<sid> be used if it is available.So I was exploring that option.

Regards.

Ruchit.

Hi Ruchit,

We have changed the user of the service saposcol to SAPServiceSRP as suggested by you. But from ST06 we are getting same error.

Following is the Log of saposcol -s.

C:\Documents and Settings\Administrator>saposcol -s

**************************************************************

Collector Versions :

running : COLL 20.94 700 - 20.57 NT 07/01/31

dialog : COLL 20.89 700 - 20.53 NT 05/11/30

Shared Memory : attached

Number of records : 579

Active Flag : active (01)

Operating System : Windows NT 5.2.3790 SP 1 SRMPROD 8x Intel 801586 (M

Collector PID : 8448 (00002100)

OpenProcess failed, lasterror 87

Collector : not running (process ID not found).

Start time coll. : Tue Mar 13 09:49:13 2007

Current Time : Tue Mar 13 13:54:18 2007

Last write access : Tue Mar 13 13:49:42 2007

Last Read Access : Tue Mar 13 09:44:11 2007

Collection Interval : 60 sec (next delay).

Collection Interval : 65 sec (last ).

Status : read

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Number of free Com. Records : 60

Resulting offset to 1.data rec. : 61

Trace level : 2

Collector in IDLE - mode ? : YES

become idle after 300 sec without read access.

Length of Idle Interval : 60 sec

Length of norm.Interval : 10 sec

**************************************************************

Warm Regards.

BASIS TEAM.

OIL INDIA LTD.

Hi,

seems implementing my solution only worsened the situation for you :-((. sorry guys.

Anyways did you try to restart the service at the OS level?

I hope before changing the user you had stopped SAPOSCOL and then restarted after the changes were affected.

May be you can try using the user Administrator for running the service.

Regards.

Ruchit.

Message was edited by:

Ruchit Khushu

opps, now your Collector : not running (process ID not found).

could you pl revert back the changes what you have done, and try to arrange the downtime. The only one option left is try with restart your windows server after restart also same problem then try to upgrade SAPOSCOL to latest version even then also same problem then you have to report to SAP support.

Cheers,

-Sunil

Hi Ruchit,

Finally we could do it. followings are the steps how we could manage it.

1. saposcol -d ; kill ; leave ; launch ; exit.

2. we run st06. From there we start collector. Now from status it says collector

running.

3. At this stage if we see the collector service at Management Console the

service is not started.

4. Current value of parameter exe/saposcol = F:\usr\sap\SRP\DVEBMGS01

\exe\saposcol.EXE

5. Location of the executable of the saposcol service is "F:\usr\sap\SRP\SCS00

\exe\saposcol.exe service"

Could you make out any reason why service status is 'not started' when started from OS ?

Thanks for your co operation.

Warm Regards.

BASIS TEAM.

OIL INDIA.

BASIS TEAM

OIL INDIA LTD.

Hi Guys,

Not sure as of now why this error is coming. Anyways is the original issue solved ?

Also the points 4 and 5 you have mentioned

are you getting them in form of logs or you have typed them out yourselves as comments from you side.

saposcol.exe should reside in kernel directory in your case F:\usr\sap\SRP\DVEBMGS01

\exe. I dont why Location of the executable of the saposcol service is "F:\usr\sap\SRP\SCS00

\exe\saposcol.exe service"!!

Regards.

Ruchit.

Hi Ruchit,

Our Original Issue seems to be solved.

About points 4 & 5 we had put our observation only.

Two more points.

1. saposcol.exe resides in both locations

2. We had replaced the old saposcol with new one.

Thanks and Regards.

BASIS TEAM.

OIL INDIA LTD.

Is this installed in cluster? or do you have any Dialog server installed?

In st06 you can findout on which server your SAPOSCOL is running. ST06 --> OS collector --> <OS> <Server_NAME>. check whether it is the same as you logged into the OS.

Cheers,

-Sunil

Hi,

We do not have cluster or Dialog Server.

It is running in the same server where we logged in.

BASIS TEAM.

OIL INDIA LTD.

sorry my query about point 5 was needless. checking on existing error still.

BTW is your os data getting refreshed now on SAP?

Regards.

Ruchit.

Is it possible you to re-register the saposcol service?

Hi Ruchit,

Though saposcol is shown running from ST06 , data is not refreshing from os.

Following is the output of ST06.

Tue Mar 13 16:38:30 2007 interval 10 sec.

CPU

Utilization user % 0 Count 0

system % 0 Load average 1 min 0.00

idle % 0 5 min 0.00

System calls/s 0 15 min 0.00

Interrupts/s 0 Context switches/s 0

Memory

Physical mem avail Kb 8386732 Physical mem free Kb 6791008

Pages in/s 0 Kb paged in/s 0

Pages out/s 0 Kb paged out/s 0

Pool

Commit charge limit Kb 35444320 Maximum swap-space Kb 29349888

Commit charge free Kb 27075100 Actual swap-space Kb 27254784

Disk with highest response time

Name Response time ms 0

Utilization 0 Queue 0

Avg wait time ms Avg service time ms 0

Kb transfered/s 0 Operations/s 0

Lan (sum)

No Data

BASIS TEAM.

OIL INDIA LTD.

Hi,

In St06 go to Operating system collector tab and then goto log file and check if it is showing any errors there. Alternative go to /usr/sap/tmp/dev_coll file and check.

please paste the logs here.

Regards.

Ruchit.

Message was edited by:

Ruchit Khushu

could i suggest you a simple tryout..

1) try to download latest version of SAPOSCOL from the SAP marketplace.

2) delete the serivce SAPOSCOL and register as service user (what was there as default before you change)

3) restart the OS ( no need but it would be nice if you do restart)

4) See the result and update us accordingly.

Cheers,

-Sunil

I as well think the solution suggested by Sunil is worth trying and should save a lot of time.

Regards.

Ruchit.

Hi ,

Log file is big one, however we are puting it below.

SAPOSCOL version COLL 20.89 700 - 20.53 NT 05/11/30, 32 bit, multithreaded, Non-Unicode

compiled at Jan 16 2006

systemid 560 (PC with Windows NT)

relno 7000

patch text COLL 20.89 700 - 20.53 NT 05/11/30

patchno 41

intno 20050900

running on SRMPROD Windows NT 5.2 3790 Service Pack 1 8x Intel 801586 (Mod 4 Step 1)

16:33:26 13.03.2007 LOG: Profile : no profile used

16:33:26 13.03.2007 LOG: Saposcol Version : [COLL 20.89 700 - 20.53 NT 05/11/30]

16:33:26 13.03.2007 LOG: Working directory : F:\usr\sap\PRFCLOG

16:33:26 13.03.2007 LOG: Allocate Counter Buffer [10000 Bytes]

16:33:26 13.03.2007 LOG: Allocate Instance Buffer [10000 Bytes]

16:33:26 13.03.2007 LOG: Shared Memory Size: 29074.

16:33:26 13.03.2007 LOG: Connected to existing shared memory.

16:33:26 13.03.2007 LOG: Reused shared memory. Clearing contents.

16:33:29 13.03.2007 LOG: Collector daemon started

16:33:29 13.03.2007 LOG: read coll.put Tue Mar 13 16:33:25 2007

16:33:29 13.03.2007 LOG: Collector PID: 9972

16:33:39 13.03.2007 LOG: Process Monitoring active.

16:33:39 13.03.2007 LOG: searching for Process Monitoring Templates in F:\usr\sap\PRFCLOG\dev_proc

16:33:39 13.03.2007 LOG: searching for Process Monitoring Templates in F:\usr\sap\PRFCLOG\procmon\

16:33:39 13.03.2007 LOG: The following processes will be monitored:

16:33:39 13.03.2007 LOG: Process: jlaunch-DSAPINFO=SRP_01_dispatcher* for user: SAPServiceSRP

16:33:39 13.03.2007 LOG: Process: jlaunch-DSAPINFO=SRP_01_server* for user: SAPServiceSRP

16:33:39 13.03.2007 LOG: Process: jlaunch-DSAPINFO=SRP_01_sdm* for user: SAPServiceSRP

16:40:36 13.03.2007 LOG: pfwnt1c.c: Error 997 [Overlapped I/O operation is in progress. ] from RegOpenKey failed on line 4500

16:40:36 13.03.2007 LOG: pfwnt1c.c: Error 997 [Overlapped I/O operation is in progress. ] from RegQueryValueEx on line 4510