Hi

      I am getting following error .     Process terminated by signal 0

     The current ABAP "SAPLSD41" program had to be terminated because the  

     ABAP processor detected an internal system error.          

        An R/3 System process was terminated by an operating system signal.                     

        -                                                                               

Possible reasons for this are:                                                          

        1. Internal system error.                                                               

        2. Process was terminated externally (by the system administrator).                     

           -                                                                               

Last error logged in SAP kernel                                                                               

Component............ "Taskhandler"                                                     

        Place................ "SAP-Server sugarland_DE1_11 on host sugarland (wp 1)"            

        Version.............. 1                                                                 

        Error code........... 11                                                                

        Error text........... "ThSigHandler: signal"                                            

        Description.......... " "                                                               

        System call.......... " "                                                               

        Module............... "thxxhead.c"                                                      

        Line................. 10852                                                                               

The error reported by the operating system is:        

How to correct the Error

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often        

contains a file called 'core'.                                                                               

Save this file under another name.                                                                               

If you cannot solve the problem yourself and want to send an error       

notification to SAP, include the following information:                                                                               

1. The description of the current problem (short dump)                                                                               

To save the description, choose "System->List->Save->Local File       

(Unconverted)".                                                                               

2. Corresponding system log                                                                               

Display the system log by calling transaction SM21.                   

   Restrict the time interval to 10 minutes before and five minutes      

after the short dump. Then choose "System->List->Save->Local File        

(Unconverted)".                                                                               

3. If the problem occurs in a problem of your own or a modified SAP                                        

        Error number..... " "                                                                   

Information on where terminated                                               

         Termination occurred in the ABAP program "SAPLSD41" - in "SYSTEM-EXIT".   

         The main program was "SAPMSRD0 ".                                                                               

In the source code you have the termination point in line 0               

         of the (Include) program " ".                                             

Need your advice on this?

Thanks

Srikanth

Dear Colleagues,

I am performing a homogeneous system copy of Solution Manager 7.1 SR1 on Windows Server 2008R2 and MSSQL 2008R2.

Source and Target Box have the same OS and DB version.

Now in the target system at phase START Instance ,I am getting error

I have perfromed R3trans -x with Kernel 720(UC) as well as after replacing with Kernel 720_EXT(UC) latest versions

but the error remains unaltered.

We have another ABAP instance running in the target box with Kernel 720_EXT (UC)

As a trail i have copied dbmssslib.dll from SAPEXE directory to C:/Windows/sysytem32 but it not help.

Another observation : In directory  C:\usr\sap\trans\bin

The TP_DOMAIN_S01.PFL is missing ,only the TP PFL for ABAP instance Q01 TP_DOMAIN_S01.PFL is available.

Attaching the R3trans -x log for your reference.

The disp+work gets stopped

R3trans Log RC=> 12:

4 ETW000 R3trans version 6.24 (release 720 - 10.10.13 - 20:13:08 ).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time   : 08.12.2013 - 10:45:17

4 ETW000 control file: <no ctrlfile>

4 ETW000 R3trans was called as follows: R3trans -d

4 ETW000  trace at level 2 opened for a given file pointer

4 ETW000  [     dev trc,00000]  Sun Dec 08 10:45:17 2013                                                9008  0.009008

4 ETW000  [     dev trc,00000]  db_con_init called                                                        60  0.009068

4 ETW000  [     dev trc,00000]  set_use_ext_con_info(): rsdb/ssfs_connect not set => ssfs not used       345  0.009413

4 ETW000  [     dev trc,00000]  determine_block_commit: no con_hdl found as blocked for con_name = R/3

4 ETW000                                                                                                  41  0.009454

4 ETW000  [     dev trc,00000]  create_con (con_name=R/3)                                                 25  0.009479

4 ETW000  [     dev trc,00000]  Loading DB library 'dbmssslib.dll' ...                                   336  0.009815

4 ETW000  [     dev trc,00000]  DlLoadLib success: LoadLibrary("dbmssslib.dll"), hdl 0, addr 0000000188360000

4 ETW000                                                                                               41324  0.051139

4 ETW000  [     dev trc,00000]      using "\\sapquality\sapmnt\S01\SYS\exe\uc\NTia64\dbmssslib.dll"       23  0.051162

