Maximum sessions reached error

[Former Member]

Hi All

I am getting a strange error in Solution Manager system while trying to logon.

It gives an error: Maximum session reached and it does not allow to logon.

When I check Abap processes it can see lot of session opened which are not getting terminated:

The only way to logon for me is the restart the server.

But these processes are triggered again. I have patched the system to SP06 but still it is not resolved.

Please suggest what can to be done for this error?

I am suspecting some job is triggering this, but I am not sure which job.

Best Regards

Saurabh

[Former Member]

Hi Jansi

My kernel is already on latest release.

Please let me know what should be the parameters of heap size and buffer size.

I have already adjust profile parameters required for Solution Manager 7.1

Best Regards

Saurabh

[Former Member]

Hi

Please help on this issue.

Ratnajit is right that there are connections open, which I can see on Managed system DB which are creating locks on managed system DB.

These session create locks and go in suspended state.

Please advise.

Best Regards

Saurabh

[Former Member]

Hi All

I am getting this kind of entries in Traces files.

Sun Aug 26 14:54:42 2012

C  Thread ID:6484

C  Thank You for using the SLODBC-interface

C  Using dynamic link library 'K:\usr\sap\.....\DVEBMGS00\exe\dbmssslib.dll'

C  dbmssslib.dll patch info

C    SAP patchlevel  0

C    SAP patchno  201

C    Last MSSQL DBSL patchlevel 0

C    Last MSSQL DBSL patchno         201

C    Last MSSQL DBSL patchcomment Take care of warnings during database connect (1600066)

C  ODBC Driver chosen: SQL Server Native Client 10.0 native

C  Network connection used from RLF-SAPSOL-01 to RLF-SAPSOL-01\SQL01 using tcp:RLF-SAPSOL-01\SQL01

C  Network connection used from RLF-SAPSOL-01 to RLF-SAPSOL-01\SQL01 using tcp:RLF-SAPSOL-01\SQL01

C  Driver: sqlncli10.dll Driver release: 10.50.2500

C  GetDbRelease: 10.50.2500.00

C  GetDbRelease: Got DB release numbers (10,50,2500,0)

B  Connection 1 opened (DBSL handle 1)

B 

B Sun Aug 26 16:24:42 2012

B  Disconnected from connection 1, con_da={R/3*TIMESTAMP,13000039}

C 

C Sun Aug 26 16:44:44 2012

C  Thread ID:6484

C  Thank You for using the SLODBC-interface

C  Using dynamic link library 'K:\usr\....\DVEBMGS00\exe\dbmssslib.dll'

C  dbmssslib.dll patch info

C    SAP patchlevel  0

C    SAP patchno  201

C    Last MSSQL DBSL patchlevel 0

C    Last MSSQL DBSL patchno         201

C    Last MSSQL DBSL patchcomment Take care of warnings during database connect (1600066)

C  ODBC Driver chosen: SQL Server Native Client 10.0 native

C  Network connection used from RLF-SAPSOL-01 to RLF-SAPSOL-01\SQL01 using tcp:RLF-SAPSOL-01\SQL01

C  Network connection used from RLF-SAPSOL-01 to RLF-SAPSOL-01\SQL01 using tcp:RLF-SAPSOL-01\SQL01

C  Driver: sqlncli10.dll Driver release: 10.50.2500

C  GetDbRelease: 10.50.2500.00

C  GetDbRelease: Got DB release numbers (10,50,2500,0)

B  Connection 1 opened (DBSL handle 1)

B 

B Sun Aug 26 17:29:42 2012

B  Disconnected from connection 1, con_da={R/3*TIMESTAMP,13000042}

C 

C Sun Aug 26 17:34:42 2012

C  Thread ID:6484

C  Thank You for using the SLODBC-interface

C  Using dynamic link library 'K:\usr\sap\....\DVEBMGS00\exe\dbmssslib.dll'

C  dbmssslib.dll patch info

C    SAP patchlevel  0

C    SAP patchno  201

C    Last MSSQL DBSL patchlevel 0

C    Last MSSQL DBSL patchno         201

C    Last MSSQL DBSL patchcomment Take care of warnings during database connect (1600066)

C  ODBC Driver chosen: SQL Server Native Client 10.0 native

C  Network connection used from RLF-SAPSOL-01 to RLF-SAPSOL-01\SQL01 using tcp:RLF-SAPSOL-01\SQL01

C  Network connection used from RLF-SAPSOL-01 to RLF-SAPSOL-01\SQL01 using tcp:RLF-SAPSOL-01\SQL01

C  Driver: sqlncli10.dll Driver release: 10.50.2500

C  GetDbRelease: 10.50.2500.00

C  GetDbRelease: Got DB release numbers (10,50,2500,0)

B  Connection 1 opened (DBSL handle 1)

B 

B Sun Aug 26 17:54:42 2012

B  Disconnected from connection 1, con_da={R/3*TIMESTAMP

This goes on.

Please suggest if anyone have any idea of what is happening.

Best Regards

Saurabh

[Former Member]

Can Somone help me out here??

Regards

Saurabh

[Former Member]

Hi

is it the work process traces dev_w0?

if not please paste the dev_w0 logs.

Since it is the new installation, I could suggest you to review the abap heap size and buffer size parameters.

and also make sure you updated the kernal.

Thanks

Jansi

[former_member189725]

When this happens , investigate the database sessions , are they stuck up , check the database diagostic/alert  logs to investigate. Also check the work-process trace files .

The work processes are to be freed up as soon as the user session is idle . Also it seems some SQL statement is triggered which actually got hanged and as a result all the workprocesses were occupied .

Regards

Ratnajit

[Former Member]

Hi

I have tired restarting the Database and server but still no help.

Please suggest what can be the cause of this error.

Best Regards

Saurabh

[Former Member]

Hi,

it is a new installation or suddenly you get such issue,

What is your DB, if it oracle, proper environemtal variable sets, did you try to adjust the session parameter over there.

and only way you can trouble shoot, check the work process traces.

any DB error

Please paste this.

Thanks,

Jansi

[Former Member]

Hi

I have MS SQL DB. It is a new installation.

I have checked the trace files. I am not getting any DB error also.

Best Regards

Saurabh

[Vivek_Hegde]

Try restaring the whole system. ( including database)