Tracking Forums, Newsgroups, Maling Lists
Home Scripts Tutorials Tracker Forums
  Advanced Search
  HOME    TRACKER    MS SQL Server






SuperbHosting.net & Arvixe.com have generously sponsored dedicated servers and web hosting to ensure a reliable and scalable dedicated hosting solution for BigResource.com.







Msbase.jar, Mssqlserver.jar, Msutil.jar For JDBC SQL Server 2005 Missing In Install From Microsoft


Why do I no longer see the following jar files (msbase.jar, mssqlserver.jar, msutil.jar ) in the new JDBC driver for SQL Server 2005?  Are they no longer used?  the JDBC for SQL 2000 had those in the install package.

I'm not sure what forum this goes in.

 


View Complete Forum Thread with Replies
Sponsored Links:

Related Messages:
Microsoft SQL Server 2005 JDBC Driver
Hi, will there be a Windows Mobile edition of this driver, so that is possible to connect to SQL Everywhere on a Pocket PC  from Java ME apps?

Best regards.

Luca

View Replies !   View Related
Microsoft SQL Server 2005 JDBC Driver
I'm getting the following exception when attempting to connect to SQL Server 2005 using Microsoft's new JDBC driver:

com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host  has failed. java.net.ConnectException: Connection refused: connect

The help docs suggest checking connectivity using telnet. So attempting to connect via telnet to 127.0.0.1:1433 generates:

Could not open connection to the host, on port 23: Connect failed.

So I try to start telnet:

net start telnet

I get the following error message:

The service cannot be started either because it is disabled or because it has no enables devices associated with it.

Can anyone help?

Thanks

View Replies !   View Related
JDBC Driver For Microsoft SQL Server 2005 SP1
Hola a todos. Saludos cordiales.

Tengo instalado Microsoft Windows 2003 Server Standard Edition en un servidor IBM xSeries 220, estoy tratando de instalar IBM Director 5.10 y no ha sido posible hacer que se conecte con la base de datos.

Esto ocurre cuando intento configurar el Servidor SQL en la fase final de la instalación de IBM Director.

Gracias  por su ayuda, ¿puede alguien darme alguna sugerencia?

Erick Gómez, Venezuela

 

View Replies !   View Related
Microsoft SQL Server 2005 JDBC Driver 1.1 On Solaris
hi,Does MS2005 JDBC Driver 1.1 support integrated security on Solaris and if sohow?Thanks,MarcM

View Replies !   View Related
Transaction Not Commiting Using Microsoft SQL Server 2005 JDBC Driver 1.1
I have some code that should execute multiple statements and then commit.  I am using the Microsoft SQL Server 2005 JDBC Driver 1.1. 

The statements only commit ifI close the connection to the SQL Server 2005 instance.  I've looked at the example given at http://msdn2.microsoft.com/en-us/library/ms378931.aspx and it doesn't require closing the connection in order to commit. 

Example:

public void doCall(Connection con) {
   try {
      /*Turn off AutoCommit.*/
      con.setAutoCommit(false);

      /**Call Two Stored Procedures.*/
      Statement stmt = con.preapareCall(/*Java Code*/);
      stmt.setObject(/*Java Code*/);
      stmt.execute();

      Statement stmts = con.preapareCall(/*Java Code*/);
      stmt2.setObject(/*Java Code*/);
      stmt2.execute();

 

      /**Commit the transaction.*/
      con.commit(); 

   }
   catch (SQLException ex) {  //If some error occurs handle it.
      ex.printStackTrace();
      try {
         con.rollback();
      }
      catch (SQLException se) {
         se.printStackTrace();
      }
   }
}

My transaction never commits, and when I try to query the associated database tables in Microsoft SQL Server Management Studio 2005 my query hangs.

 

View Replies !   View Related
Create Jbc On TomCat Microsoft SQL Server 2005 JDBC Driver
 

Hi, We are looking for a way to create the jdbc connection with Microsoft jdbc driver on a TomCat server ? Meaning the exact information to enter within the server.xml file or within the Tomcat web server administration tool - data source GUI.

 
thanks

View Replies !   View Related
IntegratedSecurity Issues With Microsoft SQL Server 2005 JDBC Driver
I am using Microsoft SQL Server 2005 JDBC Driver to connect to SQL Server 2000 database, I am using the following connection URL

boolean iSecurity = true;

String connectionUrl = "jdbc:sqlserver://machine_name:1433;" + "databaseName=dbname;integratedSecurity=" + iSecurity;

I am getting the following error.

com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication.

How do I resolve it? I have the following set

VMOPTIONS = -Xrs -Djava.compiler=NONE -Djava.library.path=C:Microsoft SQL Server 2005 JDBC Driversqljdbc_1.1enuauthx86sqljdbc_auth.dll

Any help will be highly appreciated.

Regards

Arup

 

View Replies !   View Related
Required Microsoft Sql Server 2005 Express Server Roles For JDBC Connection
Hi!

I have developed a database in MS SQL Server 2005 Express, to which I would require only bulkadmin server role from an external java application, because I only need to update rows, insert values or use select queries in the database.

The problem is that, using either the Microsoft JDBC Driver 1.1 or the Java JDBC ODBC Driver and the Windows XP Data Base (ODBC) configurations, I need a user with sysadmin server role inside Sql Server, otherwise JDBC won't connect to the database using the selected user. Even if I leave the sql login with setupadmin or any server role lower than sysadmin, the connection is refused.

Is there no way to connect using JDBC to MS Sql Server 2005 other than granting the connected user sysadmin rights? My code looks as follows:




Code Snippet

String driver = "com.microsoft.sqlserver.jdbc.SQLServerDriver";
String url = "jdbc:sqlserver://FIREBLADE\SQLEXPRESS";
String user = "username";
String password = "password$$";
Connection conn;

Class.forName(driver);
conn = DriverManager.getConnection(url,user,password);
if (conn != null)
System.out.println("SQL Server Connection established ...");

I have heard that Java JDBC connections to Microsoft require high-level access.

Any informed answer is more than welcome. Thanks for reading my post!

View Replies !   View Related
How To Configure Distributed Transaction / XA Support Using Microsoft SQL Server 2005 JDBC Driver.
I am trying to configure distributed transaction and XA support using Microsoft SQL Server 2005 JDBC Driver. I have coppied SQLJDBC_XA.dll from XA directory and placed in my sql server binn directory and trying to run the script xa_install.sql from binn directory with command as below :

C:Program FilesMicrosoft SQL Server80ToolsBinn>
osql -U sa -n -P admin -S localhost -i C:JavaLibrariesMS SQL Driversqljdbc_1.2enuxa xa_install.sql

But I am getting error saying :
[DBNETLIB]SQL Server does not exist or access denied.
[DBNETLIB]ConnectionOpen (Connect()).

when I replaced local host with the machine name it gives error :
[Shared Memory]SQL Server does not exist or access denied.
[Shared Memory]ConnectionOpen (Connect()).

where in I am able to test connection from Websphere using the same connection.

Please help some one ....... I am in URGENT need.... I need to enable XA suport for my application to run........

Thanks ----

View Replies !   View Related
Cannot Install Sql Server 2005 As SSL-certificate Is Missing
Hi there U all,

 

for the third time I am installing SQL-Server 2005 express and i have an error.

Cannot install sql because .NET 2.0 framework is missing allthough I have the .NET 2.0 framework allready installed and even re-installed it too. When trying again I get the message that there isn't an SSL-certificate present.

 

My question is, would this probably cause the error when installing?

 

Anyone?

 

Grtz and thx,

 

Recloose(Thomas)

View Replies !   View Related
SQL Server 2005 Management Studio Is Missing After Install
I have several servers that do not have SSMS installed.  A couple of them are running as a clustered server.  How do I install SSMS on these servers?  they are running and have production databases on them.  I have tried re-installing the management tools but that didn't work.
 
Any advice will be greatly appreciated.
 
 

View Replies !   View Related
Sql 2005 Sp2 Install Error Microsoft SQL Server 2005 -- Errore 29506
Sp2 cannot be install

can someone help me

 

this is hotfix log

 