4 ETW000  [     dev trc,00000]  Library 'dbmssslib.dll' loaded                                            26  0.051188

4 ETW000  [     dev trc,00000]  function DbSlExpFuns loaded from library dbmssslib.dll                    29  0.051217

4 ETW000  [     dev trc,00000]  Version of 'dbmssslib.dll' is "720.00", patchlevel (0.442)               426  0.051643

4 ETW000  [     dev trc,00000]  function dsql_db_init loaded from library dbmssslib.dll                   28  0.051671

4 ETW000  [     dev trc,00000]  function dbdd_exp_funs loaded from library dbmssslib.dll                  22  0.051693

4 ETW000  [     dev trc,00000]  New connection 0 created                                                  48  0.051741

4 ETW000  [     dev trc,00000]  0: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog = 

4 ETW000                                                                                                  44  0.051785

4 ETW000  [     dev trc,00000]  db_con_connect (con_name=R/3)                                             35  0.051820

4 ETW000  [     dev trc,00000]  determine_block_commit: no con_hdl found as blocked for con_name = R/3

4 ETW000                                                                                                  29  0.051849

4 ETW000  [     dev trc,00000]  find_con_by_name found the following connection:                          20  0.051869

4 ETW000  [     dev trc,00000]  0: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog = 

4 ETW000                                                                                                  40  0.051909

4 ETW000  [     dev trc,00000]  Thread ID:9316                                                          1311  0.053220

4 ETW000  [     dev trc,00000]  Thank You for using the SLODBC-interface                                  29  0.053249

4 ETW000  [     dev trc,00000]  Using dynamic link library '\\sapquality\sapmnt\S01\SYS\exe\uc\NTia64\dbmssslib.dll'

4 ETW000                                                                                                  41  0.053290

4 ETW000  [     dev trc,00000]  dbmssslib.dll patch info                                                  66  0.053356

4 ETW000  [     dev trc,00000]    SAP patchlevel  0                                                       25  0.053381

4 ETW000  [     dev trc,00000]    SAP patchno  500                                                       127  0.053508

4 ETW000  [     dev trc,00000]    Last MSSQL DBSL patchlevel 0                                            23  0.053531

4 ETW000  [     dev trc,00000]    Last MSSQL DBSL patchno         442                                     23  0.053554

4 ETW000  [     dev trc,00000]    Last MSSQL DBSL patchcomment DBACOCKPIT Auto-injection fails (1901875)

4 ETW000                                                                                                  33  0.053587

4 ETW000  [     dev trc,00000]  ODBC Driver chosen: SQL Server Native Client 10.0 native                1698  0.055285

4 ETW000  [     dev trc,00000]  Network connection used from SAPQUALITY to (local) using tcp:(local)

4 ETW000                                                                                                 518  0.055803

4 ETW000  [     dev trc,00000]  Network connection used from SAPQUALITY to (local) using tcp:(local)

4 ETW000                                                                                              166019  0.221822

4 ETW000  [     dev trc,00000]  Network connection used from SAPQUALITY to (local) using tcp:(local)

4 ETW000                                                                                                7713  0.229535

4 ETW000  [     dev trc,00000]  Driver: sqlncli10.dll Driver release: 10.50.2769                        7203  0.236738

4 ETW000  [     dev trc,00000]  GetDbRelease: 10.50.2769.00                                             1127  0.237865

4 ETW000  [     dev trc,00000]  GetDbRelease: Got DB release numbers (10,50,2769,0)                       72  0.237937

4 ETW000  [     dev trc,00000]  ERROR : master database cannot be used by DBSL.                         8036  0.245973

2EETW169 no connect possible: "DBMS = MSSQL                            ---  SERVER = 'SAPQUALITY' DBNAME = ''"

Please guide.

Thanks and Regards

Asadul

DEAR ALL

DO FOCUS APPLICATION WITH SQL DATABSE CAN BE SHIFT TO SAP WITH MYSQL DATABASE

CAN THIS IS POSSIBLE WITH HETEROGENEOUS  SYSTEM COPY OR ANY OTHER WAY

PLZ DO SUGGEST OR SEND DOCUMENT IF ALREADY THERE.

THANKS IN ADVANCE

