SQL 2005 SP2 Error 29506 Workaround Doesn't Work - Data On LUNs

May 13, 2008

I have had the same Error 29506 that a lot of people are having when installing SP2 for SQL 2005. I've tried the install with myself (a Domain Admin), local Administrator, cascaded full rights down the entire file system structure and still not luck. One thing I'm wondering if it is hanging me up is that all of my databases and logs are not on C:. They are on LUNS on a NetApp SAN (Data is on M: and Logs is on L:). Even the system databases (Master, Model, etc.) are on the LUNs. The error logs referenced permissions to the data directory under the default installation path on C:. Anyone else have this problem? Got a fix? I really don't want to migrate all of my data back to the local machine, apply the patch, them migrate back. Surely this SP should be able to read the data location from the SQL engine. And surely others have their databases on SANs.... I'm at a loss.

Thanks.

View 3 Replies


ADVERTISEMENT

Sql 2005 Sp2 Install Error Microsoft SQL Server 2005 -- Errore 29506

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

Failure Installing Sql Server 2005 Express On Vista Ultimate X64, Error 29506

Feb 4, 2007

Whenever I try to install SQL Server 2005 Express Edition on my Vista Ultimate x64 platform I get error 29506. All I could find on the web was that this is probably due to an access control problem. I have tried installing it as the local administrator, as a member of domain admins, and as the domain administrator. All get the same error. My domain is a Small Business Server domain. This may be part of the problem, but I can't imagine how.

When trying to force access to the domain administrator, I also seem to get an access problem.

Any suggestions?

View 3 Replies View Related

Why This Trigger Doesn't Work In Sql 2005

Mar 28, 2008

hi eveyrone,

I have an after insert trigger that works in sql2000 but not in sql2005. Can you please help me!!

CREATE trigger dbo.trUPS_tbl_I
on dbo.UPS_tbl
After Insert --For insert
as
declare @Tracking varchar(800),
@UPSID varchar(10),
@Cmmd varchar(800)

select @UPSID = cast(inserted.UPSID as varchar)
from inserted

commit

set @Cmmd = 'c:TasksUpdTrackingUpdateTrackingCS ' + @UPSID + ' ' + 'UPS1'
EXEC master.dbo.xp_cmdshell @Cmmd


The UpdateTrackingCS program will call a stored procedure to get the inserted data and update other databases. And the reason to put the commit statement in sql2000 is to have sql commit the transaction, so the store procedure in UpdateTrackingCS can query thtat inserted records.

When I use the same code in SQL2005, no matter what I do the UpdateTrackingCS program cannot query the data by the UPSID. It always says record not found.

I have tried to change commit to begin trans ... commit trans. But nothing works. Please help!

Thanks in advance.

lyw

View 1 Replies View Related

Why This Trigger Doesn't Work In Sql 2005

Mar 28, 2008

hi eveyrone,

I have an after insert trigger that works in sql2000 but not in sql2005. Can you please help me!!

CREATE trigger dbo.trUPS_tbl_I
on dbo.UPS_tbl
After Insert --For insert
as
declare @Tracking varchar(800),
@UPSID varchar(10),
@Cmmd varchar(800)

select @UPSID = cast(inserted.UPSID as varchar)
from inserted

commit

set @Cmmd = 'c:TasksUpdTrackingUpdateTrackingCS ' + @UPSID + ' ' + 'UPS1'
EXEC master.dbo.xp_cmdshell @Cmmd


The UpdateTrackingCS program will call a stored procedure to get the inserted data and update other databases. And the reason to put the commit statement in sql2000 is to have sql commit the transaction, so the store procedure in UpdateTrackingCS can query thtat inserted records.

When I use the same code in SQL2005, no matter what I do the UpdateTrackingCS program cannot query the data by the UPSID. It always says record not found.

I have tried to change commit to begin trans ... commit trans. But nothing works. Please help!

Thanks in advance.

lyw

View 8 Replies View Related

2000 Active X Doesn't Work In 2005

Feb 12, 2007

I have an active x script written in vb that just counts the records in a table and fails the step if there are not enough records. It is simple and effective. But when I transfered this task to my SSIS package I get a function not found error.