05/16/2007 13:05:30.583 ================================================================================
05/16/2007 13:05:30.599 Hotfix package launched
05/16/2007 13:05:30.630 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.646 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:30.662 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.677 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:30.693 Local Computer:
05/16/2007 13:05:30.708 Target Details: DC-01
05/16/2007 13:05:30.724   commonfilesdir = C:ProgrammiFile comuni
05/16/2007 13:05:30.740   lcidsupportdir = e:3f798aa49a0102c6d1f049aa36bd359d1040
05/16/2007 13:05:30.755   programfilesdir = C:Programmi
05/16/2007 13:05:30.771   programfilesdir_wow = C:Programmi
05/16/2007 13:05:30.771   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.802   supportdirlocal = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.818   windir = C:WINDOWS
05/16/2007 13:05:30.833   winsysdir = C:WINDOWSsystem32
05/16/2007 13:05:30.849   winsysdir_wow = C:WINDOWSSysWOW64
05/16/2007 13:05:30.865
05/16/2007 13:05:30.958 Enumerating applicable products for this patch
05/16/2007 13:05:31.005 Found Redist 2005 product definition
05/16/2007 13:05:31.021 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.036 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.052 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.068 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.442 Found Redist 2005 product definition
05/16/2007 13:05:31.458 Found Redist 2005 product definition
05/16/2007 13:05:31.474 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.489 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.505 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.521 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.677 Found SQL 2005 product definition
05/16/2007 13:05:32.270 Enumeration: Determining QFE level for product instance MSSQLSERVER
05/16/2007 13:05:32.286 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.286 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
05/16/2007 13:05:32.302 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
05/16/2007 13:05:32.317 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.333 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
05/16/2007 13:05:32.348 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.348 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:32.364 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.380 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:32.395 Product discovery completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 SP Level check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 Product language check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.426 Product version check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.442 Command-line instance name check completed during the install process
05/16/2007 13:05:32.458 SKU check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.473 Baseline build check completed during the installation process for MSSQLSERVER
05/16/2007 13:05:32.489 Baseline build check completed during the install process
05/16/2007 13:05:32.505 Found OLAP Server 2005 product definition
05/16/2007 13:05:33.004 Command-line instance name check completed during the install process
05/16/2007 13:05:33.004 Baseline build check completed during the install process
05/16/2007 13:05:33.036 Found Notification Services 2005 product definition
05/16/2007 13:05:33.520 Baseline build check completed during the install process
05/16/2007 13:05:33.551 Found Report Server 2005 product definition
05/16/2007 13:05:34.051 Command-line instance name check completed during the install process
05/16/2007 13:05:34.066 Baseline build check completed during the install process
05/16/2007 13:05:34.082 Found DTS 2005 product definition
05/16/2007 13:05:34.582 Baseline build check completed during the install process
05/16/2007 13:05:34.613 Found SQL 2005 Tools product definition
05/16/2007 13:05:35.113 Enumeration: Determining GDR branching Hotfix for product instance
05/16/2007 13:05:35.144 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL Server90Tools\BinnVSShellCommon7IDESQLWB.EXE
05/16/2007 13:05:35.160 Enumeration: No GDR branch Hotfix found for product instance
05/16/2007 13:05:35.175 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.191 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.207 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.207 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.222 Product discovery completed during the install process for SQL Tools
05/16/2007 13:05:35.238 SP Level check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product language check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product version check completed during the install process for SQL Tools
05/16/2007 13:05:35.269 SKU check completed during the install process for SQL Tools
05/16/2007 13:05:35.285 Baseline build check completed during the install process
05/16/2007 13:05:35.300 Found Redist 2005 product definition
05/16/2007 13:05:35.316 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.332 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.347 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.363 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.597 Found Redist 2005 product definition
05/16/2007 13:05:35.613 Found Redist 2005 product definition
05/16/2007 13:05:35.628 Found Redist 2005 product definition
05/16/2007 13:05:35.644 Found Redist 2005 product definition
05/16/2007 13:05:35.660 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.675 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.675 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.691 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.909 Found Redist 2005 product definition
05/16/2007 13:05:35.925 Found Redist 2005 product definition
05/16/2007 13:05:35.941 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.941 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.956 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.972 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:36.128 Found Redist 2005 product definition
05/16/2007 13:05:36.191 Product Enumeration Results:
05/16/2007 13:05:36.206   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli.inf
05/16/2007 13:05:36.222   baselinebuild = 1399
05/16/2007 13:05:36.237   build = 3042
05/16/2007 13:05:36.253   description = SQL Server Native Client
05/16/2007 13:05:36.269   details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.284   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.300   kbarticle = KB921896
05/16/2007 13:05:36.316   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.331   lcid = 1040
05/16/2007 13:05:36.347   legalproductname = Microsoft SQL Native Client
05/16/2007 13:05:36.362   machinetype = x86
05/16/2007 13:05:36.362   package = HotFixSqlncli
05/16/2007 13:05:36.378   packagetype = Hotfix
05/16/2007 13:05:36.394   productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.409   productname = Redist9
05/16/2007 13:05:36.425   recommendinstall = 1
05/16/2007 13:05:36.441   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:36.456   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:36.472   splevel = 2
05/16/2007 13:05:36.487   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:36.519   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:36.519   upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
05/16/2007 13:05:36.534   version = 9
05/16/2007 13:05:36.550
05/16/2007 13:05:36.581   File Group Details: MSI
05/16/2007 13:05:36.597     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:36.612     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:36.628     File Details: sqlncli.msi
05/16/2007 13:05:36.644
05/16/2007 13:05:36.659   Instance Details: SQL Server Native Client
05/16/2007 13:05:36.690     fullversion = 9.00.3042.00
05/16/2007 13:05:36.706     lcid = 1040
05/16/2007 13:05:36.722     productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.753     qfelevel = 3042
05/16/2007 13:05:36.769     sp = -1
05/16/2007 13:05:36.784
05/16/2007 13:05:36.800 Product Enumeration Results:
05/16/2007 13:05:36.831   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli_x64.inf
05/16/2007 13:05:36.847   baselinebuild = 1399
05/16/2007 13:05:36.862   build = 3042
05/16/2007 13:05:36.878   description = SQL Server Native Client
05/16/2007 13:05:36.893   details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.909   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.940   kbarticle = KB921896
05/16/2007 13:05:36.956   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.972   lcid = 1040
05/16/2007 13:05:36.987   legalproductname = Microsoft SQL Native Client (64 bit)
05/16/2007 13:05:37.018   machinetype = x64
05/16/2007 13:05:37.034   package = HotFixSqlncli_x64
05/16/2007 13:05:37.050   packagetype = Hotfix
05/16/2007 13:05:37.081   productname = Redist9
05/16/2007 13:05:37.097   recommendinstall = 1
05/16/2007 13:05:37.112   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.128   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.159   splevel = 2
05/16/2007 13:05:37.175   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.190   upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
05/16/2007 13:05:37.206   version = 9
05/16/2007 13:05:37.237
05/16/2007 13:05:37.253   File Group Details: MSI
05/16/2007 13:05:37.268     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:37.284     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.315     File Details: sqlncli_x64.msi
05/16/2007 13:05:37.331
05/16/2007 13:05:37.346 Product Enumeration Results:
05/16/2007 13:05:37.362   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlSupport.inf
05/16/2007 13:05:37.393   alwaysinstall = 1
05/16/2007 13:05:37.409   baselinebuild = 1399
05/16/2007 13:05:37.425   build = 3042
05/16/2007 13:05:37.456   description = File di supporto dell'installazione
05/16/2007 13:05:37.534   details = Service Pack per i file di supporto dell'installazione di SQL Server.
05/16/2007 13:05:37.565   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:37.581   kbarticle = KB921896
05/16/2007 13:05:37.596   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:37.612   keyqualifier = 1
05/16/2007 13:05:37.643   lcid = 1040
05/16/2007 13:05:37.659   legalproductname = File di supporto dell'installazione di SQL Server 2005
05/16/2007 13:05:37.674   machinetype = x86
05/16/2007 13:05:37.690   package = HotFixSqlSupport
05/16/2007 13:05:37.690   packagetype = Hotfix
05/16/2007 13:05:37.706   productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:37.737   productname = Redist9
05/16/2007 13:05:37.753   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.768   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.784   splevel = 2
05/16/2007 13:05:37.815   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:37.831   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.846   upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
05/16/2007 13:05:37.862   version = 9
05/16/2007 13:05:37.877
05/16/2007 13:05:37.893   File Group Details: MSI
05/16/2007 13:05:37.909     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCacheSQLSupport<MachineType><LCID>
05/16/2007 13:05:37.940     parameters = REINSTALL=ALL
05/16/2007 13:05:37.956     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.971     File Details: SqlSupport.msi
05/16/2007 13:05:37.987
05/16/2007 13:05:38.002   Instance Details: File di supporto dell'installazione
05/16/2007 13:05:38.018     fullversion = 9.2.3042
05/16/2007 13:05:38.049     lcid = 1040
05/16/2007 13:05:38.065     productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:38.081     qfelevel = 3042
05/16/2007 13:05:38.096     sp = -1
05/16/2007 13:05:38.112
05/16/2007 13:05:38.143 Product Enumeration Results:
05/16/2007 13:05:38.159   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQL.inf
05/16/2007 13:05:38.174   baselinebuild = 1399
05/16/2007 13:05:38.190   baselinebuildmax = 3042
05/16/2007 13:05:38.205   build = 3042
05/16/2007 13:05:38.221   description = Servizi di database
05/16/2007 13:05:38.237   details = Service Pack per il Motore di database e gli strumenti di SQL Server per la gestione di dati relazionali e XML, per la replica e per la ricerca full-text.
05/16/2007 13:05:38.252   installer = Hotfix
05/16/2007 13:05:38.268   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:38.284   kbarticle = KB921896
05/16/2007 13:05:38.299   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:38.330   lcid = 1040
05/16/2007 13:05:38.346   legalproductname = Servizi di database SQL Server 2005
05/16/2007 13:05:38.362   machinetype = x86
05/16/2007 13:05:38.393   package = HotFixSQL
05/16/2007 13:05:38.409   packagetype = Hotfix
05/16/2007 13:05:38.424   productname = SQL9
05/16/2007 13:05:38.440   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:38.471   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:38.487   sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:38.502   splevel = 2
05/16/2007 13:05:38.518   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:38.549   sqlutility = sqlcmd.exe
05/16/2007 13:05:38.565   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:38.580   validateauthentication = true
05/16/2007 13:05:38.596   version = 9
05/16/2007 13:05:38.612
05/16/2007 13:05:38.627   File Group Details: MSP
05/16/2007 13:05:38.658     parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:38.674     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:38.690     File Details: sqlrun_sql.msp
05/16/2007 13:05:38.705
05/16/2007 13:05:38.721   Instance Details: MSSQLSERVER
05/16/2007 13:05:38.752     agentservicename = SQLSERVERAGENT
05/16/2007 13:05:38.768     clustername =
05/16/2007 13:05:38.783     default = TRUE
05/16/2007 13:05:38.815     ftsservicename = MSFTESQL
05/16/2007 13:05:38.830     fullversion = 2005.090.1399.00
05/16/2007 13:05:38.846     hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
05/16/2007 13:05:38.877     id = MSSQL.1
05/16/2007 13:05:38.893     installsqldatadir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.908     installsqldir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.924     lcid = 1040
05/16/2007 13:05:38.940     name = MSSQLSERVER
05/16/2007 13:05:38.971     productcode = {E0BB3923-308B-4BE9-B3A3-FD5517481E48}
05/16/2007 13:05:39.002     qfelevel = 1399
05/16/2007 13:05:39.018     servicename = MSSQLServer
05/16/2007 13:05:39.033     sku = STANDARD
05/16/2007 13:05:39.049     sp = 0
05/16/2007 13:05:39.065     type = SQL Server Standalone Product
05/16/2007 13:05:39.096     vermajbld = 1399
05/16/2007 13:05:39.111     version = 9
05/16/2007 13:05:39.127
05/16/2007 13:05:39.143 Product Enumeration Results:
05/16/2007 13:05:39.174   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixAS.inf
05/16/2007 13:05:39.189   baselinebuild = 1399
05/16/2007 13:05:39.205   baselinebuildmax = 3042
05/16/2007 13:05:39.236   build = 3042
05/16/2007 13:05:39.252   description = Analysis Services
05/16/2007 13:05:39.268   details = Service Pack per Analysis Services e per gli strumenti per il supporto dell'elaborazione analitica in linea (OLAP) e del data mining.
05/16/2007 13:05:39.283   installer = Hotfix
05/16/2007 13:05:39.299   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.330   kbarticle = KB921896
05/16/2007 13:05:39.346   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.361   lcid = 1040
05/16/2007 13:05:39.377   legalproductname = SQL Server Analysis Services 2005
05/16/2007 13:05:39.408   machinetype = x86
05/16/2007 13:05:39.424   package = HotFixAS
05/16/2007 13:05:39.455   packagetype = Hotfix
05/16/2007 13:05:39.471   productname = OLAP9
05/16/2007 13:05:39.486   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:39.502   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:39.533   splevel = 2
05/16/2007 13:05:39.549   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:39.564   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:39.580   version = 9
05/16/2007 13:05:39.611
05/16/2007 13:05:39.627   File Group Details: MSP
05/16/2007 13:05:39.642     parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:39.674     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:39.689     File Details: sqlrun_as.msp
05/16/2007 13:05:39.705
05/16/2007 13:05:39.736 Product Enumeration Results:
05/16/2007 13:05:39.752   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixNS.inf
05/16/2007 13:05:39.767   baselinebuild = 1399
05/16/2007 13:05:39.799   baselinebuildmax = 3042
05/16/2007 13:05:39.814   build = 3042
05/16/2007 13:05:39.830   description = Notification Services
05/16/2007 13:05:39.861   details = Service Pack per Notification Services, una piattaforma per lo sviluppo e la distribuzione di applicazioni per l'invio di notifiche personalizzate e tempestive a un'ampia gamma di dispositivi o applicazioni.
05/16/2007 13:05:39.877   installer = Hotfix
05/16/2007 13:05:39.892   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.908   kbarticle = KB921896
05/16/2007 13:05:39.924   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.939   lcid = 1040
05/16/2007 13:05:39.970   legalproductname = Istanze di SQL Server Notification Services 2005
05/16/2007 13:05:39.986   machinetype = x86
05/16/2007 13:05:40.002   package = HotFixNS
05/16/2007 13:05:40.017   packagetype = Hotfix
05/16/2007 13:05:40.033   productname = NS9
05/16/2007 13:05:40.064   recommendinstall = 1
05/16/2007 13:05:40.080   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.095   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.111   splevel = 2
05/16/2007 13:05:40.142   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.158   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.189   version = 9
05/16/2007 13:05:40.205
05/16/2007 13:05:40.220   File Group Details: MSP
05/16/2007 13:05:40.236     parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.267     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.283     File Details: sqlrun_ns.msp
05/16/2007 13:05:40.298
05/16/2007 13:05:40.330 Product Enumeration Results:
05/16/2007 13:05:40.345   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixRS.inf
05/16/2007 13:05:40.361   baselinebuild = 1399
05/16/2007 13:05:40.376   baselinebuildmax = 3042
05/16/2007 13:05:40.408   build = 3042
05/16/2007 13:05:40.423   description = Reporting Services
05/16/2007 13:05:40.439   details = Service Pack per Server report e Generatore report, utilizzati per la gestione, l'esecuzione, il rendering e la distribuzione dei report.
05/16/2007 13:05:40.455   installer = Hotfix
05/16/2007 13:05:40.486   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:40.501   kbarticle = KB921896
05/16/2007 13:05:40.517   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:40.548   lcid = 1040
05/16/2007 13:05:40.564   legalproductname = SQL Server Reporting Services 2005
05/16/2007 13:05:40.580   machinetype = x86
05/16/2007 13:05:40.611   package = HotFixRS
05/16/2007 13:05:40.626   packagetype = Hotfix
05/16/2007 13:05:40.642   productname = RS9
05/16/2007 13:05:40.658   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.673   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.689   sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:40.720   splevel = 2
05/16/2007 13:05:40.736   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.751   sqlutility = sqlcmd.exe
05/16/2007 13:05:40.767   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.798   validateauthentication = 1
05/16/2007 13:05:40.814   version = 9
05/16/2007 13:05:40.829
05/16/2007 13:05:40.861   File Group Details: MSP
05/16/2007 13:05:40.876     parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.892     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.908     File Details: sqlrun_rs.msp
05/16/2007 13:05:40.939
05/16/2007 13:05:40.954 Product Enumeration Results:
05/16/2007 13:05:40.970   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixDTS.inf
05/16/2007 13:05:41.001   baselinebuild = 1399
05/16/2007 13:05:41.017   baselinebuildmax = 3042
05/16/2007 13:05:41.032   build = 3042
05/16/2007 13:05:41.064   description = Integration Services
05/16/2007 13:05:41.079   details = Service Pack per Integration Services, una serie di strumenti e oggetti programmabili per la creazione e la gestione di pacchetti per l'estrazione, la trasformazione e il caricamento dei dati, nonché per l'esecuzione di attività.
05/16/2007 13:05:41.095   installer = Hotfix
05/16/2007 13:05:41.126   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.142   kbarticle = KB921896
05/16/2007 13:05:41.157   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.173   lcid = 1040
05/16/2007 13:05:41.189   legalproductname = SQL Server Integration Services 2005
05/16/2007 13:05:41.220   machinetype = x86
05/16/2007 13:05:41.236   package = HotFixDTS
05/16/2007 13:05:41.251   packagetype = Hotfix
05/16/2007 13:05:41.282   productname = DTS9
05/16/2007 13:05:41.298   recommendinstall = 1
05/16/2007 13:05:41.314   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.329   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.360   splevel = 2
05/16/2007 13:05:41.376   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:41.392   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:41.423   version = 9
05/16/2007 13:05:41.439
05/16/2007 13:05:41.454   File Group Details: MSP
05/16/2007 13:05:41.485     parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:41.501     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:41.517     File Details: sqlrun_dts.msp
05/16/2007 13:05:41.548
05/16/2007 13:05:41.564 Product Enumeration Results:
05/16/2007 13:05:41.579   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixTools.inf
05/16/2007 13:05:41.610   baselinebuild = 1399
05/16/2007 13:05:41.626   baselinebuildmax = 3042
05/16/2007 13:05:41.642   build = 3042
05/16/2007 13:05:41.657   description = Componenti client
05/16/2007 13:05:41.688   details = Service Pack per gli strumenti interattivi di gestione per l'esecuzione di SQL Server, tra cui Gestione configurazione SQL Server, SQL Server Management Studio, SQL Profiler e Monitoraggio replica.
05/16/2007 13:05:41.704   installer = Hotfix
05/16/2007 13:05:41.720   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.751   kbarticle = KB921896
05/16/2007 13:05:41.767   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.782   lcid = 1040
05/16/2007 13:05:41.798   legalproductname = Componenti workstation e strumenti di SQL Server 2005
05/16/2007 13:05:41.829   machinetype = x86
05/16/2007 13:05:41.845   package = HotFixTools
05/16/2007 13:05:41.860   packagetype = Hotfix
05/16/2007 13:05:41.876   productname = SQLTools9
05/16/2007 13:05:41.892   recommendinstall = 1
05/16/2007 13:05:41.923   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.938   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.954   sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:41.985   splevel = 2
05/16/2007 13:05:42.001   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.016   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.032   version = 9
05/16/2007 13:05:42.063
05/16/2007 13:05:42.079   File Group Details: MSP
05/16/2007 13:05:42.095     parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:42.110     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:42.141     File Details: sqlrun_tools.msp
05/16/2007 13:05:42.157
05/16/2007 13:05:42.188   Instance Details: SQL Tools
05/16/2007 13:05:42.204     associatedhotfixbuild = 1520
05/16/2007 13:05:42.220     clustername =
05/16/2007 13:05:42.235     fullversion = 9.2.3042
05/16/2007 13:05:42.266     hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
05/16/2007 13:05:42.282     id =
05/16/2007 13:05:42.298     installsqldatadir =
05/16/2007 13:05:42.313     installsqldir = C:ProgrammiMicrosoft SQL Server90Tools
05/16/2007 13:05:42.329     lcid = 1040
05/16/2007 13:05:42.360     name =
05/16/2007 13:05:42.376     productcode = {B03FBBA3-CCE4-40CC-A0F1-01F952E7EB3E}
05/16/2007 13:05:42.391     qfelevel = 3042
05/16/2007 13:05:42.407     sku = STANDARD
05/16/2007 13:05:42.438     sp = 2
05/16/2007 13:05:42.454     type = Tools Only
05/16/2007 13:05:42.469     vermajbld = 3042
05/16/2007 13:05:42.501     version = 9
05/16/2007 13:05:42.516
05/16/2007 13:05:42.532 Product Enumeration Results:
05/16/2007 13:05:42.563   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6.inf
05/16/2007 13:05:42.579   baselinebuild = 1399
05/16/2007 13:05:42.594   build = 6.10.1129.0
05/16/2007 13:05:42.626   description = Parser MSXML 6.0
05/16/2007 13:05:42.641   details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:42.657   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:42.688   kbarticle = KB921896
05/16/2007 13:05:42.704   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:42.719   lcid = 1040
05/16/2007 13:05:42.751   legalproductname = Parser MSXML 6.0
05/16/2007 13:05:42.766   machinetype = x86
05/16/2007 13:05:42.782   package = HotFixMsxml6
05/16/2007 13:05:42.797   packagetype = Hotfix
05/16/2007 13:05:42.813   productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:42.844   productname = Redist9
05/16/2007 13:05:42.860   recommendinstall = 1
05/16/2007 13:05:42.876   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:42.891   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:42.922   splevel = 2
05/16/2007 13:05:42.938   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.969   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.985   upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
05/16/2007 13:05:43.000   version = 9
05/16/2007 13:05:43.016
05/16/2007 13:05:43.032   File Group Details: MSI
05/16/2007 13:05:43.063     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.079     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.094     File Details: msxml6.msi
05/16/2007 13:05:43.110
05/16/2007 13:05:43.141   Instance Details: Parser MSXML 6.0
05/16/2007 13:05:43.157     fullversion = 6.10.1129.0
05/16/2007 13:05:43.172     lcid = 1040
05/16/2007 13:05:43.188     productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:43.219     qfelevel = 1129
05/16/2007 13:05:43.235     sp = -1
05/16/2007 13:05:43.250
05/16/2007 13:05:43.266 Product Enumeration Results:
05/16/2007 13:05:43.297   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6_x64.inf
05/16/2007 13:05:43.313   baselinebuild = 1399
05/16/2007 13:05:43.328   build = 6.10.1129.0
05/16/2007 13:05:43.360   description = Parser MSXML 6.0
05/16/2007 13:05:43.375   details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:43.391   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.422   kbarticle = KB921896
05/16/2007 13:05:43.438   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.453   lcid = 1040
05/16/2007 13:05:43.469   legalproductname = Parser MSXML 6.0 (64 bit)
05/16/2007 13:05:43.500   machinetype = x64
05/16/2007 13:05:43.516   package = HotFixMsxml6_x64
05/16/2007 13:05:43.532   packagetype = Hotfix
05/16/2007 13:05:43.563   productname = Redist9
05/16/2007 13:05:43.578   recommendinstall = 1
05/16/2007 13:05:43.594   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:43.610   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:43.625   splevel = 2
05/16/2007 13:05:43.641   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:43.656   upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
05/16/2007 13:05:43.672   version = 9
05/16/2007 13:05:43.688
05/16/2007 13:05:43.703   File Group Details: MSI
05/16/2007 13:05:43.719     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.735     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.750     File Details: msxml6_x64.msi
05/16/2007 13:05:43.781
05/16/2007 13:05:43.797 Product Enumeration Results:
05/16/2007 13:05:43.813   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4.inf
05/16/2007 13:05:43.828   baselinebuild = 1399
05/16/2007 13:05:43.844   build = 3042
05/16/2007 13:05:43.860   description = SQLXML4
05/16/2007 13:05:43.875   details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:43.891   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.906   kbarticle = KB921896
05/16/2007 13:05:43.922   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.938   lcid = 1040
05/16/2007 13:05:43.953   legalproductname = SQLXML4
05/16/2007 13:05:43.969   machinetype = x86
05/16/2007 13:05:43.984   package = HotFixSqlxml4
05/16/2007 13:05:44.000   packagetype = Hotfix
05/16/2007 13:05:44.016   productname = Redist9
05/16/2007 13:05:44.047   recommendinstall = 1
05/16/2007 13:05:44.063   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.078   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.094   splevel = 2
05/16/2007 13:05:44.109   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:44.125   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.141   upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
05/16/2007 13:05:44.156   version = 9
05/16/2007 13:05:44.172
05/16/2007 13:05:44.188   File Group Details: MSI
05/16/2007 13:05:44.203     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.219     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.234     File Details: sqlxml4.msi
05/16/2007 13:05:44.266
05/16/2007 13:05:44.281 Product Enumeration Results:
05/16/2007 13:05:44.297   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4_x64.inf
05/16/2007 13:05:44.312   baselinebuild = 1399
05/16/2007 13:05:44.328   build = 3042
05/16/2007 13:05:44.344   description = SQLXML4
05/16/2007 13:05:44.375   details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:44.391   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.391   kbarticle = KB921896
05/16/2007 13:05:44.422   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.422   lcid = 1040
05/16/2007 13:05:44.437   legalproductname = SQLXML4 (64 bit)
05/16/2007 13:05:44.453   machinetype = x64
05/16/2007 13:05:44.469   package = HotFixSqlxml4_x64
05/16/2007 13:05:44.484   packagetype = Hotfix
05/16/2007 13:05:44.500   productname = Redist9
05/16/2007 13:05:44.516   recommendinstall = 1
05/16/2007 13:05:44.531   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.547   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.562   splevel = 2
05/16/2007 13:05:44.594   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.609   upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
05/16/2007 13:05:44.625   version = 9
05/16/2007 13:05:44.640
05/16/2007 13:05:44.656   File Group Details: MSI
05/16/2007 13:05:44.672     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.687     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.703     File Details: sqlxml4_x64.msi
05/16/2007 13:05:44.719
05/16/2007 13:05:44.734 Product Enumeration Results:
05/16/2007 13:05:44.750   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC.inf
05/16/2007 13:05:44.765   baselinebuild = 1399
05/16/2007 13:05:44.781   build = 2004
05/16/2007 13:05:44.797   description = Compatibilità con le versioni precedenti
05/16/2007 13:05:44.812   details = Service Pack per i componenti per la compatibilità con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:44.828   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.844   kbarticle = KB921896
05/16/2007 13:05:44.859   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.875   lcid = 1040
05/16/2007 13:05:44.890   legalproductname = Compatibilità con le versioni precedenti a Microsoft SQL Server 2005
05/16/2007 13:05:44.906   machinetype = x86
05/16/2007 13:05:44.922   package = HotFixSQLServer2005_BC
05/16/2007 13:05:44.937   packagetype = Hotfix
05/16/2007 13:05:44.953   productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:44.968   productname = Redist9
05/16/2007 13:05:44.984   recommendinstall = 1
05/16/2007 13:05:45.015   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.031   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.047   splevel = 2
05/16/2007 13:05:45.062   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:45.078   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.093   upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
05/16/2007 13:05:45.109   version = 9
05/16/2007 13:05:45.125
05/16/2007 13:05:45.140   File Group Details: MSI
05/16/2007 13:05:45.171     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.187     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.203     File Details: SQLServer2005_BC.msi
05/16/2007 13:05:45.203
05/16/2007 13:05:45.218   Instance Details: Compatibilità con le versioni precedenti
05/16/2007 13:05:45.234     fullversion = 8.05.2004
05/16/2007 13:05:45.250     lcid = 1040
05/16/2007 13:05:45.265     productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:45.281     qfelevel = 2004
05/16/2007 13:05:45.296     sp = -1
05/16/2007 13:05:45.312
05/16/2007 13:05:45.328 Product Enumeration Results:
05/16/2007 13:05:45.343   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC_x64.inf
05/16/2007 13:05:45.375   baselinebuild = 1399
05/16/2007 13:05:45.375   build = 2004
05/16/2007 13:05:45.390   description = Compatibilità con le versioni precedenti
05/16/2007 13:05:45.406   details = Service Pack per i componenti per la compatibilità con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:45.421   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.453   kbarticle = KB921896
05/16/2007 13:05:45.453   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.468   lcid = 1040
05/16/2007 13:05:45.484   legalproductname = Compatibilità con le versioni precedenti a Microsoft SQL Server 2005 (64 bit)
05/16/2007 13:05:45.500   machinetype = x64
05/16/2007 13:05:45.515   package = HotFixSQLServer2005_BC_x64
05/16/2007 13:05:45.531   packagetype = Hotfix
05/16/2007 13:05:45.546   productname = Redist9
05/16/2007 13:05:45.562   recommendinstall = 1
05/16/2007 13:05:45.578   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.593   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.609   splevel = 2
05/16/2007 13:05:45.624   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.640   upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
05/16/2007 13:05:45.656   version = 9
05/16/2007 13:05:45.671
05/16/2007 13:05:45.703   File Group Details: MSI
05/16/2007 13:05:45.718     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.734     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.749     File Details: SQLServer2005_BC_x64.msi
05/16/2007 13:05:45.765
05/16/2007 13:05:45.781 Product Enumeration Results:
05/16/2007 13:05:45.796   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter.inf
05/16/2007 13:05:45.812   baselinebuild = 1399
05/16/2007 13:05:45.828   build = 3042
05/16/2007 13:05:45.843   description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.874   details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:45.890   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.906   kbarticle = KB921896
05/16/2007 13:05:45.921   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.937   lcid = 1040
05/16/2007 13:05:45.953   legalproductname = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.968   machinetype = x86
05/16/2007 13:05:45.984   package = HotFixSqlWriter
05/16/2007 13:05:45.999   packagetype = Hotfix
05/16/2007 13:05:46.015   productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.031   productname = Redist9
05/16/2007 13:05:46.062   recommendinstall = 1
05/16/2007 13:05:46.078   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.093   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.109   splevel = 2
05/16/2007 13:05:46.124   sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:46.140   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.156   upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
05/16/2007 13:05:46.171   version = 9
05/16/2007 13:05:46.187
05/16/2007 13:05:46.203   File Group Details: MSI
05/16/2007 13:05:46.218     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.234     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.249     File Details: SqlWriter.msi
05/16/2007 13:05:46.281
05/16/2007 13:05:46.296   Instance Details: Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.312     fullversion = 9.00.3042.00
05/16/2007 13:05:46.328     lcid = 1040
05/16/2007 13:05:46.328     productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.359     qfelevel = 3042
05/16/2007 13:05:46.374     sp = -1
05/16/2007 13:05:46.390
05/16/2007 13:05:46.406 Product Enumeration Results:
05/16/2007 13:05:46.421   INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter_x64.inf
05/16/2007 13:05:46.437   baselinebuild = 1399
05/16/2007 13:05:46.453   build = 3042
05/16/2007 13:05:46.468   description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.484   details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:46.499   installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:46.515   kbarticle = KB921896
05/16/2007 13:05:46.546   kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:46.562   lcid = 1040
05/16/2007 13:05:46.577   legalproductname = Microsoft SQL Server VSS Writer (64 bit)
05/16/2007 13:05:46.593   machinetype = x64
05/16/2007 13:05:46.609   package = HotFixSqlWriter_x64
05/16/2007 13:05:46.640   packagetype = Hotfix
05/16/2007 13:05:46.656   productname = Redist9
05/16/2007 13:05:46.671   recommendinstall = 1
05/16/2007 13:05:46.687   relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.718   servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.734   splevel = 2
05/16/2007 13:05:46.749   supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.781   upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
05/16/2007 13:05:46.796   version = 9
05/16/2007 13:05:46.796
05/16/2007 13:05:46.827   File Group Details: MSI
05/16/2007 13:05:46.843     cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.859     sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.874     File Details: SqlWriter_x64.msi
05/16/2007 13:05:46.890
05/16/2007 13:05:57.967 Registry: Opened registry key "SystemCurrentControlSetControlSession Manager"
05/16/2007 13:05:57.967 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:57.982   Multi-string values:
05/16/2007 13:05:57.998 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:58.014   Multi-string values:
05/16/2007 13:05:58.029     ??e:1971703f8a5eaa69b207
05/16/2007 13:05:58.045 PFR Check: PFR was found, but no files to be serviced were being referenced
05/16/2007 13:06:18.980 Authenticating user using SAPWD
05/16/2007 13:06:18.995 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:19.011 Starting service: MSSQLServer
05/16/2007 13:06:23.666 Started service: MSSQLServer
05/16/2007 13:06:23.729 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:24.323 User authentication failed
05/16/2007 13:06:24.354   Messaggio 18456, livello 14, stato 1, server DC-01, riga 1
05/16/2007 13:06:24.385   Accesso non riuscito per l'utente 'sa'.
05/16/2007 13:06:24.416 Stopping service: MSSQLServer
05/16/2007 13:06:26.432 Stopped service: MSSQLServer
05/16/2007 13:06:29.978 Authenticating user using Windows Authentication
05/16/2007 13:06:29.994 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:30.009 Starting service: MSSQLServer
05/16/2007 13:06:34.837 Started service: MSSQLServer
05/16/2007 13:06:34.931 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:35.462 Authenticating user using Windows Authentication
05/16/2007 13:06:35.477 Validating database connections using Windows Authentication
05/16/2007 13:06:35.868 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.337 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:36.352 Validating database connections using Windows Authentication
05/16/2007 13:06:36.680 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.696 User authentication was successful
05/16/2007 13:06:36.696 Stopping service: MSSQLServer
05/16/2007 13:06:38.711 Stopped service: MSSQLServer
05/16/2007 13:06:40.461 Authenticating user using Windows Authentication
05/16/2007 13:06:40.477 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:40.492 Starting service: MSSQLServer
05/16/2007 13:06:45.086 Started service: MSSQLServer
05/16/2007 13:06:45.101 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:45.523 Authenticating user using Windows Authentication
05/16/2007 13:06:45.539 Validating database connections using Windows Authentication
05/16/2007 13:06:46.085 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.414 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:46.429 Validating database connections using Windows Authentication
05/16/2007 13:06:46.742 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.757 User authentication was successful
05/16/2007 13:06:46.773 Stopping service: MSSQLServer
05/16/2007 13:06:48.788 Stopped service: MSSQLServer
05/16/2007 13:06:48.835 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.851 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.866 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:48.882 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.287 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.303 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.662 Locked file: Checking for locked files
05/16/2007 13:07:05.099 Attempting to pause the 32 bit ngen queue
05/16/2007 13:07:05.271 Installing product: SQL9
05/16/2007 13:07:05.286 Installing instance: MSSQLSERVER
05/16/2007 13:07:05.302 Installing target: DC-01
05/16/2007 13:07:05.317 Installing file: sqlrun_sql.msp
05/16/2007 13:07:05.349 Copy Engine: Creating MSP install log file at: C:ProgrammiMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
05/16/2007 13:07:05.364 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:07:05.380 Registry: Cannot read registry key value "Debug"
05/16/2007 13:09:06.458 MSP Error: 29506  Impossibile modificare le autorizzazioni di protezione del file C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLData per l'utente SYSTEM. Per continuare, verificare l'esistenza dell'account e del dominio che eseguono l'installazione di SQL Server. Verificare inoltre che tale account disponga dei privilegi di amministratore e che  sia presente nell'unità di destinazione.
05/16/2007 13:10:03.685 MSP returned 1603: Si è verificato un errore irreversibile durante l'installazione.
05/16/2007 13:10:03.701 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:10:03.716 Registry: Cannot read registry key value "Debug"
05/16/2007 13:10:04.248 Copy Engine: Error, unable to install MSP file: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLFilessqlrun_sql.msp
05/16/2007 13:10:04.310 The following exception occurred: Impossibile installare il file MSP di Windows Installer  Date: 05/16/2007 13:10:04.310  File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp  Line: 800
05/16/2007 13:10:08.966 Watson: Param1 = Do_sqlFileSDDL
05/16/2007 13:10:08.997 Watson: Param2 = 0x7342
05/16/2007 13:10:09.044 Watson: Param3 = ExceptionInSDDL
05/16/2007 13:10:09.075 Watson: Param4 = 0x7342
05/16/2007 13:10:09.106 Watson: Param5 = sqlcasqlsddlca.cpp@65
05/16/2007 13:10:09.153 Watson: Param6 = Unknown
05/16/2007 13:10:09.184 Watson: Param7 = SQL9
05/16/2007 13:10:09.200 Watson: Param8 = Hotfix@
05/16/2007 13:10:09.231 Watson: Param9 = x86
05/16/2007 13:10:09.247 Watson: Param10 = 3042
05/16/2007 13:10:09.309 Installed product: SQL9
05/16/2007 13:10:09.356 Hotfix package completed
05/16/2007 13:10:09.388 Attempting to continue the 32 bit ngen queue