BEST REGARDS

SANATH

Dear All

We have migrated the QA BI system to HA system by using the system copy method backup/restore. After that we have do the basis configuration step of TMS. At the time of importing the request from DE B I to QA BW we are getting hang. in the TPlog. regarding the i am already go thru  the below notes

Note 642464 - Profile file for the program sapevt

Note 821875 - Security settings in the message server

Note 802172 - sapevt (Version 4): Release-independent version

Is this any other way we resolve the issue?

Kindly help us

___________________________________________________________________

TP Log

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System QBW. Warning.        20110815090525 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

       Please check that the R/3 system is running.

       Please check the system. Use transactions SM21, SM37, SM50.

WARNING:       (This warning is harmless if no further warnings follow.)

WARNING: System QBW. Warning.        20110815090538 :

WARNING:       Background job RDDIMPDP could not be started or terminated abnormally.

_____________________________________________________________________

Regards

Sriram

Hello,

Can you help me to understand and solve one problem related with tempdb in SQL Server 2008!?

Our SAP system sometimes shows some short-dumps: START_CALL_SICK (Database inconsistency: Start Transaction SICK). In SM21 I see the following error:

Database error 9002 at OPC

> The transaction log for database 'tempdb' is full. To fin

> out why space in the log cannot be reused, see the

> log_reuse_wait_desc column in sys.databases

Database error 9002

When I try to open the properties of the database through SQL Management Studio I see the following error:

I checked the the tempdb disk (5Gb) and in fact it´s full, but I can´t change the disk size...:

Can you tell me why this templog.ldf increased a lot? It´s possible to change the size of this templog.ldf file? How can I disable the option of autogrowth of tempdb? It´s possible?

Kind regards,

samid raif

Hi All,

We have been facing lot of memory issues in production system and QA ECC ABAP only system after kernel upgrade from Basis 700 patch 310 to 347. Is there any known issue with this release? Users are not able to login then and there. We have all parameters set as per Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel and Note 88416 - Zero administration memory management for the ABAP server. Our platform: 64 bit windows 2003 server/sql2005. I referred note Note 307976 - PXA_NO_SHARED_MEMORY and our abap buffersize is 1300000KB. Physical memory is 24GB. Do I have to increase the physical memory? System was much better before this kernel upgrade for add-on Vistex installation. Then so many memory related issues.

There are also other dumps like SYSTEM_CORE_DUMPED, STORAGE_PARAMETERS_WRONG_SET

"In the system profile, set the parameters

-abap/heap_area_dia and

-abap/heap_area_nondia

to a maximum of

1731363904. To be on the safe side, reduce the value by 10,000,

000."

But parameter values are kept standard from the above mentioned Notes. Please help ASAP.

Thanks,

Kavitha Rajan.

Hi

      I am getting following error .     Process terminated by signal 0

     The current ABAP "SAPLSD41" program had to be terminated because the  

     ABAP processor detected an internal system error.          

        An R/3 System process was terminated by an operating system signal.                     

        -                                                                               

Possible reasons for this are:                                                          

        1. Internal system error.                                                               

        2. Process was terminated externally (by the system administrator).                     

           -                                                                               

Last error logged in SAP kernel                                                                               

Component............ "Taskhandler"                                                     

        Place................ "SAP-Server sugarland_DE1_11 on host sugarland (wp 1)"            

        Version.............. 1                                                                 

        Error code........... 11                                                                

        Error text........... "ThSigHandler: signal"                                            

        Description.......... " "                                                               

        System call.......... " "                                                               

        Module............... "thxxhead.c"                                                      

        Line................. 10852                                                                               

The error reported by the operating system is:        

How to correct the Error

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often        

contains a file called 'core'.                                                                               

Save this file under another name.                                                                               

If you cannot solve the problem yourself and want to send an error       

notification to SAP, include the following information:                                                                               

1. The description of the current problem (short dump)                                                                               

To save the description, choose "System->List->Save->Local File       

(Unconverted)".                                                                               

2. Corresponding system log                                                                               

Display the system log by calling transaction SM21.                   

   Restrict the time interval to 10 minutes before and five minutes      

after the short dump. Then choose "System->List->Save->Local File        

(Unconverted)".                                                                               

