Problems to start SAP instance after reboot

[philipp_schweizer]

Hello experts,

we are occuring a problem that we are not able to start our SAP instance after we applied some MS patches and rebooted the server. We also deinstalled these patches buzt this also did not help, so I guess the reason somewhere else.

We are running a SQL server 2000 on a Windows 2003 SP2 (32bit)

SAP kernel is 640 PL 304

The SQL server seems to operate normally, however when we try to start SAP via MMC the process disp+work fails (it's green for a few seconds, but then turn so grey).

In dev_w0 I can find this entry

C Mon Feb 22 12:35:18 2010

C OpenOledbConnection: line 23082. hr: 0x8000ffff [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

C sloledb.cpp [OpenOledbConnection,line 23082]: Error/Message: (err 17, sev 10), [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

C Procname: [OpenOledbConnection - no proc]

C sloledb.cpp [OpenOledbConnection,line 23082]: Error/Message: (err 0, sev 10), Invalid connection string attribute

C Procname: [OpenOledbConnection - no proc]

C Provider SQLNCLI could not be initialized. See note #734034 for more information.

C Using provider SQLOLEDB instead.

I hope you have an idea to solve the issue soon.

Thanks a lot

Philipp

[Former Member · Accepted solution]

Philipp please try to run R3trans -d and post the error here.

SQL Server does not exist or access denied

Looks like SQL is not up or database is not up, could you check this in SQL Admin console?

Does any of those fixes is for SQLServer?

[philipp_schweizer · Accepted solution]

rtrans -d or r3trans -x finishing with return code 0

r3trans -d

This is r3trans version 6.13 (release 640 - 26.10.09 - 15:44:00).

r3trans finished (0000).

If I logon to the SQL server is cannot see any problems; the database seems up and running and also shows all tables and users and so on....

[philipp_schweizer]

problem was a profile parameter.

dbs/mss/server

This parameter was set according to SAP note 548823 - no good idea!

After we deleted it, we were able to start the SAP instance...

Thanx for yur replies and hints!

[ken_halvorsen2]

Hi Philipp

Have you checked the database user id's? Is it possible the DB owner needs to be changed or re-set?

Ken

[Former Member]

Hi Philipp,

You wrote that r3trans -d works.

R3trans uses the environment variables

MSSQL_SERVER -- name of database host, in case of a named instance the complete instance name,

protocol can be specified, too

MSSQL_DBNAME -- database name

MSSQL_SCHEMA -- dbo for non-schema systems, otherwise the lowercase SAP system name

to build his connect strings.

The SAP system's work processes instead use profile parameters:

dbs/mss/server -- same meaning as MSSQL_SERVER

dbs/mss/dbname -- same meaning as MSSQL_DBNAME

dbs/mss/schema -- same meaning as MSSQL_SCHEMA

So, are the environment settings different to the profile parameters?

Regards,

Guenther

Edited by: Guenther Drach on Feb 23, 2010 5:15 PM

[former_member524429]

Hi,

Have you read that suggested SAP Note 734034 within that error message ?

Its looking like port blocking problem.

Whts the version of DBNETLIB.dll ?

Please download this [SQL Security patch|http://www.microsoft.com/downloads/details.aspx?familyid=9552d43b-04eb-4af9-9e24-6cde4d933600&displaylang=en], it will detect the vulnerability and will correct the affected files. After executing this patch, try to start SAP system.

Regards,

Bhavik G. Shroff

[philipp_schweizer]

Hi,

yes I read this SAP note however when I try to install this patch I fails with message "installation unsuccessful"

The version of DBNETLIB.dll is 2000.086.3959

best regards

Philipp

Edited by: Philipp Schweizer on Feb 22, 2010 4:53 PM

[former_member524429]

Hi,

yes I read this SAP note however when I try to install this patch 
It fails with message "installation unsuccessful"

Reason ??

Check the following:

1. Status of SQLServer Service(s)?

2. Windows Event Log Entries?

What is the SP level of SQL Server 2000 ?

Also, Perform the Connectivity Test as per[ this link|http://support.microsoft.com/kb/827422/].

Regards,

Bhavik G. Shroff

[philipp_schweizer]

sorry, no idea why the installation fails - there is not written anything into a log or the event log.

The services of the SQL Server are up and running - as I wrote before the SQL server seems to operate normally.

There are no hints in the event log concerning this problem....

The version of the server is Microsoft SQL Server 2000 - 8.00.2055

I went through the kb article without success....

any further ideas?

Thank you!