View Replies !   View Related
SQL Server 2005 64bit Install - Missing Management Studio
Good Afternoon,

 

I just installed SQL Server 2005 64bit on a fresh system with no other applications loaded on running on the new server.

 

The only other component that was installed with the SS2K5 database services is SSIS. The base installation and the SP2 patch went on perfect.

 

I went looking for the Management Studio thru the Start menu options and it is NOT under the Microsoft SQL Server 2005 group. The only options under the SS2K5 group are "Configuration Tools" and "Docs and Tutorials".

 

Here are file names that I downloaded from the MS website and installed.

 

   SW CD SQL Svr Enterprise Edtn 2005 64Bit X64 English #1 x64 MLF.x11-57796 (which is a zipped)

 

   SQLServer2005SP2-KB921896-x64-ENU

 

There was also another zipped file that I tried to install but it seems to be a duplicate of the zipped file above:

 

SW CD SQL Svr Enterprise Edtn 2005 64Bit X64 English #2 x64 MLF.x11-57797

 

Any help would be greatly appriciated.

 

Thanks ALL!

 

J Kusch

View Replies !   View Related
Trying To Install Microsoft SQL Server 2005 CTP Setup
Hi

I need help when i try to install Microsoft SQL Server 2005 CTP Setup it fails every time i tried and now i don't what to do

