MX7 SQL SERVER Datasource problem

hello
I installed MX7 and I do not manage to create a datasource
which
point towards my dB MSSQL SERVER on local, it posts me this:
Connection verification failed for data source: blanko
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver]Error
establishing socket. Unknown host: (local)
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer
JDBC Driver]Error establishing socket. Unknown host: (local)
under Coldfiusion server 5.5 there was the possibility of
checked “Trusted connnection” and it had no prob with
MSQLSERVER there Apparently it is necessary to work with the JDBc
drivers but I do not have any idea of how to install it I am sure
that it is a traditional error, if somebody has already encountered
the problem,
thank you to light me
thks Sam
Configuration: Windows 2003 Internet Explorer 7.0

I found why it did not recognize localhost, because I placed
(localhost) between bracket because on CF 5.5 it was the case for
(local), therefore now it recognizes apparently the localhost as
server but it is another problem now: it did not recognize the
username and password,
however I configured SQL SERVER 2005 in mixed mode and thus
I test with login: Administrator and password empty (because I
don't have password on Windows authentication) and I also test with
username: sa and my password admin but without success, here what
it indicates as error:
Connection verification failed for data source: blanko
java.sql.SQLException: [Macromedia][SQLServer JDBC
Driver]Error establishing socket. Connection refused: connect
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver]Error establishing socket.
Connection refused: connect
in addition I do not know if there is a bond, (I work under
win 2003 standard edition) and according to what I read on the Net,
it may be that it is a problem of port, can be the port 1433 is not
open? If I make on DOS prompt: telnet localhost 1433 ==> failure
to connect whereas telnet localhost 80 works
I even tried to connect with
username: sa
pwd: mypwd
port: 80 (I know that 80 is the port for HTTP)
it posts the following message:
Connection verification failed for data source: blanko
java.sql.SQLException: [Macromedia][SQLServer JDBC Driver]No
more data available to read.
The root cause was that: java.sql.SQLException:
[Macromedia][SQLServer JDBC Driver]No more data available to read
thanks for your help