I am not familiar with active x or vb script so I have no idea what is wrong. I can do without while I build the package but I need it in the end to prevent possible problems....

Here is the script...

'**********************************************************************

' Visual Basic ActiveX Script

'************************************************************************

Function Main()

dim myConn

dim myRecordset

dim iRowCount

' instantiate the ADO objects

set myConn = CreateObject("ADODB.Connection")

set myRecordset = CreateObject("ADODB.Recordset")

' Init ADO Connection object

With myConn

.ConnectionString = "File Name=D:Data Linksmusic_load.udl;" 'Full path to the UDL

.Open

End With



mySQLCmdText = "Select 'totalcount' = Count(*) from fulltext"

myRecordset.Open mySQLCmdText, myConn

set Flds = myRecordset.Fields

set iRowCount = Flds("totalcount")

If iRowCount.Value < 1000000 then

' MsgBox "The number of products is: " & iRowCount.Value & ". The total number is wrong"

Main = DTSTaskExecResult_Failure

Else

' MsgBox "The number of products is: " & iRowCount.Value & ". The total number is good"

Main = DTSTaskExecResult_Success

End If



End Function

View 2 Replies View Related

SQL Server 2005 Express Doesn't Work With .NET Framework 3.0

Sep 22, 2007

Hi,

Can anybody help me with the following problem:

I have Vista Ultimate installed and within Vista .NET Framework 3.0 is installed as a part of the operating system so I can't remove 3.0
Now for MS SQL Server 2005 Express I need .NET Framework 2.0 and the SQL Server 2005 doesn't work with .NET Framework 3.0
Can't install 2.0, get the message that 3.0 is already installed.
Is there another version of SQL Server that works with .NET Framework 3.0 and runs under Vista Ultimate?
Please help me!!

René

View 3 Replies View Related

ASP And SQL 2005 Passing And Returning Parameters Doesn't Work...help!!!!!

Feb 29, 2008

Ok, I'm a long time reader of this forum and just about everytime I come here looking for an answer its allready been posted and answered. But I can't seem to find this one anywhere. Sorry if its allready been posted...Just point me in the right direction.

Ok, Ive been coding in VB2005 for a while but i'm new to SQL stored procedures. This is prolly going to sound stupid but I don't know where to start. Heres what I need to do.

I have a stored procedure that requires a parameter. I can pass that parameter to the stored procedure and execute it just fine. But I need the result thats returned when the stored procedure is executed. I can't seem to find anyway to return the Result back to me. DataReaders keep blowing up and I have no Idea Why????? Here is how i'm passing the param to the stored proc.

I'm running MS SQL BTW.


Dim myConnection As New SqlClient.SqlConnection("yadayada;Database=BlaBlaBla;Trusted_Connection=True;")

Dim cmd As New SqlClient.SqlCommand("NameOfStoredProc")

cmd.Connection = myConnection

cmd.CommandType = CommandType.StoredProcedure

Dim sqlParam As SqlClient.SqlParameter

sqlParam = cmd.Parameters.Add("Variable", SqlDbType.VarChar, 22)

sqlParam.Value = Address 'declared higher up.....its just an int

myConnection.Open()

cmd.ExecuteNonQuery()

myConnection.Close()



Thats all great, but I need to read back the results the stored proc returns. If I execute this in server management studio, it returns a result. But nothing I try in my asp page works. Any help would be Great. Code samples are good too.

View 12 Replies View Related

Maintenance Plan For SQL Server 2005 64-bit Doesn't Work!

Jul 5, 2007

Hi all,
We have a SQL Server 2005 64-bit, and recently I upgrade from build 3042 to 3054 and I try to do a maintenance plan for transaction logs(TL) backup, including cleanup for two days (have full backup every night).

Problem I have is that I want the TL files to dump in a different location(due to disk space), so I put in the UNC path in the "Create a backup file for every database - >Folder:\FileServerTLDBLogs"

NB: if using the local drives, it work

Check List
Security:
- The account that I used to create the plan is an sa account
- The location that I dump the TL files, I have full access to the folder

SQL Statement:
exec xp_cmdshell 'dir FileServerTLDBLogs' (it list all files)

Is this a bug for 64-bit? because I can do this on SQL Server 2005 32-bit and it's work perfectly