Thank's

View Replies !   View Related
Microsoft SQL Server 2005 Install Problem.........
when i install the SQL server 2005, it occured the follow message:Product: Microsoft SQL Server 2005 CTP -- Error 29628. The setup hasencountered an unexpected error in datastore. The action isPrepareUpgradeDialog. The error is :Failed to find property "langId"{"SetupStateScope", "", ""} in cacheNo collector registered for scope: "SetupStateScope"--Posted using the http://www.dbforumz.com interface, at author's requestArticles individually checked for conformance to usenet standardsTopic URL: http://www.dbforumz.com/General-Dis...pict248148.htmlVisit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbforumz.com/eform.php?p=859943

View Replies !   View Related
Cannot Load JDBC Driver Class 'com.microsoft.jdbc.sqlserver.SQLServerDriver'
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/"

"WebRoot/WEB-INF/web.xml":
<?xml version="1.0" encoding="UTF-8"?>
<web-app version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsichemaLocation="http://java.sun.com/xml/ns/j2ee
    http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd">
    <resource-ref>
        <res-ref-name>jdbc/DefaultDS</res-ref-name>
        <res-type>javax.sql.DataSource</res-type>
        <res-auth>Container</res-auth>
    </resource-ref>
</web-app>


"WebRoot/META-INFcontext.xml":

