Microsoft SQL Server 2005 Setup Problem
Mar 28, 2007
i keep getting this message whenever i double click the setup for sql server 2005. i previously installed the sql server 2005 beta 2 and have since deleted it. i've followed the readme on uninstalling some of the beta components and tried running some program i got from microsoft.com which would uninstal the pre release- the program doesn't detect any pre-release component. i however continue to get this message and need help resolving it.
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=setup.rll&EvtID=50000&EvtType=setup%5csqlsetupactions.cpp%40PerformSCCAction2%40sqls%3a%3aPerformSCCAction%3a%3aperform%400x11190
------------------------------
BUTTONS:
OK
------------------------------
View 3 Replies
ADVERTISEMENT
Aug 24, 2005
Hi
I need help when i try to install Microsoft SQL Server 2005 CTP Setup it fails every time i tried and now i don't what to do
Thank's
View 2 Replies
View Related
Jan 7, 2008
"SQL Server is unable to run. Either the owning node or all nodes that currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online."
Can someone tell me what's the cause of this error?
How can this be corrected?
I am very grateful for all feedback.
View 1 Replies
View Related
Mar 5, 2008
I was in the process of installing Microsof Project 2003 when we suddenly decided to move up to Microsoft Project 2007. We removed SharePoint 3.0 and SQL Server 2K so all that is installed on the box is Windows Server 2003 with all Service Packs. During the install of SQL Server 2005, here is the error message we get.
Microsoft SQL Server 2005 Setup
SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Cannot alter the login €˜sa€™, because it does not exist or you do not have permission.. Refer to the server error logs and Setup logs for detailed error information.
Any help is appreciated.
Thanks,
Ron
View 1 Replies
View Related
Feb 6, 2008
Hi,
I'have this error during install of Microsoft SQL Server 2005 Express Edition (x86). I'm Using Windows XP Professional with SP2 Build 2600. Does anyone knows how to solve this?
****
Microsoft SQL Server 2005 Setup was unable to install on your computer.
EventType : sql90setup P1 : unknown P2 : 0x659 P3 : unknown
P4 : 0x659 P5 : unknown P6 : unknown P7 : msxml6.msi@6.10.1129.0
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab
View 2 Replies
View Related
Dec 26, 2007
Hi guys,
I have problems installing SQL server 2005, any help ??
Tks...
This is the log file description...
=== Verbose logging started: 25/12/2007 21:05:41 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: c:Archivos de programaMicrosoft SQL Server90Setup Bootstrapsetup.exe ===
MSI (c) (AC:50) [21:05:41:656]: Resetting cached policy values
MSI (c) (AC:50) [21:05:41:656]: Machine policy value 'Debug' is 0
MSI (c) (AC:50) [21:05:41:656]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (AC:50) [21:05:41:656]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (AC:50) [21:05:41:656]: Grabbed execution mutex.
MSI (c) (AC:50) [21:05:41:671]: No se puede conectar al servidor. Error: 0x80040154
MSI (c) (AC:50) [21:05:41:671]: Failed to connect to server.
MSI (c) (AC:50) [21:05:41:671]: MainEngineThread is returning 1601
=== Verbose logging stopped: 25/12/2007 21:05:41 ===
View 11 Replies
View Related
Aug 23, 2007
I have tried to install Outlook 2007 with BCM and recieve the error listed above. I have also included a copy of my log file. Any suggestions?
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Thu Aug 23 14:22:59 2007
Machine : MACBOOK
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLSupport_1.log
--------------------------------------------------------------------------------
Machine : MACBOOK
Product : Microsoft SQL Server Native Client
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLNCLI_1.log
--------------------------------------------------------------------------------
Machine : MACBOOK
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.2047.00
Install : Successful
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SqlWriter_1.log
--------------------------------------------------------------------------------
Machine : MACBOOK
Product : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install : Failed
Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_MSXML6_1.log
Error Number : 1603
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Thu Aug 23 14:23:45 2007
List of log files:
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Core(Local).log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLSupport_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SQLNCLI_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SqlWriter_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_MSXML6_1.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Datastore.xml
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_.NET Framework 2.0.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SNAC.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Core.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_Support.log
C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0010_MACBOOK_SCC.log
View 3 Replies
View Related
Feb 13, 2008
I'm attempting to install the standard version of SQL server 2005 on XP SP2. I'm getting the following:
Errors occurred during the installation:
Error 1603 installing Microsoft SQL Server 2005 setup support files.
View 11 Replies
View Related
Jul 4, 2007
I Don't understand what this means: Everytime I try and install the disc 2 of my Office Small Business 2007, it gives the same message. Help.
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Home Edition (Build 6000)
Time : Tue Jul 03 17:14:45 2007
Machine : SWANNER-PC
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLSupport_1.log
Error Number : 1618
--------------------------------------------------------------------------------
Machine : SWANNER-PC
Product : Microsoft SQL Server Native Client
Product Version : 9.00.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLNCLI_1.log
Error Number : 1618
--------------------------------------------------------------------------------
Machine : SWANNER-PC
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.3042.00
Install : Failed
Log File : c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SqlWriter_1.log
Error Number : 1618
--------------------------------------------------------------------------------
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Tue Jul 03 17:15:12 2007
List of log files:
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Core(Patched).log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLSupport_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SQLNCLI_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SqlWriter_1.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Datastore.xml
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_.NET Framework 2.0.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Support.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_Core.log
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt
c:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_SWANNER-PC_SCC.log
View 38 Replies
View Related
Feb 3, 2007
I have a very small project written in VB.Net 2005 using the SQL Server 2005 SSiS DTSx package.
I migrated a SLQ 2000 DTS package using the SQL 2005 Legacy tools and saved the package as a local .DTSx package on our file server.
I need to run the package from a clients PC.
I added the reference Microsoft.SqlServer.ManagedDTS so I could then use the Microsoft.SqlServer.Dts.Runtime so I can execute the commands:
Dim oApp As New Application
Dim oPkg As New Package
oPkg = oApp.LoadPackage(g_DTSx_Directory & "AOC copy Generic1 CSV to AOC_verify_file_1.dtsx", Nothing)
Dim oResults As DTSExecResult
oResults = oPkg.Execute
Ok. That works fine and is basically the entire app. It executes without a hitch in debug and as a compiled exe on my PC, but I have all the tools. So now I try and create a setup project for this and I use the setup wizard.
During the creation of the setup project I get a message that states:
The following files may have dependencies that cannot be determined automatically. Please confirm that all dependencies have been added to the project.
C:windowssystem32msxml6.dll
OK. The dll is part of the reference I mentioned above and I have no idea what other dependencies it may have.
How do I find this out?
Has anyone else created a project like this and experenced the same?
I am on a clean build running WinXP Pro with SP2 - VS2005 with SP1 and the SQL Server 2005 tools.
View 4 Replies
View Related
Oct 11, 2006
error saying disk compressed or encryted, choose another drive?
how should i t-shoot !!!!!
View 1 Replies
View Related
Aug 9, 2005
I installed Microsoft SQL Server 2005 Express Manager and connect to SQL 2000 normally
View 10 Replies
View Related
Jun 21, 2007
Hi
I am trying to use Association Viewer Control in
Microsoft.AnalysisServices.Viewers.DLL dll in VS 2005 but sometimes it gives an error.
"Code generatio for property 'ConnecitonManager'" failed. Error was:'Property accesor 'ConnectionManager' on object 'AssosiactionViewer1' threw the following exception:'Object referance not set to instance of an object"
Is there anyone here who use
"Microsoft SQL Server 2005 Datamining Viewer Controls" in SQLServer2005 FeaturePack ?
http://www.microsoft.com/downloads/details.aspx?FamilyID=50b97994-8453-4998-8226-fa42ec403d17&DisplayLang=en
i am using VS2005 Version 8.0.50727.762 (SP.050727-7600)
and SQL Server 2005 SP2
thanks from now.
Cem Ãœney
View 9 Replies
View Related
May 2, 2006
I'm trying in vain to upgrade sql server 2000 to 2005 with great headache and pain.
I (finally) have removed all Beta, and other incompatible version of .NET, Visual Studio and any other offending components, and made it to the first page of the install shield.
The .NET 2.0 components installed fine - but I get a fatal error trying to install the SQL Server Set Support Files.
I do have a log file - and have tired searching on the various error codes in it, but am coming up blank. Please advise - this is taking forever!
sample of error msgs in log file:
MSI (s) (B0:E0) [12:33:06:613]: Note: 1: 1935 2: 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.NetEnterpriseServers.ExceptionMessageBox,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:613]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:613]: Executing op: ComponentRegister(ComponentId={52723CBD-3400-458C-988A-4D012E6CAEDB},KeyPath=<Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
Error 2908. The installer has encountered an unexpected error. The error code is 2908. Could not register component {1F3316BE-825B-4390-A9D2-AF3EECCAE9F6}.
MSI (s) (B0:E0) [12:33:06:629]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:E0) [12:33:06:629]: Assembly Error:Function not defined in specified DLL.
MSI (s) (B0:E0) [12:33:06:629]: Note: 1: 1935 2: {52723CBD-3400-458C-988A-4D012E6CAEDB} 3: 0x8002802F 4: 5: CreateAssemblyNameObject 6: Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"
MSI (s) (B0:E0) [12:33:06:629]: Product: Microsoft SQL Server Setup Support Files (English) -- Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
Error 1935. An error occurred during the installation of assembly 'Microsoft.SqlServer.WizardFrameworkLite,Version="9.0.242.0",processorArchitecture="MSIL",Culture="neutral",PublicKeyToken="89845dcd8080cc91",FileVersion="9.0.1399.0"'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {52723CBD-3400-458C-988A-4D012E6CAEDB}
MSI (s) (B0:E0) [12:33:06:629]: User policy value 'DisableRollback' is 0
MSI (s) (B0:E0) [12:33:06:629]: Machine policy value 'DisableRollback' is 0
Action ended 12:33:06: InstallFinalize. Return value 3.
mandpenny
View 5 Replies
View Related
Mar 27, 2008
Pls tell me about the adjact difference between sql server 2005 and sql server 2008.
Why to upgrade for Sql Server 2008
View 1 Replies
View Related
Feb 2, 2007
I am update/inserting records threw a web form in vb.net. I need to insert 'NULL' into my microsoft sql server database. I am not talking about the below line of code where website is the name of my paramater. If i do that it will just place a blank into that field in the database. If i dont enter anything into that textbox I want it to to say NULL in that field. So if I go into the actual table in the SQL Server Management Studio and look at the website field of the recored I just added or updated and did not type anything into the web site textbox it needs to say NULL. I also tried the second line of code but that places a single quote in front and behind NULL. So the field will have the value 'NULL'.
website.value = txtwebsite.text.tostirng
if txtwebsite.text ="" then
website.value ="NULL"
end if
The reason why I need the NULL there is because I bind the website filed to a hyperlink template in a gridview. The actual text of the hyperlink is bound to PAYER which is a name of a insurance payer but the navigateto is bound to the website field. If i do not enter any data into the website field and it stays as NULL, then when my gridview is loaded, payers that dont have a website will not be underlined and user wont have the option to click on them since there is no value for the navigateto. But if i use my form to update/add a payer and leave the website textbox blank in puts a blank into that field in my database and when it loads that new row into the gridview the PAYER is underlined and u can click on it but it will just take u to the web site is unavailable page. So is there anyway to actaull have NULL placed into a filed and not just blank space
View 3 Replies
View Related
May 16, 2007
Sp2 cannot be install
can someone help me
this is hotfix log
05/16/2007 13:05:30.583 ================================================================================
05/16/2007 13:05:30.599 Hotfix package launched
05/16/2007 13:05:30.630 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.646 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:30.662 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:30.677 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:30.693 Local Computer:
05/16/2007 13:05:30.708 Target Details: DC-01
05/16/2007 13:05:30.724 commonfilesdir = C:ProgrammiFile comuni
05/16/2007 13:05:30.740 lcidsupportdir = e:3f798aa49a0102c6d1f049aa36bd359d1040
05/16/2007 13:05:30.755 programfilesdir = C:Programmi
05/16/2007 13:05:30.771 programfilesdir_wow = C:Programmi
05/16/2007 13:05:30.771 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.802 supportdirlocal = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:30.818 windir = C:WINDOWS
05/16/2007 13:05:30.833 winsysdir = C:WINDOWSsystem32
05/16/2007 13:05:30.849 winsysdir_wow = C:WINDOWSSysWOW64
05/16/2007 13:05:30.865
05/16/2007 13:05:30.958 Enumerating applicable products for this patch
05/16/2007 13:05:31.005 Found Redist 2005 product definition
05/16/2007 13:05:31.021 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.036 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.052 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.068 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.442 Found Redist 2005 product definition
05/16/2007 13:05:31.458 Found Redist 2005 product definition
05/16/2007 13:05:31.474 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.489 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:31.505 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:31.521 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:31.677 Found SQL 2005 product definition
05/16/2007 13:05:32.270 Enumeration: Determining QFE level for product instance MSSQLSERVER
05/16/2007 13:05:32.286 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.286 Enumeration: Found following QFE level for product instance MSSQLSERVER: 1399
05/16/2007 13:05:32.302 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
05/16/2007 13:05:32.317 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLServr.exe
05/16/2007 13:05:32.333 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
05/16/2007 13:05:32.348 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.348 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:32.364 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:32.380 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:32.395 Product discovery completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 SP Level check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.411 Product language check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.426 Product version check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.442 Command-line instance name check completed during the install process
05/16/2007 13:05:32.458 SKU check completed during the install process for MSSQLSERVER
05/16/2007 13:05:32.473 Baseline build check completed during the installation process for MSSQLSERVER
05/16/2007 13:05:32.489 Baseline build check completed during the install process
05/16/2007 13:05:32.505 Found OLAP Server 2005 product definition
05/16/2007 13:05:33.004 Command-line instance name check completed during the install process
05/16/2007 13:05:33.004 Baseline build check completed during the install process
05/16/2007 13:05:33.036 Found Notification Services 2005 product definition
05/16/2007 13:05:33.520 Baseline build check completed during the install process
05/16/2007 13:05:33.551 Found Report Server 2005 product definition
05/16/2007 13:05:34.051 Command-line instance name check completed during the install process
05/16/2007 13:05:34.066 Baseline build check completed during the install process
05/16/2007 13:05:34.082 Found DTS 2005 product definition
05/16/2007 13:05:34.582 Baseline build check completed during the install process
05/16/2007 13:05:34.613 Found SQL 2005 Tools product definition
05/16/2007 13:05:35.113 Enumeration: Determining GDR branching Hotfix for product instance
05/16/2007 13:05:35.144 Enumeration: Associated hotfix build information not found for the following file: C:ProgrammiMicrosoft SQL Server90Tools\BinnVSShellCommon7IDESQLWB.EXE
05/16/2007 13:05:35.160 Enumeration: No GDR branch Hotfix found for product instance
05/16/2007 13:05:35.175 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.191 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.207 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.207 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.222 Product discovery completed during the install process for SQL Tools
05/16/2007 13:05:35.238 SP Level check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product language check completed during the install process for SQL Tools
05/16/2007 13:05:35.253 Product version check completed during the install process for SQL Tools
05/16/2007 13:05:35.269 SKU check completed during the install process for SQL Tools
05/16/2007 13:05:35.285 Baseline build check completed during the install process
05/16/2007 13:05:35.300 Found Redist 2005 product definition
05/16/2007 13:05:35.316 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.332 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.347 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.363 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.597 Found Redist 2005 product definition
05/16/2007 13:05:35.613 Found Redist 2005 product definition
05/16/2007 13:05:35.628 Found Redist 2005 product definition
05/16/2007 13:05:35.644 Found Redist 2005 product definition
05/16/2007 13:05:35.660 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.675 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.675 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.691 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:35.909 Found Redist 2005 product definition
05/16/2007 13:05:35.925 Found Redist 2005 product definition
05/16/2007 13:05:35.941 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.941 Registry: Read registry key value "CommonFilesDir", string value = C:ProgrammiFile comuni
05/16/2007 13:05:35.956 Registry: Opened registry key "SOFTWAREMicrosoftWindowsCurrentVersion"
05/16/2007 13:05:35.972 Registry: Read registry key value "ProgramFilesDir", string value = C:Programmi
05/16/2007 13:05:36.128 Found Redist 2005 product definition
05/16/2007 13:05:36.191 Product Enumeration Results:
05/16/2007 13:05:36.206 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli.inf
05/16/2007 13:05:36.222 baselinebuild = 1399
05/16/2007 13:05:36.237 build = 3042
05/16/2007 13:05:36.253 description = SQL Server Native Client
05/16/2007 13:05:36.269 details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.284 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.300 kbarticle = KB921896
05/16/2007 13:05:36.316 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.331 lcid = 1040
05/16/2007 13:05:36.347 legalproductname = Microsoft SQL Native Client
05/16/2007 13:05:36.362 machinetype = x86
05/16/2007 13:05:36.362 package = HotFixSqlncli
05/16/2007 13:05:36.378 packagetype = Hotfix
05/16/2007 13:05:36.394 productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.409 productname = Redist9
05/16/2007 13:05:36.425 recommendinstall = 1
05/16/2007 13:05:36.441 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:36.456 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:36.472 splevel = 2
05/16/2007 13:05:36.487 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:36.519 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:36.519 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
05/16/2007 13:05:36.534 version = 9
05/16/2007 13:05:36.550
05/16/2007 13:05:36.581 File Group Details: MSI
05/16/2007 13:05:36.597 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:36.612 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:36.628 File Details: sqlncli.msi
05/16/2007 13:05:36.644
05/16/2007 13:05:36.659 Instance Details: SQL Server Native Client
05/16/2007 13:05:36.690 fullversion = 9.00.3042.00
05/16/2007 13:05:36.706 lcid = 1040
05/16/2007 13:05:36.722 productcode = {BA06B694-0CFE-4A3E-81A7-9CED25B74E2B}
05/16/2007 13:05:36.753 qfelevel = 3042
05/16/2007 13:05:36.769 sp = -1
05/16/2007 13:05:36.784
05/16/2007 13:05:36.800 Product Enumeration Results:
05/16/2007 13:05:36.831 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlncli_x64.inf
05/16/2007 13:05:36.847 baselinebuild = 1399
05/16/2007 13:05:36.862 build = 3042
05/16/2007 13:05:36.878 description = SQL Server Native Client
05/16/2007 13:05:36.893 details = Service Pack per Microsoft SQL Server Native Client.
05/16/2007 13:05:36.909 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:36.940 kbarticle = KB921896
05/16/2007 13:05:36.956 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:36.972 lcid = 1040
05/16/2007 13:05:36.987 legalproductname = Microsoft SQL Native Client (64 bit)
05/16/2007 13:05:37.018 machinetype = x64
05/16/2007 13:05:37.034 package = HotFixSqlncli_x64
05/16/2007 13:05:37.050 packagetype = Hotfix
05/16/2007 13:05:37.081 productname = Redist9
05/16/2007 13:05:37.097 recommendinstall = 1
05/16/2007 13:05:37.112 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.128 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.159 splevel = 2
05/16/2007 13:05:37.175 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.190 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
05/16/2007 13:05:37.206 version = 9
05/16/2007 13:05:37.237
05/16/2007 13:05:37.253 File Group Details: MSI
05/16/2007 13:05:37.268 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:37.284 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.315 File Details: sqlncli_x64.msi
05/16/2007 13:05:37.331
05/16/2007 13:05:37.346 Product Enumeration Results:
05/16/2007 13:05:37.362 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlSupport.inf
05/16/2007 13:05:37.393 alwaysinstall = 1
05/16/2007 13:05:37.409 baselinebuild = 1399
05/16/2007 13:05:37.425 build = 3042
05/16/2007 13:05:37.456 description = File di supporto dell'installazione
05/16/2007 13:05:37.534 details = Service Pack per i file di supporto dell'installazione di SQL Server.
05/16/2007 13:05:37.565 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:37.581 kbarticle = KB921896
05/16/2007 13:05:37.596 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:37.612 keyqualifier = 1
05/16/2007 13:05:37.643 lcid = 1040
05/16/2007 13:05:37.659 legalproductname = File di supporto dell'installazione di SQL Server 2005
05/16/2007 13:05:37.674 machinetype = x86
05/16/2007 13:05:37.690 package = HotFixSqlSupport
05/16/2007 13:05:37.690 packagetype = Hotfix
05/16/2007 13:05:37.706 productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:37.737 productname = Redist9
05/16/2007 13:05:37.753 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:37.768 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:37.784 splevel = 2
05/16/2007 13:05:37.815 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:37.831 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:37.846 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
05/16/2007 13:05:37.862 version = 9
05/16/2007 13:05:37.877
05/16/2007 13:05:37.893 File Group Details: MSI
05/16/2007 13:05:37.909 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCacheSQLSupport<MachineType><LCID>
05/16/2007 13:05:37.940 parameters = REINSTALL=ALL
05/16/2007 13:05:37.956 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:37.971 File Details: SqlSupport.msi
05/16/2007 13:05:37.987
05/16/2007 13:05:38.002 Instance Details: File di supporto dell'installazione
05/16/2007 13:05:38.018 fullversion = 9.2.3042
05/16/2007 13:05:38.049 lcid = 1040
05/16/2007 13:05:38.065 productcode = {6379FD0A-8964-4A50-80A6-B20B65117905}
05/16/2007 13:05:38.081 qfelevel = 3042
05/16/2007 13:05:38.096 sp = -1
05/16/2007 13:05:38.112
05/16/2007 13:05:38.143 Product Enumeration Results:
05/16/2007 13:05:38.159 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQL.inf
05/16/2007 13:05:38.174 baselinebuild = 1399
05/16/2007 13:05:38.190 baselinebuildmax = 3042
05/16/2007 13:05:38.205 build = 3042
05/16/2007 13:05:38.221 description = Servizi di database
05/16/2007 13:05:38.237 details = Service Pack per il Motore di database e gli strumenti di SQL Server per la gestione di dati relazionali e XML, per la replica e per la ricerca full-text.
05/16/2007 13:05:38.252 installer = Hotfix
05/16/2007 13:05:38.268 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:38.284 kbarticle = KB921896
05/16/2007 13:05:38.299 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:38.330 lcid = 1040
05/16/2007 13:05:38.346 legalproductname = Servizi di database SQL Server 2005
05/16/2007 13:05:38.362 machinetype = x86
05/16/2007 13:05:38.393 package = HotFixSQL
05/16/2007 13:05:38.409 packagetype = Hotfix
05/16/2007 13:05:38.424 productname = SQL9
05/16/2007 13:05:38.440 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:38.471 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:38.487 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:38.502 splevel = 2
05/16/2007 13:05:38.518 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:38.549 sqlutility = sqlcmd.exe
05/16/2007 13:05:38.565 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:38.580 validateauthentication = true
05/16/2007 13:05:38.596 version = 9
05/16/2007 13:05:38.612
05/16/2007 13:05:38.627 File Group Details: MSP
05/16/2007 13:05:38.658 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:38.674 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:38.690 File Details: sqlrun_sql.msp
05/16/2007 13:05:38.705
05/16/2007 13:05:38.721 Instance Details: MSSQLSERVER
05/16/2007 13:05:38.752 agentservicename = SQLSERVERAGENT
05/16/2007 13:05:38.768 clustername =
05/16/2007 13:05:38.783 default = TRUE
05/16/2007 13:05:38.815 ftsservicename = MSFTESQL
05/16/2007 13:05:38.830 fullversion = 2005.090.1399.00
05/16/2007 13:05:38.846 hiveregpath = SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1
05/16/2007 13:05:38.877 id = MSSQL.1
05/16/2007 13:05:38.893 installsqldatadir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.908 installsqldir = C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQL
05/16/2007 13:05:38.924 lcid = 1040
05/16/2007 13:05:38.940 name = MSSQLSERVER
05/16/2007 13:05:38.971 productcode = {E0BB3923-308B-4BE9-B3A3-FD5517481E48}
05/16/2007 13:05:39.002 qfelevel = 1399
05/16/2007 13:05:39.018 servicename = MSSQLServer
05/16/2007 13:05:39.033 sku = STANDARD
05/16/2007 13:05:39.049 sp = 0
05/16/2007 13:05:39.065 type = SQL Server Standalone Product
05/16/2007 13:05:39.096 vermajbld = 1399
05/16/2007 13:05:39.111 version = 9
05/16/2007 13:05:39.127
05/16/2007 13:05:39.143 Product Enumeration Results:
05/16/2007 13:05:39.174 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixAS.inf
05/16/2007 13:05:39.189 baselinebuild = 1399
05/16/2007 13:05:39.205 baselinebuildmax = 3042
05/16/2007 13:05:39.236 build = 3042
05/16/2007 13:05:39.252 description = Analysis Services
05/16/2007 13:05:39.268 details = Service Pack per Analysis Services e per gli strumenti per il supporto dell'elaborazione analitica in linea (OLAP) e del data mining.
05/16/2007 13:05:39.283 installer = Hotfix
05/16/2007 13:05:39.299 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.330 kbarticle = KB921896
05/16/2007 13:05:39.346 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.361 lcid = 1040
05/16/2007 13:05:39.377 legalproductname = SQL Server Analysis Services 2005
05/16/2007 13:05:39.408 machinetype = x86
05/16/2007 13:05:39.424 package = HotFixAS
05/16/2007 13:05:39.455 packagetype = Hotfix
05/16/2007 13:05:39.471 productname = OLAP9
05/16/2007 13:05:39.486 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:39.502 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:39.533 splevel = 2
05/16/2007 13:05:39.549 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:39.564 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:39.580 version = 9
05/16/2007 13:05:39.611
05/16/2007 13:05:39.627 File Group Details: MSP
05/16/2007 13:05:39.642 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:39.674 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:39.689 File Details: sqlrun_as.msp
05/16/2007 13:05:39.705
05/16/2007 13:05:39.736 Product Enumeration Results:
05/16/2007 13:05:39.752 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixNS.inf
05/16/2007 13:05:39.767 baselinebuild = 1399
05/16/2007 13:05:39.799 baselinebuildmax = 3042
05/16/2007 13:05:39.814 build = 3042
05/16/2007 13:05:39.830 description = Notification Services
05/16/2007 13:05:39.861 details = Service Pack per Notification Services, una piattaforma per lo sviluppo e la distribuzione di applicazioni per l'invio di notifiche personalizzate e tempestive a un'ampia gamma di dispositivi o applicazioni.
05/16/2007 13:05:39.877 installer = Hotfix
05/16/2007 13:05:39.892 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:39.908 kbarticle = KB921896
05/16/2007 13:05:39.924 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:39.939 lcid = 1040
05/16/2007 13:05:39.970 legalproductname = Istanze di SQL Server Notification Services 2005
05/16/2007 13:05:39.986 machinetype = x86
05/16/2007 13:05:40.002 package = HotFixNS
05/16/2007 13:05:40.017 packagetype = Hotfix
05/16/2007 13:05:40.033 productname = NS9
05/16/2007 13:05:40.064 recommendinstall = 1
05/16/2007 13:05:40.080 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.095 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.111 splevel = 2
05/16/2007 13:05:40.142 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.158 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.189 version = 9
05/16/2007 13:05:40.205
05/16/2007 13:05:40.220 File Group Details: MSP
05/16/2007 13:05:40.236 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.267 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.283 File Details: sqlrun_ns.msp
05/16/2007 13:05:40.298
05/16/2007 13:05:40.330 Product Enumeration Results:
05/16/2007 13:05:40.345 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixRS.inf
05/16/2007 13:05:40.361 baselinebuild = 1399
05/16/2007 13:05:40.376 baselinebuildmax = 3042
05/16/2007 13:05:40.408 build = 3042
05/16/2007 13:05:40.423 description = Reporting Services
05/16/2007 13:05:40.439 details = Service Pack per Server report e Generatore report, utilizzati per la gestione, l'esecuzione, il rendering e la distribuzione dei report.
05/16/2007 13:05:40.455 installer = Hotfix
05/16/2007 13:05:40.486 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:40.501 kbarticle = KB921896
05/16/2007 13:05:40.517 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:40.548 lcid = 1040
05/16/2007 13:05:40.564 legalproductname = SQL Server Reporting Services 2005
05/16/2007 13:05:40.580 machinetype = x86
05/16/2007 13:05:40.611 package = HotFixRS
05/16/2007 13:05:40.626 packagetype = Hotfix
05/16/2007 13:05:40.642 productname = RS9
05/16/2007 13:05:40.658 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:40.673 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:40.689 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:40.720 splevel = 2
05/16/2007 13:05:40.736 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:40.751 sqlutility = sqlcmd.exe
05/16/2007 13:05:40.767 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:40.798 validateauthentication = 1
05/16/2007 13:05:40.814 version = 9
05/16/2007 13:05:40.829
05/16/2007 13:05:40.861 File Group Details: MSP
05/16/2007 13:05:40.876 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:40.892 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:40.908 File Details: sqlrun_rs.msp
05/16/2007 13:05:40.939
05/16/2007 13:05:40.954 Product Enumeration Results:
05/16/2007 13:05:40.970 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixDTS.inf
05/16/2007 13:05:41.001 baselinebuild = 1399
05/16/2007 13:05:41.017 baselinebuildmax = 3042
05/16/2007 13:05:41.032 build = 3042
05/16/2007 13:05:41.064 description = Integration Services
05/16/2007 13:05:41.079 details = Service Pack per Integration Services, una serie di strumenti e oggetti programmabili per la creazione e la gestione di pacchetti per l'estrazione, la trasformazione e il caricamento dei dati, nonché per l'esecuzione di attività .
05/16/2007 13:05:41.095 installer = Hotfix
05/16/2007 13:05:41.126 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.142 kbarticle = KB921896
05/16/2007 13:05:41.157 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.173 lcid = 1040
05/16/2007 13:05:41.189 legalproductname = SQL Server Integration Services 2005
05/16/2007 13:05:41.220 machinetype = x86
05/16/2007 13:05:41.236 package = HotFixDTS
05/16/2007 13:05:41.251 packagetype = Hotfix
05/16/2007 13:05:41.282 productname = DTS9
05/16/2007 13:05:41.298 recommendinstall = 1
05/16/2007 13:05:41.314 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.329 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.360 splevel = 2
05/16/2007 13:05:41.376 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:41.392 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:41.423 version = 9
05/16/2007 13:05:41.439
05/16/2007 13:05:41.454 File Group Details: MSP
05/16/2007 13:05:41.485 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:41.501 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:41.517 File Details: sqlrun_dts.msp
05/16/2007 13:05:41.548
05/16/2007 13:05:41.564 Product Enumeration Results:
05/16/2007 13:05:41.579 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixTools.inf
05/16/2007 13:05:41.610 baselinebuild = 1399
05/16/2007 13:05:41.626 baselinebuildmax = 3042
05/16/2007 13:05:41.642 build = 3042
05/16/2007 13:05:41.657 description = Componenti client
05/16/2007 13:05:41.688 details = Service Pack per gli strumenti interattivi di gestione per l'esecuzione di SQL Server, tra cui Gestione configurazione SQL Server, SQL Server Management Studio, SQL Profiler e Monitoraggio replica.
05/16/2007 13:05:41.704 installer = Hotfix
05/16/2007 13:05:41.720 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:41.751 kbarticle = KB921896
05/16/2007 13:05:41.767 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:41.782 lcid = 1040
05/16/2007 13:05:41.798 legalproductname = Componenti workstation e strumenti di SQL Server 2005
05/16/2007 13:05:41.829 machinetype = x86
05/16/2007 13:05:41.845 package = HotFixTools
05/16/2007 13:05:41.860 packagetype = Hotfix
05/16/2007 13:05:41.876 productname = SQLTools9
05/16/2007 13:05:41.892 recommendinstall = 1
05/16/2007 13:05:41.923 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:41.938 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:41.954 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/16/2007 13:05:41.985 splevel = 2
05/16/2007 13:05:42.001 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.016 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.032 version = 9
05/16/2007 13:05:42.063
05/16/2007 13:05:42.079 File Group Details: MSP
05/16/2007 13:05:42.095 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/16/2007 13:05:42.110 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:42.141 File Details: sqlrun_tools.msp
05/16/2007 13:05:42.157
05/16/2007 13:05:42.188 Instance Details: SQL Tools
05/16/2007 13:05:42.204 associatedhotfixbuild = 1520
05/16/2007 13:05:42.220 clustername =
05/16/2007 13:05:42.235 fullversion = 9.2.3042
05/16/2007 13:05:42.266 hiveregpath = SoftwareMicrosoftMicrosoft SQL Server90Tools
05/16/2007 13:05:42.282 id =
05/16/2007 13:05:42.298 installsqldatadir =
05/16/2007 13:05:42.313 installsqldir = C:ProgrammiMicrosoft SQL Server90Tools
05/16/2007 13:05:42.329 lcid = 1040
05/16/2007 13:05:42.360 name =
05/16/2007 13:05:42.376 productcode = {B03FBBA3-CCE4-40CC-A0F1-01F952E7EB3E}
05/16/2007 13:05:42.391 qfelevel = 3042
05/16/2007 13:05:42.407 sku = STANDARD
05/16/2007 13:05:42.438 sp = 2
05/16/2007 13:05:42.454 type = Tools Only
05/16/2007 13:05:42.469 vermajbld = 3042
05/16/2007 13:05:42.501 version = 9
05/16/2007 13:05:42.516
05/16/2007 13:05:42.532 Product Enumeration Results:
05/16/2007 13:05:42.563 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6.inf
05/16/2007 13:05:42.579 baselinebuild = 1399
05/16/2007 13:05:42.594 build = 6.10.1129.0
05/16/2007 13:05:42.626 description = Parser MSXML 6.0
05/16/2007 13:05:42.641 details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:42.657 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:42.688 kbarticle = KB921896
05/16/2007 13:05:42.704 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:42.719 lcid = 1040
05/16/2007 13:05:42.751 legalproductname = Parser MSXML 6.0
05/16/2007 13:05:42.766 machinetype = x86
05/16/2007 13:05:42.782 package = HotFixMsxml6
05/16/2007 13:05:42.797 packagetype = Hotfix
05/16/2007 13:05:42.813 productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:42.844 productname = Redist9
05/16/2007 13:05:42.860 recommendinstall = 1
05/16/2007 13:05:42.876 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:42.891 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:42.922 splevel = 2
05/16/2007 13:05:42.938 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:42.969 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:42.985 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
05/16/2007 13:05:43.000 version = 9
05/16/2007 13:05:43.016
05/16/2007 13:05:43.032 File Group Details: MSI
05/16/2007 13:05:43.063 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.079 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.094 File Details: msxml6.msi
05/16/2007 13:05:43.110
05/16/2007 13:05:43.141 Instance Details: Parser MSXML 6.0
05/16/2007 13:05:43.157 fullversion = 6.10.1129.0
05/16/2007 13:05:43.172 lcid = 1040
05/16/2007 13:05:43.188 productcode = {8919A89C-D378-4899-BE19-12893E4DCCEE}
05/16/2007 13:05:43.219 qfelevel = 1129
05/16/2007 13:05:43.235 sp = -1
05/16/2007 13:05:43.250
05/16/2007 13:05:43.266 Product Enumeration Results:
05/16/2007 13:05:43.297 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixMsxml6_x64.inf
05/16/2007 13:05:43.313 baselinebuild = 1399
05/16/2007 13:05:43.328 build = 6.10.1129.0
05/16/2007 13:05:43.360 description = Parser MSXML 6.0
05/16/2007 13:05:43.375 details = Service Pack per il parser Microsoft XML 6.0.
05/16/2007 13:05:43.391 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.422 kbarticle = KB921896
05/16/2007 13:05:43.438 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.453 lcid = 1040
05/16/2007 13:05:43.469 legalproductname = Parser MSXML 6.0 (64 bit)
05/16/2007 13:05:43.500 machinetype = x64
05/16/2007 13:05:43.516 package = HotFixMsxml6_x64
05/16/2007 13:05:43.532 packagetype = Hotfix
05/16/2007 13:05:43.563 productname = Redist9
05/16/2007 13:05:43.578 recommendinstall = 1
05/16/2007 13:05:43.594 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:43.610 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:43.625 splevel = 2
05/16/2007 13:05:43.641 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:43.656 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
05/16/2007 13:05:43.672 version = 9
05/16/2007 13:05:43.688
05/16/2007 13:05:43.703 File Group Details: MSI
05/16/2007 13:05:43.719 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:43.735 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:43.750 File Details: msxml6_x64.msi
05/16/2007 13:05:43.781
05/16/2007 13:05:43.797 Product Enumeration Results:
05/16/2007 13:05:43.813 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4.inf
05/16/2007 13:05:43.828 baselinebuild = 1399
05/16/2007 13:05:43.844 build = 3042
05/16/2007 13:05:43.860 description = SQLXML4
05/16/2007 13:05:43.875 details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:43.891 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:43.906 kbarticle = KB921896
05/16/2007 13:05:43.922 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:43.938 lcid = 1040
05/16/2007 13:05:43.953 legalproductname = SQLXML4
05/16/2007 13:05:43.969 machinetype = x86
05/16/2007 13:05:43.984 package = HotFixSqlxml4
05/16/2007 13:05:44.000 packagetype = Hotfix
05/16/2007 13:05:44.016 productname = Redist9
05/16/2007 13:05:44.047 recommendinstall = 1
05/16/2007 13:05:44.063 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.078 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.094 splevel = 2
05/16/2007 13:05:44.109 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:44.125 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.141 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
05/16/2007 13:05:44.156 version = 9
05/16/2007 13:05:44.172
05/16/2007 13:05:44.188 File Group Details: MSI
05/16/2007 13:05:44.203 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.219 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.234 File Details: sqlxml4.msi
05/16/2007 13:05:44.266
05/16/2007 13:05:44.281 Product Enumeration Results:
05/16/2007 13:05:44.297 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlxml4_x64.inf
05/16/2007 13:05:44.312 baselinebuild = 1399
05/16/2007 13:05:44.328 build = 3042
05/16/2007 13:05:44.344 description = SQLXML4
05/16/2007 13:05:44.375 details = Service Pack per Microsoft SQLXML 4.0.
05/16/2007 13:05:44.391 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.391 kbarticle = KB921896
05/16/2007 13:05:44.422 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.422 lcid = 1040
05/16/2007 13:05:44.437 legalproductname = SQLXML4 (64 bit)
05/16/2007 13:05:44.453 machinetype = x64
05/16/2007 13:05:44.469 package = HotFixSqlxml4_x64
05/16/2007 13:05:44.484 packagetype = Hotfix
05/16/2007 13:05:44.500 productname = Redist9
05/16/2007 13:05:44.516 recommendinstall = 1
05/16/2007 13:05:44.531 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:44.547 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:44.562 splevel = 2
05/16/2007 13:05:44.594 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:44.609 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
05/16/2007 13:05:44.625 version = 9
05/16/2007 13:05:44.640
05/16/2007 13:05:44.656 File Group Details: MSI
05/16/2007 13:05:44.672 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:44.687 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:44.703 File Details: sqlxml4_x64.msi
05/16/2007 13:05:44.719
05/16/2007 13:05:44.734 Product Enumeration Results:
05/16/2007 13:05:44.750 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC.inf
05/16/2007 13:05:44.765 baselinebuild = 1399
05/16/2007 13:05:44.781 build = 2004
05/16/2007 13:05:44.797 description = Compatibilità con le versioni precedenti
05/16/2007 13:05:44.812 details = Service Pack per i componenti per la compatibilità con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:44.828 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:44.844 kbarticle = KB921896
05/16/2007 13:05:44.859 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:44.875 lcid = 1040
05/16/2007 13:05:44.890 legalproductname = Compatibilità con le versioni precedenti a Microsoft SQL Server 2005
05/16/2007 13:05:44.906 machinetype = x86
05/16/2007 13:05:44.922 package = HotFixSQLServer2005_BC
05/16/2007 13:05:44.937 packagetype = Hotfix
05/16/2007 13:05:44.953 productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:44.968 productname = Redist9
05/16/2007 13:05:44.984 recommendinstall = 1
05/16/2007 13:05:45.015 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.031 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.047 splevel = 2
05/16/2007 13:05:45.062 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:45.078 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.093 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
05/16/2007 13:05:45.109 version = 9
05/16/2007 13:05:45.125
05/16/2007 13:05:45.140 File Group Details: MSI
05/16/2007 13:05:45.171 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.187 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.203 File Details: SQLServer2005_BC.msi
05/16/2007 13:05:45.203
05/16/2007 13:05:45.218 Instance Details: Compatibilità con le versioni precedenti
05/16/2007 13:05:45.234 fullversion = 8.05.2004
05/16/2007 13:05:45.250 lcid = 1040
05/16/2007 13:05:45.265 productcode = {B532F403-16FA-4433-929C-3768090D70E3}
05/16/2007 13:05:45.281 qfelevel = 2004
05/16/2007 13:05:45.296 sp = -1
05/16/2007 13:05:45.312
05/16/2007 13:05:45.328 Product Enumeration Results:
05/16/2007 13:05:45.343 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLServer2005_BC_x64.inf
05/16/2007 13:05:45.375 baselinebuild = 1399
05/16/2007 13:05:45.375 build = 2004
05/16/2007 13:05:45.390 description = Compatibilità con le versioni precedenti
05/16/2007 13:05:45.406 details = Service Pack per i componenti per la compatibilità con le versioni precedenti, tra cui Data Transformation Services Runtime e SQL-DMO.
05/16/2007 13:05:45.421 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.453 kbarticle = KB921896
05/16/2007 13:05:45.453 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.468 lcid = 1040
05/16/2007 13:05:45.484 legalproductname = Compatibilità con le versioni precedenti a Microsoft SQL Server 2005 (64 bit)
05/16/2007 13:05:45.500 machinetype = x64
05/16/2007 13:05:45.515 package = HotFixSQLServer2005_BC_x64
05/16/2007 13:05:45.531 packagetype = Hotfix
05/16/2007 13:05:45.546 productname = Redist9
05/16/2007 13:05:45.562 recommendinstall = 1
05/16/2007 13:05:45.578 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:45.593 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:45.609 splevel = 2
05/16/2007 13:05:45.624 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:45.640 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
05/16/2007 13:05:45.656 version = 9
05/16/2007 13:05:45.671
05/16/2007 13:05:45.703 File Group Details: MSI
05/16/2007 13:05:45.718 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:45.734 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:45.749 File Details: SQLServer2005_BC_x64.msi
05/16/2007 13:05:45.765
05/16/2007 13:05:45.781 Product Enumeration Results:
05/16/2007 13:05:45.796 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter.inf
05/16/2007 13:05:45.812 baselinebuild = 1399
05/16/2007 13:05:45.828 build = 3042
05/16/2007 13:05:45.843 description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.874 details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:45.890 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:45.906 kbarticle = KB921896
05/16/2007 13:05:45.921 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:45.937 lcid = 1040
05/16/2007 13:05:45.953 legalproductname = Microsoft SQL Server VSS Writer
05/16/2007 13:05:45.968 machinetype = x86
05/16/2007 13:05:45.984 package = HotFixSqlWriter
05/16/2007 13:05:45.999 packagetype = Hotfix
05/16/2007 13:05:46.015 productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.031 productname = Redist9
05/16/2007 13:05:46.062 recommendinstall = 1
05/16/2007 13:05:46.078 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.093 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.109 splevel = 2
05/16/2007 13:05:46.124 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>Microsoft SQL Server90Sharedsqlprov.exe
05/16/2007 13:05:46.140 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.156 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
05/16/2007 13:05:46.171 version = 9
05/16/2007 13:05:46.187
05/16/2007 13:05:46.203 File Group Details: MSI
05/16/2007 13:05:46.218 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.234 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.249 File Details: SqlWriter.msi
05/16/2007 13:05:46.281
05/16/2007 13:05:46.296 Instance Details: Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.312 fullversion = 9.00.3042.00
05/16/2007 13:05:46.328 lcid = 1040
05/16/2007 13:05:46.328 productcode = {DCEFDFAB-9543-4F03-ADAE-F6729C2B9966}
05/16/2007 13:05:46.359 qfelevel = 3042
05/16/2007 13:05:46.374 sp = -1
05/16/2007 13:05:46.390
05/16/2007 13:05:46.406 Product Enumeration Results:
05/16/2007 13:05:46.421 INF File Name: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSqlWriter_x64.inf
05/16/2007 13:05:46.437 baselinebuild = 1399
05/16/2007 13:05:46.453 build = 3042
05/16/2007 13:05:46.468 description = Microsoft SQL Server VSS Writer
05/16/2007 13:05:46.484 details = Service Pack per Microsoft SQL Server VSS Writer.
05/16/2007 13:05:46.499 installerlogpath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapLOGHotfix
05/16/2007 13:05:46.515 kbarticle = KB921896
05/16/2007 13:05:46.546 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/16/2007 13:05:46.562 lcid = 1040
05/16/2007 13:05:46.577 legalproductname = Microsoft SQL Server VSS Writer (64 bit)
05/16/2007 13:05:46.593 machinetype = x64
05/16/2007 13:05:46.609 package = HotFixSqlWriter_x64
05/16/2007 13:05:46.640 packagetype = Hotfix
05/16/2007 13:05:46.656 productname = Redist9
05/16/2007 13:05:46.671 recommendinstall = 1
05/16/2007 13:05:46.687 relatedlinks = <LCIDSUPPORTDIR>FinalSQL2005Information.rtf
05/16/2007 13:05:46.718 servicepackname = Installazione di Microsoft SQL Server 2005 Service Pack 2
05/16/2007 13:05:46.734 splevel = 2
05/16/2007 13:05:46.749 supportdir = e:3f798aa49a0102c6d1f049aa36bd359d
05/16/2007 13:05:46.781 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
05/16/2007 13:05:46.796 version = 9
05/16/2007 13:05:46.796
05/16/2007 13:05:46.827 File Group Details: MSI
05/16/2007 13:05:46.843 cachedmsipath = <PROGRAMFILESDIR>Microsoft SQL Server90Setup BootstrapCache
05/16/2007 13:05:46.859 sourcepath = <SUPPORTDIR><PACKAGE>Files
05/16/2007 13:05:46.874 File Details: SqlWriter_x64.msi
05/16/2007 13:05:46.890
05/16/2007 13:05:57.967 Registry: Opened registry key "SystemCurrentControlSetControlSession Manager"
05/16/2007 13:05:57.967 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:57.982 Multi-string values:
05/16/2007 13:05:57.998 Registry: Read registry key value "PendingFileRenameOperations"
05/16/2007 13:05:58.014 Multi-string values:
05/16/2007 13:05:58.029 ??e:1971703f8a5eaa69b207
05/16/2007 13:05:58.045 PFR Check: PFR was found, but no files to be serviced were being referenced
05/16/2007 13:06:18.980 Authenticating user using SAPWD
05/16/2007 13:06:18.995 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:19.011 Starting service: MSSQLServer
05/16/2007 13:06:23.666 Started service: MSSQLServer
05/16/2007 13:06:23.729 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:24.323 User authentication failed
05/16/2007 13:06:24.354 Messaggio 18456, livello 14, stato 1, server DC-01, riga 1
05/16/2007 13:06:24.385 Accesso non riuscito per l'utente 'sa'.
05/16/2007 13:06:24.416 Stopping service: MSSQLServer
05/16/2007 13:06:26.432 Stopped service: MSSQLServer
05/16/2007 13:06:29.978 Authenticating user using Windows Authentication
05/16/2007 13:06:29.994 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:30.009 Starting service: MSSQLServer
05/16/2007 13:06:34.837 Started service: MSSQLServer
05/16/2007 13:06:34.931 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:35.462 Authenticating user using Windows Authentication
05/16/2007 13:06:35.477 Validating database connections using Windows Authentication
05/16/2007 13:06:35.868 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.337 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:36.352 Validating database connections using Windows Authentication
05/16/2007 13:06:36.680 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:36.696 User authentication was successful
05/16/2007 13:06:36.696 Stopping service: MSSQLServer
05/16/2007 13:06:38.711 Stopped service: MSSQLServer
05/16/2007 13:06:40.461 Authenticating user using Windows Authentication
05/16/2007 13:06:40.477 SQL Service MSSQLServer was not previously running, started for authentication
05/16/2007 13:06:40.492 Starting service: MSSQLServer
05/16/2007 13:06:45.086 Started service: MSSQLServer
05/16/2007 13:06:45.101 SQL Agent Service SQLSERVERAGENT was not previously running
05/16/2007 13:06:45.523 Authenticating user using Windows Authentication
05/16/2007 13:06:45.539 Validating database connections using Windows Authentication
05/16/2007 13:06:46.085 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.414 Received sysadmin status for instance: MSSQLSERVER
05/16/2007 13:06:46.429 Validating database connections using Windows Authentication
05/16/2007 13:06:46.742 Pre-script database connection check was successful - proceeding with script execution
05/16/2007 13:06:46.757 User authentication was successful
05/16/2007 13:06:46.773 Stopping service: MSSQLServer
05/16/2007 13:06:48.788 Stopped service: MSSQLServer
05/16/2007 13:06:48.835 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.851 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:48.866 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:48.882 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.287 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.303 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.319 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/16/2007 13:06:55.662 Locked file: Checking for locked files
05/16/2007 13:07:05.099 Attempting to pause the 32 bit ngen queue
05/16/2007 13:07:05.271 Installing product: SQL9
05/16/2007 13:07:05.286 Installing instance: MSSQLSERVER
05/16/2007 13:07:05.302 Installing target: DC-01
05/16/2007 13:07:05.317 Installing file: sqlrun_sql.msp
05/16/2007 13:07:05.349 Copy Engine: Creating MSP install log file at: C:ProgrammiMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log
05/16/2007 13:07:05.364 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:07:05.380 Registry: Cannot read registry key value "Debug"
05/16/2007 13:09:06.458 MSP Error: 29506 Impossibile modificare le autorizzazioni di protezione del file C:ProgrammiMicrosoft SQL ServerMSSQL.1MSSQLData per l'utente SYSTEM. Per continuare, verificare l'esistenza dell'account e del dominio che eseguono l'installazione di SQL Server. Verificare inoltre che tale account disponga dei privilegi di amministratore e che sia presente nell'unità di destinazione.
05/16/2007 13:10:03.685 MSP returned 1603: Si è verificato un errore irreversibile durante l'installazione.
05/16/2007 13:10:03.701 Registry: Opened registry key "SoftwarePoliciesMicrosoftWindowsInstaller"
05/16/2007 13:10:03.716 Registry: Cannot read registry key value "Debug"
05/16/2007 13:10:04.248 Copy Engine: Error, unable to install MSP file: e:3f798aa49a0102c6d1f049aa36bd359dHotFixSQLFilessqlrun_sql.msp
05/16/2007 13:10:04.310 The following exception occurred: Impossibile installare il file MSP di Windows Installer Date: 05/16/2007 13:10:04.310 File: depotsqlvaultstablesetupmainl1setupsqlsesqlsedllcopyengine.cpp Line: 800
05/16/2007 13:10:08.966 Watson: Param1 = Do_sqlFileSDDL
05/16/2007 13:10:08.997 Watson: Param2 = 0x7342
05/16/2007 13:10:09.044 Watson: Param3 = ExceptionInSDDL
05/16/2007 13:10:09.075 Watson: Param4 = 0x7342
05/16/2007 13:10:09.106 Watson: Param5 = sqlcasqlsddlca.cpp@65
05/16/2007 13:10:09.153 Watson: Param6 = Unknown
05/16/2007 13:10:09.184 Watson: Param7 = SQL9
05/16/2007 13:10:09.200 Watson: Param8 = Hotfix@
05/16/2007 13:10:09.231 Watson: Param9 = x86
05/16/2007 13:10:09.247 Watson: Param10 = 3042
05/16/2007 13:10:09.309 Installed product: SQL9
05/16/2007 13:10:09.356 Hotfix package completed
05/16/2007 13:10:09.388 Attempting to continue the 32 bit ngen queue
View 1 Replies
View Related
Jul 25, 2007
Hello, How are you?
I have a problem when I try to create a new connection with Microsoft SQL Server 2005 Compact Edition from Visual Studio 2005 IDE. When I€™m going to choose the data source, the SQL Server 2005 Compact Edition provider doesn€™t appear in the list. I installed the SQL Server 2005 Compact Edition from this page http://www.microsoft.com/downloads/details.aspx?FamilyId=%2085E0C3CE-3FA1-453A-8CE9-AF6CA20946C3&displaylang=en. In the additional information says by installing SQLServerCE31-EN.msi installs the provider (System.Data.SqlServerCe.dll) in the GAC (global assembly cache) and registers the OLEDB provider (sqlceoledb30.dll). So, I don€™t understand why couldn€™t I create a new connection with Microsoft SQL Server 2005 Compact Edition from Visual Studio 2005 IDE?
I appreciate your help€¦
View 6 Replies
View Related
Jul 18, 2006
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
View 1 Replies
View Related
Jul 18, 2006
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
View 2 Replies
View Related
Apr 17, 2007
Hi,all BI experts here,
Thank you very much for your kind attention.
I am having a problem with connecting to SQL Server 2005 database from Office Business Scorecard Manager 2005 (the connection string i am using is: provider=SQLOLEDB;Data source=server_name; Initial catalog=database_name). But the connection failed. Would please any experts here shed me any light on what is the problem and how to fix it then? As there is no any forum for Office Business Scrorecard manager 2005. Therefore I post my thread here as it is related to the connection to SQL Server 2005 database engine, thought here is the best place for this question.
Thank you very in advance for your kind advices and help. And I am looking forward to hearing from you soon.
With best regards,
Yours sincerely,
View 6 Replies
View Related
Jul 18, 2006
Hello, I would like to know if anyone here has any information on how to change the default version of SQL Server 2005 Express which ships with Visual Studio 2005 to the new SQL 2005 Express SERVICE PACK 1?
I see a file under disc:vswcuSSESQLEXPR.exe I am wondering if changing that file with the new one from Microsoft Download Center will do it...
There's another file under that folder named sqlexpr32.exe I am wondering what it's for?
Thanks in advance.
View 4 Replies
View Related
Jun 26, 2015
How does one enable sql connections limits for user connections per new and existing databases? how to do it on whole server per database but not set a limit per user.Looks like this must be run on each databases but what if you have 100s of databases:
USE AdventureWorks2012 ;
GO
EXEC sp_configure 'show advanced options', 1;
GO
RECONFIGURE ;
GO
EXEC sp_configure 'user connections', 325 ;
GO
RECONFIGURE;
GO
View 3 Replies
View Related
Jul 26, 2007
Hi Fellas,
I would really appreciate if you could help me out with the following two questions?
1) Can 2005 server files be converted to 6.5? and how?
2) How easy it to upgrade from 6.5 to 2005? and how?
I would be really grateful by your help
Nick
View 3 Replies
View Related
Aug 1, 2006
I need Microsoft SQL Server 2005 direct link even if is trail
plz...
View 7 Replies
View Related
Aug 31, 2006
What is the maximum number of DB that I can create? Infinite?Thanks
View 1 Replies
View Related
Nov 10, 2006
Hi,I have a requirement of SQL server 2005 but I am confused about the different edition like Workgroup Edition, Standard Edition, Enterprise Edition. What is the feature base difference in these editions. Can any one help me on this issue it's urgent.
I am running a database server in SQL Server 2000 websites (ASP.net application is also running there) and the database access will be high as there are number of websites accessing data from it.Thanks in advance.Ankur
View 6 Replies
View Related
Oct 20, 2007
I just recently installed SQL Server 2005. I have a question about "SQL Server Management Studio".
I want my machine to act as the db server, so I can learn the basics of SQL Server 2005. Once I open
"SQL Server Management Studio" and attempt to connect to a database engine, I get the following error
Cannot connect to database engine....
I don't see any services running in the windows services console, I used to
work with SQL Server v7 awhile back and I remember within the left frame of "SQL Server Management Studio"
window, in the Registered Servers frame that the "Database Engine" icon usually had a green right arrow in it
when it was running correctly. Right now I have this "Database Engine" icon but there is a white circle with
no right green arrow signifying that it is running....
Thanks in advance for your help,
Wes
View 1 Replies
View Related
Nov 6, 2007
Hi,I have a Microsoft SQL Server 2005 Enterprise installed on Windows Server 2003, and developing web application for 500 clients. So I am interested will I have any performance issues if I put in 'Articles' table, data for all 500 clients and then filter it on client ID, or should I make 500 'Articles' tables for every client one with different name and then change sqldatasource for gridview depending on which client is working on it. I will have, beside 'Articles' table, another 10 tables, which means 5500 tables total, if I use second approach, on first I will have only 11 tables. So I am asking is it better to have more tables with less data, or less tables with more data. And what are pros and cons for both approach. Thanks a lot!
View 1 Replies
View Related
Mar 1, 2006
Hi,
Firstly, I had to post this query here since I did not find any other place relating to Microsoft SQL Analysis Server 2005 and that it is related to SQL server 2005.
I am using Microsoft SQL analysis server 2005 and .NET 1.1 for Asp.NET (C#)
I need to programmatically create Measures, Dimensions and Cubes using .Net 1.1 (C#) in an Asp.NET page, and then I need to access the measures, dimensions and cubes again from another Asp.Net page.
My querys are:
1. To create and manipulate the SQL Analysis server objects like Dimensions, Cubes what should I use? The documentation for Analysis server 2005 says we can use (Analysis Management Objects)AMO. but I am not sure if we can use it with .NET 1.1?
2. If AMO is possible, then what to use? There is one more technology we can use called as (Deciscion Suport Objects) DSO. but they are COM based and were for Analysis services 2000.
3. To query the data, what technology can I use? Microsoft says we can use ADOMD.NET. Microsoft also gives many other technologies that I think do similar work, like XMLA, ASSL.
Can somebody help me in this.
Also please do give me some links that have code samples for the same.
Thanks and Regards
Vijay R
View 1 Replies
View Related
Mar 25, 2008
Hello,
I need the Microsoft SQL Server 2005 Edition Express SP2 and the Management Studio Express SP2 in 4 languages (French, English, German, Spanish).
Where can I found a multilanguage (if exist) and the parameters to an unnaattended install off the Management Studio Express (I have for the Server 2005 Edition Express)?
In the same Idea, It's also exist for the Framework 2.0 (and the parameters)?
Thanks in advance
Best Regards
View 7 Replies
View Related
Nov 1, 2007
The Microsoft SQL Server Driver for PHP Team is proud to announce the availability of the Microsoft SQL Server 2005 Driver for PHP CTP. This driver is a PHP 5 extension that allows the reading and writing of SQL Server data from within PHP scripts. The extension provides a procedural interface for accessing data in all editions (including Express editions) of SQL Server 2005 and SQL Server 2000. The API makes use of PHP features, including PHP streams to read and write large objects.
The SQL Server 2005 Driver for PHP Community Technology Preview (October 2007) is a preview release not intended for production purposes and can be downloaded here. To provide feedback or to get more information, visit our team blog at http://blogs.msdn.com/sqlphp . Please post any questions you have about this CTP release in this forum.
Thanks.
The SQL Server Driver for PHP Team
View 1 Replies
View Related
Mar 7, 2007
An issue was recently discovered with SQL Server 2005 SP2 which might impact customers using cleanup tasks in Maintenance Plans and SQL Server Integration Services packages. The issue is described in detail here. We have created a General Distribution Release (GDR) #50000939 to address this issue which is available for download and we have included the GDR in a refresh of the SP2 installation package.
Customers who download SP2 starting Monday, March 5th, 2007 will not need to need any further action since the refreshed SP2 installation package includes the necessary GDR.
We recommend that everyone who has downloaded and installed SP2 prior to March 5th, 2007 apply the GDR either from Microsoft Update or by downloading it directly from http://go.microsoft.com/fwlink/?LinkId=85124. As described in the KB article, this is primarily for customers who use cleanup tasks in maintenance plans and SQL Server Integration Services packages.
Maintenance Plan Changes in SQL Server 2005 SP2
Users of SQL Server 2005 maintenance plans and SQL Server Integration Services should be aware of a change in SP2 that affects existing cleanup tasks until updated using SQL Server SP2 tools.
Who is affected?
You are affected if you use cleanup tasks in Maintenance Plans and SQL Server Integration Services packages, those plans include a History Cleanup Task or a Maintenance Cleanup Task, and you install SQL Server 2005 SP2. Users of SQL Server 2000 legacy maintenance plans are not affected.
What is the issue?
When SQL Server 2005 was released, cleanup intervals were measured in days, weeks, months, or years. In response to customer feedback, SQL Server 2005 SP2 includes significant enhancements to maintenance plans. These include an enhancement that lets users specify the cleanup interval in hours.
The change in intervals caused the initial release of SQL Server 2005 SP2 to misinterpret existing cleanup task intervals in maintenance plans and Integration Services packages. This can lead to the files being cleaned up earlier than intended. The issue is described in detail here.
What if I have already installed SP2 on my server?
If you downloaded SQL Server 2005 SP2 before Monday, March 5th, 2007, install a general distribution release (GDR) update for those SQL Server 2005 SP2 installations. The GDR is available at the Microsoft Download Center:
Critical Update for SQL Server 2005 Service Pack 2
After you install this GDR, you might have to restart your computer.
This GDR is also available through Microsoft Update, and will be applied automatically if you are using automatic updates. However, if you are using failover clustering, you must download and apply the GDR manually. Microsoft Update will not apply the GDR to failover cluster nodes.
What if I haven't yet installed SP2 on my server?
SQL Server 2005 RTM and SQL Server 2005 SP1 do not have this issue, and the current SQL Server 2005 SP2 download is updated to resolve this issue. If you have not installed the initial release of SP2, you can download the current release and install it.
Note: If you try to apply the SP2 refresh over a previous SP2 installation, no files are updated. Instead, use the general distribution release (GDR) update below.
View 5 Replies
View Related