View 1 Replies View Related

Error 'Cannot Create A Row Of Size Xxxx' - My Fix Doesn't Work

Jul 12, 2007

Been doing some research after getting this error:
Microsoft OLE DB Provider for SQL Server error '80040e14'

Cannot create a row of size 8297 which is greater than the allowable maximum of 8060.


And realised that my nice responsive varchars had a maximum total size. so I changed them for 'slower' text data types. but my DB still won't allow any more input.

has the limit been reached now regardless of what I change or can I rebuild the DB to recover the space or something?

View 14 Replies View Related

Trouble With Trigger: Doesn't Seem To Work At All And No Error Messages.

Oct 3, 2007

Hi Everyone,
I'm having some trouble with the below trigger. When I add a row of data either manually or using an INSERT query, it just doesn't do anything. It doesn't provide any error messages either. This makes me think that it's aborting the operation because rowsAffected are 0 or some other simple error. My row manipulation code could be suspect also. This is my first time writing a trigger or using T-SQL for that matter.
What I'm trying to do is to have the trigger add +1 to the Iter field of all rows where BouleID is equal to the BouleID of the row being inserted. So let's say I have the following table:


BouleID CurrentLocation Iter
A01 Inventory 1
A01 Cutting 0
A01 WIP 2
B01 WIP 0
B02 WIP 1
B02 Inventory 0

Now, if I insert a row with BouleID = A01 and Current Location = Polishing, I want the Iter field of all previous rows to iterate by +1 and this new row to have Iter = 0.

I am using SQL Management Studio Express, and SQL Server Express.

Any thoughts on anything wrong with my selection code and iteration code? Could I adapt this to handle more than one row by using a GROUP BY BouleID somehow?






Code Block

SET ANSI_NULLS ON


GO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Description: <this trigger will iterate the Iter field by one for each rows that has the BouleID matching the one of
-- the row being inserted>
-- =============================================
CREATE TRIGGER dbo.trgCG_DispoIterate$InsertTrigger
ON dbo.dbCG_Disposition
AFTER INSERT AS
BEGIN

DECLARE @rowsAffected int,
@msg varchar(2000), --for error message
@BouleID varchar(6) -- and do I need to enter more than one?

SET @rowsAffected = @@rowcount

IF (@rowsAffected = 0 or @rowsAffected > 1 ) RETURN --don't continue if no rows changed or doing more than one at a time.
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON
SET ROWCOUNT 0

BEGIN TRY

--VALIDATION BLOCK Leave this alone for now

SELECT @BouleID = BouleID FROM Inserted --sets @bouleID equal to the BouleID of the row being inserted.

UPDATE dbo.dbCG_Disposition --This block sets the Iter field to it's previous value +1
SET Iter = ( Iter + 1 ) --
WHERE BouleID = @BouleID --


END TRY
BEGIN CATCH
IF @@TRANCOUNT >0
ROLLBACK TRANSACTION

--or this will get rolled back
EXECUTE dbo.ErrorLog$Insert -- this function creates an errorlog table which gets filled up if there is an error in the try block.

DECLARE @ERROR_MESSAGE nvarchar(4000)
SET @ERROR_MESSAGE = ERROR_MESSAGE()
RAISERROR (@ERROR_MESSAGE, 16, 1)
END CATCH

View 6 Replies View Related

T-SQL (SS2K8) :: Paging Data Doesn't Work

Jun 12, 2014

This my stored procedure

ALTER PROCEDURE [dbo].[PageWise]
@PageIndex INT = 1
,@PageSize INT = 10
,@PageCount INT OUTPUT,
@CatId int

[code]....

I'm trying to paging data but page size doesn't work and it returns all data.

View 8 Replies View Related

Import Excel Data Doesn't Work.

Dec 7, 2005

Hi there,

I'm having trouble getting an import to work.

Here what i want:

i have created a dsn to extract data from an SQL2000 server into Excel. this all works fine. Now i have edited the data and would like to import the updated fields in my database.

There are no new fields just updated information. I have used the import wizard from SQL Enterprise manager. I have selected to delete the current table and replace is with the one ive created.

This is where the problems begin.

When i finish the wizard i get an error saying there is a conflict "collum reference constraint". wich i think has something to do that there are links to this table wich can not be simply deleted and recreated.

