System copy ended with errors

[Former Member]

Hi Gurus,

I am doing the system copy of ABAP + Java running on Windows 2008 with SQL server 2008.

During import at target system I am getting the below error at Post Load activities.

*sapinst.log*

E:\usr\sap\BPD\SYS\exe\uc\NTAMD64\dipgntab.exe -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT is written to the logfile dipgntab.log

dipgntab.log

Here's the short version of the dipgntab.log:

ERROR in initialization (can't get R/3-version)

ERROR in initialization (can't get R/3-version)

E:\usr\sap
D00\log\SLOG00.LOG: No such file or directory

rslgwr1(20): rstrbopen cannot open pre-existing SysLog file.

E:\usr\sap
D00\log\SLOG00.LOG: No such file or directory

rslgwr1(11): rstrbopen cannot open SysLog file.

I have tried the below steps.

1) The environment variable MSSQL_FORCEOLEDB = 1 has to be set for the userID performing the installation

2) Kernel upgrade.

Any help would be highly appreciable.

Thanks,

Akram

[Former Member]

>

> ERROR in initialization (can't get R/3-version)

> ERROR in initialization (can't get R/3-version)

> E:\usr\sap
D00\log\SLOG00.LOG: No such file or directory

> rslgwr1(20): rstrbopen cannot open pre-existing SysLog file.

> E:\usr\sap
D00\log\SLOG00.LOG: No such file or directory

> rslgwr1(11): rstrbopen cannot open SysLog file.

Dear Akram

Can you check what files are exported from the source system while performing system copy.

Also, if you run sapinst on target system it asks you system copy using standard method or attach/detach method.

Which is selected?

Regards

Khalid

[markus_doehr2]

Did the source system run on the same database version? Did you do an R3load copy or database copy?

Markus

[Former Member]

I'm seeing the same exact error:

ERROR in initialization (can't get R/3-version)

E:\usr\sap
D00\log\SLOG00.LOG: No such file or directory

rslgwr1(20): rstrbopen cannot open pre-existing SysLog file

This is Netweaver 7.0 SR3, MS SQL 2005 with JDK 1.4.2_17 and doing system copy on target Win2003). I upgraded JDK from 10 to 17, and added the MSSQL_FORCEOLEDB = 1 variable..I tried re-booting the server, and run sapinst as <sid>adm but no luck.Currently using the 'adminstrator' id for sapinst. Has anybody seen a fix to this error? any suggestion?

Thanks!

John

[Former Member]

Hi Marcus,

Any reason why you asked:

"Did the source system run on the same database version? Did you do an R3load copy ?"

In my case they are both the same DB - MS SQL 2005 and I'm using R3load copy. I know its a homogeneous system copy, but this is just a test migration for my own documentation.

Thanks!

[Former Member]

Hi JOhn,

Try to run import with user sidadm and hopefully it will resolve your issue.

Thanks,

ND