JDBC Error with SQL Server
I created another post asking about this but cannot find it.
I had a perfiectly good piece of JDBC code working in a freestanding program that could retrieve a result of any size without issue. However, when I ran the same code from a servlet in Tomcat, this error was thrown:
java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]IO Error creating temp file: null
at com.microsoft.jdbc.base.BaseExceptions.createException(BaseExceptions.java:45)
at com.microsoft.jdbc.base.BaseExceptions.getException(BaseExceptions.java:92)
at com.microsoft.jdbc.sqlserver.tds.TDSRPCRequest.submitRequest(TDSRPCRequest.java:191)The fix has to do with the tmpdir variable in Tomcat 5. If the $CATALINA_HOME/temp is missing, the File.createTempFile() method blows up.
Hope the 5 hours I blew finding it helps you.
SQLServer Error creating temp file
Similar Messages
-
Error with Sql Server and Java App
Hi i have a java based multithread application which comunicate with SQL SERVER via DSN bridge , some time my application crashes with this error any idea what its happend and how to remove it .
Thanks
************* Exception ********************************8
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x77F87EEB
Function=RtlEnterCriticalSection+0xB
Library=F:\WINNT\system32\ntdll.dll
Current Java thread:
at sun.jdbc.odbc.JdbcOdbc.numResultCols(Native Method)
at sun.jdbc.odbc.JdbcOdbc.SQLNumResultCols(JdbcOdbc.java:4625)
at sun.jdbc.odbc.JdbcOdbcStatement.getColumnCount(JdbcOdbcStatement.java:1235)
at sun.jdbc.odbc.JdbcOdbcStatement.execute(JdbcOdbcStatement.java:352)
- locked <04DC3EE0> (a sun.jdbc.odbc.JdbcOdbcStatement)
at sun.jdbc.odbc.JdbcOdbcStatement.executeUpdate(JdbcOdbcStatement.java:288)
at advcomm.advrad.DBParams.Ltht(Unknown Source)
at advcomm.advrad.DBParams.BDhb(Unknown Source)
at advcomm.advrad.DlkhlHz.run(Unknown Source)
Dynamic libraries:
0x00400000 - 0x00406000 F:\j2sdk1.4.1_03\bin\java.exe
0x77F80000 - 0x77FFC000 F:\WINNT\system32\ntdll.dll
0x7C2D0000 - 0x7C335000 F:\WINNT\system32\ADVAPI32.dll
0x7C570000 - 0x7C623000 F:\WINNT\system32\KERNEL32.dll
0x77D30000 - 0x77DA8000 F:\WINNT\system32\RPCRT4.dll
0x78000000 - 0x78045000 F:\WINNT\system32\MSVCRT.dll
0x75030000 - 0x75044000 F:\WINNT\system32\WS2_32.DLL
0x75020000 - 0x75028000 F:\WINNT\system32\WS2HELP.DLL
0x6D340000 - 0x6D46B000 F:\j2sdk1.4.1_03\jre\bin\client\jvm.dll
0x77E10000 - 0x77E79000 F:\WINNT\system32\USER32.dll
0x77F40000 - 0x77F7C000 F:\WINNT\system32\GDI32.dll
0x77570000 - 0x775A0000 F:\WINNT\system32\WINMM.dll
0x6D1E0000 - 0x6D1E7000 F:\j2sdk1.4.1_03\jre\bin\hpi.dll
0x6D310000 - 0x6D31E000 F:\j2sdk1.4.1_03\jre\bin\verify.dll
0x6D220000 - 0x6D239000 F:\j2sdk1.4.1_03\jre\bin\java.dll
0x6D330000 - 0x6D33D000 F:\j2sdk1.4.1_03\jre\bin\zip.dll
0x6D260000 - 0x6D26B000 F:\j2sdk1.4.1_03\jre\bin\JdbcOdbc.dll
0x1F7A0000 - 0x1F7DA000 F:\WINNT\system32\ODBC32.dll
0x71710000 - 0x71794000 F:\WINNT\system32\COMCTL32.dll
0x7CF30000 - 0x7D175000 F:\WINNT\system32\SHELL32.dll
0x70A70000 - 0x70AD6000 F:\WINNT\system32\SHLWAPI.dll
0x76B30000 - 0x76B6E000 F:\WINNT\system32\comdlg32.dll
0x1F840000 - 0x1F857000 F:\WINNT\system32\odbcint.dll
0x1F9C0000 - 0x1FA27000 F:\WINNT\System32\SQLSRV32.dll
0x41090000 - 0x410BD000 F:\WINNT\System32\SQLUNIRL.dll
0x77800000 - 0x7781E000 F:\WINNT\System32\WINSPOOL.DRV
0x76620000 - 0x76631000 F:\WINNT\system32\MPR.DLL
0x77820000 - 0x77827000 F:\WINNT\system32\VERSION.dll
0x759B0000 - 0x759B6000 F:\WINNT\system32\LZ32.DLL
0x779B0000 - 0x77A4B000 F:\WINNT\system32\OLEAUT32.dll
0x7CE20000 - 0x7CF0F000 F:\WINNT\system32\ole32.dll
0x7CDC0000 - 0x7CE13000 F:\WINNT\System32\NETAPI32.dll
0x77980000 - 0x779A4000 F:\WINNT\System32\DNSAPI.dll
0x75050000 - 0x75058000 F:\WINNT\System32\WSOCK32.dll
0x751C0000 - 0x751C6000 F:\WINNT\System32\NETRAP.dll
0x77BF0000 - 0x77C01000 F:\WINNT\System32\NTDSAPI.dll
0x77950000 - 0x7797B000 F:\WINNT\system32\WLDAP32.DLL
0x7C340000 - 0x7C34F000 F:\WINNT\System32\SECUR32.DLL
0x75150000 - 0x75160000 F:\WINNT\System32\SAMLIB.dll
0x769A0000 - 0x769A7000 F:\WINNT\system32\NDDEAPI.DLL
0x1FA30000 - 0x1FA46000 F:\WINNT\System32\sqlsrv32.rll
0x1F7F0000 - 0x1F80A000 F:\WINNT\system32\odbccp32.dll
0x74CB0000 - 0x74CCA000 F:\WINNT\system32\DBNETLIB.DLL
0x75500000 - 0x75504000 F:\WINNT\system32\security.dll
0x782D0000 - 0x782F2000 F:\WINNT\system32\msv1_0.dll
0x7C740000 - 0x7C7CC000 F:\WINNT\system32\CRYPT32.dll
0x77430000 - 0x77441000 F:\WINNT\system32\MSASN1.dll
0x77340000 - 0x77353000 F:\WINNT\system32\iphlpapi.dll
0x77520000 - 0x77525000 F:\WINNT\system32\ICMP.DLL
0x77320000 - 0x77337000 F:\WINNT\system32\MPRAPI.DLL
0x773B0000 - 0x773DF000 F:\WINNT\system32\ACTIVEDS.DLL
0x77380000 - 0x773A3000 F:\WINNT\system32\ADSLDPC.DLL
0x77830000 - 0x7783E000 F:\WINNT\system32\RTUTILS.DLL
0x77880000 - 0x7790E000 F:\WINNT\system32\SETUPAPI.DLL
0x7C0F0000 - 0x7C154000 F:\WINNT\system32\USERENV.DLL
0x774E0000 - 0x77514000 F:\WINNT\system32\RASAPI32.DLL
0x774C0000 - 0x774D1000 F:\WINNT\system32\rasman.dll
0x77530000 - 0x77552000 F:\WINNT\system32\TAPI32.dll
0x77360000 - 0x77379000 F:\WINNT\system32\DHCPCSVC.DLL
0x74CD0000 - 0x74CD8000 F:\WINNT\system32\DBmsLPCn.dll
0x0B990000 - 0x0B9E6000 F:\WINNT\system32\MSVCR71.dll
0x6D2E0000 - 0x6D2EE000 F:\j2sdk1.4.1_03\jre\bin\net.dll
0x782C0000 - 0x782CC000 F:\WINNT\System32\rnr20.dll
0x777E0000 - 0x777E8000 F:\WINNT\System32\winrnr.dll
0x777F0000 - 0x777F5000 F:\WINNT\system32\rasadhlp.dll
0x74FD0000 - 0x74FEE000 F:\WINNT\system32\msafd.dll
0x75010000 - 0x75017000 F:\WINNT\System32\wshtcpip.dll
0x77920000 - 0x77943000 F:\WINNT\system32\imagehlp.dll
0x72A00000 - 0x72A2D000 F:\WINNT\system32\DBGHELP.dll
0x690A0000 - 0x690AB000 F:\WINNT\system32\PSAPI.DLL
Local Time = Wed Mar 08 17:24:41 2006
Elapsed Time = 9294
# The exception above was detected in native code outside the VM
# Java VM: Java HotSpot(TM) Client VM (1.4.1_03-b02 mixed mode)
#I'm having the same problem.
One potential solutions is to use a custom SQL server JDBC driver instead of going through the ODBC bridge. This will minimize dependencies and should also improved performance. Hope this helps.
- Joe -
Problem: VSS error with 'SQL Server Backup to Windows Azure Tool' installed
When 'SQL Server Backup to Windows Azure Tool' is installed, shadow copies cannot be enable and backups fail. When attempting to enable shadow copies, we get a "volsnap" error: "The shadow copies of volume X were aborted because
of a failed free space computation". After uninstalling the "Tool", VSS works. Reinstalling "Tool" causes the problem to return.
While the error suggests a space issue, there is plenty of space on the server's two volumes. Additionally, another 100GB volume was added and VSS storage was allocated to it; still received the error.
Issue seems to point to 'SQL Server Backup to Windows Azure Tool'.
Environment: Hyper-V guest: "Windows Server 2012 R2 Standard" with "SQL Server 2008 R2 Standard". Using "Azure Storage" for SQL backups.
Suggestions?Hello,
Yes, we have a confirmed interference between the tool and the VSS Framework. This was identified very recently and is under investigation by the product group. Since the issue is within the filter driver shipped by the tool, that unfortunately means that
you currently need to choose between the tool and a working VSS Framework. If the latter is more important, then uninstall the tool (that will require a restart).
We apolologize for the inconvenience. I'm going to try to get the home page of the tool updated to avoid other situations like yours. Hopefully we should see a new version of the tool soon.
As a side note, recent versions of SQL Server can directly use Azure Storage as backup target, see
http://msdn.microsoft.com/en-us/library/jj919148(v=sql.110).aspx.
Regards,
Guillaume Fourrat - Microsoft France -
i have used type 2 driver for connectin to my SQL Server. Its working fine with normal java program. but when i used the same driver in my servlet its returning null pointer exception. i.e. Connection is null
here is the code i have used:
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
Connection conn =DriverManager.getConnection("jdbc:odbc:mydsn",
"username",
"password");That is THE type 1 driver by the way.
Anyway who knows. Have you considered using a type 4 (pure Java driver) instead? There are several available that work with SQL server including one from microsoft (not recommended) and one from sourceforge http://jtds.sourceforge.net/ (recommended)
I would strongly consider using a type 4 driver instead because the problem likely has something to do with it can't find the DSN or the bridge is not available on your servlet platform etc etc
FInally if your connection is null it suggests that you are swallowing an exception somewhere because DriverManager.getConnection will throw an exception if it can't connect (which appears to be the case). -
Versioning Error with SQL Server JDBC Driver
Hi,
I wrote a simple class for inserting rows into a database. The database is SQL Server 2000, and I am using weblogic's mssqlserver4 driver. The class works fine, but when I try to export the class as a remote object (using Sun's RMI implementation, not Weblogic RMI), I get the following error:
Exception in thread "main" weblogic.common.internal.VersioningError: No WebLogic packages defined in CLASSPATH at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:35) at weblogic.version.<clinit>(version.java:18)
at weblogic.jdbc.common.internal.FileProxy.initFileHandles(FileProxy.java:30) at weblogic.jdbc.mssqlserver4.BaseConnection.prepareConnection(BaseConnection.java:215)
at weblogic.jdbc.mssqlserver4.Driver.newConnection(Driver.java:34) at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:151) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171)
Can anyone tell me why this happens? What is difference between using the driver standalone and using it with RMI? Does it have anything to do with the fact that I'm using Javasoft RMI and not Weblogic RMI? I'm pretty sure I have the classpaths set up correctly.
Thanks,
BoYou seem to have done everything correctly and diligently. I would ask that you open
an official support case. -
JDBC Connection Error with Sql Server 2005
Hi
I am trying to connect the Sql Server 2005 thru jdbc but I am getting the following error.
SQLException: The TCP/IP connection to the host usselect.com/x-logs, port 1433 has failed. Error: usselect.com/x-logs. Please verify the connection properties and check that a SQL Server instance is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.
I am using sqljdbc4.jar (driver)
import java.sql.Connection; import java.sql.DatabaseMetaData; import java.sql.DriverManager; import java.sql.SQLException; public class testdb { public static void main(String s[]){ String userid="xxxx", password = "xxxxx"; String url = "jdbc:sqlserver://usselect.com/x-logs:1433"; Connection con = null; try { Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); }catch(java.lang.ClassNotFoundException e) { System.err.print("ClassNotFoundException: "); System.err.println(e.getMessage()); } try { con = DriverManager.getConnection(url,userid,password); } catch(SQLException ex) { System.err.println("SQLException: " + ex.getMessage()); } if(con!= null){ System.out.println("Got Connection."+con); }else{ System.out.println("Could not Get Connection"); } } }
Please advise.srinu1198 wrote:
By using Jdbc thin driver are we able to connect to mssql 2005 through windows authentication or not? "thin driver" refers to a specific Oracle driver.
Far as I know both the current (not older) MS driver supports windows auth. Certianly the jTDS driver does.
If yes what is the procedure. One starts by reading the docs. If necessary then one googles. -
Error with SQL Server 2000 and Tomcat 4.1.12
I'm using a JDBC Datasource with Tomcat 4.1.12 as follows.
Server.xml snippet:
<Resource name="jdbc/indemand" scope="Shareable" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/indemand">
<parameter>
<name>validationQuery</name>
<value>select top 100 * from Subscriber</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:microsoft:sqlserver://vc34:1433;databaseName=TibcoClearHouse</value>
</parameter>
<parameter>
<name>password</name>
<value>tibco_user</value>
</parameter>
<parameter>
<name>maxActive</name>
<value>10</value>
</parameter>
<parameter>
<name>maxWait</name>
<value>5000</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>com.microsoft.jdbcx.sqlserver.SQLServerDataSource</value>
</parameter>
<parameter>
<name>username</name>
<value>tibco_user</value>
</parameter>
<parameter>
<name>maxIdle</name>
<value>2</value>
</parameter>
</ResourceParams>
END OF Server.xml Snippet
My Web XML specifies the JDBC resource as follows:
<resource-ref>
<description>Clearinghouse DB Connectio</description>
<res-ref-name>jdbc/indemand</res-ref-name>
<res-type>com.microsoft.jdbcx.sqlserver.SQLServerDataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
When I cause a database access within my application, I get the following horrifying result. It's the "Error Establishing Socket" error that's worrying me, as I'm using the native Microsoft SQL Server Drivers. The ones in my lib directory are msutil.jar, msutil.jar, and mssqlserver.jar
Any thoughts?
John
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.thoughtworks.util.pool.JDCConnectionPool.getConnection(JDCConnectionPool.java:174)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnectionForTibco(ConnectionFactory.java:59)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnection(ConnectionFactory.java:40)
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:123)
at com.thoughtworks.clearinghouse.web.service.UserProfileService.validateUserNamePassword(UserProfileService.jav
a:16)
at com.thoughtworks.clearinghouse.web.servlet.LogonAction.actionExecuted(LogonAction.java:48)
at com.thoughtworks.clearinghouse.web.servlet.AbstractAction.execute(AbstractAction.java:38)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:437)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:470)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)
com.thoughtworks.clearinghouse.util.SystemException: failed to load user
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:147)
at com.thoughtworks.clearinghouse.web.service.UserProfileService.validateUserNamePassword(UserProfileService.jav
a:16)
at com.thoughtworks.clearinghouse.web.servlet.LogonAction.actionExecuted(LogonAction.java:48)
at com.thoughtworks.clearinghouse.web.servlet.AbstractAction.execute(AbstractAction.java:38)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:437)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:470)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)
Caused by: java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.thoughtworks.util.pool.JDCConnectionPool.getConnection(JDCConnectionPool.java:174)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnectionForTibco(ConnectionFactory.java:59)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnection(ConnectionFactory.java:40)
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:123)
... 38 more
Cause:
java.sql.SQLException: [Microsoft][SQLServer JDBC Driver]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:140)
at com.thoughtworks.util.pool.JDCConnectionPool.getConnection(JDCConnectionPool.java:174)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnectionForTibco(ConnectionFactory.java:59)
at com.thoughtworks.clearinghouse.util.ConnectionFactory.createConnection(ConnectionFactory.java:40)
at com.thoughtworks.clearinghouse.util.DatabaseUtility.getUserByName(DatabaseUtility.java:123)
at com.thoughtworks.clearinghouse.web.service.UserProfileService.validateUserNamePassword(UserProfileService.jav
a:16)
at com.thoughtworks.clearinghouse.web.servlet.LogonAction.actionExecuted(LogonAction.java:48)
at com.thoughtworks.clearinghouse.web.servlet.AbstractAction.execute(AbstractAction.java:38)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:437)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:264)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1109)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:470)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:260)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2396)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:170)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:405)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:380)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:508)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:533)
at java.lang.Thread.run(Thread.java:536)You can check two things
1. Whether the ports to the database server are blocked by a fire wall.
2. And more simpler and most probably the case here, you can try to findout if you can see the database server from the webserver. i.e. ping the database server from a console in the webserver. -
JMS error with SQL Server 2005 SP1
Hi all,
I have set up LC 8.0 with a SQL Server and the server seems to be running, however I get some errors in the log that I don't like. Can you help me fix this problem?
2008-07-23 12:06:49,197 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider
2008-07-23 12:06:49,213 ERROR [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnect failed: JMS provider failure detected:
javax.naming.NameNotFoundException: XAConnectionFactory
at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:223)
at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:229)
at $Proxy181.lookup(Unknown Source)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:151)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:245)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:173)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java :605)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl.run(JMSContainerInvok er.java:1471)
Sincerely
KimHi,
I found that in the log file. I follow the preparing to install livecycle Es guide to configure JMS with SqlServer 2005 SP1
jboss.mq:service=DestinationManager
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.jca:service=DataSourceBinding,name=DefaultDS
State: NOTYETINSTALLED
Depends On Me:
jboss.ejb:service=EJBTimerService,persistencePolicy=database
jboss:service=juddi
jboss:service=KeyGeneratorFactory,type=HiLo
jboss.mq:service=StateManager
jboss.mq:service=PersistenceManager -
Checkin error with sql server as backend database
Hello,
I get regulary the following error messages (attached as screenshot) when I'm try to checkin my current model.
The message states, that my database is in single user mode, but this isn't the case. I checked the many times.
My repository database is a Microsoft SQL Server 2008 SP3 64 Bit Enterprise Edition. Are there any known issues with this database?
With PowerDesigner 16.1 I didn't have such issues.
kind regards
ChristianHi Christian,
The error message is not referring to your database.
Within PowerDesigner, PD, some 'Unexpected Exceptions' are not really an issue (a true exception).
Here is an explanation for the error you are encountering:
PD has found that something potentially wrong happened with an action selection in the merge dialog. A single user has been the only one to work on the model, but the actions were not all selected by default (which is unexpected).
So PD decided by itself to select all the actions anyway.
The PD developers created this dialog to be a warning about this condition in order for it to be analyzed further if required.
Using the Comparison Legend from the Merge window:
[-+] object present only in model in the left pane (deletion for the merge dialog)
The action in question is now selected:
[-+]<Trigger> CompoundDeleteTrigger _adm_prepare_load
If you would like to pursue this further, a copy of the local model and a copy of the model already in the repository would be needed for review.
Regards,
Anthony -
Bcp error with SQL Server 2008
In working through the 70-432 training material, I have entered the follwing:
bcp AdventureWorks
.HumanResources.Department out
c:
\test/department.txt -c -S HOME -T
I receive the error message -- Could not find stored procedure'bcp'.
and a syntax error after c: What am I missing?Where are you entering these commands?
BCP is a command line program. NOte that there is a typo in teh code you pasted and is your server name HOME?
bcp AdventureWorks.HumanResources.Department out c:\test\department.txt -c -S HOME -T
Refer below for more details.
http://msdn.microsoft.com/en-us/library/ms162802.aspx| Sankar Reddy | http://sankarreddy.spaces.live.com/ | -
Jdeveloper connecting with SQL Server Express
Hi i am trying to connect jdeveloper with SQL Server Express. At the moment i am getting a TCP/IP connection to the host error message.
My connection string is as follows:
Class.forName("com.micorosoft.sqlserver.jdbc.SQLServerDriver")
Connection conn = DriverManager.getConnection("jdbc:sqlserver://mustang/sqlexpress; database = matt1; Uid = matt; Pwd = matt1")
Can someone please help me!Enable TCP/IP protocol. Select Microsoft SQL Server 2005>Configuration Tools>SQL Server Configuration Manager. In the SQL Server Configuration Manager select the node SQL Server 2005 Network Configuration>Protocols for SQLEXPRESS. Right-click on the TCP/IP node and select Enable. Restart the SQL Server (SQLEXPRESS) service. In Adminstrative Tools>Services, right-click on the SQL Server (SQLEXPRESS) service and select Restart.
To configure a JDBC connection with SQL Server 2005 Express, add SQL Server 2005 JDBC driver JAR file <Microsoft SQL Server 2005 JDBC Driver>/sqljdbc_1.0/enu/sqljdbc.jar to classpath. <Microsoft SQL Server 2005 JDBC Driver> is the directory in which SQL Server 2005 JDBC Driver zip file is installed.
Driver class for SQL Server 2005 database is com.microsoft.sqlserver.jdbc.SQLServerDriver. Connection URL for the default SQL Server 2005 database is jdbc:sqlserver://localhost:<port>.
In the connection URL, <port> is obtained from the SQL Server configuration Manager. When the SQL Server 2005 SQLEXPRESS is restarted the port number changes.
To obtain the <port> in the SQL Server Configuration Manager, select the node SQL Server 2005 Network Configuration>Protocols for SQLEXPRESS. Right-click on TCP/IP node and select Properties. Select the IP Addresses tab. In IP ALL, the TCP Dynamic Ports specifies the <port> value. The connection URL format for another database name is shown in following listing. -
Error JDBC - Connect java instance with sql server
We are working with SAP Netweaver 7.0 SP 18 and we need to upgrade to SP 23.
The XML generated contains only ABAP Stack but the SUM also load the Java tab.
This part of Java is giving me several problems Connection with SQL Server database 2005. Add image of the last error.
To continue forward I am evaluating the following:
1. How I can validate data Connection jdbc to connect to the database? How valid username and password that you use? Where
Best Regards!Hi Hidalgo,
The XML generated contains only ABAP Stack but the SUM also load the Java tab.
Please check for the following
1) Existence of j2ee related profile parameters in SAP profiles ( default, instance and start )
2) Existence of j2ee related folders on the SAP server
If you system is only ABAP stack, please remove information identified in option(1) and (2).
Hope this helps.
Regards,
Deepak Kori -
*****Error in Microsoft JDBC drivers for SQL Server 2000****
hi guys,
I am getting the following error in my application. The error seems to have thrown by Microsoft JDBC drivers for SQL Server 2000
The application tries to execute the the following query when the error is thorwn:
SELECT getDate(); // getDate is a function which returns currebt date time. The error is thrown occassionally. Other times the same query is executed correctly by the application.
Can any one help with this one.
The error is:
java.lang.NullPointerException
at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.setupTempFiles(Unknown Source)
at com.microsoft.jdbc.base.BaseImplStaticCursorResultSet.<init>(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.chainInServiceImplResultSets(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.getNextResultSet(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.commonGetNextResultSet(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQueryInternal(Unknown Source)
at com.microsoft.jdbc.base.BaseStatement.executeQuery(Unknown Source)
at com.sanderson.tallyman.util.TallymanDB.executeQuery(Unknown Source)
at com.sanderson.tallyman.util.TallymanDB.getCurrentDate(Unknown Source)
at com.sanderson.tallyman.operations.interfaces.RecordUpdateControl.updateRecord(Unknown Source)
at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processUpdate(Unknown Source)
at com.sanderson.tallyman.operations.interfaces.DebtInterfaceControl.processInterface(Unknown Source)
at com.sanderson.tallyman.operations.interfaces.InterfaceHandler$ProcessRecord.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
rgds,Hi,
Did you ever get an answer to this? I am also having this problem. -
Error while Installing WAS with SQL server
Hi all,
I am trying to install WAS with SQL server as Database. I am getting error at "Register SDM targets" section. We have given SQL server authentication mode to install WAS.
Following is the error Log....
Exception: [DataDirect][SQLServer JDBC Driver][SQLServer]Cannot open database requested in login 'HCL'. Login fails.
at com.ddtek.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.ddtek.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
at com.ddtek.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
at com.ddtek.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.ddtek.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.ddtek.jdbc.base.BaseConnection.open(Unknown Source)
at com.ddtek.jdbc.base.BaseDriver.connect(Unknown Source)
at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:149)
at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:472)
at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:253)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMVendorConnection(DBSCConnectionManager.java:214)
at com.sap.sdm.serverext.servertype.dbsc.extern.DBSCConnectionManager.createSDMConnections(DBSCConnectionManager.java:77)
at com.sap.sdm.serverext.servertype.dbsc.ConnectionManagerDecorator.createSDMConnections(ConnectionManagerDecorator.java:73)
at com.sap.sdm.serverext.servertype.dbsc.DatabaseTargetSystem.connect(DatabaseTargetSystem.java:140)
at com.sap.sdm.serverext.servertype.dbsc.DBSCDeploymentActionProcessor.executeAction(DBSCDeploymentActionProcessor.java:115)
at com.sap.sdm.app.proc.deployment.impl.PhysicalDeploymentActionExecutor.execute(PhysicalDeploymentActionExecutor.java:58)
at com.sap.sdm.app.proc.deployment.impl.DeploymentActionImpl.execute(DeploymentActionImpl.java:181)
at com.sap.sdm.app.proc.deployment.controllers.internal.impl.DeploymentExecutorImpl.execute(DeploymentExecutorImpl.java:51)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.executeAction(ExecuteDeploymentHandler.java:84)
at com.sap.sdm.app.proc.deployment.states.eventhandler.ExecuteDeploymentHandler.handleEvent(ExecuteDeploymentHandler.java:61)
at com.sap.sdm.app.proc.deployment.states.StateBeforeNextDeployment.processEvent(StateBeforeNextDeployment.java:78)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEventServerSide(InstContext.java:88)
at com.sap.sdm.app.proc.deployment.states.InstContext.processEvent(InstContext.java:74)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.doPhysicalDeployment(DeployerImpl.java:121)
at com.sap.sdm.app.sequential.deployment.impl.DeployerImpl.deploy(DeployerImpl.java:90)
at com.sap.sdm.control.command.cmds.Deploy.execute(Deploy.java:162)
at com.sap.sdm.control.command.decorator.AssureStandaloneMode.execute(AssureStandaloneMode.java:54)
at com.sap.sdm.control.command.decorator.AssureOneRunningSDMOnly.execute(AssureOneRunningSDMOnly.java:61)
at com.sap.sdm.control.command.decorator.SDMInitializer.execute(SDMInitializer.java:52)
at com.sap.sdm.control.command.decorator.GlobalParamEvaluator.execute(GlobalParamEvaluator.java:60)
at com.sap.sdm.control.command.decorator.AbstractLibDirSetter.execute(AbstractLibDirSetter.java:46)
at com.sap.sdm.control.command.decorator.ExitPostProcessor.execute(ExitPostProcessor.java:48)
at com.sap.sdm.control.command.decorator.CommandNameLogger.execute(CommandNameLogger.java:49)
at com.sap.sdm.control.command.decorator.AdditionalLogFileSetter.execute(AdditionalLogFileSetter.java:65)
at com.sap.sdm.control.command.decorator.AbstractLogDirSetter.execute(AbstractLogDirSetter.java:52)
at com.sap.sdm.control.command.Command.exec(Command.java:42)
at SDM.main(SDM.java:21)
Thanks in Advance
Regards
VasuHi Vasudevan,
Does you password contain any special characters?
Try using a simple password.
Regards
Daniel -
IDM with SQL server Error: Cannot find columns for the table...
Hi all,
I am Configuring IDM with SQL Server repository and ran into this error.
'Cannot find columns for the table 'object'
.....jdbc...[SQL Server]Invalid object name 'object'
Can anybody please help me!!
GYes, permissions are very important. I ran into a similar problem because I didn't have the correct permissions. Make sure the user has the following permissions:
CREATE ANY TABLE
ALTER ANY TABLE
DROP ANY TABLE
CREATE ANY PROCEDURE
EXECUTE ANY PROCEDURE
DROP ANY PROCEDURE
Also, make sure there is enough space in the default tablespace of that user.
HTH
~Suvesh
Maybe you are looking for
-
How to show only filtered rows in download file of Interactive report
I have an interactive report. If i filter column A and don't want to show column A in the download spreadsheet or PDF(NVL(:REQUEST,'column A') NOT IN('XLS','PDF'). All of the rows will show up in my download file. How could i show just filtered rows
-
Discovered my 3GS no longer shows on the calendar nonrepeating events before 9/23/12. However, those events show in icloud and on my laptop. We tried reloading icloud but still missing. Guess is due to downloading of IOS6 - if so, why didn't Apple le
-
Hi All, Please help me out against this issue. I have spent so much (3 working days) time just figuring out what is the issue and its solution. I am learning Tabular Mode and trying to create a mode based on PowerPivot model. I am getting following e
-
How do I make my Apple Airport Base Station wireless connection secure please?
-
HT1414 How can I get my contacts back after update 5.1.1? I've tried everything
After updating my Iphone 4 to the 5.1.1 version all my contacts are now gone. Ive tried restore and all the tricks everyone suggests. What else can I do? Thanks!