<?xml version="1.0" encoding="UTF-8"?>
<Context>
    <Resource name="jdbc/DefaultDS"
              auth="Container"
              type="javax.sql.DataSource"
              username="tec"
              password="tec"
              driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDrive"
              url="jdbcqlserver://localhost:1433/tec;databaseName=tec;user=tec;password=test;"
              validationQuery="select 1"
              maxActive="10"
              maxIdle="2"/>
</Context>

Classpath:
<?xml version="1.0" encoding="UTF-8"?>
<classpath>
    <classpathentry kind="src" path="src"/>
    <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
    <classpathentry kind="con" path="com.genuitec.eclipse.j2eedt.core.J2EE14_CONTAINER"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/dom.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/jaxen-full.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/jaxp-api.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/jdbc2_0-stdext.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/sqljdbc.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/jstl.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/mail.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/sax.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/saxpath.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/standard.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/xalan.jar"/>
    <classpathentry kind="lib" path="WebRoot/WEB-INF/lib/xercesImpl.jar"/>
    <classpathentry kind="output" path="WebRoot/WEB-INF/classes"/>
</classpath>

Code to connect:

import java.io.Serializable;
import java.sql.*;

import javax.sql.*;
import javax.naming.*;
    public int testConnect(){
        Connection conn = null;
        InitialContext ctx = null;
        java.sql.Statement stmt = null;

        try {
            ctx = new InitialContext();
            Context envCtx = (Context) ctx.lookup("java:comp/env");
            DataSource ds = (DataSource) envCtx.lookup("jdbc/DefaultDS");/*This is generating the Cannot load JDBC driver class... error*/
            conn = ds.getConnection();
            stmt = conn.createStatement();
            return CONSTANT.SUCCESS;   

    } catch (Exception e) {
        return CONSTANT.FAILURE;
    }finally {
        try {
            if (stmt != null)
        stmt.close();
            if (conn != null)
        conn.close();
            if (ctx != null)
        ctx.close();
        } catch (Exception ex) {
            // do nothing
            return CONSTANT.FAILURE;
        }
    }
    }

Any ideas would be greatly appreciated.

View Replies !   View Related
Cannot Install Microsoft SQL Server 2005 Express Edition X86
I recently (yesterday) installed a fresh copy of Windows XP with Service Pack 2 applied.

I proceeded with Visual Studio 2005 Express Editions installation straight away.

But I cannot install Microsoft SQL Server 2005 Express Edition x86.

I choose to install Microsoft SQL Server 2005 Express Edition x86 component along with every component of visual studio but it simply would not install.

In the end, after the installation of each complete is complete, I simply get an error message saying that Microsoft SQL Server 2005 Express Edition x86 failed to install.

What is the problem?

View Replies !   View Related
Microsoft SQL Server 2005 Setup Was Unable To Install On Your Computer
Hi,

I'have this error during install of Microsoft SQL Server 2005 Express Edition (x86). I'm Using Windows XP Professional with SP2 Build 2600. Does anyone knows how to solve this?


****

Microsoft SQL Server 2005 Setup was unable to install on your computer.

EventType : sql90setup     P1 : unknown     P2 : 0x659     P3 : unknown    
P4 : 0x659     P5 : unknown     P6 : unknown     P7 : msxml6.msi@6.10.1129.0

C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab

View Replies !   View Related
Microsoft SQL Server 2005 Cannot Install On Vista, Problem With 'sa' Login
Hi
 
I have just installed Vista on my computer and now has problems with installing: Microsoft sql server 2005. In the last part during the installation the following error occurs:
 
"SQL Server Setup could not connect to database service for server configuration..... Login failed for user 'sa'....,"
 
What is wrong? Why cant I install? Thank you for your help.
 
Here are more details from log:
 
SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections
Service MSSQL$SQLEXPRESS started at Sun Feb 03 09:01:52 2008
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
        Error Code: 0x80074818 (18456)
Windows Error Text:   Source File Name: libodbc_connection.cpp
Compiler Timestamp: Wed Jun 14 16:28:15 2006
     Function Name: OdbcConnection::connect@connect
Source Line Number: 148
 
---- Context -----------------------------------------------

Connecting to SQL Server
ExecuteSqlCommands
Originial error was 80074818 (18456)
ipt
SqlScriptHlpr
 
Error Code: 18456
MSI (s) (04!E8) [09:02:52:245]: Product: Microsoft SQL Server 2005 Express Edition -- Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<Func Name='GetCAContext'>
<EndFunc Name='GetCAContext' Return='T' GetLastError='203'>
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Sun Feb 03 09:02:52 2008
Service MSSQL$SQLEXPRESS with parameters '-m SqlSetup -Q -qDanish_Norwegian_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Sun Feb 03 09:02:52 2008
Attempt to start service when it is already running
SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections
Service MSSQL$SQLEXPRESS started at Sun Feb 03 09:02:52 2008
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=28000, level=-1, state=-1, native_error=18456, msg=[Microsoft][SQL Native Client][SQL Server]Login failed for user 'sa'.
        Error Code: 0x80074818 (18456)
