SqlServer Connection String For JDBC When Using Named Pipe
Apr 27, 2008
Hi!
I'm writing a java application that queries sqlserver 2005 (and 2000). In case the sql browser service is stopped I need to use the named pipe property or the port property, right?
But how could the program know at runtime what is the port and what is the pipe name? And how should a connection string to sqlserver 2005 (and 2000) that includes named pipe, look like?
Does anybody have a working Java code sample that connects to an SQLServer 2005 database on a remote host, via the default named pipe, from a client using the SQLServer 2005 JDBC driver? Could you post it, or a pointer to it?
I've gotten java.sql DriverManager.getConnection() to work fine with TCP/IP connections before. But I'm a newbie with named pipes, and unclear on how the connection string/properties are different. I've tried to piece it together from multiple docs and threads, but haven't found sample code that quite fits my situation. I think a simple working example would best clarify the syntax.
The server is not using SQL Express. Most SQLServer configuration options are defaults; the named pipes protocol is enabled.
I'm currently having an issue with a linked server. Here's the surrounding information:
A) I have a clustered SQL Server 2005 Instance (A) and a SQL Server 2000 instance (B). B) There is a linked server on A to B. When I set it up, I did run the fix to ensure A could talk to B (There was an issue with communication between 2005 and 2000 servers). It has been there since I installed A, and has worked fine.. Until last week. C) This linked server uses static credentials to connect to B. D) Named Pipes are enabled on both servers to listen to both connections on both A and B in cliconfg. So A has a named pipe listening for B, and B has a named pipe listening for A. E) A has a view that looks at a table on B - It's a table view, very simple, just pulls in all the data from the table on B.
So, I go to do a select statement from the view, connected as a user other then 'sa'. I then get the error:
Named Pipes Provider: Could not open a connection to SQL Server Linked Server Error Source: ncli Client (Paraphrasing, didn't copy that down, but it was the ODBC connector)
Well, that's odd. It's been working fine for months now..
I then go and connect as sa on A to query B. It works! Mind you, absolutely NO QUERY from A to B will run again until I run SOME kind of query has been run as sa on A.
Mind you, this is not a credential issue. Every user who connects to the linked server to B uses a stored credential that is DBO to the database on B. The same User Name and Password exists on both A and B.
Also of note, I check the activity monitor. There's a process that is "dormant" every time I run a query against the view. The details of this connection are:
sp_reset_connection;1
My question is, why is it resetting the connection on B when being queried from A? Why is it "all of a sudden" a problem? Are there any changes that coudl ahve been made that would cause this?
Any help with this confusing issue would be appreciated.
I am using sqljdbc41.jar to connect with MSSQL database, it is working fine on my local machine.Where as on the remote server, same class giving me error
Login failed for user '<domain><windows loginID>' My connection string is URL...
I am using sqljdbc41.jar and on 64 bit processor , I am using following command which included path for sqljdbc_auth.dll java -Djava.library.path= C: sqljdbc_4.1enuauthx64 TestDao and error is Login failed for user '<domain><windows loginID>' why it is not picking up username passed in connection string. I have 2 machines, one is local and other is remote. on both machine I login using my domain, it is working absolutely fine on local then why the error is coming on remote machine.Both the machines are identical.
try { // Establish the connection. Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver"); con = DriverManager.getConnection(connectionUrl,"ifc2","password");
com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(DriverManager.java:512) at java.sql.DriverManager.getConnection(DriverManager.java:171) at connectURL.main(connectURL.java:43)
I am using the code example that came from Microsoft for making a JDBC connection. I looked at my configuration of SQL Server and change to use a static port 1433. I shut off Windows firewall to make sure it was not blocking communication.
When I try to telnet to port 1433 it says
Connecting To 1433...Could not open connection to the host, on port 23: Connect failed
Linked server is created as (from SQL 2005 to SQL 2000)
EXEC sp_addlinkedserver @server = @SPKServerName,
@srvproduct = '',
@provider = 'SQLOLEDB',
@datasrc = @SPKdatasrc //np:remoteservername
exec sp_serveroption @server = @SPKServerName
, @optname = 'rpc'
, @optvalue = 'on'
exec sp_serveroption @server = @SPKServerName
, @optname = 'rpc out'
, @optvalue = 'on'
exec sp_serveroption @server = @SPKServerName
, @optname = 'data access'
, @optvalue = 'on'
when asp.net applicaiton hits the Stored Procedure, it uses Linked server to get data from remote server. It fails with exception message
OLE DB provider "SQLNCLI" for linked server "ServerName" returned message "Login timeout expired". OLE DB provider "SQLNCLI" for linked server "ServerName" returned message "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". Msg 5, Level 16, State 1, Line 0 Named Pipes Provider: Could not open a connection to SQL Server [5].
Hi All , I have been racking my head on this for the last two days and really it should be a no brainier. Anyways I can only assume that I€™m missing something here but...
In a nut shell I am attempting to connect to a new SQL Alias that i have created by simply adding the following in the client network utility
Current SQL server name DASQL
Default instance
Alias Name: TASQL
Server Name: DASQL
Pipe Name: \DASQLpipesqlquery
I can connect the new alias via the local (server consol) yet when i attempt to connect remotely it times out as if it can't find the server.
I installed sql server 2005 express on a server with window server 2003 SP1 and tried to connect it from a remote computer with vista installed.
I have already enabled named pipe and tcp/ip protocol for instance SQLEXPRESS on the server, and started sql server browser as well. Of course, I also enabled local and remote connection using tcp/ip and named pipe by sql server surface area configuration tool.
In this senario, I can connect to server locally or remotely by tcp/ip and connect to server locally by named pipe(c>sqlcmd -S \192.168.1.100pipeMSSQL$SQLEXPRESSsqlquery -U * -P *), but I can not connect to server remotely using same command line.
According to some article from MSDN, it might be caused by firewall, but I already disabled my firewall. Moreover, I used tools like makepipe.exe and readpipe.exe, they didn't work too. Why the 2 computers can't create connection using named pipe protocol.
Why can I no longer backup a database to a named pipe in SQL Server 2005? Named pipes are much easier to work with than VDI (and VDI is covered in obscurities). I really want the ability to dump a database to a named pipe reimplementation if it€™s been removed. I hate to think of the cost of redesigning our backup applications. Can I force a PIPE dump device into the sysdevices table? Any suggestions? (and DO NOT tell me to use VDI, as it is absurdly cumbersome and loaded with unnecessary dependencies)
I have read similar posts to this, but I am still having problems.
I am trying to use connection pooling to connect to a local SQL Server 2005 database. I am running my application using MyEclipse Enterprise Workbench. I have verified that sqljdbc.jar resides in "WebRoot/WEB-INF/lib/"
I am working on a C# stored procedure for SQL 2005, and i've uncovered a couple questions.
First a description of the procedure:
I have a series of equations taking place to calculate a score based on activities in which the user participated in, that will give them an over all grade or rating. The calculations currently take place in the database, and I am moving this from T-SQL to C# CRL.
1. In order to connect the stored procedure to the database I use a SqlConnection and a SqlCommand to execute either dynamic sql or a stored procedure to return data to a data reader. Is there an easier way to connect to the database? In SSMS if i open up the query it knows what database i am connected to. Do I have to make a sql connection in C# stored Procedures?
2. I have multiple functions within the main C# Stored Procedure that I'm working on. This ends up requiring Multiple Active Recordsets. I must set this withing the connection string. Seeing as I'm using a named instance of SQL 2005, I now must put the userid, password, and server name into the code. Is there a more secure way to connect to SQL Server in a C# Stored procedure that allows MARS?
3. I encryped the connection string, and put it into the assembly, I wrote a decryption class, and in the procedure itself everytime I need to refrence the connection string, I call it, decrypt it, and pass it along. But my code to decrypt the connection string is in the compiled DLL, if the server was ever compromised the encrypted connection string and the key to decrypt it are sitting in the DLL. Is there a config file that I can use for C# Stored Procedures?
4. If I have to keep the connection string in the file, then I need to change that per environment. Example I have 3 test environments before production. So I would need to change the connection string for each file. That may be fine for one procedure, but what if I have 20, that will quickly get of hand?
5. Along the security lines, can the assembly for a C# Stored Procedure be called from outside the assembly? From a command prompt, or by a maliceous program? Or could it be called directly by a .NET application instead of going through a T-SQL Stored Procedure that is using WITH EXECUTE AS CALLER AS EXTERNAL NAME [PROJECTNAME].[CLASSNAME].[METHODNAME]
I have to supply a sqlserver connection string in the format:
ip address:port, how do i go about finding out what the port number is on the sqlserver server ??? This is for an R25 collegent interface connection, if that helps .
For nearly 6 wks I have been trying to workout with GoDaddy.com a connection string that will connect to the SQL Server 2000 from my ASP.Net web application. In my programming, I have placed the connection string in the web.config file and then call it from there within code behind using the SQLConnection object. My web.config entry has the following form: <appSettings> <add key="Conn" value="server=GoDaddyserver;integrated security=SSPI;database=databaseonGoDaddyserver;" /> </appSettings>I have also written the key supplying the UID and pwd. Nothing works and their support is of no help.Has anyone else had this difficulty either in general or with GoDaddy in particular?
I need to conect my software from a remote client to a server, mystandard connection:Provider=SQLOLEDB.1;Persist Security Info=False;UserID=sa;Password=;Initial Catalog=MyDb;DataSource=192.168.0.100;Network=DBMSSOCN;andProvider=SQLOLEDB.1;Persist Security Info=False;UserID=sa;Password=;Initial Catalog=MyDb;DataSource=192.168.0.100;Network=DBNMPNTW;make a error connection,i have tryed with ODBC connection and its OK only in Named Piped.Can any one help me write the right connection string?thanksrm
I just can't get it to connect to the database. Says something that remote connections are not allowed. I've done the Area thing and allowed all connection including remote connections.
data source=RemoteHostName;initial catalog=myDb;password=sa;user id=sa; Max pool size = 200;
And now strange thing is happening ,, I am receiving error :
Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached
The SqlServer Activity Manager is telling that only 100 connections are pooled, and I guess that the Max pool size is 100, It is not being changed by my Connection string. As I am trying to change the default 100 pool size value to 200.
Huh , So stucked up , how to increase the Max pool size.. Is there any way .
I've got a dilemma here. I'm currently reading records into EasyListBox (ELB) dropdownlist. The criteria in the dropdownlist is based on the select from another ELB dropdownlist. The problem is that the data contains rows with pipes that serve as separters. For example, one of the options that comes back now might be 123 | 456 | 789. I need to be able to make each of them its own row in the dropdownlist. Can anyone advice? Most records don't have any pipes and come throught fine, but some dont. My code below: Dim sAT As String = Replace(elbAttribute.SelectedValue, "'", "''") Dim adapter As New SQLDataAdapter("Select Feature_Type As Attribute_Name, FEATURE_TEXT_VALUE as Attribute_Value, (select distinct FILTER_FAMILY_FEATURE_EXCLUDED.FEATURE_TYPE_ID from FILTER_PROFILES, FILTER_FAMILY_FEATURE_EXCLUDED, FAMILY_ALLOWED_FEATURE_TYPES, SHARED_FEATURE_TYPES, SHARED_FEATURE_VALUES where FILTER_PROFILES.FILTER_PROFILE_NAME = 'MAQ' And FILTER_PROFILES.FILTER_PROFILE_ID = FILTER_FAMILY_FEATURE_EXCLUDED.FILTER_PROFILE_ID And FAMILY_ALLOWED_FEATURE_TYPES.FAMILY_ID = FILTER_FAMILY_FEATURE_EXCLUDED.FAMILY_ID And FILTER_FAMILY_FEATURE_EXCLUDED.FEATURE_TYPE_ID = SHARED_FEATURE_TYPES.FEATURE_TYPE_ID And (SHARED_FEATURE_TYPES.Feature_Type_ID = SHARED_FEATURE_VALUES.Feature_Type_ID And left(FEATURE_TYPE, 4) <> 'CPLV' And Feature_Type = '" & sAT & "')) As ExclusionFlag From SHARED_FEATURE_TYPES, SHARED_FEATURE_VALUES, PRODUCT_FEATURE_VALUES Where PRODUCT_FEATURE_VALUES.FEATURE_VALUE_ID = SHARED_FEATURE_VALUES.Feature_Value_ID And SHARED_FEATURE_TYPES.Feature_Type_ID = SHARED_FEATURE_VALUES.Feature_Type_ID And left(FEATURE_TYPE, 4) <> 'CPLV' And Feature_Type = '" & sAT & "' UNION Select distinct Column_Name As Attribute_Name, SMALL_TEXT_VALUE As Attribute_Value, (select FILTER_ATTRIBUTES_EXCLUDED.EXT_ATT_ID from FILTER_PROFILES, FILTER_ATTRIBUTES_EXCLUDED where FILTER_PROFILES.FILTER_PROFILE_NAME = 'MAQ' And FILTER_PROFILES.FILTER_PROFILE_ID = FILTER_ATTRIBUTES_EXCLUDED.FILTER_PROFILE_ID And FILTER_ATTRIBUTES_EXCLUDED.EXT_ATT_ID = EXTENDED_ATTRIBUTES.EXT_ATT_ID) As ExclusionFlag From EXTENDED_ATTRIBUTE_VALUES, EXTENDED_ATTRIBUTES, PRODUCTS Where PRODUCTS.PRODUCT_ID = EXTENDED_ATTRIBUTE_VALUES.PRODUCT_ID And not SMALL_TEXT_VALUE is null And EXTENDED_ATTRIBUTE_VALUES.EXT_ATT_ID > 1499 And EXTENDED_ATTRIBUTE_VALUES.EXT_ATT_ID = EXTENDED_ATTRIBUTES.EXT_ATT_ID And Column_Name = '" & sAT & "'", myConnection) Dim dt As New DataTable() adapter.Fill(dt) elbValue.DataSource = dt elbValue.DataBind()
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
I can access SqlServer 2000 fine, but not SqlServer 2005. My client is on Windows XP and SqlServer 2005 (dev version) is on Windows 2003. When I run I get: Error: net.windward.datasource.DataSourceException: JdbcDataSource could not ope n jdbc:sqlserver://T1-Databases;databaseName=AdventureWorks;integratedSecurity=t rue; net.windward.datasource.DataSourceException: net.windward.datasource.DataSourceE xception: JdbcDataSource could not open jdbc:sqlserver://T1-Databases;databaseNa me=AdventureWorks;integratedSecurity=true; at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1030) at net.windward.xmlreport.RunReport.main(RunReport.java:165) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe curity property value:true at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U nknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour ce) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1024) ... 1 more Exception in thread "main" net.windward.datasource.DataSourceException: net.wind ward.datasource.DataSourceException: JdbcDataSource could not open jdbc:sqlserve r://T1-Databases;databaseName=AdventureWorks;integratedSecurity=true; at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1030) at net.windward.xmlreport.RunReport.main(RunReport.java:165) Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid integratedSe curity property value:true at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(U nknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour ce) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at java.sql.DriverManager.getConnection(Unknown Source) at net.windward.datasource.jdbc.JdbcDataSource.<init>(JdbcDataSource.jav a:1024) ... 1 more Any ideas? thanks - dave
When using jdbc with IntegratedSecurity, I run into this problem when the machine is not part of a domain & gets its IP address via dhcp. Is this expected behavior or a bug in the jdbc driver.
The SQLServer and client application are installed on the same machine and a local admin is logged in, running the client app.
If I change one of the two parameters mentioned above, the connection can be established leading me to believe this may be intentional for security issues. Am I correct?
Hello All, kindly help me resolving following error. Earlier it was working fine with SQL server 2000, we want to migrate to sql server 2005. I am using websphere 6.0 with following jdbc_registry.properties contents. The driver file is copied under E:Program FilesIBMWebSphereAppServerlibext ***************************************************************************** driver.class=com.microsoft.sqlserver.jdbc.SQLServerDriver connection.url=jdbc: sqlserver://MyDBServer:1433;DatabaseName=abc;user=a; password=a user=a password=a ******************************************************************************
I am using sqljdbc_1.2.2828.100_enu drivers to connect to sql server 2005. following is the exception trace from my IDE.
************ Start Display Current Environment ************ WebSphere Platform 6.0 [BASE 6.0.2.13 cf130631.22] running with process name onschedule5Node01Cellonschedule5Node01server1 and process id 244 Host Operating System is Windows 2003, version 5.2 Java version = J2RE 1.4.2 IBM Windows 32 build cn142-20050609 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM was.install.root = E:Program FilesIBMWebSphereAppServer user.install.root = E:Program FilesIBMWebSphereAppServer/profiles/default Java Home = E:Program FilesIBMWebSphereAppServerjavajre ws.ext.dirs = E:Program FilesIBMWebSphereAppServer/java/lib;E:Program FilesIBMWebSphereAppServer/profiles/default/classes;E:Program FilesIBMWebSphereAppServer/classes;E:Program FilesIBMWebSphereAppServer/lib;E:Program FilesIBMWebSphereAppServer/installedChannels;E:Program FilesIBMWebSphereAppServer/lib/ext;E:Program FilesIBMWebSphereAppServer/web/help;E:Program FilesIBMWebSphereAppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime Classpath = E:Program FilesIBMWebSphereAppServer/profiles/default/properties;E:Program FilesIBMWebSphereAppServer/properties;E:Program FilesIBMWebSphereAppServer/lib/bootstrap.jar;E:Program FilesIBMWebSphereAppServer/lib/j2ee.jar;E:Program FilesIBMWebSphereAppServer/lib/lmproxy.jar;E:Program FilesIBMWebSphereAppServer/lib/urlprotocols.jar Java Library path = E:Program FilesIBMWebSphereAppServerjavain;.;C:WINDOWSsystem32;C:WINDOWS;E:Program FilesIBMWebSphereAppServerin;E:Program FilesIBMWebSphereAppServerjavain;E:Program FilesIBMWebSphereAppServerjavajrein;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;E:Program FilesIBMWebSphereAppServerjavain ************* End Display Current Environment ************* [3/20/08 7:15:44:188 EST] 0000000a ManagerAdmin I TRAS0028I: The trace output is stored in the circular memory buffer, holding 8192 message objects. [3/20/08 7:15:44:531 EST] 0000000a ManagerAdmin I TRAS0017I: The startup trace state is *=info. [3/20/08 7:15:44:531 EST] 0000000a ManagerAdmin A TRAS0007I: Logging to the service log is disabled [3/20/08 7:15:44:719 EST] 0000000a AdminInitiali A ADMN0015I: The administration service is initialized. [3/20/08 7:15:49:109 EST] 0000000a SystemOut O PLGC0057I: Plug-in configuration service is started successfully. [3/20/08 7:15:49:188 EST] 0000000a PMIImpl A PMON1001I: PMI is enabled [3/20/08 7:15:49:750 EST] 0000000a SibMessage I [:] CWSIU0000I: Release: WAS602.SIB Level: o0625.16 [3/20/08 7:15:49:766 EST] 0000000a SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true. [3/20/08 7:15:49:875 EST] 0000000a AuditServiceI A SECJ6004I: Security Auditing is disabled. [3/20/08 7:15:49:938 EST] 0000000a distSecurityC I SECJ0309I: Java 2 Security is disabled. [3/20/08 7:15:50:000 EST] 0000000a Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration. [3/20/08 7:15:50:016 EST] 0000000a distSecurityC I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class. [3/20/08 7:15:50:031 EST] 0000000a distSecurityC I SECJ0240I: Security service initialization completed successfully [3/20/08 7:15:50:297 EST] 0000000a ObjectPoolSer I OBPL0007I: Object Pool Manager service is disabled. [3/20/08 7:15:50:328 EST] 0000000a J2EEServiceMa I ASYN0059I: Work Manager service initialized successfully. [3/20/08 7:15:50:391 EST] 0000000a CScopeCompone I CSCP0002I: Compensation service is disabled. [3/20/08 7:15:50:531 EST] 0000000a SibMessage I [:] CWSID0006I: The SIB service was not enabled and will not be started. [3/20/08 7:15:50:531 EST] 0000000a ActivitySessi I WACS0045I: ActivitySession service is disabled. [3/20/08 7:15:50:562 EST] 0000000a SOAPContainer I WSWS1062I: SOAP Container Service has been initialized. [3/20/08 7:15:50:641 EST] 0000000a SchedulerServ I SCHD0036I: The Scheduler Service is initializing. [3/20/08 7:15:50:688 EST] 0000000a SchedulerServ I SCHD0037I: The Scheduler Service has been initialized. [3/20/08 7:15:50:875 EST] 0000000a StartUpServic I STUP0008I: The Startup Beans service is disabled. [3/20/08 7:15:50:891 EST] 0000000a I18nService I I18N0010I: The Internationalization service is created on server1. [3/20/08 7:15:50:891 EST] 0000000a I18nServiceSe I I18N0010I: The Internationalization service is disabled on server1. [3/20/08 7:15:51:406 EST] 0000000a SASRas A JSAS0001I: Security configuration initialized. [3/20/08 7:15:51:859 EST] 0000000a SASRas A JSAS0002I: Authentication protocol: CSIV2/IBM [3/20/08 7:15:51:859 EST] 0000000a SASRas A JSAS0003I: Authentication mechanism: SWAM [3/20/08 7:15:51:875 EST] 0000000a SASRas A JSAS0004I: Principal name: OnProjectRealm/wsadmin [3/20/08 7:15:51:891 EST] 0000000a SASRas A JSAS0005I: SecurityCurrent registered. [3/20/08 7:15:52:047 EST] 0000000a SASRas A JSAS0006I: Security connection interceptor initialized. [3/20/08 7:15:52:078 EST] 0000000a SASRas A JSAS0007I: Client request interceptor registered. [3/20/08 7:15:52:156 EST] 0000000a SASRas A JSAS0008I: Server request interceptor registered. [3/20/08 7:15:52:172 EST] 0000000a SASRas A JSAS0009I: IOR interceptor registered. [3/20/08 7:15:53:031 EST] 0000000a CoordinatorIm I HMGR0206I: The Coordinator is an Active Coordinator for core group DefaultCoreGroup. [3/20/08 7:15:53:062 EST] 0000000a DCSPluginSing I HMGR0005I: The Single Server DCS Core Stack transport has been started for core group DefaultCoreGroup. [3/20/08 7:15:53:344 EST] 0000000a NameServerImp A NMSV0018I: Name server available on bootstrap port 2809. [3/20/08 7:15:54:078 EST] 0000000a TreeBuilder W ODCF0002E: Exception: E:Program FilesIBMWebSphereAppServerprofilesdefaultconfigcellsonschedule5Node01Cellodeswebserver1_nodevariables.xml (The system cannot find the file specified). [3/20/08 7:15:54:203 EST] 0000000a UserRegistryI A SECJ0136I: Custom Registry:com.onproject.security.registry.JdbcRegistry has been initialized [3/20/08 7:15:54:344 EST] 0000000a distContextMa E SECJ0270E: Failed to get actual credentials. The exception is java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) . [3/20/08 7:15:54:359 EST] 0000000a distSecurityC E SECJ0208E: An unexpected exception occurred when attempting to authenticate the server's id during security initialization. The exception is java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) . [3/20/08 7:15:54:391 EST] 0000000a distSecurityC E SECJ0007E: Error during security initialization. The exception is java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) . [3/20/08 7:15:59:406 EST] 0000000a SchedulerServ I SCHD0040I: The Scheduler Service is stopping. [3/20/08 7:15:59:422 EST] 0000000a SchedulerServ I SCHD0002I: The Scheduler Service has stopped. [3/20/08 7:15:59:438 EST] 0000000a AppProfileCom I ACIN0009I: The application profiling service is stopping. [3/20/08 7:15:59:438 EST] 0000000a ActivitySessi I WACS0049I: The ActivitySession service is stopping. [3/20/08 7:15:59:547 EST] 0000000a WsServerImpl E WSVR0009E: Error occurred during startup META-INF/ws-server-components.xml [3/20/08 7:15:59:562 EST] 0000000a WsServerImpl E WSVR0009E: Error occurred during startup com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:194) at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133) at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387) at com.ibm.ws.runtime.WsServer.main(WsServer.java:53) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219) at java.lang.Thread.run(Thread.java:568) Caused by: com.ibm.ws.exception.RuntimeError: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:322) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149) at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820) at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649) at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:408) at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187) ... 10 more Caused by: com.ibm.websphere.security.WSSecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2187) at com.ibm.ws.security.core.distSecurityComponentImpl.initializeServerSubject(distSecurityComponentImpl.java:1928) at com.ibm.ws.security.core.distSecurityComponentImpl.initialize(distSecurityComponentImpl.java:341) at com.ibm.ws.security.core.distSecurityComponentImpl.startSecurity(distSecurityComponentImpl.java:298) at com.ibm.ws.security.core.SecurityComponentImpl.startSecurity(SecurityComponentImpl.java:101) at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:279) ... 17 more Caused by: com.ibm.websphere.security.auth.WSLoginFailedException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:435) at com.ibm.ws.security.common.auth.module.proxy.WSLoginModuleProxy.login(WSLoginModuleProxy.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:699) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:151) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:634) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:351) at javax.security.auth.login.LoginContext.invokeModule(LoginContext.java:631) at javax.security.auth.login.LoginContext.login(LoginContext.java:557) at com.ibm.ws.security.auth.JaasLoginHelper.jaas_login(JaasLoginHelper.java:376) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:1050) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:890) at com.ibm.ws.security.auth.distContextManagerImpl.login(distContextManagerImpl.java:881) at com.ibm.ws.security.auth.distContextManagerImpl.getServerSubjectInternal(distContextManagerImpl.java:2167) ... 22 more Caused by: java.lang.SecurityException: class "com.microsoft.sqlserver.jdbc.SQLServerConnection"'s signer information does not match signer information of other classes in the same package at java.lang.ClassLoader.checkCerts(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.defineClass(ClassLoader.java(Compiled Code)) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java(Compiled Code)) at java.net.URLClassLoader.defineClass(URLClassLoader.java:475) at java.net.URLClassLoader.access$500(URLClassLoader.java:109) at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848) at java.security.AccessController.doPrivileged1(Native Method) at java.security.AccessController.doPrivileged(AccessController.java:389) at java.net.URLClassLoader.findClass(URLClassLoader.java:371) at com.ibm.ws.bootstrap.ExtClassLoader.findClass(ExtClassLoader.java:113) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at java.lang.ClassLoader.loadClass(ClassLoader.java(Compiled Code)) at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source) at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:37) at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:290) at org.apache.commons.dbcp.BasicDataSource.validateConnectionFactory(BasicDataSource.java:877) at org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSource.java:851) at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:540) at com.onproject.security.registry.JdbcRegistry.getConnection(JdbcRegistry.java:188) at com.onproject.security.registry.JdbcRegistry.checkPassword(JdbcRegistry.java:225) at com.ibm.ws.security.registry.UserRegistryImpl.checkPassword(UserRegistryImpl.java:296) at com.ibm.ws.security.server.lm.swamLoginModule.login(swamLoginModule.java:429) ... 40 more
I have written a shell script that connects to a SQL Server 2005 database from Linux in order to monitor various areas of SQL.
One of the databases that are being monitored is mirrored, which is no problem in itself as I use the failoverPartner property in my connection string before I pass the TSQL. Unfortunately when the principal/mirror status changes, I get a constant stream of Failure Audit (Login failure) messages in the Mirror server Windows event log even though the failoverPartner property works and redirects to the partner, returning the correct information.
Here is a trace of the connection:
------
22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property : serverName Value:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:databaseNameValue:TESTDATABASE 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:failoverPartnerValue:SERVER2 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:integratedSecurityValue:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:loginTimeoutValue:3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: Calling securityManager.checkConnect(SERVER1,1433) 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: securityManager.checkConnect succeeded. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: Start time: 1172160120083 Time out time: 1172160123083 Timeout Unit Interval: 240 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER1 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160120323 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 0 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER1 port: 1433 Timeout slice: 232 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerException logException FINE: *** SQLException:[Thread[main,5,main], IO:5571e, Dbc:a8327] com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "TESTDATABASE" requested by the login. The login failed. Msg 4060, Level 11, State 1, Cannot open database "TESTDATABASE" requested by the login. The login failed. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER2 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160120369 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER2 port: 1433 Timeout slice: 237 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: adding new failover info server: SERVER1 instance: null database: TESTDATABASE server provided failover: SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverInfo failoverAdd FINE: Failover detected. failover partner=SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverMapSingleton putFailoverInfo FINE: Failover map add server: SERVER1; database:TESTDATABASE; Mirror:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: End of connect 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement <init> FINE: Statement properties ID:0 Connection:1 Result type:1003 (2003) Concurrency:1007 Fetchsize:128 bIsClosed:false tdsVersion:com.microsoft.sqlserver.jdbc.TDSVersion@15fea60 bCp1252:false useLastUpdateCount:true isServerSideCursor:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement doExecuteStatement FINE: Executing (not server cursor) USE TESTDATABASE SELECT "TESTCOLUMN" FROM TEST_TABLE ORDER BY DateTime 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection close FINE: Closing connection ID:1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property : serverName Value:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:databaseNameValue:TESTDATABASE 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:failoverPartnerValue:SERVER2 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:integratedSecurityValue:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.Util parseUrl FINE: Property:loginTimeoutValue:3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: Calling securityManager.checkConnect(SERVER1,1433) 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: securityManager.checkConnect succeeded. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: Start time: 1172160120736 Time out time: 1172160123736 Timeout Unit Interval: 240 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER1 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160120976 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 0 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER1 port: 1433 Timeout slice: 233 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerException logException FINE: *** SQLException:[Thread[main,5,main], IO:5571e, Dbc:a8327] com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "TESTDATABASE" requested by the login. The login failed. Msg 4060, Level 11, State 1, Cannot open database "TESTDATABASE" requested by the login. The login failed. 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt server name: SERVER2 port: 1433 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt endtime: 1172160121031 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: This attempt No: 1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connectHelper FINE: Connecting with server: SERVER2 port: 1433 Timeout slice: 236 Timeout Full: 3 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection loginWithFailover FINE: adding new failover info server: SERVER1 instance: null database: TESTDATABASE server provided failover: SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverInfo failoverAdd FINE: Failover detected. failover partner=SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.FailoverMapSingleton putFailoverInfo FINE: Failover map add server: SERVER1; database:TESTDATABASE; Mirror:SERVER1 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerConnection connect FINE: End of connect 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement <init> FINE: Statement properties ID:0 Connection:1 Result type:1003 (2003) Concurrency:1007 Fetchsize:128 bIsClosed:false tdsVersion:com.microsoft.sqlserver.jdbc.TDSVersion@15fea60 bCp1252:false useLastUpdateCount:true isServerSideCursor:false 22-Feb-2007 16:02:00 com.microsoft.sqlserver.jdbc.SQLServerStatement doExecuteStatement FINE: Executing (not server cursor) USE TESTDATABASE SELECT DATEDIFF(SECOND, DATETIME, GETDATE()) FROM TEST_TABLE 22-Feb-2007 16:02:01 com.microsoft.sqlserver.jdbc.SQLServerConnection close FINE: Closing connection ID:1
I cant supply a native database in the connection string (i.e Master) and then switch to the mirrored database in TSQL because the failoverPartner property does not apply to the session, only to the initial connection.
I have a problem with a PIPE "|" delimited flat file. I have a column "Description" in which we get a string in which we have PIPE "|" as data. How we can skip this and load it as a data into the column Description.
Hi;I went to the microsoft site to try to find a guide to the errormessages that the jdbc drivers give ( for sqlserver 2000 ).I had no luck.Does anyone know if there is such a guide?I got this mysterious error message below in my logs ( nothing visiblein user land ).Anyone know what it means?Thanks in advanceStevejava.sql.SQLException: [Microsoft][SQLServer 2000 Driver forJDBC][SQLServer]Transaction (Process ID 151) was deadlocked on lockresources with another process and has been chosen as the deadlockvictim. Rerun the transaction.
from time to time i get a Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException (no security manager: RMI class loader disabled) when i try to use the MS SQLServer 2005 JDBC Driver 1.1. with our RMI Server.
The connect String is jdbc:sqlserver://localhost:1433;databaseName=EXBBERLIN The SQL Server Version is 2000 SP 3. I am using java Version 1.5.0_08-b03.
I have tried to start our Server with the -Djava.security.manager switch, but this does not resolve the problem.
The stacktrace of the exception is
java.rmi.UnmarshalException: Error unmarshaling return; nested exception is: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException (no security manager: RMI class loader disabled) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:217) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at de.eidon.logis.database.DBReadManager_Stub.base2treeAndEdit(Unknown Source) .... Caused by: java.lang.ClassNotFoundException: com.microsoft.sqlserver.jdbc.SQLServerException (no security manager: RMI class loader disabled) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:371) at sun.rmi.server.LoaderHandler.loadClass(LoaderHandler.java:165) at java.rmi.server.RMIClassLoader$2.loadClass(RMIClassLoader.java:631) at java.rmi.server.RMIClassLoader.loadClass(RMIClassLoader.java:257) at sun.rmi.server.MarshalInputStream.resolveClass(MarshalInputStream.java:200) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215)
On another comnputer with almost the same setup everything works fine. The SQLServer 2000 JDBC Driver seems to work fine as well. Does anonne of you has an idea how to resolve this issue ?
Hello,I am working with the driver JDBC and I have a strange error that I can't find in Google for example.Caused by: com.seeburger.smarti.util.SmartiEJBException: nested exception is: com.seeburger.smarti.dao.DAOSysException: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Must declare the variable '@P2GROUP'.I don't know what is this variable '@P2GROUP'.Does anybody know it ?Thanks
public static void main(String[] args) { new Main(); }
}
The first call is ok, but the second throws an exception at sproc_stmt.executeQuery(); which says:
com.microsoft.sqlserver.jdbc.SQLServerException: Server failed to resume the transaction, desc: 3600000001. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source) at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.getPrepExecResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PreparedStatementExecutionRequest.executeStatement(Unknown Source) at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(Unknown Source) at javaapplication2.Main.getID(Main.java:53) at javaapplication2.Main.<init>(Main.java:33) at javaapplication2.Main.main(Main.java:85)
Am I doing something wrong or is this a bug?
I'm running on Win2003 with SQL Server 2005 Developer edition.
I'm trying to connect to a sql server 2005 express edition but have some trouble with it: i can connect to sql server through eclipse IDE but when I create a jar and try connecting to server, I get the following error.
Exception in thread "main" java.lang.SecurityException: invalid SHA1 signature f ile digest for com/microsoft/sqlserver/jdbc/SQLServerException.class at sun.security.util.SignatureFileVerifier.verifySection(Unknown Source)
at sun.security.util.SignatureFileVerifier.processImpl(Unknown Source) at sun.security.util.SignatureFileVerifier.process(Unknown Source) at java.util.jar.JarVerifier.processEntry(Unknown Source) at java.util.jar.JarVerifier.update(Unknown Source) at java.util.jar.JarFile.initializeVerifier(Unknown Source) at java.util.jar.JarFile.getInputStream(Unknown Source) at sun.misc.URLClassPath$JarLoader$2.getInputStream(Unknown Source) at sun.misc.Resource.cachedInputStream(Unknown Source) at sun.misc.Resource.getByteBuffer(Unknown Source) at java.net.URLClassLoader.defineClass(Unknown Source) at java.net.URLClassLoader.access$000(Unknown Source) at java.net.URLClassLoader$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClass(Unknown Source) at java.lang.ClassLoader.loadClassInternal(Unknown Source)
I'm using : - os : winxp - jdk1.5.0_06 - drivers : sqljdbc_1.1.1501.101 / sqljdbc_1.2.2828.100