How do i get around this?

Greets Axel

View 2 Replies View Related

VS 2005 Doesn't Work With SQL Server 2005.

Jul 23, 2007

When I try to add a SQL Server Database as a new item into the App_Data folder of my Web Project, I get this error demanding that SQL Server Express has to be installed. That is the stupidest thing I have ever heard of. Is there some setting or something to make VS 2005 Pro work with a standard SS database? I don't want to use the express edition. I can't use SS's management studio with that.



Does Microsoft monitor this forum? I thought they were going to be taking technology forward; not backwards. I'm losing a lot of time having to install and uninstall and reinstall to get the environment into a mode that works lke I want it to work. If they didn't intend for SS standard edition to be used with VS 2005 Pro, then why did they include SS developers edition in the Pro package?

View 2 Replies View Related

Pass-thru Query Doesn't Work With A SQL 2005 SSIS Package

Dec 14, 2007

I am trying to execute an SSIS package from an MS Access 2003 database that imports a table from the Access database into a target table in SQL 2005. I saved the package in SQL 2005 and tested it out. If I run it from the Management Studio Console with Run->Execute ... everything works just fine. However, if I try to run it using the following line command "Exec master.dbo.xp_cmdshell 'DTExec /SER DATAFORCE /DTS SQL2005TestPackage /CHECKPOINTING OFF /REPORTING V'" the execution will always fail when the Access database is open (shared mode). The connection manager looks like this: "Data Source=E:Test.mdb;Provider=Microsoft.Jet.OLEDB.4.0;Persist Security Info=False;Jet OLEDB:Global Bulk Transactions=1". The error is listed below:

Code: 0xC0202009
Source: NewPackage Connection manager "SourceConnectionOLEDB"
Description: An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft JET Database Engine" Hresult: 0x80004005 Description: "Could not use ''; file already in use.".


What am I doing wrong?

View 4 Replies View Related

Any Idea Why OpenRowSet To Open Excel File Doesn't Work Well In SQL 2005?

Mar 3, 2007

Maybe it worked once, but in most time it doesn't work, query like below

select top 10 *
from OpenRowSet('microsoft.jet.oledb.4.0','Excel 8.0;hdr=yes;database=\ws8webablefilessitefiles4000010
eibcactive.xls',
'select * from [crap2$]')


I got error

OLE DB provider "microsoft.jet.oledb.4.0" for linked server "(null)" returned message "Unspecified error".
Msg 7303, Level 16, State 1, Line 1
Cannot initialize the data source object of OLE DB provider "microsoft.jet.oledb.4.0" for linked server "(null)".


but the same query can run without any problem on a SQL 2000 server run on a server in the same network.

Any idea?

View 12 Replies View Related

Integrated Security Doesn't Work - Not Associated With A Trusted SQL Server Connection. Error

Oct 20, 2006

 

Hi,

I have a piece of Java code that needs to connect to SQL 2000 (SP4) using Windows Authentication. It's running on Windows Server 2003 SP1.

I tried JDBC v1.1 and followed the code from the following blog:

http://blogs.msdn.com/angelsb/default.aspx?p=1

But still get this error as shown below. Any help appreciated.

I am using JDK1.4.2, "sqljdbc_auth.dll" is located under "E:SQL2005JDBCDrvsqljdbc_1.1enuauthx86", also made a copy under "E:JavaTest" and "C:WindowsSystem32" but still won't work.

Cheers

Allan

 

===========================================================

E:JavaTest>javac -classpath ".;E:JavaTestsqljdbc.jar" TestW2.java

E:JavaTest>java -classpath ".;E:JavaTestsqljdbc.jar" -Djava.library.path=E:S
QL2005JDBCDrvsqljdbc_1.1enuauthx86  TestW2
com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user '(null)'.
 Reason: Not associated with a trusted SQL Server connection.
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError
(Unknown Source)
        at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.processLogon(Unknown
 Source)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(Unknown Source
)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknow
n Source)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover
(Unknown Source)
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Sour
ce)
        at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
        at java.sql.DriverManager.getConnection(Unknown Source)
        at java.sql.DriverManager.getConnection(Unknown Source)
        at TestW2.main(TestW2.java:7)