Windows Error Text:   Source File Name: libodbc_connection.cpp
Compiler Timestamp: Wed Jun 14 16:28:15 2006
     Function Name: OdbcConnection::connect@connect
Source Line Number: 148
 
 
 
 
 
 
 
 

View Replies !   View Related
Microsoft SQL Server 2005 Service Pack 1 (KB 913090) Cluster Install
I have the initial MSSQL 2005 install on a two-node cluster in place with no production db's moved over, basically prepping it for sp_attach further down the road. I proceeded with applying SP1 on the primary node. I moved the cluster over to the secondary node and checked for any critical windows updates and it reported back that the SQL 2005 SP1 was still required. According to what I have read online the SP1 update on the primary node would have been applied to all nodes.

Is this a false report? What harm if any would be if I applied SQL 2005 SP1 again on the secondary node.

TIA.

Mark

 

 

View Replies !   View Related
Jdbc Driver Error For Mssqlserver. Need Urgent Help!
im stuck and despirately need help. my jdbc driver for mssql server 2000 (dont laugh).

here's the code:


Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
Connection con = DriverManager.getConnection("jdbc:microsoftqlserver://user:1433");


and here's the exception it throws at me:

Exception in thread "main" java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
at com.microsoft.jdbc.base.BaseExceptions.createException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.base.BaseExceptions.getException(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSConnection.<init>(Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.getNewImplConnection(Unknown Source)
at com.microsoft.jdbc.base.BaseConnection.open(Unknown Source)
at com.microsoft.jdbc.base.BaseDriver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(DriverManager.java:582)
at java.sql.DriverManager.getConnection(DriverManager.java:207)
at jdbctest.NewClass.main(NewClass.java:29)


i know this is a very common question for a thread, but u gotta pls answer me.

View Replies !   View Related
&&"Visual Studio 2005 Command Prompt&&" Missing From SQL Server 2005 Express Toolkit Install
The program shortcut "Visual Studio 2005 Command Prompt" seems to be mising from the "Visual Studio 2005 Command Prompt" Start menu added by the current Microsoft SQL Server 2005 Express Edition Toolkit.  Where is it?  How to workaround?

I am trying to do Download details SQL Server 2005 Samples and Sample Databases (April 2006) ->   GettingStartedWithSQLSamples.htm which says "a. Open a Microsoft Visual Studio 2005 command prompt. Click Start, point to All Programs, point to Microsoft Visual Studio 2005, point to Visual Studio Tools, and then click Visual Studio 2005 Command Prompt." but I can find no such command prompt within "Visual Studio Tools", only "Visual Studio 2005 Remote Debugger{, Configuration Wizard}".

What's wrong?  How to fix or workaround?  I'd install .NET SDK 2.0 to get it's Command Prompt but that's about 570MB merely for a command prompt!

Thanks for your help,  -Mike Parker

View Replies !   View Related
Looking For The Definitive Answer: Microsoft SQL Server 2005 Express Edition X86 Install Failed
I installed, uninstalled, deleted, editted my registry etc and I finally goto to this error while trying to install VS2005 (released) on a Windows 2000 PC (that had Beta2 and RC1 installed & uninstalled):

View Replies !   View Related
Setup Failed To Install Required Microsoft SQL Server 2005 Express (MSSMLBIZ)
I have tried to install Outlook 2007 with BCM and recieve the error listed above.  I have also included a copy of my log file.  Any suggestions?
 
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version      : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time            : Thu Aug 23 14:22:59 2007
 
Machine         : MACBOOK
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install         : Successful
Log File        : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine         : MACBOOK
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install         : Successful
Log File        : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine         : MACBOOK
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install         : Successful
Log File        : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine         : MACBOOK
Product         : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install         : Failed
Log File        : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_MSXML6_1.log
Error Number    : 1603
--------------------------------------------------------------------------------
 SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.

Time            : Thu Aug 23 14:23:45 2007

List of log files:
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Core(Local).log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLSupport_1.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLNCLI_1.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SqlWriter_1.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_MSXML6_1.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Datastore.xml
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_.NET Framework 2.0.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SNAC.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Core.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Support.log
 C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SCC.log

View Replies !   View Related
Setup Failed To Install The Required Component Microsoft SQL Server 2005 Express (MSSMLBIZ)
I Don't understand what this means: Everytime I try and install the disc 2 of my Office Small Business 2007, it gives the same message.  Help.

 


Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version      : Home Edition  (Build 6000)
Time            : Tue Jul 03 17:14:45 2007
 
Machine         : SWANNER-PC
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install         : Failed
Log File        : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLSupport_1.log
Error Number    : 1618
--------------------------------------------------------------------------------
Machine         : SWANNER-PC
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install         : Failed
Log File        : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLNCLI_1.log
Error Number    : 1618
--------------------------------------------------------------------------------
Machine         : SWANNER-PC
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install         : Failed
Log File        : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SqlWriter_1.log
Error Number    : 1618
--------------------------------------------------------------------------------

 SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.


Time            : Tue Jul 03 17:15:12 2007


List of log files:
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Core(Patched).log
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLSupport_1.log
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLNCLI_1.log
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SqlWriter_1.log
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Datastore.xml
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_.NET Framework 2.0.log
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Support.log
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Core.log
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
 c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SCC.log

View Replies !   View Related
Error When Trying To Install Microsoft SQL Server 2005 Express Edition Service Pack 2 (KB 921896)
I am running Windows 2003 Server with SP1.  Our windows update server pushed and attempted to install kb921896.  It failed and Now the SQL Service will not start.  The service is using the Network Service as the log on account and will  not log on. If I change the log on account to an application account that has admin rights on the box I am able to start the service.  However, if I try to install the update again using the app account the account gets locked out and i get the following errors:

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17058
User:  N/A
Computer: 
Description:
initerrlog: Could not open error log file 'C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOGERRORLOG'. Operating system error = 5(Access is denied.).

 

Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17053
Description:
UpdateUptimeRegKey: Operating system error 5(Access is denied.) encountered.

The ntauthority/networkservice was initially running the sql service but now i cannot change it back becuase of an apparent password issue.  The sql instance is default name. What convention would be used for the default password?

 

Please help.

         ..     
..     

View Replies !   View Related
Microsoft SQL Server Connections Using JDBC
Logging in via JDBC

Hello,

I have installed SQL Server and can now successfully access it using

osql -U aberglas2
password:
1> Select * from ajbtable
2> go
etc.

However, when I try to use the the JDBC driver I get

[java] java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Login failed for user 'aberlgas2'.

I use the following config
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver:);

java.sql.DriverManager.getConnection("jdbc:microsoft:sqlserver://localhost:1433", "aberlgas2", "XXX");

Any ideas most welcome. This is very frustrating.

I seem to be able to connect to the server OK, because if I change the port number to something meaningless I get
[java] java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.

Anyway to step through the process and find out more about the problem?

-----------

Before achieving the above error, I was getting "Not associated with a trusted SQL Server connection".

After much stuffing arround I discoverd that you have to go into the
"Enterprise Manager", and change the properties on the thing under
Server Group to Security | SQL Server and Windows, otherwise User "SQL
Server Authentication" will not be enabled. It is not enough to enable this under Security | Logins, you have to enable "SQL Server" authentication on the entire server as well.

Microsoft products are a bit too easy to use for me.

View Replies !   View Related
MSSqlserver Missing
I installed SQL server 2005 on a win2003 server box.

When I open the Connect to Server dialog box, I choose server type: Database Engine. There is no Servername listed, so I put in the name of the PC.

I get a long error message when I try to connect:

Cannot connect to PCName....
...error: 40 - Could not open a connection to SQL Server)...

When I try to go into the Surface area Configuration, I get this message:
"No sql server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSAC)"

I am logged in as Administrator in the PC, so did I do something seriously wrong with the installation?

In the services window, I can not fine MSSQLserver (not sure if this is relevant).

regards,
Jozi68

View Replies !   View Related
JDBC Driver For Microsoft SQL Server CE / Compact Edition
Hi,

I have a J2EE based web application. There is a requirement where user triggers a process to query a database, and the application needs to save the results to an SDF file (Microsoft SQL Server CE 2.0 / Microsoft SQL Server Compact Edition) database. I need JDBC driver for it, but could not find it anywhere. Please help. Also, if there is any alternate way to do this, please let me know.

Thanks,
Vaibhav

View Replies !   View Related
MSSQLServer Logging Many Missing Stored Procedure Messages
Hello,  I am getting many of these messages in my server's event log (approximately 13 every 5 seconds or so).  I have tried clearing the queue with "END CONVERSATION @ConvHandle WITH CLEANUP;" but the event log keeps getting messages.  I have attached an example below.

Type:    Information
Event Source:    MSSQLSERVER
Event Category:    (2)
Event ID:    9724
Date:        7/10/2007
Time:        3:52:37 PM
Description:
The activated proc [dbo].[SqlQueryNotificationStoredProcedure-32e779eb-edcb-44d1-ba30-93f46ef9d9f8] running on queue HoudiniPlatform.dbo.SqlQueryNotificationService-32e779eb-edcb-44d1-ba30-93f46ef9d9f8 output the following:  'Could not find stored procedure 'dbo.SqlQueryNotificationStoredProcedure-32e779eb-edcb-44d1-ba30-93f46ef9d9f8'.'

View Replies !   View Related
Unable To Install SP2 For SQL 2005 - Missing SqlSupport.msi
I have seen a few postings in regards to this so I know it has to be a known problem.  I haven't seen a solid solution posted yet.  Is there an answer to getting this SP2 installed for those of us that are missing the SqlSupport.msi file.  Below is the log from the failed install that details the problem I have.

=== Verbose logging started: 02/26/2007  20:09:34  Build type: SHIP UNICODE 3.01.4000.2435  Calling process: c:ff90771f64dd6f8ce34ad219f3114010hotfix.exe ===
MSI (c) (B4:08) [20:09:34:531]: Resetting cached policy values
MSI (c) (B4:08) [20:09:34:531]: Machine policy value 'Debug' is 0
MSI (c) (B4:08) [20:09:34:531]: ******* RunEngine:
           ******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (B4:08) [20:09:34:531]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (B4:08) [20:09:34:531]: Grabbed execution mutex.
MSI (c) (B4:08) [20:09:34:546]: Cloaking enabled.
MSI (c) (B4:08) [20:09:34:546]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (B4:08) [20:09:34:546]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C0:94) [20:09:34:562]: Grabbed execution mutex.
MSI (s) (C0:E0) [20:09:34:562]: Resetting cached policy values
MSI (s) (C0:E0) [20:09:34:562]: Machine policy value 'Debug' is 0
MSI (s) (C0:E0) [20:09:34:562]: ******* RunEngine:
           ******* Product: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (C0:E0) [20:09:34:562]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (C0:E0) [20:09:34:593]: File will have security applied from OpCode.