Similar Messages

  • Please help: problem configuring a SQL server datasource in Websphere.

    I am using Rational Developer 6 and its integrated testing server (websphere v6). When configuring a data source for SQL server, I did the following steps in admin console of the test server:
    1. Created a JDBC provider, using WebSphere embedded ConnectJDBC driver for MS SQL Server;
    2. Created a datasource under the previously created JDBC provider, filled in the server name, DB name and port number (1433 for SQL server);
    3. Created a J2C authentication alias that has the login info of SQL server;
    4. Assigned the created J2C alias to both component and container managed authentication alias;
    However, when I click "Test Connection", it always gets back to me with an error "java.lang.Exception: java.sql.SQLException: [IBM][SQLServer JDBC Driver]Error establishing socket. Connection refused: connectDSRA0010E: SQL State = 08001, Error Code = 0.".
    My ultimate goal is to configure a SQL server datasource so that I can configure Kodo to use this datasource.
    Can some one please help? Thanks in advance.

    Try this:
    http://www-1.ibm.com/support/docview.wss?uid=swg21210871
    I am yet to test this. I am going to download latest SP for SQL Server 2000 and install it. I hope it will do the magic.

  • SQL Server Datasource

    Hello,
    I'm trying to create a SQL server datasource in Visual Administrator, when I get this error while testing an sql statement.....
    [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]xa_open (0) returns -3
    My DTC service is started and I'm not sure what else could be the problem. Could anyone help me resolve this issue?

    Hello Sudhakar,
    This is database specific error and it has nothing to do with the NetWeaver Server. Try to look for help in the MSSQL forums. I attach an article about this problem that I found:
    http://knowledgebase.datadirect.com/kbase.nsf/ce24d9443437511f85256e57006bfe2a/f9b6b90e5d3a802285256f2000543b96?OpenDocument&Highlight=0,xa_open,(0),returns,-3
    I hope it can help a bit.
    Best Regards
    Vyara

  • RE: Database (SQL-SERVER) access problem

    Have you used NT Control Panel/ ODBC to set up the ODBC data source name?
    You have to define the data source (database) SecTrade as well as the
    driver to be used (SQL Server). This can be done by selecting the Add
    button on the Data Sources screen in Control Panel/ ODBC.
    Hope this helps.
    Sanjay Murthi
    Indus Consultancy Services, Inc.
    From: Administrator
    Sent: Wednesday, August 13, 1997 6:49 PM
    To: "'[email protected]'"
    Cc: murthis; thyagarajm; thyagarm; vasasm; chandraa
    Subject: Database (SQL-SERVER) access problems
    MCI Mail date/time: Mon Aug 11, 1997 10:28 pm EST
    Source date/time: Mon, 11 Aug 1997 19:25:34 +0530
    Hi Forte-Users,
    We have a setup a Sql-Server database on a NT server. In the Forte
    EConsole,
    we have
    setup a ODBC-type Resource for this server, named SERVER2_ODBC. This NT
    server
    is configured as a Client Node in the active Forte environment. Note
    that
    Server2 is not
    the Forte server, but has Forte installed. There is another NT server
    which
    acts as the
    Forte server. NODEMGR and Sql-Server are running on SERVER2.
    In our application, we have a DBSession SO with the database source
    as SERVER2_ODBC, Userid=ForteInstructor. When running the application,
    Forte
    throws an exception, the gist of it being as follows:
    USER ERROR: (This error was converted)
    Failed to connect to database: SecTrade, username: ForteInstructor.
    [Microsoft][ODBC Driver Manager] Data source name not found and no
    default
    driver specified
    We have tried
    1) Installing ODBC drivers on the NT server (Server2)
    2) Accessing local databases from Forte clients which works fine
    3) Accessing the Sql-Server database through Isqlw (Sql-Server Client
    s/w) -
    It works.
    Could someone suggest what we should try to get rid of this problem?
    Thanks for any help,
    Kishore Puvvada

    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"

  • Setting up Microsoft SQL Server datasource in Websphere 4.0

    Does anyone know how to setup an SQL Server jdbc driver in Websphere 4.0? I am using jdbc driver from jTurbo. But I am having trouble specifying the proper URL and other datasource settings in Websphere 4.0 (or WTE) server configuration.

    Hi,
    Please find the extract from jTurbo site (http://www.newatlanta.com/support/jturbo/third-party.jsp#WebSphere)
    which will explain the steps to follow for setting up Microsoft SQL Server datasource
    in Websphere 4.0 using jTurbo jdbc driver.
    1.Always make sure the JTurbo.jar is set in your classpath.
    2.Started "WebSphere Admin Server"
    3.Open "WebSphere Administrative Console"
    4.Install the JTurbo Driver into WAS by modifying the following field of "Admin DB Driver"
    Name: JTurbo
    Class Name: com.ashna.jturbo.driver.Driver
    URL prefix: jdbc:JTurbo://localhost/pubs
    JTA Enabled: false
    (apply changes which resulted in the installation of JTurbo Driver)
    5.Selected "Create Data Source" in Console "Wizards" drop down
    6.Selected "Use an already installed JDBC Driver" JDBC Option
    7.Specified "my ds name" as the "Data Source Name"
    Specified "pubs" as the "Database Name" pull down is showing "JTurbo"
    This should sucessfully create a new data source by the name of "my ds name".
    Also there is an excellent document on "Configuring the Merant ConnectJDBC data source for MS SQL Server for the WebSphere Application Server Advanced Single Server Edition" at http://www-4.ibm.com/software/webservers/appserv/doc/v40/ae/infocenter/was/was402/rn112253.4.html .
    Hope this helps. Good luck.
    Best Regards
    Gayam_Slash

  • 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

  • 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

  • Unable to connect Informatica on Sun Solaris to a SQL Server datasource

    Background*
    We have a fully operational OBIEE with OBIA Apps infrastructure running with Informatica PC8.6 ETL suite. Informatica services are running on a Sun Solaris 64 bit platform.
    We currently extract data from two Oracle EBS 11.5.10 sources. Now we are trying to extract data from a new MS SQL Server 2000 source into the OBAW.
    Problem*
    I'm trying the use the native ODBC 5.2 Data Direct driver to connect the the data source.
    I've gone through and completed the 9 steps of the 'Connecting to an ODBC Data Source' chapter in Informatica on our Solaris Unix box.
    I've made the following changes to the *.profile*
    # ODBC HOME
    ODBC_HOME=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2
    export ODBC_HOME
    ODBC_INI=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2/odbc.ini
    export ODBC_INI
    PATH=${PATH}:$ODBC_HOME/bin
    export PATH
    LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$ODBCHOME/lib
    export LD_LIBRARY_PATH
    I've also made changes to the odbc.ini file as suggested:
    [MSS_DB]
    Driver=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2/lib/DWmsss22.so
    Description=DataDirect 5.2 SQL Server Wire Protocol
    Address=MssServer.xxx.co.uk,1433
    AlternateServers=
    AnsiNPW=Yes
    ConnectionRetryCount=0
    ConnectionRetryDelay=3
    Database=MIS_Report_DB
    LoadBalancing=0
    LogonID=myuser
    Password=mypwd
    QuotedId=No
    ReportCodePageConversionErrors=0
    InstallDir=/oracle/Informatica/PowerCenter8.6.0/ODBC5.2
    I've created the Connection--> Relational --> ODBC connection on Workflow Manager
    I've specified the username/pwd and connect string MssServer.xxx.co.uk@MIS_Report_DB. I've called it exactly the same as MSS_DB specified in the odbc.ini
    When I run the workflow. It fails but doesn't throw up any error/error code in the session log. The last 3 lines of the Session Log below and then it just bombs out within 5 secs.
    PETL_24006 : Starting data movement.
    TM_6660 : Total Buffer Pool size is 4234808 bytes and Block size is 468312 bytes.
    DBG_21438 : Reader: Source is [MssServer.xxx.co.uk], user [myuser]
    If you ping from the Unix server it says 'MssServer.xxx.co.uk is alive'
    Can anyone suggest what we need to do different or spot something obvious?
    Edited by: bebedi123 on 13-Apr-2010 09:43

    user00726 wrote:
    i am able to create files in /tmp
    $ pwd
    /tmp
    $ touch test
    $ ls -l
    total 64
    drwxr-xr-x   2 root     other        194 May 27 14:20 OraInstall2009-05-27_02-20
    -02PM
    drwxr-xr-x   2 root     other        194 May 27 14:35 OraInstall2009-05-27_02-35
    -06PM
    drwxr-xr-x   6 root     other        445 May 27 14:38 OraInstall2009-05-27_02-38
    -48PM
    -rw-rw-r--   1 root     sys         6644 May 27 14:00 ps_data
    -rw-r--r--   1 oracle   dba            0 May 27 16:04 test
    $and i have also removed /tmp_dir_n8ai9b files
    but still there is a problemYou have root as owner of subdirectories (e.g. OraInstall2009-05-27_02-38-48PM) and not oracle:
    - do you install as root now?
    - or make the directories writable for oracle, too.The write flag is missing (something like chmod -R a+w OraInstall2009-05-27_02-38-48PM)
    Edited by: TanteKaethe on May 28, 2009 9:54 AM

  • SQL Server excuteBatch() problem....

    Hi All,
    I am trying to Bulk insert using addBatch() and excuteBatch()
    which works fine.
    The problem I am facing is, when I am inserting 50 queries in excuteBatch(), even
    one of them fails, ( due to some foriegn key violation ) whole process stops.
    Can we able to ignore all the failed ones, and proceed till the end in excuteBatch()?
    I am using MS JDBC Driver for SQL Server and WL server 6.1 sp3.
    any help will be really helpful..
    thanks,
    Arun

    Arun wrote:
    Hi All,
    I am trying to Bulk insert using addBatch() and excuteBatch()
    which works fine.
    The problem I am facing is, when I am inserting 50 queries in excuteBatch(), even
    one of them fails, ( due to some foriegn key violation ) whole process stops.
    Can we able to ignore all the failed ones, and proceed till the end in excuteBatch()?
    I am using MS JDBC Driver for SQL Server and WL server 6.1 sp3.
    any help will be really helpful..
    thanks,
    ArunHi. Duplicate the problem in a standalone program, without weblogic code.
    It sounds like a driver bug, and you should post this to the ms jdbc newsgroup.
    Joe Weinstein

  • SQL Server driver problem

    I am trying to connect to SQL Server 2000. I have JDK1.3.1_02. When I compile my applet I get the error that class sqlserver from the statement "Class.forName(com.microsoft.jdbc.sqlserver.SQLServerDriver);" not found. I have included the path in my classpath as "d:\JDBC\lib\msbase.jar;d:\JDBC\lib\msutil.jar;d:\JDBC\lib\mssqlserver.jar" where JDBC is the root directory for the driver.
    Even the statement "import com.microsoft.*;" returns an error that package com.microsoft.* does not exist. What can be the problem?
    Any suggestions/help appreciated!

    You should be getting a different compiler error. Class.forName() requires a String argument, so your code should look like this:Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");Note the quotes around the class name. Also, your "import" statement is irrelevant in any case because that class is not in the com.microsoft package, it is in the com.microsoft.jdbc.sqlserver package.

  • SQL Server/JDBC Problems...

    I know this topic has been posted before, and believe me I've read all of it and followed instructions at least 5 times over. But I just can't get rid of :
    Got an exception!
    [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
    On my SQL server side:
    1) My Client Network Utility and Server Network Utility both have TCP enabled and default port set to 1433
    2) I've set authentication to "SQL Server and Windows" instead of just "windows".
    3) For now I'm using my 'sa' account as startup which is set to "SQL Server and Windows" authentication.
    4) I've disabled and then enabled TCP a bunch of times, that doesn't seem to help.
    5) My SQL Server log says:
    2005-02-22 10:12:12.86 server SQL server listening on Shared Memory, Named Pipes.
    It should say something about TCP according to the MS SQL help, but I've had no luck with that.
    I've even tried NMAP on my computer to check for open TCP ports, and 1433 doesn't show up. My guess is the problem is with SQL Server 2000 (I'm using Java 1.5.0_01 for now). Is there some kind of trick (ritual? animal sacrifice?) needed to get SQL Server to start listening on TCP? God knows I''ve tried everything short of kicking the **** out of my purchased boxed set. Please...any help in the matter would be GREATLY appreciated. Thanks

    I had the same problem on my windows XP laptop.
    For windows XP you need SQL Server 2000 service pack 3.
    Of course you may not be using windows XP but the service pack will not hurt.

  • SQL Server Database Problems

    I have been using SQL Server for sometime with my company's product with no
    unusual problems for some time.
    However, having recently installed a Forte repository on a newly setup NT
    machine (Workstation 4, SP4), I have come across problems.
    The code constructs a cusor which requests columns from a table. Some of those
    columns are of int type but when they are retrieved, the values are completely
    different to those that can be seen when writing SQL statements directly from
    ISQL.
    For example, 1 becomes a seven figure number.
    The following code is being used to iterate through the result set and create
    another string which is made from the values concatenated together :
    for CurRow in 1 to outputDataSet.ActualRows do
    outputDataSet.CurrentRow = CurRow;
    for curCol in 1 to outputDataSet.ColumnList.Items do
    outputDataSet.GetValue(curCol,Value);
    if(not Value.IsNull) then
    // If datetime datatype, need some conversion
    if (outputDataset.columnList[curCol].DataType =
    DV_DT_DATETIME ) or (outputDataset.columnList[curCol].DataType =
    DV_DT_DATETIME_NULLABLE ) then
    begin
    tempDateTime.SetValue( Value.TextValue );
    -- The user has entered an invalid Date format.
    exception
    when e : UsageException do
    tempDateTime.DecodeValue(source=Value.TextValue,
    format=dateForm);
    end;
    pResultData.Concat(dateForm.FormatDate(tempDateTime));
    else
    pResultData.Concat(Value.TextValue);
    end if;
    end if;
    if(curCol <> outputDataSet.ColumnList.Items ) then
    -- pResultData.Concat('\t');
    pResultData.Concat(pDelimChar);
    else
    pResultData.Concat( source = '\r\n' );
    end if;
    end for;
    end for;
    This has not occurred on any other installation and the only ideas that I have
    are that :
    i) the ODBC driver is either the incorrect version or has been setup incorrectly
    in some way
    ii) there are problems with the configuration of SQL Server or NT that is
    causing this problem
    Does anyone have any ideas ?
    Thanks,
    Alex

    My recomendation is to debug the web page. Set a breakpoint by clicking on the row say probably at the page load/form load event. Press F5 to start the debug. Click F10 to step over next row multiple times until and unless you get the error message. i.e
    Invalid column name 'UserId'.
    The piece of code which you have posted does not contain any assignment or usage of column name "UserId", therefore post the portion of the code where the error is actually taking place.
    Regards, RSingh

  • SQL Server 2000 problem with MII Version 12.1.8 Build(24) Reconnecting

    Hi,
    I have a problem using XMII Version 12.1.8 Build(24) with com.microsoft.sqlserver.jdbc.SQLServerDriver JDBC driver with SQL 2000.
    The problem we have is the machine where the SQL server is installed on reboot as per schedule once a week. When the server comes back online, XMII  seems to get problem to reconnect correctly. Sometimes it reconnects perfectly, sometimes not.
    When it fails, the only way to fix the problem is to uncheck the 'Enabled' checkbox, then save the data server, then check the 'Enabled' checkbox, then save again.
    When the reconnect issue happens, uploading messages to SAP fail 100% of time, but downloading Control Recipes  from SAP works 50% of time. For example, some PO's can be processed correctly, some others not, causing data losses due to poor data buffering(buffering doesn't cover connection time out). The failed PO's are marked as 'Sent' into CO53 SAP transaction but in fact, are lost in a hole causing data losses.
    See the error we get atfer the server reboot:
    Unable to get a connection from the pool
    [EXCEPTION]
    com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
    Cannot create a connection to the database
    [EXCEPTION]
    com.sap.xmii.Illuminator.system.CommunicationException: Cannot create a connection to the database... [see details]
    Error processing transaction com.sap.xmii.bls.engine.TransactionInstance@cee764f
    [EXCEPTION]
    com.sap.xmii.scheduler.CronException: PMU ERR VAN - Cannot Qry MSIDs.... [see details]
    Unable to get a connection from the pool
    [EXCEPTION]
    com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "Connection refused. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
    Unable to get a connection from the pool
    [EXCEPTION]
    com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host VANASR70, port 1433 has failed. Error: "connect timed out. Verify the connection properties, check that an instance of SQL Server is running on the host and accepting... [see details]
    The only way we have thought to workaround this problem is to develop our own buffering method into XMII workbench puting all data received from SAP or SQL insert query into an Oracle temp database. We should probably be able to fix this by this way, but it reprensents many costs and efforts, so we try to avoid this for sure.
    Please, if you can provide us a patches or hints about how to fix this, it could be very appreciated because loosing data is very anoying.
    Thanks a lot!
    Edited by: mrmans on May 19, 2011 5:48 PM
    Edited by: Michael Appleby on May 19, 2011 6:10 PM

    The validation query is in place and the system works very well 99% of the time.
    When the SQL server machine reboot each sunday morning, during the time the machine is rebooting, the data server lose the connection which is normal, but when the machine comes back alive(less then 10 minutes), the data server seems to stay in an 'in-between' state showing the connection status 'Running' but showing also error messages posted in the orginial post in Netweaver logs. So at first look the data server is up and running and reconnected to SQL server after the reboot, but in fact, following these errors after the SQL server machine has rebooted, some data are processed correctly from SAP (Control Recipes) and some not.
    The problems looks like very similar to threadID 1596329.
    Here is the data server configuration for all our 5 data servers:
    Connector IDBC
    ConnectorID  
    ConnectorType SQL
    DatePrefix '
    DateSuffix '
    DaysRetention 7
    Description VANASR70 INTERFACE with MS-SQL JDBC 3.0
    Enabled T
    InitCommand  
    InternalDateFormat yyyy-MM-dd HH:mm:ss
    JDBCDriver com.microsoft.sqlserver.jdbc.SQLServerDriver
    MaxRetryCount 50
    Name PROF_INT_VAN
    PoolMax 150
    PoolSize 100
    RetryInterval 60000
    ServerPackage com.sap.xmii.Illuminator.connectors.IDBC
    ServerURL jdbc:sqlserver://VANASR70:1433;databaseName=INTERFACE
    Timeout 30
    UseCount 256
    UserName mii_user
    ValidationQuery SELECT GETDATE()
    WaitTime 60

  • SQL server 2005 problem with service starting

    I am having a problem starting my sqlserver service. It will not start and therefore i have no access to my sql 2005 server database. This is what in the event log. This database was working fine until i had two drives kill over in a RAID configuration.
    The striping went out with a hitch and no i want to see if anyone have any ideas before i perform a restore. Do i need to run SQL server repair with the installation disk?

    Well from viewing the log it looks like i am in a pickle. Since the SQL service won't start, is there a command or script to run for a database check using powershell? Since it looks like i will be doing a restore, just curious now.
    2014-01-16 15:27:58.30 spid5s      Starting up database 'master'.
    2014-01-16 15:27:59.81 spid5s      Error: 824, Severity: 24, State: 2.
    2014-01-16 15:27:59.81 spid5s      SQL Server detected a logical consistency-based I/O error: incorrect pageid (expected 1:363; actual 0:0). It occurred during a read of page (1:363) in database ID 1 at offset 0x000000002d6000 in file
    'W:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf'.  Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately.
    Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
    2014-01-16 15:27:59.81 spid6s      Error: 922, Severity: 14, State: 1.
    2014-01-16 15:27:59.81 spid6s      Database 'master' is being recovered. Waiting until recovery is finished.
    2014-01-16 15:27:59.81 spid6s      System Task System Task produced an error that was not handled.  Major: 9, Minor: 22, Severity:14, State:1
    2014-01-16 15:27:59.81 spid5s      Error: 3313, Severity: 21, State: 2.
    2014-01-16 15:27:59.81 spid5s      During redoing of a logged operation in database 'master', an error occurred at log record ID (2369:160:2). Typically, the specific failure is previously logged as an error in the Windows Event Log
    service. Restore the database from a full backup, or repair the database.
    2014-01-16 15:27:59.81 spid5s      Cannot recover the master database. SQL Server is unable to run. Restore master from a full backup, repair it, or rebuild it. For more information about how to rebuild the master database, see SQL
    Server Books Online.

  • MS SQL Server 2000 Problem to Connect

    Hi There
    I have a problem with MS SQL Server 2000 with Service Pack 3 and JDBC from Microsoft
    My tools are:
    - Windows 2003 Server Standart Edition
    - MS SQLServer 2000 with ServicePack 3
    - JDBC from Microsoft with ServicePack 3
    I want to connect in the database using JDBC.
    At first time, I follow the example to chance the authentication of SQL
    Server
    http://www.banmanpro.com/support/sql2k.asp
    Now, when I will try out to connect in the SQL Server, I receive this error
    message
    java.sql.SQLException: [Micro$oft][SQLServer 2000 Driver for
    JDBC][SQLServer]Login failed for user 'Administrador'.
    I'm trying to connect in SQL Server using my Windows Account, in other
    words, I'm using the ADMIN account of Windows and which was registered in
    the SQL Server.
    In then DriverManager.getConnection line from Java, the Username and
    Password is same the operation system, but I receive the error below.
    Maybe Can you help me please?

    You can't log in using Windows credentials using the MS driver (yes, I know that sounds kind of funny). Use jTDS for that, if you really need it (or if you encounter any other problems with the MS driver). Otherwise log in using SQL Server credentials (try with user sa and blank password if not sure).
    Alin.

Maybe you are looking for