sql report manager: sp2

Showing posts with label sp2. Show all posts

Sunday, March 25, 2012

Can't start 2005 Report Services on XP SP2

Hej,
I am attempting to get a test environment up and running on my XP SP2
machine but I can't start reporting services. I found the following log in
the Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles directory:
ReportingServicesService!servicecontroller!4!28-03-2006-09:27:22:: e ERROR:
Exception caught starting RPC server:
Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:
The user or group name 'ANEISHA\ASPNET' is not recognized.
at Microsoft.ReportingServices.Library.Native.NameToSid(String name)
at
Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean
firstTime)
Anybody have any clues?
Thanks in advance,
Antony C. Roberts.In desperation, I created an ASPNET user and gave it all possible roles.
That solved the problem... What is the CORRECT solution to this problem?
Thanks!
/Ant.
"Antony C. Roberts" <acr@.no.way.com> wrote in message
news:ONFgYrjUGHA.1444@.TK2MSFTNGP11.phx.gbl...
> Hej,
> I am attempting to get a test environment up and running on my XP SP2
> machine but I can't start reporting services. I found the following log in
> the Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles directory:
> ReportingServicesService!servicecontroller!4!28-03-2006-09:27:22:: e
> ERROR: Exception caught starting RPC server:
> Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException:
> The user or group name 'ANEISHA\ASPNET' is not recognized.
> at Microsoft.ReportingServices.Library.Native.NameToSid(String name)
> at
> Microsoft.ReportingServices.Library.ServiceAppDomainController.StartRPCServer(Boolean
> firstTime)
> Anybody have any clues?
> Thanks in advance,
> Antony C. Roberts.
>

Tuesday, March 20, 2012

can't see SQL server objects and counters on performance monitor

I installed SQL server 2005 on Windows XP sp2, but I can't see SQL counters
on performance monitor.
does anybody have the same situation?
ThanksHi
Do you mean that if you click on Performance object's combobox you don't see
SQL Server counters?
"chacha" <lichangang@.hotmail.com> wrote in message
news:FF74189B-EDFD-4C8A-96AF-260F11BD49CE@.microsoft.com...
>I installed SQL server 2005 on Windows XP sp2, but I can't see SQL counters
> on performance monitor.
> does anybody have the same situation?
> Thanks|||This can happen sometimes. The main reason that it causes it is that
by the time that you run perfmon with SQL Server's counters, you stop
the server's service. Few years ago I found the procedure bellow to
get the counters back (Sorry that I don't give credit, but I don't
remember where I got it from). I always start from step 4. I never
needed to run the first 3 steps.
1. You have full permission to access the local folder: C:\Program
Files\Microsoft SQL Server\MSSQL
Make sure that you can access this folder or your current account is
located in local administrator group.
2. Make sure there is no third-party application which add keys in
Register to disable the performance counters.
You can open the registry to check if there is a key named "Disable
Performance Counters" valued "1" in:
& #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services\MSSQLSERVER\Perfor
mance]
If it exists, please delete it
3. Under the register key:
& #91;HKEY_LOCAL_MACHINE\SYSTEM\CurrentCon
trolSet\Services\MSSQLSERVER\Perfor
mance]
Make sure the following keys with the value DO EXIST. If not, please
create
a new one and add the value.
# Note # : The "Last Counter", "Last Help", "First Help",
"WbemAdapFileSignature",
"WbemAdapFileTime", and "First Counter" values can vary between SQL
Server
installations.
"Library"=" C:\PROGRA~1\MICROS~3\MSSQL$~1\BINN\SQLCT
R80.DLL "
"Collect"="CollectSQLPerformanceData"
"Open"="OpenSQLPerformanceData"
"Close"="CloseSQLPerformanceData"
"Last Counter"=dword:000016ce
"Last Help"=dword:000016cf
"First Help"=dword:000015bb
"WbemAdapFileSignature" =hex:d1,70,dc,f8,a7,75,5e,e4,9e,e6,dd,91
,9e,cd,06,65
"WbemAdapFileTime"=hex:d6,34,9d,95,64,0d,c2,01
"WbemAdapFileSize"=dword:00008238
"WbemAdapStatus"=dword:00000000
"First Counter"=dword:000015ba
4. Unload the SQL Server Counters
In command line, execute "unlodctr MSSQLServer" (Without quotation, the
same as below)
5. Reloading the SQL Server Counters
(1) In command line, locate the current folder to C:\Program
Files\Microsoft SQL Server\MSSQL\BINN
(2) Execute "lodctr sqlctr.ini"
6. Stop SQL Server Services and Restart the Services
(1) In command line, execute "net stop mssqlserver"
(2) Execute "net start mssqlserver"
(Or you can perform it in Service Manager or in System Services)
7. Open Perforam Monitor to check if the counters appear
(1) In command line, execute "perfmon"
(2) Add and check if the counter appear
Adi
chacha wrote:
> I installed SQL server 2005 on Windows XP sp2, but I can't see SQL counter
s
> on performance monitor.
> does anybody have the same situation?
> Thanks

can't see SQL server objects and counters on performance monitor

I installed SQL server 2005 on windows Xp sp2, but I can't see SQL counters
on performance monitor.
does anybody have the same situation?
ThanksHi
Do you mean that if you click on Performance object's combobox you don't see
SQL Server counters?
"chacha" <lichangang@.hotmail.com> wrote in message
news:FF74189B-EDFD-4C8A-96AF-260F11BD49CE@.microsoft.com...
>I installed SQL server 2005 on windows Xp sp2, but I can't see SQL counters
> on performance monitor.
> does anybody have the same situation?
> Thanks|||This can happen sometimes. The main reason that it causes it is that
by the time that you run perfmon with SQL Server's counters, you stop
the server's service. Few years ago I found the procedure bellow to
get the counters back (Sorry that I don't give credit, but I don't
remember where I got it from). I always start from step 4. I never
needed to run the first 3 steps.
1. You have full permission to access the local folder: C:\Program
Files\Microsoft SQL Server\MSSQL
Make sure that you can access this folder or your current account is
located in local administrator group.
2. Make sure there is no third-party application which add keys in
Register to disable the performance counters.
You can open the registry to check if there is a key named "Disable
Performance Counters" valued "1" in:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\Performance]
If it exists, please delete it
3. Under the register key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSSQLSERVER\Performance]
Make sure the following keys with the value DO EXIST. If not, please
create
a new one and add the value.
# Note # : The "Last Counter", "Last Help", "First Help",
"WbemAdapFileSignature",
"WbemAdapFileTime", and "First Counter" values can vary between SQL
Server
installations.
"Library"=" C:\PROGRA~1\MICROS~3\MSSQL$~1\BINN\SQLCTR80.DLL "
"Collect"="CollectSQLPerformanceData"
"Open"="OpenSQLPerformanceData"
"Close"="CloseSQLPerformanceData"
"Last Counter"=dword:000016ce
"Last Help"=dword:000016cf
"First Help"=dword:000015bb
"WbemAdapFileSignature"=hex:d1,70,dc,f8,a7,75,5e,e4,9e,e6,dd,91,9e,cd,06,65
"WbemAdapFileTime"=hex:d6,34,9d,95,64,0d,c2,01
"WbemAdapFileSize"=dword:00008238
"WbemAdapStatus"=dword:00000000
"First Counter"=dword:000015ba
4. Unload the SQL Server Counters
In command line, execute "unlodctr MSSQLServer" (Without quotation, the
same as below)
5. Reloading the SQL Server Counters
(1) In command line, locate the current folder to C:\Program
Files\Microsoft SQL Server\MSSQL\BINN
(2) Execute "lodctr sqlctr.ini"
6. Stop SQL Server Services and Restart the Services
(1) In command line, execute "net stop mssqlserver"
(2) Execute "net start mssqlserver"
(Or you can perform it in Service Manager or in System Services)
7. Open Perforam Monitor to check if the counters appear
(1) In command line, execute "perfmon"
(2) Add and check if the counter appear
Adi
chacha wrote:
> I installed SQL server 2005 on windows Xp sp2, but I can't see SQL counters
> on performance monitor.
> does anybody have the same situation?
> Thankssql

cant see server

Hi,
Twice this has happened....
WinXP Pro SP2. SQL server 2000
When I have used a third party app (.net tool) to select my sql box from the
"available list" it pauses for a while and the drop down list is empty.
I manually type the name of the server in and it goes ahead just fine.
The same happened when I just tried to create a DSN via the MS Access upsize
wizard.

Why can't 3rd parties see the server instance?

JayIf your are using TCP. Sounds like WINS is working but something is
blocking UDP port 1434.

Could be a router, firewall, XP SP2's built in firewall blocks this...

"Jay" <nospam@.*here.com> wrote in message
news:WqUsd.22789$9A.392629@.news.xtra.co.nz...
> Hi,
> Twice this has happened....
> WinXP Pro SP2. SQL server 2000
> When I have used a third party app (.net tool) to select my sql box from
> the "available list" it pauses for a while and the drop down list is
> empty.
> I manually type the name of the server in and it goes ahead just fine.
> The same happened when I just tried to create a DSN via the MS Access
> upsize wizard.
> Why can't 3rd parties see the server instance?
> Jay|||Hi Danny,
More info...

