SQL-SERVER 2005 Connection

[Former Member]

Hellow All,

We're running MII 12.1.7 and we are have problems with SQL-SERVER 2005 connection.

We try connection with some drivers : sqljdbc.jar, Una2000.jar and sqljdbc4.jar

For driver Una2000 we use this configuration on DataServer:

- JDBC Driver : com.inet.tds.TdsDriver

- ServerURL : jdbc:inetdae:<servername>:1433?database=<dbname>&sql7=true

For driver Microsoft we use this configuration on DataServer:

- JDBC Driver : com.microsoft.jdbc.sqlserver.SQLServerDriver

- ServerURL : jdbc:microsoft:sqlserver://<servername>:1433;databaseName=<dbname>

All Data servers for db are stopped status. We are set enabled property for true and false and all servers continue stoped

Can I have some help please?

[erik_schrampf · Accepted solution]

Without anymore information it is tough to debug, looks like your parameters are setup correctly. I would check the NetWeaver logs and see what errors they are providing as MII will return and show you teh SQL error their. Most likely invalid credentials, or it cannot resolve the server name try the IP address instead.

If that does not work post the Error in NW back to this post for more help. When you enable an MII server it runs a simple query so then afterwards go check the logs. Also if you have Java console open it will display the error there as well.

[Former Member · Accepted solution]

Hi Erik,

Thanks for your response.

We have used IP address and server name.

The user name and password are correct.

The NetWeaver log is below:

ERROR:

Message: Unable to create connection to database for TCAL1

Date: 2010-12-09

Time: 09:52:42:211

Category: /Applications/XMII/Connector

Location: com.sap.xmii.Illuminator.server.Server

Application: sap.com/xapps_xmiiear

Thread: Thread[Managed_Application_Thread_11,5,Managed_Application_Thread]

Data Source: j2ee\cluster\server0\log\applications_00.log

Arguments:

DSR Transaction: 82767390039b11e09132002219a60d90

Message Code:

Session: 0

Transaction:

User: Guest

Time Zone: 0-400

CSN Component:

DC Component: sap.com/xapps_xmiiear

Correlation ID: 3714450000000008

DSR Root Context ID: 82767390039B11E09132002219A60D90

DSR Connection: 82767390039b11e09132002219a60d90

DSR Counter: 0

Log ID: 002219A60D9000560000000200000584

Host: csacop01

System: MCS

Instance: J00

Node: server0

WARNING:

Message: Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource com/inet/tds/TdsDriver.class from .\temp\Una2000.jar112027224706309039.tmp

Date: 2010-12-09

Time: 10:00:19:014

Category: /Applications/LHCommon

Location: com.sap.lhcommon.system.CustomClassLoader

Application: sap.com/xapps_xmiiear

Thread: Thread[Managed_Application_Thread_18,5,Managed_Application_Thread]

Data Source: j2ee\cluster\server0\log\applications_00.log

Arguments:

DSR Transaction: 9055d2c0039c11e099cb002219a60d90

Message Code:

Session: 0

Transaction:

User: Guest

Time Zone: 0-400

CSN Component:

DC Component: sap.com/xapps_xmiiear

Correlation ID: 3714450000000008

DSR Root Context ID: 9055D2C0039C11E099CB002219A60D90

DSR Connection: 9055d2c0039c11e099cb002219a60d90

DSR Counter: 0

Log ID: 002219A60D90005B0000000000000584

Host: csacop01

System: MCS

Instance: J00

Node: server0

[Former Member · Accepted solution]

Marcelo,

For the sqljdbc.jar, try tweaking you connection string to look like this:

jdbc:sqlserver://<servername>:1433;databaseName=<db name>

I've found that SQL Server 2005 uses something called "dynamic ports". You can try leaving the port number off the connection string, or, inside of SQL Sever 2005, configure it not to use dynamic ports, to use just 1433.

Kind Regards,

Diana Hoppe

[erik_schrampf · Accepted solution]

Just to make sure you have uploaded the JDBC drivers to the MII system. The error showing below is that is it having problems opening this file. You can upload the driver on the MII Menu under System Management -> JDBC Drivers.

[Former Member · Accepted solution]

Yes Erick, We can.

See below the display:

JDBC Drivers Status Created By Created

sqljdbc.jar Deployed marcelo.neoris 12/9/10 8:55:55 AM AMT

Una2000.jar Deployed marcelo.neoris 12/9/10 8:05:22 AM AMT

sqljdbc4.jar Deployed marcelo.neoris 12/9/10 8:47:10 AM AMT

[Former Member · Accepted solution]

Hi Diana,

We try, but the error continues yet.

[erik_schrampf · Accepted solution]

Your users may be having problems accessing this temp directory try the following if it is a Windows machine.

Please try the following steps and let us know the results:-

1.)Go to Control Panel>>User Accounts>>Users

2.)You will have a SAPService<SID> user in the Users.Please check if

that user is assigned to a Group>>Administrators.

If it is not please assign it to the Group Administrators.

3.)Restart the SAP Server.

4.)Logon into MII and check if you are able to connect.

If not please take a look at the NW Logs again and see if the same error message is appearing.

[Former Member · Accepted solution]

Marcelo,

Sorry, didn't see this initially, for the sqljdbc.jar the JDBCDriver property should read:

com.microsoft.sqlserver.jdbc.SQLServerDriver

So, to summarize, the properties should read:

JDBCDriver com.microsoft.sqlserver.jdbc.SQLServerDriver

ServerURL jdbc:sqlserver://<servername>:1433;databaseName=<db name>

You can successful ping the database server from the MII server as well?

- Diana

Edited by: Diana Hoppe on Dec 9, 2010 10:49 AM

Edited by: Diana Hoppe on Dec 9, 2010 10:52 AM

[Former Member · Accepted solution]

Hi Erick,

We have three user SapService<>. We assigned Administrator permition for all SapService user, restarted the server. But the error continue yet.

[erik_schrampf · Accepted solution]

Marcelo,

Since I am seeing this error:

WARNING: Message: Ignoring Exception java.util.zip.ZipException: error in opening zip file reading resource com/inet/tds/TdsDriver.class from .\temp\Una2000.jar112027224706309039.tmp

Try deleting the UNA200.jar from the JDBC Drivers page and then reimport it again. It may have been corrupted upon import since it cannot open that file. Also to make sure your jar file(s) is not corrupt, try opening it up in winzip or winrar and see if you can open up those jar files. If you cannot I would recommend that you download them again and then redeploy to the MII server.

Good Luck!

Edited by: Erik Schrampf on Dec 9, 2010 2:21 PM

[Former Member · Accepted solution]

Hi All,

This problem is solved.

We assigned administration permition for all SapService users.

We used the driver sqljdbc_2.0.1803.100_enu because the una2000 not run right.

Thanks all.