SQL Server 2005 JDBC Connection Woes.....
Feb 5, 2008
I'd recently upgraded SQL Server2000 to SQL server2005. I've been using Tibco DX to connect to the database. While working with SQL Server2000 things were going fine. I could access the databases from the repository through TibcoDX and could deploy my tasks which involved migrating data from source to target databases.
But when I had installed SQL server 2005 an error cropped up while deploying tasks
Exception occurred while initializing the JDBCTransformer: The TCP/IP connection to the host has failed. java.net.UnknownHostException:
I'd checked the port numbers and they were matching, the TCP protocols were also enabled. But I'm not able to fix this problem. Any help would be highly appreciated. Thank You.
View 6 Replies
ADVERTISEMENT
Oct 12, 2007
Dear All,
Using JDBC trying to connect MS SQL server 2005. Getting the following error:
org.apache.commons.dbcp.DbcpException: java.sql.SQLException: Network error IOException: Connection refused: connect
java.sql.SQLException: Network error IOException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
org.apache.commons.dbcp.DbcpException: java.sql.SQLException: Network error IOException: Connection refused: connect
java.sql.SQLException: Network error IOException: Connection refused: connect
java.net.ConnectException: Connection refused: connect
Here is the TCP/IP setting in our SQL server 2005:
I disable the Windows 2003 R2 firewall, but that didn’t help.
In SQL server 2005 for Remote connections:
Enabled “Local and Remote connections: Using both TCP/IP and Named Pipes
In TCP/IP Prosperities:
IP Addresses:
IP1: Active: Yes
Enabled: Yes
IP address: the server IP address Example 192.168.0.1
TCP Dynamic port: 0
TCP Port: 1433
///
IP2: Active: Yes
Enabled: Yes
IP address: the server IP address Example 192.168.0.1
TCP Dynamic port: 0
TCP Port: 1433
////
IP3: Active: Yes
Enabled: Yes
IP address: the server IP address Example 192.168.0.1
TCP Dynamic port: 0
TCP Port:
///
IP4: Active: Yes
TCP Dynamic ports: 1053
TCP Port:
For Protocols:
Under general:
Enable: Yes
Keep Alive: 30000
Listen ALL: Yes
No Delay: No
I think that should be enough info to start with.
Please advice.
Thanks for any help.
Abrahim
View 1 Replies
View Related
Mar 28, 2007
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 1 Replies
View Related
Jul 10, 2007
When using jdbc with IntegratedSecurity, I run into this problem when the machine is not part of a domain & gets its IP address via dhcp. Is this expected behavior or a bug in the jdbc driver.
The SQLServer and client application are installed on the same machine and a local admin is logged in, running the client app.
If I change one of the two parameters mentioned above, the connection can be established leading me to believe this may be intentional for security issues. Am I correct?
View 6 Replies
View Related
Jun 15, 2006
I am having problems installing SP1 successfully. So far I've tried it on two separate Windows 2003 server boxes running SQL Server 2005 Standard v9.0.1399.
The first upgraded successfully all over services except the SQL server itself. Reporting services then failed due to database version mismatch but that was easily fixed. The other box doesn't have anything other than SQL2005 and components were upgraded but the database upgrade failed. I got the generic "send this error to microsoft" message.
I've tried other suggested fixes on this board but none have worked so far.
The Logfile seems to go haywire at about this point:
Property(S): REINSTALLMODE = omus
Property(S): Privileged = 1
Property(S): RedirectedDllSupport = 2
Property(S): REINSTALL = All
Property(S): PATCH = \TESTC$SP1HotFixSQLFilessqlrun_sql.msp
Property(S): MsiWin32AssemblySupport = 5.2.3790.1830
Property(S): MsiNetAssemblySupport = 2.0.50727.42
Property(S): Date = 6/15/2006
Property(S): ProductToBeRegistered = 1
Property(S): Time = 13:52:47
Property(S): ProductState = 5
Property(S): TTCSupport = 1
Property(S): TRANSFORMS = :SqlRun01.mst;:InstID01.mst;:InstName01.mst
Property(S): ColorBits = 32
Property(S): TextHeight = 16
Property(S): PackageCode = {3185FC73-41E0-43F4-97DF-2254C4D7C667}
Property(S): BorderSide = 1
Property(S): BorderTop = 1
Property(S): CaptionHeight = 19
Property(S): ScreenY = 1024
Property(S): ScreenX = 1280
Property(S): SystemLanguageID = 1033
Property(S): SQL200532Hotfix2047 = \TESTC$SP1HotFixSQLFilessqlrun_sql.msp
Property(S): BrowseAuto.2FC2D269_8625_4826_BB3F_F9059090CB38 = 0
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 1729
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Transforming table Error.
MSI (s) (C4:30) [13:52:47:807]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (C4:30) [13:52:47:807]: Product: Microsoft SQL Server 2005 -- Configuration failed.
MSI (s) (C4:30) [13:52:47:807]: Attempting to delete file C:WINDOWSInstaller6770f.msp
MSI (s) (C4:30) [13:52:47:807]: Unable to delete the file. LastError = 32
MSI (s) (C4:30) [13:52:47:839]: Cleaning up uninstalled install packages, if any exist
MSI (s) (C4:30) [13:52:47:839]: MainEngineThread is returning 1602
MSI (s) (C4:08) [13:52:47:839]: Destroying RemoteAPI object.
MSI (s) (C4:B0) [13:52:47:839]: Custom Action Manager thread ending.
=== Logging stopped: 6/15/2006 13:52:47 ===
MSI (c) (D4:90) [13:52:47:854]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D4:90) [13:52:47:854]: MainEngineThread is returning 1602
=== Verbose logging stopped: 6/15/2006 13:52:47 ===
Help!
View 5 Replies
View Related
Jul 10, 2006
Hi,
I am trying to install sql server express with advanced services and I can't get any further than this message:
Name: Microsoft SQL Server 2005 (SQLEXPRESS)Allowed Action: Maintain (Action is only available from Add or Remove Programs)Reason: Cannot maintain product, to maintain the product go to Add or Remove Programs
Name: Microsoft SQL Server 2005 ToolsReason: Your upgrade is blocked. For more information about upgrade support, see the "Version and Edition Upgrades" and "Hardware and Software Requirements" topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.
Edition check:Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.I have looked ay the book sonline and it got me nowhere very quickly!
Any ideas reatly appreciated! I have no other SQL products installed or express versions etc. I have VS 2005 and I want to install that next!
Thanks!
View 1 Replies
View Related
Apr 22, 2007
Hey guys, I'm creating an ASP.Net 2.0 Web app with VB in the code behind files. I've created a few reports in Business Intelligence Dev Studio that I've deployed to a Windows 2003 Server that has SQL Server 2005 & Reporting Services 2005 on it. Last night I ran into a problem as I tested code on my laptop. And after about 3 hours I have come to the conclusion that it's the way Vista authenticates or its some kind of bug.
When I go to set the report parameters I get an error about invalid credentials and get a HTTP 401 unauthorized. I googled and searched on the forums, however it didn't make sense to me why it was working before now not working. No one was signed on AIM to test to see if it was a specific computer issue, so I decided to try and code a workaround.
I set ShowCredentialsPromt to True and I never got a prompt for credentials when the parameters were attempted to be set. I just got the error. I'm not on my laptop right now, but I will include the exact verbiage of the error message.
i have read lots of posts regarding this by my question is why does the same code not work on Vista than XP? Is that the deciding factor of my issue? I'll get some friends with Vista to test out the site and see if they get the error as well. Any insight?
View 1 Replies
View Related
Apr 27, 2008
Hello,
I have installed successfully Microsoft SQL server 2005 in MSCS.
However the set up did not install Workstation components (client tools - SSMS etc).
I have successfully installed workstation components in one node of cluster.
However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed).
Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.
I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup".
It executed but no error, no output.
Any gues, help in isolating issue?
Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.)
Regards.
Mahesh
===========
Setup
1) Microsoft Cluster of two nodes.
2) Hardare - HP Blade servers
3) OS - Windows 2003 EE with SP2
4) SQL Server 2005 Standard Edition with SP2.
=============================
MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup
MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup
MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729
MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed.
MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist
MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603
MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object.
MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
View 1 Replies
View Related
Feb 8, 2004
Hi..
I want to find out the List of users created in SQL Server.
Im using type 4 Driver to Connect SQL Server.
Regards
maruthi.
View 3 Replies
View Related
May 19, 2004
Hi
I'm trying to setup a sql server 2000 connection but I'm having some trouble.
I've been reading the quickstart tutorial for server-side data access - http://samples.gotdotnet.com/quickstart/aspplus/doc/webdataaccess.aspx
But when I try to use the examples I get errors (using visual studio.net).
I've created a web form (webform1.aspx) and in the page load I'm typing this - Dim
myConnection As New SqlConnection("server=(local)NetSDK;database=pubs;Trusted_Connection=yes")
Dim myCommand As New SqlDataAdapter("select * from Authors", myConnection)
The error says "Too many arguments to public sub New()"
Any ideas?
Also, I'd like to know how to find the connection string, my database is on the same machine so it's using the local host.
Would it be better to write a connection class, if so could you point me to any examples please?
Hope you can help!
ps. Using vb.net
View 5 Replies
View Related
Apr 3, 2007
In testing new patches, I tried Windows 2003 Server SP2 and our JDBC connections stopped working. I uninstalled SP2 and they started working again. Anyone know where the problem is?
I have already read pages of documentation, but I will keep looking. Please let me know if you know the setting that needs to be changed. I'm assuming it is a new "security enhancement" but I'm just not sure exactly where.
Thanks in advance.
Hugh
View 8 Replies
View Related
Sep 16, 2015
I am using sqljdbc41.jar to connect with MSSQL database, it is working fine on my local machine.Where as on the remote server, same class giving me error
Login failed for user '<domain><windows loginID>'
My connection string is URL...
I am using sqljdbc41.jar and on 64 bit processor , I am using following command which included path for sqljdbc_auth.dll java -Djava.library.path= C: sqljdbc_4.1enuauthx64 TestDao and error is Login failed for user '<domain><windows loginID>' why it is not picking up username passed in connection string. I have 2 machines, one is local and other is remote. on both machine I login using my domain, it is working absolutely fine on local then why the error is coming on remote machine.Both the machines are identical.
View 4 Replies
View Related
Apr 18, 2008
I am having MSSQLServer2000 on Win2k and Win2k3 server.
i have to connect these servers from a application using JDBC driver and AD Authentication.
I have programmed all the things needed for AD authentication in my application(changed url , using integratedSecurity=true), and it is working fine when my application connects to MSSQLServer2k5 on WinXP(which is added to same domain of my application).
But when i try to connect MSSQL2000 server on Win2000 server it failes and gives error as follows.
Apr 18, 2008 12:39:51 PM com.microsoft.sqlserver.jdbc.AuthenticationJNI SNISecGenClientContextINFO: Failed to get the SPNcom.microsoft.sqlserver.jdbc.SQLServerException: Connection reset at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSChannel.read(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.readPacket(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSReader.readResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.startResponse(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$000(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(Unknown Source) at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source) at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(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 ChangePassword.process(ChangePassword.java:33) at ChangePassword.main(ChangePassword.java:14)
I am using following code for connection --
String url = "jdbcqlserver://172.16.1.243\dbaudit;portNumber=1034;integratedSecurity=true";
Class dbDriverClass = Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
Driver driver = (Driver) dbDriverClass.newInstance();
Properties props = new Properties();
conn=driver.connect(url, props);
View 13 Replies
View Related
Mar 12, 2008
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 3 Replies
View Related
Jan 3, 2007
Hi folks,
I'm trying to figure out if the SQL Server 2005 JDBC driver supports SSL at all. I've downloaded the driver documentation, looked at more web pages than I care to count, and even went as far as to take a stab at guessing at different driver property names in the hopes I might discover some undocumented feature. Each time I try, I come up dry.
The following exception shows up in my JBoss log:
2007-01-03 12:13:36,812 WARN [org.jboss.resource.connectionmanager.JBossManagedConnectionPool] Throwable while attempting to get a new connection: null org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.microsoft.sqlserver.jdbc.SQLServerException: The SQL Server login requires an SSL connection.)
I know I have things working properly on the SQL Server side, as both osql and Query Analyzer work fine, and packet sniffing yields no plain text information. I've also tried swapping in the open source JTDS driver, and once again, sniffing shows that the data between the two machines in encrypted.
Does anyone know if I'm just missing something completely obvious, or can someone state with absolute certainty that the driver does not support SSL? Any ideas on how to find out if there are plans to support this feature and what the timeline might be?
Thanks in advance.
Trev.
View 3 Replies
View Related
Apr 1, 2007
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 7 Replies
View Related
Jul 24, 2007
Can any version of the SQL Server 2000 JDBC driver connect to SQL Server 2005 or do I have to install the new JDBC version 1.1 to connect to my 2005 instance?
View 1 Replies
View Related
Apr 11, 2007
Hello,
I've run into a problem trying to install SP2 for SQL2005 on a Server 2003 system. I tried to troubleshoot this myself but the logs are just not verbose enough. The box was just rebuilt with Server 2003, then SP2 for 2003 was immediately applied. SQL2005 was then installed. In my attempt to install SP2 for SQL2005, the following errors occured:
Summary.txt
----------------------------------------------------------------------------------
Product : Database Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
----------------------------------------------------------------------------------
Product : Analysis Services (MSSQLSERVER)
Product Version (Previous): 1399
Product Version (Final) :
Status : Failure
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log
Error Number : 29528
Error Description : MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
----------------------------------------------------------------------------------
Hotfix.log
04/11/2007 09:26:13.317 Locked file: Checking for locked files
04/11/2007 09:26:16.692 Attempting to pause the 32 bit ngen queue
04/11/2007 09:26:16.848 Installing product: SQL9
04/11/2007 09:26:16.848 Installing instance: MSSQLSERVER
04/11/2007 09:26:16.848 Installing target: MINKE
04/11/2007 09:26:16.848 Installing file: sqlrun_sql.msp
04/11/2007 09:26:16.864 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
04/11/2007 09:26:16.864 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
04/11/2007 09:26:16.864 Registry: Cannot read registry key value "Debug"
04/11/2007 09:26:25.411 MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
04/11/2007 09:26:26.239 MSP returned 1603: A fatal error occurred during installation.
04/11/2007 09:26:26.255 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
04/11/2007 09:26:26.255 Registry: Cannot read registry key value "Debug"
04/11/2007 09:26:26.911 Copy Engine: Error, unable to install MSP file: d: a41f59141805a7af3438aHotFixSQLFilessqlrun_sql.msp
04/11/2007 09:26:26.911 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/11/2007 09:26:26.911 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 800
04/11/2007 09:26:27.286 Watson: Param1 = SetInstanceProperty
04/11/2007 09:26:27.286 Watson: Param2 = 0x7358
04/11/2007 09:26:27.286 Watson: Param3 = SetInstanceProperty
04/11/2007 09:26:27.286 Watson: Param4 = 0x7358
04/11/2007 09:26:27.286 Watson: Param5 = sqlcasqlcax.cpp@1223
04/11/2007 09:26:27.286 Watson: Param6 = Unknown
04/11/2007 09:26:27.286 Watson: Param7 = SQL9
04/11/2007 09:26:27.286 Watson: Param8 = Hotfix@
04/11/2007 09:26:27.286 Watson: Param9 = x86
04/11/2007 09:26:27.286 Watson: Param10 = 3042
04/11/2007 09:26:27.301 Installed product: SQL9
04/11/2007 09:26:27.301 Installing product: OLAP9
04/11/2007 09:26:27.301 Installing instance: MSSQLSERVER
04/11/2007 09:26:27.301 Installing target: MINKE
04/11/2007 09:26:27.317 Installing file: sqlrun_as.msp
04/11/2007 09:26:27.317 Copy Engine: Creating MSP install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixOLAP9_Hotfix_KB921896_sqlrun_as.msp.log
04/11/2007 09:26:27.317 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
04/11/2007 09:26:27.317 Registry: Cannot read registry key value "Debug"
04/11/2007 09:26:32.020 MSP Error: 29528 The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.
04/11/2007 09:26:32.552 MSP returned 1603: A fatal error occurred during installation.
04/11/2007 09:26:32.567 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
04/11/2007 09:26:32.567 Registry: Cannot read registry key value "Debug"
04/11/2007 09:26:33.348 Copy Engine: Error, unable to install MSP file: d: a41f59141805a7af3438aHotFixASFilessqlrun_as.msp
04/11/2007 09:26:33.348 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/11/2007 09:26:33.348 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 800
04/11/2007 09:26:33.755 Watson: Param1 = SetInstanceProperty
04/11/2007 09:26:33.755 Watson: Param2 = 0x7358
04/11/2007 09:26:33.755 Watson: Param3 = SetInstanceProperty
04/11/2007 09:26:33.755 Watson: Param4 = 0x7358
04/11/2007 09:26:33.755 Watson: Param5 = sqlcasqlcax.cpp@1223
04/11/2007 09:26:33.755 Watson: Param6 = Unknown
04/11/2007 09:26:33.755 Watson: Param7 = OLAP9
04/11/2007 09:26:33.755 Watson: Param8 = Hotfix@
04/11/2007 09:26:33.755 Watson: Param9 = x86
04/11/2007 09:26:33.755 Watson: Param10 = 3042
04/11/2007 09:26:33.770 Installed product: OLAP9
04/11/2007 09:26:33.770 Hotfix package completed
04/11/2007 09:26:33.770 Attempting to continue the 32 bit ngen queue
Any help would be appreciated. Thanks in advance.
Regards,
Nathan
View 3 Replies
View Related
Nov 20, 2005
I installed VS 2005 & SQL Server 2005.
View 25 Replies
View Related
Apr 28, 2006
Hi,
I'm having trouble with SQL 2005 SP1.
The following comes from SQL9_Hotfix_KB913090.log:
04/28/2006 15:13:27.843 ================================================================================
04/28/2006 15:13:27.843 Hotfix package launched
04/28/2006 15:13:28.718 Product discovery successfully completed during the install process for MSSQLSERVER
04/28/2006 15:13:28.718 SP Level check successfully completed during the install process for MSSQLSERVER
04/28/2006 15:13:28.718 Product language check successfully completed during the install process for MSSQLSERVER
04/28/2006 15:13:28.718 Product version check successfully completed during the install process for MSSQLSERVER
04/28/2006 15:13:28.718 Command-line instance name check completed during the install process
04/28/2006 15:13:28.718 Baseline build check completed during the install process
04/28/2006 15:14:16.375 Attempting to install instance: MSSQLSERVER
04/28/2006 15:14:16.375 Attempting to install target: DEAN
04/28/2006 15:14:16.390 Attempting to check for locked files: sqlrun_sql.msp
04/28/2006 15:14:16.421 Attempting to check for locked files: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp
04/28/2006 15:14:16.421 Creating MSP locked file check log at: C:WINNTHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out
04/28/2006 15:14:27.171 MSP returned 1602: The user cancels installation.
04/28/2006 15:14:27.187 Successfully checked file: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp
04/28/2006 15:14:27.187 Successfully opened registry key: SystemCurrentControlSetControlSession Manager
04/28/2006 15:14:27.187 Failed to read registry key: PendingFileRenameOperations
04/28/2006 15:14:27.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll
04/28/2006 15:14:27.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll
04/28/2006 15:14:27.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll
04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll
04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll
04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll
04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe
04/28/2006 15:14:27.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll
04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe
04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll
04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll
04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll
04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll
04/28/2006 15:14:27.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll
04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL
04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplrec.dll
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
plisapi.dll
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:WINNTassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll
04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
plhtfin.sql
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMsnapshot.exe
04/28/2006 15:14:27.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COM
eplmerg.exe
04/28/2006 15:14:27.234 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe
04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0
C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe
04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe
04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll
04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll
04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll
04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll
04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL
04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/28/2006 15:14:27.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll
04/28/2006 15:14:27.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5
C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll
04/28/2006 15:14:27.265 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll
04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll
04/28/2006 15:14:27.265 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll
04/28/2006 15:14:27.265 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll
04/28/2006 15:14:27.265 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll
04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/28/2006 15:14:27.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/28/2006 15:14:27.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/28/2006 15:14:27.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE
04/28/2006 15:14:27.296 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0
C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll
04/28/2006 15:14:27.296 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0
C:Program FilesCommon FilesSystemole dbxmlrw.dll
04/28/2006 15:14:27.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll
04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe
04/28/2006 15:14:27.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll
04/28/2006 15:14:27.328 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml
04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll
04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll
04/28/2006 15:14:27.328 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033
C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml
04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/28/2006 15:14:27.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll
04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll
04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/28/2006 15:14:27.343 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll
04/28/2006 15:14:27.343 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql
04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL
04/28/2006 15:14:27.359 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0
C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe
04/28/2006 15:14:27.359 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll
04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/28/2006 15:14:27.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/28/2006 15:14:27.375 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll
04/28/2006 15:14:27.390 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0
C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe
04/28/2006 15:14:27.390 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0
C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll
04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe
04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll
04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL
04/28/2006 15:14:27.390 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll
04/28/2006 15:14:27.406 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll
04/28/2006 15:14:27.421 Failed to read associated hotfix build information for the following file: C:WINNTassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll
04/28/2006 15:14:27.421 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe
04/28/2006 15:14:27.421 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll
04/28/2006 15:14:27.484 Attempting to install file: sqlrun_sql.msp
04/28/2006 15:14:27.531 Attempting to install file: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp
04/28/2006 15:14:27.531 Creating MSP install log file at: C:WINNTHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log
04/28/2006 15:14:27.531 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
04/28/2006 15:14:27.531 Failed to read registry key: Debug
04/28/2006 15:17:17.312 MSP returned 1603: A fatal error occurred during installation.
04/28/2006 15:17:17.359 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
04/28/2006 15:17:17.359 Failed to read registry key: Debug
04/28/2006 15:17:17.359 Unable to install MSP file: \DEANd$4c016e0f5dfb4a37300a7ce503HotFixSQLFilessqlrun_sql.msp
04/28/2006 15:17:17.359 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/28/2006 15:17:17.359 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856
04/28/2006 15:17:17.406
04/28/2006 15:17:17.406 Product Status Summary:
04/28/2006 15:17:17.406 Product: SQL Server Native Client
04/28/2006 15:17:17.406 SQL Server Native Client (RTM ) - Success
04/28/2006 15:17:17.421
04/28/2006 15:17:17.421 Product: Setup Support Files
04/28/2006 15:17:17.421 Setup Support Files (RTM ) - Success
04/28/2006 15:17:17.421
04/28/2006 15:17:17.421 Product: Database Services
04/28/2006 15:17:17.421 Database Services (SP1 2047 ENU) - Failure
04/28/2006 15:17:17.421 Details: Unable to install Windows Installer MSP file
04/28/2006 15:17:17.421 Analysis Services (SP1 2047 ENU) - Not Applied
04/28/2006 15:17:17.421
04/28/2006 15:17:17.421 Product: Integration Services
04/28/2006 15:17:17.437 Integration Services (SP1 2047 ENU) - Not Applied
04/28/2006 15:17:17.437
04/28/2006 15:17:17.437 Product: Client Components
04/28/2006 15:17:17.437 Client Components (SP1 2047 ENU) - Not Applied
04/28/2006 15:17:17.437
04/28/2006 15:17:17.437 Product: MSXML 6.0 Parser
04/28/2006 15:17:17.437 MSXML 6.0 Parser (RTM ) - Not Applied
04/28/2006 15:17:17.437
04/28/2006 15:17:17.437 Product: Backward Compatibility
04/28/2006 15:17:17.437 Backward Compatibility (RTM ) - Not Applied
04/28/2006 15:17:17.437
04/28/2006 15:17:17.453 Product: Microsoft SQL Server VSS Writer
04/28/2006 15:17:17.453 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
04/28/2006 15:17:17.453
View 3 Replies
View Related
Jan 25, 2008
I have one query which executes properly with mssql 2000 jdbc driver but fails with the 2005 driver.
The query creates a table, using insert exec method tries to get the data in the created table. But, executing this statement fails producing exception com.microsoft.sqlserver.jdbc.SQLServerException: The statement did no
t return a result set.
the command is as:
insert into #temp exec ('dbcc inputbuffer (' + @spid + ')')
I tried executing only the dbcc command on the db with query analyzer, it returns the results correctly, even with the same driver if I execute the dbcc query it runs fine and returns the resultset. But, only when I use it with insert exec it fails.
Does anyone know why this error occurs and what can be work-around.
Thanks in advance.
View 4 Replies
View Related
Oct 7, 2006
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 1 Replies
View Related
Oct 6, 2007
We have a problem with SQL Server 2005 v1.2 JDBC driver, where the application is failing with java.lang.OutOfMemoryError. We have a database of around 50 milion rows and our application has to query that database and operate on the large dataset. However, we are not facing this problem with databases having 1 million rows.
Database is running fine even after the java.lang.OutOfMemoryError in the application side. However, the application is not responding after this error.
We are facing this problem with SQL Server 2005 Standard Edition as well as Enterprise Edition.
Any help or suggestions will be highly appreciated.
View 1 Replies
View Related
Sep 28, 2006
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 12 Replies
View Related
Apr 8, 2006
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 7 Replies
View Related
Mar 27, 2008
Is there a JDBC driver specific for 2005 Express ? Or should I be using the SQLServer 2005 JDBC driver -
If specific, please provide link!
Thanks,
MrCuban
View 1 Replies
View Related
Oct 18, 2007
Hi Friends ,
Recently I downloaded version 1.2 release of the Microsoft SQL Server 2005 JDBC Driver. Thanks a ton to Microsoft
for providing many new features such as Adaptive Buffering , SSL Encryption , Tightly Coupled XA Transactions etc.
I am mainly concerned about SSL part of it and would be grateful if you can solve my queries or forward it to app-
ropriate forum.
1 ) I tried connecting to SSL enabled SQL Server 2005 through a sample program provided by Microsoft along with this
package ( Version 1.2 ) and I succeeded whereas in previous versions I use to get an exception as "The SQL Server
login requires an SSL connection." My connection string is as follows "jdbcqlserver://Ip adress of dataserver
machine:1433;databaseName=master;user=sa;password=sapassword" .
Ideally we should only get an SSL connection when we request it else an error message should be thrown informing
the user that dataserver requires an SSL connection. This would help in choosing between type of communication
a user needs with dataserver.
The scenario now is like forcing a user to have SSL communication if dataserver forces it. A flag may be added
as ssl should be mandatory or auto .
2 ) Current driver 1.2 is not capable of communicating with MS SQL Server 2000 both in case of SSL and Non - SSL
cases , The error which we receive in both cases is :
Oct 18, 2007 4:57:17 PM com.microsoft.sqlserver.jdbc.SQLServerConnection Prelogin
WARNING: ConnectionID:1 TransactionID:0x0000000000000000 Prelogin response packet not marked as EOM
The TDS protocol stream is not valid.
To communicate with both MS SQL Server 2000 and 2005 a user will have to maintain both the drivers which may
increase complexity of the application , like loading both driver in a single process , etc etc . . .
If version 1.2 id built on top of Sql server 2000 JDBC drive then it should be able to handle following 4 cases :
i ) SQL Server 2005 - SSL ,
ii ) SQL Server 2005 - Non - SSL ,
iii ) SQL Server 2000 - SSL ,
iv ) SQL Server 2000 - Non - SSL .
If this single driver handles all above 4 cases , life of a developer and application developed by him/her would
become less complex.
3 ) Last but not the least , the SQL Server 2000 JDBC driver connects with both kind of SQL Server 2000 instances i.e.
SSL and Non - SSL without any certificate of flags specified. I was able to establish non - SSL connection with SQL
Server 2000 using two third party JDBC drivers which I think is not appropriate behaviour.
4 ) I have also noticed that when SQL Server 2005 is running in Non - SSL mode i.e. "ForecEncryption=No" and our Client
application requests SSL communication , we are not warned about server is not runnning in SSL mode , could you please
explain this ?
Kindly correct me I am wrong anywhere as I am just a beginner and don't have much knowledge on this subject .
Thanks a lot.
Sincerly ,
Sudhansu Tiwari
View 1 Replies
View Related
Apr 26, 2007
hi,Does MS2005 JDBC Driver 1.1 support integrated security on Solaris and if sohow?Thanks,MarcM
View 1 Replies
View Related
Jan 11, 2008
I'm encountering a problem that seems to be due to the StreamError class not being serializable. This was raised on the JDBC Driver Team blog by Jonas on 10/24/2007. Jimmy Wu notes on 10/29/2007 that it is under investigation. Any progress?
http://blogs.msdn.com/jdbcteam/archive/2007/10/12/microsoft-sql-server-2005-jdbc-driver-v1-2-official-release.aspx#comments
Thanks,
Mike
View 2 Replies
View Related
Feb 22, 2006
We are in the process of configuring a j2ee application with SQL Server 2005. We have downloaded the new version of SQL Server 2005 Java Database Connectivity (JDBC) Driver 1.0.
We are having some issues in getting it to work using the XA datasource. Description of the error is as follows:
javax.transaction.xa.XAException: java.sql.SQLException: Failed to create the XA control connection. Error: Could not find stored procedure 'master..xp_sqljdbc_xa_init'..
at com.microsoft.sqlserver.jdbc.SQLServerXAResource.start(Unknown Source)
Has anyone else has encountered this and possibly found a solution.
Regards,
Bindu
View 33 Replies
View Related
Dec 7, 2006
Hi All,
My java application executes one stored procedure that returns two resultsets and then deal with data. The code actually is very simple
Statement stmt = con.createStatement(); con is database connection
ResultSet rs = stmt.getResultSet();
//Do something
rs.close();
rs = stmt.getResultSet();
//Do something
Then I got the error: The result set is closed.
The code worked well with jdbc sql server 2000 driver.
Thanks for your help.
Eric
View 1 Replies
View Related
Oct 5, 2006
Hi,
I'm using JDBC driver for Server 2005 (version 1.1.1501) to access Server 2000. I have no problems reading my data, but every update returns "Cursor is READ ONLY".
If I use driver for Server 2000 I have no problems. And I have no problems running the same program with 2005 driver against SQL Server Express.
Where should I start debugging?
Thank you,
View 1 Replies
View Related
