Having problems with com.sap.dbtech.jdbc.DriverSapDB

Hi all,
I'm using webdynpro and i need to connect to a db.
the line below throghs the Exception
the line above throghs an Exception ClassNotFoundException
Class.forName("com.sap.dbtech.jdbc.DriverSapDB");
I have imported thre jar sapDB.jar what else can i do?
I want to connect to an sql DB via java and i stack.
need your help,
Yoav
Message was edited by: Yoav Toussia Cohen

Hi Yoav,
I belive you put the database access codes in your Web Dynpro's implementation. In this case you need to have your JDBC driver deployed as shared library to the server. You also need to define the Library Reference in your Web Dynpro's project properties.
However, this is not a good approach and Web Dynpro never intends for business process development. You should have an EJB wrapped your database access. Then import this EJB as a model in Web Dynpro to preserve the MVC separation. Always remember Web Dynpro is an UI development tool and not for business process.
Regards,
Marc

Similar Messages

ClassNotFoundException: com.sap.dbtech.jdbc.DriverSapDB

where i can find sapDB.jar? i searched everywhere in my directory, but didn't find anything.

hi
good
try this
ftp://ftp.sap.com/pub/sapdb/bin/java/sapdbc.jar
plz reward points if helpful.
thanks
mrutyun^

Having problem with the SAP ERP on HANA trial