3. If the problem occurs in a problem of your own or a modified SAP                                        

        Error number..... " "                                                                   

Information on where terminated                                               

         Termination occurred in the ABAP program "SAPLSD41" - in "SYSTEM-EXIT".   

         The main program was "SAPMSRD0 ".                                                                               

In the source code you have the termination point in line 0               

         of the (Include) program " ".                                             

Need your advice on this?

Thanks

Srikanth

I submit that a dump on my system, when running a job SAP_COLLECTOR_FOR_PERFMONITOR,

===========================================================================

JOb Error:

===========================================================================

Job started                                                                               

Step 001 started (program RSCOLL00, variant , user ID MGBAUTE)                               

Clean_Plan:Cleanup of DB13 Plannings                                                         

Clean_Plan:started by RSDBPREV                                                               

Clean_Plan:Jobs in System R3D      werden bereinigt                                          

You are not authorized for DB access (S_DBCON: <LOCAL SYSTEM> R3D <Windows authentication> 03)

Function DB6_PLAN_STOP_BATCH_JOB failed with return code = Job error                         

Clean_Plan:terminated with error                                                             

REASON=Job error                                                                             

ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW                                                 

Job cancelled                                                                               

===========================================================================

ST22 "Abap Dump"

===========================================================================

Runtime Errors         COMPUTE_INT_TIMES_OVERFLOW                                  

Exception              CX_SY_ARITHMETIC_OVERFLOW                                   

Date and Time          03.06.2009 08:43:12                                                                               

Short text                                                                        

     Whole number overflow on multiplication.                                                                               

What happened?                                                                    

     Error in the ABAP Application Program                                                                               

The current ABAP program "RSMSQSNP" had to be terminated because it has       

     come across a statement that unfortunately cannot be executed.                                                                               

What can you do?                                                                  

     Note down which actions and inputs caused the error.                                                                               

To process the problem further, contact you SAP system                        

     administrator.                                                                               

Using Transaction ST22 for ABAP Dump Analysis, you can look                   

     at and manage termination messages, and you can also                          

     keep them for a long time.                                                                               

Error analysis                                                                    

     An exception occurred that is explained in detail below.                      

     The exception, which is assigned to class 'CX_SY_ARITHMETIC_OVERFLOW', was not

      caught in                                                                    

     procedure "GET_ELAPSEDSECS" "(FORM)", nor was it propagated by a RAISING      

      clause.                                                                      

     Since the caller of the procedure could not have anticipated that the         

exception would occur, the current program is terminated.                        

The reason for the exception is:                                                 

In the current program "RSMSQSNP", multiplying the numbers 733562 and            

86400 (using the operation '*' or 'MULTIPLY') resulted in a value                

greater than 2147483647 or smaller than -2147483648. This                        

results in a whole number overflow.                                                                               

to correct the error                                                             

It may be possible to break the current process down into subprocesses           

so that only smaller values occur.                                                                               

If the error occurred in your own ABAP program or in an SAP                      

program you modified, try to remove the error.                                                                               

If the error occures in a non-modified SAP program, you may be able to           

find an interim solution in an SAP Note.                                         

If you have access to SAP Notes, carry out a search with the following           

keywords:                                                                               

"COMPUTE_INT_TIMES_OVERFLOW" "CX_SY_ARITHMETIC_OVERFLOW"                         

"RSMSQSNP" or "RSMSQSNP"                                                         

"GET_ELAPSEDSECS"                                                                

System environment                                                               

    SAP-Release 700                                                                               

Application server... "srvctrsapd01"                                         

    Network address...... "200.200.1.2"                                          

    Operating system..... "Windows NT"                                           

    Release.............. "5.2"                                                  

    Hardware type........ "4x Intel 80686"                                       

    Character length.... 8 Bits                                                  

    Pointer length....... 32 Bits                                                

    Work process number.. 15                                                     

    Shortdump setting.... "full"                                                                               

Database server... "SRVCTRSAPD01"                                            

    Database type..... "MSSQL"                                                   

    Database name..... "R3D"                                                     

    Database user ID.. "r3d"                                                                               

Char.set.... "Spanish_Spain.1252"                                                                               

SAP kernel....... 700                                                        

    created (date)... "Aug 25 2008 01:11:49"                                     

    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"             

    Database version. "SQL_Server_8.00 "                                                                               