MSI (s) (C0:E0) [20:09:34:656]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi' against software restriction policy
MSI (s) (C0:E0) [20:09:34:656]: SOFTWARE RESTRICTION POLICY: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi has a digital signature
MSI (s) (C0:E0) [20:09:35:906]: SOFTWARE RESTRICTION POLICY: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (C0:E0) [20:09:35:906]: End dialog not enabled
MSI (s) (C0:E0) [20:09:35:906]: Original package ==> C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
MSI (s) (C0:E0) [20:09:35:906]: Package we're running from ==> C:WINDOWSInstaller380cff.msi
MSI (s) (C0:E0) [20:09:35:906]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (C0:E0) [20:09:35:906]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C0:E0) [20:09:35:906]: MSCOREE not loaded loading copy from system32
MSI (s) (C0:E0) [20:09:35:906]: Couldn't find local patch ''. Looking for it at its source.
MSI (s) (C0:E0) [20:09:35:906]: Resolving Patch source.
MSI (s) (C0:E0) [20:09:35:906]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C0:E0) [20:09:35:906]: User policy value 'DisableMedia' is 0
MSI (s) (C0:E0) [20:09:35:906]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (C0:E0) [20:09:35:906]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (C0:E0) [20:09:35:906]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (C0:E0) [20:09:35:906]: Note: 1: 1706 2: {EE92F683-5F5C-4970-BB0B-9AC591B60268} 3: 
MSI (s) (C0:E0) [20:09:35:906]: SOURCEMGMT: Failed to resolve source
MSI (s) (C0:E0) [20:09:35:921]: Note: 1: 1708
MSI (s) (C0:E0) [20:09:35:921]: Note: 1: 2729
MSI (s) (C0:E0) [20:09:35:921]: Note: 1: 2729
MSI (s) (C0:E0) [20:09:35:921]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.

MSI (s) (C0:E0) [20:09:35:937]: MainEngineThread is returning 1612
The installation source for this product is not available.  Verify that the source exists and that you can access it.
C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
MSI (c) (B4:08) [20:09:36:046]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1
MSI (c) (B4:08) [20:09:36:046]: MainEngineThread is returning 1612
=== Verbose logging stopped: 02/26/2007  20:09:36 ===

I look forward to hearing from anyone with a solution.  Thanks.

Barry

View Replies !   View Related
How Can I Connect To Microsoft SQL Server 2005 CTP With Microsoft SQL Server 2005 Express Manager?
I installed Microsoft SQL Server 2005 Express Manager and connect to SQL 2000 normally

View Replies !   View Related
New SQL Server Install Missing Services
I have a recent installation of SQL Server 2005 running on a client location.  All the requisite services for SQL appear in the Windows Services screen, but not in SQL Server Configuration Manager.  I need to change the ownership of the services, but obviously can't because they are not in the Config. Manager.  Does anyone have any idea as to how this could happen and how I might get them loaded.  Any and all assistance is appreciated.

 

Thanks

View Replies !   View Related
Microsoft.AnalysisServices.Viewers.DLL Microsoft SQL Server 2005 Datamining Viewer Controls
 

 

Hi

I am trying to use Association Viewer Control in

Microsoft.AnalysisServices.Viewers.DLL dll in VS 2005 but sometimes it gives an error.

"Code generatio for property 'ConnecitonManager'" failed. Error was:'Property accesor 'ConnectionManager' on object 'AssosiactionViewer1' threw the following exception:'Object referance not set to instance of an object"


Is there anyone here who use
"Microsoft SQL Server 2005 Datamining Viewer Controls" in SQLServer2005 FeaturePack ?
http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en

i am using VS2005 Version 8.0.50727.762 (SP.050727-7600)
and SQL Server 2005 SP2

thanks from now.

Cem Ãœney

 

 

 

 

View Replies !   View Related
JDBC Query Running Indefinitely (Connection Missing)
We see an unusual case where a query seems to be taking a long time (more than 30 minutes) as shown by the Java thread dump (below) - however the SQL server DB does'nt show any corresponding Connection for the query at the lower layer.

 

The JDBC layer seems to be "in progress" as far as processing the results of the query are concerned. If the Connection was dropped or had a failure we should have seen a corresponding SQLException in the JDBC layer - which is also not the case.

 

Any tips on how to debug this? Is there a timeout set on the JDBC Connection which causes it to wait before it detects any failures?

 

thanks

 

 

"JMS Session Delivery Thread" daemon prio=6 tid=0x0000000006434780 nid=0x868 run
nable [0x0000000020d6e000..0x0000000020d6f860]
        at java.net.SocketInputStream.socketRead0(Native Method)
        at java.net.SocketInputStream.read(SocketInputStream.java:129)
        at com.microsoft.sqlserver.jdbc.DBComms.receive(Unknown Source)
        at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePrep
aredStatement(Unknown Source)
        at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PreparedState
mentExecutionRequest.executeStatement(Unknown Source)
        at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source
)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unkno
wn Source)
        - locked <0x00000000955574e0> (a com.microsoft.sqlserver.jdbc.TDSWriter)

        at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate
(Unknown Source)
        at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Del
egatingPreparedStatement.java:101)
        at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(Del
egatingPreparedStatement.java:101)
        at org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeInsert(JdbcAc
cessImpl.java:213)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(Persistenc
eBrokerImpl.java:2021)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro
kerImpl.java:977)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro
kerImpl.java:1014)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro
kerImpl.java:884)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeAndLinkOneToOne
(PersistenceBrokerImpl.java:1074)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeReferences(Pers
istenceBrokerImpl.java:1050)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(Persistenc
eBrokerImpl.java:1981)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro
kerImpl.java:977)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro
kerImpl.java:1014)
        at org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBro
kerImpl.java:884)
        at org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(Delegati
ngPersistenceBroker.java:220)
        at org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(Delegati
ngPersistenceBroker.java:220)
        at org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(Delegati
ngPersistenceBroker.java:220)
        at com.serus.db.ojbutils.SerusPersistenceBrokerHandle.store(SerusPersist
enceBrokerHandle.java:178)
        at com.serus.common.OJBDAOUtil.store(OJBDAOUtil.java:636)
        at com.serus.dao.wip.AbsWipDAO.saveDTO(AbsWipDAO.java:251)
        at com.serus.dao.wip.tx.LotTXDAO.saveLotTx(LotTXDAO.java:56)
        at com.serus.manager.wip.txprocessing.AbstractTxProcessorImp.storeLotTx(
AbstractTxProcessorImp.java:1380)
        at com.serus.manager.wip.txprocessing.LotTxProcessingMoveStage.storeLotT
x(LotTxProcessingMoveStage.java:802)
        at com.serus.manager.wip.tx.LotTxManager.saveLotTx(LotTxManager.java:248
)
        at com.serus.manager.wip.tx.LotTxXMLProcessor.parseMessageOriginal(LotTx
XMLProcessor.java:137)
        at com.serus.manager.wip.tx.LotTxXMLProcessor.parseMessage(LotTxXMLProce
ssor.java:78)
        at com.serus.events.listener.SerusJMSListener.onSerusMessage(SerusJMSLis
tener.java:197)
        at com.serus.events.listener.AbstractEventListener.onMessage(AbstractEve
ntListener.java:53)
        at progress.message.jimpl.Session.deliver(Unknown Source)
        at progress.message.jimpl.Session.run(Unknown Source)
        at progress.message.jimpl.Session$SessionThread.run(Unknown Source)

View Replies !   View Related
CLOB && BLOB With Microsoft JDBC Driver ?
The microsoft JDBC driver doesn't accept CLOB & BLOB field.
Does anyone know about this problem ?
Is it possible to found another driver that works correctly and that is free ?

Thank's

View Replies !   View Related
Com.microsoft.sqlserver.jdbc.SQLServerConnection Exception
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


thanks in advance
Nirav
 

View Replies !   View Related
JDBC Datasource In Microsoft Visual Studio
How do you define a JDBC datasource in Microsoft Visual Studio?  I am using Microsoft Visual Studio to develop reports for SSRS and would like to connect to DB2 via JDBC.  Attempting to use the SQL JDBC install as a example, I don't see how to define the SQL JDBC driver to Visual Studio.  The SQL JDBC runtime install is very clear, but I don't see how to use this type of datasource in Visual Studio.
 
Thanks!

View Replies !   View Related
Microsoft JDBC Driver - TDS Prelogin Error (?)
 

Hi,
 
Anyone know what I'm doing wrong? My JDBC is erroring. I'm using the Microsoft 1.2 driver, I have a SQL Server 2005 back end with the following clients connecting to it:
 

ASP.NET 2.0 web application
Visual Studio C# console applications (*2)
Java command line client.
 
 

Everything runs hunky-dory on my dev. environment (laptop, local, launched via Visual Studio) but now it's on the server, the Java client is erroring.
 
When I use the 1.2 sqljdbc.jar file, I get:
 

25-Jan-2008 12:20:29 com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING:  ConnectionID:1 TransactionID:0x0000000000000000 Prelogin response packet not marked as a REPLY

My Error Trap:
--------------
SQL STATE : 08S01
ERROR CODE: 0
MESSAGE   : The TDS protocol stream is not valid.
 
When I use the 1.1 file I get:
 

My Error Trap:
--------------
SQL STATE : 08S01
ERROR CODE: 0
MESSAGE   : The TDS prelogin response is incomplete. The target server must be SQL Server 2000 or later.
 
I don't know what these errors mean. I've tried compiling as java 1.5 and 1.6 with the same results. It works fine on my laptop (Vista Home Premium) but won't when I try and connect to the server. I've searched the web on the error messages and can't find an answer yet.
 
Any help appreciated.
 
My drivers are the Windows versions. Also, everything else is working okay on the server: The consoles are up and running and the web browser connects and SELECTs, UPDATEs & INSERTs okay.
I ought to mention: My laptop is running SQL Server Development edition and the Server is running obviously something else.

 
My SQL Server version is 9.0.1399 and the OS is Windows Server 2003. SQL Authentication is mixed mode.

View Replies !   View Related
Com.microsoft.sqlserver.jdbc.SQLServerConnection LoginWithFailover
Hi all

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

------

Connect string:

java -classpath /conf/javasql/sqljdbc_1.1/enu/sqljdbc.jar:/conf/javasql/jisql/lib/jisql.jar com.xigole.util
.sql.Jisql -user SOMEUSER -password SOMEPASSWORD -driver com.microsoft.sqlserver.jdbc.SQLServerDriver -input $QUERYFILE -cstring jdbc:sqlserver://SERVER1;DataBaseName=TESTDATABASE;failoverPartner=SERVER2;loginTimeout=3

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.

