SQL Server 2005 Vista Problems

I have 3 databases in SQL Server 2005 that I want to connect
to. Everything works fine in XP, but when I try to set it up on
Vista I get all sorts of problems. All software is latest version
with all available updates installed.
After restarting the Vista computer, the first database I
select in CF administrator connects successfully, but the other two
return Connection Reset error. It doesn't matter which of the 3 I
select, just the first one connects.
However, whichever one it is that CF confirmed was
successful, when accessed from a CF page also returns Connection
Reset error.
The security settings in SQL Server are the same for each
database.
Anyone got any idea how to solve this problem??
Doug

The one that was connecting was connecting to port 1434. I
have now locked it down and only port 1433 is available. Now I get
the same error every time I try to make a connection:
Error establishing socket. Connection refused: connect
Apart from the port number (which was not 1433 on my old XP
computer) everything else is identical.
Is there some setting in Vista out of the box that has to be
changed to get CF to connect to SQL Server 2005?
Doug

Similar Messages

  • MS SQL Server 2005 Capture Problem

    Hi Friends
    I am looking to migrate SQL Server 2005 standard edition to oracle 10g. for that I am using oracle SQL Developer workbench tool 1.5.3 but I am getting error while capturing the MS SQL Server database.
    One thing I noticed, after creating repository database that Under the repository schema the package body for MD_META* package is showing Invalid, I tried to compile it manually but still its in Invalid state I don't know the reason why it's in Invalid state.
    My Detals are as below
    Oracle 10.2g Standard edition without any patchset.
    MS SQL Server 2005 Standard Edition
    SQL Developer 1.5.3
    Please can anybody help me out in this issue ? Waiting for your reply
    Regards
    Anandkumar S.M

    Hello,
    have you tried what happens if you delete the migration repository and recreate it?
    If the problem persists:
    1. Make sure the user that you are using has the following privileges
    Roles
    CONNECT WITH ADMIN OPTION
    RESOURCE WITH ADMIN OPTION
    Privileges
    ALTER ANY ROLE
    ALTER ANY SEQUENCE
    ALTER ANY TABLE
    ALTER TABLESPACE
    ALTER ANY TRIGGER
    COMMENT ANY TABLE
    CREATE ANY SEQUENCE
    CREATE ANY TABLE
    CREATE ANY TRIGGER
    CREATE VIEW WITH ADMIN OPTION
    CREATE PUBLIC SYNONYM WITH ADMIN OPTION
    CREATE ROLE
    CREATE TABLESPACE
    CREATE USER
    DROP ANY SEQUENCE
    DROP ANY TABLE
    DROP ANY TRIGGER
    DROP TABLESPACE
    DROP USER
    DROP ANY ROLE
    GRANT ANY ROLE
    INSERT ANY TABLE
    SELECT ANY TABLE
    UPDATE ANY TABLE
    2. Run the following in SQLPLUS as the user that is being used to create the repository
    SQL> alter package md_meta compile ;
    3. If you then get a message like:
    Warning: Package altered with compilation errors.
    then issue:
    SQL> show errors
    4. If that does not show any error, what does the following query show:
    alter package md_meta compile;
    select text from dba_errors where name ='MD_META' and owner ='<your owner>' ;
    Best regards
    Wolfgang

  • SQL Server 2005 - CDC problem - real / float type

    Dear Sirs,
    I test the functionality of CDC in Business Objects Data Services 4.0 (14.0.1.245).
    I am using SQL Server 2005 Developer Edition.
    I made all the steps in accordance with the Designer Guide.
    I see a table with the changes, I can change the target system using this information  but I have one problem.
    I have a problem with the real / float type.
    If I make changes in the column real / float (in the table), tha I always see the number -999.000000.
    Does anyone know how to deal with thie bug?
    Best regards,
    Michal

    Sounds very much like a bug to me. I have seen these things in the past with regular tables whenever we had an issue around regional settings. Can you change your computer locale and SQL server language to english to proof it is that and keep it as a workaround for now?

  • SQL server 2005 TSQL problem

    Deal all\,
    Table1
    Table2
    T1Col1
    T1col2
    T2Col1
    T2col2
    1
    asdf
    1
    asdf
    2
    ghgh
    2
    ghgh
    3
    kkjk
    3
    kkjk
    4
    kkjk
    4
    ldflkl
    5
    jhjj
    5
    urws
    Think that i have above 2 tables in SQL server 2005.
    select * from table1 where T1Col1 in ( select T1Col1 from Table2)
    should i except error for the above query ?
    But SQL server 2005 is not giving any error , it is simple resulting all rows  from Table1
    regards
    ranganadh kodali

    You will not receive any type of error because T1Col1 does exist in Table1 and even inside the parens
    you are still within the context of the same query, the reason for this is that SQL Server allows you to use the values of the outer table inside the inner condition, you will find tons of examples of this usage when people use exists, here is one that's perfectly
    valid:
    select *
    from table1
    where exists (select 1 from Table2 where T1Col1 = T2Col1)
    so in your particular query what's happening is that you're selecting a kind of "constant" value in your inner query, similar to doing this:
    select 'constant' as myCol from Table2;
    just that the 'constant' value is really coming from your outer table.
    please mark as answer if it helps! :)

  • Microsoft sql server 2005 setup problem

    i am trying to install sql server 2005 on windows 8,
    they is a popup
    window 
    that
    says;
    the sql server servi failed to start. for more information, see the sql server book
    online topics, "How to: view sql server 2005 setup log
    files" and starting sql server Manually."

    i am trying to install sql server 2005 on windows 8,
    they is a popup window 
    that says;
    the sql server servi failed to start. for more information, see the sql server book online topics, "How to: view sql server 2005 setup log files" and starting sql server Manually."
    I merged your two threads into one, because they are the same. Thanks for asking your questions here!
    sqldevelop.wordpress.com

  • Database sql server 2005 instalation problem.

    Dear sir/mam,
    I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).

    Rajsarawat wrote:
    Dear sir/mam,
    I have installed sql server 2005 (server) and on another computer installed client. It installed successfully but on client side it does not seen, from where should i start it. so please send me procedure to install sql server 2005 on both side(client and server).You have to turn on network (external to your computer) access.
    Under programs->sql server look for "surface"

  • MS SQL Server 2005 connection problem?

    Hi all,
    I am a beginner in these things, so be patient please. I have established database connection with my MS SQL 2005 server with a 3rd party JDBC driver. Testing databasae connection was successfull, but there are no tables from my created database in JDeveloper. Instead of my tables there are some for me unknown tables. Can anybody help me with this problem? just ask for further information.
    Here is port, that I have used to make connection. Actually I don't know, if this port is good. I get this information from my SQL server configuration manager.
    http://b.imagehost.org/0592/Clipboard01.jpg
    -->
    http://b.imagehost.org/0592/Clipboard04.jpg
    This is my simple testing database that was created in MS SQL:
    http://b.imagehost.org/0592/Clipboard03-3.jpg
    as you can see on the picture, my database called "skusobna" includes only one table called "osoba".
    After making connection to MS SQL Server there are only these uknown tables.I don't know from where are these tables inserted, but my database with table "osoba" isn't included.
    http://b.imagehost.org/0592/Clipboard02-2.jpg
    All I want to do is to connect my database to JDeveloper that I can see my tables created in MS SQL.
    Thanks...

    Here is port, that I have used to make connection. Actually I don't know, if this port is good. I get this information from my SQL server configuration manager.
    http://b.imagehost.org/0592/Clipboard01.jpg
    The port is correct.
    -->
    http://b.imagehost.org/0592/Clipboard04.jpg
    The connection url is correct.
    This is my simple testing database that was created in MS SQL:
    http://b.imagehost.org/0592/Clipboard03-3.jpg
    as you can see on the picture, my database called "skusobna" includes only one table called "osoba".
    The database is correct.
    After making connection to MS SQL Server there are only these uknown tables.I don't know from where are these tables inserted, but my database with table "osoba" isn't included.
    http://b.imagehost.org/0592/Clipboard02-2.jpg
    Click on the dbo node for the osoba table.

  • SQL Server 2005 Database connecting problem

    Hi,
    I have installed MDM 5.5 SP06 - 64bit servers,  32bit clients and  SQL server 2005  in Vista 64 bit operating system.
    But I can't able to connect the server...
    I believe sa is reserved user name but in SQL server management studio I couldn't able to connect the server and registered the Server.
    Can you guys please guide me in this regard how to fix this problem ASAP?
    Thanks,
    Pooja

    Hi,
    Thanks for your time and help, but I couldn't able to see the database itself.
    as I know my computer name is database name but SQL Server is not providing that.
    and its showing network data base names.
    If I type the database name and user is sa...but there is no luck in connecting...
    is there any way that we can define server name and user names??? also it doesn't ask for any database name or user name during installation of SQL Server 2005
    I'm not a SQL person so, please help me in this regard.
    Thanks, Pooja

  • Crystal Report 8.5 with SQL SERVER 2005 problems

    Post Author: AREVA
    CA Forum: Data Connectivity and SQL
    Hi All !We have some problems with Crystal Reports version 8.5 with SQL Server 2005: 1) When we want to generate a report (using data in SQL Server 2005) we have a popup message error : "impossible to loaded pdssql.dll".2) If we want to use SQL Server 2005, which Crystal Reports version we must used ? Is there any restrictions with this connectivity with 8.5 version ?Please, let me known, all informations about SQL Server 2005 and Crystal Report 8.5.Thanks for all !Best regards Anthony

    Hello Kamlesh,
    There is no expectation that the ActiveX viewer (RDC?) from CR8.5 will work in any version of Visual Studio .NET. There is also no expectation that the ActiveX viewer from CR8.5 will work on a machine with a 64 bit operating system.
    You're using VS2008. You should migrate to the bundled edition of CR for VS2008 (v10.5), the ReportDocument object, and the .NET Windows form viewer or Web form viewer.
    Sincerely,
    Dan Kelleher

  • Migration From SQL Server 2005 to Oracle DB through Oracle SQ Dev Problem

    Hi all,
    we are trying to do a full Migration from MS SQL Server 2005 to Oracle DB 9.2 i
    we are using Oracle SQL Developer V 1.5.3,
    the capturing of the DB and the conversion to the oracle model completed succefully
    however when we try to generate the scripts from the converted model
    the script generation hangs on a sequence and no further progress is made (the script generation pop up keeps still on a certain sequence displaying its name, and thats it )
    no error messages are displayed,
    how can we know the reason for this? or atleast find a log for whats happening...
    any suggestions?
    Thank you

    Hi,
    migrating a sequence shouldn't make a problem. I did a quick test. I created this table in SQL Server:
    create table test_seq (col1 int identity(1,1),col2 char(1))
    Then I captured the table, converted the table and generated the script. There was no problem.
    CREATE SEQUENCE succeeded.
    CREATE TABLE succeeded.
    Connected
    TRIGGER test_seq_col1_TRG Compiled.
    As you see, applying the script was also successful.
    I am using Oracle RDBMS 11g, I don't know whether this makes a difference. Do you have any 11g instance available to test it?
    Can you show me one of the sequences that are causing the hang? Is the CREATE SEQUENCE statement already in the generated script, or not? Your table is for sure more complex than my simple example.
    Regards,
    Wolfgang
    Edited by: wkobargs on Jan 13, 2009 3:01 AM

  • SQL Server 2005 SP2 install on Vista

    Hi,
    I have all updates for Vista, tried to install SQL Server 2005 SP2, the following log file:
    Microsoft SQL Server 2005 9.00.3042.00
    ==============================
    OS Version      : Professional  (Build 6000)
    Time            : Wed Mar 26 12:20:54 2008
    USER-PC : To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter.
    Machine         : USER-PC
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.3042.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_1.log
    Machine         : USER-PC
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.3042.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_1.log
    Machine         : USER-PC
    Product         : Microsoft SQL Server VSS Writer
    Product Version : 9.00.3042.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SqlWriter_1.log
    Machine         : USER-PC
    Product         : Microsoft SQL Server Setup Support Files (English)
    Product Version : 9.00.3042.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLSupport_2.log
    Machine         : USER-PC
    Product         : Microsoft SQL Server Native Client
    Product Version : 9.00.3042.00
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQLNCLI_2.log
    Machine         : USER-PC
    Product         : Microsoft SQL Server 2005 Express Edition
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_SQL.log
    Machine         : USER-PC
    Product         : Workstation Components, Books Online and Development Tools
    Warning         : Warning 28123.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.
    Machine         : USER-PC
    Product         : Microsoft SQL Server 2005 Tools Express Edition
    Product Version : 9.00.1399.06
    Install         : Successful
    Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0002_USER-PC_Tools.log
     Setup succeeded with the installation, inspect the log file completely for status on all the components.
    Time            : Wed Mar 26 12:23:51 2008
    ==============================================================
    When I try to start SQL Server it times out. SQL Server Express is running ok.
    Can you help me get this started?
    Thank you,
    Lucy

    This is the previous errorlog:
    2008-04-09 11:47:06.27 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
     Mar 23 2007 16:28:52
     Copyright (c) 1988-2005 Microsoft Corporation
     Enterprise Evaluation Edition on Windows NT 6.0 (Build 6000: )
    2008-04-09 11:47:06.27 Server      (c) 2005 Microsoft Corporation.
    2008-04-09 11:47:06.27 Server      All rights reserved.
    2008-04-09 11:47:06.27 Server      Server process ID is 240.
    2008-04-09 11:47:06.27 Server      Authentication mode is WINDOWS-ONLY.
    2008-04-09 11:47:06.27 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
    2008-04-09 11:47:06.27 Server      This instance of SQL Server last reported using a process ID of 4180 at 4/5/2008 11:17:36 AM (local) 4/5/2008 6:17:36 PM (UTC). This is an informational message only; no user action is required.
    2008-04-09 11:47:06.27 Server      Registry startup parameters:
    2008-04-09 11:47:06.27 Server        -d C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
    2008-04-09 11:47:06.27 Server        -e C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
    2008-04-09 11:47:06.27 Server        -l C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
    2008-04-09 11:47:06.32 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2008-04-09 11:47:06.32 Server      Detected 2 CPUs. This is an informational message; no user action is required.
    2008-04-09 11:47:06.50 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
    2008-04-09 11:47:06.55 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
    2008-04-09 11:47:06.64 Server      The Microsoft Distributed Transaction Coordinator (MS DTC) service could not be contacted.  If you would like distributed transaction functionality, please start this service.
    2008-04-09 11:47:06.64 Server      Database mirroring has been enabled on this instance of SQL Server.
    2008-04-09 11:47:06.64 spid4s      Starting up database 'master'.
    2008-04-09 11:47:06.80 spid4s      4 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
    2008-04-09 11:47:06.82 spid4s      0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
    2008-04-09 11:47:06.82 spid4s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2008-04-09 11:47:07.06 spid4s      SQL Trace ID 1 was started by login "sa".
    2008-04-09 11:47:07.10 spid4s      Starting up database 'mssqlsystemresource'.
    2008-04-09 11:47:07.13 spid4s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
    2008-04-09 11:47:07.34 spid4s      Server name is 'USER-PC'. This is an informational message only. No user action is required.
    2008-04-09 11:47:07.34 spid9s      Starting up database 'model'.
    2008-04-09 11:47:07.53 spid9s      Clearing tempdb database.
    2008-04-09 11:47:08.11 Server      A self-generated certificate was successfully loaded for encryption.
    2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv6> 1433].
    2008-04-09 11:47:08.11 Server      Server is listening on [ 'any' <ipv4> 1433].
    2008-04-09 11:47:08.17 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2008-04-09 11:47:08.17 Server      Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ].
    2008-04-09 11:47:08.17 Server      Server is listening on [ ::1 <ipv6> 1434].
    2008-04-09 11:47:09.12 spid9s      Starting up database 'tempdb'.
    2008-04-09 11:47:09.47 spid12s     The Service Broker protocol transport is disabled or not configured.
    2008-04-09 11:47:09.47 spid12s     The Database Mirroring protocol transport is disabled or not configured.
    2008-04-09 11:47:09.53 spid12s     Service Broker manager has started.
    2008-04-09 11:51:06.92 Server      CPU time stamp frequency has changed from 1662000 to 199683 ticks per millisecond. The new frequency will be used.
    2008-04-09 11:55:07.29 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 11:55:07.29 Server      CPU time stamp frequency has changed from 199683 to 136029 ticks per millisecond. The new frequency will be used.
    2008-04-09 12:23:09.84 Server      CPU time stamp frequency has changed from 136029 to 586928 ticks per millisecond. The new frequency will be used.
    2008-04-09 12:59:13.12 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 13:07:13.85 Server      CPU time stamp frequency has changed from 586928 to 824822 ticks per millisecond. The new frequency will be used.
    2008-04-09 13:47:17.50 Server      CPU time stamp frequency has changed from 824822 to 140502 ticks per millisecond. The new frequency will be used.
    2008-04-09 14:07:19.33 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 15:07:24.80 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 15:11:25.16 Server      CPU time stamp frequency has changed from 140502 to 1413355 ticks per millisecond. The new frequency will be used.
    2008-04-09 15:15:25.53 Server      CPU time stamp frequency has changed from 1413355 to 161989 ticks per millisecond. The new frequency will be used.
    2008-04-09 15:19:25.89 Server      CPU time stamp frequency has changed from 161989 to 134822 ticks per millisecond. The new frequency will be used.
    2008-04-09 16:23:31.73 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 17:23:37.20 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 18:11:41.58 Server      CPU time stamp frequency has changed from 134822 to 154257 ticks per millisecond. The new frequency will be used.
    2008-04-09 18:23:42.67 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 18:23:42.67 Server      CPU time stamp frequency has changed from 154257 to 134721 ticks per millisecond. The new frequency will be used.
    2008-04-09 18:35:43.79 Server      CPU time stamp frequency has changed from 134721 to 151448 ticks per millisecond. The new frequency will be used.
    2008-04-09 18:43:44.51 Server      CPU time stamp frequency has changed from 151448 to 125134 ticks per millisecond. The new frequency will be used.
    2008-04-09 19:15:47.35 Server      CPU time stamp frequency has changed from 125134 to 182297 ticks per millisecond. The new frequency will be used.
    2008-04-09 19:23:48.08 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 19:27:48.45 Server      CPU time stamp frequency has changed from 182297 to 120770 ticks per millisecond. The new frequency will be used.
    2008-04-09 19:47:50.27 Server      CPU time stamp frequency has changed from 120770 to 1370171 ticks per millisecond. The new frequency will be used.
    2008-04-09 20:07:52.10 Server      CPU time stamp frequency has changed from 1370171 to 106932 ticks per millisecond. The new frequency will be used.
    2008-04-09 20:23:53.56 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
    2008-04-09 20:35:54.65 Server      CPU time stamp frequency has changed from 106932 to 88924 ticks per millisecond. The new frequency will be used.
    2008-04-09 20:51:56.11 Server      CPU time stamp frequency has changed from 88924 to 102106 ticks per millisecond. The new frequency will be used.
    2008-04-09 20:59:56.84 Server      CPU time stamp frequency has changed from 102106 to 118592 ticks per millisecond. The new frequency will be used.

  • Database Connection Problem-SQL SERVER 2005

    Dear all,
    I have been struggling with this database connection.I have installed sql server 2005 in my PC and i am trying to connect to the Database Adventity.But it is showing port 1432 invalid.I have placed sqljdbc jar in my lib folder.If i dont specify Database name then it will print hi Message..if i specify Database name then the error will come.
    MY CODE is::
    <%@page import="java.sql.*,java.io.*,java.lang.*,java.util.*,java.util.Vector,bean.*" %>
    <%
              Connection con;
              Statement stmt;
              String url= "jdbc:sqlserver://156.0.11.140:1433/Adventity";
              Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
              con = DriverManager.getConnection(url,"sa","hcl@123");
              stmt = con.createStatement();     
              out.println("hi");
    %>
    THE ERROR IS:
    javax.servlet.ServletException: The port number 1433/Adventity is not valid.
         org.apache.jasper.runtime.PageContextImpl.doHandlePageException(PageContextImpl.java:867)
         org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:800)
         org.apache.jsp.adv1_jsp._jspService(adv1_jsp.java:66)
         org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:133)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:311)
         org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:301)
         org.apache.jasper.servlet.JspServlet.service(JspServlet.java:248)
         javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
    root cause
    PLEASE HELP ME TO GET RID OUT FROM THIS PROBLEM.
    THANKS IN ADVANCE.

    hi
    i have given what u said and it is not working but it displays blank page.even i tried to getdate..
    pls help me
    <%@page import="java.sql.*,java.io.*,java.lang.*,java.util.*,java.util.Vector,bean.*" %>
    <%
              Connection con;
              Statement stmt;
              try
              String url= "jdbc:sqlserver://156.0.11.140:1433;databaseName=test";
              Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
              con = DriverManager.getConnection(url,"sa","hcl@123");
              stmt = con.createStatement();
              String user="select getdate();"
              System.out.println(user);
         catch (Exception e) {
                   out.println(e.toString());
              } finally {
                   try {
                   } catch (Exception e) {
                        e.printStackTrace()     ;
    %>

  • SQL Server 2005 Update mechanism problem

    Hi Gurus,
          We're faced with one SQL Server 2005 update mechanism problem. Here is my problem:
          According to our requirement, an add_on interface program is designed to execute creation of production order by calling Bapi.
          There are 3 steps in this add_on program:
          Step 1: Create production order
          Step 2: Change the information of production.
          Step 3: Some other
          After the step 1 has finished immediately step 2 is called, Howerver the information which should have inserted into database table couldn't be found from database. (Maybe because the time between two steps is too short to finish inserting)
          In order to ensure the complete of the transaction, before the step 2 executed, the information in step 1 should have inserted into database.
           Is there any solution to solve this problem?
           I guess whether there is any parameter which control the time of writing buffer into database...
    Any advice is appreciated.
    Thanks & Best Regards,
    Derek Yang

    Hi
    I have the same problem, but that post didnt help me
    This is the error I have:
    My snapshot agent hangs.. waiting for a response from the server.. and timeouts.
    This only hapens for a publication that has a filter based on HOSTNAME()
    The other publications work fine
    Error messages:
    Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
    Command Text: sp_MSsetup_partition_groups
    Parameters: @publication = XXXXXXX
    Stack: at Microsoft.SqlServer.Replication.AgentCore.ReMapSqlException(SqlException e, SqlCommand command)
    at Microsoft.SqlServer.Replication.AgentCore.AgentExecuteNonQuery(SqlCommand command, Int32 queryTimeout)
    at Microsoft.SqlServer.Replication.AgentCore.ExecuteDiscardResults(CommandSetupDelegate commandSetupDelegate, Int32 queryTimeout)
    at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.SetupPartitionGroups()
    at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.DoRegularMergeSnapshotPreparations()
    at Microsoft.SqlServer.Replication.Snapshot.MergeSnapshotProvider.DoPreArticleFilesGenerationProcessing()
    at Microsoft.SqlServer.Replication.Snapshot.SqlServerSnapshotProvider.GenerateSnapshot()
    at Microsoft.SqlServer.Replication.SnapshotGenerationAgent.InternalRun()
    at Microsoft.SqlServer.Replication.AgentCore.Run() (Source: MSSQLServer, Error number: -2)
    Get help: http://help/-2
    Server XXXXXXXXX, Level 11, State 0, Procedure , Line 0
    Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (Source: MSSQLServer, Error number: -2)
    Get help: http://help/-2

  • Problem using production version of SQL Server 2005 JDBC drivers

    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    Sabrina
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

    SabrinaL wrote:
    A production version of the Microsoft SQL Server 2005 JDBC driver became available on 1/20/06, and we are having some issues getting it to work with WLS 9.1. The non-XA driver works fine, but when we attempt to use the XA version, we see the error below in our logs. (Note that in the text "status:0 msg:null", the "null" is actually an unprintable character that I was not able to copy/paste.)
    We have successfully tested WLS 9.1 with the beta JDBC drivers that were released by Microsoft a number of months ago, so this appears to be a problem with the prod version only (although we had no trouble using the prod drivers with JBoss). We have actually opened a support case for this, but the response we have received thus far has been negligible at best and we really need to get this issue resolved, so I am posting the problem here as well to see if anyone else has encountered it.
    Regards,
    SabrinaHi. Have you done all the XA-related install for the new MS driver? (put the XA
    dll in the DBMS environment etc)? Is your DBMS on a 32-bit machine or 64-bit machine?
    Does the driver present a dll for each of those? You can also get good JDBC help
    from MS via their microsoft.public.sqlserver.jdbcdriver newsgroup.
    Joe Weinstein at BEA
    >
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
    Caused by: ourpackage.OurDBUtil.openConnection(OurDBUtil.java:130)     
         ... 11 more
    Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XA_OK start() failed on resource 'OurXADataSource': XA_OK
    javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: xp_sqljdbc_xa_init failure, status:0 msg:null.
         at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Ljavax.transaction.xa.Xid;I)V(Unknown Source)
         at weblogic.jdbc.jta.DataSource.start(DataSource.java:679)
         at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1160)
         at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1093)
         at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:496)
         at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:428)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1390)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1395)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1314)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)     
         at ourpackage.OurMDB.onMessage(OurMDB.java:184)
         at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:426)
         at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:332)
         at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:288)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:3824)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:3738)
         at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:4228)
         at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
         at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1327)
         at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:436)
         at weblogic.jdbc.jta.DataSource.connect(DataSource.java:392)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
         at ourpackage.OurDBUtil.openConnection(OurDBUtil.java:125)
         ... 12 more

  • MS SQL Server 2005...  Problem while executing stored procedure

    Hi.. all
    I have got a problem with sql server 2005
    When i execute any stored procedure on a remote database using
    ResultSet.TYPE_SCROLL_INSENSITIVE,
    ResultSet.CONCUR_READ_ONLY
    options, it throws SQL Exception with following message
    "A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor."
    Note: Every thing works fine, if I execute the same sp from the PC where sql server is installed, it throws this exception only when i execute sp from a computer different thn one where SQL server is installed.
    Here is d code.
    CallableStatement call = conn.prepareCall( "{call getAttributeLabelValues(?,?,?)}",
    ResultSet.TYPE_SCROLL_INSENSITIVE,
    ResultSet.CONCUR_READ_ONLY
    // set parameters.
    ResultSet rs = call.executeQuery( ) ;
    If I remove options
    ResultSet.TYPE_SCROLL_INSENSITIVE,
    ResultSet.CONCUR_READ_ONLY
    while executin SP, thn every thing works fine.
    here is d exception
    com.microsoft.sqlserver.jdbc.SQLServerException: A server cursor cannot be opened on the given statement or statements. Use a default result set or client cursor.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
    at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.sendExecute(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteQuery(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(Unknown Source)
    I will appreciate any help.
    Sudhir
    http://www.jyog.com

    use sql server jdbc driver v1.2..........

Maybe you are looking for