cancel
Showing results for 
Search instead for 
Did you mean: 

problem with system copy crm 7.01

0 Kudos

Hey,

today i tried my first system copy over SWPM on Windows 2003 r2 / SQL 2005

at ABAP Export on step  "testing database connection" i get following error message r3load.exe -testconnect exists with error code 2 see log files. log file in attached.

i tried it via cmd too

(DB) ERROR: db connect rc = 256

(DB) ERROR: DbSlErrorMsg rc = 99

i got the newest kernel (721) and set up following environment settings:

DBMS_TYPE                          MSS

MSSQL_SERVER                    MSSQLSERVER

MSSQL_DBNAME                   <sid>    

MSSQL_SCHEMA                   <sid>

MSSQL_USER                        <sid>adm

MSSQL_PASSWD                  pass

MSSQL_FORCEOLEDB          1

that was all i can find in notes or other entries. Please help me

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Run connection to DB test with R3trans -x and check trans.log file for errors.

Sriram2009
Active Contributor
0 Kudos

Hi Steffen

Kindly go thru the SAP  Knowledge Base Article

1875902  - R3load -testconnect fails during system export

1595787  - Distribution Monitor - Execution of 'R3load Testconnect' failed

Thanks

Sriram

Knowledge Base Article

Former Member
0 Kudos

Hi Steffen,

what does the trans.log file say when you execute:

R3trans -x

You mentioned you set

DBMS_TYPE                          MSS

MSSQL_SERVER                    MSSQLSERVER

MSSQL_DBNAME                   <sid>    

MSSQL_SCHEMA                   <sid>

MSSQL_USER                        <sid>adm

MSSQL_PASSWD                  pass

MSSQL_FORCEOLEDB          1

Remove these, you don't need them:

MSSQL_USER, MSSQL_PASSWD

When you say you've set MSSQL_SERVER = <sid> I'm not sure what your setting looks like... have you used uppercase? You need to, because it's case sensitive and the <SID> DB created by SAP is always uppercase.

Regards,

Beate

former_member206552
Active Contributor
0 Kudos

hi steffen

duplicate thread

please try the solution suggested in http://scn.sap.com/thread/3345107

Please set  environmental variable MSSQL_FORCEOLEDB=1 in your database instance.

source = http://scn.sap.com/thread/1639404

best regards

marius