Has anyone got any suggestions?

 

Thanks

View Replies !   View Related
Unable To Install SQL Server 2K5 Express From Microsoft Update
Windows Update gave a 0X65B error when installing SQL Server 2K5 Express SP2. The solution said to copy the summary.txt data below to this forum:

 

Time: 05/08/2007 11:06:22.102
KB Number: KB921896
Machine: WA10015USG93127
OS Version: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Package Language: 1033 (ENU)
Package Platform: x86
Package SP Level: 2
Package Version: 3042
Command-line parameters specified:
     /quiet
     /allinstances
Cluster Installation: No

**********************************************************************************
Prerequisites Check & Status
SQLSupport: Passed

**********************************************************************************
Products Detected                         Language  Level  Patch Level       Platform  Edition
Express Database Services (SQLEXPRESS)    ENU       SP1    2005.090.2047.00  x86       EXPRESS
Express Database Services (SQLExpress)    ENU       SP2                     x86       EXPRESS

**********************************************************************************
Products Disqualified & Reason
Product                                   Reason

**********************************************************************************
Processes Locking Files
Process Name          Feature               Type          User Name                  PID

**********************************************************************************
Product Installation Status
Product                   : Express Database Services (SQLEXPRESS)
Product Version (Previous): 2047
Product Version (Final)   :
Status                    : Failure
Log File                  : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features      : SQL_Data_Files,SQL_Engine,SQL_SharedTools
Error Number              : 1627
Error Description         : Unable to install Windows Installer MSI file
----------------------------------------------------------------------------------
Product                   : Express Database Services (SQLExpress)
Product Version (Previous):
Product Version (Final)   : 3042
Status                    : Success
Log File                  : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9Express_Hotfix_KB921896_SQLEXPR.EXE
SQL Express Features      : Client_Components,Connectivity,SDK
Error Number              : 0
Error Description         :
----------------------------------------------------------------------------------

**********************************************************************************
Summary
     One or more products failed to install, see above for details
     Exit Code Returned: 1627

 

Any help would be appreciated in getting this service pack installed.

 

Thanks,

Marty

View Replies !   View Related
Difference Between Microsoft Sql Server 2008 And Microsoft Sql Server 2005
 

Pls tell me about the adjact difference between sql server 2005 and sql server 2008.
Why to upgrade for Sql Server 2008

View Replies !   View Related
[Microsoft][SQLServer 2000 Driver For JDBC]Statement(s) Could Not Be Prepared
When we are using the Microsoft SQL Server 2000 thin driver,
we get the following error.

java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Statement(s) could not be prepared.
at com.microsoft.jdbc.base.BaseExceptions.createExcep tion(Unknown Source
)
at com.microsoft.jdbc.base.BaseExceptions.getExceptio n(Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sErrorToken(Unknown
Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.proces sReplyToken(Unknown
Source)
at com.microsoft.jdbc.sqlserver.tds.TDSExecuteRequest .processReplyToken(
Unknown Source)
at com.microsoft.jdbc.sqlserver.tds.TDSRequest.getRow (Unknown Source)
at com.microsoft.jdbc.sqlserver.SQLServerImplResultSe t.positionCursor(Un
known Source)
at com.microsoft.jdbc.base.BaseResultSet.next(Unknown Source)
at DBConnection.main(DBConnection.java:56)


The Query due to which this error was occuring is given below.

SELECT CP_CD,COMPANY_NAME_J,COUNTRY_NAME_J,CP_NAME,CP_NAM E_J, (CASE RESIDENT WHEN 'Y' THEN '‹??Z' WHEN 'N' THEN '”ñ‹??Z' END ), (CASE BANK WHEN 'Y' THEN '‹â?s?i‹à—Z‹@ŠÖ?j' WHEN 'N' THEN '‚»‚Ì‘¼' END ), (CASE RISK_BCD WHEN '1' THEN '‹â?s' WHEN '2' THEN '?ØŒ”' WHEN '3' THEN '?¶•Û?E‘¹•Û' WHEN '4' THEN 'Ž–‹Æ–@?l' WHEN '5' THEN 'ŠO?‘?_•{' WHEN '0' THEN '‚»‚Ì‘¼' END ), (CASE RISK_ACD WHEN '1' THEN '’†‰›?_•{‚¨‚æ‚Ñ’†‰›‹â?s' WHEN '2' THEN 'Ž©?s—a‹à“™’S•Û' WHEN '3' THEN '?‘?Â’S•Û' WHEN '4' THEN '?‘?ÛŠJ”_‹â?s' WHEN '5' THEN '–¢Žg—p' WHEN '6' THEN '–{–MŒö‹¤•”–å' WHEN '7' THEN '–{–M‹â?s‹y‚Ñ–{–M?ØŒ”‰ïŽÐ'WHEN '8' THEN 'OECD?”?‘‹â?s‹y‚ÑOECD?”?‘?ØŒ”‰ïŽÐ?A‚Ü‚½‚Í‚»‚Ì‘¼‚Ì‹ â?s‚Ì’ZŠú?–±' WHEN '9' THEN 'OECD?”?‘‹â?sˆÈŠO‚Ì‹â?s‚Ì’·Šú?–±' WHEN '11' THEN '’n•ûŒö‹¤’c‘Ì' WHEN '10' THEN '‚»‚Ì‘¼' END ) , (CASE RISK_CLASS WHEN '1' THEN '–{–M' WHEN '2' THEN 'OECD?”?‘' WHEN '0' THEN '‚»‚Ì‘¼' END ), (CASE SUBSIDIARY WHEN '1' THEN 'Œ»’n–@?l' WHEN '2' THEN 'ŠCŠO“X' WHEN '0' THEN '‚»‚Ì‘¼' END )FROM CP LEFT OUTER JOIN COUNTRY ON CP.COUNTRY_CD = COUNTRY.COUNTRY_CD LEFT OUTER JOIN COMPANY ON CP.COMPANY_CD = COMPANY.COMPANY_CD ORDER BY CP_CD ASC

Note :
====

The Same Query when run in SQL Server 2000 Query Analyser is working fine and also in ORACLE 9i.

Please tell us where is the problem ?

View Replies !   View Related
Com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP Connection To The Host Has Failed.
I am trying to connect to SQL Server 2005 Express with JDBC.   I am getting the following exception:


Code SnippetString connectionUrl = "jdbc:sqlserver://localhost:1433;" +
            "databaseName=IFC3;";
        // Declare the JDBC objects.
        Connection con = null;
        Statement stmt = null;
        ResultSet rs = null;
       
            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


Any suggestions?
Thanks,
Tom

View Replies !   View Related
Sending NULL To Stored Procedure Using Microsoft JDBC Driver 1.1
I am unable to send null values through the Microsoft JDBC 1.1 driver to a stored procedure.  Please look at the thread already started on the SQL Server Transact SQL Forum at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1772215&SiteID=1

View Replies !   View Related
Java.lang.ClassNotFoundException: Com.microsoft.sqlserver.jdbc.SQLServerException
Hallo,

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 ?

Thanks a lot, best regards,

Florian Brunswicker

View Replies !   View Related
Microsoft Visual Studio Is Unable To Load This Document After SQL Server SP2 Install.
Hello all,
 
Over the weekend, I loaded the SQL Server SP2 on to my production database after having it on my dev server for two weeks with out any problems.
 
After I did this, I went to check all my SSIS packages and found them not able to load.
I get this message €œMicrosoft Visual Studio is unable to load this document: The package failed to load due to error 0xC0010014 €œOne or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors€?. This occurs when CPackage::LoadFromXML fails.
 
Now when I look at the errors I see:


Error    1          Error loading Master_Full_Weekly.dtsx: Error loading value "<DTS:LogProvider xmlns  : DTS="www.microsoft.com/SqlServer/Dts" > <DTS : Property DTS:Name="ConfigString">SQL_TPMTSH_Datamart</DTS: Property><DTS : Property DTS:Name="DelayValidation">0</DTS: Property><DTS: Property DTS:Name="ObjectName">DTS Log Provider for SQL Serve" from node "DTS: LogProvider".      D:ETLProjectsTPMTPMTSHMaster_Full_Weekly.dtsx      1          1


 Does anyone know what this is about and how I can go about fixing it?

View Replies !   View Related
2000 JDBC Vs 2005 JDBC
 

I've got an import app written in Java.  One table I'm importing from contains 22 million records.  When I run the app in a 2000 environment, I have my max heap set at 512, and the table gets imported.  When I run in a 2005 environment, I have to change the max heap to 1152 or it will error out with a similiar error:
 
com.microsoft.sqlserver.jdbc.SQLServerException: The system is out of memory. Use server side cursors for large result sets:Java heap space. Result set size:854,269,999. JVM total memory size:1,065,484,288. (<--this is with max heap at 1024)
 
what is the difference between the 2000 and 2005 JDBC that I have to set max heap in one and not the other?

View Replies !   View Related
How To Retreive Data From Nvarchar(max) Column, Using Com.microsoft.sqlserver.jdbc.SQLServerDriver?
I've looked through msdn and found an example, but it doesn't work. The problem is that when i use such construction

ResultSet rs1 = stmt.executeQuery("SELECT TOP 1 * FROM sys.check_constraints");
rs1.next();
Reader reader = rs1.getCharacterStream(17);

reader is set to null,but it mustn't be null cause i see some data through management studio in 17th column of sys.check_constraints table.

View Replies !   View Related
Can't Install JDBC On OpenSUSE
When i try to execute



Code Snippet
>java -classpath /usr/java/jdk1.6.0_04/lib/sqljdbc.jar com.microsoft.sqlserver.jdbc.SQLServerDriver
 
Java throws and exeption:



Code Snippet
Exception in thread "main" java.lang.NoSuchMethodError: main
 
 





What can i do?
I'm using openSUSE on VMWare.

View Replies !   View Related
Com.microsoft.sqlserver.jdbc.SQLServerException.class Throws Java.lang.SecurityException
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

is there anything i've missed? please, help me..

View Replies !   View Related
SQL Server 2005 JDBC Driver
Hi

 

Do we have to use SQL server 2005 JDBC driver to connect the sql server 2005? I got  sql server 2000 driver for JDBC, it works fine to connect the database. But when I use sql server migration assistant for oracle, i got an error saying: [sql server 2000 driver for JDBC] Error establishing socket. Do I have to download SQL server 2005 driver for JDBC or I miss something else?

 

Thanks

 

Li

View Replies !   View Related

Copyright © 2005-08 www.BigResource.com, All rights reserved