Well, I left my SAP ERP Foundation Extension powered by SAP HANA - Fully Activated Appliance Landscape Trial suspended for about a week. When I re-activated the instance, I could connect to the SAP clients but not log in.
I get the "Logon not possible (error in license check)" message.
I also logged into my AWS console to look at the system log.
The log ends with a number of entries like:
This is R3trans version 6.24 (relesae 741 - 10.10.13 - 20:13:08 ).
unicode enabled version
2EETW169 no connect possible: "DBMS = HDB --- SERVER = '' PORT = ''"
R3trans finished (0012).
Is there anyway to fix this? or do I just terminate and start over, again. (yes, this is the forth or fifth time I've had to rebuild).
Thanks,
Brian

Hi Brian,
there is a bug in the SAP Kernel which unfortunately invalidates the license after each reboot. We are already working on releasing a new version of the SAP ERP Foundation Extension Trial end of this week/early next week which will fix the error.
Alternatively you might fetch the new kernel from the Service Marketplace (if you have access). You would need SAP Kernel 7.41 PL47 for Linux x86_64. After launching the instance in CAL before it turns "green" in the CAL UI you would need to exchange the binaries after logon via ssh.
Quite complex to do, so the suggestion is to wait until end of this week/early next week until we are able to release a new version of the appliance incl. the fix.
Best Regards,
Hannes

ObjectIsClosedException: SAP DBTech JDBC: Object is closed

Hi everybody,
i try to insert data via jdbc in a loop (a Thread) with a PreparedStatement.
the first insertion is successful - but all following inserts are not because of
ObjectIsClosedException (see jdbc-traces)
I do not close the PrepearedStatement or the Connection.
What is the cause of the "[T166].close()" (see trace #2) ???
the Problem is with a call DBROC ({call INSERTEVENTENTRY(?,?,?,?,?,?,?,?,?,?,?,?,?,?)}, too!!
Thanks for your help!
Matthias
(MaxDB is running on SuSE Linux 11.1)
JDBC-Trace: #1
===========================
ClassLoader: sun.misc.Launcher$AppClassLoader at 1a16869
package com.sap.dbtech.jdbc, MaxDB JDBC Driver, SAP AG, 7.6.06 Build 002-000-008-537 (Make-Version: 7.7.06 Build 009-121-202-944) on Java 1.6.0_10
Thread a8c488 main Timestamp: 2009-05-15 13:06:58.792
new Connection 'jdbc:sapdb://xxxxxxxxxxEVENTDB'
user=eventhist
password=***
connectiontrace=/home/ighjhgj/workspace/EventLogger/jd...
Reject GSS Authentication - password is not empty
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000]
Thread 1431340 Thread-3 Timestamp: 2009-05-15 13:07:41.02
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setTimestamp (1, 2009-05-15 12:39:12.175)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setShort (2, 2)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setShort (3, 0)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setShort (4, -1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (5, Biologie 2)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (6, 01GD61)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (7, aus)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (8, Nährstoffpumpe Gaswäsche)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (9, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (10, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (11, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (12, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (13, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].setString (14, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[T141][ParseID 000002440000090154000000].executeUpdate ()
new RTEException: -708 Timeout
whereAmIjava.lang.Throwable
 at com.sap.dbtech.util.Tracer.whereAmI(Tracer.java:328)
 at com.sap.dbtech.rte.comm.RTEException. 0
com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18[T142].commit ()
com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18[T142].close ()
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setTimestamp (1, 2009-05-15 13:07:35.886)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (2, 1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (3, 1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (4, 1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setString (5, Biologie 2)
<-!
Timestamp: 2009-05-15 13:07:41.111com.sap.dbtech.jdbc.exceptions.ObjectIsClosedException: SAP DBTech JDBC: Object is closed.
 at com.sap.dbtech.jdbc.ConnectionItem.assertOpen(ConnectionItem.java:53)
 at com.sap.dbtech.jdbc.CallableStatementSapDB.setString(CallableStatementSapDB.java:2191)
 at com.sap.dbtech.jdbc.trace.log.PreparedStatement.setString(PreparedStatement.java:704)
 at com.sap.dbtech.jdbc.trace.PreparedStatement.setString(PreparedStatement.java:336)
 at de.pkv.eventlogger.handler.EventLogEntryDAO.insertEventLogEntry(EventLogEntryDAO.java:141)
 at de.pkv.eventlogger.handler.DBhistoryOutputHandler.run(DBhistoryOutputHandler.java:50)
 at java.lang.Thread.run(Thread.java:619)
com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18.close ()
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setTimestamp (1, 2009-05-15 13:07:36.046)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (2, 2)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (3, 0)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setShort (4, -1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 17ce4e7[closed][ParseID 000002450000060154000000].setString (5, Biologie 2)
<-!
Timestamp: 2009-05-15 13:07:41.119com.sap.dbtech.jdbc.exceptions.ObjectIsClosedException: SAP DBTech JDBC: Object is closed.
 at com.sap.dbtech.jdbc.ConnectionItem.assertOpen(ConnectionItem.java:53)
 at com.sap.dbtech.jdbc.CallableStatementSapDB.setString(CallableStatementSapDB.java:2191)
 at com.sap.dbtech.jdbc.trace.log.PreparedStatement.setString(PreparedStatement.java:704)
 at com.sap.dbtech.jdbc.trace.PreparedStatement.setString(PreparedStatement.java:336)
 at de.pkv.eventlogger.handler.EventLogEntryDAO.insertEventLogEntry(EventLogEntryDAO.java:141)
 at de.pkv.eventlogger.handler.DBhistoryOutputHandler.run(DBhistoryOutputHandler.java:50)
 at java.lang.Thread.run(Thread.java:619)
JDBC-Trace: #2
===========================
ClassLoader: sun.misc.Launcher$AppClassLoader at 1a16869
package com.sap.dbtech.jdbc, MaxDB JDBC Driver, SAP AG, 7.6.06 Build 002-000-008-537 (Make-Version: 7.7.06 Build 009-121-202-944) on Java 1.6.0_10
Thread a8c488 main Timestamp: 2009-05-15 22:48:58.594
new Connection 'jdbc:sapdb://xxxxxxx/EVENTDB'
user=eventhist
password=***
connectiontrace=/home/mlbbl/workspace/EventLogger/jd...
Reject GSS Authentication - password is not empty
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00]
Thread e45076 Thread-3 Timestamp: 2009-05-15 22:49:15.555
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setTimestamp (1, 2009-05-15 22:48:26.031)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setShort (2, 6)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setShort (3, 0)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setShort (4, -1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (5, KM2 Konstt)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (6, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (7, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (8, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (9, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (10, KM2)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (11, DCT1_XDC8:0)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (12, S24VD20.ACK)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (13, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].setString (14, null)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[T166][ParseID 0000026800000a0212003c00].execute ()
=> false
com.sap.dbtech.jdbc.ConnectionSapDB at 166aa18[T166].close ()
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setTimestamp (1, 2009-05-15 22:48:26.021)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setShort (2, 1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setShort (3, 1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setShort (4, 1)
com.sap.dbtech.jdbc.CallableStatementSapDB at 1c0e45a[closed][ParseID 0000026800000a0212003c00].setString (5, KM2 Konstt)
<-!
Timestamp: 2009-05-15 22:49:15.692com.sap.dbtech.jdbc.exceptions.ObjectIsClosedException: SAP DBTech JDBC: Object is closed.
 at com.sap.dbtech.jdbc.ConnectionItem.assertOpen(ConnectionItem.java:53)
 at com.sap.dbtech.jdbc.CallableStatementSapDB.setString(CallableStatementSapDB.java:2191)
 at com.sap.dbtech.jdbc.trace.log.CallableStatement.setString(CallableStatement.java:2888)
 at com.sap.dbtech.jdbc.trace.CallableStatement.setString(CallableStatement.java:1050)
 at de.pkv.eventlogger.handler.EventLogEntryDAO.callInsertEventLogEntry(EventLogEntryDAO.java:150)
 at de.pkv.eventlogger.handler.DBhistoryOutputHandler.run(DBhistoryOutputHandler.java:52)
 at java.lang.Thread.run(Thread.java:619)

it was the wrong place for a finally-statement in run()-Method:
 public void run() {
 while (true) { // do forever
 try {
 entry = this.theQueue.take(); // wait, if empty
 if (DEBUG) System.out.println(name + ": try to take from queue: " + entry);
 if (DEBUG) System.out.println(name + ": EventLogEntry: " + entry.toString());
 // do the work: insert into Database:
 success = dao.insertEventLogEntry(entry); // insert new Entry (Prep.Statement)
 //success = dao.callInsertEventLogEntry(entry); // insert new Entry (call db_proc)
 if (DEBUG) System.out.println(name + ": Insert new LogEntry. Success: " + success);
 // Thread.sleep(10);
 //Thread.yield();
 } catch (InterruptedException e) {
 System.err.println(name + ": Error in Thread.sleep()");
 e.printStackTrace();
 } catch (Exception e) {
 System.err.println(name + ": Error: " + e.getMessage());
 } // catch
 // finally {
 // if (con != null) {
 // try {
 // con.close();
 // } catch (SQLException e) {
 // // TODO Auto-generated catch block
 // e.printStackTrace();
 // } // if con
 // } // finally
 } // while
 } // run
regards
Matthias

I just updated to new final cut pro x 10.1.1 and i am also on mavericks so but on my editing timeline i was trying to color grade using magic bullet looks but i am having problem with it. when it comes back to tcp x it's black.

I just updated to the new final cut pro x 10.1.1 and i am also on mavericks so but on my editing timeline i was trying to color grade using magic bullet looks but i am having problem with it. When i send a sample to MBL and color grade it , it comes back to final cut pro x all black even after render. By the way on the MBL i am using the GPU rendering, I used before like 4months ago and it was fine. And i don't like to use the CPU because it very slow.

What is the frame rate of the project? At what frame rate was the media recorded? What frame size?
What are the audio settings?
What are the specs of the machine, in particular how much RAM, how is the hard drive connected, etc.?
If possible, post screenshots of the inspector for the project.
It could be related to the audio frequency?

Having problem with UDF, getting unwanted result Ljava.lang.String;@25c560

Hi,
This is atually a follow-up to other post in the same forum: Sending XMl message as text (Mail body) by receiver mail adapter
We are having problem with UDF to get correct output.
We are getting result of UDF as below:
[[Ljava.lang.String;@f37573 [Ljava.lang.String;@1a409ed [Ljava.lang.String;@87c011 [Ljava.lang.String;@52a077 [Ljava.lang.String;@a4e8e5 [Ljava.lang.String;@f37573 [Ljava.lang.String;@1a409ed [Ljava.lang.String;@87c011 [Ljava.lang.String;@52a077 [Ljava.lang.String;@a4e8e5 [Ljava.lang.String;@f37573 [Ljava.lang.String;@1a409ed [Ljava.lang.String;@87c011 [Ljava.lang.String;@52a077 [Ljava.lang.String;@a4e8e5 [Ljava.lang.String;@f37573 [Ljava.lang.String;@1a409ed [Ljava.lang.String;@87c011 [Ljava.lang.String;@52a077 [Ljava.lang.String;@a4e8e5 ]
Does any body know what it mean?
Following are the source ans target XSD's:
Here is the source xsd:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://NameSpace" targetNamespace="NameSpace">
<xsd:complexType name="row">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5e090470385011db9654000e7f22e9d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="DeliveryNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a0377b11db91dbf237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="DeliveryLineItem">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a1377b11db98aaf237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="6" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderNumber">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a2377b11dbc5c4f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderLineItem">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a3377b11db9d84f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="6" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BillToID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a4377b11dbb49bf237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="17" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BillToName">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a5377b11dbb38ff237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipToID">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a6377b11db9370f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="17" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ShipToName">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a7377b11dbb66cf237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ProductCode">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a8377b11db8f94f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="18" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ProductDesc">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0a9377b11db929ff237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ScheduledLoadDate">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0aa377b11db8d1df237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="8" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="ScheduledLoadTime">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0ab377b11dba57ff237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="6" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Carrier">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0ac377b11dbcc03f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="CustomerPO">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0ad377b11dbb5a2f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="35" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OutYard">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0ae377b11dbcc51f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="16" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderedQty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0af377b11dbbe6cf237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="OrderUofM">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0b0377b11db9264f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="3" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="LabConc">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0b1377b11dbb0e7f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GrossMT">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0b2377b11db99f1f237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="GrossST">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0b3377b11db9b6ff237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="BilledQty">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0b4377b11db8a9af237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="8" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="Status">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9d3ac0b5377b11dba39cf237ac102206
</xsd:appinfo>
</xsd:annotation>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:length value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="resultset">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
5e044980385011dbb2d3000e7f22e9d4
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="row" type="row" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
c1cb8fd0377b11db912af237ac102206
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Target xsd:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://sap.com/xi/XI/Mail/30" targetNamespace="http://sap.com/xi/XI/Mail/30">
<xsd:element name="Mail">
<xsd:annotation>
<xsd:documentation>
Mail package for XI - Mail Adapter
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Subject" type="xsd:string" minOccurs="0" />
<xsd:element name="From" type="xsd:string" minOccurs="0" />
<xsd:element name="To" type="xsd:string" minOccurs="0" />
<xsd:element name="Reply_To" type="xsd:string" minOccurs="0" />
<xsd:element name="Content_Type" type="xsd:string" minOccurs="0" />
<xsd:element name="Date" type="xsd:dateTime" minOccurs="0" />
<xsd:element name="Message_ID" type="xsd:string" minOccurs="0" />
<xsd:element name="X_Mailer" type="xsd:string" minOccurs="0" />
<xsd:element name="Content" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:documentation>
any type
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="encoding" type="xsd:string" />
</xsd:complexType>
</xsd:element>
</xsd:schema>
And following is the UDF we are using:
=========================================
String mailBody = new String();
int inta, intb, intc, intd, inte;
inta = a.length;
intb = b.length;
intc = c.length;
intd = d.length;
inte = e.length;
for(int i = 0; i < a.length; i++)
mailBody = mailBody + a + " " + b + " " + c + " " + d + " " + e + " ";
result.addValue(mailBody);
====================================
Any help to resolve this would be very helpful.
Thanx
Sue

Hi Bhavesh,
We are getting following error if we use the UDF you given below:
Check Result for Object test Source code has syntax error: D:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapf2026120390a11db9d1f000e7f22e9d4/source/com/sap/xi/tf/_test_.java:75: a is already defined in testUDF$(java.lang.String[],java.lang.String[],java.lang.String[],java.lang.String[],java.lang.String[],com.sap.aii.mappingtool.tf3.rt.ResultList,com.sap.aii.mappingtool.tf3.rt.Container) int a = a.length(); ^ D:/usr/sap/XID/DVEBMGS00/j2ee/cluster/server0/./temp/classpath_resolver/Mapf2026120390a11db9d1f000e7f22e9d4/source/com/sap/xi/tf/_test_.java:75: int cannot be dereferenced int a = a.length(); ^
We have no knowledge of java at all.
We did some modifications to it as below:
String mailBody = new String();
int a = a.length();
int b = b.length();
int c = c.length();
int d = d.length();
int e = e.length();
for(int i = 0; i < a.length(); i++)
mailBody = mailBody + a + " " + b + " " + c + " " + d + " " + e + " ";
result.addValue(mailBody);
It it didn't work. Think we are missing something. Can please help us to figure it out.
Thanx
Sue

SAP DBTech JDBC: [259] (at 26): invalid table name: Could not find table/view RS_POOL_CLUSTER_TABLES in schema SYSTEM: line 1 col 27 (at pos 26)

Hi Gurus,
I am trying to load a HANA column table using the import function and get the following error even though the mappings from the file to the table are 1:1.
I get the following errors:
Error 1: SAP DBTech JDBC: Result set is positioned before first row.
Error 2: SAP DBTech JDBC: [259] (at 26): invalid table name: Could not find table/view RS_POOL_CLUSTER_TABLES in schema SYSTEM: line 1 col 27 (at pos 26)
With the following stack trace:
com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [259] (at 26): invalid table name: Could not find table/view RS_POOL_CLUSTER_TABLES in schema SYSTEM: line 1 col 27 (at pos 26)
at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:334)
at com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateDatabaseException(SQLExceptionSapDB.java:165)
at com.sap.db.jdbc.packet.ReplyPacket.buildExceptionChain(ReplyPacket.java:100)
at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1141)
at com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:888)
at com.sap.db.jdbc.StatementSapDB.sendCommand(StatementSapDB.java:929)
at com.sap.db.jdbc.StatementSapDB.sendSQL(StatementSapDB.java:978)
at com.sap.db.jdbc.StatementSapDB.execute(StatementSapDB.java:256)
at com.sap.db.jdbc.StatementSapDB.executeQuery(StatementSapDB.java:401)
at com.sap.db.jdbc.trace.Statement.executeQuery(Statement.java:131)
at com.sap.ndb.studio.bi.dataprovisioning.util.DBUtil.getPoolTables(DBUtil.java:200)
at com.sap.ndb.studio.bi.dataprovisioning.util.DBUtil.getTablesToHide(DBUtil.java:188)
at com.sap.ndb.studio.bi.filedataupload.ui.wizards.pages.SelectTableDialog.createDialogArea(SelectTableDialog.java:108)
at org.eclipse.jface.dialogs.Dialog.createContents(Dialog.java:775)
at org.eclipse.jface.window.Window.create(Window.java:432)
at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
at com.sap.ndb.studio.bi.filedataupload.ui.wizards.pages.SelectTableDialog.create(SelectTableDialog.java:186)
at com.sap.ndb.studio.bi.filedataupload.ui.wizards.pages.ImportFileSelectionWizardPage$14.widgetSelected(ImportFileSelectionWizardPage.java:779)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
at org.eclipse.jface.window.Window.open(Window.java:802)
at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.GeneratedMethodAccessor33.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584)
at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501)
at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1057)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4170)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3759)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
I'm sure many of you have come across this before. Any help will be much appreciated.
Thanks in advance

Hello Akhtar,
Have you tryed to delete the heador row from your file?
I received the same error when loading a csv file, but when I delete the heador row it worked.
Best Regards,
Juliana Genova

SAP DBTech JDBC: [4]: cannot allocate enough memory: Out of memory

Hello,
I am currently experiencing this error when making request to the Hana database via jdbc : SAP DBTech JDBC: [4]: cannot allocate enough memory: Out of memory
I guess I am running out of space, so I wanted to delete some data from unused tables. The problem is that I cannot connect with Studio anymore "Error when connecting to system".
Is there another way to delete data from some tables when getting this particular error ?
Does anyone experienced such a situation ?
Thank you,
Benoît

Hi Benoit,
Please plan to migrate to the latest version from Rev 38 before 1 year license expires in Rev 38 in Oct 2013. You need to export your content and import in the latest version.
As you are aware, a lot of bugs are fixed between Rev 38 and the newer releases along with new SPS5 features and HANA One is adding new web based management features in each HANA One release which does not need SSH to stop|start HANA as it can be done in browser starting in Rev 52 (check out The specified item was not found.for additional info). Please stay tuned for the upcoming version which will have additional management features to manage your instance.
Thanks,
Swapan

SAP DBTech JDBC: [258]: insufficient privilege: Not authorized - SAP HANA

Dear All,
We are getting the below error when we tried to call procedure ART_PROC using the SYSTEM user in SAP HANA Studio,
Could not execute 'call "TESTECC"."ART_PROC"'
SAP DBTech JDBC: [258]: insufficient privilege: Not authorized
Kindly provide your suggestions on the same.
Thanks
Arun R

Hello Arun,
Firstly it is **not** recommended to use SYSTEM for anything other than management tasks.
My Assumptions
* the procedure ART_PROC was not created by the SYSTEM user
Solution : you need to give EXECUTE privileges on the procedure to SYSTEM
How: Only the user who created the procedure or who has been give grant privilege can give the EXECUTE privilege. SYSTEM cannot give itself this privilege
For the Grant command check out sec 1.8.6.17 of the http://help.sap.com/hana/SAP_HANA_SQL_Script_Reference_en.pdf
OR
in the HANA Studio
in the System tab expand the system with the log in user as the owner/grantor of the privilege
here you will see a node called Security.
Right-click and choose 'Find User/Role'
Type System in the search dialog that opens - double click on SYSTEM user displayed below
System user opens up - Navigate to Object Privileges tab
here using the green '+' button search for ART_PROC and then on the right side tick the 'Execute' checkbox
click on save.
Warm regards
aadi

ClassNotFoundException: com.sap.portals.jdbc.sqlserver.SQLServerDriver

Hello,
(Running NW04SP14)
I am trying to use the jdbc class in my code as follows:
Class.forName("com.sap.portals.jdbc.sqlserver.SQLServerDriver");
I am getting a ClassNotFoundException.
Could you please tell me what do I need to do to import this class for all my portal components?
Do I need to physically include a jar file, if so where can I find it?
Should I include a sharing reference in my code?
Thanks.

Hi Detlev,
I'm asking to you about a problem with connection that since many days I'm not able to solve. I hope in your help regarding this.
I have to connect to Oracle DB from an EJB, I used two solution but without success:
----
1. JDBC Connection from a Bean

Connection con = null;
 Statement stmt = null;
 ResultSet rset = null;
 String connectionURLThin = "jdbc:oracle:thin:@liposv01:1527:PCD";
 String driverClass = "oracle.jdbc.driver.OracleDriver";
 String userID = "sappcddb";
 String userPassword = "1qaz2wsx";
 String queryString = "select ordine_modello_sq.nextval from dual";
 int risultato = 0;
 try {
 //check = "start connection";
 Class.forName(driverClass).newInstance();
 con = DriverManager.getConnection(connectionURLThin, userID, userPassword);
 stmt = con.createStatement ();
 rset = stmt.executeQuery(queryString);
 if (rset.next()) {
 risultato = rset.getInt(1);
 //prog_ordine_seq = new Integer(risultato);
 //check = "Connessione JDBC avvenuta";
 rset.close();
 stmt.close();
 } catch (ClassNotFoundException e) {
 e.printStackTrace();
 } catch (InstantiationException e) {
 e.printStackTrace();
 } catch (IllegalAccessException e) {
 e.printStackTrace();
 } catch (SQLException e) {
 e.printStackTrace();
 if (con != null) {
 try {
 con.rollback();
 } catch (SQLException e1) {
 e1.printStackTrace();
 } finally {
 if (con != null) {
 try {
 con.close();
 } catch (SQLException e) {
 e.printStackTrace();
I have the error(the server is unix and a classpath is set)
java.lang.ClassNotFoundException: oracle.jdbc.driver.OracleDriver
Loader Info -
ClassLoader name: [local/OrdineWD]
Parent loader name: [Frame ClassLoader]
References:
 common:service:http;service:servlet_jsp
 service:ejb
 common:service:iiop;service:naming;service:p4;service:ts
 service:jmsconnector
 library:jsse
 library:servlet
 common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
 library:ejb20
 library:j2eeca
 library:jms
 library:opensql
 common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
 interface:resourcecontext_api
 interface:webservices
 interface:ejbserialization
 sap.com/tcwddispwda
 sap.com/ModelloApplication
 sap.com/tcwdcorecomp
 service:webdynpro
 service:sld
 library:tcddicddicservices
 library:com.sap.aii.proxy.framework
 library:tcgraphicsigs
 library:com.sap.mw.jco
 library:com.sap.lcr.api.cimclient
 library:sapxmltoolkit
 library:com.sap.aii.util.rb
 library:com.sap.util.monitor.jarm
 library:tcddicddicruntime
 library:com.sap.aii.util.xml
 library:tccolapi
 library:com.sap.aii.util.misc
 library:tc~cmi
 library:tccolruntime
Resources:
 /usr/sap/PCD/JC00/j2ee/cluster/server0/apps/local/OrdineWD/webdynpro/public/lib/ModelloHelper.jar
 /usr/sap/PCD/JC00/j2ee/cluster/server0/apps/local/OrdineWD/webdynpro/public/lib/app.jar
 /usr/sap/PCD/JC00/j2ee/cluster/server0/apps/local/OrdineWD/webdynpro/public/lib/MyCommandBean.jar
 /usr/sap/PCD/JC00/j2ee/cluster/server0/apps/local/OrdineWD/webdynpro/public/lib/ModelloEjb.jar
Loading model: {parent,references,local}
----
1. DataSource Connection from sessionBean

 try {
 InitialContext ctx = new InitialContext();
 DataSource ds = (DataSource) ctx.lookup("java:comp/env/ejb/ORDINE_MODELLO_POOL");
 Connection con = ds.getConnection();
 String query = "select ordine_modello_sq.nextval from dual";
 Statement stmt = con.createStatement();
 try {
 ResultSet rs = stmt.executeQuery(query);
 try {
 while ( rs.next() ) {
 //Insert the sequence value
 int prog_ordine_int = rs.getInt(1);
 prog_ordine_seq = new Integer(prog_ordine_int);
 } finally {
 rs.close();
 } finally {
 stmt.close();
 }catch (Exception e) {
 e.printStackTrace();
I have the error finding datasource:
com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContexts/sap.com/ModelloApplication/MySessionBean/java:comp/env/jdbc/ORDINE_MODELLO_POOL, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "jdbc/ORDINE_MODELLO_POOL" does not exist. Possible reasons: the connector in which ConnectionFactory "jdbc/ORDINE_MODELLO_POOL" is defined is not deployed or not started.]
Thanks in advance for your help.
Vito Palasciano

I am having problems with creating my apple id. On the phone it is advising me that the ID is not created and then when i do it online it says that it has been created. Can you advise me on what to do please?

I am having problems with creating my apple id. On the phone it is advising me that the ID is not created and then when i do it online it says that it has been created. Can you advise me on what to do please?

Apple ID FAQ http://support.apple.com/kb/HE37

I am having problems with my music collection, after burning all of my music to the computer I organized it into folders and placed it in the iTunes Folder. Starting on a new computer now. I can get my music from old computer?

I am having problems with my music collection, after burning all of my music to the computer I organized it into folders and placed it in the iTunes Folder. As of now i realize this was a mistake. Starting on a new computer now. I cant get my music to transfer from the itunes folder on the old computer? I keep getting error "Can't Read from the source file or disk." Whenever I got to folder properties its always checked read only. But when i play the song it works just fine. Im sure this is just because I added music into itunes folder but is there anyway to fix it?

WMA files are 'window media audio' files, which is a Microsoft format. If you want to add them to your iTunes library on your Mac then you will need to convert them into a compatible format first. If you still have your windows machine then iTunes for Windows can convert them from WMA to MP3 format : https://discussions.apple.com/message/24158701#24158701
Or try a search for, for example, 'convert wma to mp3' to find programs to convert them.

I have been having problems with my FaceTime for the last few weeks. Up to then I was able to use it daily and then it suddenly stopped functioning. I have 4 friends in the same situation. Is there a problem centrally with Apple? Anyone else with problems

I have been using FaceTime regularly over the past year or so and suddenly it has stopped working. It seems to dial up and says its connecting and then just switches off. I have a number of other friends who are also having problems with this and also on their iPhones. Does anyone have an answer to this problem?

Make sure all parties are running IOS 7.1.1
http://support.apple.com/kb/TS5419

If you're having problems with USB ports, read on...

i'm reading that alot of people on here are having problems with their front (or top) usb on their cases not working with their k7n2 boards. i have come across the correct solution to this problem in one of the posts (after having solved the problem on my own), however noone has posted the solution by itself on this forum so everyone can easily see it.
The trick is to make sure that pin 10 (at least on a K7n2 delta-L), the pin labeled USBOC (USB Open Connection), is wired to NOTHING. If the connector to your front usb ports is fused into one giant connector and it HAS a wire that will connect to this pin (labeled GND2 or Shield or something), CUT THAT WIRE. Pin 10 on JUSB2 (at least on a K7n2 delta-L) must be OPEN. If this pin IS connected to something (even if it is only GND), the motherboard will think something is connected to this usb port and you will get many unknown devices listed in your windows device manager and the rest of your usb ports may or may not work.
As a general rule of thumb, if a pin on a motherboard is labeled OC for "Open Connection" and you wire something to it, you're asking for trouble.
If you cannot understand this you should not be attempting to wire a motherboard in the first place.
Here is a picture to go along with this discussion. If you cannot see this picture, I am sorry for it has probably been removed from the place I posted it online as I cannot attach pictures physically to this post. If someone here has a way to permanently host this picture and post it to this thread permanently, that would be wonderful.
In summary: all usb ports/headers have only four pins associated with it (VCC, USB+, USB-, GND). If the connector (whether it's one big connector or individual sockets) to your front/top usb port has 5 sockets, don't connect the 5th socket to anything. That goes for any case/motherboard combination. This is what i'm talking about above. I have no idea why motherboard and case manufacturers have a 5th pin involved in any way on either the pin or socket side. It is not used for usb.
EDIT: I just noticed this has already been discussed in the trouble shooting guide in the above sticky post. oh well, now we have a pretty picture to go along with it (i hope).

:-D)Hello guys,
as promised I come back here to give the results of my tests... and I have to say that you saved my day (even if I had to open back 60 secured cases).
So the solution was the right one, when I unplugged the "ground" end of the front USB connector cable from the USBOC pin, those connectors finally worked as expected with USB 2.0 compliant devices.
So thank you really much for this very usefull information !
And even if maybe it's not only MSI's fault, I still believe that more information on those connectors in the user's manual would be really usefull (who knows what USBOC means except a few people and who could imagine that pluggin on it a "ground" cable would make it unserviceable ??). And who ever saw a user's manual bundled with a case ?? it's pretty unusual
Hope that someone at MSI will read that and take it into consideration, not for me (because now I'm aware) but for the thousands other consumers that will feel a little bit "annoyed" with that issue. I don't think that adding one line about it in user's manuals would be so much expensive
But I'm quite lucky myself... being able to understand and write english (even if I still have some progress to do ) gave me the possibility to find the solution... but a lot of my french fellows can't do that... and there's no french forum here... How can they do ? They rely on user's manual
Best regards,
Nicolas

Is Anyone Else Having Problems With 10.6.1 Freezing?

Is anyone else having problems with iTunes 10.6.1 freezing? On a perfectly-maintained Windows PC, 10.6.1 is suddenly freezing for no reason. This means that my iPhone or iPad can't be synchronized.

From my experience, involving three hours of troubleshooting using Apple's tutorials, without help from Apple:
1. Do the steps here to remove and reinstall all Apple software on your machine, "Removing and Reinstalling iTunes, QuickTime, and other software components for Windows XP," at http://support.apple.com/kb/HT1925.
2. If you care, they don't tell you or ask you to uninstall MobileMe in those steps.
3. After I did as they wrote to do, iTunes wouldn't recognize either my iPhone or iPad. On my own I found that Applie's software reinstallation failed to install the Apple Mobile Device Software Driver. So I followed the steps at, "iOS: Device not recognized in iTunes for Windows," which took me 25 minutes alone to find. See http://support.apple.com/kb/TS1538
Those steps solved everything and iTunes is now back to normal.

Having problems with com.sap.dbtech.jdbc.DriverSapDB

Similar Messages

Maybe you are looking for