sql server indexing using dih problem
(SQLServerDriver.java:841) at org.apache.solr.handler.dataimport.JdbcDataSource$1.call(JdbcDataSource.java:133) at org.apache.solr.handler.dataimport.JdbcDataSource$1.call(JdbcDataSource.java:119) at org.apache.solr.handler.dataimport.JdbcDataSource.getConnection(JdbcDataSource.java:298) at org.apache.solr.handler.dataimport.JdbcDataSource.access$200(JdbcDataSource.java:43) at org.apache.solr.handler.dataimport.JdbcDataSource$ResultSetIterator.init(JdbcDataSource.java:173) ... 32 more/str str name=time-taken0:0:29.641/str /lst /lst /lst str name=statusidle/str str name=importResponseConfiguration Re-loaded sucessfully/str - lst name=statusMessages str name=Time Elapsed0:0:29.641/str str name=Total Requests made to DataSource1/str str name=Total Rows Fetched0/str str name=Total Documents Processed0/str str name=Total Documents Skipped0/str str name=Full Dump Started2009-08-31 15:21:22/str /lst str name=WARNINGThis response format is experimental. It is likely to change in the future./str /response Please let me know what might be the reason? -- View this message in context: http://www.nabble.com/sql-server-indexing-using-dih-problem-tp25220884p25220884.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: sql server indexing using dih problem
On Mon, Aug 31, 2009 at 3:25 PM, rameshgalla ramesh.ga...@cognizant.comwrote: Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host 10.232.6.38, port 1433 has failed. Error: Connection refused: connect. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port, and that no firewall is blocking TCP connections to the port.. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(SQLServerException.java:170) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1049) at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:833) at The reason is given in the exception itself. The driver is not able to connect to your server at port 1433. Either your server is down or the host/port is incorrect or there is a firewall which is blocking access. -- Regards, Shalin Shekhar Mangar.