Looked at network config and it says that named pipes and tcp are the
enabled protocols.
I don't use the XP SP2 firewall. I use Kerio.
I've checked the kerio app settings and SQL is set to "ask" as opposed to
permit or deny (so I'd expect a Kerio dialogue if anything was trying?)
The server installation (in EM) is listed simply as (local).

New DSN and the server drop down box is empty but, get this!, if I type in a
period "." and click next it goes ahead no problem and the connection tests
ok!

Jay

"Danny" <istdrs@.flash.net> wrote in message
news:mzYsd.29107$Rf1.16651@.newssvr19.news.prodigy. com...
> If your are using TCP. Sounds like WINS is working but something is
> blocking UDP port 1434.
> Could be a router, firewall, XP SP2's built in firewall blocks this...
>
> "Jay" <nospam@.*here.com> wrote in message
> news:WqUsd.22789$9A.392629@.news.xtra.co.nz...
>> Hi,
>> Twice this has happened....
>> WinXP Pro SP2. SQL server 2000
>> When I have used a third party app (.net tool) to select my sql box from
>> the "available list" it pauses for a while and the drop down list is
>> empty.
>> I manually type the name of the server in and it goes ahead just fine.
>> The same happened when I just tried to create a DSN via the MS Access
>> upsize wizard.
>>
>> Why can't 3rd parties see the server instance?
>>
>> Jay
>>

Sunday, March 11, 2012

Can't run rskeymgmt after SP2

After installing SP2 for SQL 2005 I can no longer run rskeymgmt. I was
trying to backup the encryption key
(rskeymgmt -e -fc:\rsdbkey.txt -ppassword) but I get the following error:
The Report Server Windows service in not responding to RPC requests. The
service may not be running.
I have checked and the service is running. Are there any issues with SP2?On Apr 5, 1:21 pm, "Tim Kelley" <tkel...@.company.com> wrote:
> After installing SP2 for SQL 2005 I can no longer run rskeymgmt. I was
> trying to backup the encryption key
> (rskeymgmt -e -fc:\rsdbkey.txt -ppassword) but I get the following error:
> The Report Server Windows service in not responding to RPC requests. The
> service may not be running.
> I have checked and the service is running. Are there any issues with SP2?
This article might be helpful:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1323751&SiteID=1
Regards,
Enrique Martinez
Sr. Software Consultant

Thursday, March 8, 2012

CAN'T remove "Execute job" from alert in SS 2005?

This is kind of strange. On a SQL 2005 SP2 box, I've set up a few alerts to
monitor tran log growth. If they reach the threshold the alerts will fire
and send emails and kick off a tran log dump job. Now I want to remove the
job by unchecking the "Execute job" box from the "Response" node. after
clicking OK and going back to revisit it, the job is still checked. I've
tested this on a few other SQL instances - all are the same. From my
machine, I tested on a SQL 2000 server and it works as expected.
The alert is scripted below. I have also tried to change @.job_id to null in
a hope that the sproc will make it unchecked. But still the old job exists
in the alert.
EXEC msdb.dbo.sp_add_alert @.name=N'test',
@.message_id=0,
@.severity=0,
@.enabled=1,
@.delay_between_responses=0,
@.include_event_description_in=1,
@.category_name=N'[Uncategorized]',
@.performance_condition=N'SQLServer:Databases|Log File(s) Used Size
(KB)|tempdb|>|100000',
@.job_id=N'4d9d9fde-0fed-4d79-b894-0a04ae0d2b85'
I tend to believe this is a SQL 2005 bug. Has anyone else seen or can anyone
duplicate the same problem?
RickIt is not strange if it's a bug. :-) confirmed for ss2005. someone already
reported in April 2007.
"YPD" <y.ding@.neu.edu> wrote in message
news:C272B7CA-23BD-497A-AACC-C84E60A5030E@.microsoft.com...
> This is kind of strange. On a SQL 2005 SP2 box, I've set up a few alerts
> to monitor tran log growth. If they reach the threshold the alerts will
> fire and send emails and kick off a tran log dump job. Now I want to
> remove the job by unchecking the "Execute job" box from the "Response"
> node. after clicking OK and going back to revisit it, the job is still
> checked. I've tested this on a few other SQL instances - all are the same.
> From my machine, I tested on a SQL 2000 server and it works as expected.
> The alert is scripted below. I have also tried to change @.job_id to null
> in a hope that the sproc will make it unchecked. But still the old job
> exists in the alert.
> EXEC msdb.dbo.sp_add_alert @.name=N'test',
> @.message_id=0,
> @.severity=0,
> @.enabled=1,
> @.delay_between_responses=0,
> @.include_event_description_in=1,
> @.category_name=N'[Uncategorized]',
> @.performance_condition=N'SQLServer:Databases|Log File(s) Used Size
> (KB)|tempdb|>|100000',
> @.job_id=N'4d9d9fde-0fed-4d79-b894-0a04ae0d2b85'
> I tend to believe this is a SQL 2005 bug. Has anyone else seen or can
> anyone duplicate the same problem?
>
> Rick

Thursday, February 16, 2012

Can't install sqlncli.msi

When trying to install sqlncli.msi on Windows XP SP2 I get the following
error
"The system administrator has set policies to prevent this installation"
Given that I am the system administrator ...
What do I need to do to resolve this ?
What policies have been set ?
Can you execute any msi? Or is it just with this windows
intaller package?
Try checking the local policies on the PC for windows
installer using the group policy editor snap in.
From the run command, run gpedit.msc
Go to Computer Configuration, then to Administrative
templates, then to Windows Components, then to Windows
Installer.
You could also be hitting this:
http://support.microsoft.com/kb/322963
Did you check the windows installer service on the PC
itself? Is it manual or running?
Did you also try updating your windows installer?
http://support.microsoft.com/kb/893803
-Sue
On Tue, 19 Jun 2007 12:41:14 -0600, "Michael Tissington"
<mtissington@.newsgroups.nospam> wrote:

>When trying to install sqlncli.msi on Windows XP SP2 I get the following
>error
>"The system administrator has set policies to prevent this installation"
>Given that I am the system administrator ...
>What do I need to do to resolve this ?
>What policies have been set ?

Can't install sqlncli.msi

When trying to install sqlncli.msi on Windows XP SP2 I get the following
error
"The system administrator has set policies to prevent this installation"
Given that I am the system administrator ...
What do I need to do to resolve this ?
What policies have been set ?Can you execute any msi? Or is it just with this windows
intaller package?
Try checking the local policies on the PC for windows
installer using the group policy editor snap in.
From the run command, run gpedit.msc
Go to Computer Configuration, then to Administrative
templates, then to Windows Components, then to Windows
Installer.
You could also be hitting this:
http://support.microsoft.com/kb/322963
Did you check the windows installer service on the PC
itself? Is it manual or running?
Did you also try updating your windows installer?
http://support.microsoft.com/kb/893803
-Sue
On Tue, 19 Jun 2007 12:41:14 -0600, "Michael Tissington"
<mtissington@.newsgroups.nospam> wrote:

>When trying to install sqlncli.msi on Windows XP SP2 I get the following
>error
>"The system administrator has set policies to prevent this installation"
>Given that I am the system administrator ...
>What do I need to do to resolve this ?
>What policies have been set ?

Can't install sqlncli.msi

Cant install sql server express...check out these errors

I can't get the download to work...i've tried regular sql server express 2005, the express for sp2 and the express with advanced services.  I keep getting this message after the native client and support files are installed.."This application has failed to start because XOLEHLP.dll was not found. Re-installing the application may fix this problem."Then right after that message is says... "Failed to load SQLSpars.dll"Follow up: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=437605&SiteID=1

Jens K. Suessmeyer.

http://www.sqlserver2005.de

Can't install SQL Server 2005 SP2

Hi, can't install SP2 for SQL 2005. Here is copy of Hotfix.

05/18/2007 21:44:35.339 ================================================================================
05/18/2007 21:44:35.339 Hotfix package launched
05/18/2007 21:44:35.370 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:35.370 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:35.370 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:35.370 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:35.370 Local Computer:
05/18/2007 21:44:35.370 Target Details: DMZ-SQL03
05/18/2007 21:44:35.370 commonfilesdir = C:\Program Files (x86)\Common Files
05/18/2007 21:44:35.370 lcidsupportdir = d:\78475438a18ffeb151\1033
05/18/2007 21:44:35.370 programfilesdir = C:\Program Files (x86)
05/18/2007 21:44:35.370 programfilesdir_wow = C:\Program Files (x86)
05/18/2007 21:44:35.370 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:35.370 supportdirlocal = d:\78475438a18ffeb151
05/18/2007 21:44:35.370 windir = C:\WINDOWS
05/18/2007 21:44:35.370 winsysdir = C:\WINDOWS\system32
05/18/2007 21:44:35.370 winsysdir_wow = C:\WINDOWS\SysWOW64
05/18/2007 21:44:35.370
05/18/2007 21:44:35.386 Enumerating applicable products for this patch
05/18/2007 21:44:35.386 Found Redist 2005 product definition
05/18/2007 21:44:35.402 Found Redist 2005 product definition
05/18/2007 21:44:35.402 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:35.402 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:35.402 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:35.402 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:35.495 Found Redist 2005 product definition
05/18/2007 21:44:35.495 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:35.495 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:35.495 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:35.495 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:35.527 Found SQL 2005 product definition
05/18/2007 21:44:36.152 Enumeration: Determining QFE level for product instance MSSQLSERVER
05/18/2007 21:44:36.152 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
05/18/2007 21:44:36.152 Enumeration: Found following QFE level for product instance MSSQLSERVER: 2047
05/18/2007 21:44:36.152 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
05/18/2007 21:44:36.152 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\SQLServr.exe
05/18/2007 21:44:36.152 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
05/18/2007 21:44:36.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:36.152 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:36.152 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:36.152 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:36.152 Product discovery completed during the install process for MSSQLSERVER
05/18/2007 21:44:36.152 SP Level check completed during the install process for MSSQLSERVER
05/18/2007 21:44:36.152 Product language check completed during the install process for MSSQLSERVER
05/18/2007 21:44:36.152 Product version check completed during the install process for MSSQLSERVER
05/18/2007 21:44:36.152 Command-line instance name check completed during the install process
05/18/2007 21:44:36.152 SKU check completed during the install process for MSSQLSERVER
05/18/2007 21:44:36.152 Baseline build check completed during the installation process for MSSQLSERVER
05/18/2007 21:44:36.152 Baseline build check completed during the install process
05/18/2007 21:44:36.152 Found OLAP Server 2005 product definition
05/18/2007 21:44:36.730 Command-line instance name check completed during the install process
05/18/2007 21:44:36.730 Baseline build check completed during the install process
05/18/2007 21:44:36.730 Found Notification Services 2005 product definition
05/18/2007 21:44:37.324 Enumeration: Determining QFE level for product instance
05/18/2007 21:44:37.339 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
05/18/2007 21:44:37.339 Enumeration: Found following QFE level for product instance : 3054
05/18/2007 21:44:37.339 Enumeration: Determining GDR branching Hotfix for product instance
05/18/2007 21:44:37.339 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
05/18/2007 21:44:37.339 Enumeration: Found following GDR branch hotfix for product instance : 3159
05/18/2007 21:44:37.339 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:37.339 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:37.339 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:37.339 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:37.339 Product discovery completed during the install process for NS
05/18/2007 21:44:37.339 SP Level check completed during the install process for NS
05/18/2007 21:44:37.339 Product language check completed during the install process for NS
05/18/2007 21:44:37.355 The product instance NS been patched with more recent updates.
05/18/2007 21:44:37.355 Baseline build check completed during the install process
05/18/2007 21:44:37.355 Found Report Server 2005 product definition
05/18/2007 21:44:37.949 Command-line instance name check completed during the install process
05/18/2007 21:44:37.949 Baseline build check completed during the install process
05/18/2007 21:44:37.949 Found DTS 2005 product definition
05/18/2007 21:44:38.542 Enumeration: Determining QFE level for product instance
05/18/2007 21:44:38.542 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\DTS\\Binn\msdtssrvr.exe
05/18/2007 21:44:38.542 Enumeration: Found following QFE level for product instance : 3054
05/18/2007 21:44:38.542 Enumeration: Determining GDR branching Hotfix for product instance
05/18/2007 21:44:38.542 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files (x86)\Microsoft SQL Server\90\DTS\\Binn\msdtssrvr.exe
05/18/2007 21:44:38.542 Enumeration: Found following GDR branch hotfix for product instance : 3159
05/18/2007 21:44:38.542 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:38.542 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:38.542 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:38.542 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:38.542 Product discovery completed during the install process for Integration Services
05/18/2007 21:44:38.558 SP Level check completed during the install process for Integration Services
05/18/2007 21:44:38.558 Product language check completed during the install process for Integration Services
05/18/2007 21:44:38.558 The product instance Integration Services been patched with more recent updates.
05/18/2007 21:44:38.558 Baseline build check completed during the install process
05/18/2007 21:44:38.558 Found SQL 2005 Tools product definition
05/18/2007 21:44:39.167 Enumeration: Determining GDR branching Hotfix for product instance
05/18/2007 21:44:39.167 Enumeration: Found following GDR branch hotfix for product instance : 3159
05/18/2007 21:44:39.167 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.167 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:39.167 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.167 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:39.167 Product discovery completed during the install process for SQL Tools
05/18/2007 21:44:39.167 SP Level check completed during the install process for SQL Tools
05/18/2007 21:44:39.167 Product language check completed during the install process for SQL Tools
05/18/2007 21:44:39.167 The product instance SQL Tools been patched with more recent updates.
05/18/2007 21:44:39.167 SKU check completed during the install process for SQL Tools
05/18/2007 21:44:39.167 Baseline build check completed during the install process
05/18/2007 21:44:39.167 Found Redist 2005 product definition
05/18/2007 21:44:39.167 Found Redist 2005 product definition
05/18/2007 21:44:39.183 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.183 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:39.183 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.183 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:39.214 Found Redist 2005 product definition
05/18/2007 21:44:39.230 Found Redist 2005 product definition
05/18/2007 21:44:39.230 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.230 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:39.230 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.230 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:39.277 Found Redist 2005 product definition
05/18/2007 21:44:39.277 Found Redist 2005 product definition
05/18/2007 21:44:39.277 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.277 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:39.277 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.277 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:39.339 Found Redist 2005 product definition
05/18/2007 21:44:39.339 Found Redist 2005 product definition
05/18/2007 21:44:39.339 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.339 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files (x86)\Common Files
05/18/2007 21:44:39.339 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
05/18/2007 21:44:39.339 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files (x86)
05/18/2007 21:44:39.449 Product Enumeration Results:
05/18/2007 21:44:39.449 INF File Name: d:\78475438a18ffeb151\HotFixSqlncli.inf
05/18/2007 21:44:39.449 baselinebuild = 1399
05/18/2007 21:44:39.449 build = 3042
05/18/2007 21:44:39.449 description = SQL Server Native Client
05/18/2007 21:44:39.449 details = Service Pack for Microsoft SQL Server Native Client.
05/18/2007 21:44:39.449 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.449 kbarticle = KB921896
05/18/2007 21:44:39.449 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.449 lcid = 1033
05/18/2007 21:44:39.449 legalproductname = Microsoft SQL Native Client
05/18/2007 21:44:39.449 machinetype = x86
05/18/2007 21:44:39.449 package = HotFixSqlncli
05/18/2007 21:44:39.449 packagetype = Hotfix
05/18/2007 21:44:39.449 productname = Redist9
05/18/2007 21:44:39.449 recommendinstall = 1
05/18/2007 21:44:39.449 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.449 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.449 splevel = 2
05/18/2007 21:44:39.449 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.449 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.449 upgradecode = {A6B19337-7392-4765-8675-5C25B758BA37}
05/18/2007 21:44:39.449 version = 9
05/18/2007 21:44:39.449
05/18/2007 21:44:39.449 File Group Details: MSI
05/18/2007 21:44:39.449 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.449 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.449 File Details: sqlncli.msi
05/18/2007 21:44:39.449
05/18/2007 21:44:39.449 Product Enumeration Results:
05/18/2007 21:44:39.449 INF File Name: d:\78475438a18ffeb151\HotFixSqlncli_x64.inf
05/18/2007 21:44:39.449 baselinebuild = 1399
05/18/2007 21:44:39.449 build = 3042
05/18/2007 21:44:39.449 description = SQL Server Native Client
05/18/2007 21:44:39.449 details = Service Pack for Microsoft SQL Server Native Client.
05/18/2007 21:44:39.449 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.449 kbarticle = KB921896
05/18/2007 21:44:39.449 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.449 lcid = 1033
05/18/2007 21:44:39.449 legalproductname = Microsoft SQL Native Client (64-bit)
05/18/2007 21:44:39.449 machinetype = x64
05/18/2007 21:44:39.449 package = HotFixSqlncli_x64
05/18/2007 21:44:39.449 packagetype = Hotfix
05/18/2007 21:44:39.449 productcode = {6E740973-8E71-42F9-A910-C18452E60450}
05/18/2007 21:44:39.449 productname = Redist9
05/18/2007 21:44:39.449 recommendinstall = 1
05/18/2007 21:44:39.449 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.449 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.449 splevel = 2
05/18/2007 21:44:39.449 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.449 upgradecode = {6EC3319D-84BE-4C32-AA91-7D6057CF05A5}
05/18/2007 21:44:39.449 version = 9
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 File Group Details: MSI
05/18/2007 21:44:39.464 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.464 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.464 File Details: sqlncli_x64.msi
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 Instance Details: SQL Server Native Client
05/18/2007 21:44:39.464 fullversion = 9.00.3042.00
05/18/2007 21:44:39.464 lcid = 1033
05/18/2007 21:44:39.464 productcode = {6E740973-8E71-42F9-A910-C18452E60450}
05/18/2007 21:44:39.464 qfelevel = 3042
05/18/2007 21:44:39.464 sp = -1
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 Product Enumeration Results:
05/18/2007 21:44:39.464 INF File Name: d:\78475438a18ffeb151\HotFixSqlSupport.inf
05/18/2007 21:44:39.464 alwaysinstall = 1
05/18/2007 21:44:39.464 baselinebuild = 1399
05/18/2007 21:44:39.464 build = 3042
05/18/2007 21:44:39.464 description = Setup Support Files
05/18/2007 21:44:39.464 details = Service Pack for the SQL Server support files.
05/18/2007 21:44:39.464 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.464 kbarticle = KB921896
05/18/2007 21:44:39.464 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.464 keyqualifier = 1
05/18/2007 21:44:39.464 lcid = 1033
05/18/2007 21:44:39.464 legalproductname = SQL Server 2005 Setup Support Files
05/18/2007 21:44:39.464 machinetype = x86
05/18/2007 21:44:39.464 package = HotFixSqlSupport
05/18/2007 21:44:39.464 packagetype = Hotfix
05/18/2007 21:44:39.464 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
05/18/2007 21:44:39.464 productname = Redist9
05/18/2007 21:44:39.464 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.464 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.464 splevel = 2
05/18/2007 21:44:39.464 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.464 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.464 upgradecode = {3A91FA19-A197-467C-850F-0AFE90899371}
05/18/2007 21:44:39.464 version = 9
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 File Group Details: MSI
05/18/2007 21:44:39.464 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\<MachineType>\<LCID>
05/18/2007 21:44:39.464 parameters = REINSTALL=ALL
05/18/2007 21:44:39.464 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.464 File Details: SqlSupport.msi
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 Instance Details: Setup Support Files
05/18/2007 21:44:39.464 fullversion = 9.2.3042
05/18/2007 21:44:39.464 lcid = 1033
05/18/2007 21:44:39.464 productcode = {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
05/18/2007 21:44:39.464 qfelevel = 3042
05/18/2007 21:44:39.464 sp = -1
05/18/2007 21:44:39.464 wow64 = true
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 Product Enumeration Results:
05/18/2007 21:44:39.464 INF File Name: d:\78475438a18ffeb151\HotFixSQL.inf
05/18/2007 21:44:39.464 baselinebuild = 1399
05/18/2007 21:44:39.464 baselinebuildmax = 3042
05/18/2007 21:44:39.464 build = 3042
05/18/2007 21:44:39.464 description = Database Services
05/18/2007 21:44:39.464 details = Service Pack for the SQL Server database engine, and the tools for managing relational and XML data, Replication, and Full-Text Search.
05/18/2007 21:44:39.464 installer = Hotfix
05/18/2007 21:44:39.464 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.464 kbarticle = KB921896
05/18/2007 21:44:39.464 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.464 lcid = 1033
05/18/2007 21:44:39.464 legalproductname = SQL Server Database Services 2005
05/18/2007 21:44:39.464 machinetype = x86
05/18/2007 21:44:39.464 package = HotFixSQL
05/18/2007 21:44:39.464 packagetype = Hotfix
05/18/2007 21:44:39.464 productname = SQL9
05/18/2007 21:44:39.464 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.464 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.464 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/18/2007 21:44:39.464 splevel = 2
05/18/2007 21:44:39.464 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.464 sqlutility = sqlcmd.exe
05/18/2007 21:44:39.464 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.464 validateauthentication = true
05/18/2007 21:44:39.464 version = 9
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 File Group Details: MSP
05/18/2007 21:44:39.464 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/18/2007 21:44:39.464 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.464 File Details: sqlrun_sql.msp
05/18/2007 21:44:39.464
05/18/2007 21:44:39.464 Instance Details: MSSQLSERVER
05/18/2007 21:44:39.480 agentservicename = SQLSERVERAGENT
05/18/2007 21:44:39.480 associatedhotfixbuild = 0
05/18/2007 21:44:39.480 clustername =
05/18/2007 21:44:39.480 default = TRUE
05/18/2007 21:44:39.480 ftsservicename = MSFTESQL
05/18/2007 21:44:39.480 fullversion = 2005.090.2047.00
05/18/2007 21:44:39.480 hiveregpath = Software\Wow6432Node\Microsoft\Microsoft SQL Server\MSSQL.1
05/18/2007 21:44:39.480 id = MSSQL.1
05/18/2007 21:44:39.480 installsqldatadir = C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL
05/18/2007 21:44:39.480 installsqldir = C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL
05/18/2007 21:44:39.480 lcid = 1033
05/18/2007 21:44:39.480 name = MSSQLSERVER
05/18/2007 21:44:39.480 productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
05/18/2007 21:44:39.480 qfelevel = 2047
05/18/2007 21:44:39.480 servicename = MSSQLServer
05/18/2007 21:44:39.480 sku = STANDARD
05/18/2007 21:44:39.480 sp = 1
05/18/2007 21:44:39.480 type = SQL Server Standalone Product
05/18/2007 21:44:39.480 vermajbld = 2047
05/18/2007 21:44:39.480 version = 9
05/18/2007 21:44:39.480 wow64 = true
05/18/2007 21:44:39.480
05/18/2007 21:44:39.480 Product Enumeration Results:
05/18/2007 21:44:39.480 INF File Name: d:\78475438a18ffeb151\HotFixAS.inf
05/18/2007 21:44:39.480 baselinebuild = 1399
05/18/2007 21:44:39.480 baselinebuildmax = 3042
05/18/2007 21:44:39.480 build = 3042
05/18/2007 21:44:39.480 description = Analysis Services
05/18/2007 21:44:39.480 details = Service Pack for Analysis Services, and the tools used to support online analytical processing (OLAP) and data mining.
05/18/2007 21:44:39.480 installer = Hotfix
05/18/2007 21:44:39.480 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.480 kbarticle = KB921896
05/18/2007 21:44:39.480 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.480 lcid = 1033
05/18/2007 21:44:39.480 legalproductname = SQL Server Analysis Services 2005
05/18/2007 21:44:39.480 machinetype = x86
05/18/2007 21:44:39.480 package = HotFixAS
05/18/2007 21:44:39.480 packagetype = Hotfix
05/18/2007 21:44:39.480 productname = OLAP9
05/18/2007 21:44:39.480 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.480 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.480 splevel = 2
05/18/2007 21:44:39.480 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.480 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.480 version = 9
05/18/2007 21:44:39.480
05/18/2007 21:44:39.480 File Group Details: MSP
05/18/2007 21:44:39.480 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/18/2007 21:44:39.480 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.480 File Details: sqlrun_as.msp
05/18/2007 21:44:39.480
05/18/2007 21:44:39.480 Product Enumeration Results:
05/18/2007 21:44:39.480 INF File Name: d:\78475438a18ffeb151\HotFixNS.inf
05/18/2007 21:44:39.480 baselinebuild = 1399
05/18/2007 21:44:39.480 baselinebuildmax = 3042
05/18/2007 21:44:39.480 build = 3042
05/18/2007 21:44:39.480 description = Notification Services
05/18/2007 21:44:39.480 details = Service Pack for Notification Services, a platform for developing and deploying applications that send personalized, timely notifications to a variety of devices or applications.
05/18/2007 21:44:39.480 installer = Hotfix
05/18/2007 21:44:39.480 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.480 kbarticle = KB921896
05/18/2007 21:44:39.480 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.480 lcid = 1033
05/18/2007 21:44:39.480 legalproductname = SQL Server Notification Services 2005 instances
05/18/2007 21:44:39.480 machinetype = x86
05/18/2007 21:44:39.480 package = HotFixNS
05/18/2007 21:44:39.480 packagetype = Hotfix
05/18/2007 21:44:39.480 productname = NS9
05/18/2007 21:44:39.480 recommendinstall = 1
05/18/2007 21:44:39.480 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.480 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.480 splevel = 2
05/18/2007 21:44:39.480 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.480 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.480 version = 9
05/18/2007 21:44:39.480
05/18/2007 21:44:39.480 File Group Details: MSP
05/18/2007 21:44:39.480 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/18/2007 21:44:39.480 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.480 File Details: sqlrun_ns.msp
05/18/2007 21:44:39.480
05/18/2007 21:44:39.480 Instance Details: NS
05/18/2007 21:44:39.480 associatedhotfixbuild = 3159
05/18/2007 21:44:39.480 clustername =
05/18/2007 21:44:39.480 details = The product instance NS been patched with more recent updates.
05/18/2007 21:44:39.480 fullversion = 9.00.3054.00
05/18/2007 21:44:39.495 hiveregpath = Software\Wow6432Node\Microsoft\Microsoft SQL Server\90\NS
05/18/2007 21:44:39.495 id =
05/18/2007 21:44:39.495 installsqldatadir =
05/18/2007 21:44:39.495 installsqldir = C:\Program Files (x86)\Microsoft SQL Server\90\NotificationServices\9.0.242\
05/18/2007 21:44:39.495 lcid = 1033
05/18/2007 21:44:39.495 name =
05/18/2007 21:44:39.495 productcode = {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}
05/18/2007 21:44:39.495 qfelevel = 3054
05/18/2007 21:44:39.495 sku = STANDARD
05/18/2007 21:44:39.495 sp = 2
05/18/2007 21:44:39.495 type = Tools Only
05/18/2007 21:44:39.495 vermajbld = 3042
05/18/2007 21:44:39.495 version = 9
05/18/2007 21:44:39.495 wow64 = true
05/18/2007 21:44:39.495
05/18/2007 21:44:39.495 Product Enumeration Results:
05/18/2007 21:44:39.495 INF File Name: d:\78475438a18ffeb151\HotFixRS.inf
05/18/2007 21:44:39.495 baselinebuild = 1399
05/18/2007 21:44:39.495 baselinebuildmax = 3042
05/18/2007 21:44:39.495 build = 3042
05/18/2007 21:44:39.495 description = Reporting Services
05/18/2007 21:44:39.495 details = Service Pack for the Report Server and Report Builder, which manages, executes, renders, and distributes reports.
05/18/2007 21:44:39.495 installer = Hotfix
05/18/2007 21:44:39.495 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.495 kbarticle = KB921896
05/18/2007 21:44:39.495 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.495 lcid = 1033
05/18/2007 21:44:39.495 legalproductname = SQL Server Reporting Services 2005
05/18/2007 21:44:39.495 machinetype = x86
05/18/2007 21:44:39.495 package = HotFixRS
05/18/2007 21:44:39.495 packagetype = Hotfix
05/18/2007 21:44:39.495 productname = RS9
05/18/2007 21:44:39.495 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.495 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.495 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/18/2007 21:44:39.495 splevel = 2
05/18/2007 21:44:39.495 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.495 sqlutility = sqlcmd.exe
05/18/2007 21:44:39.495 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.495 validateauthentication = 1
05/18/2007 21:44:39.495 version = 9
05/18/2007 21:44:39.495
05/18/2007 21:44:39.495 File Group Details: MSP
05/18/2007 21:44:39.495 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/18/2007 21:44:39.495 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.495 File Details: sqlrun_rs.msp
05/18/2007 21:44:39.495
05/18/2007 21:44:39.495 Product Enumeration Results:
05/18/2007 21:44:39.495 INF File Name: d:\78475438a18ffeb151\HotFixDTS.inf
05/18/2007 21:44:39.495 baselinebuild = 1399
05/18/2007 21:44:39.495 baselinebuildmax = 3042
05/18/2007 21:44:39.495 build = 3042
05/18/2007 21:44:39.495 description = Integration Services
05/18/2007 21:44:39.495 details = Service Pack for Integration Services, a set of tools and programmable objects used to create and manage packages that extract, transform, and load data, as well as perform tasks.
05/18/2007 21:44:39.495 installer = Hotfix
05/18/2007 21:44:39.495 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.495 kbarticle = KB921896
05/18/2007 21:44:39.495 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.495 lcid = 1033
05/18/2007 21:44:39.495 legalproductname = SQL Server Integration Services 2005
05/18/2007 21:44:39.495 machinetype = x86
05/18/2007 21:44:39.495 package = HotFixDTS
05/18/2007 21:44:39.495 packagetype = Hotfix
05/18/2007 21:44:39.495 productname = DTS9
05/18/2007 21:44:39.495 recommendinstall = 1
05/18/2007 21:44:39.495 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.495 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.495 splevel = 2
05/18/2007 21:44:39.495 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.495 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.495 version = 9
05/18/2007 21:44:39.495
05/18/2007 21:44:39.495 File Group Details: MSP
05/18/2007 21:44:39.495 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/18/2007 21:44:39.495 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.495 File Details: sqlrun_dts.msp
05/18/2007 21:44:39.495
05/18/2007 21:44:39.495 Instance Details: Integration Services
05/18/2007 21:44:39.495 associatedhotfixbuild = 3159
05/18/2007 21:44:39.495 clustername =
05/18/2007 21:44:39.495 details = The product instance Integration Services been patched with more recent updates.
05/18/2007 21:44:39.495 dtsservicename = MsDtsServer
05/18/2007 21:44:39.495 fullversion = 9.00.3054.00
05/18/2007 21:44:39.495 hiveregpath = Software\Wow6432Node\Microsoft\Microsoft SQL Server\90\DTS
05/18/2007 21:44:39.495 id =
05/18/2007 21:44:39.495 installsqldatadir =
05/18/2007 21:44:39.495 installsqldir = C:\Program Files (x86)\Microsoft SQL Server\90\DTS\
05/18/2007 21:44:39.495 lcid = 1033
05/18/2007 21:44:39.511 name =
05/18/2007 21:44:39.511 productcode = {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
05/18/2007 21:44:39.511 qfelevel = 3054
05/18/2007 21:44:39.511 servicename = MsDtsServer
05/18/2007 21:44:39.511 sku = STANDARD
05/18/2007 21:44:39.511 sp = 2
05/18/2007 21:44:39.511 type = Tools Only
05/18/2007 21:44:39.511 vermajbld = 3042
05/18/2007 21:44:39.511 version = 9
05/18/2007 21:44:39.511 wow64 = true
05/18/2007 21:44:39.511
05/18/2007 21:44:39.511 Product Enumeration Results:
05/18/2007 21:44:39.511 INF File Name: d:\78475438a18ffeb151\HotFixTools.inf
05/18/2007 21:44:39.511 baselinebuild = 1399
05/18/2007 21:44:39.511 baselinebuildmax = 3042
05/18/2007 21:44:39.511 build = 3042
05/18/2007 21:44:39.511 description = Client Components
05/18/2007 21:44:39.511 details = Service Pack for the interactive management tools for running SQL Server, including SQL Server Configuration Manager, SQL Server Management Studio, SQL Profiler, and Replication Monitor.
05/18/2007 21:44:39.511 installer = Hotfix
05/18/2007 21:44:39.511 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.511 kbarticle = KB921896
05/18/2007 21:44:39.511 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.511 lcid = 1033
05/18/2007 21:44:39.511 legalproductname = SQL Server Tools and Workstation Components 2005
05/18/2007 21:44:39.511 machinetype = x86
05/18/2007 21:44:39.511 package = HotFixTools
05/18/2007 21:44:39.511 packagetype = Hotfix
05/18/2007 21:44:39.511 productname = SQLTools9
05/18/2007 21:44:39.511 recommendinstall = 1
05/18/2007 21:44:39.511 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.511 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.511 sku = DESKTOP,STANDARD,WORKGROUP,ENTERPRISE,SBS,OFFICE,MSDE,DEVELOPERDESKTOP,DEVELOPERSTANDARD,PERSONAL,DEVELOPER,EVAL
05/18/2007 21:44:39.511 splevel = 2
05/18/2007 21:44:39.511 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.511 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.511 version = 9
05/18/2007 21:44:39.511
05/18/2007 21:44:39.511 File Group Details: MSP
05/18/2007 21:44:39.511 parameters = SQLBUILD=3042 KBNUMBER=KB921896 REBOOT=ReallySuppress
05/18/2007 21:44:39.511 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.511 File Details: sqlrun_tools.msp
05/18/2007 21:44:39.511
05/18/2007 21:44:39.511 Instance Details: SQL Tools
05/18/2007 21:44:39.511 associatedhotfixbuild = 3159
05/18/2007 21:44:39.511 clustername =
05/18/2007 21:44:39.511 details = The product instance SQL Tools been patched with more recent updates.
05/18/2007 21:44:39.511 fullversion = 9.2.3054
05/18/2007 21:44:39.511 hiveregpath = Software\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools
05/18/2007 21:44:39.511 id =
05/18/2007 21:44:39.511 installsqldatadir =
05/18/2007 21:44:39.511 installsqldir = C:\Program Files (x86)\Microsoft SQL Server\90\Tools\
05/18/2007 21:44:39.511 lcid = 1033
05/18/2007 21:44:39.511 name =
05/18/2007 21:44:39.511 productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
05/18/2007 21:44:39.511 qfelevel = 3054
05/18/2007 21:44:39.511 sku = STANDARD
05/18/2007 21:44:39.511 sp = 2
05/18/2007 21:44:39.511 type = Tools Only
05/18/2007 21:44:39.511 vermajbld = 3042
05/18/2007 21:44:39.511 version = 9
05/18/2007 21:44:39.511 wow64 = true
05/18/2007 21:44:39.511
05/18/2007 21:44:39.511 Product Enumeration Results:
05/18/2007 21:44:39.511 INF File Name: d:\78475438a18ffeb151\HotFixMsxml6.inf
05/18/2007 21:44:39.511 baselinebuild = 1399
05/18/2007 21:44:39.511 build = 6.10.1129.0
05/18/2007 21:44:39.511 description = MSXML 6.0 Parser
05/18/2007 21:44:39.511 details = Service Pack for Microsoft XML 6.0 Parser.
05/18/2007 21:44:39.511 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.511 kbarticle = KB921896
05/18/2007 21:44:39.511 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.511 lcid = 1033
05/18/2007 21:44:39.511 legalproductname = MSXML 6.0 Parser
05/18/2007 21:44:39.511 machinetype = x86
05/18/2007 21:44:39.511 package = HotFixMsxml6
05/18/2007 21:44:39.511 packagetype = Hotfix
05/18/2007 21:44:39.511 productname = Redist9
05/18/2007 21:44:39.511 recommendinstall = 1
05/18/2007 21:44:39.511 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.511 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.511 splevel = 2
05/18/2007 21:44:39.511 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.511 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.511 upgradecode = {1B117BA7-5BC1-419E-820E-7D4F3F412C7B}
05/18/2007 21:44:39.511 version = 9
05/18/2007 21:44:39.511
05/18/2007 21:44:39.527 File Group Details: MSI
05/18/2007 21:44:39.527 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.527 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.527 File Details: msxml6.msi
05/18/2007 21:44:39.527
05/18/2007 21:44:39.527 Product Enumeration Results:
05/18/2007 21:44:39.527 INF File Name: d:\78475438a18ffeb151\HotFixMsxml6_x64.inf
05/18/2007 21:44:39.527 baselinebuild = 1399
05/18/2007 21:44:39.527 build = 6.10.1129.0
05/18/2007 21:44:39.527 description = MSXML 6.0 Parser
05/18/2007 21:44:39.527 details = Service Pack for Microsoft XML 6.0 Parser.
05/18/2007 21:44:39.527 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.527 kbarticle = KB921896
05/18/2007 21:44:39.527 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.527 lcid = 1033
05/18/2007 21:44:39.527 legalproductname = MSXML 6.0 Parser (64-bit)
05/18/2007 21:44:39.527 machinetype = x64
05/18/2007 21:44:39.527 package = HotFixMsxml6_x64
05/18/2007 21:44:39.527 packagetype = Hotfix
05/18/2007 21:44:39.527 productcode = {633F3A7E-471D-4C08-A643-C184A2EE19AB}
05/18/2007 21:44:39.527 productname = Redist9
05/18/2007 21:44:39.527 recommendinstall = 1
05/18/2007 21:44:39.527 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.527 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.527 splevel = 2
05/18/2007 21:44:39.527 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.527 upgradecode = {5BBED1F8-E6F3-4A02-BC97-26D35BE200CA}
05/18/2007 21:44:39.527 version = 9
05/18/2007 21:44:39.527
05/18/2007 21:44:39.527 File Group Details: MSI
05/18/2007 21:44:39.527 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.527 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.527 File Details: msxml6_x64.msi
05/18/2007 21:44:39.527
05/18/2007 21:44:39.527 Instance Details: MSXML 6.0 Parser
05/18/2007 21:44:39.527 fullversion = 6.10.1129.0
05/18/2007 21:44:39.527 lcid = 1033
05/18/2007 21:44:39.527 productcode = {633F3A7E-471D-4C08-A643-C184A2EE19AB}
05/18/2007 21:44:39.527 qfelevel = 1129
05/18/2007 21:44:39.527 sp = -1
05/18/2007 21:44:39.527
05/18/2007 21:44:39.527 Product Enumeration Results:
05/18/2007 21:44:39.527 INF File Name: d:\78475438a18ffeb151\HotFixSqlxml4.inf
05/18/2007 21:44:39.527 baselinebuild = 1399
05/18/2007 21:44:39.527 build = 3042
05/18/2007 21:44:39.527 description = SQLXML4
05/18/2007 21:44:39.527 details = Service Pack for Microsoft SQLXML 4.0.
05/18/2007 21:44:39.527 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.527 kbarticle = KB921896
05/18/2007 21:44:39.527 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.527 lcid = 1033
05/18/2007 21:44:39.527 legalproductname = SQLXML4
05/18/2007 21:44:39.527 machinetype = x86
05/18/2007 21:44:39.527 package = HotFixSqlxml4
05/18/2007 21:44:39.527 packagetype = Hotfix
05/18/2007 21:44:39.527 productname = Redist9
05/18/2007 21:44:39.527 recommendinstall = 1
05/18/2007 21:44:39.527 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.527 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.527 splevel = 2
05/18/2007 21:44:39.527 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.527 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.527 upgradecode = {D9CA3D82-6F1B-41A7-8141-B90ACA8F865B}
05/18/2007 21:44:39.527 version = 9
05/18/2007 21:44:39.527
05/18/2007 21:44:39.527 File Group Details: MSI
05/18/2007 21:44:39.527 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.527 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.527 File Details: sqlxml4.msi
05/18/2007 21:44:39.527
05/18/2007 21:44:39.527 Product Enumeration Results:
05/18/2007 21:44:39.527 INF File Name: d:\78475438a18ffeb151\HotFixSqlxml4_x64.inf
05/18/2007 21:44:39.527 baselinebuild = 1399
05/18/2007 21:44:39.527 build = 3042
05/18/2007 21:44:39.527 description = SQLXML4
05/18/2007 21:44:39.527 details = Service Pack for Microsoft SQLXML 4.0.
05/18/2007 21:44:39.527 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.527 kbarticle = KB921896
05/18/2007 21:44:39.527 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.527 lcid = 1033
05/18/2007 21:44:39.527 legalproductname = SQLXML4 (64-bit)
05/18/2007 21:44:39.527 machinetype = x64
05/18/2007 21:44:39.527 package = HotFixSqlxml4_x64
05/18/2007 21:44:39.527 packagetype = Hotfix
05/18/2007 21:44:39.527 productcode = {1FE327DF-E05C-47C0-BDC9-1A3DC88089A0}
05/18/2007 21:44:39.527 productname = Redist9
05/18/2007 21:44:39.542 recommendinstall = 1
05/18/2007 21:44:39.542 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.542 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.542 splevel = 2
05/18/2007 21:44:39.542 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.542 upgradecode = {F457D8E6-7686-437D-9B17-E21D45CCABD8}
05/18/2007 21:44:39.542 version = 9
05/18/2007 21:44:39.542
05/18/2007 21:44:39.542 File Group Details: MSI
05/18/2007 21:44:39.542 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.542 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.542 File Details: sqlxml4_x64.msi
05/18/2007 21:44:39.542
05/18/2007 21:44:39.542 Instance Details: SQLXML4
05/18/2007 21:44:39.542 fullversion = 9.00.3042.00
05/18/2007 21:44:39.542 lcid = 1033
05/18/2007 21:44:39.542 productcode = {1FE327DF-E05C-47C0-BDC9-1A3DC88089A0}
05/18/2007 21:44:39.542 qfelevel = 3042
05/18/2007 21:44:39.542 sp = -1
05/18/2007 21:44:39.542
05/18/2007 21:44:39.542 Product Enumeration Results:
05/18/2007 21:44:39.542 INF File Name: d:\78475438a18ffeb151\HotFixSQLServer2005_BC.inf
05/18/2007 21:44:39.542 baselinebuild = 1399
05/18/2007 21:44:39.542 build = 2004
05/18/2007 21:44:39.542 description = Backward Compatibility
05/18/2007 21:44:39.542 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
05/18/2007 21:44:39.542 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.542 kbarticle = KB921896
05/18/2007 21:44:39.542 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.542 lcid = 1033
05/18/2007 21:44:39.542 legalproductname = Microsoft SQL Server 2005 Backward Compatibility
05/18/2007 21:44:39.542 machinetype = x86
05/18/2007 21:44:39.542 package = HotFixSQLServer2005_BC
05/18/2007 21:44:39.542 packagetype = Hotfix
05/18/2007 21:44:39.542 productname = Redist9
05/18/2007 21:44:39.542 recommendinstall = 1
05/18/2007 21:44:39.542 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.542 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.542 splevel = 2
05/18/2007 21:44:39.542 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.542 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.542 upgradecode = {1E70C6C9-E1B7-4A74-BC8C-8EB5D010CEC9}
05/18/2007 21:44:39.542 version = 9
05/18/2007 21:44:39.542
05/18/2007 21:44:39.542 File Group Details: MSI
05/18/2007 21:44:39.542 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.542 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.542 File Details: SQLServer2005_BC.msi
05/18/2007 21:44:39.542
05/18/2007 21:44:39.542 Product Enumeration Results:
05/18/2007 21:44:39.542 INF File Name: d:\78475438a18ffeb151\HotFixSQLServer2005_BC_x64.inf
05/18/2007 21:44:39.542 baselinebuild = 1399
05/18/2007 21:44:39.542 build = 2004
05/18/2007 21:44:39.542 description = Backward Compatibility
05/18/2007 21:44:39.542 details = Service Pack for the Backward Compatibility components, including Data Transformation Services Runtime and SQL-DMO.
05/18/2007 21:44:39.542 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.542 kbarticle = KB921896
05/18/2007 21:44:39.542 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.542 lcid = 1033
05/18/2007 21:44:39.542 legalproductname = Microsoft SQL Server 2005 Backward Compatibility (64-bit)
05/18/2007 21:44:39.542 machinetype = x64
05/18/2007 21:44:39.542 package = HotFixSQLServer2005_BC_x64
05/18/2007 21:44:39.542 packagetype = Hotfix
05/18/2007 21:44:39.542 productcode = {AAA936C2-46D5-401F-92E9-483616DDCCBD}
05/18/2007 21:44:39.542 productname = Redist9
05/18/2007 21:44:39.542 recommendinstall = 1
05/18/2007 21:44:39.542 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.542 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.542 splevel = 2
05/18/2007 21:44:39.542 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.542 upgradecode = {7B6BF434-3C72-4DB3-8049-FEF31AEAFF9A}
05/18/2007 21:44:39.542 version = 9
05/18/2007 21:44:39.542
05/18/2007 21:44:39.542 File Group Details: MSI
05/18/2007 21:44:39.542 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.542 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.542 File Details: SQLServer2005_BC_x64.msi
05/18/2007 21:44:39.542
05/18/2007 21:44:39.542 Instance Details: Backward Compatibility
05/18/2007 21:44:39.542 fullversion = 8.05.2004
05/18/2007 21:44:39.542 lcid = 1033
05/18/2007 21:44:39.542 productcode = {AAA936C2-46D5-401F-92E9-483616DDCCBD}
05/18/2007 21:44:39.542 qfelevel = 2004
05/18/2007 21:44:39.542 sp = -1
05/18/2007 21:44:39.558
05/18/2007 21:44:39.558 Product Enumeration Results:
05/18/2007 21:44:39.558 INF File Name: d:\78475438a18ffeb151\HotFixSqlWriter.inf
05/18/2007 21:44:39.558 baselinebuild = 1399
05/18/2007 21:44:39.558 build = 3042
05/18/2007 21:44:39.558 description = Microsoft SQL Server VSS Writer
05/18/2007 21:44:39.558 details = Service Pack for Microsoft SQL Server VSS Writer.
05/18/2007 21:44:39.558 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.558 kbarticle = KB921896
05/18/2007 21:44:39.558 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.558 lcid = 1033
05/18/2007 21:44:39.558 legalproductname = Microsoft SQL Server VSS Writer
05/18/2007 21:44:39.558 machinetype = x86
05/18/2007 21:44:39.558 package = HotFixSqlWriter
05/18/2007 21:44:39.558 packagetype = Hotfix
05/18/2007 21:44:39.558 productname = Redist9
05/18/2007 21:44:39.558 recommendinstall = 1
05/18/2007 21:44:39.558 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.558 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.558 splevel = 2
05/18/2007 21:44:39.558 sqladminprovisioningtool = <PROGRAMFILESDIR_WOW>\Microsoft SQL Server\90\Shared\sqlprov.exe
05/18/2007 21:44:39.558 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.558 upgradecode = {65D8E1DF-6201-4B53-A0F9-E654F8E80F97}
05/18/2007 21:44:39.558 version = 9
05/18/2007 21:44:39.558
05/18/2007 21:44:39.558 File Group Details: MSI
05/18/2007 21:44:39.558 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.558 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.558 File Details: SqlWriter.msi
05/18/2007 21:44:39.558
05/18/2007 21:44:39.558 Product Enumeration Results:
05/18/2007 21:44:39.558 INF File Name: d:\78475438a18ffeb151\HotFixSqlWriter_x64.inf
05/18/2007 21:44:39.558 baselinebuild = 1399
05/18/2007 21:44:39.558 build = 3042
05/18/2007 21:44:39.558 description = Microsoft SQL Server VSS Writer
05/18/2007 21:44:39.558 details = Service Pack for Microsoft SQL Server VSS Writer.
05/18/2007 21:44:39.558 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
05/18/2007 21:44:39.558 kbarticle = KB921896
05/18/2007 21:44:39.558 kbarticlehyperlink = http://support.microsoft.com/?kbid=921896
05/18/2007 21:44:39.558 lcid = 1033
05/18/2007 21:44:39.558 legalproductname = Microsoft SQL Server VSS Writer (64-bit)
05/18/2007 21:44:39.558 machinetype = x64
05/18/2007 21:44:39.558 package = HotFixSqlWriter_x64
05/18/2007 21:44:39.558 packagetype = Hotfix
05/18/2007 21:44:39.558 productcode = {50822200-2E95-4E62-A8D8-41C3B308DF5E}
05/18/2007 21:44:39.558 productname = Redist9
05/18/2007 21:44:39.558 recommendinstall = 1
05/18/2007 21:44:39.558 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
05/18/2007 21:44:39.558 servicepackname = Microsoft SQL Server 2005 Service Pack 2 Setup
05/18/2007 21:44:39.558 splevel = 2
05/18/2007 21:44:39.558 supportdir = d:\78475438a18ffeb151
05/18/2007 21:44:39.558 upgradecode = {E9031696-DD39-4C25-BAEB-425FF28279EA}
05/18/2007 21:44:39.558 version = 9
05/18/2007 21:44:39.558
05/18/2007 21:44:39.558 File Group Details: MSI
05/18/2007 21:44:39.558 cachedmsipath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\Cache
05/18/2007 21:44:39.558 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
05/18/2007 21:44:39.558 File Details: SqlWriter_x64.msi
05/18/2007 21:44:39.558
05/18/2007 21:44:39.558 Instance Details: Microsoft SQL Server VSS Writer
05/18/2007 21:44:39.558 fullversion = 9.00.3042.00
05/18/2007 21:44:39.558 lcid = 1033
05/18/2007 21:44:39.558 productcode = {50822200-2E95-4E62-A8D8-41C3B308DF5E}
05/18/2007 21:44:39.558 qfelevel = 3042
05/18/2007 21:44:39.558 sp = -1
05/18/2007 21:44:39.558
05/18/2007 21:44:43.949 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
05/18/2007 21:44:43.949 Registry: Read registry key value "PendingFileRenameOperations"
05/18/2007 21:44:43.949 Multi-string values:
05/18/2007 21:44:43.949 Registry: Read registry key value "PendingFileRenameOperations"
05/18/2007 21:44:43.949 Multi-string values:
05/18/2007 21:44:43.949 \?\d:\9c1880f2c0e05774722e49ad92
05/18/2007 21:44:43.949
05/18/2007 21:44:43.949 \?\d:\3b3c254d11e6c983cf743ab7
05/18/2007 21:44:43.949
05/18/2007 21:44:43.949 \?\d:\9b2f5a0be415da080e4390cb
05/18/2007 21:44:43.949
05/18/2007 21:44:43.949 \?\d:\2561ac7c0eba02af9f7bca1f0f5f
05/18/2007 21:44:43.949
05/18/2007 21:44:43.949 \?\d:\92b39bc2fdf6071a77e8ab
05/18/2007 21:44:43.949
05/18/2007 21:44:43.949 \?\d:\31ceba34bac86e2d0623
05/18/2007 21:44:43.949 PFR Check: PFR was found, but no files to be serviced were being referenced
05/18/2007 21:44:45.417 Authenticating user using Windows Authentication
05/18/2007 21:44:45.417 SQL Service MSSQLServer was previously running, ready for authentication
05/18/2007 21:44:45.417 SQL Agent Service SQLSERVERAGENT was previously running
05/18/2007 21:44:45.574 Authenticating user using Windows Authentication
05/18/2007 21:44:45.574 Validating database connections using Windows Authentication
05/18/2007 21:44:45.683 Pre-script database connection check was successful - proceeding with script execution
05/18/2007 21:44:45.792 Received sysadmin status for instance: MSSQLSERVER
05/18/2007 21:44:45.792 Validating database connections using Windows Authentication
05/18/2007 21:44:45.902 Pre-script database connection check was successful - proceeding with script execution
05/18/2007 21:44:45.902 User authentication was successful
05/18/2007 21:44:45.902 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/18/2007 21:44:45.902 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
05/18/2007 21:44:45.902 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/18/2007 21:44:45.902 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
05/18/2007 21:44:46.699 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/18/2007 21:44:46.699 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
05/18/2007 21:44:46.699 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/18/2007 21:44:46.699 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
05/18/2007 21:44:46.730 Locked file: Checking for locked files
05/18/2007 21:44:46.792 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\msfte.dll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.839 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\databasemailprotocols.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.839 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\databasemailengine.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.855 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\resources\1033\sqlevn70.rll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.855 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\resources\1033\xpstar90.rll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.855 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\dbghelp.dll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.870 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlsvc90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.870 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\xpstar90.dll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.870 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlos.dll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.870 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\xpsqlbot.dll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.870 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\xplog70.dll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.870 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlservr.exe (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\batchparser90.dll (MSSQLSERVER [sqlservr.exe] - 2668)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\batchparser90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\resources\1033\sqlagent90.rll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagentmail90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqldtsss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlrepss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlolapss90.dll (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:44:46.886 Locked file: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.1\MSSQL\binn\sqlagent90.exe (SQLSERVERAGENT [SQLAGENT90.EXE] - 4216)
05/18/2007 21:45:43.370 Locked file: Checking for locked files
05/18/2007 21:45:44.745 Attempting to pause the 32 bit ngen queue
05/18/2007 21:45:45.277 Installing product: SQL9
05/18/2007 21:45:45.277 Installing instance: MSSQLSERVER
05/18/2007 21:45:45.292 Installing target: DMZ-SQL03
05/18/2007 21:45:45.324 Installing file: sqlrun_sql.msp
05/18/2007 21:45:45.324 Copy Engine: Creating MSP install log file at: C:\Program Files (x86)\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB921896_sqlrun_sql.msp.log
05/18/2007 21:45:45.339 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
05/18/2007 21:45:45.339 Registry: Cannot read registry key value "Debug"
05/18/2007 21:46:18.995 MSP returned 1603: A fatal error occurred during installation.
05/18/2007 21:46:18.995 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
05/18/2007 21:46:18.995 Registry: Cannot read registry key value "Debug"
05/18/2007 21:46:19.480 Copy Engine: Error, unable to install MSP file: d:\78475438a18ffeb151\HotFixSQL\Files\sqlrun_sql.msp
05/18/2007 21:46:19.480 The following exception occurred: Unable to install Windows Installer MSP file Date: 05/18/2007 21:46:19.480 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 800
05/18/2007 21:46:19.792 Watson: Param1 = Unknown
05/18/2007 21:46:19.792 Watson: Param2 = 0x2b18
05/18/2007 21:46:19.792 Watson: Param3 = Unknown
05/18/2007 21:46:19.792 Watson: Param4 = 0x0
05/18/2007 21:46:19.792 Watson: Param5 = copyengine.cpp@.800
05/18/2007 21:46:19.792 Watson: Param6 = Unknown
05/18/2007 21:46:19.792 Watson: Param7 = SQL9
05/18/2007 21:46:19.792 Watson: Param8 = Hotfix@.
05/18/2007 21:46:19.792 Watson: Param9 = x86
05/18/2007 21:46:19.792 Watson: Param10 = 3042
05/18/2007 21:46:19.792 Installed product: SQL9
05/18/2007 21:46:19.792 Hotfix package completed
05/18/2007 21:46:19.792 Attempting to continue the 32 bit ngen queue

Can you search your log directory for the text string "value 3" and post the 10-15 lines above that? It should contain a more helpful error message.

Thanks,
Sam Lester (MSFT)

Cant install SQL Server 2005 on vista..

I'm loading the dev version of sql 2005 on vista ultmate. I'm not seeing the manager tools. I've installed sp2. In the services it says sql express but not sql server. I read the requirments for the dev version and it didn't list vista. Any ideas?

Two issues.

First, you may have SQL Express installed. SQL Express is NOT installed by SQL Developer Edition. You may wish to remove the SQL Express instance.

Second, the client tools are not automatically installed when you install SQL Server. You will need to insert the installation media, and select [Client Tools] to install SSMS.

|||

Thanks Arnie.

I'll take a look. However when I had xp pro setup SQL and SQL Express were both runnning. And I did the client tools and I'll revisit that. I want to make sure there are no issues between Vista Ultmate and SQL 2005. I think I've seen a few problems out there, but none like this particular issue.

|||

I am unable to download the following modules/components with my installation on Vista. As for not seeing the management console, I am using the trial download, so I cannot access any of the management tools on the media you are referring to, as well. Once I finish the installation, I do not see any reference to the SQL Server application in the Program directory, however, a directory has been created for it. I suppose this is because most of the key components are failing to install. In addition, IIS is installed, enabled, and running on my system, but I continually receive the error message during the first stage of installation indicating that IIS has not been detected and needs to be installed and enabled. I have tried stopping the service during installation, and it has not made a difference. I would greatly appreciate any good advice. Thanks.

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

BUTTONS:

&Retry
Cancel

TITLE: Microsoft SQL Server 2005 Setup

SQL Server Setup Failed to compile the Managed Object Format (MOF) file C:\Program Files\Microsoft SQL Server\90\Shared\sqlmgmproviderxpsp2up.mof. To proceed, see "Troubleshooting an Installation of SQL Server 2005" or "How to: View SQL Server 2005 Setup Log Files" in SQL Server 2005 Setup Help documentation.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=29513&EvtType=sqlca%5csqlmofca.cpp%40Do_sqlMofcomp%40Do_sqlMofcomp%40x7349

BUTTONS:

&Retry
Cancel

TITLE: Microsoft SQL Server 2005 Setup

BUTTONS:

&Retry
Cancel

TITLE: Microsoft SQL Server 2005 Setup

BUTTONS:

&Retry
Cancel

Tuesday, February 14, 2012

can't install sql developer on vista

i am having a heck of a time -- i know SP2 makes sql server 2005
incompatiable... however, i need an instance INSTALLED first and that is
where the problem lies.
i of course built my system and put office on before visual studio - so
office put sql express on the system (which worked by the way) -- so i had to
uninstall sql express, because i wanted to use sql developer.
when i try to install sql developer it doesn't install owc , sql server or
the workstation tools.
how do I get sql installed on vista so i can continue working?
thanks
SandyHi Sandy
"Sandy Ryan" wrote:
> i am having a heck of a time -- i know SP2 makes sql server 2005
> incompatiable... however, i need an instance INSTALLED first and that is
> where the problem lies.
> i of course built my system and put office on before visual studio - so
> office put sql express on the system (which worked by the way) -- so i had to
> uninstall sql express, because i wanted to use sql developer.
> when i try to install sql developer it doesn't install owc , sql server or
> the workstation tools.
> how do I get sql installed on vista so i can continue working?
> thanks
> Sandy
Did you check what the readme says about Vista issues?
http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm#_windows_vista or the log files such as SQLSTP.log
John|||i did read this, but this relates to SP2 - not the base installation WHICH
has to be there before apply SP2 -- and that's what i'm having trouble with.
any clues?
"John Bell" wrote:
> Hi Sandy
> "Sandy Ryan" wrote:
> > i am having a heck of a time -- i know SP2 makes sql server 2005
> > incompatiable... however, i need an instance INSTALLED first and that is
> > where the problem lies.
> > i of course built my system and put office on before visual studio - so
> > office put sql express on the system (which worked by the way) -- so i had to
> > uninstall sql express, because i wanted to use sql developer.
> > when i try to install sql developer it doesn't install owc , sql server or
> > the workstation tools.
> > how do I get sql installed on vista so i can continue working?
> > thanks
> > Sandy
> Did you check what the readme says about Vista issues?
> http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm#_windows_vista or the log files such as SQLSTP.log
> John
>|||Hi Sandy
So what messages are you getting when it fails? What does SQLStp.log say?
John
"Sandy Ryan" wrote:
> i did read this, but this relates to SP2 - not the base installation WHICH
> has to be there before apply SP2 -- and that's what i'm having trouble with.
> any clues?
> "John Bell" wrote:
> > Hi Sandy
> >
> > "Sandy Ryan" wrote:
> >
> > > i am having a heck of a time -- i know SP2 makes sql server 2005
> > > incompatiable... however, i need an instance INSTALLED first and that is
> > > where the problem lies.
> > > i of course built my system and put office on before visual studio - so
> > > office put sql express on the system (which worked by the way) -- so i had to
> > > uninstall sql express, because i wanted to use sql developer.
> > > when i try to install sql developer it doesn't install owc , sql server or
> > > the workstation tools.
> > > how do I get sql installed on vista so i can continue working?
> > > thanks
> > > Sandy
> >
> > Did you check what the readme says about Vista issues?
> > http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm#_windows_vista or the log files such as SQLSTP.log
> >
> > John
> >
> >|||John
I searched my system and couldn't find the ssqlstp.log -
but the summary log says:
Microsoft SQL Server 2005 9.00.1399.06
==============================OS Version : Professional (Build 6000)
Time : Fri Feb 23 10:12:20 2007
Machine : SWTAB2
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_1.log
----
Machine : SWTAB2
Product : OWC11
Error : Error 1706. Setup cannot find the required files. Check
your connection to the network, or CD-ROM drive. For other potential
solutions to this problem, see C:\Program Files\Microsoft
Office\OFFICE11\1033\SETUP.CHM.
----
Machine : SWTAB2
Product : Microsoft Office 2003 Web Components
Product Version : 11.0.8003.0
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_OWC11_1.log
Last Action : InstallExecute
Error String : Setup cannot find the required files. Check your
connection to the network, or CD-ROM drive. For other potential solutions to
this problem, see C:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM.
Error Number : 1706
----
Machine : SWTAB2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_1.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_2.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_1.log
----
Machine : SWTAB2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_2.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_3.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_2.log
----
Machine : SWTAB2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_3.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_4.log
----
Machine : SWTAB2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_4.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_5.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_3.log
----
Machine : SWTAB2
Product : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SqlWriter_1.log
----
Machine : SWTAB2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_5.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_6.log
----
Machine : SWTAB2
Product : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_4.log
----
Machine : SWTAB2
Product : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BOL_1.log
----
Machine : SWTAB2
Product : Microsoft SQL Server 2005 Backward compatibility
Product Version : 8.05.1054
Install : Successful
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_6.log
----
Machine : SWTAB2
Product : SQLXML4
Error : An installation package for the product SQLXML4 cannot be
found. Try the installation again using a valid copy of the installation
package 'sqlxml4.msi'.
----
Machine : SWTAB2
Product : SQLXML4
Product Version : 9.00.3042.00
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLXML4_1.log
Last Action : InstallFinalize
Error String : An installation package for the product SQLXML4 cannot be
found. Try the installation again using a valid copy of the installation
package 'sqlxml4.msi'.
Error Number : 1706
---
"John Bell" wrote:
> Hi Sandy
> So what messages are you getting when it fails? What does SQLStp.log say?
> John
> "Sandy Ryan" wrote:
> >
> > i did read this, but this relates to SP2 - not the base installation WHICH
> > has to be there before apply SP2 -- and that's what i'm having trouble with.
> >
> > any clues?
> >
> > "John Bell" wrote:
> >
> > > Hi Sandy
> > >
> > > "Sandy Ryan" wrote:
> > >
> > > > i am having a heck of a time -- i know SP2 makes sql server 2005
> > > > incompatiable... however, i need an instance INSTALLED first and that is
> > > > where the problem lies.
> > > > i of course built my system and put office on before visual studio - so
> > > > office put sql express on the system (which worked by the way) -- so i had to
> > > > uninstall sql express, because i wanted to use sql developer.
> > > > when i try to install sql developer it doesn't install owc , sql server or
> > > > the workstation tools.
> > > > how do I get sql installed on vista so i can continue working?
> > > > thanks
> > > > Sandy
> > >
> > > Did you check what the readme says about Vista issues?
> > > http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm#_windows_vista or the log files such as SQLSTP.log
> > >
> > > John
> > >
> > >|||also
all the path error messages - the files ARE There
"Sandy Ryan" wrote:
> John
> I searched my system and couldn't find the ssqlstp.log -
> but the summary log says:
> Microsoft SQL Server 2005 9.00.1399.06
> ==============================> OS Version : Professional (Build 6000)
> Time : Fri Feb 23 10:12:20 2007
> Machine : SWTAB2
> Product : Microsoft SQL Server Setup Support Files (English)
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_1.log
> ----
> Machine : SWTAB2
> Product : OWC11
> Error : Error 1706. Setup cannot find the required files. Check
> your connection to the network, or CD-ROM drive. For other potential
> solutions to this problem, see C:\Program Files\Microsoft
> Office\OFFICE11\1033\SETUP.CHM.
> ----
> Machine : SWTAB2
> Product : Microsoft Office 2003 Web Components
> Product Version : 11.0.8003.0
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_OWC11_1.log
> Last Action : InstallExecute
> Error String : Setup cannot find the required files. Check your
> connection to the network, or CD-ROM drive. For other potential solutions to
> this problem, see C:\Program Files\Microsoft Office\OFFICE11\1033\SETUP.CHM.
> Error Number : 1706
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server 2005 Backward compatibility
> Product Version : 8.05.1054
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_1.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Setup Support Files (English)
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_2.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Native Client
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_1.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server 2005 Backward compatibility
> Product Version : 8.05.1054
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_2.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Setup Support Files (English)
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_3.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Native Client
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_2.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server 2005 Backward compatibility
> Product Version : 8.05.1054
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_3.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Setup Support Files (English)
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_4.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server 2005 Backward compatibility
> Product Version : 8.05.1054
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_4.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Setup Support Files (English)
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_5.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Native Client
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_3.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server VSS Writer
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SqlWriter_1.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server 2005 Backward compatibility
> Product Version : 8.05.1054
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_5.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Setup Support Files (English)
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLSupport_6.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server Native Client
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLNCLI_4.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server 2005 Books Online (English)
> Product Version : 9.00.1399.06
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BOL_1.log
> ----
> Machine : SWTAB2
> Product : Microsoft SQL Server 2005 Backward compatibility
> Product Version : 8.05.1054
> Install : Successful
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_BackwardsCompat_6.log
> ----
> Machine : SWTAB2
> Product : SQLXML4
> Error : An installation package for the product SQLXML4 cannot be
> found. Try the installation again using a valid copy of the installation
> package 'sqlxml4.msi'.
> ----
> Machine : SWTAB2
> Product : SQLXML4
> Product Version : 9.00.3042.00
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0001_SWTAB2_SQLXML4_1.log
> Last Action : InstallFinalize
> Error String : An installation package for the product SQLXML4 cannot be
> found. Try the installation again using a valid copy of the installation
> package 'sqlxml4.msi'.
> Error Number : 1706
> ---
> "John Bell" wrote:
> > Hi Sandy
> >
> > So what messages are you getting when it fails? What does SQLStp.log say?
> >
> > John
> >
> > "Sandy Ryan" wrote:
> >
> > >
> > > i did read this, but this relates to SP2 - not the base installation WHICH
> > > has to be there before apply SP2 -- and that's what i'm having trouble with.
> > >
> > > any clues?
> > >
> > > "John Bell" wrote:
> > >
> > > > Hi Sandy
> > > >
> > > > "Sandy Ryan" wrote:
> > > >
> > > > > i am having a heck of a time -- i know SP2 makes sql server 2005
> > > > > incompatiable... however, i need an instance INSTALLED first and that is
> > > > > where the problem lies.
> > > > > i of course built my system and put office on before visual studio - so
> > > > > office put sql express on the system (which worked by the way) -- so i had to
> > > > > uninstall sql express, because i wanted to use sql developer.
> > > > > when i try to install sql developer it doesn't install owc , sql server or
> > > > > the workstation tools.
> > > > > how do I get sql installed on vista so i can continue working?
> > > > > thanks
> > > > > Sandy
> > > >
> > > > Did you check what the readme says about Vista issues?
> > > > http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/ReadmeSQL2005SP2.htm#_windows_vista or the log files such as SQLSTP.log
> > > >
> > > > John
> > > >
> > > >|||Hi
"Sandy Ryan" wrote:
> also
> all the path error messages - the files ARE There
>
Have you tried copying the CD to the local hard disc? Where did you get the
installation from? Is it corrupted?
John|||msdn subscription
i have it on the local machines cd - i'll try copying it over
"John Bell" wrote:
> Hi
> "Sandy Ryan" wrote:
> > also
> > all the path error messages - the files ARE There
> >
> Have you tried copying the CD to the local hard disc? Where did you get the
> installation from? Is it corrupted?
> John|||"Sandy Ryan" wrote:
> i am having a heck of a time -- i know SP2 makes sql server 2005
> incompatiable... however, i need an instance INSTALLED first and that is
> where the problem lies.
> i of course built my system and put office on before visual studio - so
> office put sql express on the system (which worked by the way) -- so i had to
> uninstall sql express, because i wanted to use sql developer.
> when i try to install sql developer it doesn't install owc , sql server or
> the workstation tools.
> how do I get sql installed on vista so i can continue working?
> thanks
> Sandy
I found the following similar problem and resolution. I am not sure if this
is exactly what you experienced, but it sounds close.
I installed:
-Vista Ultimate x64
-Sql Server 2005 Express Edition (via Visual Studio 2005 Pro)
At this point, Sql Express is installed, but NOT Management Studio. I then
tried to Install Sql Dev edition. I discovered that it was considered an
Upgrade from Sql Express. But the kicker: it would NOT install the
Workstation Tools because it thought it didnâ't qualify for an Upgrade! I
think this is a bug personally. Even though Sql Express was installed AND is
a valid upgrade path to Sql Dev, the problem is that it didnâ't see Management
Studio, and therefore assumed you donâ't have rights to install Dev edition
Workstation Tools (completely stupid).
Resolution:
-Go to Programs and Features
-Right Click Microsoft Sql Server 2005 and select Uninstall
-Check ONLY the box that says Workstation Tools (donâ't uninstall Sql Express
unless you donâ't want it)
-Click Next and finish the Uninstall of the Workstation Components
-Run setup for Sql Dev edition
Worked like a charm. I now have Sql 2005 Express and Sql Dev 2005 editions
running, and the Dev edition tools wherewith to manage them (and BTW, there
are reasons you want to keep Sql Express depending on what you are
developing). Apparently, Sql Dev edition has now been tricked into thinking
itâ's a clean install since the Express edition of the workstation tools were
removed (no longer an â'unsupported upgradeâ' scenario). It will therefore go
ahead with Dev edition Workstation tools, and Management Studio also gets
installed.
Tip: Remember to run SP2 for both Sql Express and Sql Dev at this point.
Also, I believe an alternative resolution is to simply install Sql Express
Management Studio after Sql Express (Visual Studio), and THEN run the Sql Dev
edition install, and it will in fact upgrade everything properly. I cannot
confirm this, but I recall having a conversation with a friend at Microsoft
who said that worked for him.
I hope this post helps some poor souls out there!
-David P.|||You helped out this poor soul.
Thanks David.|||David
Thanks for the information
Unfortuntately it didn't work, I'm still getting SQLXMK4; OWC11 and
Workstation errors so they don't install
any other thoughts?
thanks
Sandy
"David Pugmire" wrote:
>
> "Sandy Ryan" wrote:
> > i am having a heck of a time -- i know SP2 makes sql server 2005
> > incompatiable... however, i need an instance INSTALLED first and that is
> > where the problem lies.
> > i of course built my system and put office on before visual studio - so
> > office put sql express on the system (which worked by the way) -- so i had to
> > uninstall sql express, because i wanted to use sql developer.
> > when i try to install sql developer it doesn't install owc , sql server or
> > the workstation tools.
> > how do I get sql installed on vista so i can continue working?
> > thanks
> > Sandy
> I found the following similar problem and resolution. I am not sure if this
> is exactly what you experienced, but it sounds close.
> I installed:
> -Vista Ultimate x64
> -Sql Server 2005 Express Edition (via Visual Studio 2005 Pro)
> At this point, Sql Express is installed, but NOT Management Studio. I then
> tried to Install Sql Dev edition. I discovered that it was considered an
> Upgrade from Sql Express. But the kicker: it would NOT install the
> Workstation Tools because it thought it didnâ't qualify for an Upgrade! I
> think this is a bug personally. Even though Sql Express was installed AND is
> a valid upgrade path to Sql Dev, the problem is that it didnâ't see Management
> Studio, and therefore assumed you donâ't have rights to install Dev edition
> Workstation Tools (completely stupid).
> Resolution:
> -Go to Programs and Features
> -Right Click Microsoft Sql Server 2005 and select Uninstall
> -Check ONLY the box that says Workstation Tools (donâ't uninstall Sql Express
> unless you donâ't want it)
> -Click Next and finish the Uninstall of the Workstation Components
> -Run setup for Sql Dev edition
> Worked like a charm. I now have Sql 2005 Express and Sql Dev 2005 editions
> running, and the Dev edition tools wherewith to manage them (and BTW, there
> are reasons you want to keep Sql Express depending on what you are
> developing). Apparently, Sql Dev edition has now been tricked into thinking
> itâ's a clean install since the Express edition of the workstation tools were
> removed (no longer an â'unsupported upgradeâ' scenario). It will therefore go
> ahead with Dev edition Workstation tools, and Management Studio also gets
> installed.
> Tip: Remember to run SP2 for both Sql Express and Sql Dev at this point.
> Also, I believe an alternative resolution is to simply install Sql Express
> Management Studio after Sql Express (Visual Studio), and THEN run the Sql Dev
> edition install, and it will in fact upgrade everything properly. I cannot
> confirm this, but I recall having a conversation with a friend at Microsoft
> who said that worked for him.
> I hope this post helps some poor souls out there!
> -David P.
>|||David
Thanks for the help - unfortunately I'm still getting errors on SQLS=XML4;
OWC11 and Workstation tools when i attempt to load (eventhough SQLXML4 is
already installed)
Any other suggestions?
"David Pugmire" wrote:
>
> "Sandy Ryan" wrote:
> > i am having a heck of a time -- i know SP2 makes sql server 2005
> > incompatiable... however, i need an instance INSTALLED first and that is
> > where the problem lies.
> > i of course built my system and put office on before visual studio - so
> > office put sql express on the system (which worked by the way) -- so i had to
> > uninstall sql express, because i wanted to use sql developer.
> > when i try to install sql developer it doesn't install owc , sql server or
> > the workstation tools.
> > how do I get sql installed on vista so i can continue working?
> > thanks
> > Sandy
> I found the following similar problem and resolution. I am not sure if this
> is exactly what you experienced, but it sounds close.
> I installed:
> -Vista Ultimate x64
> -Sql Server 2005 Express Edition (via Visual Studio 2005 Pro)
> At this point, Sql Express is installed, but NOT Management Studio. I then
> tried to Install Sql Dev edition. I discovered that it was considered an
> Upgrade from Sql Express. But the kicker: it would NOT install the
> Workstation Tools because it thought it didnâ't qualify for an Upgrade! I
> think this is a bug personally. Even though Sql Express was installed AND is
> a valid upgrade path to Sql Dev, the problem is that it didnâ't see Management
> Studio, and therefore assumed you donâ't have rights to install Dev edition
> Workstation Tools (completely stupid).
> Resolution:
> -Go to Programs and Features
> -Right Click Microsoft Sql Server 2005 and select Uninstall
> -Check ONLY the box that says Workstation Tools (donâ't uninstall Sql Express
> unless you donâ't want it)
> -Click Next and finish the Uninstall of the Workstation Components
> -Run setup for Sql Dev edition
> Worked like a charm. I now have Sql 2005 Express and Sql Dev 2005 editions
> running, and the Dev edition tools wherewith to manage them (and BTW, there
> are reasons you want to keep Sql Express depending on what you are
> developing). Apparently, Sql Dev edition has now been tricked into thinking
> itâ's a clean install since the Express edition of the workstation tools were
> removed (no longer an â'unsupported upgradeâ' scenario). It will therefore go
> ahead with Dev edition Workstation tools, and Management Studio also gets
> installed.
> Tip: Remember to run SP2 for both Sql Express and Sql Dev at this point.
> Also, I believe an alternative resolution is to simply install Sql Express
> Management Studio after Sql Express (Visual Studio), and THEN run the Sql Dev
> edition install, and it will in fact upgrade everything properly. I cannot
> confirm this, but I recall having a conversation with a friend at Microsoft
> who said that worked for him.
> I hope this post helps some poor souls out there!
> -David P.
>|||I also was having a problem installing SQL 2005 Developer edition on Vista. I
ended up copying the install to my hard drive and then right clicking on the
setup.exe and choose properties. I then went to the compatability tab and
checked the box that said run in compatability mode for Windows XP Service
Pack2 and also checked the box that said run this prgram as administrator. I
then ran the setup.exe by double clicking on it and I no longer got any
errors.
"Sandy Ryan" wrote:
> David
> Thanks for the help - unfortunately I'm still getting errors on SQLS=XML4;
> OWC11 and Workstation tools when i attempt to load (eventhough SQLXML4 is
> already installed)
> Any other suggestions?
> "David Pugmire" wrote:
> >
> >
> > "Sandy Ryan" wrote:
> >
> > > i am having a heck of a time -- i know SP2 makes sql server 2005
> > > incompatiable... however, i need an instance INSTALLED first and that is
> > > where the problem lies.
> > > i of course built my system and put office on before visual studio - so
> > > office put sql express on the system (which worked by the way) -- so i had to
> > > uninstall sql express, because i wanted to use sql developer.
> > > when i try to install sql developer it doesn't install owc , sql server or
> > > the workstation tools.
> > > how do I get sql installed on vista so i can continue working?
> > > thanks
> > > Sandy
> >
> > I found the following similar problem and resolution. I am not sure if this
> > is exactly what you experienced, but it sounds close.
> >
> > I installed:
> > -Vista Ultimate x64
> > -Sql Server 2005 Express Edition (via Visual Studio 2005 Pro)
> >
> > At this point, Sql Express is installed, but NOT Management Studio. I then
> > tried to Install Sql Dev edition. I discovered that it was considered an
> > Upgrade from Sql Express. But the kicker: it would NOT install the
> > Workstation Tools because it thought it didnâ't qualify for an Upgrade! I
> > think this is a bug personally. Even though Sql Express was installed AND is
> > a valid upgrade path to Sql Dev, the problem is that it didnâ't see Management
> > Studio, and therefore assumed you donâ't have rights to install Dev edition
> > Workstation Tools (completely stupid).
> >
> > Resolution:
> > -Go to Programs and Features
> > -Right Click Microsoft Sql Server 2005 and select Uninstall
> > -Check ONLY the box that says Workstation Tools (donâ't uninstall Sql Express
> > unless you donâ't want it)
> > -Click Next and finish the Uninstall of the Workstation Components
> > -Run setup for Sql Dev edition
> >
> > Worked like a charm. I now have Sql 2005 Express and Sql Dev 2005 editions
> > running, and the Dev edition tools wherewith to manage them (and BTW, there
> > are reasons you want to keep Sql Express depending on what you are
> > developing). Apparently, Sql Dev edition has now been tricked into thinking
> > itâ's a clean install since the Express edition of the workstation tools were
> > removed (no longer an â'unsupported upgradeâ' scenario). It will therefore go
> > ahead with Dev edition Workstation tools, and Management Studio also gets
> > installed.
> >
> > Tip: Remember to run SP2 for both Sql Express and Sql Dev at this point.
> > Also, I believe an alternative resolution is to simply install Sql Express
> > Management Studio after Sql Express (Visual Studio), and THEN run the Sql Dev
> > edition install, and it will in fact upgrade everything properly. I cannot
> > confirm this, but I recall having a conversation with a friend at Microsoft
> > who said that worked for him.
> >
> > I hope this post helps some poor souls out there!
> >
> > -David P.
> >

Sunday, March 25, 2012

Can't start 2005 Report Services on XP SP2

Tuesday, March 20, 2012

can't see SQL server objects and counters on performance monitor

can't see SQL server objects and counters on performance monitor

cant see server

Sunday, March 11, 2012

Can't run rskeymgmt after SP2

Thursday, March 8, 2012

CAN'T remove "Execute job" from alert in SS 2005?

Thursday, February 16, 2012

Can't install sqlncli.msi

Can't install sqlncli.msi

Can't install sqlncli.msi

Cant install sql server express...check out these errors

Can't install SQL Server 2005 SP2

Cant install SQL Server 2005 on vista..

Tuesday, February 14, 2012

can't install sql developer on vista

sql report manager

Blog Archive

About Me