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
ADVERTISEMENT
Feb 19, 2007
Last night at home on my 64 bit Vista machine, I encountered the same error 29506 that said that the management studio express could not be installed. I looked up the error message and below is what I received. I also installed the 64 bit .net framework which installed just fine before trying to install the SSSME.
I followed the instructions below but this did not seem to make a difference. However, I did not reboot after applying new permissions. I have installed this software a few times now on 32 bit machines for both XP and RC1 Vista, and have not had a problem. Last night, I did use the 64 bit version. Also, there is no data file yet because after the install it rolls back, so I gave myself Full permissions on the SQL server directory which should include all sub directories, right? Thanks, Teri
Error 29506.
SQL Server Setup failed to modify security permissions on file Drive:Program FilesMicrosoft SQL ServerMSSQL.xMSSQLData for user SYSTEM. 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.
Note A SQL Server service pack refers to SQL Server 2005 Service Pack 1 (SP1) and later service packs.
CAUSE
This problem occurs because one or more data files exist that do not have the required permissions. By default, the Full Control permission of the Administrators group is granted to the data file when you create a database. If the permission of this group is removed from the data file, the SQL Server 2005 service pack setup will fail.
RESOLUTION
To resolve this problem, grant the Full Control permission to the Administrators group on all data files and on the Data folder. To grant the Full Control permission to the data files, follow these steps:
1.
Locate the folder that contains the data files. By default, these files are located in the following folder:
C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
2.
Right-click the data file that has no required permissions for the Administrators group, and then click Properties.
3.
If the Administrators group is not in the Group or user names list, click Add, type Administrators, and then click OK.
4.
Click Administrators in the Group or user names list, and then click to select the Allow check box for the Full Control item in the Permissions for Administrators list.Note If the files in the Data folder have an orphan owner, you have to take ownership of the files and then grant the Full Control permission to the files. We recommend that you do not change the default permissions for the data files.
View 5 Replies
View Related
Feb 12, 2013
Permissions on SQL Server Agent.
I would like to assign the permission to user ,who can edit all SQL agent job(even own by others) without assigning the sysadmin role.
View 14 Replies
View Related
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
Oct 12, 2006
Re: SQL Server 2000 Developer Edition
Error message: Setup failed to configure the server
I'm attempting to install SQL Server 2000 Developer Edition on a 2nd workstation in our area for development and practice with having this 2nd workstation as a "local" (test) SQL Server box. The install fails with the above mentioned message. (We have a database running in production on SQL Server 2000 and we need a place to simply copy the database and run tests on it)
The target PC is running WInXP Pro-SP3 and has IIS installed, along with Visual Studio 2005 & .Net framework, etc.
I downloaded it (via MSDN license) and accepted the defaults on the install.
Any feedback is appreciated.
Thanks,
RLN
View 4 Replies
View Related
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
Feb 23, 2007
Hi, I get the following error message error : "the setup failed to read IISmimemaptable the server code is 2147024893" and I cannot uninstall SQL Server 2005. Any idea this is happening. thanks!
chi
View 2 Replies
View Related
Feb 15, 2009
We have a new Win 2008 Enterprise x64 server running SQL 2008When we try to connect to the server using Windows Authentication, from a user account which is a domain administrator, we get the following message:"Token-based server access validation failed with an infrastructure error"What needs to be configured here for this to work ?
View 31 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
Feb 22, 2001
I am trying to install the SQL7 server, at the end of the installation before
rebooting the server I got the following error:
"Setup failed to configure the server. Refer to the server error logs and cnfgsvr.out for more information". I have not seen that error before. I cannot install the SQL7 because I always get the same message. Your help would be very appreciate helping me to solve this problem.
Thanks.
View 2 Replies
View Related
Jun 15, 2006
I installed sql 2005 a while back. Then I recently found out my file system was fat32 (I don't understand why the hardware people did this...) and I had to convert to NTFS. Naturally the sql service no longer worked so I uninstalled inorder to reinstall now I can't reinstall it I keep getting this message
native_error=5039, msg=[Microsoft][SQL Native Client][SQL Server]MODIFY FILE failed. Specified size is less than current size.
I'll try to post the full log in a new post.
View 11 Replies
View Related
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
View Related
May 8, 2015
No logs created, this is all I have:
Â
Unhandled Exception: System.Security.SecruityException: Request failed.
        at Microsoft.SqlServer.Chainer.Setup.Setup.DebugBreak()
        at Microsoft.SqlServer.Chainer.Setup.Setup.Main()
Then the Managed SQL Server Installer box pops up with Managed SQL Server Installer has stopped working.
View 11 Replies
View Related
Sep 21, 2005
I am working with a SQLServer installation where all public permissionshave been revoked from the system.I currently hold the securityadmin and sysadmin roles to perform mylogicall access control work (creating logins and adding users todatabases and changing group memberships.)There has been a question as to whether or not I need the sysadmin roleto do my job, so we tried an experiment in dropping the sysadmin rolefrom my id.With no public permissions, I see no user information on the server,which really limits my ability to do the job.Has anyone ever worked with a super-locked-down server without thesysadmin role for doing security admin work?What I'm looking for is hopefully SQL to perform the access privilegesneeded for the security admin role by itself.Thanks in advance!
View 2 Replies
View Related
Jun 25, 2015
I'm trying to harden our SQL Server environment to improve overall security of our systems. I would like to check what specific permissions are granted to SQL Server, SQL Server Agent and SQL Server Integration Services account. I've tried with the "sc qprivs <service_name> " command, but it returns an empty privilege list. Is there a way to retrieve the permissions using a cmd or powershell command?
View 2 Replies
View Related
Jun 6, 2007
All:
I am writing an Internet/Extranet based (ASP.Net 2.0) web application that uses SQL server 2005 as the database. I am using forms authentication on my web application. I am also storing the connection string to SQL server in my web config file. The conn string is encrypted using DPAPI with entropy. I currently have created a SQL login account on my SQL server for use by the web application. This is the user ID I am using in my conn string. The reason for this is because all persons using the application will NOT have a windows login.
Here is my question: The login I created currently has defaulted to the "dbo" role and therefore has "dbo" rights to the database. I want to setup up this login account so that all it can do is execute stored procedures. I dont want this SQL login to be able to do anything else. In my application I am using stored procedures for ALL data access functions, via a data access layer in my application. Can someone guide me step by step as to how to setup this type of access for this SQL login.
Thanks,
Blue.
View 1 Replies
View Related
May 6, 2015
i have recently ported an old asp.net web application using crystal reports 9 from windows server 2003 to windows server 2008 . the crystal reports smoothly at first but one of the reports stopped working when the admin changed his password now the report is showing error. Failed to open a rowset
View 3 Replies
View Related
Jan 20, 2008
I have finally gotten a setup to work, but I suspect there are improvements I should make to the permissions. Here's the setup:
I am accessing two databases, (aspnetdb and my own database called custom) on a local SQL 2005 server.
In SQL Server Management Studio (SMS) I created logins at the level of the SQL instance for two users ( "NT AUTHORITYNETWORK SERVICE" and "viewer"). Then I select each user, and set the properties to access the Server Roles section. There I found each was given the public server role. Now here's where I set the permission to sysadmin. This setting allows my application to work, but I'm sure there are less permissive approaches I should take. However, I just can't seem to find a simple and direct explanation of the procedure to set more appropriate permissions. The "NT AUTHORITYNETWORK SERVICE" accesses aspnetdb in order to create users and membership settings. The "viewer" login accesses the database called custom, and it reads and alters this database. The application (which is name viewer) performs these operations using a connection string like this:
Data Source=STORE;Initial Catalog=custom;Persist Security Info=True; User ID=viewer; password=xxxxx;
What is the recommended way to set the minimal permissions for these logins on these databases?
View 7 Replies
View Related
May 21, 2014
We have a SQL 2012 SSRS instance. We need to modify the permissions on one of the reporting folders. I went to the Security setting of the folder, clicked "New role assignment", then entered a group name into the box and selected desired permission ("Browser" in this case).
However this always fails with the same error: "The user or group name 'BUILTINBUILTIN' is not recognized. (rsUnknownUserName)"
I always get the same error no matter if I enter user or group, domain or local. And it always says BUILTINBUILTIN. I've tried changing the SSRS service account to a domain account (it was a local one), but that didn't work.
View 3 Replies
View Related
Oct 19, 2006
When installing SQLEXPRESS I am getting this message:
Setup failed because service MSSQL$SQLExpress is disabled for the current hardware profile. Services must be set with the current Hardware Profile logon property enabled.
Anybody knows how to fix this problem?
Eitan
View 6 Replies
View Related
Apr 9, 2004
Please suggest what I can do .
I had SQL Server 7.0 ( NT 4) installed on my desktop . I have not used it for a while and lately found that there is a problem to start service. So , I decided to reinstall it.
As a result of installation I got the message : "Setup Failed to configure the server"
The log does not tell to much besides repreating the same message , that setup failed.
What could be a problem ? How I can fix it.
Thank you.
View 5 Replies
View Related
Jul 6, 2007
I have Sql Server Express installed on Vista (service pack 2)
I have Visual Studio 2005 with an application that I'm trying to access it with within a WCF service.
The login ID of the service is added to the database.
The database has remote access turned on.
The ID is granted access to all databases within the server.
The thread is being set with WindowsProvider and the services set their thread to WindowsProvider.
The dataserver is set with using Windows Authentication for security.
When I open my connection to the database, though, it reports the typically useless message that the connection is not allowed and that the server may not allow remote connections.
How to I get past this? I've done everything right.
View 1 Replies
View Related
Nov 17, 2007
Here is my situation: I am creating a database driven ASP.Net web application that will be used over the internet. My ASP.Net application connects to my SQL server 2005 database/server by using a SQL server login. I am using the DPAPI API to encrypt my connection stings with a hidden entropy value for extra security. I am using the SQL login for obvious reasons, as my users will not have a windows login.
What I am trying to do: I want to limit this SQL login account to be able to just run/execute stored procedures and NOT access the tables or views directly. In my ASP.Net application I am using the MS applications data block, and I am using stored procedures for every single database access action. There is no inline SQL being executed from my web application.
What I have tried so far:
I created a new schema and made the above SQL login account owner of this schema. I then granted "Execute" permissions to the SQL login and DENY permissions to all other permissions.
I created an database role with "Execute" only permissions and DENY permissions to all other permissions.
What Happened: In BOTH of the above scenarios I tested a direct SQL statement against one of my tables, from my ASP.Net application and I was able retrieve data back, NOT GOOD, exactly what I am trying to STOP.
If someone could give me (Step-by-Step) guide on how to setup the situation I am looking for, I would be very grateful!
Thanks to all that help!
View 13 Replies
View Related
Jul 21, 2005
Hi
I am trying to install SQL server 7 on XP. I did not install any prerequisite such as service pack 4. During the installation process, I received a error message that says:
'Setup fail to configure the server. Refer to server errorlog and cnfigsvr.out for more information. '
In Errorlog file, the last part of it says:
.
.
.
SQL server's unicode collation is:
'English' (ID =1033) Comparison style =196609
SQL server's non-unicode sort order is:
'no case_iso'(ID=52)
SQL servers non-Unicode character setn is 'iso_1(ID=1)
Warning:
Override, autoexec procedures skipped.
Closing file c:MSSQL7DATAmodel.mdf
Closing file c:mssql7datamodelling.ldf
SQL server is terminating due to 'stop' request from service Control Manager.
In cnfgsvr.out
.
.
.
[Microsoft][ODBC SQL Server Driver][SQL Server] Successfully attached database 'Northwind'
Disconnecting from Server...
Stopping Server ......
Starting Server ......
An error occured while attempting to start the service (1460)
SQL server configuration failed.
Please, help me on how to complete the installation.
Or
Is it because of the service pack 4 that I didn't install that is causing the problem.
View 3 Replies
View Related
Jun 19, 2006
Hi,
I am having the same problem as Cherley Vasconcelos mentioned.
I checked for the 2 below mentioned Registery entries as suggested and they are present.
System:
HKEY_USERSS-1-5-18SoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders
User:
HKEY_CURRENT_USERSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell Folders
AppData entry is present under the above registry entries with the value of "%USERPROFILE%Application Data
But the problem still exists.
Please Help,
Thanks in advance,
Sonia
The log file is as follows
========================
Microsoft SQL Server 2005 Setup beginning at Mon Jun 19 10:43:41 2006
Process ID : 3476
c:c8e46d550eeabd55d7setup.exe Version: 2005.90.2047.0
Running: LoadResourcesAction at: 2006/5/19 10:43:40
Complete: LoadResourcesAction at: 2006/5/19 10:43:40, returned true
Running: ParseBootstrapOptionsAction at: 2006/5/19 10:43:40
Loaded DLL:c:c8e46d550eeabd55d7xmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2006/5/19 10:43:41, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Oct 26 16:38:20 2005
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Oct 26 16:38:20 2005
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: -2146893813
Windows Error Text: Key not valid for use in specified state.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Wed Oct 26 16:37:25 2005
Function Name: sqls::CryptSameUserSameMachine::ProtectData
Source Line Number: 50
2148073483
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "3476"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2006/5/19 10:43:41
Complete: ValidateWinNTAction at: 2006/5/19 10:43:41, returned true
Running: ValidateMinOSAction at: 2006/5/19 10:43:41
Complete: ValidateMinOSAction at: 2006/5/19 10:43:41, returned true
Running: PerformSCCAction at: 2006/5/19 10:43:41
Complete: PerformSCCAction at: 2006/5/19 10:43:41, returned true
Running: ActivateLoggingAction at: 2006/5/19 10:43:41
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00F8CFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Class not registered.
Failed to create CAB file due to datastore exception
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:20 2005
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "3476"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Oct 26 16:37:21 2005
Function Name: SetupBootstrapOptionsScope.HostSetup
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Message pump returning: 2
View 1 Replies
View Related
Nov 6, 2007
hi,
Whenever i tried to install Sql Server 2005, the installation fails giving errors for
event logs and error logs
[microsoft][SQL Native Client][SQL Server]. The server could not load DCOM...
In the log file,
Property(S): Ver.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90
Property(S): SqlTools.7354AFCB_913B_4E9F_B76C_2376101FDE0C = c:Program FilesMicrosoft SQL Server90Tools
Property(S): checksum.7354AFCB_913B_4E9F_B76C_2376101FDE0C = **********
Property(S): SqlInstance.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceRegKey.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = Microsoft SQL ServerMSSQL.1
Property(S): InstanceName.F4D8CFB2_1D8D_48C0_84BF_29B900BACB11 = SQLEXPRESS
Property(S): PackagecodeChanging = 1
Property(S): SqlInstance.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceInstall.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): SqlInstanceInstallDel.0B635761_6487_42ED_9925_C9ACF2263D3A = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall
Property(S): ProductState = -1
Property(S): TRANSFORMS = qlRun01.mst;:InstID01.mst;:InstName01.mst
Property(S): PackageCode = {A81ED606-6AF4-48DA-A5D9-1AFCC4767FEE}
Property(S): SqlInstance.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.81902028_4743_45C1_9C8C_17223CBC7128 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.D5FA3BDB_C132_4ACB_9BCE_75B981C3A65B = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): MsiLogFileLocation = C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_SHITAL-PC_SQL.log
Property(S): Shared.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlToolsBinRes.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlToolsBinRes1033.AAAE4242_504F_4BF8_8B64_2BDEA4CA2807 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlInstance.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): SqlInstanceJet.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceOther.88C26F26_166C_4CD7_8175_38297C2276D7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstance.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): SqlInstanceBinRes.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources
Property(S): SqlInstanceBinRes1033.9B89D747_AB3E_403D_94D0_4BF9BB07718F = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033
Property(S): sqlevn70.rll.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033sqlevn70.rll
Property(S): Shared.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90Shared
Property(S): Ver.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlSharedRes.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources
Property(S): SqlSharedRes1033.D0F5D514_45CE_48E8_9A6D_BAEFAA8E6A89 = c:Program FilesMicrosoft SQL Server90SharedResources1033
Property(S): SqlVerComBin.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = c:Program FilesMicrosoft SQL Server90
Property(S): InstanceName.FB04F6FB_D3EA_4FB5_B80C_362DD852A799 = SQLEXPRESS
Property(S): SqlInstance.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): InstanceName.3FC4518C_E6C5_4D52_909C_F090B324EBF7 = SQLEXPRESS
Property(S): DataInstance.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceBackup.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBackup
Property(S): DataInstanceLog.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLLOG
Property(S): DataInstanceTemplate.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.BA9A7592_6647_4283_9B99_2885BD96A224 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): AdministratorsGroupQuoted = BUILTINAdministrators
Property(S): LocalSystemAccountQuoted = NT AUTHORITYSYSTEM
Property(S): QuotedServiceGroupSQL.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = SHITAL-PCSQLServer2005MSSQLUser$SHITAL-PC$SQLEXPRESS
Property(S): AdministratorsGroup = BUILTINAdministrators
Property(S): UsersGroupQuoted = BUILTINUsers
Property(S): UsersGroup = BUILTINUsers
Property(S): InstanceRegKey.BA9A7592_6647_4283_9B99_2885BD96A224 = Microsoft SQL ServerMSSQL.1
Property(S): DataInstance.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL Server
Property(S): DataInstanceData.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData
Property(S): DataInstanceTemplate.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLTemplate Data
Property(S): DataInstanceTxt.75D79626_87FB_4E9A_B07F_87DAE18D0F36 = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): ModuleID_SYSDB2 = 75D79626_87FB_4E9A_B07F_87DAE18D0F36
Property(S): SqlInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlTarget.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstanceBin.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): Data.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL Server
Property(S): DataInstance.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): DataInstanceRepldata.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
epldata
Property(S): DataInstanceTxt.64F184C7_4276_4FEF_AAF4_800825026CED = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlVerComBin.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.779ED4A9_FDA8_4DBD_8D11_1C6CD6EE5AC7 = c:Program FilesMicrosoft SQL Server90
Property(S): TempFolder = c:UsersshitalAppDataLocalTemp
Property(S): DataInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): Data.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlTarget.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL Server
Property(S): SqlInstance.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): SqlInstanceBin.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn
Property(S): DataInstanceTxt.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQL
Property(S): WORKINGDIRECTORY.2F9C839A_286D_4B39_BD89_4DF4067604DF = c:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLREPLDATA
Property(S): InstanceRegKey.2F9C839A_286D_4B39_BD89_4DF4067604DF = Microsoft SQL ServerMSSQL.1
Property(S): SqlVerComBin.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.727FAD0C_033D_4A8B_8329_145D3EEA67B7 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90
Property(S): MSVSPrivateAssembliesEN.13676F0C_8438_4754_8C60_7ED008CBAB8D = c:Program FilesMicrosoft SQL Server90COMen
Property(S): SqlVerComBin.8E491190_3328_49D2_9FFE_2D036D847DE2 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8E491190_3328_49D2_9FFE_2D036D847DE2 = c:Program FilesMicrosoft SQL Server90
Property(S): WindowsFolder = c:Windows
Property(S): CommonFilesFolder.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon Files
Property(S): MSShared.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft Shared
Property(S): DatabaseRepl.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase Replication
Property(S): DatabaseReplRes.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources
Property(S): DatabaseReplRes1033.D9BC9C10_2DCD_44D3_AACC_9C58CAF76128 = c:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources1033
Property(S): SqlVerComBin.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.8B75390F_DF2F_4C2C_92F5_9B83F3B36340 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.889BED4C_E3F4_4943_956C_6FFD882F721F = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.889BED4C_E3F4_4943_956C_6FFD882F721F = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBin.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COM
Property(S): Ver.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90
Property(S): SqlVerComBinRes.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COMResources
Property(S): SqlVerComBinRes1033.CC4DBEA7_CD8B_4AAE_A10F_657CBA390BD6 = c:Program FilesMicrosoft SQL Server90COMResources1033
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): RSVirtualDirectoryServer = ReportServer$SQLEXPRESS
Property(S): SqlActionManaged = 3
Property(S): SqlNamedInstance = 1
Property(S): SqlStateManaged = 2
Property(S): RSVirtualDirectoryManager = Reports$SQLEXPRESS
Property(S): SOURCEDIR = c:2aae5517aa4b91d8f50a9cSetup
Property(S): SourcedirProduct = {2AFFFDD7-ED85-4A90-8C52-5DA9EBDC9B8F}
Property(S): InstallNgenTicks = 110000
Property(S): SQLBROWSERSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): SQLSCMACCOUNT = NT AUTHORITYNetworkService
Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {0D7C3EF4-D4A8-4796-9452-44FC73491B48}
Property(S): ProductToBeRegistered = 1
MSI (s) (24:44) [12:45:07:442]: Note: 1: 1708
MSI (s) (24:44) [12:45:07:442]: Product: Microsoft SQL Server 2005 Express Edition -- Installation failed.
MSI (s) (24:44) [12:45:07:443]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Express Edition. Product Version: 9.2.3042.00. Product Language: 1033. Installation success or error status: 1603.
MSI (s) (24:44) [12:45:07:457]: Cleaning up uninstalled install packages, if any exist
MSI (s) (24:44) [12:45:07:457]: MainEngineThread is returning 1603
MSI (s) (24:BC) [12:45:07:458]: Destroying RemoteAPI object.
MSI (s) (24:74) [12:45:07:459]: Custom Action Manager thread ending.
MSI (s) (24:BC) [12:45:07:460]: RESTART MANAGER: Session closed.
MSI (s) (24:BC) [12:45:07:460]: No System Restore sequence number for this installation.
=== Logging stopped: 11/6/2007 12:45:07 ===
MSI (c) (F0:98) [12:45:07:514]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (F0:98) [12:45:07:516]: MainEngineThread is returning 1603
=== Verbose logging stopped: 11/6/2007 12:45:07 ===
Can anyone provide me solution?
View 3 Replies
View Related
Nov 20, 2007
While trying to download SQL Server 2005 Express SP2 I receive the following error message: 'SQL server Setup Unexpectedly dailed. For more information review the Setup memory log file in %Program Files%Microsoft SQL Server90Setup BootstrapLOGSummary.txt'.
That log file simply contains the text:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
In the Files folder under log, a text file has been created with the following data:
Microsoft SQL Server 2005 Setup beginning at Mon Nov 19 20:30:29 2007
Process ID : 4648
c:fc359db69b5e5a0ff927be3c2esetup.exe Version: 2005.90.3042.0
Running: LoadResourcesAction at: 2007/10/19 20:30:28
Complete: LoadResourcesAction at: 2007/10/19 20:30:28, returned true
Running: ParseBootstrapOptionsAction at: 2007/10/19 20:30:28
Loaded DLL:c:fc359db69b5e5a0ff927be3c2exmlrw.dll Version:2.0.3609.0
Complete: ParseBootstrapOptionsAction at: 2007/10/19 20:30:29, returned false
Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run:
Could not parse command line due to datastore exception.
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 124
----------------------------------------------------------
writeEncryptedString() failed
Source File Name: utillibpersisthelpers.cpp
Compiler Timestamp: Wed Jun 14 16:30:14 2006
Function Name: writeEncryptedString
Source Line Number: 123
----------------------------------------------------------
Error Code: -2146893813
Windows Error Text: Key not valid for use in specified state.
Source File Name: cryptohelpercryptsameusersamemachine.cpp
Compiler Timestamp: Wed Jun 14 16:28:04 2006
Function Name: sqls::CryptSameUserSameMachine:rotectData
Source Line Number: 50
2148073483
Could not skip Component update due to datastore exception.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "4648"} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupBootstrapOptionsScope"
Running: ValidateWinNTAction at: 2007/10/19 20:30:29
Complete: ValidateWinNTAction at: 2007/10/19 20:30:29, returned true
Running: ValidateMinOSAction at: 2007/10/19 20:30:29
Complete: ValidateMinOSAction at: 2007/10/19 20:30:29, returned true
Running: PerformSCCAction at: 2007/10/19 20:30:29
Complete: PerformSCCAction at: 2007/10/19 20:30:29, returned true
Running: ActivateLoggingAction at: 2007/10/19 20:30:29
Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run:
Datastore exception while trying to write logging properties.
Source File Name: datastorecachedpropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:27:59 2006
Function Name: CachedPropertyCollection::findProperty
Source Line Number: 130
----------------------------------------------------------
Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupStateScope.primaryLogFiles
Source Line Number: 44
----------------------------------------------------------
No collector registered for scope: "SetupStateScope"
00DFCFC0Unable to proceed with setup, there was a command line parsing error. : 2
Error Code: 0x80070002 (2)
Windows Error Text: The system cannot find the file specified.
Source File Name: datastorepropertycollection.cpp
Compiler Timestamp: Wed Jun 14 16:28:01 2006
Function Name: SetupBootstrapOptionsScope.InstallMediaPath
Source Line Number: 44
Class not registered.
Can anyone give me some advice on what I need to correct in order to be able to install SQl server Express? Thanks very much in advance.
View 2 Replies
View Related
Dec 6, 2006
One of my customers is trying to setup SQL Server 2005 Express SP1 on his Windows XP Home SP2 machine.
Setup failed with the following in the Summary.txt file:
-------
Microsoft SQL Server 2005 9.00.2047.00
==============================
OS Version : Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Time : Mon Dec 04 23:59:22 2006
D86VH461 : Unknown article Result.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt.
Time : Mon Dec 04 23:59:23 2006
---------
What is this D86VH461 error code? I seached the Internet and could not find any information on it.
Thanks,
Herbert
View 7 Replies
View Related
Jun 14, 2006
I´m running WinXP SP2 with 1GB RAM, dotNET 2.0. and a previous install of SQL Server 2000. I have tried to install SQL Server 2005 Express and it fails early in the installation: "SQL Server Setup unexpectedly failed. For more information, review the Setup summary log file...". The log file is: (!)
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Wed Jun 14 10:27:51 2006
I have tried named instances, reinstall SQL Server 2000, search readme, kb, forums about the problem....nothing
Help, please.
View 10 Replies
View Related
Jun 8, 2007
Dear Helpers,
I can not setup SQL server 2005 express and the full trial version as well.
The setup progress stops at "setting file security", and nothing happens. I dont even get an error message.
This is very annoying. I have local administrator access, so it should work. Op system: Windows XP professional.
Machine: Hp Compaq dc7700p, 1 GB RAM, 80 GB HDD
Thanks for your help in advance.
View 5 Replies
View Related
Aug 30, 2006
I had a strange experience with MS SQL Server 2005 Express Edition installation, I am running a P4 3G Processor, 1 GB of RAM, Windows XP SP2, 300 GB HDD (SATA if it matters at all :) ) And using Visual Studio Pro 2005.
I have managed to install the SQL Express with no hassle at all, then had to format my HDD, and start from scratch, to make a new home for my VS 2005 Pro (The 300 GB HDD) And managed to install the SQL Express as part of the VS 2005 without any problems, after using it for 3 months now, I've started a new project in VS 2005, and tried to add a new SQL DB, but it had failed for several times.
I€™ve decided that the files got corrupted for some reason and tried to reinstall the MS SQL 2005 using the original SQL Express installation file I've used before, but without joy.
I thought that it is conflicting with some new MS Update patch and downloaded the latest SQL Express advanced installation, but that did not fix the problem either.
The message I'm getting every time I attempt the installation is" SQL Server service failed to start" with all the bla bla about the online books and whatever useless stuff to learn how to start the service manually.
I have uninstalled the whole thing, including VS 2005, .NET Framework, and any registry trace of the SQL Server installation, but again all in vain.
Finally, some smart wizard suggested in one of the threads that if your computer is not part of a domain, you should run the SQL service as a local service, using the advanced option during the first step of the setup.
And guess what! It worked!!!!
My Question is why did it work during the first two installations, without me fiddling with the advanced installation feature?
My computer was and still is, not part of any domain, my hardware did not change at all, and I had the installation failing with or without any software installed!
View 1 Replies
View Related
Sep 19, 2005
When I try to install SQL 2005 Developer September CTP on Windows XP Professional it returns an error "SQL Server Setup failed to
View 21 Replies
View Related
Apr 2, 2007
When i try to install, the filed are extracted and then i get this error message:
SQL Server Setup unexpectedly failed. For more information, review the Setup summery log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt
I open the file and this is all i get:
Microsoft SQL Server 2005 9.00.3042.00
==============================
OS Version : Microsoft Windows XP Professional
Service Pack 2 (Build 2600)
Time : Mon Apr 02 15:31:10 2007
I looked in this forum at others peoples threads and it seems as if they all have a lot larger Summary.txt file. I never had any other verson of SQL Server installed on this computer and i just uninstalled .net 2.0 framework and reinstalled it.
My computer runs Windows XP Pro with SP 2, AMD Athlon 64 Processor 3500+ 2.20 GHz, 1.00GB of RAM.
Anyone have any clue why the installation wont even start?
View 9 Replies
View Related