Patch level. 175                                                             

    Patch text.. " "                                                                               

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"             

    SAP database version. 700                                                    

    Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

     NT 6.0"                                                                     

Termination occurred in the ABAP program "RSMSQSNP" - in "GET_ELAPSEDSECS". 

The main program was "RSMSQSNP ".                                                                               

In the source code you have the termination point in line 205               

of the (Include) program "RSMSQSNP".                                        

The program "RSMSQSNP" was started as a background job.                     

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                             

Job Initiator.. "MGBAUTE"                                                   

Job Number..... 07431004                                                    

The termination is caused because exception "CX_SY_ARITHMETIC_OVERFLOW"     

occurred in                                                                

procedure "GET_ELAPSEDSECS" "(FORM)", but it was neither handled locally nor

declared                                                                   

in the RAISING clause of its signature.                                                                               

The procedure is in program "RSMSQSNP "; its source code begins in line     

172 of the (Include program "RSMSQSNP ".                                    

Thank and regards for your help.

Gustavo Gonzalez.

Hello,

Can you help me to understand and solve one problem related with tempdb in SQL Server 2008!?

Our SAP system sometimes shows some short-dumps: START_CALL_SICK (Database inconsistency: Start Transaction SICK). In SM21 I see the following error:

Database error 9002 at OPC

> The transaction log for database 'tempdb' is full. To fin

> out why space in the log cannot be reused, see the

> log_reuse_wait_desc column in sys.databases

Database error 9002

When I try to open the properties of the database through SQL Management Studio I see the following error:

I checked the the tempdb disk (5Gb) and in fact it´s full, but I can´t change the disk size...:

Can you tell me why this templog.ldf increased a lot? It´s possible to change the size of this templog.ldf file? How can I disable the option of autogrowth of tempdb? It´s possible?

Kind regards,

samid raif

Hi

      I am getting following error .     Process terminated by signal 0

     The current ABAP "SAPLSD41" program had to be terminated because the  

     ABAP processor detected an internal system error.          

        An R/3 System process was terminated by an operating system signal.                     

        -                                                                               

Possible reasons for this are:                                                          

        1. Internal system error.                                                               

        2. Process was terminated externally (by the system administrator).                     

           -                                                                               

Last error logged in SAP kernel                                                                               

Component............ "Taskhandler"                                                     

        Place................ "SAP-Server sugarland_DE1_11 on host sugarland (wp 1)"            

        Version.............. 1                                                                 

        Error code........... 11                                                                

        Error text........... "ThSigHandler: signal"                                            

        Description.......... " "                                                               

        System call.......... " "                                                               

        Module............... "thxxhead.c"                                                      

        Line................. 10852                                                                               

The error reported by the operating system is:        

How to correct the Error

The R/3 System work directory (e.g. /usr/sap/c11/D00/work ) often        

contains a file called 'core'.                                                                               

Save this file under another name.                                                                               

If you cannot solve the problem yourself and want to send an error       

notification to SAP, include the following information:                                                                               

1. The description of the current problem (short dump)                                                                               

To save the description, choose "System->List->Save->Local File       

(Unconverted)".                                                                               

2. Corresponding system log                                                                               

Display the system log by calling transaction SM21.                   

   Restrict the time interval to 10 minutes before and five minutes      

after the short dump. Then choose "System->List->Save->Local File        

(Unconverted)".                                                                               

3. If the problem occurs in a problem of your own or a modified SAP                                        

        Error number..... " "                                                                   

Information on where terminated                                               

         Termination occurred in the ABAP program "SAPLSD41" - in "SYSTEM-EXIT".   

         The main program was "SAPMSRD0 ".                                                                               

In the source code you have the termination point in line 0               

         of the (Include) program " ".                                             

Need your advice on this?

Thanks

Srikanth

Hi,

Our development system is down as we are getting the short dump while executing any updated program or when accessing table contents.

While activating a program we get the same dump error.

I have attached the screen shot of the dump error.

Please help.

Regards,

Rekha

Hi All,

We have installed SAP EHP6 system on MS SQL 2008 R2, Since it was development system we have kept in simple mode.

But still we find the Transaction log is growing daily and cannot  truncate the log.

I found the  below reuse wait reason as Replication.

Recovery model          SIMPLE

Reuse wait reason       REPLICATION

Do we have DB setting as above as default  when we install MS SQL or any DB consultant has changed any parameter.

And also how can we remove Replication for Transaction Log.

Regards,

Kiran

Hi,

we are getting below dump while the user executing the IW32 transaction, please advice me

Short text
    The current application triggered a termination with a short dump.

What happened?
    The current application program detected a situation which really
    should not occur. Therefore, a termination with a short dump was
    triggered on purpose by the key word MESSAGE (type X).

What can you do?
    Note down which actions and inputs caused the error.

    To process the problem further, contact you SAP system
    administrator.

    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.

Error analysis
    Short text of error message:
    Program error (contact your system administrator)

    Long text of error message:
     Diagnosis
         An internal error has occurred.
     System Response
         Processing stopped.
     Procedure
         Contact your system administrator.
         If possible, send all relevant documents to SAP for analysis.

    Technical information about the message:
    Message class....... "CO"
    Number.............. 901
    Variable 1.......... " "
    Variable 2.......... " "
    Variable 3.......... " "
    Variable 4.......... " "

Hi Guys,

I am trying to connect to one of the SQL Server in my Domain. I have made entries as mentioned by SAP note in DBCO Transaction. When I am testing connection through program 'ADBC_TEST_CONNECTION' it is showing me following error:

Testing a Database Connection Defined in DBCON

Could not open connection SQLCONNECTION

sql error          1- occured:

I have already installed DBMSSSLIB.DLL in executable directory also.

Please advice.

Thanks,

Usman Malik

Hi community,

We are running SAP EHP 1 for SAP Solution Manager 7.0 on MS SQL Server 2005 Release 9.00.3042  DB.

From this morning without install/update/change nothing, we have got on systemlog and trace data, lot of entries with this detail:

Database error 7719 at EXE

ExecuteAndFlush return code: 0x80040e14 Stmt: [ALTER PARTITION FUNCTION [/BI0/F0SMD_PE2H_PFUN0]() SPLIT RANGE (0000001009) ]

sloledb.cpp [ExecuteAndFlush,line 6678]: Error/Message: (err 7719, sev 0), CREATE/ALTER partition function failed as only a maxim

Procname: [ExecuteAndFlush - no proc]

DbSlExecute - Error 99 (dbcode 7719) on DDLExecute

DbSlExecute - <ALTER PARTITION FUNCTION [/BI0/F0SMD_PE2H_PFUN0]() SPLIT RANGE (0000001009) >

dbdsmss: DBSL99 SQL7719

CREATE/ALTER partition function failed as only a maximum of 1000 partitions can be created.

***LOG BY2=> sql error 7719       performing EXE        [dbds#2 @ 699] [dbds    0699 ]

***LOG BY0=> CREATE/ALTER partition function failed as only a maximum of 1000 partitions can be created. [dbds#2 @ 699] [dbds

***LOG BY2=> sql error 7719       performing EXE        [dbacds#2 @ 893] [dbacds  0893 ]

On SE14 I found anything whit the name /BI0/F0SMD_PE2H table and function /BI0/F0SMD_PE2H_PFUN0. Check option was succesfully but indicates number of partitions =1000.

After look for any similar situation, I didn't found nothing except this SDN Thread: BI : msg " Database error 7719 at EXE " during loading Here the solution applied is not valid to our system because the OSS Note 1494789 - Enabling 1000+ partitions support on SQL Server is by SQL Server 2008 SP2 (not our version).

On OSS Note 1010854 - Table with too many partitions on SQL Server 2005/2008 I am not really sure about if the solution(symptom2)  fits to our problem.

And on OSS Note Note 869407 - Partitioning on Microsoft SQL Server i didn't correct with tool RSDD_MSSQL_CUBEANALYZE because we don't have enabled the (vardecimal) compression.

Do you know how can I achive this error???

Thanks in advance!

Scottie

Hi

I´m in the process of a abab java split.

I have done all the step´s until create central instance.  This step fails with the error A key/value pair with this key already exists in the store.

I have try´d a few things renamed the files in the SECstore.key and Secstore.properties.  I have done a uninstall of the java but still get the same error.

I have look´d for and error in the  keydb.xml put did not find that.

The secstorefiles get created when I create the database.

I´m stuck so help would be nice.

hi everyone,

        plz find the below attached screen shot.. i got an error while installing ecc6 ehp5 at import abap phase..can anyone suggest me the solution...

Hi experts,

  I install a non shared disk cluster on SQL 2012 AlwaysOn like the procedure below. It runs on first node without any problems.

However, when I fail over ASCS to second node, I always get an error: login not possible(error in license check). I check every item in the KBA: 1512766 and I find it can't connect to MS on second node. I try to restart SAP servers but the problem persists, please help.

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

Thu Aug 22 17:58:59 2013

***LOG Q0I=> NiPConnect2: 10.243.23.60:3901: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3286]

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 17/sock 1232

    (SI_ECONN_REFUSE/10061; I4; ST; 10.243.23.60:3901) [nixxi.cpp    3286]

*** ERROR => MsIAttachEx: NiBufConnect to sapgrptcd/3901 failed (rc=NIECONN_REFUSED) [msxxi.c 718]

***LOG Q0L=> DpLoopInit, nomscon () [dpxxdisp.c   1801]

CCMS: SemInMgt: Semaphore Management initialized by AlAttachShm_Doublestack.

CCMS: SemInit: Semaphore 38 initialized by AlAttachShm_Doublestack.

CCMS: start to initalize 3.X shared alert area (first segment).

DpAppcBlksLow: max appc blocks in queue is 1000 (50 %)

DpWpBlksLow: max wp blocks in queue is 1600 (80 %)

Thu Aug 22 17:59:40 2013

***LOG Q0I=> NiPConnect2: 10.243.23.60:3901: connect (10061: WSAECONNREFUSED: Connection refused) [nixxi.cpp 3286]

*** ERROR => NiPConnect2: SiPeekPendConn failed for hdl 49/sock 1544

    (SI_ECONN_REFUSE/10061; I4; ST; 10.243.23.60:3901) [nixxi.cpp    3286]

*** ERROR => MsIAttachEx: NiBufConnect to sapgrptcd/3901 failed (rc=NIECONN_REFUSED) [msxxi.c 718]

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

First node downtime:

1. 1.     1. 70SWPM -> System copy -> First node
2. 2.     2. Change dbs/mss/server & SAPDBHOST to node 1
3. 3.     3. 70SWPM -> System copy -> Database instance

Second node downtime:

1. 1.     4. 70SWPM -> System copy -> Additional node
2. 2.     5. Change SAPDBHost and dbs/mss/server to AG Listener

  6.     Sp_help_revlogin + add sysadmin role for SAPserivce<SID> + SWPM(7.3) -> Database copy completion

HI EXPERTS I TRY TO IMPORT A SUPPORT PACKAGE IN SOLMAN WINDOWS SERVER 2008 R2 WITH SQL SERVER 2008 R2 BUT A I CANu00B4T BECAUSE THE USER <SID>ADM DONT HAVE PERMISION TO LOGON DB. I APLIED R3trans.exe -d WITH THE USER <SID>ADM AND AS A RESULT IS THAT:

4 ETW000 E:\usr\sap\slm\sys\exe\uc\NTAMD64\R3trans.exe version 6.14 (release 701 - 23.07.10 - 09:23:00).

4 ETW000 unicode enabled version

4 ETW000 ===============================================

4 ETW000

4 ETW000 date&time   : 18.08.2011 - 14:44:43

4 ETW000 control file: <no ctrlfile>

4 ETW000 R3trans was called as follows: E:\usr\sap\slm\sys\exe\uc\NTAMD64\R3trans.exe -d

4 ETW000  trace at level 2 opened for a given file pointer

4 ETW000  [dev trc     ,00000]  Thu Aug 18 14:44:46 2011                                               11769  0.011769

4 ETW000  [dev trc     ,00000]  db_con_init called                                                        25  0.011794

4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                                                633  0.012427

4 ETW000  [dev trc     ,00000]  Loading DB library 'dbmssslib.dll' ...                                    52  0.012479

4 ETW000  [dev trc     ,00000]  DlLoadLib success: LoadLibrary("dbmssslib.dll"), hdl 0, addr 0000000186BB0000

4 ETW000                                                                                139786  0.152265

4 ETW000  [dev trc     ,00000]      using "E:\usr\sap\slm\sys\exe\uc\NTAMD64\dbmssslib.dll"               16  0.152281

4 ETW000  [dev trc     ,00000]  Library 'dbmssslib.dll' loaded                                            18  0.152299

4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library dbmssslib.dll                    19  0.152318

4 ETW000  [dev trc     ,00000]  Version of 'dbmssslib.dll' is "700.08", patchlevel (0.117)              3239  0.155557

4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library dbmssslib.dll                   29  0.155586

4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library dbmssslib.dll                  21  0.155607

4 ETW000  [dev trc     ,00000]  New connection 0 created                                                  31  0.155638

4 ETW000  [dev trc     ,00000]  000: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,

4 ETW000                             reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000                                                                                49  0.155687

4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                                             24  0.155711

4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:                16  0.155727

4 ETW000  [dev trc     ,00000]  000: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , hc = NO , perm = YES,

4 ETW000                             reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO

4 ETW000                                                                                44  0.155771

4 ETW000  [dev trc     ,00000]  Thread ID:7748                                                         16461  0.172232

4 ETW000  [dev trc     ,00000]  Thank You for using the SLODBC-interface                                  24  0.172256

4 ETW000  [dev trc     ,00000]  Using dynamic link library 'E:\usr\sap\slm\sys\exe\uc\NTAMD64\dbmssslib.dll'

4 ETW000                                                                                32  0.172288

4 ETW000  [dev trc     ,00000]  dbmssslib.dll patch info                                                  27  0.172315

4 ETW000  [dev trc     ,00000]    SAP patchlevel  0                                                       16  0.172331

4 ETW000  [dev trc     ,00000]    SAP patchno  117                                                        15  0.172346

4 ETW000  [dev trc     ,00000]    Last MSSQL DBSL patchlevel 0                                            19  0.172365

4 ETW000  [dev trc     ,00000]    Last MSSQL DBSL patchno         117                                     29  0.172394

4 ETW000  [dev trc     ,00000]    Last MSSQL DBSL patchcomment Tables ########## in SM50 or SM66 (1523684)

4 ETW000                                                                                77  0.172471

4 ETW000  [dev trc     ,00000]  lpc:(local) connection used on SMAPORTA                                 3990  0.176461

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                42813  0.219274

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.219305

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2399  0.221704

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.221735

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2398  0.224133

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.224164

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                3724  0.227888

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                32  0.227920

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2440  0.230360

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.230391

4 ETW000  [dev trc     ,00000]  ERROR: -1 in function SQLConnectWithRetry (SQLConnectWithRetry) [line 2285]

4 ETW000                                                                                2433  0.232824

4 ETW000  [dev trc     ,00000]  (18456) [28000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'.

4 ETW000                                                                                31  0.232855

4 ETW000  [dev trc     ,00000]  Connection 0 failed using Driver={SQL Server Native Client 10.0};Server=SMAPORTA;AutoTranslate=no;Trusted_Connection=yes;WSID=SMAPORTA;APP=R3 00 comm rd ODBC;Database=SLM;

4 ETW000                                                                                41  0.232896

4 ETW000  [dblink      ,00433]  ***LOG BY2=>sql error 18456  performing CON [dblink#4 @ 433]            8207  0.241103

4 ETW000  [dblink      ,00433]  ***LOG BY0=>[Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'SMAPORTA\slmadm'. [dblink#4 @ 433]

4 ETW000                                                                                42  0.241145

2EETW169 no connect possible: "DBMS = MSSQL                            ---  SERVER = 'SMAPORTA' DBNAME = 'SLM'"

PLEASE HELP ME EXPERTS!!!

Good Evening  My Dear Friends....

My Scenario :

I set the Approval procedure for Purchase Order Document

I want to Block the PO for going to approval via transaction notification ,if The Purchase order line containing Project and Dist.rule field will be empty.

Note the point:

I can able to Block PO,if it does'nt apply approval,My problem is that,A new window will open for approval applied PO when click on the add button. So,I can't able to manage the Docentry of that PO.

So,I am Expecting helpful query from my dearest friends...