Help - JDBC MS SQL Server and Cursors Error
Hello,
Please help. I am using weblogic 8.1 and MS SQL Server 2000. Using JDBC. I have am calling a stored procedure which outputs a CURSOR. I haveing problems specifying the right java.sql.Type for this. I tried java.sql.Type.OTHER but it fails. The code is as follows
Connection conn = null;
CallableStatement stmt = null;
String sqlProc = "{ call GetDocumentDetails(?,?) }";
try {
conn = this.getConnection();
stmt = conn.prepareCall(sqlProc);
stmt.setInt(1, docId);
stmt.registerOutParameter(2,Types.OTHER);
stmt.execute();
ResultSet rs = (ResultSet) stmt.getObject(2);
while(rs.next()) {
The exception that I get is
java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver.
at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
PLEASE HELP.
Thanks in advance
GM
hi llturro,
Thanks for answering my question. I have tried out what you suggested, but I still can't fix my problem. The following are the messages that display when I try to run my servlet. It seems that the DataSource, Connection and Statement are ok, however when it comes to the ResultSet the error message appear. What's wrong with my ResultSet coding ?
ResultSet rs = stat.executeQuery("SELECT ISBN FROM BOOKSINFO WHERE ISBN='"+primarykey+"'");
setEntityContext Method
Find by primary key
DataSource OK
Connection OK
Primary Key = 013-00-675721-9
Statement OK
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.lang.NullPointerException
<<no stack trace available>>
Similar Messages
-
Need help:Urgent:MS SQL Server and J2EE Server
Hello,
i am developing simple bean managed persistence bean. i want to know how could i use microsoft SQL Server as my database with ejb's in J2EE. i don't want to use cloudscape rather i want to connect through jdbc bridge with sql server. can any body help me out ?
i have developed DSN for my database with the name of DsnProduct and user name for DB is guest and password is guest123.
so do i have to change configuration is my J2EE server . or put some additional code. so far i have added the following line in my implementation class
private String dbName= "java:comp/env/jdbc/ProductDB";
DataSource ds = (DataSource) ic.lookup(dbName);
con = ds.getConnection("guest","guest123");
moreover in server configuration i have added driver
sun.jdbc.odbc.JdbcOdbcDriver
and also provide the following JNDI Name
jdbc/ProductDB
and
it's url is
jdbc:odbc:DsnProduct
i am thankfull for your support.
[email protected]hi llturro,
Thanks for answering my question. I have tried out what you suggested, but I still can't fix my problem. The following are the messages that display when I try to run my servlet. It seems that the DataSource, Connection and Statement are ok, however when it comes to the ResultSet the error message appear. What's wrong with my ResultSet coding ?
ResultSet rs = stat.executeQuery("SELECT ISBN FROM BOOKSINFO WHERE ISBN='"+primarykey+"'");
setEntityContext Method
Find by primary key
DataSource OK
Connection OK
Primary Key = 013-00-675721-9
Statement OK
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.rmi.RemoteException: Unknown Exception/Error thrown by EJB method.; nested exception is:
java.lang.NullPointerException
java.lang.NullPointerException
<<no stack trace available>> -
BOXI R2 deployment on Solaris, data access to SQL Server and DB2
<p>Have you deployed BusinessObjects XI Release 2 on Solaris and are accessing Microsoft SQL server 2000/2005? How about DB2? We had planned on using JDBC for SQL Server, and StarSQL 5.x for DB2. We are having trouble with configuration planning.</p><p>Anyone have experience with this?</p>
<p>Have you deployed BusinessObjects XI Release 2 on Solaris and are accessing Microsoft SQL server 2000/2005? How about DB2? We had planned on using JDBC for SQL Server, and StarSQL 5.x for DB2. We are having trouble with configuration planning.</p><p>Anyone have experience with this?</p>
-
Need Guide to create a table in SQL Server and Process data for JDBC
Dear All,
Scenario:JDBC to JDBC
I need to practice JDBC to JDBC scenario and for that i need to create a table in SQL server for sender ,receiver and update i have installed SQL Server and no idea about creation of table and Connection string for PI.
I want you to explain each and every step for the Table Creation ,Driver and connection string.
Thanks in Advance.Try searchin in the forum and then google. This forum is not for teaching the basics.
VJ -
VCM installation help needed on SQL DB and Reporting server
Hi All,
I'm new to VCM and now i got stuck at the SQL DB and Report server portion.
I'm running the vcm server on VM and the SQL is a physical server, both are sitting on the same LAN.
I have create the SQL DB but VCM just fail to validate the DB and report server.
I login to VCM using a Domain account for installation, and i tried to testing the DB using ODBC from the window, result fail.
Error message as attach.
I'm now totally lost on SQL portion.
My Question:
Is there any configuration needed on SQL DB?
How to get the reporting server to working?
What port is needed to it all working??
VCM server Ms Win2012.
SQL version 2012.
Many thanks to all who reply.Hi Simonhoo79,
For SSRS, first check whether the report server link is accessible from your browser : "http://s01-fes-vcm1:80/ReportServer" . If you continue to get 404 error there also, then you need to reconfigure you report server first before proceeding to vcm installation. Follow the steps on below link on how to reconfigure report server using report services configuration Manager for 404 error.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/75910bcb-a879-4eb7-9757-acc45201fa3a/can-not-connect-to-reportserver-http-404-file-not-found?forum=sqlexpress
For SQL server ODBC connection,
Dont create ODBC connection for SQL Native Client. Create ODBC connection for SQL Server.
1. Open ODBC Data Source Administrator
2. Click User DSN tab and Click Add button.
3. Select SQL server and click finish
4. Give name and description and Give the SQL server name (with instance name if your using named instance) or IP in the Server text box.
5. Click Next and select either Windows authentication or sql authentication based on your SQL server authentication mode and click next.
6. If the details given are correct then it will proceed further and check "Change the dafault database to" to your VCM database
7. Click next and finish and try test data source.
VCM 5.7.2 and below will support installation only on windows server 2008 R2 and it doesn't support windows server 2012 but it support both 2008 and 2012 sql servers. -
How to establish a trusted connection with JDBC for SQL SERVER 2000
Hi!I am using jdk 1.4 and eclipse 3.3.
I create a servlet in eclipse with in-build tomcat.
When I run it ,it was working perfectlly has it was suppose to work.
In this servlet I connect to a sql 2000 database using jdbc-odbc bridge driver.
But when I tried to deploy the servlet on tomcat 5.5 manully on the same machine ,it gave me error saying
[Microsoft][SQLServer JDBC Driver][SQLServer]Login failed
for user 'sa'
I searched around some post and found that ok ,I need trusted connection
But I have 2 Questions
1). Why was in eclipse I was able to connect to the SQL server and why not in the servlet which I deployed manully on tomcat.
2). How do I create a trusted connection with JDBC for SQL server 2000
Thnaks for your help in advance.Hi! duffymo ,QussayNajjar ,dvohra09 .
Thank for help.
The ideas are really great.
I am trying generate reports for my company.
When I used eclipse the code worked perfectly.
below is code which I used
out.println("Calling For Class Name<br>");
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
out.println("Calling For Class Name success Now calling database <br>");
1). jdbcConnection = DriverManager.getConnection("jdbc:odbc:SQLJasper");
2). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb");
3). jdbcConnection = DriverManager.getConnection("jdbc:odbc:Driver={SQL Server};Server=ServerName;Database=tempdb","UID=UserName","Password=Password");
out.println("connecting to database success<br>");
I had tried to connect the database using this three way.
In 1st I tried using DSN name .
Next 2 self explainer for expert like you.
I used to 2nd variant to connect in eclipse and it worked fine.
I not an expert in java ,I just doing some research on jasperReport.
My best guest is that eclipse is using some library files of which I have no clue.
Thank's for your help,I appretiate it.
Once again thank a billion.
Sorry for the messy righting. -
JDBC - MS SQL Server 2005 with multible instances
I want to get data from a Microsoft SQL Server via JDBC. We have such a scenario and till now it works fine. Now we have a second instance at the sql server and we want to connect to this instance. I've found the following MSD article:
http://msdn2.microsoft.com/en-us/library/ms378428.aspx
<b>SQL Server 2000 and SQL Server 2005 allow for the installation of multiple database instances per server. Each instance is identified by a specific name. To connect to a named instance of SQL Server, you can either specify the port number of the named instance (preferred), or you can specify the instance name as a JDBC URL property or a datasource property. If no instance name or port number property is specified, a connection to the default instance is created. See the following examples:
To use a port number, do the following:
jdbc:sqlserver://localhost:1433;integratedSecurity=true;<more properties as required>;
To use a JDBC URL property, do the following:
jdbc:sqlserver://localhost;instanceName=instance1;integratedSecurity=true;<more properties as required>;</b>
Because the named instance has no explicit port I've tried to use the second one but this doesn't work. I've tried all possible combinations of these parameters but either I get an error or my adapter connects to the first instance
Any idea how I can connect to the second named instance?We have also a SQL server 2000 instance at the same server. Yesterday I have spoken with the sql server admin and he told me that he has disconnect the sql server 2000 databases whatever this means. :-D
Now all works fine. Thank you for your help
BTW I use the following connection string:
jdbc:sqlserver://my_db_server;instanceName=my_instance_name;DatabaseName=my_db_name -
MX7 SQL Server 2005 datasoucre error
Webserver is Windows 2003 RC2, MX7.02
SQL Server is Windows 2003 RC2, SQL Server 2005 (9.0.1399)
CF and SQL are on seperate machines
[edit: the fix]
OK, gotta love those netops guys.
So we were narrowing it down to server -> server
communication issues...specifically windows authentication.
We set up a SQL Server user on the SQL Server and set up the
datasource in coldfusion that used that SQL Server user (not
DOMAIN\user, just user) and skipped the whole System DSN on the
webserver and it works.
So the long and the short of it is that there seems to be
some network trust issue between our app server (cf) and our db
server (sql) and we are unable to set up datasources the way we
used to (from win2k/cf5 -> win2k3/sql2005). Oh well.
[/edit]
[Edit: additional info]
SQL Server logs give this error message:
Error: 18456, Severity: 14, State: 6.
I've looked up this error message on msdn (
http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx)
and they say it means "Attempt to use a Windows login name with SQL
Authentication"
I've made sure that SQL Server is running in "SQL Server and
Windows Authentication Mode" (and restarted). No change. Of course
Adobe says that you HAVE to use "SQL Server and Windows
Authentication Mode" and Microsoft say the fix to the error is to
chose "Windows Authentication Mode". Grrr.
I've tried changing the JDBC URL to the IP of the SQL Server
and I get the same error mesaage. I purposely fudge the IP and I
get a totally different "time out" error (duh ;^) So something
about the way Cold Fusion talks to SQL Server isn't quite right.
I feel dumb asking this, but is there any specific
documentation about connecting MX7 to SQL Server 2005? The
documenation on livedocs refers to SQL Server 2000 (I think...but
I'm sure it's not talking about 2005). I'm beginning to wonder if
there is some stupid little step that I missed somewhere along the
way when setting things up...*sigh*
[/Edit]
I get the following error when attempting to set up the
datasource in Coldfusion administrator:
Connection verification failed for data source: wamaxDS
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed
for user 'UWT\cfusion2'.
The root cause was that:
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for
user 'UWT\cfusion2'.
Now, I've got our production box which is running CF 5
connecting to the same database on the same SQL server and does NOT
get the 'Login failed for user' error...which leads me to believe
that it's not a simple permissions issue. To be clear my CF5 box
connects fine to the database. My CF7 box simply will not.
I've installed the latest JDBC drivers and set up a
datasource that generates the error above (I get the same error
when trying to set it up as "Microsoft SQL Server" with the obvious
exception of the driver in the error being different).
I've searched the forums and did the TCP/IP fix.
I've tried setting the ODBC DSN up in windows using "windows
authentication" and the "mixed mode"...I'm just lost here.
I've lost track of the combinations of things I've tried to
get this to work (ya know how you get into "try anything and pray
mode"?...that was me all day today).
Hopefully I've provided enough information to get someone
started on helping me. If I've left anything out, please chastise
me and then let me know what I need to let you know. Sorry if this
message is incoherent...my brain is mush *sigh*.Hi,
I presume, this is how you have placed your code
Code Snippet
-- Retrive the product archive record
select * from dbo.api_userArchive where isActive = 1
Seems just fine. Could you post the error. Also try posting the entire code
HTH,
Suprotim Agarwal
http://www.dotnetcurry.com -
MS SQL Server with Cursor Problem
Dear all:I use JDBC type four connect with MS SQL Server and the language is jsp.
I run it on my local computer is ok.If I run it on the other computer.I get this error messege.
javax.servlet.ServletException: [Microsoft][SQLServer 2000 Driver for JDBC]Error setting up static cursor cache.
If someone get some or can surve this qusition.
Please tell me.thinks you kind.Jamie,
Did you ever get a reply from anyone regarding this problem. I too am having a similar problem and would like to know the solution. -
Problem in Creating a JDBC System - SQL Server
Hi All
I failed in creating a JDBC System(SQL Server). I am using SAP EP 7.0 SP 9. I tried to create the JDBC system with the following properties:
I am listing them Category wise:
Connection Properties:
1. Connection Timeout: 300
2. Connection URL: jdbc:sap.sqlserver://<server name> : <port name>; DatabaseName=master
3. Driver Class Name: com.sap.portals.jdbc.sqlserver.SQLServerDriver
4. Validate Connection: Yes
UserManagement Properties:
5. User Mapping Type: admin;user
Please help me out in making this work. And let me know if any changes to incorporated.
Regards,
Vijay.Hi vijay,
I have tried this thing sometime back. But when i create a JDBC system, I never give the <b>Connection Timeout</b> and change the<b> Validate Connection</b> from No to Yes. I just give the <b>Connection URL</b> and the <b>Driver Class Name</b> in the Connection Properties dropdown.
Try making these changes and check whether the user mapping is done correctly. Also check whether the Connection URL and the Driver Class Name are correct or not. Have a look at the following link:
<a href="https://www.sdn.sap.com/irj/sdn/wiki?path=/display/VC/JDBC%2bConnection%2bSetup">https://www.sdn.sap.com/irj/sdn/wiki?path=/display/VC/JDBC%2bConnection%2bSetup</a>
Let me know if this works.
Bye
Ankur
Reward points if it helps!! -
Microsoft SQL Server 2014 Setup error: Wait on the Database Engine recovery handle failed
Hi,
Having this annoying error trying to install SQL Server 2014 (RTM). I saw it's been asked several times... But each post seems a different cause and no definitive answer...
I'm not doing an upgrade, so no "sa account" issue.
Tried different media. Even three different distributions: trial, Standard and Enterprise.
Tried disabling Microsoft antivirus/firewall.
Of course tried restarting, updating, installing, uninstalling, repairing, etc., etc.
I noticed the users folders under C:\Users weren't created. (Maybe something related to permissions?) After playing around, I managed for the users to be created and the service started. Though I couldn't log in.Summary for last "repair" attempt:
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2068578302
Start time: 2014-04-27 23:54:21
End time: 2014-04-27 23:59:48
Requested action: Repair
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, and then try the setup process again.
Next step for DQ: Use the following information to resolve the error, and then try the setup process again.
Next step for FullText: Use the following information to resolve the error, and then try the setup process again.
Next step for LocalDB: Use the following information to resolve the error, and then try the setup process again.
Machine Properties:
Machine name: CHARLY13C
Machine processor count: 4
OS version: Windows 8
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered Configured
SQL Server 2012 DENALI MSSQL11.DENALI Database Engine Services 1033 Enterprise Edition 11.1.3128.0 No Yes
SQL Server 2012 LocalDB 1033 Express Edition 11.1.3128.0 No Yes
SQL Server 2014 HEKATON MSSQL12.HEKATON Database Engine Services 1033 Enterprise Edition 12.0.2000.8 No Yes
SQL Server 2014 HEKATON MSSQL12.HEKATON Full-Text and Semantic Extractions for Search 1033 Enterprise Edition 12.0.2000.8 No Yes
SQL Server 2014 HEKATON MSSQL12.HEKATON Data Quality Services 1033 Enterprise Edition 12.0.2000.8 No Yes
SQL Server 2014 Management Tools - Basic 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
SQL Server 2014 Management Tools - Complete 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
SQL Server 2014 Client Tools Connectivity 1033 Enterprise Evaluation Edition 12.0.2000.8 No Yes
SQL Server 2014 LocalDB 1033 Express Edition 12.0.2000.8 No Yes
Package properties:
Description: Microsoft SQL Server 2014
ProductName: SQL Server 2014
Type: RTM
Version: 12
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: Enterprise
User Input Settings:
ACTION: Repair
AGTDOMAINGROUP: <empty>
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: <empty>
AGTSVCSTARTUPTYPE: Manual
ASCONFIGDIR: Config
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
ENU: true
FAILOVERCLUSTERGROUP: <empty>
FAILOVERCLUSTERNETWORKNAME: <empty>
FTSVCACCOUNT: NT Service\MSSQLFDLauncher$HEKATON
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS: false
INSTANCENAME: HEKATON
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
QUIET: false
QUIETSIMPLE: false
SQLSVCACCOUNT: NT Service\MSSQL$HEKATON
SQLSVCPASSWORD: <empty>
UIMODE: Normal
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\ConfigurationFile.ini
Detailed results:
Feature: Management Tools - Complete
Status: Passed
Feature: Client Tools Connectivity
Status: Passed
Feature: Management Tools - Basic
Status: Passed
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
Feature: Data Quality Services
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
Feature: Full-Text and Semantic Extractions for Search
Status: Failed: see logs for details
Reason for failure: An error occurred for a dependency of the feature causing the setup process for the feature to fail.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x84B40002
Error description: The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=12.0.2000.8&EvtType=0x2841E06E%401204%402&EvtType=0x2841E06E%401204%402
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: LocalDB
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, and then try the setup process again.
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Feature: Setup Support Files
Status: Passed
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20140427_235420\SystemConfigurationCheck_Report.htm -
Error: [Microsoft][ODBC SQL Server Driver]Protocol error in TDS stream
hello,
our application vendors are receving the below errors while running their data load job.I spoke to our networking team member and he said everything looks good on the networking side .Can someone please help me with the below errors.we are using
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64) Enterprise
Edition: Core-based Licensing (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1).
Windows OS:windows server 2008 R2 sp1
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
|Data flow DIM_CONTRACT_SWAM_INIT_LOAD_DF|Loader Key_Generation_DIM_CONTRACT
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
ODBC data source <HPWDBOE001> error message for operation <SQLExecute>: <[Microsoft][ODBC SQL Server
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
Driver][DBNETLIB]ConnectionWrite (send()).
7280
6920
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.>.
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
|Data flow DIM_EMPLOYER_GROUP_SWAM_INIT_LOAD_DF|Reader TCRdr_9
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
ODBC data source <serverName> error message for operation <SQLExecute>: <[Microsoft][ODBC SQL Server Driver]Protocol error in
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
TDS stream
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (recv()).
6760
6164
DBS-070401
6/5/2014 1:17:24 PM
[Microsoft][ODBC SQL Server Driver][DBNETLIB]General network error. Check your network documentation.>.
I googled and found the below link the below link which asked me to enable named pipes.I enabled
namped pipes in the sql server Network configuration.I havent yet restarted the sql services as this is a prod box.I will do it later in the evening today.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/69149a71-3c15-4c95-9f95-a30db458abeb/sql-server-2005-communcations-errors-through-odbc?forum=sqldataaccess
Can someone help me with these errors.
Thanks
luckyThank you Erland.
I dont see any crash dumps in sql server.I checked the tcp chimney and its set to automatic.I am not knowing what to look at to resolve this issue.
if its the issue with the client API can i ask our vendor to check the client?
Our networking member gave the following report:
No problems on vlan 14 or your port the top is from the switch to your server then bottom is from my pc to your server
SP_DC_CORE_VSS# ping 10.10.12.228
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.12.228, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
SP_DC_CORE_VSS#
lucky -
sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
but it does not work.
Plz give the exact soln to solve this error.sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
but it does not work.
Plz give the exact soln to solve this error.
So when you tried starting SQL server service it gave the error right ? or when you click on SQL server services in SQL server configuration manager(SSCM) you get this error. Can you be more clear. As far as I read your question it has something
to do with permission. Close SSCM window and this time right click on SQL server configuration manager and select run as administrator and check if you can see SQL server services
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles -
JDBC MS SQL Server driver catch SQLException on Update statement
Hi,
We change the driver for the BEA WebLogic Type 4 JDBC MS SQL Server driver
driver=weblogic.jdbc.sqlserver.SQLServerDriver
url=jdbc:bea:sqlserver://db_name:port_number
since we use this driver we got an error when the application try to update a field date type with a NULL value.
Before, we use this driver and we didn't have this error
driver=com.inet.tds.TdsDriver
url=jdbc:inetdae:ammtl1sqls01:1961
The stack is:
Failed to update - id [updateItemBranch] - parameterObject [xxx.domain.store.Item@b0237c].
Cause:com.ibatis.common.jdbc.exception.NestedSQLException:
--- The error occurred in com/gildan/ecrm/persistence/sql/Item.xml.
--- The error occurred while applying a parameter map.
--- Check the updateItemBranch-InlineParameterMap.
--- Check the parameter mapping for the 'availableDate' property.
--- Cause: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver
Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driverCarol Villeneuve wrote:
Hi,
We change the driver for the BEA WebLogic Type 4 JDBC MS SQL Server driver
driver=weblogic.jdbc.sqlserver.SQLServerDriver
url=jdbc:bea:sqlserver://db_name:port_number
since we use this driver we got an error when the application try to update a field date type with a NULL value.
Before, we use this driver and we didn't have this error
driver=com.inet.tds.TdsDriver
url=jdbc:inetdae:ammtl1sqls01:1961
The stack is:
Failed to update - id [updateItemBranch] - parameterObject [xxx.domain.store.Item@b0237c].
Cause:com.ibatis.common.jdbc.exception.NestedSQLException:
--- The error occurred in com/gildan/ecrm/persistence/sql/Item.xml.
--- The error occurred while applying a parameter map.
--- Check the updateItemBranch-InlineParameterMap.
--- Check the parameter mapping for the 'availableDate' property.
--- Cause: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driver
Caused by: java.sql.SQLException: [BEA][SQLServer JDBC Driver]The specified SQL type is not supported by this driverHi. You should do two things:
1 - Contact BEA support for the very latest versions of the weblogic drivers.
2 - show us the actual jdbc code being called, and the full original stacktrace
of the SQLException.
Joe -
SQL Server Failover Clustering error
Hi All,
I am currently setting up 2-node SQL Server cluster but I am getting error when doing the failover test from Node2 to Node1.
Here is the quick overview of what I have so far.
1. Setup the failover cluster for both nodes, public and private network, cluster disks for Quorum, MSDTC and SQL, etc.
2. Run validation configuration before creating the cluster. Validation report completed successfully with no errors/warnings.
3. Created cluster, created MSDTC cluster and installed SQL server on both nodes.
Now I am doing some failover test on whether cluster resources will failover from Node1 to Node2 and Node2 to Node1.
Failover Test: Active Node is Node1.
1. Disable Public network on Node1.
2. Failover to Node2 -> successful
3. Enable Public network on Node1.
Problem:
After the failover to Node1, I tried to failback the resources from Node2 to Node1 by disabling the public network on Node2 (which is the active Node after the failover from Node1 to Node2) but the cluster resources won't failback to Node1.
Failback from Node2 to Node1 -> failed
1. Disable Public network on Node2.
2. Failback to Node1 -> failed
- Cluster Name and Cluster IP ->
failed
- SQL cluster group (SQL name, SQL IP address, Analysis, SQL server and SQL Server Agent) ->
failed
MSDTC cluster group -> failed back successfully to Node1
3. Enable Public network on Node 2.
4. Manually online Cluster Group and SQL cluster group
I tried to Manually online the Cluster Group and SQL cluster group but it CANNOT be online unless I enable the Public network on Node2. I have checked on the cluster event log and I am getting some event ID 1077 and 1069 errors and Event ID 1069 and 1205.
Here are some of the logs on the cluster events.
Event ID 1069: The Cluster service failed to bring clustered service or application 'SQL_Group' completely online or offline. One or more resources may be in a failed state. This may impact the availability of the clustered service or application.
Event ID 1205: Cluster resource 'SQL IP Address 2 (db-vip)' in clustered service or application 'SQL_Group' failed.
Anyone experience the same issue before? Appreciate if someone can point me to right direction to resolve the issue.
Thanks in advance for your feedback.
BTW, failover and failback works perfectly when I try to reboot the Active node. Resources failed over successfully from Node1 to Node2 and vice versa when I reboot the server.
Thanks again.
Regards,
IvanHi,
In above node test process 6, after “disable public network on node 2” the two cluster should still have private heartbeat network communication, check can you ping node 1 now?
Check event viewer, whether you received Event 1069 in node 1? Refer to this article to troubleshoot this issue:
Event ID 1069 — Clustered Service or Application Availability
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
Check and correct any problems with the application or service associated with the resource. For example, if the application or service cannot start within reasonable time limits, diagnose and resolve the issues that cause slow starting.
Check and correct any problems with cables or cluster-related devices.
Adjust properties for the resource in the cluster configuration, especially the value for Pending timeout for the resource. This value must allow enough time for the associated application or service to start. For more information, see "Viewing the value
for Pending timeout for a resource."
To view the value for Pending timeout for a resource:
To open the failover cluster snap-in, click Start, click Administrative Tools, and then click Failover Cluster Management. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
In the Failover Cluster Management snap-in, if the cluster you want to manage is not displayed, in the console tree, right-click Failover Cluster Management, click Manage a Cluster, and then select or specify the cluster that you want.
If the console tree is collapsed, expand the tree under the cluster you want to manage, and then expand Services and Applications.
In the console tree, click a clustered service or application.
In the center pane, if you cannot see the clustered resource that you want to view, expand one or more visible resources until you see the clustered resource.
Right-click the resource you want to view, click Properties, and then click the Policies tab.
Under Pending timeout, view the setting. Make sure it allows enough time for the associated application or service to start.
For more information please refer to following MS articles:
Network failure detection and recovery in a two-node Windows Server 2000 cluster
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support
Maybe you are looking for
-
Stored Proc to create .csv file from table
Hi all, I have a table with 4 columns and 10 rows. Now I need a stored proc to create a .csv file from the table data. Here the scripts to create a table and insert the row's. Create table emp(emp_id number(10), emp_name varchar2(20), department varc
-
Need to create two nodes based on one condition in message mapping.
Hi Experts, In my mapping I have two different nodes. If my condition is true then only one node should be created otherwise both the nodes should be created. requirement is I need to print. one header before first item record and aft
-
Report Painter - Income Statement Report
Hi SAP Experts, I'm trying to enhance an existing Income Statement Report (table GLPCT) by adding the PLAN (table GLPCP) columns. Right now, PLAN columns has no data when I execute it. Report Layout: Profit & Loss ACT-2007 ACT-2006 PLAN-2007 PLAN-
-
Moving iTunes to a new hard drive
I followed Apple's instructions to move iTunes when I changed the hard drive on my first generation MacBook Pro (i.e., consolidate, change the media folder location), but when I opened a brand new version of iTunes on the new drive (holding down the
-
Just FYI so this doesn't ruin anyone else's day ... I synched my calendar with Outlook 2003 on XP. All is well. Then fall daylight savings happened last Sunday. The iPhone switched just fine. However, the iPhone software automatically advanced all my