MS SQL Server - System Copy Error (post load activitities Step)

[Former Member]

hello Gurus,

We are doing a system copy on SQL Server 2005 to create a new Test Instance, at the post load step the following error stop the procces:

WARNING[E] 2010-01-13 19:52:44.906

CJSlibModule::writeError_impl()

CJS-30023 Process call 'D:\usr\sap\RB3\SYS\exe\uc\NTI386\dipgntab.exe -rwr40 -srctt DDNTT -srctf DDNTF -dsttt DDNTT -dsttf DDNTF -ttonly TT' exits with error code -1. For details see log file(s) dipgntab.log.

TRACE 2010-01-13 19:52:44.906 [iaxxejsbas.hpp:483]

EJS_Base::dispatchFunctionCall()

JS Callback has thrown unknown exception. Rethrowing.

ERROR 2010-01-13 19:52:44.921 [sixxcstepexecute.cpp:951]

FCO-00011 The step adjustNametab with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_Postload|ind|ind|ind|ind|10|0|NW_Postload_MSS|ind|ind|ind|ind|2|0|adjustNametab was executed with status ERROR .

The file dipgntab.log anly contain:

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

Before the system copy process we upgrade the SQL Server from 2000 to 2005.

How we can fix this error and continue the system copy?

Thanks

Hernando

Edited by: Hernando Polania Cadena on Jan 14, 2010 2:32 AM

[Former Member]

Error in DB

[Former Member]

What was the error in DB, did you guys fix it.

Thanks

[Former Member]

>

> The file dipgntab.log anly contain:

>

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

>

> Before the system copy process we upgrade the SQL Server from 2000 to 2005.

>

Hi Hernando,

What is your source system configuration and what is your target system configuration ?

Like - Hardware = 32 bit or 64 bit ?

database = SQL 2000 or SQL 2005 ?

SAP version ?

-Rohit

[Former Member]

hello,

the syste is Ecc 6.0, OS windows 2003 server 32 bit and DB MS SQL Server 2005. We are trying to do a system copy to create a new instance (sandbox) in the same server, attaching the files from copy of the source system.

Hernando

[ken_halvorsen2]

Hi Hernando

Are the target and source systems exactly the same? Meaning they are both at the same level and patches. Is the backup used to restore from at the same level as the Target system?

Are they both Unicode or non-unicode? (I've had this happen when we had a non-unicode source system with a unicode target system)

Did you run the SAPInst.exe successfully, to do the post restore process?

Ken

[Former Member]

hello,

the systems are the same, the target system is copy (attach/Deattach) from source system, the system is unicode.

The SAPINst stop in this step but we couldn't find how to fix this error.

Hernando