Skip to Content
avatar image
Former Member

R3Trans error 0012 on shifting DB to a new host

Hi,

We have a Discovery system with WAS and SQL2005 sitting on the same system. We're trying to move the DB to a new System.

We have been able to connect to our New SQL2005 host and our ABAP interface is working fine, even the portal is working fine. However when we try to test our TMS using the new DB server it gives an error, some notes suggested that we run R3Trans –d first and this is the error message that we get.

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

The new DB server is “SAPSQL2005”, “IWDFVM2160” is the OLD DB server, IWDFVM2160 also happens to be the server where WAS is running.

Is there some configuration that needs to be changed? Any advice on how to get the TMS working will be appriciated.

Thanks and Regards,

Aniruddha

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Jun 25, 2007 at 03:07 PM

    Hi

    You must be getting error while importing the request into the system also like "Connetion Failed" and also when u perform tests for tool in STMS.

    The problem lies with the environment variables for all the user like administrator, sapservice<sid>, <sid>adm!

    Check that all required parameters set in the old system exists for the users in the new system.

    Probably the error is because of this environment variables for the above users.

    It should solve your problem.

    Regards

    Sumit

    [reward with points if useful]

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 20, 2007 at 01:25 PM

    Discovery system is meant as a learning system. you are not supposed to change or move componets around.

    1.) Hostname must be iwdfvm2160

    The hostname might have been changed during the cloning to something similar like PREREFFE-xxx .

    2.) Domain name must be wdf.sap.corp

    3.) Do not change password for user “Administrator” to other than sap123

    Start of Integration Builder might no longer be working resulting in “500 Internal Server Error”

    4.) Drive letters

    Data drive must be D:

    DVD drive must be E:

    Drive letters might have been changed during the cloning process. Check after boot up that this is correct.

    5.) If no network connection is established, NS lookback adapter needs to be installed.

    If no network connection is available the discovery server is running stand-alone and isolated.

    6.) Swap area should be 6.651 GB distributed over drive C: and D: with system managed size

    Smaller Swap area might lead to start-up errors in the J2EE-instance “IWDFM2160 10” staying in “yellow” in SAP-MMC

    7.) Make error entries in event viewer readable

    Registry modifications might be necessary to synchronise registry with environment variables for ERP and make error messages readable from cryptic before.

    8.) MS SQL Server Evaluation version (180 days) might need to be replaced by the corporate version with a permanent license.

    9.) Boot.ini

    Boot.ini should look like this:

    [boot loader]

    timeout=30

    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

    [operating systems]

    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Standard" /noexecute=optout /fastdetect /PAE /3GB

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Kevin,

      I appreciate your concern of not moving components around on ESA and completely agree we have the SAP ALL in One license and we are not moving any SAP components to another system.

      Our Licensed version of SQL DB is residing on another system and hence we would need to shift the DB, We have been advised to go in for the 2 tier physical model by the OEM of the discovery system. There is a system constraint which is forcing us to shift the SQL server, though i'll skip the reasons as it is not relevant to this context.

      Having said that, lets for the time being, forget the Discover system, would you then be able to shed some light on the issue.

      Thanks and Regards,

      Aniruddha Gargya