===========================================================

The code is simple (TestW2.java):

import java.sql.*;

public class TestW2 {
 public static void main(String[] args) {
  try {
   java.lang.Class.forName("com.microsoft.sqlserver.jdbc.SQLServerDriver");
   Connection conn = java.sql.DriverManager.getConnection("jdbc:sqlserver://VMW2k3ENT003.TESTCBFPOC.COM.AU;integratedSecurity=true");
   System.out.println("Connected!");
   conn.close();

  } catch (Exception ex) {
   ex.printStackTrace();
  }
 }
}

==============================================================

View 27 Replies View Related

Data Mining Add-Ins Doesn't Work With Non-English Regional Settings

Dec 23, 2006

I tried Data Mining Add-Ins for Office 2007 - CTP December 2006.
Test settings: Windows XP SP2 english with Italian regional settings, Office 2007 english (RTM), SQL Server 2005 Developer (with SP2 CTP Dec06) and Data Mining Add-ins for Office 2007 (CTP Dec06).

If I keep regional settings in Italian, I get error like this:

Old format or invalid type library. (Exception from HRESULT: 0x80028018 (TYPE_E_INVDATAREAD))

If I change regional settings to English, the Add-in works.

I found this description as the possible cause of the problem: http://msdn2.microsoft.com/en-us/library/ms178780(vs.80).aspx - if this is the issue, it would be necessary to change the ExcelLocale1033Attribute on the component.

Is there another workaround other than to install the Office 2007 MUI?

Marco Russo
http://www.sqlbi.eu
http://www.sqljunkies.com/weblog/sqlbi

View 10 Replies View Related

Parameters Approach To Fill Report Header With Source Data Doesn't Work

Jan 19, 2007

It's well known issue, that one can't use any dataset fields in a
report header/footer directly. One of the approach is to create
query-based parameter that basically equals
=First(Fields!@FieldName@.Value, "@DataSetName@") and use that
parameter value instead. But it doesn't work in my case!



My report displays some entity description and is parametrized with
EntityID param. Its header contains entity name that, according to the
approach, is queried from the data source through the EntityName
report parameter. There's important issue: the report is displayed in
ReportViewer control, that is embedded into my application and entity
ID parameter isn't ser by user in ReportViewer parameters area. Its
default value is changed by the application with SetReportParameters()
web method every time a user wants to view the report according to the
entity the user is exploring in the application. But after the report
has been rendered, its header always contains not actual (outdated)
entity name. Nevertheless, the report body contains actual data
(including entity name). If I alter entity ID parameter in ReportViewer
or in web-based Report Manager and refresh report, header displays
correct entity name.



What's wrong in the workflow described?

View 3 Replies View Related

SQL Server Management, Error 29506

Mar 20, 2007

I tried to install this evening SQL Server Management Express on my Windows Vista 32 bit Home Premium Edition + Sql server 2005 express.

The problem is that at the end of the installation this error comes out:


"Si è verificato un errore imprevisto durante l'installazione di questo pacchetto. Probabile problema con questo pacchetto. Il codice errore è: 29506"

What could I do?



Thanks Luke

View 45 Replies View Related

Package With File System Task Doesn't Work Without Sensitive Data With User Keys

Dec 14, 2006

This problem is a bit weird but I'm just wondering if anybody else experienced this.

I have a package that has file system tasks (copying dtsx files actually). Basically the package copies other packages to a pre-defined destination. Thing is, it only works if one of the packages it is configured to copy has some sort of sensitive data (e.g., a connectionstring with a password), otherwise it reports a success message on execution but doesn't actually do anything. I've checked the forcedexecutionresult and it is set to None for that matter.

Just wondering if anybody else experienced this problem and of course if there's a way to solve it.

Thanks.

View 2 Replies View Related

Error 29506. SQL Server Setup Failed To Modify Security Permissions

Aug 15, 2007

Received the following error while installing SP2

MSI (s) (D8!A0) [21:07:09:062]: Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user Administrator. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive.

Tried running install with a domain account and local account with same results.

Based on the error message, I checked permission on the drive and still received the same error.

Followed resolution based on KB 916766, this did not resolve the error.

