Trouble Connecting To SQL Server 2005
Feb 12, 2007
Hi, I have SBS 2003 installed and have currently been working with Sharepoint. I upgraded to SQL Server 2005 using the methods described in the documentation provided on the SBS CD, which can be found here: http://go.microsoft.com/fwlink/?LinkId=60500
I followed the document step by step and the installation completed without any problems, however after installation when trying to access a website I created in Sharepoint prior to upgrading I ran into this error: "Unable to connect to database." That error led me to the following Microsoft support article: http://support.microsoft.com/kb/823287
I followed all three methods in that article to ensure that the server is running and that it is configured properly, but it didn't change a thing.
Looking in eventvwr I noticed the following:
Failure Audit: Login failed for user 'NT AUTHORITYNETWORK SERVICE'.
Followed by:
Error: #50070: Unable to connect to database
It sounds as if Network Service doens't have the appropriate permissions to access the SQL server, but I defined those permissions in the SQL Server 2005 upgrade following what the upgrade manual provided on the CD told me.
I have been fooling around with this issue for a long time now, does anyone have any ideas?
Thanks.
~Robert Winterstein
View 1 Replies
ADVERTISEMENT
May 28, 2007
This is my first post ever so forgive me if this is too basic a question.
I have an Access 2000 database that I'm trying to make into a SQL 2005 Express database. Both databases are on the same machine (I've given up with the networking of this) and, after straightening out several problems I've ran into one I can't seem to fix.
Using the Upsizing Wizard in Access 2000 I try to connect to SQL 2005 Express but I keep getting this error: http://www.paulmauer.com/SQL%20connection%20error.doc
SInce both programs are on the same machine I don't understand what is happening. Any help would be appreciated.
Paul Mauer
View 1 Replies
View Related
Jul 17, 2007
Hi, i am trying to get to my hosting companies database server. Its SQL Sever 2000, but i want to connect through SQL Server Management Studio 2005. The connection is unable to be established, although i have tried all sorts of settings for the connection. I called the hosting company and they told me to connect using the IP address of the name server for my domain. It failed and i called again to check back, and one of the guy told me that u cannot connect to an instance of sql servr 2000 from sql server 2005. Is this true? Please help.
regards
Sarfaraz
View 12 Replies
View Related
May 3, 2006
Here is the information that I have... ( ps all information is not the actuall information )
1) URL abc.somehostingcompany.com IP: 211.11.111.1 PORT: 1433 ( NOTE: if I go to a cmd promt and type in ping abc.somehostingcompany.com I get a response )
2) dbname = mydatabase
3) userUid = sa pwd = sa
Inside SQL Server Configuration Manager --> SQL Server Network Configuration --> Protocols for SQLEXPRESS, I enabled TCP/IP and Shared Memory. Inside the properties of TCP / IP, I made sure under the "IP Address" tab that the
IP1: Active = yes
IP1: Enabled = yes
IP1: IP Address = abc.somehostingcompany.com
IP1: TCP Dynamic Ports = 0
IP1: TCP Port = < empty string >
I clicked "OK", and I stopped and started the SQL Server 2005 Services --> SQL Server (SQLEXPRESS). Then I started up SQL Server Brower.
Lastly I go to SQL Server Management Studio Express and try to connect to this remote server and database and I keep getting timeout issues and a message saying that the default settings for SQL Server Express do not allow remote connectioning by default.
Any ideas what I could be doing wrong? Should I use the port number instead of Dynamic Ports? Should I use the real IP address? Does the LOG ON AS under SQL Server (SQLEXPRESS) properties need to be updated?
Any help would be great.
Sean
View 3 Replies
View Related
Jun 9, 2004
Greetings,
I am having difficulty connecting to a SQL DB in my ASP page. Each time I run my application I receive the following error, "Login failed for user 'CX259ASPNET'". This is obviously something to do with permissions. I am all out of ideas but I will list the things I have already attempted to see if I either missed something or somebody can add to what I have already done.
1. In SQL Server I right-clicked the db -> properties -> security tab -> selected the option button to "SQL Server and Windows" instead of "Windows Only".
2. I installed SP3 and changed the sa password.
3. I created a new user under my db using the ASPNET account listed. I then changed the permissions to allow selecting, update, insert and delete access.
4. I also created a new user under my db using the IUSR account listed. I changed the permissions to the same settings as above.
I did a search on google which provided with all of the information above, but I am still stuck and hoping that this is a common problem and will be easy to fix.
Below is the code which I am attempting to use.
Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
If Not Page.IsPostBack Then
Dim strConnString As String = _
"Data Source=(local);" & _
"Initial Catalog=Names;" & _
"Integrated Security=SSPI;"
Dim objConn As New SqlConnection(strConnString)
Dim strSQL As String = "SELECT * FROM [Names]"
Dim objCmd As New SqlCommand(strSQL, objConn)
objConn.Open()
MyDataGrid.DataSource = objCmd.ExecuteReader
MyDataGrid.DataBind()
objConn.Close()
End If
End Sub
Regards,
Corey
View 11 Replies
View Related
Jul 17, 2006
ok, we have a development server in our office and it has SQL running on it. If i remote over to that machine i can open the database administrator and create tables and things just fine. I use the windows login.
now when i try to goto my machine and open up visual studio or dreamweaver to try to make a dataset connection it will not connect to the server. I get a message in visual studio saying it is probly because the default settings prohibit remote connections to the DB. I'm also doing the wondows login mode from the remote computer.
So is there a way i can change it so i can have remote access? i dont see how else they expect anyone to be able to do any development from a remote machine elsewise...
View 6 Replies
View Related
May 4, 2006
Hi,
I'm trying to use the bcp utility to create a format file to import data from a flat file. However, bcp cannot connect to the local instance of SQLEXPRESS. I am able to connect using both Visual Studio 2005 and SSMSE. Here is what I get:
snip
C:>bcp SQLEXPRESS.SAMS1DB2.Organization_01A format nul -c -f Organization_01A.fmt -T
SQLState = 08001, NativeError = 10061
Error = [Microsoft][SQL Native Client]TCP Provider: No connection could be made because the target machine actively refused it.
SQLState = HYT00, NativeError = 0
Error = [Microsoft][SQL Native Client]Login timeout expired
SQLState = 08001, NativeError = 10061
Error = [Microsoft][SQL Native Client]An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
snip
SAMS1DB2 is the database name. Organization_01A is the table name.
I'm new to SQL Server but it appears to be set up to allow remote connections, using Windows Authentication, TCP/IP and Named Pipes are enabled. I have also tried to connect using sqlcmd -S and I get a similar msg.
Any help is appreciated...Thanks in advance.
Sturdy
View 8 Replies
View Related
Aug 19, 2006
Hi I am new at this.
I have a little program written in C# in asp.net. The program basically accesses a database and stores new records. The database is supposedly already attached to MSDE so I am able to see the tables of the database inside asp.net. I can click on the individual slots of the table and modify the datas manually. However, I want to connect to the database from my C# program and be able to input data into the database via the website that the C# program produces. After I type in the data into the website and click the submit button on the website, I get an error page that says this:
Login failed for user 'sa'
the line of code thats causing this error is:
con = new SqlConnection("data source=(local)\NetSdk; initial catalog=Friends; user id=sa");
Why is it not able to connect to the database?
View 2 Replies
View Related
Feb 13, 2007
I am doing one of the Microsoft virtual labs "Creating ASP.NET Web Applications with C# - Part 2" using Visual Web Developer Express. I am trying to fill a gridview with database information, but it gives me the error "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)".This is on the local machine that I am executing the code. public void BindGrid(string sortfield)
{
//Create DataAdapter to fetch data from Prodcuts table
SqlDataAdapter myCommand = new SqlDataAdapter("select * from Products", myConnection);
//Create dataset and fill it with Product data
DataSet ds = new DataSet();
myCommand.Fill(ds, "Products");
//Bind Product data to Datagrid
DataView Source = ds.Tables["Products"].DefaultView;
Source.Sort = sortfield;
dgProducts.DataSource = Source;
dgProducts.DataBind();
} It stops on the line "myCommand.Fill(ds, "Products"); and points out the error mentioned earlier. I am not sure what to do...any help would be greatly appreciated, thanks in advance, and I apologize as well if I have not pointed out enough information.
View 4 Replies
View Related
Sep 7, 2007
Dear Sir -
I am new to thsi and I have installed the SQL server 2005 Dev (not express). I am useing Visual Web Express - When I create an application and attempt to launch it - the web config tell me that I am unable to connect to the Database - in the properties page (sidebar) the database status says closed - an I cannot seem to connect if though I go into the connections and test it says connected!
What is happening?
I need this to work? Can anyone assist?
View 1 Replies
View Related
Dec 18, 2006
Hello, I'm using Visual Studio 2003 and I need to be able to connect to an SQL Server 2005 Express database on the same machine using ASP.NET pages, but I'm having difficulty getting the pages to make a connection. I'm new to ASP.NET and I'm probably making some totally elemental mistake. I'd appreciate any assistance anyone can offer. I have pasted in part of the codebehind file for a web form (asterisking out the database name) and the error report that appears in the browser when I call the page.using System;using System.Collections;using System.ComponentModel;using System.Data;using System.Data.SqlClient;using System.Drawing;using System.Web;using System.Web.SessionState;using System.Web.UI;using System.Web.UI.WebControls;using System.Web.UI.HtmlControls;namespace WebApplication2{ /// <summary> /// Summary description for WebForm1. /// </summary> public class WebForm1 : System.Web.UI.Page { private void Page_Load(object sender, System.EventArgs e) { // Put user code to initialize the page here string strConnection="Integrated Security=SSPI;Persist Security Info=False;"; strConnection +="initial catalog = ******;server=WILL-000993DB49\SQLEXPRESS;"; SqlConnection objConnection = new SqlConnection(strConnection); objConnection.Open(); objConnection.Close(); } #region Web Form Designer generated code override protected void OnInit(EventArgs e) { // // CODEGEN: This call is required by the ASP.NET Web Form Designer. // InitializeComponent(); base.OnInit(e); } /// <summary> /// Required method for Designer support - do not modify /// the contents of this method with the code editor. /// </summary> private void InitializeComponent() { this.Load += new System.EventHandler(this.Page_Load); } #endregion }} Server Error in '/WebApplication2' Application.
Cannot open database "******" requested by the login. The login failed.Login failed for user 'WILL-000993DB49ASPNET'.
Description: An
unhandled exception occurred during the execution of the current web
request. Please review the stack trace for more information about the
error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: Cannot open database "******" requested by the login. The login failed.Login failed for user 'WILL-000993DB49ASPNET'.
Source Error:
Line 24: strConnection +="initial catalog = ******;server=WILL-000993DB49\SQLEXPRESS;";Line 25: SqlConnection objConnection = new SqlConnection(strConnection);Line 26: objConnection.Open();Line 27: objConnection.Close();Line 28:
Source File: c:inetpubwwwrootwebapplication2webform1.aspx.cs Line: 26
Stack Trace:
[SqlException (0x80131904): Cannot open database "******" requested by the login. The login failed.Login failed for user 'WILL-000993DB49ASPNET'.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734963 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 WebApplication2.WebForm1.Page_Load(Object sender, EventArgs e) in c:inetpubwwwrootwebapplication2webform1.aspx.cs:26 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +47 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061
Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.210
View 3 Replies
View Related
Sep 20, 2007
New sql2005 install as a named instance and having trouble connecting from remote machines.
I noticed on our other servers that the "Public" server role is listed in permissions (right-click over the sqlmgr connection for the dialog, then permissions).
When I try to add the role to the new server it doesn't save! This is the only setting that's different, can't connect using sqlmgr from other machines to this server so any ideas on other settings to look at appreciated.
View 6 Replies
View Related
Feb 5, 2006
I downloaded a sample blog sample from Scot Mitchel and wanted to try it out. I attached the .mdf file to SQL Server 2005 but noticed that, when I create users they don't come into the database that I attached, though all the necessary aspnet_ tables are in there but in the dedicated table I didn't see any new user. My dedicated database (LocalSqlServer) is in another database. I have the connectionstring made up in the machine.config file in the LocalSqlServer name.So I thought that the web.config does override the settings in the machine.config I could easily place this in my web.config:<remove name="LocalSqlServer"/> <add name="LocalSqlServer" connectionString="Data Source=TESTINGDBSERVER;Initial Catalog=ScotBlog;Integrated Security=True" providerName="System.Data.SqlClient"/>But that too doesn't do the trick. Does anyone have an anwser on what's going wrong here? And especially how I can solve this...
View 3 Replies
View Related
Mar 25, 2007
HiI recently installed MS SQL Server 2005 Developer Ed. w/ SP2 on my XP... I use VS2005 to create personal websites. I was previously using SQL Server Express, and things worked fine by default settings. I am a beginner to web development and I really don't know anything about SQL Server. I'm guessing it needs to be configured somehow to work with VS, but I have no idea how to do that. I have an existing Web App which uses a database for login functionality, and everytime I try and log on I get this message:An error has occurred while establishing a connection to
the server. When connecting to SQL Server 2005, this failure may be
caused by the fact that under the default settings SQL Server does not
allow remote connections. (provider: SQL Network Interfaces, error: 26
- Error Locating Server/Instance Specified)I made sure that the Server's database engine accepts remote connections but that didn't help. Does anyone have any suggestions?~Miro
View 2 Replies
View Related
Aug 11, 2007
Hello,
I am trying to install SQL Server 2005. I just installed Microsoft Visual Studio 2005(.NET). I got an option in my Start -> Programs for Microsoft SQL Server 2005. But I don't see how to bring up the query analyzer. It just has options for Configuration Tools ->SQL Server Configuration Manager,SQL Server Error and Usage Reporting, SQL Server Surface Area Configuration.
Did I install it wrong by chance? Do I need to do something else now? Do I need to configure it? If yes, how do I do that? Could anyone lead me in the right direction please? Thanks!
I have no idea how to proceed since I've never installed this before.
Could anyone please help me install or do whatever needs to be done to it so I can bring up the query analyzer/user interface and be able to use SQL?
Thanks,
Looking forward to hearing from you.
View 3 Replies
View Related
Mar 20, 2007
I am having trouble installing SQL Server 2005 on a new machine at a hosted company. I am only installing the minimum, SQL Databaes Services. It errors out at the end and says see log. I have installed SQl 2005 10 times with no problem at other locations. The service won't even start it says error 3 path unkown. If I look for the path it shows in the service it hasn't been created, the files and directories were not created at that directory location. I tried to install bot as a Domain Admin and Local Admin accounts.
Here THe summary Log., Core(local) and Core Log files below.
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Standard Edition Service Pack 1 (Build 3790)
Time : Tue Mar 20 02:48:40 2007
Machine : CATCSAP021211
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : CATCSAP021211
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : CATCSAP021211
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.6558.0
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_OWC11_1.log
--------------------------------------------------------------------------------
Machine : CATCSAP021211
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : CATCSAP021211
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_BackwardsCompat_1.log
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Tue Mar 20 02:50:13 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_OWC11_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_BackwardsCompat_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_.NET Framework 2.0 LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_.NET Framework Upgrade Advisor.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_.NET Framework Upgrade Advisor LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_.NET Framework Windows Installer.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_.NET Framework Windows Installer LangPack.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_SCC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0016_CATCSAP021211_WI.log
Core(local)
Microsoft SQL Server 2005 Setup beginning at Mon Mar 19 19:49:04 2007
Process ID : 1300
C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/2/19 19:49:4
Complete: LoadResourcesAction at: 2007/2/19 19:49:4, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/19 19:49:4
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/2/19 19:49:4, returned true
Running: ValidateWinNTAction at: 2007/2/19 19:49:4
Complete: ValidateWinNTAction at: 2007/2/19 19:49:4, returned true
Running: ValidateMinOSAction at: 2007/2/19 19:49:4
Complete: ValidateMinOSAction at: 2007/2/19 19:49:4, returned true
Running: PerformSCCAction at: 2007/2/19 19:49:4
Complete: PerformSCCAction at: 2007/2/19 19:49:4, returned true
Running: ActivateLoggingAction at: 2007/2/19 19:49:4
Complete: ActivateLoggingAction at: 2007/2/19 19:49:4, returned true
Running: DetectPatchedBootstrapAction at: 2007/2/19 19:49:4
Complete: DetectPatchedBootstrapAction at: 2007/2/19 19:49:4, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1300" returned false.
Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions:
Condition "Setup is running locally." returned true.
Running: PerformDotNetCheck2 at: 2007/2/19 19:49:4
Complete: PerformDotNetCheck2 at: 2007/2/19 19:49:4, returned true
Running: InvokeSqlSetupDllAction at: 2007/2/19 19:49:4
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.1399.0
<Func Name='DwLaunchMsiExec'>
Examining 'sqlspars' globals to initialize 'SetupStateScope'
Opening 'MachineConfigScope' for [CATCSAP021211]
Trying to find Product Code from command line or passed transform
If possible, determine install id and type
Trying to find Instance Name from command line.
No Instance Name provided on the command line
If possible, determine action
Machine = CATCSAP021211, Article = WMIServiceWin32OSWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceReadRegWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = WMIServiceCIMDataWorking, Result = 0 (0x0)
Machine = CATCSAP021211, Article = XMLDomDocument, Result = 0 (0x0)
Machine = CATCSAP021211, Article = Processor, Result = 0 (0x0)
Machine = CATCSAP021211, Article = PhysicalMemory, Result = 0 (0x0)
Machine = CATCSAP021211, Article = DiskFreeSpace, Result = 0 (0x0)
Machine = CATCSAP021211, Article = OSVersion, Result = 0 (0x0)
Machine = CATCSAP021211, Article = OSServicePack, Result = 0 (0x0)
Machine = CATCSAP021211, Article = OSType, Result = 0 (0x0)
Machine = CATCSAP021211, Article = iisDep, Result = 0 (0x0)
Machine = CATCSAP021211, Article = AdminShare, Result = 0 (0x0)
Machine = CATCSAP021211, Article = PendingReboot, Result = 0 (0x0)
Machine = CATCSAP021211, Article = PerfMon, Result = 0 (0x0)
Machine = CATCSAP021211, Article = IEVersion, Result = 0 (0x0)
Machine = CATCSAP021211, Article = DriveWriteAccess, Result = 0 (0x0)
Machine = CATCSAP021211, Article = COMPlus, Result = 0 (0x0)
Machine = CATCSAP021211, Article = ASPNETVersionRegistration, Result = 0 (0x0)
Machine = CATCSAP021211, Article = MDAC25Version, Result = 0 (0x0)
*******************************************
Setup Consistency Check Report for Machine: CATCSAP021211
*******************************************
Article: WMI Service Requirement, Result: CheckPassed
Article: MSXML Requirement, Result: CheckPassed
Article: Operating System Minimum Level Requirement, Result: CheckPassed
Article: Operating System Service Pack Level Requirement, Result: CheckPassed
Article: SQL Compatibility With Operating System, Result: CheckPassed
Article: Minimum Hardware Requirement, Result: CheckPassed
Article: IIS Feature Requirement, Result: CheckPassed
Article: Pending Reboot Requirement, Result: CheckPassed
Article: Performance Monitor Counter Requirement, Result: CheckPassed
Article: Default Installation Path Permission Requirement, Result: CheckPassed
Article: Internet Explorer Requirement, Result: CheckPassed
Article: Check COM+ Catalogue, Result: CheckPassed
Article: ASP.Net Registration Requirement, Result: CheckPassed
Article: Minimum MDAC Version Requirement, Result: CheckPassed
<Func Name='PerformDetections'>
0
<EndFunc Name='PerformDetections' Return='0' GetLastError='0'>
<Func Name='DisplaySCCWizard'>
CSetupBootstrapWizard returned 1
<EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'>
Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0
<EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'>
Complete: InvokeSqlSetupDllAction at: 2007/2/19 19:51:1, returned true
Running: SetPackageInstallStateAction at: 2007/2/19 19:51:1
Complete: SetPackageInstallStateAction at: 2007/2/19 19:51:1, returned true
Running: DeterminePackageTransformsAction at: 2007/2/19 19:51:1
Complete: DeterminePackageTransformsAction at: 2007/2/19 19:51:3, returned true
Running: ValidateSetupPropertiesAction at: 2007/2/19 19:51:3
Complete: ValidateSetupPropertiesAction at: 2007/2/19 19:51:3, returned true
Running: OpenPipeAction at: 2007/2/19 19:51:3
Complete: OpenPipeAction at: 2007/2/19 19:51:3, returned false
Error: Action "OpenPipeAction" failed during execution.
Running: CreatePipeAction at: 2007/2/19 19:51:3
Complete: CreatePipeAction at: 2007/2/19 19:51:3, returned false
Error: Action "CreatePipeAction" failed during execution.
Action "RunRemoteSetupAction" will be skipped due to the following restrictions:
Condition "Action: CreatePipeAction has finished and passed." returned false.
Running: PopulateMutatorDbAction at: 2007/2/19 19:51:3
Complete: PopulateMutatorDbAction at: 2007/2/19 19:51:3, returned true
Running: GenerateRequestsAction at: 2007/2/19 19:51:3
SQL_Engine = 3
SQL_Data_Files = 3
SQL_Replication = 3
SQL_FullText = 3
SQL_SharedTools = 3
SQL_BC_DEP = 3
Analysis_Server = -1
AnalysisDataFiles = -1
AnalysisSharedTools = -1
RS_Server = -1
RS_Web_Interface = -1
RS_SharedTools = -1
Notification_Services = -1
NS_Engine = -1
NS_Client = -1
SQL_DTS = -1
Client_Components = 3
Connectivity = 3
SQL_Tools90 = 3
SQL_WarehouseDevWorkbench = 3
SDK = 3
SQLXML = 3
Tools_Legacy = 3
TOOLS_BC_DEP = 3
SQL_Documentation = 3
SQL_BooksOnline = 3
SQL_DatabaseSamples = -1
SQL_AdventureWorksSamples = -1
SQL_AdventureWorksDWSamples = -1
SQL_AdventureWorksASSamples = -1
SQL_Samples = -1
Complete: GenerateRequestsAction at: 2007/2/19 19:51:4, returned true
Running: CreateProgressWindowAction at: 2007/2/19 19:51:4
Complete: CreateProgressWindowAction at: 2007/2/19 19:51:4, returned true
Running: ScheduleActionAction at: 2007/2/19 19:51:4
Complete: ScheduleActionAction at: 2007/2/19 19:51:4, returned true
Skipped: InstallASAction.11
Skipped: Action "InstallASAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.18
Skipped: Action "InstallASAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.22
Skipped: Action "InstallASAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result.
Skipped: InstallASAction.9
Skipped: Action "InstallASAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result.
Skipped: InstallDTSAction
Skipped: Action "InstallDTSAction" was not run. Information reported during analysis:
No install request found for package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.11
Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.12
Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.18
Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.22
Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result.
Skipped: InstallDTSAction.9
Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result.
Skipped: InstallNSAction
Skipped: Action "InstallNSAction" was not run. Information reported during analysis:
No install request found for package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.11
Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.12
Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis:
No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.18
Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.22
Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result.
Skipped: InstallNSAction.9
Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis:
No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result.
Skipped: InstallRSAction.11
Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis:
No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.18
Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis:
No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result.
Skipped: InstallRSAction.22
Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis:
No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result.
Running: InstallSqlAction.11 at: 2007/2/19 19:51:4
Installing: sqlsupport on target: CATCSAP021211
Complete: InstallSqlAction.11 at: 2007/2/19 19:51:5, returned true
Running: InstallSqlAction.12 at: 2007/2/19 19:51:5
Installing: sqlncli on target: CATCSAP021211
Complete: InstallSqlAction.12 at: 2007/2/19 19:51:6, returned true
Running: InstallSqlAction.18 at: 2007/2/19 19:51:6
Installing: owc11 on target: CATCSAP021211
Complete: InstallSqlAction.18 at: 2007/2/19 19:51:13, returned true
Running: InstallSqlAction.21 at: 2007/2/19 19:51:13
Installing: sqlwriter on target: CATCSAP021211
Complete: InstallSqlAction.21 at: 2007/2/19 19:51:18, returned true
Running: InstallSqlAction.22 at: 2007/2/19 19:51:18
Installing: bcRedist on target: CATCSAP021211
Complete: InstallSqlAction.22 at: 2007/2/19 19:51:28, returned true
Running: InstallSqlAction.9 at: 2007/2/19 19:51:28
Installing: msxml6 on target: CATCSAP021211
Error: MsiOpenDatabase failed with 110
Failed to install package
The installation source for this product is not available. Verify that the source exists and that you can access it.
Error: MsiOpenDatabase failed with 110 for MSI {5A710547-B58E-488B-828D-CA9A25A0533C}
Setting package return code to: 1612
Complete: InstallSqlAction.9 at: 2007/2/19 19:51:28, returned false
Error: Action "InstallSqlAction.9" failed during execution. Error information reported during run:
Target collection includes the local machine.
Invoking installPackage() on local machine.
Running: InstallToolsAction.11 at: 2007/2/19 19:51:28
Installing: sqlsupport on target: CATCSAP021211
Complete: InstallToolsAction.11 at: 2007/2/19 19:51:33, returned true
Running: InstallToolsAction.12 at: 2007/2/19 19:51:33
Installing: sqlncli on target: CATCSAP021211
Complete: InstallToolsAction.12 at: 2007/2/19 19:51:34, returned true
Running: InstallToolsAction.13 at: 2007/2/19 19:51:34
Installing: PPESku on target: CATCSAP021211
Complete: InstallToolsAction.13 at: 2007/2/19 19:53:48, returned true
Running: InstallToolsAction.18 at: 2007/2/19 19:53:48
Installing: owc11 on target: CATCSAP021211
Complete: InstallToolsAction.18 at: 2007/2/19 19:53:51, returned true
Running: InstallToolsAction.20 at: 2007/2/19 19:53:51
Installing: BOL on target: CATCSAP021211
Complete: InstallToolsAction.20 at: 2007/2/19 19:55:37, returned true
Running: InstallToolsAction.22 at: 2007/2/19 19:55:37
Installing: bcRedist on target: CATCSAP021211
Complete: InstallToolsAction.22 at: 2007/2/19 19:55:40, returned true
Error: Action "InstallToolsAction.9" failed during execution. Error information reported during run:
Action: "InstallToolsAction.9" will be marked as failed due to the following condition:
Condition "Package "9" either passed when it was last installed, or it has not been executed yet" returned false. Condition context:
Prereq package will be failed due to the previous installation attempt returning: 1612
Installation of package: "msxml6" failed due to a precondition.
Action "InstallSqlAction" will return false due to the following preconditions:
Condition "Action: InstallSqlAction.9 has finished and failed." returned true.
Installation of package: "sql" failed due to a precondition.
Step "InstallSqlAction" was not able to run.
Skipped: InstallNSAction.10
Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis:
No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result.
Running: InstallToolsAction.10 at: 2007/2/19 19:55:40
Installing: sqlxml4 on target: CATCSAP021211
Complete: InstallToolsAction.10 at: 2007/2/19 19:55:44, returned true
Skipped: RepairForBackwardsCompatRedistAction
Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis:
Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run:
Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchMSDE2000" failed due to a precondition.
Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run:
Action: "UninstallForSQLAction" will be marked as failed due to the following condition:
Condition "sql was successfully upgraded." returned false. Condition context:
sql failed to upgrade and so the uninstall of the upgraded product will not occur.
Installation of package: "patchLibertySql" failed due to a precondition.
Action "InstallToolsAction" will return false due to the following preconditions:
Condition "Action: InstallToolsAction.9 has finished and failed." returned true.
Installation of package: "tools" failed due to a precondition.
Step "InstallToolsAction" was not able to run.
Skipped: InstallASAction
Skipped: Action "InstallASAction" was not run. Information reported during analysis:
No install request found for package: "as", install will be skipped as a result.
Skipped: InstallRSAction
Skipped: Action "InstallRSAction" was not run. Information reported during analysis:
No install request found for package: "rs", install will be skipped as a result.
Skipped: UninstallForRS2000Action
Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis:
Action: "UninstallForRS2000Action" will be skipped due to the following condition:
Condition "Action: InstallRSAction was skipped." returned true.
Running: ReportChainingResults at: 2007/2/19 19:55:44
Error: Action "ReportChainingResults" threw an exception during execution.
One or more packages failed to install. Refer to logs for error details. : 1612
Error Code: 0x8007064c (1612)
Windows Error Text: The installation source for this product is not available. Verify that the source exists and that you can access it.
Source File Name: sqlchainingsqlchainingactions.cpp
Compiler Timestamp: Thu Sep 1 22:23:05 2005
Function Name: sqls::ReportChainingResults::perform
Source Line Number: 3097
---- Context -----------------------------------------------
sqls::HostSetupPackageInstallerSynch::postCommit
sqls::HighlyAvailablePackage::preInstall
sqls::HighlyAvailablePackage::manageVsResources
sqls::Host
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_CATCSAP021211_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_CATCSAP021211_.NET Framework 2.0 LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_CATCSAP021211_.NET Framework Upgrade Advisor.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_CATCSAP021211_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_CATCSAP021211_.NET Framework Windows Installer.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0012.cab" Error Code : 2
Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0012_CATCSAP021211_.NET Framework Windows Installer LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0012.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2007/2/19 19:56:20
Message pump returning: 1612
Core.log
Microsoft SQL Server 2005 Setup beginning at Mon Mar 19 19:48:44 2007
Process ID : 1864
\Catcsdc021209SQLDISC1setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2007/2/19 19:48:44
Complete: LoadResourcesAction at: 2007/2/19 19:48:44, returned true
Running: ParseBootstrapOptionsAction at: 2007/2/19 19:48:44
Loaded DLL:\Catcsdc021209SQLDISC1xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2007/2/19 19:48:44, returned true
Running: ValidateWinNTAction at: 2007/2/19 19:48:44
Complete: ValidateWinNTAction at: 2007/2/19 19:48:44, returned true
Running: ValidateMinOSAction at: 2007/2/19 19:48:44
Complete: ValidateMinOSAction at: 2007/2/19 19:48:44, returned true
Running: PerformSCCAction at: 2007/2/19 19:48:44
Complete: PerformSCCAction at: 2007/2/19 19:48:44, returned true
Running: ActivateLoggingAction at: 2007/2/19 19:48:44
Complete: ActivateLoggingAction at: 2007/2/19 19:48:44, returned true
Delay load of action "DetectPatchedBootstrapAction" returned nothing. No action will occur as a result.
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1864" returned false.
Running: PerformSCCAction2 at: 2007/2/19 19:48:44
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.2435
Loaded DLL:C:WINDOWSsystem32msi.dll Version:3.1.4000.2435
Complete: PerformSCCAction2 at: 2007/2/19 19:48:44, returned true
Running: PerformDotNetCheck at: 2007/2/19 19:48:44
Complete: PerformDotNetCheck at: 2007/2/19 19:48:44, returned true
Running: ComponentUpdateAction at: 2007/2/19 19:48:44
Complete: ComponentUpdateAction at: 2007/2/19 19:49:3, returned true
Running: DetectLocalBootstrapAction at: 2007/2/19 19:49:3
Complete: DetectLocalBootstrapAction at: 2007/2/19 19:49:3, returned true
Running: LaunchLocalBootstrapAction at: 2007/2/19 19:49:3
Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:
"C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 1612
Aborting queue processing as nested installer has completed
Message pump returning: 1612
Thanks for any Help
Don
View 1 Replies
View Related
Nov 28, 2007
I was having trouble with SQL server 2005 and reporting services. Finally I had to un-install and then re-install, had trouble with uninstalling initially. I couldn't use Add/Remove to remove Microsoft SQL Server 2005 until I found this command: "%ProgramFiles%Microsoft SQL Server90Setup BootstrapARPWrapper.exe" /Remove from http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=354408&SiteID=1
So I was able to remove (from what I know) all traces of SQL 2005 and its configuration tools. However when I reinstall it, I only have the configuration tools installed. Going to Start>>Microsoft SQL Server 2005 - configuration tools is all i have. Going to Add Remove Programs I can see Microsoft SQL Server 2005 along with Microsoft SQL Server Native Client.
When I use windows exploerer the only folders I see in c:Program FilesMicrosoft SQL Server are:
80, 90, InetPub, MSSQL.1, MSSQL.2, MSSQL.3
when I install SP2 everything but
PRODUCT INSTANCE
Database Services MSSQLSERVER
install correctly.
After that nothing changes.
My questions are; do I really have SQL Sever installed so that I can create and edit queries, reports, etc. And if I do how do I access it? It seems like something is left over telling the installer that I already have SQL already installed but not the configurations tools. So it just installs them.
View 8 Replies
View Related
Mar 20, 2007
I'm Having problem installing SQL server 2005 SP1 on Windows 2003 server R2 SP2.
The log file talk about SQL server express but I have SQL server 2005.
03/19/2007 13:49:07.203 ================================================================================
03/19/2007 13:49:07.203 Hotfix package launched
03/19/2007 13:49:32.984 Attempting to install instance: SQL Server Native Client
03/19/2007 13:49:33.000 Attempting to install target: OMNIWEBPACS
03/19/2007 13:49:33.000 Attempting to install file: sqlncli.msi
03/19/2007 13:49:33.015 Attempting to install file: \OMNIWEBPACSd$c06cd32e1991973c97744b9c4HotFixSqlncliFilessqlncli.msi
03/19/2007 13:49:33.015 Creating MSI install log file at: C:WINDOWSHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log
03/19/2007 13:49:33.015 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
03/19/2007 13:49:33.015 Failed to read registry key: Debug
03/19/2007 13:49:34.062 MSP returned 0: The action completed successfully.
03/19/2007 13:49:34.062 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller
03/19/2007 13:49:34.062 Failed to read registry key: Debug
03/19/2007 13:49:34.062 Successfully installed file: \OMNIWEBPACSd$c06cd32e1991973c97744b9c4HotFixSqlncliFilessqlncli.msi
03/19/2007 13:49:34.062 Successfully installed target: OMNIWEBPACS
03/19/2007 13:49:34.062 Successfully installed instance: SQL Server Native Client
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product Status Summary:
03/19/2007 13:49:34.062 Product: SQL Server Native Client
03/19/2007 13:49:34.062 SQL Server Native Client (RTM ) - Success
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: Setup Support Files
03/19/2007 13:49:34.062 Setup Support Files (RTM ) - Not Applied
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: Database Services
03/19/2007 13:49:34.062 Database Services (SP1 2047 ENU) - NA
03/19/2007 13:49:34.062 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer.
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: Database Services
03/19/2007 13:49:34.062 Database Services (RTM 1399 ENU) - Not Applied
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: Integration Services
03/19/2007 13:49:34.062 Integration Services (RTM 1399 ENU) - Not Applied
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: Client Components
03/19/2007 13:49:34.062 Client Components (RTM 1399 ENU) - Not Applied
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: MSXML 6.0 Parser
03/19/2007 13:49:34.062 MSXML 6.0 Parser (RTM ) - Not Applied
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: SQLXML4
03/19/2007 13:49:34.062 SQLXML4 (RTM ) - Not Applied
03/19/2007 13:49:34.062
03/19/2007 13:49:34.062 Product: Backward Compatibility
03/19/2007 13:49:34.078 Backward Compatibility (RTM ) - Not Applied
03/19/2007 13:49:34.078
03/19/2007 13:49:34.078 Product: Microsoft SQL Server VSS Writer
03/19/2007 13:49:34.078 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
03/19/2007 13:49:34.078
any Idea?
View 1 Replies
View Related
Mar 15, 2007
I tried the hotfix listed in the "Unable to install SQl Server 2005 SP2 - Unexpected error" thread and it did not work. Something I'm running into that I haven't seen here is I cannot install or uninstall anything at all. I am getting a message that says I'm still in the process of installing something, please finish that first. I assume it is the install of SQL SP2.
Here is the log file:
03/09/2007 14:03:45.750 ================================================================================
03/09/2007 14:03:45.750 Hotfix package launched
03/09/2007 14:03:45.812 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:45.812 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:45.843 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:45.875 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:45.890 Local Computer:
03/09/2007 14:03:45.921 Target Details: BVTBIQA
03/09/2007 14:03:45.953 commonfilesdir = C:Program FilesCommon Files
03/09/2007 14:03:45.984 lcidsupportdir = c:57a10d1e173eea2efd90865f301376381033
03/09/2007 14:03:46.000 programfilesdir = C:Program Files
03/09/2007 14:03:46.031 programfilesdir_wow = C:Program Files
03/09/2007 14:03:46.046 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:03:46.078 supportdirlocal = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:03:46.109 windir = C:WINDOWS
03/09/2007 14:03:46.125 winsysdir = C:WINDOWSsystem32
03/09/2007 14:03:46.156 winsysdir_wow = C:WINDOWSSysWOW64
03/09/2007 14:03:46.171
03/09/2007 14:03:46.218 Enumerating applicable products for this patch
03/09/2007 14:03:46.250 Found Redist 2005 product definition
03/09/2007 14:03:46.296 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:46.328 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:46.359 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:46.375 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:46.640 Found Redist 2005 product definition
03/09/2007 14:03:46.671 Found Redist 2005 product definition
03/09/2007 14:03:46.703 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:46.734 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:46.765 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:46.781 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:47.187 Found SQL 2005 product definition
03/09/2007 14:03:49.046 Enumeration: Determining QFE level for product instance MSSQLSERVER
03/09/2007 14:03:49.078 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
03/09/2007 14:03:49.093 Enumeration: Found following QFE level for product instance MSSQLSERVER: 2047
03/09/2007 14:03:49.109 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
03/09/2007 14:03:49.140 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
03/09/2007 14:03:49.156 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
03/09/2007 14:03:49.187 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:49.203 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:49.234 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:49.265 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:49.281 Product discovery completed during the install process for MSSQLSERVER
03/09/2007 14:03:49.312 SP Level check completed during the install process for MSSQLSERVER
03/09/2007 14:03:49.343 Product language check completed during the install process for MSSQLSERVER
03/09/2007 14:03:49.359 Product version check completed during the install process for MSSQLSERVER
03/09/2007 14:03:49.375 Command-line instance name check completed during the install process
03/09/2007 14:03:49.406 SKU check completed during the install process for MSSQLSERVER
03/09/2007 14:03:49.437 Baseline build check completed during the installation process for MSSQLSERVER
03/09/2007 14:03:49.453 Baseline build check completed during the install process
03/09/2007 14:03:49.484 Found OLAP Server 2005 product definition
03/09/2007 14:03:50.468 Command-line instance name check completed during the install process
03/09/2007 14:03:50.500 Baseline build check completed during the install process
03/09/2007 14:03:50.531 Found Notification Services 2005 product definition
03/09/2007 14:03:51.515 Baseline build check completed during the install process
03/09/2007 14:03:51.546 Found Report Server 2005 product definition
03/09/2007 14:03:52.546 Command-line instance name check completed during the install process
03/09/2007 14:03:52.578 Baseline build check completed during the install process
03/09/2007 14:03:52.609 Found DTS 2005 product definition
03/09/2007 14:03:53.734 Enumeration: Determining QFE level for product instance
03/09/2007 14:03:53.765 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90DTS\Binnmsdtssrvr.exe
03/09/2007 14:03:53.828 Enumeration: Found following QFE level for product instance : 2047
03/09/2007 14:03:53.843 Enumeration: Determining GDR branching Hotfix for product instance
03/09/2007 14:03:53.875 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90DTS\Binnmsdtssrvr.exe
03/09/2007 14:03:53.906 Enumeration: No GDR branch Hotfix found for product instance
03/09/2007 14:03:53.921 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:53.953 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:53.984 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:54.015 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:54.031 Product discovery completed during the install process for Integration Services
03/09/2007 14:03:54.062 SP Level check completed during the install process for Integration Services
03/09/2007 14:03:54.078 Product language check completed during the install process for Integration Services
03/09/2007 14:03:54.109 Product version check completed during the install process for Integration Services
03/09/2007 14:03:54.140 Baseline build check completed during the installation process for Integration Services
03/09/2007 14:03:54.156 Baseline build check completed during the install process
03/09/2007 14:03:54.187 Found SQL 2005 Tools product definition
03/09/2007 14:03:55.187 Enumeration: Determining GDR branching Hotfix for product instance
03/09/2007 14:03:55.218 Enumeration: Associated hotfix build information not found for the following file: C:Program FilesMicrosoft SQL Server90Tools\BinnVSShellCommon7IDESQLWB.EXE
03/09/2007 14:03:55.250 Enumeration: No GDR branch Hotfix found for product instance
03/09/2007 14:03:55.281 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:55.296 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:55.328 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:55.343 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:55.375 Product discovery completed during the install process for SQL Tools
03/09/2007 14:03:55.406 SP Level check completed during the install process for SQL Tools
03/09/2007 14:03:55.421 Product language check completed during the install process for SQL Tools
03/09/2007 14:03:55.453 Product version check completed during the install process for SQL Tools
03/09/2007 14:03:55.468 SKU check completed during the install process for SQL Tools
03/09/2007 14:03:55.500 Baseline build check completed during the installation process for SQL Tools
03/09/2007 14:03:55.531 Baseline build check completed during the install process
03/09/2007 14:03:55.562 Found Redist 2005 product definition
03/09/2007 14:03:55.593 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:55.625 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:55.640 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:55.671 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:55.859 Found Redist 2005 product definition
03/09/2007 14:03:55.890 Found Redist 2005 product definition
03/09/2007 14:03:55.921 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:55.953 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:55.984 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:56.000 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:56.234 Found Redist 2005 product definition
03/09/2007 14:03:56.265 Found Redist 2005 product definition
03/09/2007 14:03:56.296 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:56.312 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:56.343 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:56.375 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:56.640 Found Redist 2005 product definition
03/09/2007 14:03:56.671 Found Redist 2005 product definition
03/09/2007 14:03:56.703 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:56.734 Registry: Read registry key value "CommonFilesDir", string value = C:Program FilesCommon Files
03/09/2007 14:03:56.750 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
03/09/2007 14:03:56.781 Registry: Read registry key value "ProgramFilesDir", string value = C:Program Files
03/09/2007 14:03:56.968 Found Redist 2005 product definition
03/09/2007 14:03:57.171 Product Enumeration Results:
03/09/2007 14:03:57.203 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSqlncli.inf
03/09/2007 14:03:57.234 baselinebuild = 1399
03/09/2007 14:03:57.250 build = 3042
03/09/2007 14:03:57.281 description = SQL Server Native Client
03/09/2007 14:03:57.296 details = Service Pack for Microsoft SQL Server Native Client.
03/09/2007 14:03:57.328 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:03:57.343 kbarticle = KB921896
03/09/2007 14:03:57.375 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:03:57.406 lcid = 1033
03/09/2007 14:03:57.421 legalproductname = Microsoft SQL Native Client
03/09/2007 14:03:57.453 machinetype = x86
03/09/2007 14:03:57.468 package = HotFixSqlncli
03/09/2007 14:03:57.500 packagetype = Hotfix
03/09/2007 14:03:57.515 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
03/09/2007 14:03:57.546 productname = Redist9
03/09/2007 14:03:57.562 recommendinstall = 1
03/09/2007 14:03:57.593 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:03:57.625 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:03:57.640 splevel = 2
03/09/2007 14:03:57.671 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:03:57.703 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:03:57.718 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
03/09/2007 14:03:57.750 version = 9
03/09/2007 14:03:57.765
03/09/2007 14:03:57.796 File Group Details: MSI
03/09/2007 14:03:57.828 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:03:57.843 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:03:57.875 File Details: sqlncli.msi
03/09/2007 14:03:57.890
03/09/2007 14:03:57.921 Instance Details: SQL Server Native Client
03/09/2007 14:03:57.953 fullversion = 9.00.2047.00
03/09/2007 14:03:57.984 lcid = 1033
03/09/2007 14:03:58.000 productcode = {50A0893D-47D8-48E0-A7E8-44BCD7E4422E}
03/09/2007 14:03:58.031 qfelevel = 2047
03/09/2007 14:03:58.062 sp = -1
03/09/2007 14:03:58.078
03/09/2007 14:03:58.109 Product Enumeration Results:
03/09/2007 14:03:58.125 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSqlncli_x64.inf
03/09/2007 14:03:58.156 baselinebuild = 1399
03/09/2007 14:03:58.171 build = 3042
03/09/2007 14:03:58.203 description = SQL Server Native Client
03/09/2007 14:03:58.234 details = Service Pack for Microsoft SQL Server Native Client.
03/09/2007 14:03:58.250 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:03:58.281 kbarticle = KB921896
03/09/2007 14:03:58.296 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:03:58.328 lcid = 1033
03/09/2007 14:03:58.359 legalproductname = Microsoft SQL Native Client (64-bit)
03/09/2007 14:03:58.375 machinetype = x64
03/09/2007 14:03:58.406 package = HotFixSqlncli_x64
03/09/2007 14:03:58.421 packagetype = Hotfix
03/09/2007 14:03:58.453 productname = Redist9
03/09/2007 14:03:58.484 recommendinstall = 1
03/09/2007 14:03:58.500 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:03:58.531 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:03:58.546 splevel = 2
03/09/2007 14:03:58.578 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:03:58.609 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
03/09/2007 14:03:58.625 version = 9
03/09/2007 14:03:58.656
03/09/2007 14:03:58.671 File Group Details: MSI
03/09/2007 14:03:58.703 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:03:58.734 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:03:58.750 File Details: sqlncli_x64.msi
03/09/2007 14:03:58.781
03/09/2007 14:03:58.796 Product Enumeration Results:
03/09/2007 14:03:58.828 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSqlSupport.inf
03/09/2007 14:03:58.859 alwaysinstall = 1
03/09/2007 14:03:58.875 baselinebuild = 1399
03/09/2007 14:03:58.906 build = 3042
03/09/2007 14:03:58.921 description = Setup Support Files
03/09/2007 14:03:58.953 details = Service Pack for the SQL Server support files.
03/09/2007 14:03:58.984 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:03:59.000 kbarticle = KB921896
03/09/2007 14:03:59.031 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:03:59.046 keyqualifier = 1
03/09/2007 14:03:59.078 lcid = 1033
03/09/2007 14:03:59.109 legalproductname = SQL Server 2005 Setup Support Files
03/09/2007 14:03:59.125 machinetype = x86
03/09/2007 14:03:59.156 package = HotFixSqlSupport
03/09/2007 14:03:59.187 packagetype = Hotfix
03/09/2007 14:03:59.203 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
03/09/2007 14:03:59.234 productname = Redist9
03/09/2007 14:03:59.250 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:03:59.281 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:03:59.312 splevel = 2
03/09/2007 14:03:59.328 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:03:59.359 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:03:59.375 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
03/09/2007 14:03:59.406 version = 9
03/09/2007 14:03:59.437
03/09/2007 14:03:59.468 File Group Details: MSI
03/09/2007 14:03:59.484 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCacheSQLSupport<MachineType><LCID>
03/09/2007 14:03:59.515 parameters = REINSTALL=ALL
03/09/2007 14:03:59.562 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:03:59.593 File Details: SqlSupport.msi
03/09/2007 14:03:59.609
03/09/2007 14:03:59.640 Instance Details: Setup Support Files
03/09/2007 14:03:59.671 fullversion = 9.1.2047
03/09/2007 14:03:59.718 lcid = 1033
03/09/2007 14:03:59.750 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
03/09/2007 14:03:59.765 qfelevel = 2047
03/09/2007 14:03:59.796 sp = -1
03/09/2007 14:03:59.828
03/09/2007 14:03:59.859 Product Enumeration Results:
03/09/2007 14:03:59.890 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSQL.inf
03/09/2007 14:03:59.921 baselinebuild = 1399
03/09/2007 14:03:59.953 baselinebuildmax = 3042
03/09/2007 14:03:59.984 build = 3042
03/09/2007 14:04:00.125 description = Database Services
03/09/2007 14:04:00.187 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
03/09/2007 14:04:00.234 installer = Hotfix
03/09/2007 14:04:00.250 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:00.296 kbarticle = KB921896
03/09/2007 14:04:00.328 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:00.359 lcid = 1033
03/09/2007 14:04:00.390 legalproductname = SQL Server Database Services 2005
03/09/2007 14:04:00.421 machinetype = x86
03/09/2007 14:04:00.453 package = HotFixSQL
03/09/2007 14:04:00.484 packagetype = Hotfix
03/09/2007 14:04:00.515 productname = SQL9
03/09/2007 14:04:00.546 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:00.578 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:00.609 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/09/2007 14:04:00.640 splevel = 2
03/09/2007 14:04:00.671 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:00.703 sqlutility = sqlcmd.exe
03/09/2007 14:04:00.734 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:00.765 validateauthentication = true
03/09/2007 14:04:00.796 version = 9
03/09/2007 14:04:00.812
03/09/2007 14:04:00.843 File Group Details: MSP
03/09/2007 14:04:00.875 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/09/2007 14:04:00.906 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:00.937 File Details: sqlrun_sql.msp
03/09/2007 14:04:00.968
03/09/2007 14:04:01.000 Instance Details: MSSQLSERVER
03/09/2007 14:04:01.031 agentservicename = SQLSERVERAGENT
03/09/2007 14:04:01.062 associatedhotfixbuild = 0
03/09/2007 14:04:01.093 clustername =
03/09/2007 14:04:01.125 default = TRUE
03/09/2007 14:04:01.156 ftsservicename = MSFTESQL
03/09/2007 14:04:01.187 fullversion = 2005.090.2047.00
03/09/2007 14:04:01.218 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
03/09/2007 14:04:01.250 id = MSSQL.1
03/09/2007 14:04:01.281 installsqldatadir = C:Program FilesMicrosoft SQL ServerMSSQL
03/09/2007 14:04:01.312 installsqldir = C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
03/09/2007 14:04:01.343 lcid = 1033
03/09/2007 14:04:01.375 name = MSSQLSERVER
03/09/2007 14:04:01.406 productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
03/09/2007 14:04:01.437 qfelevel = 2047
03/09/2007 14:04:01.468 servicename = MSSQLServer
03/09/2007 14:04:01.500 sku = STANDARD
03/09/2007 14:04:01.531 sp = 1
03/09/2007 14:04:01.562 type = SQL Server Standalone Product
03/09/2007 14:04:01.593 vermajbld = 2047
03/09/2007 14:04:01.625 version = 9
03/09/2007 14:04:01.656
03/09/2007 14:04:01.687 Product Enumeration Results:
03/09/2007 14:04:01.718 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixAS.inf
03/09/2007 14:04:01.750 baselinebuild = 1399
03/09/2007 14:04:01.781 baselinebuildmax = 3042
03/09/2007 14:04:01.812 build = 3042
03/09/2007 14:04:01.843 description = Analysis Services
03/09/2007 14:04:01.875 details = Service Pack for Analysis Services, and the tools used to support online analytical processing (OLAP) and data mining.
03/09/2007 14:04:01.906 installer = Hotfix
03/09/2007 14:04:01.921 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:01.953 kbarticle = KB921896
03/09/2007 14:04:02.000 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:02.015 lcid = 1033
03/09/2007 14:04:02.046 legalproductname = SQL Server Analysis Services 2005
03/09/2007 14:04:02.078 machinetype = x86
03/09/2007 14:04:02.109 package = HotFixAS
03/09/2007 14:04:02.140 packagetype = Hotfix
03/09/2007 14:04:02.171 productname = OLAP9
03/09/2007 14:04:02.203 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:02.234 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:02.265 splevel = 2
03/09/2007 14:04:02.312 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:02.328 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:02.359 version = 9
03/09/2007 14:04:02.390
03/09/2007 14:04:02.421 File Group Details: MSP
03/09/2007 14:04:02.453 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/09/2007 14:04:02.484 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:02.515 File Details: sqlrun_as.msp
03/09/2007 14:04:02.546
03/09/2007 14:04:02.578 Product Enumeration Results:
03/09/2007 14:04:02.609 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixNS.inf
03/09/2007 14:04:02.640 baselinebuild = 1399
03/09/2007 14:04:02.671 baselinebuildmax = 3042
03/09/2007 14:04:02.687 build = 3042
03/09/2007 14:04:02.718 description = Notification Services
03/09/2007 14:04:02.750 details = Service Pack for Notification Services, a platform for developing and deploying applications that send personalized, timely notifications to a variety of devices or applications.
03/09/2007 14:04:02.781 installer = Hotfix
03/09/2007 14:04:02.812 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:02.843 kbarticle = KB921896
03/09/2007 14:04:02.875 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:02.906 lcid = 1033
03/09/2007 14:04:02.953 legalproductname = SQL Server Notification Services 2005 instances
03/09/2007 14:04:02.984 machinetype = x86
03/09/2007 14:04:03.015 package = HotFixNS
03/09/2007 14:04:03.046 packagetype = Hotfix
03/09/2007 14:04:03.062 productname = NS9
03/09/2007 14:04:03.093 recommendinstall = 1
03/09/2007 14:04:03.109 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:03.140 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:03.171 splevel = 2
03/09/2007 14:04:03.187 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:03.218 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:03.234 version = 9
03/09/2007 14:04:03.265
03/09/2007 14:04:03.296 File Group Details: MSP
03/09/2007 14:04:03.312 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/09/2007 14:04:03.343 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:03.359 File Details: sqlrun_ns.msp
03/09/2007 14:04:03.390
03/09/2007 14:04:03.421 Product Enumeration Results:
03/09/2007 14:04:03.437 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixRS.inf
03/09/2007 14:04:03.468 baselinebuild = 1399
03/09/2007 14:04:03.484 baselinebuildmax = 3042
03/09/2007 14:04:03.515 build = 3042
03/09/2007 14:04:03.531 description = Reporting Services
03/09/2007 14:04:03.562 details = Service Pack for the Report Server and Report Builder, which manages, executes, renders, and distributes reports.
03/09/2007 14:04:03.593 installer = Hotfix
03/09/2007 14:04:03.625 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:03.687 kbarticle = KB921896
03/09/2007 14:04:03.734 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:03.765 lcid = 1033
03/09/2007 14:04:03.796 legalproductname = SQL Server Reporting Services 2005
03/09/2007 14:04:03.843 machinetype = x86
03/09/2007 14:04:03.875 package = HotFixRS
03/09/2007 14:04:03.890 packagetype = Hotfix
03/09/2007 14:04:03.921 productname = RS9
03/09/2007 14:04:03.953 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:03.968 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:04.000 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/09/2007 14:04:04.015 splevel = 2
03/09/2007 14:04:04.046 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:04.078 sqlutility = sqlcmd.exe
03/09/2007 14:04:04.093 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:04.125 validateauthentication = 1
03/09/2007 14:04:04.140 version = 9
03/09/2007 14:04:04.171
03/09/2007 14:04:04.203 File Group Details: MSP
03/09/2007 14:04:04.234 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/09/2007 14:04:04.250 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:04.281 File Details: sqlrun_rs.msp
03/09/2007 14:04:04.296
03/09/2007 14:04:04.328 Product Enumeration Results:
03/09/2007 14:04:04.359 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixDTS.inf
03/09/2007 14:04:04.375 baselinebuild = 1399
03/09/2007 14:04:04.406 baselinebuildmax = 3042
03/09/2007 14:04:04.421 build = 3042
03/09/2007 14:04:04.453 description = Integration Services
03/09/2007 14:04:04.484 details = Service Pack for Integration Services, a set of tools and programmable objects used to create and manage packages that extract, transform, and load data, as well as perform tasks.
03/09/2007 14:04:04.500 installer = Hotfix
03/09/2007 14:04:04.531 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:04.562 kbarticle = KB921896
03/09/2007 14:04:04.578 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:04.609 lcid = 1033
03/09/2007 14:04:04.625 legalproductname = SQL Server Integration Services 2005
03/09/2007 14:04:04.656 machinetype = x86
03/09/2007 14:04:04.687 package = HotFixDTS
03/09/2007 14:04:04.703 packagetype = Hotfix
03/09/2007 14:04:04.734 productname = DTS9
03/09/2007 14:04:04.765 recommendinstall = 1
03/09/2007 14:04:04.796 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:04.812 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:04.843 splevel = 2
03/09/2007 14:04:04.875 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:04.906 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:04.921 version = 9
03/09/2007 14:04:04.953
03/09/2007 14:04:04.984 File Group Details: MSP
03/09/2007 14:04:05.000 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/09/2007 14:04:05.031 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:05.046 File Details: sqlrun_dts.msp
03/09/2007 14:04:05.078
03/09/2007 14:04:05.109 Instance Details: Integration Services
03/09/2007 14:04:05.125 associatedhotfixbuild = 0
03/09/2007 14:04:05.156 clustername =
03/09/2007 14:04:05.171 dtsservicename = MsDtsServer
03/09/2007 14:04:05.203 fullversion = 9.00.2047.00
03/09/2007 14:04:05.234 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90DTS
03/09/2007 14:04:05.265 id =
03/09/2007 14:04:05.281 installsqldatadir =
03/09/2007 14:04:05.312 installsqldir = C:Program FilesMicrosoft SQL Server90DTS
03/09/2007 14:04:05.328 lcid = 1033
03/09/2007 14:04:05.375 name =
03/09/2007 14:04:05.390 productcode = {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
03/09/2007 14:04:05.421 qfelevel = 2047
03/09/2007 14:04:05.453 servicename = MsDtsServer
03/09/2007 14:04:05.484 sku = STANDARD
03/09/2007 14:04:05.515 sp = 1
03/09/2007 14:04:05.546 type = Tools Only
03/09/2007 14:04:05.578 vermajbld = 2047
03/09/2007 14:04:05.593 version = 9
03/09/2007 14:04:05.625
03/09/2007 14:04:05.656 Product Enumeration Results:
03/09/2007 14:04:05.671 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixTools.inf
03/09/2007 14:04:05.703 baselinebuild = 1399
03/09/2007 14:04:05.718 baselinebuildmax = 3042
03/09/2007 14:04:05.750 build = 3042
03/09/2007 14:04:05.781 description = Client Components
03/09/2007 14:04:05.796 details = Service Pack for the interactive management tools for running SQL Server, including SQL Server Configuration Manager, SQL Server Management Studio, SQL Profiler, and Replication Monitor.
03/09/2007 14:04:05.828 installer = Hotfix
03/09/2007 14:04:05.859 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:05.875 kbarticle = KB921896
03/09/2007 14:04:05.906 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:05.921 lcid = 1033
03/09/2007 14:04:05.953 legalproductname = SQL Server Tools and Workstation Components 2005
03/09/2007 14:04:05.984 machinetype = x86
03/09/2007 14:04:06.000 package = HotFixTools
03/09/2007 14:04:06.031 packagetype = Hotfix
03/09/2007 14:04:06.046 productname = SQLTools9
03/09/2007 14:04:06.078 recommendinstall = 1
03/09/2007 14:04:06.109 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:06.125 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:06.156 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
03/09/2007 14:04:06.171 splevel = 2
03/09/2007 14:04:06.203 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:06.234 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:06.250 version = 9
03/09/2007 14:04:06.281
03/09/2007 14:04:06.296 File Group Details: MSP
03/09/2007 14:04:06.328 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
03/09/2007 14:04:06.359 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:06.375 File Details: sqlrun_tools.msp
03/09/2007 14:04:06.406
03/09/2007 14:04:06.421 Instance Details: SQL Tools
03/09/2007 14:04:06.453 associatedhotfixbuild = 0
03/09/2007 14:04:06.468 clustername =
03/09/2007 14:04:06.500 fullversion = 9.1.2047
03/09/2007 14:04:06.531 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
03/09/2007 14:04:06.546 id =
03/09/2007 14:04:06.578 installsqldatadir =
03/09/2007 14:04:06.593 installsqldir = C:Program FilesMicrosoft SQL Server90Tools
03/09/2007 14:04:06.625 lcid = 1033
03/09/2007 14:04:06.656 name =
03/09/2007 14:04:06.671 productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
03/09/2007 14:04:06.703 qfelevel = 2047
03/09/2007 14:04:06.718 sku = STANDARD
03/09/2007 14:04:06.750 sp = 1
03/09/2007 14:04:06.781 type = Tools Only
03/09/2007 14:04:06.796 vermajbld = 2047
03/09/2007 14:04:06.828 version = 9
03/09/2007 14:04:06.843
03/09/2007 14:04:06.875 Product Enumeration Results:
03/09/2007 14:04:06.906 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixMsxml6.inf
03/09/2007 14:04:06.937 baselinebuild = 1399
03/09/2007 14:04:06.968 build = 6.10.1129.0
03/09/2007 14:04:07.000 description = MSXML 6.0 Parser
03/09/2007 14:04:07.031 details = Service Pack for Microsoft XML 6.0 Parser.
03/09/2007 14:04:07.062 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:07.093 kbarticle = KB921896
03/09/2007 14:04:07.125 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:07.156 lcid = 1033
03/09/2007 14:04:07.187 legalproductname = MSXML 6.0 Parser
03/09/2007 14:04:07.218 machinetype = x86
03/09/2007 14:04:07.250 package = HotFixMsxml6
03/09/2007 14:04:07.281 packagetype = Hotfix
03/09/2007 14:04:07.312 productcode = {5A710547-B58E-488B-828D-CA9A25A0533C}
03/09/2007 14:04:07.343 productname = Redist9
03/09/2007 14:04:07.375 recommendinstall = 1
03/09/2007 14:04:07.406 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:07.437 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:07.468 splevel = 2
03/09/2007 14:04:07.500 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:07.531 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:07.562 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
03/09/2007 14:04:07.593 version = 9
03/09/2007 14:04:07.625
03/09/2007 14:04:07.656 File Group Details: MSI
03/09/2007 14:04:07.687 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:07.718 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:07.750 File Details: msxml6.msi
03/09/2007 14:04:07.781
03/09/2007 14:04:07.812 Instance Details: MSXML 6.0 Parser
03/09/2007 14:04:07.843 fullversion = 6.00.3890.0
03/09/2007 14:04:07.875 lcid = 1033
03/09/2007 14:04:07.906 productcode = {5A710547-B58E-488B-828D-CA9A25A0533C}
03/09/2007 14:04:07.937 qfelevel = 3890
03/09/2007 14:04:07.968 sp = -1
03/09/2007 14:04:08.000
03/09/2007 14:04:08.031 Product Enumeration Results:
03/09/2007 14:04:08.046 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixMsxml6_x64.inf
03/09/2007 14:04:08.093 baselinebuild = 1399
03/09/2007 14:04:08.125 build = 6.10.1129.0
03/09/2007 14:04:08.140 description = MSXML 6.0 Parser
03/09/2007 14:04:08.171 details = Service Pack for Microsoft XML 6.0 Parser.
03/09/2007 14:04:08.203 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:08.250 kbarticle = KB921896
03/09/2007 14:04:08.281 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:08.312 lcid = 1033
03/09/2007 14:04:08.328 legalproductname = MSXML 6.0 Parser (64-bit)
03/09/2007 14:04:08.359 machinetype = x64
03/09/2007 14:04:08.390 package = HotFixMsxml6_x64
03/09/2007 14:04:08.421 packagetype = Hotfix
03/09/2007 14:04:08.468 productname = Redist9
03/09/2007 14:04:08.484 recommendinstall = 1
03/09/2007 14:04:08.515 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:08.546 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:08.578 splevel = 2
03/09/2007 14:04:08.609 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:08.640 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
03/09/2007 14:04:08.671 version = 9
03/09/2007 14:04:08.703
03/09/2007 14:04:08.734 File Group Details: MSI
03/09/2007 14:04:08.765 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:08.796 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:08.828 File Details: msxml6_x64.msi
03/09/2007 14:04:08.859
03/09/2007 14:04:08.890 Product Enumeration Results:
03/09/2007 14:04:08.921 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSqlxml4.inf
03/09/2007 14:04:08.953 baselinebuild = 1399
03/09/2007 14:04:08.984 build = 3042
03/09/2007 14:04:09.015 description = SQLXML4
03/09/2007 14:04:09.046 details = Service Pack for Microsoft SQLXML 4.0.
03/09/2007 14:04:09.078 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:09.109 kbarticle = KB921896
03/09/2007 14:04:09.140 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:09.171 lcid = 1033
03/09/2007 14:04:09.203 legalproductname = SQLXML4
03/09/2007 14:04:09.234 machinetype = x86
03/09/2007 14:04:09.265 package = HotFixSqlxml4
03/09/2007 14:04:09.296 packagetype = Hotfix
03/09/2007 14:04:09.328 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
03/09/2007 14:04:09.359 productname = Redist9
03/09/2007 14:04:09.375 recommendinstall = 1
03/09/2007 14:04:09.406 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:09.453 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:09.484 splevel = 2
03/09/2007 14:04:09.515 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:09.531 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:09.562 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
03/09/2007 14:04:09.609 version = 9
03/09/2007 14:04:09.640
03/09/2007 14:04:09.656 File Group Details: MSI
03/09/2007 14:04:09.687 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:09.718 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:09.750 File Details: sqlxml4.msi
03/09/2007 14:04:09.796
03/09/2007 14:04:09.812 Instance Details: SQLXML4
03/09/2007 14:04:09.843 fullversion = 9.00.2047.00
03/09/2007 14:04:09.875 lcid = 1033
03/09/2007 14:04:09.906 productcode = {A188FCCF-E929-494D-B1F1-4313E02ACD52}
03/09/2007 14:04:09.937 qfelevel = 2047
03/09/2007 14:04:09.968 sp = -1
03/09/2007 14:04:10.000
03/09/2007 14:04:10.031 Product Enumeration Results:
03/09/2007 14:04:10.062 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSqlxml4_x64.inf
03/09/2007 14:04:10.093 baselinebuild = 1399
03/09/2007 14:04:10.125 build = 3042
03/09/2007 14:04:10.156 description = SQLXML4
03/09/2007 14:04:10.187 details = Service Pack for Microsoft SQLXML 4.0.
03/09/2007 14:04:10.218 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:10.250 kbarticle = KB921896
03/09/2007 14:04:10.281 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:10.312 lcid = 1033
03/09/2007 14:04:10.343 legalproductname = SQLXML4 (64-bit)
03/09/2007 14:04:10.375 machinetype = x64
03/09/2007 14:04:10.406 package = HotFixSqlxml4_x64
03/09/2007 14:04:10.437 packagetype = Hotfix
03/09/2007 14:04:10.468 productname = Redist9
03/09/2007 14:04:10.500 recommendinstall = 1
03/09/2007 14:04:10.531 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:10.562 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:10.593 splevel = 2
03/09/2007 14:04:10.625 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:10.656 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
03/09/2007 14:04:10.687 version = 9
03/09/2007 14:04:10.718
03/09/2007 14:04:10.750 File Group Details: MSI
03/09/2007 14:04:10.781 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:10.812 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:10.843 File Details: sqlxml4_x64.msi
03/09/2007 14:04:10.875
03/09/2007 14:04:10.906 Product Enumeration Results:
03/09/2007 14:04:10.937 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSQLServer2005_BC.inf
03/09/2007 14:04:10.968 baselinebuild = 1399
03/09/2007 14:04:11.000 build = 2004
03/09/2007 14:04:11.031 description = Backward Compatibility
03/09/2007 14:04:11.062 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
03/09/2007 14:04:11.093 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:11.125 kbarticle = KB921896
03/09/2007 14:04:11.156 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:11.187 lcid = 1033
03/09/2007 14:04:11.218 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
03/09/2007 14:04:11.250 machinetype = x86
03/09/2007 14:04:11.281 package = HotFixSQLServer2005_BC
03/09/2007 14:04:11.312 packagetype = Hotfix
03/09/2007 14:04:11.343 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
03/09/2007 14:04:11.375 productname = Redist9
03/09/2007 14:04:11.406 recommendinstall = 1
03/09/2007 14:04:11.437 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:11.468 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:11.500 splevel = 2
03/09/2007 14:04:11.531 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:11.562 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:11.593 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
03/09/2007 14:04:11.625 version = 9
03/09/2007 14:04:11.656
03/09/2007 14:04:11.687 File Group Details: MSI
03/09/2007 14:04:11.718 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:11.750 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:11.781 File Details: SQLServer2005_BC.msi
03/09/2007 14:04:11.812
03/09/2007 14:04:11.843 Instance Details: Backward Compatibility
03/09/2007 14:04:11.875 fullversion = 8.05.1704
03/09/2007 14:04:11.906 lcid = 1033
03/09/2007 14:04:11.937 productcode = {2243F21A-E132-44F7-BA13-024D0845C815}
03/09/2007 14:04:11.968 qfelevel = 1704
03/09/2007 14:04:12.000 sp = -1
03/09/2007 14:04:12.031
03/09/2007 14:04:12.062 Product Enumeration Results:
03/09/2007 14:04:12.093 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSQLServer2005_BC_x64.inf
03/09/2007 14:04:12.125 baselinebuild = 1399
03/09/2007 14:04:12.156 build = 2004
03/09/2007 14:04:12.187 description = Backward Compatibility
03/09/2007 14:04:12.218 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
03/09/2007 14:04:12.250 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:12.281 kbarticle = KB921896
03/09/2007 14:04:12.296 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:12.343 lcid = 1033
03/09/2007 14:04:12.375 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
03/09/2007 14:04:12.406 machinetype = x64
03/09/2007 14:04:12.437 package = HotFixSQLServer2005_BC_x64
03/09/2007 14:04:12.453 packagetype = Hotfix
03/09/2007 14:04:12.484 productname = Redist9
03/09/2007 14:04:12.515 recommendinstall = 1
03/09/2007 14:04:12.546 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:12.578 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:12.609 splevel = 2
03/09/2007 14:04:12.640 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:12.671 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
03/09/2007 14:04:12.703 version = 9
03/09/2007 14:04:12.734
03/09/2007 14:04:12.765 File Group Details: MSI
03/09/2007 14:04:12.796 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:12.828 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:12.859 File Details: SQLServer2005_BC_x64.msi
03/09/2007 14:04:12.890
03/09/2007 14:04:12.921 Product Enumeration Results:
03/09/2007 14:04:12.968 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSqlWriter.inf
03/09/2007 14:04:12.984 baselinebuild = 1399
03/09/2007 14:04:13.015 build = 3042
03/09/2007 14:04:13.046 description = Microsoft SQL Server VSS Writer
03/09/2007 14:04:13.078 details = Service Pack for Microsoft SQL Server VSS Writer.
03/09/2007 14:04:13.109 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:13.140 kbarticle = KB921896
03/09/2007 14:04:13.171 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:13.203 lcid = 1033
03/09/2007 14:04:13.234 legalproductname = Microsoft SQL Server VSS Writer
03/09/2007 14:04:13.265 machinetype = x86
03/09/2007 14:04:13.296 package = HotFixSqlWriter
03/09/2007 14:04:13.328 packagetype = Hotfix
03/09/2007 14:04:13.359 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
03/09/2007 14:04:13.390 productname = Redist9
03/09/2007 14:04:13.421 recommendinstall = 1
03/09/2007 14:04:13.453 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:13.484 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:13.515 splevel = 2
03/09/2007 14:04:13.546 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
03/09/2007 14:04:13.578 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:13.609 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
03/09/2007 14:04:13.640 version = 9
03/09/2007 14:04:13.671
03/09/2007 14:04:13.703 File Group Details: MSI
03/09/2007 14:04:13.734 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:13.765 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:13.796 File Details: SqlWriter.msi
03/09/2007 14:04:13.828
03/09/2007 14:04:13.859 Instance Details: Microsoft SQL Server VSS Writer
03/09/2007 14:04:13.890 fullversion = 9.00.2047.00
03/09/2007 14:04:13.921 lcid = 1033
03/09/2007 14:04:13.953 productcode = {C0D2F614-5CE5-4DCB-8678-E5C9AF7044F8}
03/09/2007 14:04:13.984 qfelevel = 2047
03/09/2007 14:04:14.015 sp = -1
03/09/2007 14:04:14.046
03/09/2007 14:04:14.078 Product Enumeration Results:
03/09/2007 14:04:14.109 INF File Name: c:57a10d1e173eea2efd90865f30137638HotFixSqlWriter_x64.inf
03/09/2007 14:04:14.140 baselinebuild = 1399
03/09/2007 14:04:14.156 build = 3042
03/09/2007 14:04:14.187 description = Microsoft SQL Server VSS Writer
03/09/2007 14:04:14.234 details = Service Pack for Microsoft SQL Server VSS Writer.
03/09/2007 14:04:14.265 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
03/09/2007 14:04:14.296 kbarticle = KB921896
03/09/2007 14:04:14.312 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
03/09/2007 14:04:14.343 lcid = 1033
03/09/2007 14:04:14.390 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
03/09/2007 14:04:14.421 machinetype = x64
03/09/2007 14:04:14.437 package = HotFixSqlWriter_x64
03/09/2007 14:04:14.468 packagetype = Hotfix
03/09/2007 14:04:14.500 productname = Redist9
03/09/2007 14:04:14.531 recommendinstall = 1
03/09/2007 14:04:14.578 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
03/09/2007 14:04:14.593 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
03/09/2007 14:04:14.625 splevel = 2
03/09/2007 14:04:14.656 supportdir = c:57a10d1e173eea2efd90865f30137638
03/09/2007 14:04:14.687 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
03/09/2007 14:04:14.703 version = 9
03/09/2007 14:04:14.734
03/09/2007 14:04:14.765 File Group Details: MSI
03/09/2007 14:04:14.796 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
03/09/2007 14:04:14.828 sourcepath = <SUPPORTDIR><PACKAGE>Files
03/09/2007 14:04:14.859 File Details: SqlWriter_x64.msi
03/09/2007 14:04:14.890
03/09/2007 14:04:20.125 Registry: Opened registry key "SystemCurrentControlSetControlSession Manager"
03/09/2007 14:04:20.156 Registry: Cannot read registry key value "PendingFileRenameOperations"
03/09/2007 14:04:21.203 Authenticating user using Windows Authentication
03/09/2007 14:04:21.234 SQL Service MSSQLServer was previously running, ready for authentication
03/09/2007 14:04:21.265 SQL Agent Service SQLSERVERAGENT was previously running
03/09/2007 14:04:21.593 Authenticating user using Windows Authentication
03/09/2007 14:04:21.625 Validating database connections using Windows Authentication
03/09/2007 14:04:21.796 Pre-script database connection check was successful - proceeding with script execution
03/09/2007 14:04:21.968 Received sysadmin status for instance: MSSQLSERVER
03/09/2007 14:04:22.000 Validating database connections using Windows Authentication
03/09/2007 14:04:22.187 Pre-script database connection check was successful - proceeding with script execution
03/09/2007 14:04:22.218 User authentication was successful
03/09/2007 14:04:22.265 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
03/09/2007 14:04:22.296 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
03/09/2007 14:04:22.328 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
03/09/2007 14:04:22.359 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
03/09/2007 14:04:23.390 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
03/09/2007 14:04:23.421 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
03/09/2007 14:04:23.437 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
03/09/2007 14:04:23.468 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
03/09/2007 14:04:23.531 Locked file: Checking for locked files
03/09/2007 14:04:24.031 Locked file: C:WINDOWSsystem32sqlncli.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:24.046 Locked file: C:WINDOWSsystem32sqlncli.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:26.000 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnmsftesql.exe (msftesql [msftesql.exe] - 4944)
03/09/2007 14:04:26.046 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnmsftepxy.dll (msftesql [msftesql.exe] - 4944)
03/09/2007 14:04:26.093 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnmsftepxy.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:26.218 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnmsfte.dll (msftesql [msftesql.exe] - 4944)
03/09/2007 14:04:26.250 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnmsfte.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:27.703 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinn
esources1033sqlevn70.rll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:27.843 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinn
esources1033xpstar90.rll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:27.937 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinndbghelp.dll (msftesql [msftesql.exe] - 4944)
03/09/2007 14:04:27.984 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinndbghelp.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:28.312 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqlsvc90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:28.359 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnxpstar90.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:28.406 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqlos.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:28.484 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnxpsqlbot.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:28.515 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnxplog70.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:28.546 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqlservr.exe (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:28.656 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnatchparser90.dll (MSSQLSERVER [sqlservr.exe] - 4956)
03/09/2007 14:04:28.687 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnatchparser90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:28.750 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinn
esources1033sqlagent90.rll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:28.812 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqldtsss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:28.843 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqlrepss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:28.875 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqlolapss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:28.921 Locked file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLinnsqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 4312)
03/09/2007 14:04:36.203 Attempting to pause the 32 bit ngen queue
03/09/2007 14:04:36.968 Installing product: Redist9
03/09/2007 14:04:37.000 Installing instance: Setup Support Files
03/09/2007 14:04:37.046 Installing target: BVTBIQA
03/09/2007 14:04:37.109 Installing file: SqlSupport.msi
03/09/2007 14:04:37.250 Copy Engine: Creating MSI install log file at: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixRedist9_Hotfix_KB921896_SqlSupport.msi.log
03/09/2007 14:04:37.281 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
03/09/2007 14:04:37.312 Registry: Cannot read registry key value "Debug"
03/09/2007 14:04:40.359 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
03/09/2007 14:04:40.390 Registry: Cannot read registry key value "Debug"
03/09/2007 14:04:40.421 Copy Engine: Error, unable to install MSI file: C:Program FilesMicrosoft SQL Server90Setup BootstrapCacheSQLSupportx861033SqlSupport.msi
03/09/2007 14:04:40.453 The following exception occurred: Unable to install Windows Installer MSI file Date: 03/09/2007 14:04:40.453 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 1378
03/09/2007 14:04:47.171 Watson: Param1 = Unknown
03/09/2007 14:04:47.218 Watson: Param2 = 0x652
03/09/2007 14:04:47.250 Watson: Param3 = Unknown
03/09/2007 14:04:47.296 Watson: Param4 = 0x652
03/09/2007 14:04:47.343 Watson: Param5 = copyengine.cpp@1378
03/09/2007 14:04:47.375 Watson: Param6 = Unknown
03/09/2007 14:04:47.421 Watson: Param7 = Redist9
03/09/2007 14:04:47.453 Watson: Param8 = @
03/09/2007 14:04:47.515 Watson: Param9 = x86
03/09/2007 14:04:47.546 Watson: Param10 = 3042
03/09/2007 14:04:47.593 Attempting to continue the 32 bit ngen queue
03/09/2007 14:04:53.984 Watson: Param1 = Unknown
03/09/2007 14:04:54.015 Watson: Param2 = 0x643
03/09/2007 14:04:54.046 Watson: Param3 = Unknown
03/09/2007 14:04:54.078 Watson: Param4 = 0x652
03/09/2007 14:04:54.125 Watson: Param5 = copyengine.cpp@1378
03/09/2007 14:04:54.140 Watson: Param6 = Unknown
03/09/2007 14:04:54.171 Watson: Param7 = Redist9
03/09/2007 14:04:54.203 Watson: Param8 = @
03/09/2007 14:04:54.234 Watson: Param9 = x86
03/09/2007 14:04:54.265 Watson: Param10 = 3042
View 10 Replies
View Related
Sep 5, 2007
Hi, I upgraded to Vista and then re-installed Sql Server 2005 and then installed SP2. When I choose "Connect to Server" in Management studio I have no choice for "Server Name". If I type in the computer name (which is what the local server used to be) I get a logon error, but I chose windows authentication in setup. Please help. Thanks!
View 1 Replies
View Related
Apr 14, 2006
I downloaded the 2 CD ISO Format from msdn to install SQL Server 2005 English Developer Edition on my XP SP2 box.
I currently have SQL 2000 running. So Sql Server 2005 Dev Edition is to run side by side in a named instance.
From CD1, I launched default.hta and could not install Database Services. The log mentioned could not find a 'valid copy of xxx.msi' where xxx is VSS writer, Database Services or SQL XML4 etc...
I tried 3 times and each time it damaged my SQL2000 beyond repair.
Any suggestions will be much appreciated. Thanks
View 4 Replies
View Related
Sep 18, 2006
I am getting an error saying incorrect syntax near fIt works in SQL Server 2005, but I cannot get it to work in SQL Server 2000 The error appears to be in the section that I marked in Bold. CREATE PROCEDURE [dbo].[pe_getReport] -- Add the parameters for the stored procedure here @BranchID INT, @InvestorID INT, @Status INT, @QCAssigned INT, @LoanOfficer nvarChar(40), @FromCloseDate DateTime, @ToCloseDate DateTime, @OrderBy nvarChar(50)ASDECLARE @l_Sql NVarChar(4000), @l_OrderBy NVarChar(500), @l_OrderCol NVarChar(150), @l_CountSql NVarChar(4000), @l_Where NVarChar(4000), @l_SortDir nvarChar(4)BEGIN -- SET NOCOUNT ON added to prevent extra result sets from -- interfering with SELECT statements. SET NOCOUNT ON; SET @l_Where = N' Where 1=1' IF (@BranchID IS NOT NULL) SET @l_Where = @l_Where + N' AND f.BranchID=' + CAST(@BranchID As NVarChar) IF (@Status IS NOT NULL) SET @l_Where = @l_Where + N' AND f.Status=' + CAST(@Status As NVarChar) IF (@InvestorID IS NOT NULL) SET @l_Where = @l_Where + N' AND f.InvestorID=' + CAST(@InvestorID As NVarChar) IF (@QCAssigned IS NOT NULL) SET @l_Where = @l_Where + N' AND f.QCAssigned=' + CAST(@QCAssigned As NVarChar) IF (@LoanOfficer IS NOT NULL) SET @l_Where = @l_Where + N' AND f.LoanOfficer LIKE ''' + @LoanOfficer + '%''' IF (@FromCloseDate IS NOT NULL) SET @l_Where = @l_Where + N' AND f.ClosingDate>=''' + CAST(@FromCloseDate AS NVarChar) + '''' IF (@ToCloseDate IS NOT NULL) SET @l_Where = @l_Where + N' AND f.ClosingDate<=''' + CAST(@ToCloseDate AS NVarChar) + '''' IF @OrderBy IS NULL SET @OrderBy = 'DateEntered DESC' SET @l_SortDir = SUBSTRING(@OrderBy, CHARINDEX(' ', @OrderBy) + 1, LEN(@OrderBy)) SET @l_OrderCol = SUBSTRING(@OrderBy, 1, NULLIF(CHARINDEX(' ', @OrderBy) - 1, -1)) IF @l_OrderCol = 'InvestorName' SET @l_OrderBy = 'i.InvestorName ' + @l_SortDir ELSE IF @l_OrderCol = 'BName' SET @l_OrderBy = 'b.BName ' + @l_SortDir ELSE IF @l_OrderCol = 'StatusDesc' SET @l_OrderBy = 's.StatusDesc ' + @l_SortDir ELSE IF @l_OrderCol = 'QCAssigned' SET @l_OrderBy = 'q.LoginName ' + @l_SortDir ELSE SET @l_OrderBy = 'f.' + @l_OrderCol + ' ' + @l_SortDir SET @l_CountSql = 'SELECT f.FundedID As FundedID FROM FundedInfo AS f LEFT OUTER JOIN Investors AS i ON f.InvestorID = i.InvestorID LEFT OUTER JOIN Branches AS b ON f.BranchID = b.BranchID LEFT OUTER JOIN Status AS s ON f.Status = s.StatusID LEFT OUTER JOIN QCLogins AS q f.QCAssigned = q.LoginID ' + @l_Where + ' ORDER BY ' + @l_OrderBy CREATE TABLE #RsltTable (ID int IDENTITY PRIMARY KEY, FundedID int) INSERT INTO #RsltTable(FundedID) EXECUTE (@l_CountSql)SELECT f.DateEntered As DateEntered, f.LastName As LastName, f.LoanNumber As LoanNumber, f.LoanOfficer As LoanOfficer, f.ClosingDate As ClosingDate, i.InvestorName As InvestorName, b.BName As BName, s.StatusDesc As StatusDesc, q.LoginName As LoginNameFROM FundedInfo AS f LEFT OUTER JOIN Investors AS i ON f.InvestorID = i.InvestorID LEFT OUTER JOIN Branches AS b ON f.BranchID = b.BranchID LEFT OUTER JOIN Status AS s ON f.Status = s.StatusID LEFT OUTER JOIN QCLogins As q ON f.QCAssigned = q.LoginID WHERE FundedID IN(SELECT FundedID FROM #rsltTable) ORDER BY CASE @OrderBy WHEN 'DateEntered ASC' THEN f.DateEntered END ASC, CASE @OrderBy WHEN 'DateEntered DESC' THEN f.DateEntered END DESC, CASE @OrderBy WHEN 'LastName ASC' THEN f.LastName END ASC, CASE @OrderBy WHEN 'LastName DESC' THEN f.LastName END DESC, CASE @OrderBy WHEN 'LoanNumber ASC' THEN f.LoanNumber END ASC, CASE @OrderBy WHEN 'LoanNumber DESC' THEN f.LoanNumber END DESC, CASE @OrderBy WHEN 'LoanOfficer ASC' THEN f.LoanOfficer END ASC, CASE @OrderBy WHEN 'LoanOfficer DESC' THEN f.LoanOfficer END DESC, CASE @OrderBy WHEN 'ClosingDate ASC' THEN f.ClosingDate END ASC, CASE @OrderBy WHEN 'ClosingDate DESC' THEN f.ClosingDate END DESC, CASE @OrderBy WHEN 'InvestorName ASC' THEN i.InvestorName END ASC, CASE @OrderBy WHEN 'InvestorName DESC' THEN i.InvestorName END DESC, CASE @OrderBy WHEN 'BName ASC' THEN b.BName END ASC, CASE @OrderBy WHEN 'BName DESC' THEN b.BName END DESC, CASE @OrderBy WHEN 'StatusDesc ASC' THEN s.StatusDesc END ASC, CASE @OrderBy WHEN 'StatusDesc DESC' THEN s.StatusDesc END DESC, CASE @OrderBy WHEN 'LoginName ASC' THEN q.LoginName END ASC, CASE @OrderBy WHEN 'LoginName DESC' THEN q.LoginName END DESCENDGO
View 2 Replies
View Related
Jun 14, 2007
I created a stored procedure (see snippet below) and the owner is "dbo".
I created a data connection (slcbathena.SLCPrint.AdamsK) using Windows authentication.
I added a new datasource to my application in VS 2005 which created a dataset (slcprintDataSet.xsd).
I opened up the dataset in Designer so I could get to the table adapter.
I selected the table adapter and went to the properties panel.
I changed the DeleteCommand as follows: CommandType = StoredProcedure; CommandText = usp_OpConDeleteDirectory. When I clicked on the Parameters Collection to pull up the Parameters Collection Editor, there was no parameters listed to edit even though there is one defined in the stored procedure. Why?
If I create the stored procedure as "AdamsK.usp_OpConDeleteDirectory", the parameters show up correctly in the Parameters Collection Editor. Is there a relationship between the owner name of the stored procedure and the data connection name? If so, how can I create a data connection that uses "dbo" instead of "AdamsK" so I can use the stored procedure under owner "dbo"?
Any help will be greatly appreciated!
Code SnippetCREATE PROCEDURE dbo.usp_OpConDeleteDirectory
(
@DirectoryID int
)
AS
SET NOCOUNT ON
DELETE FROM OpConDirectories WHERE (DirectoryID = @DirectoryID)
View 1 Replies
View Related
Dec 4, 2007
Hi,
We have (after several weeks of testing in all kind of environments) send out a new version of our application to several of our customers. Within days problems where drippin in; After looking for the problem on various customer situations we found a problem which I think is rather disturbing and very odd. I'll describe the situation, on which we finally managed to recreate the problem, here.
In my problem I use the following configuration:
Windows 2003 (standard edition) AD network with 2 domain controllers, multiple Windows XP workstations, some without SQL instances, some with SQL 2000 instances, some with SQL 2005 instances and even one with SQL 7 running.
All run a 32 bit OS.
Tools to reproduce:
ListSQLSvr application (found on SQLDev.net) to enumerate the instances.
Problem description:
--------------------------------------------------
I am running the machine called DEV001, which has SQL 2000 (instancename DRUMIS) and SQL 7.0 (has no instancename so this is the root instance) installed.
In any 'normal' situation all the runnings SQL instances are visible on the network like this:
Code Block
C:>listsqlsvr -X
(local);Clustered:No;Version:7.00.623
ADM002DRUMIS;Clustered:No;Version:8.00.194
DEV001DRUMIS
DEV001DRUMIS;Clustered:No;Version:8.00.194
DEV002DRUMIS;Clustered:No;Version:8.00.194
DEV002EXPRESS;Clustered:No;Version:9.00.3042.00
DEV002EXPRESS
INSADBACKOFFICEDRUMIS;Clustered:No;Version:8.00.194
INSADBACKOFFICEEXACT;Clustered:No;Version:9.00.3042.00
INSADOFFICEWSUS;Clustered:No;Version:8.00.194
SUP001DRUMIS;Clustered:No;Version:8.00.194
When I turn the SQL 2005 Browser service off on the machine called DEV002 the list looks like:
Code Block
C:>listsqlsvr -X
(local);Clustered:No;Version:7.00.623
ADM002DRUMIS;Clustered:No;Version:8.00.194
DEV001DRUMIS;Clustered:No;Version:8.00.194
DEV001DRUMIS
DEV002
DEV002EXPRESS
DEV004DRUMIS;Clustered:No;Version:9.00.3042.00
INSADBACKOFFICEDRUMIS;Clustered:No;Version:8.00.194
INSADBACKOFFICEEXACT;Clustered:No;Version:9.00.3042.00
INSADOFFICEWSUS;Clustered:No;Version:8.00.194
SUP001DRUMIS;Clustered:No;Version:8.00.194
Notice that the browser service might be off on DEV002, you can still see the EXPRESS instance and a new root instance has appeared (though it doesn't exist!)??
After restarting the Browser service all is OK again.
When I turn on Hide Server in the SQL 2000 TCP/IP properties (or turn it on in the registry [HKEY_LOCAL_MACHINESOFTWAREMicrosoftMicrosoft SQL ServerDRUMISMSSQLServerSuperSocketNetLibTcp] "TcpHideFlag"=dword:00000001) on the DEV002 computer something real scary is happening..
The list looks as follows:
Code Block
C:listsqlsvr -X
(local)
ADM002
DEV001
DEV002
DEV004
INSADBACKOFFICE
INSADOFFICE
SUP001
When someone has entered a database (for example the backoffice database on INSADBACKOFFICEEXACT) the list looks as follows (for a short moment; 5 secs or so):
Code Block
C:listsqlsvr -X
(local)
ADM002
DEV001
DEV002
DEV004
INSADBACKOFFICEDEVELOP;Clustered:No;Version:8.00.194
INSADBACKOFFICEDRUMIS;Clustered:No;Version:8.00.194
INSADBACKOFFICEEXACT;Clustered:No;Version:9.00.3042.00
INSADOFFICE
SUP001
Notice now that ALL instances are gone and no extended information is available. In the Query Analyser and in the SQL Management Studio when browsing you'll see this as well!
When someone is accessing a database instance it appears for a few seconds again.
Since our installation and applications rely on selecting a existing instance it will fail in the above situations (or at least not showing all available instances).
In my opinion this is a bug somewhere!
Note that even when the SQL Services are stopped on DEV002 (leaving the Browser service running) it still seems to block out ALL instance on the ENTIRE network!
I don't mind that one INSTANCE or even the entire MACHINE is hidden from the network, but ALL instances on ALL machines??
And the SQL Browser issue also worries me a bit since it does not stop the possibily to browse the SQL instances; it removes the SQL2000 instances but adds a root instance which doesn't even exist! Also the extended info is stripped.
Can anyone help me solve this/advise?
Also mind that in any situation there might run a lot of computers with a lot of SQL instances and I cannot tell our customers to find which machine has the SQL TCP/IP properties set to Hide...
It even seems that in some situations SBS 2003 does the hiding automatically on Install? And if so, when and why?
Regards,
Albert van Peppen
Senior System Engineer
Insad Grafisch b.v.
View 31 Replies
View Related
Sep 29, 2006
I had SQL Server Express Edition installed. I then uninstalled both it and Visual C#. I then installed SQL Server 2005 Developer's Edition and reinstalled Visual C# -- both on the same machine. I can connect to SQL Server 2005 using SQL Server Management Studio. However, Visual C# is a different story. When I try to add a new Data Connection, it defaults the data source to .SQLEXPRESS, which is no longer on my machine. I can select .MSSQLSERVER, but when I click on either OK or Test Connection, I time out with an error message -- error 25 - Connection string is not valid. The connection string that is shown at the bottom of the Advanced dialog box is -- Data Source=.MSSQLSERVER;AttachDbFilename=E:InventoryDataInventory_Data.MDF;Integrated Security=True;Connect Timeout=30;User Instance=True
View 12 Replies
View Related
Apr 14, 2008
ok so i have set up SQL server 2005 on a Windows server 2003 machine. I am trying to connect to it via ODBC and/or Visual Studio 2005 on a computer running off the same switch. I have set SQL server to accept remote connections and named pipes as well as had the port unblocked. when i try and connect to it via Vista ODBC wizard or visual studio wizard it says that the server is not there or access is denied.
The server is set up for SQL authentication and i am 100% pos that the username/password i am using is correct. i am at a total loss as to what to do to get my vista machine to talk to that SQL server.
View 1 Replies
View Related
Sep 22, 2006
Hi all,
I have a SQL Server 2005 Express edition instance set up on one server, and IIS on another server.
The SQL Server process account is a domain user account, which I have added to the local groups that SQL Server created during installation (I originally used a local user account instead of domain account; however, the problem occurs with both).
SQL Server runs fine, and if I set my IIS application pool identity to a domain admin, my web app can access the database and retrieve the data necessary.
However, I have a domain user account that I want to use to run the app pool and retrieve the data. The domain user account is added to the IIS_WPG group on the web server. On the database server, I have created a login for the account, as well as added it to the db_datareader role of the database that is used for the site.
However, the user is not able to connect to the SQL Server. I get the "Login failed for user <user account>" error in ASP.NET. I also tried connecting with SQL Server Management Studio, and I get the same error. I checked and the user has connect permission to the database server.
With admin accounts, there are no problems logging in, etc.
Any pointers are appreciated,
Thanks,
SA.
Edit: I was able to find out that the State is 11 for the error. According to http://blogs.msdn.com/sql_protocols/archive/2006/02/21/536201.aspx, this indicates "Valid login but server access failure." I am not sure how to resolve this.
View 1 Replies
View Related
Nov 29, 2006
Dear Sir,
We are using VB.NET 2005 (Winform) and the backend SQL Server Express 2005. We would like to connect the Express (.mdf) database from Remote Machine. What type of connection string we have to use?
We tried the following ConnectionString but we got the error:
Provider=SQLNCLI.1;Server=.SQLEXPRESS;AttachDbFileName=S:MLJData.mdf;Database=MLJData;Trusted_Connection=Yes;
Also suggest what are all the prerequisites to run sql server express 2005 database in client machine.
We did installed the following tools in client machine:
1. .NET framework 2.0
2. sqlncli.msi (SQL Server Native Client Setup)
Please provide us the solution for this.
Thanks
M. Gopalan
Sofist India
okugops@hotmail.com
View 3 Replies
View Related
Mar 21, 2007
Hi
I am installing Visual Studio 2005 Professional Edition. Everything goes well until the installation of SQL Server Express occurs. SQL Express installation progresses fine until very end of the installation. At that point it becomes stuck.
The installation says "Current component is installing" and is stuck on that message. The installer does not seem to be frozen as the picutres changes. However CPU usage for the setup processes is 0.
I have disabled all virus scanning software already.
Any help is apprceciated.
View 1 Replies
View Related
Aug 13, 2007
Is there any way to connect to Hosting SQL Server using VS 2005.
I have only VS 2005 on my computer and Dont have SQL Server.
I have a SQL Server credentials on the Hosting server but the problem is the hosting website control panel didnt provide any enterprise manager to work on the database.
Thanks in advance.
View 13 Replies
View Related
Sep 7, 2007
Hoi,
Can someone help me? I have made a website with a database. Local on my pc all work fine. but now i need to set it op on my webhost.
all pages with no database access work but the ones with database controls i get :
Server Error in '/' Application.
Login failed for user 'username'..
I got from my webhost:
db server:
View 1 Replies
View Related
Apr 14, 2006
I installed the SQL Server 2005 Trial and am now having trouble connecting. When I bring up the ASP.NET Configuration tool and Go to "Provider configuration" "Select a single provider for all site management data" AspNetSqlProvider Test I get the following message.
"Could not establish a connection to the database. If you have not yet created the SQL Server database, exit the Web Site Administration tool, use the aspnet_regsql command-line utility to create and configure the database, and then return to this tool to set the provider. "
I have already run the aspnet_regsql command-line utility.
Can anybody give me some information on how to set this up.
I am currently working with the club web site starter kit.
View 1 Replies
View Related
Apr 19, 2008
I have a VB.Net Winform application installed at a client’s site using .net 1.0 and sql server 2000. I am in the process of upgrading to them to sql server 2005. The installation of sql server 2005 is on a different machine then the 2000 version. I have installed SQL Server 2005, SP2 and converted the database from SQL Sever 2000. Everything is good at this point. I can even establish a connection through a user’s login.
The Problem is when I try to connect from a client machine using my .net 1.0 application. The client test machine that I am using is a Windows NT Server which may have something to do with the problem. Any way I am getting the following error message.
SSL Security error
From other topics I have read I believe this is something to do with a certificate. The application only needs to connect from within the local network. I have tried connecting using the ODBC Data Sources tool from the client machine I get the following error.
Microsoft SQL Server ODBC Driver Version 03.81.9001
Running connectivity tests...
Attempting connection
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SSL Security error
TESTS FAILED!
Should I be using the TCP/IP?
Do I need to install anything on the client machines?
Do I need to open ports on the firewall?
Is there anything else that I am overlooking?
Thanks,
David
View 3 Replies
View Related
