Transport Check: DB Connect Link to database failed - Cannot use SAINT!

[Former Member]

Hi All

I am currently having an issue with our Solution Manager transport system. Basically we need to import some pataches via SAINT but we are getting errors relating to our transport system.

So I have checked stms and when I run the Check Transport tool i get the following:

RFC Link tp was started successfully

tp Version 372.04.04

DB Connect Link to database failed

Offline Call connect failed

DB Connect Log:

4 (release 700, unicode enabled)

DBMS_TYPE in parameter file (line 6).

d (20080313083031, probably wrong environment).

,00000] Thu Mar 13 08:30:31 2008

,00000] load shared library (dbmssslib.dll), hdl 0

,00000] using "E:\usr\sap\SMP\DVEBMGS00\exe\dbmssslib.d

,00000] Thread ID:4912

,00000] Thank You for using the SLOLEDB-interface

,00000] Using dynamic link library 'E:\usr\sap\SMP\DVEBMGS0

,00000] dbmssslib.dll patch info

,00000] patchlevel 0

,00000] patchno 131

,00000] patchcomment MSSQL: BCP failed: Invalid characte

,00000] np:(local) connection used on ARMIDALE

,00000] CopyLocalParameters: dbuser is 'dbo'

,00000] Using Provider SQLNCLI

,00000] OpenOledbConnection: MARS property was set success

,00000] Provider Release:9.00.3042.00

,00000] Using Provider SQLNCLI

,00000] OpenOledbConnection: MARS property was set success

,00000] i'm dbo but there exists 1 users <> dbo with table

tp returncode summary:

TOOLS: Highest return code of single steps was: 0

ERRORS: Highest tp internal error was: 0232

standard output from tp and from tools called by tp:

All the environment var. are set - so I am now running out of ideas!!!

Cheers

Phil

[Former Member · Accepted solution]

Hi Phil,

The log statement "DB Connect Link to database failed

Offline Call connect failed" point towards a possible problem with db connectivity. Please check if R3trans executes with return code 0.

regards, Shantanu

[Former Member · Accepted solution]

Thanks both of you!

When I test the R3Trans tool I get the following message:

2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."

[Former Member · Accepted solution]

Ok , I am now getting slighly annoyed now!!!

The errors I am getting, appear to point to a problem with the Environment Variables or Profile Parameters. However I have checked these and they both exist:

HKEY_LOCAL_MACHINE > SOFTWARE > SAP > PRD > Environment >

DBMS_TYPE = mss

In the 'Default.pfl':

dbms/type = mss

I must be missing something here - but currently I can do nothing with SPAM, Saint or STMS!!!

[Former Member · Accepted solution]

Oh, an this is the contents of the TP.PFL:

#TMS:0001:DOMAIN_SMP

#U

#

#----

---

#Caution !

#This file was generated by the Transport Management System.

#Do not change this file using a text editor.

#For further information please see the online documentation of

#transaction STMS.

#If this file was destroyed, it can be regenerated in the TMS.

#To do this, log on to the domain controller (system SMP) and call

#Transaction STMS. In the System Overview, you can distribute the TMS

#configuration. This regenerates the file.

#STMS -> Overview -> Systems -> Extras -> Distribute TMS Configuration

#----

---

#

#

TRANSDIR =
ARMIDALE\sapmnt\trans

#

SMP/DBHOST = ARMIDALE

SMP/DBNAME = SMP

SMP/DBTYPE = mss

SMP/NBUFFORM = 1

SMP/TP_VERSION = 266

Also my system is Solution Manager 4 SP15

[Former Member · Accepted solution]

Phil,

The only way to check if TMS has a problem is now to use tp for transport at OS level. Please try doing that.

Also, may I suggest that you check for tp version in case you recently updated it.

regards, Shantanu

[Former Member · Accepted solution]

Hi,

Can you please post how this issue was resolved?

Thanks in advance,

Shival

[Former Member · Accepted solution]

Hello Phil

Could you please let me know how you resolved this issue.

Thanks

Nitesh

[yuezhi_zhao]

Hello,

Please try to use the latest TP, R3trans and DBSL from SAP Service Market.

Best Regards,

Joe