Only possible resolution I found was to disable UAP, reboot and retry the install. This will be done as a last resort, but any other suggestion will be appreciated.


Many Thanks

View 3 Replies View Related

Workaround Divide By Zero Error Encountered Message

Jan 7, 2004

Hey all,

When i exec an sp it runs a sum, sometimes it is possible that there is a 0 value, it then returns an error Divide by zero error encountered
How can i work around this error

My sp code is

CREATE proc CP_avgloss_rings
@mID varchar(10),
@startdate datetime,
@enddate datetime
as
select ((sum(vtp)-(sum(moneyout)))/100) / ((sum(playtime))/ 3600) as avgloss
from dbo.rings
where
machineID = @mID
and convert(varchar,njdate,121)
between convert(varchar,@startdate,121)
and convert(varchar,@enddate,121)
GO


Maybe someone can help me
Cheers Wimmo

View 4 Replies View Related

DTS Doesn't Work Through Job

Sep 15, 2005

I'm pretty new to DTS, so forgive me if this is basic. I created a simple DTS package to run a query and export it to a text file. I can execute the package fine from my workstation through EM, but when I try to execute the job to run the package I get this error:
Error = -2147467259 (80004005) Error string: Error opening datafile: Access is denied.

I think that maybe SQL Agent doesn't have the right permissions to write to that network drive. What should the permissions be?

View 3 Replies View Related

IIF Doesn't Work

Nov 10, 2004

This is probably very simple, but I can't get passed this problem.

I have a report in MS Access that uses info generated by a query. One of the text fields in the query contains either the word 'Select' or the name of a course.
The report should display a space if the value is 'Select', or the actual value of the field in any other case. The field can never contain a null value.

I've used:
=IIf([optVoc1]="Select","",[optVoc1])
in the text box on the report, but this only returns #error regardless of the actual content of the field.

What am I doing wrong?

Regards,

BD

View 5 Replies View Related

Sql Job Doesn't Work

Aug 27, 2004

Hi all,

I create and schedule a SQL job to run every minute to update a table base on certain condition but it doesn't work. Job history says successful every time but the table doesn't get updated.

However if I move it to Query Analyzer and run it under dba, it will work. Thinking that it may have to do with the user the job run as, I then change run as user from self to dba. But still SQL job won't update my table.

Anything about user permission or security that I can check? Or it there any other possibility?

TIA

View 1 Replies View Related

Why Doesn't This Work

Apr 26, 2007

When I run the select its fine but I cannot delete..... i have done this many times and it has worked.... I cannot see the error what am i missing

select
eqnow.empnumber,
eqnow_names.empnumber,
eqnow_names.names
--delete
from
eqnow
inner join eqnow_names
on eqnow.empnumber = eqnow_names.empnumber
where
eqnow_names.names is null



i get this error
Server: Msg 156, Level 15, State 1, Line 4
Incorrect syntax near the keyword 'inner'.

View 3 Replies View Related

Doesn't Work

Oct 21, 2007



Msg 15123, Level 16, State 1, Procedure sp_configure, Line 78

The configuration option 'user instances enabled' does not exist, or it may be an advanced option.



Valid configuration options are

View 1 Replies View Related

Help! LIKE Doesn't Work!!!

Apr 19, 2008

Hi to all, I'm building (and learn) an application with VB Express. In "edit dataset with designer" I've build this sql query:

SELECT tbl_soggetto.[ID Soggetto], tbl_soggetto_tipo.Tipo, tbl_soggetto.[Cognome/Denominazione], tbl_soggetto.Nome, tbl_soggetto.Indirizzo, tbl_soggetto.CAP, tbl_soggetto.Città , tbl_soggetto.Provincia, tbl_soggetto.[Telefono 1], tbl_soggetto.[Telefono 2], tbl_soggetto.[Telefono 3], tbl_soggetto.[Telefono 4], tbl_soggetto.[eM@il 1], tbl_soggetto.[eM@il 2], tbl_soggetto.Note
FROM tbl_soggetto INNER JOIN tbl_soggetto_tipo ON tbl_soggetto.[ID Tipo] = tbl_soggetto_tipo.[ID Tipo]
WHERE (tbl_soggetto.[Cognome/Denominazione] LIKE '%' + @Testo + '%')


The LIKE doesn't work!
I call the query with Me.griglia.DataSource = Me.TA_tbl_soggetto_ricerca.Search_Cognome(Me.txt_trova.Text.Trim)

But with LIKE '%ABC%' work!

Me.griglia.DataSource = Me.TA_tbl_soggetto_ricerca.Search_Cognome()

Someone can help me? Thanks...

View 12 Replies View Related

SET Doesn't Work

Dec 11, 2006

When I try to install the problem I get the following error.

The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, "How to: View SQL Server 2005 Setup Log Files" and "Starting SQL Server Manually."

The log tells me nothing useful. I can't start the thing manually because after clicking cancel on the error message, the installer proceeds to roll back the installation.

How do I fix this problem?








View 3 Replies View Related

Sum In Subquery Doesn't Work Well

Jun 8, 2005

This is the autogenerated code from the SelectCommand of my DataAdapter, except the red text. This DataAdapter is used to fill a DataGrid. What I want to do, is to calculate the total memory (4 slots) / PC.This code makes the sum of all memory of all PC's together.I'm not sure if the group by clause is needed here ...Me.OleDbSelectCommand1.CommandText = "SELECT PC.ID, PC.Nummer, PC.Netwerknaam, Case_Type.Type AS Case_Type, Processor_T" & _"ype.Type AS Processor_Type, Processor_Snelheid.Snelheid AS Processor_Snelheid, " & _"(SELECT SUM(Memory) FROM Memory, PC, RAM WHERE RAM.PcID = PC.ID AND RAM.GrootteID = Memory.ID)" & _"AS Memory, OS.Naam AS OS, OS_SP.Nummer AS OS_SP, Gebru" & _"iker.Naam AS Gebruiker_Naam, Status.Status, PC.Tagged FROM (Status RIGHT OUTER J" & _"OIN ((((((((PC LEFT OUTER JOIN (RAM LEFT OUTER JOIN Geheugen ON RAM.GrootteID = " & _"Geheugen.ID) ON PC.ID = RAM.PcID) LEFT OUTER JOIN Case_Type ON PC.Case_TypeID = " & _"Case_Type.ID) LEFT OUTER JOIN OS_SP ON PC.OS_SpID = OS_SP.ID) LEFT OUTER JOIN Ge" & _"bruiker ON PC.GebruikersID = Gebruiker.ID) LEFT OUTER JOIN Processor_Snelheid ON" & _" PC.Processor_SnelheidID = Processor_Snelheid.ID) LEFT OUTER JOIN Processor_Type" & _" ON PC.Processor_TypeID = Processor_Type.ID) LEFT OUTER JOIN OS ON PC.OsID = OS." & _"ID) LEFT OUTER JOIN Switchbox_Details ON PC.ID = Switchbox_Details.PcID) ON Stat" & _"us.ID = PC.StatusID) GROUP BY PC.ID, PC.Nummer, PC.Netwerknaam, Case_Type.Type, " & _"Processor_Type.Type, Processor_Snelheid.Snelheid, OS.Naam, OS_" & _"SP.Nummer, Gebruiker.Naam, Status.Status, PC.Tagged"I would like to know how to calculate the total memory for each separate PC.Hope you can help me.

View 5 Replies View Related

HELP! Sp_attach_db Doesn&#39;t Work!

Sep 20, 2000

I had a SQL Server falure. I rebiuld Master and tried to attach my database
with sp_attach_db? but get an error

Location: pageref.cpp:3931
Expression: rowLog.RowCount () == 1 || pPage->IsEmpty ()
SPID: 10
Process ID: 119

Connection Broken

View 1 Replies View Related

Attaching Db Doesn&#39;t Work

Mar 1, 2001

I try to copy a DB from one server to another. On the target server an older version of the DB has been deleted and I now try to attach the new version using "sp_attach_db DBname, Filelocation", but I always get an error "Device Activation error. The physical file name 'D:mssql7dataAgency_log.ldf' may be incorrect"
"Database 'Agency' cannot be Created"

To me it seems that the database is looking for the log files (now deleted).
I've tried forcing a new log file I created using the same locations for the mdfs. I've tried using create a new database and replace the mdf file, but nothing works.

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved