Sql 2005 express installation (Vista Ultimate)
While installing SQL Server 2005 Express Edition SP2 or SQL Server 2005 Express Edition with Advanced Services SP2
on Vista Ultimate, I get the error "The feature(s) selected are not valid for this edition of SQL server". Then the installation stops and exist. The only feature selected is Database Services, data files and shared tools.
HELP!
Thank you in advance for your response. I have listed below my system configuration check and the error message text.
System Configuration Check
- WMI Service Requirement (Success)
Messages
· WMI Service Requirement
· Check Passed
- MSXML Requirement (Success)
Messages
· MSXML Requirement
· Check Passed
- Operating System Minimum Level Requirement (Success)
Messages
· Operating System Minimum Level Requirement
· Check Passed
- Operating System Service Pack Level Requirement. (Success)
Messages
· Operating System Service Pack Level Requirement.
· Check Passed
- SQL Server Edition Operating System Compatibility (Success)
Messages
· SQL Server Edition Operating System Compatibility
· Check Passed
- Minimum Hardware Requirement (Success)
Messages
· Minimum Hardware Requirement
· Check Passed
- IIS Feature Requirement (Success)
Messages
· IIS Feature Requirement
· Check Passed
- Pending Reboot Requirement (Success)
Messages
· Pending Reboot Requirement
· Check Passed
- Performance Monitor Counter Requirement (Success)
Messages
· Performance Monitor Counter Requirement
· Check Passed
- Default Installation Path Permission Requirement (Success)
Messages
· Default Installation Path Permission Requirement
· Check Passed
- Internet Explorer Requirement (Success)
Messages
· Internet Explorer Requirement
· Check Passed
- COM Plus Catalog Requirement (Success)
Messages
· COM Plus Catalog Requirement
· Check Passed
- ASP.Net Version Registration Requirement (Success)
Messages
· ASP.Net Version Registration Requirement
· Check Passed
- Minimum MDAC Version Requirement (Success)
Messages
· Minimum MDAC Version Requirement
· Check Passed
- Edition Change Check (Success)
Messages
· Edition Change Check
· Check Passed
====================================================================================================
After selecting the database feature only, this error message below pop up and the install quits and exit.
TITLE: Microsoft SQL Server 2005 Setup
The feature(s) specified are not valid for this edition of SQL Server.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=70031&EvtType=sqlchaining%5csqlchainingactions.cpp%40DeterminePackageTransformsAction%40sqls%3a%3aDeterminePackageTransformsAction%3a%3aperform%400x1118f
BUTTONS:
OK
Similar Messages
-
MOF syntax error occurred while installing 2008 SQL server Express on Vista Ultimate
I have tried cleaning, then installing 2008 SQL server Express on Vista Ultimate 3 times and spent hours on this. I have installed regular SQL server on 2003 server with no issues many times, but I have huge issues with 2008 SQL server Express. I keep getting the proceeding errors.
Any ideas?
Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: A MOF syntax error occurred.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt
Feature: SQL Client Connectivity SDK
Status: Passed
MSI status: Passed
Configuration status: Passed
Feature: SQL Server Replication
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: A MOF syntax error occurred.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt
Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x0A2FBD17@1211@1
Configuration error description: A MOF syntax error occurred.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\Detail.txt
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20081202_010008\SystemConfigurationCheck_Report.htmSimilar error (not SQL Express but Enterprise) on my network reveals the following issue (still prevalent after removing and re-adding the machine to the network):
The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/machinename.domainname.local. The target name used was cifs/MACHINENAME. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (DOMAINNAME.LOCAL), and the client realm. Please contact your system administrator.
ALSO: The session setup from the computer MACHINENAME failed to authenticate. The name(s) of the account(s) referenced in the security database is MACHINENAME$. The following error occurred: Access is denied.
This default instance (Ent SQL 2008 on Ent Server 64 bit 2003 R2 SP2) failed with the MOF error using a service account to install SQL 2008. Repair does not work. "The SQL Server feature 'SQL_Engine_Core_Inst' is not in a supported state for repair, as it was never successfully configured. Only features from successful installations can be repaired. To continue, remove the specified SQL Server feature."
I expected to have more luck with the information here: http://mark.michaelis.net/Blog/CategoryView.aspx?category=.Net but wound up with result seen in my next post.
Of note, tried the removal of leftover registry entries after a failed install as in link above, also removed sql folders prior to re-install. Error is the same and rather than list entire log here, there is a portion available below but as is evident, there is a permission error in the registry which verifies what mark michaelis has pointed out:
"Sco: Compile operation for mof file \etcls.mof.transformed failed. Exit code 3" "Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC." "A MOF syntax error occurred." "Configuration action failed for feature SQL_Engine_Core_Inst during timing ConfigNonRC and scenario ConfigNonRC." Here is more: at Microsoft.SqlServer.Configuration.Sco.WmiProvider.InstallMof() 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.EtwSetup.Install(String strInstanceName, Guid guidInstance, String strPath) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.SetupETW(EffectiveProperties properties) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install_ConfigNonRC_Prepare(EffectiveProperties properties) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineSetupPrivate.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcb) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SqlFeatureConfigBase.Execute(ConfigActionScenario scenario, ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbCurrent) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId) 2009-03-31 10:51:19 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream) 2009-03-31 10:51:19 Slp: Exception: Microsoft.SqlServer.Configuration.Sco.ScoException. 2009-03-31 10:51:19 Slp: Source: Microsoft.SqlServer.Configuration.Sco. 2009-03-31 10:51:19 Slp: Message: A MOF syntax error occurred.. 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file E:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20090331_102539\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_ 2009-03-31 10:51:20 Slp: Sco: Attempting to write hklm registry key
(And so on - cannot read or write the registry key)... -
B1i (2005) installation failedSo far: windows XP, MS-SQL 2005 express: ok
Dear All,
I try to install B1i for NW 2005 on a SBO 2005B installation. I have installed all prerequisites like JDK, MSXML, Tomcat (no blanks in path). When running the setup program and after all information gathered, the connection to the MS-SQL 2005 database succeeds and the final installation step starts but returns the message:
"Initail database failed, make sure Tomcat or mini-http is shut down and please check your database's status and try again"
Looking into MS-SQL shows a database beeing created named localhost/B1i. Tomcat and mini-http are definately shut down. When starting Tomcat, it is accessible via http://localhost:8080.
System Parameters:
windows server 2003
SBO 2005B
java: 1.4.2.19
tomcat 5.5.27 including compat package for 1.4.2.19)
sql jdbc 1.2.2828.100
msxml 4.0 SP 2
I can not find an error in the system. Is there a way to diagnose what is happening and does anyone have an idea where the problem lies?
Ciao, Mathias
[Update]
I have tried JDBC 2.0.1008 and JDBC 2.0.1607 - both lead to a fatal error when trying to connect to the database. I assume this is due to Java JDK 1.4.2 as JDBC requires Java 5.0 (1.5.0)
Does anybody know if I can use JDK 1.5.0_17 instead of 1.4.2_19?
[Update 2]
I have tried to install the B1i on two other servers with identical setup and it worked. However, this will not help me with this machine... On the other side, it shows, that there is nothing wrong with the procedure I am using
I found by the way: B1i works fine with MSSQL 2005 Express, it works with jdk 1.5.0.17 (and then JDBC 2.0)
[Update 3]
So far:
windows XP, MS-SQL 2005 express: ok
windows XP, MS-SQL 2005 express, SBO2005A: ok
windows 2003, MS-SQL 2005 SBO2005A: fail
windows 2003, MS-SQL 2005 SBO2005B: fail
windows 2003, MS-SQL 2005 SBO2007A: ok
windows 2003, MS-SQL 2005 Netweaver 2004S: fail
Unfortunately the three servers where it fails are the ones I need to use for production
The precise error state is that the install routine creates the database in SQL 2005 and then reports that it can not create the database. Is there something I should check in SQL 2005?
Edited by: Mathias Wilhelm on Feb 11, 2009 5:17 PMSalut Eddy,
I tried it with tomcat 5.0.30 - no success. JDK is 1.4.2.19
I tried it with tomcat 5.5.27 - no success. JDK was 1.4.2.19 and 1.5.17
I checked the database: The structure is created but the tables are not created. As the user 'sa' has full admin rights it must be with the access path to the database that is wrong. What I do not understand is, why the installation routine is able to connect to the database to create B1i and then unable to create the tables. I checked in the log files of the db and found no error messages. I tested this as well by using a wrong password for sa or a wrong user. In both cases, the installation routine fails already when checing the existence of B1i database
[Update]
In the meantime:
Checked permissions on database
Checked that administrator is member of local admin group
Checked JAVA_HOME environment variable
Found collation SQL_Latin1_General_CP1_CI_AS for working setup and SQL_Latin1_General_CP1_CS_AS in failing setup
Checked all security settings by comparing to working setup
Checked event viewer and found no errors
Checked all log files and found no errors
Checked that sa can create tables manually in localhost\B1i
Ciao, Mathias
Edited by: Mathias Wilhelm on Feb 12, 2009 2:36 PM -
IPC 4.0 Standalone with SQL 2005 Express as a database
Hello,
I am trying to setup IPC 4.0 standalone up for a training class on a XP laptop with SQL 2005 Express as the database. I keep getting login errors connecting the IPC admin.bat tool to the sql database. And yes, I know this is not 'officially' supported by SAP, but I see no technical reason why it shouldn't work and yes my port is correct. My entries are as such:
Alias: 00_230
Server: localhost
System: Microsoft SQL Server
Database Name: 00_230
port: 1433
User: ipc
password: hidden
client: 230
Is everything I entered correct? Am I missing anything that I need?
Thanks!Hi Jeff.
You will probably have problems with the database subsystem, when you upgrade to UccX7.0.1 if the 3rd party database is af SQL2k5 server.
There is a fix for that problem, check below :
Upgrading UCCX to 7.0(1)Sr4 is failing ODBC connection to SQL 2005.
Symptom:
Upgrading the UCCX server to 7.0(1) Sr4 and OS to 2003.1.4a SR11 is failing the ODBC connection to SQL 2005 external database. (also a problem in new installations)
The error generated when trying to setup a ODBC connection to SQL 2005 database is
======
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
=======
Conditions:
Upgrade to UCCX 7.0(1) Sr3 or 4 and OS upgrade to 2003.1.4a SR11
Workaround:
Work around:
a) In UCCX SQL Server 2000 - Start the Client Network Utility. (cliconfg.exe is used from MSDE versions of UccX)
b) On the General tab, add TCP/IP in the list under Enabled protocols by order. (make sure its first)
c) Click the Alias tab, and then click Add. Under Network libraries, select TCP/IP.
d) In the Server name text box, type the IP address of the server that is running SQL Server
2005.
Note:
If port other that 1433 is being used Click the check box to clear the Dynamically determine port option, and then type the port number of the instance of SQL Server 2005 in the Port number text box.
Regards
\Søren Lavard -
I am currently installing ESM and was wondering if SQL 2005 Express can be
used or does it require the full version of SQL 2005?
Thanks,
RonRon,
While it may work, SQL 2005 Express is not supported. Standard or Enterprise Edition is required. See the Installation Guide for details of requirements before installing:
http://www.novell.com/documentation/.../bookinfo.html
Good luck,
Daniel
>>>
From: Ron Friesen<[email protected]>
To:novell.support.zenworks.endpoint-security-management
Date: 11/25/2008 4:29 PM
Subject: ESM - SQL 2005 Express
I am currently installing ESM and was wondering if SQL 2005 Express can be
used or does it require the full version of SQL 2005?
Thanks,
Ron -
Providing configuration file for SQL 2012 Express installation which installing HPC 2012 R2
Hi guys,
I need to know if there is any way to provide configuration file for SQL 2012 Express installation which installing HPC 2012 R2?
I am scripting installation on HPC 2012 R2 with default SQL 2012 Express edition but I am not able to find any option to provide a configuation file for SQL 2012 Express installaiton.
Thanks,
Vivs.Hi Vivs,
As my understanding, you want to generate a configuration file and install SQL Server 2012 express edition using that configuration file.
If that is the case, firstly, you could generate the configuration file following the steps below since express edition is run in AutoAdvance mode which skips "Ready to Install" page.
1.Double-click SQL Server installation file in your local drive, you will see that the file will be extracted to a temporary folder. Please make a note of what directory it is extracted to. For example, it could be in c:\ followed by a folder name which
will be a set of random letters and numbers "gy7h8hjhhj67rfs7".
2.Cancel installation. Then click on the Start button on the task bar, click run, type the command cmd.exe, and go to that directory via cmd.
3.Execute the following command: setup.exe /ACTION=INSTALL /UIMODE=Normal
4.Follow the wizard through to the 'Ready to Install' page. The path to the configuration file is specified in the 'Ready to Install' page in the configuration file path section.
5.Cancel the setup without actually completing the installation, to generate the INI file.
Secondly, to install SQL Server using Command Prompt, go to the SQL Server installation media root (the temporary folder) from the command prompt and specify the ConfigurationFile.ini as a parameter as shown below.
Setup.exe /ConfigurationFile=ConfigurationFile.INI
For more information about the process, please refer to the article:
http://www.mssqltips.com/sqlservertip/2511/standardize-sql-server-installations-with-configuration-files/
Regards,
Michelle Li -
SQL 2005 Setup on Win7 Ultimate [No SQL Services after installation]
Win 7 Ultimate (64bit)
4GB RAM
New installation of Win 7 Ultimate
Re-installation of SQL: Originally SQLExpress which didn't work out so I went to SQL2005 Standard Edition SP1 & updated to SQL2005 SP4. I installed Visual Studio 2005 during the SP1 installation. Actually, I installed all SQL2005 components
'just in case'.
I had attempted, unsuccessfully, to install SQLExpress so I uninstalled all SQLExpress components via Programs and Features, removed all SQL related directories and subdirectories in c:\Program Files (x86)\SQL.... and started the DVD setup.exe installation.
[I didn't do a RegEdit32!]
Uniquely, During installation of SQL2005, I wasn't asked for the SQL Product Key nor whether the mode was Windows or Mixed (I want Mixed Mode). Now, after rebooting with all MS updates (Win7 and SQL2005) I don't see any SQL services even though the
Microsoft SQL Server 2005, Backward compatibility and Books etc are listed as installed under Programs and Features. IIRC, I saw a message regarding ASP.Net for 64bit being installed but some issues on the 32bit not being installed (warning message).
So, how do I get the necessary SQL 2005 services installed and get SQL functional??? I'm open to a complete re-install if necessary. My original DVD is SQL2005 Standard Edition SP1, fyi.
THANKS!1) SQL Server Configuration Manager? Yes, I do under "Configuration Tools" When selecting this and going into SQL Server 2005 Services I get "There are no items to show in this view".
2) Exact SQL Server edition? From Help of SQL Server Configuration Manager: 2005.090.5000.00
3) Compact Edition installed? I used the SQL2005 SP1 Standard Edition DVD and then selected setup.exe. If you'd like for me to uninstall SQL and reinstall I will (including removing appropriate SQL Server directories). I'd remove the RegEdit
entries but I don't know where/what they are. [[Note!: See #4 below where under Server Type I see "SQL Server Compact Edition ... as well as Database Engine, Analysis Services, Reporting Services and Integration Services]
4) ??: Since I can't get into SQL Server Management Studio. I get "Cannot connect to XYZ02" "A network-related or instance specific error occurred while establishing a connection to SQL server. The server was not found or was not accessible.
Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (Provider: Named Pipes Provider, error:40- Could not open a connection to SQL server) (Microsoft SQL server, Error:2)" [Note: XYZ02 is the name
of the laptop and I used: Server Type: Database Engine; Server Name: XYZ02 (I had to enter as it wasn't listed); Authentication: Windows Authentication
So, suggestions... looks like I DO have Compact Edition? Thoughts?????
Thanks
BTW, I have another 64bit laptop (same mfr/model but with 8GB vs this 4GB under 64bit Win7 Ultimate) that runs SQL fine. Been running SQL 2005 on it for 3-4+ years. -
SAP IDES ECC5.0 (SQL 2005 Database) installation Error at Database instan.
At the time IDES ECC 5.0 installation (SQL 2005 database), I was copy all DVD on Hard drive and start setup then at installation of database instance, following Errors are occured. so I cant continue with the installation, if anyone have installation guide/or solve the following error please mail me at [email protected]
from Log file SAPCLUST
Interface access functions from dynamic library dbmssslib.dll loaded.myCluster
(3.5.Imp): 613: error when retrieving table description for physical table AABLG.
myCluster (3.5.Imp): 614: return code received from nametab is 32
myCluster (3.5.Imp): 296: error when retrieving physical nametab for table AABLG.
(CNV) ERROR: code page conversion failed
rc = 2
from sappool.log
Interface access functions from dynamic library dbmssslib.dll loaded.failed to read short nametab of table ARCH_NUM (rc=32)conversion failed for row 0 of table VARKEY = ⁘
(CNV) ERROR: code page conversion failed
So please send me solution/ or any configuration need for SQL 2005 / installation guide thanksThis may be hard disk problem, some file not able to write on HDD.
Regards
Rajnish -
Visual Studio prevents SQL 2008 Express installation on win 8.1
I wanted to install SQL Express 2008 on my Win 8.1 desktop. It gives an error indicating that I should install Visual Studio 2008 SP1 first. I tried, but SP1 installation fails. I also tried to remove VS2008 completely but I still get the same fail when
installing SQL 2008 Express.
Now I cannot even install SQL Manager 2008, to manage database on SQL server.Hello,
You should install SQL Server 2008 Express with SP3 included to make it compatible with Windows 8.1. Please try the following download:
http://www.microsoft.com/en-us/download/details.aspx?id=27597
For more information, please read the following article:
http://support.microsoft.com/kb/2681562
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
SQL 2005 Patch installation fail
Hi all
I am having error on installing KB2716429... currently the SQL server is build no. 9.0.5057
here following is the error
11/30/2013 09:46:45.484 ================================================================================
11/30/2013 09:46:45.484 Hotfix package launched
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:45.500 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:45.500 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:45.515 Local Computer:
11/30/2013 09:46:45.515 Target Details: SV53704
11/30/2013 09:46:45.515 commonfilesdir = C:\Program Files\Common Files
11/30/2013 09:46:45.515 lcidsupportdir = e:\6ce33de16cc8ba67b3e41388bb\1033
11/30/2013 09:46:45.515 programfilesdir = C:\Program Files
11/30/2013 09:46:45.515 programfilesdir_wow = C:\Program Files
11/30/2013 09:46:45.515 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 supportdirlocal = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:45.515 windir = C:\WINDOWS
11/30/2013 09:46:45.515 winsysdir = C:\WINDOWS\system32
11/30/2013 09:46:45.515 winsysdir_wow = C:\WINDOWS\SysWOW64
11/30/2013 09:46:45.515
11/30/2013 09:46:45.531 Enumerating applicable products for this patch
11/30/2013 09:46:45.531 Found SQL 2005 product definition
11/30/2013 09:46:45.531 Warning: Product HotFixSQL is missing LCID value
11/30/2013 09:46:46.953 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:46.969 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:46.969 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:46.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:46.984 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:46.984 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:46.984 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:46.984 Command-line instance name check completed during the install process
11/30/2013 09:46:46.984 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:47.000 Baseline build check completed during the install process
11/30/2013 09:46:47.000 Found OLAP Server 2005 product definition
11/30/2013 09:46:47.000 Warning: Product HotFixAS is missing LCID value
11/30/2013 09:46:48.453 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:48.453 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:48.453 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\\Bin\msmdsrv.exe
11/30/2013 09:46:48.453 Enumeration: No GDR branch Hotfix found for product instance MSSQLSERVER
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:48.469 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:48.469 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:48.469 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.469 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:48.484 Command-line instance name check completed during the install process
11/30/2013 09:46:48.484 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:48.484 Baseline build check completed during the install process
11/30/2013 09:46:48.484 Found Notification Services 2005 product definition
11/30/2013 09:46:48.484 Warning: Product HotFixNS is missing LCID value
11/30/2013 09:46:50.015 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:50.047 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:50.062 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:50.062 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\\Bin\nsservice.exe
11/30/2013 09:46:50.062 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.062 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:50.062 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:50.078 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:50.078 Product discovery completed during the install process for NS
11/30/2013 09:46:50.078 SP Level check completed during the install process for NS
11/30/2013 09:46:50.078 Product language check completed during the install process for NS
11/30/2013 09:46:50.078 Product version check completed during the install process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the installation process for NS
11/30/2013 09:46:50.078 Baseline build check completed during the install process
11/30/2013 09:46:50.078 Found Report Server 2005 product definition
11/30/2013 09:46:50.109 Warning: Product HotFixRS is missing LCID value
11/30/2013 09:46:51.687 Enumeration: Determining QFE level for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following QFE level for product instance MSSQLSERVER: 5057
11/30/2013 09:46:51.703 Enumeration: Determining GDR branching Hotfix for product instance MSSQLSERVER
11/30/2013 09:46:51.703 Enumeration: Associated hotfix build information not found for the following file: C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\\ReportServer\bin\ReportingServicesService.exe
11/30/2013 09:46:51.703 Enumeration: Found following GDR branch hotfix for product instance MSSQLSERVER: 5292
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:51.703 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:51.703 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:51.703 Product discovery completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 SP Level check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product language check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.703 Product version check completed during the install process for MSSQLSERVER
11/30/2013 09:46:51.719 Command-line instance name check completed during the install process
11/30/2013 09:46:51.750 Baseline build check completed during the installation process for MSSQLSERVER
11/30/2013 09:46:51.750 Baseline build check completed during the install process
11/30/2013 09:46:51.765 Found DTS 2005 product definition
11/30/2013 09:46:51.765 Warning: Product HotFixDTS is missing LCID value
11/30/2013 09:46:53.359 Enumeration: Determining QFE level for product instance
11/30/2013 09:46:53.375 Enumeration: Found following QFE level for product instance : 5057
11/30/2013 09:46:53.375 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:53.375 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:53.375 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:53.375 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:53.375 Product discovery completed during the install process for Integration Services
11/30/2013 09:46:53.375 SP Level check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product language check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Product version check completed during the install process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the installation process for Integration Services
11/30/2013 09:46:53.375 Baseline build check completed during the install process
11/30/2013 09:46:53.390 Found SQL 2005 Tools product definition
11/30/2013 09:46:53.390 Warning: Product HotFixTools is missing LCID value
11/30/2013 09:46:54.953 Enumeration: Determining GDR branching Hotfix for product instance
11/30/2013 09:46:54.969 Enumeration: Found following GDR branch hotfix for product instance : 5292
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "CommonFilesDir", string value = C:\Program Files\Common Files
11/30/2013 09:46:54.969 Registry: Opened registry key "SOFTWARE\Microsoft\Windows\CurrentVersion"
11/30/2013 09:46:54.969 Registry: Read registry key value "ProgramFilesDir", string value = C:\Program Files
11/30/2013 09:46:54.969 Product discovery completed during the install process for SQL Tools
11/30/2013 09:46:54.969 SP Level check completed during the install process for SQL Tools
11/30/2013 09:46:54.969 Product language check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Product version check completed during the install process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the installation process for SQL Tools
11/30/2013 09:46:54.984 Baseline build check completed during the install process
11/30/2013 09:46:55.031 Product Enumeration Results:
11/30/2013 09:46:55.031 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL.inf
11/30/2013 09:46:55.031 arpfolder = SQL9_KB2716429_ENU
11/30/2013 09:46:55.031 associatedhotfixbuild = 5320
11/30/2013 09:46:55.031 baselinebuild = 5000
11/30/2013 09:46:55.031 baselinebuildmax = 5069
11/30/2013 09:46:55.031 build = 5069
11/30/2013 09:46:55.031 description = SQL Server Database Services 2005
11/30/2013 09:46:55.031 details = Patch for SQL Server Database Services 2005
11/30/2013 09:46:55.031 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.031 kbarticle = KB2716429
11/30/2013 09:46:55.031 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.031 legalproductname = SQL Server Database Services 2005
11/30/2013 09:46:55.031 machinetype = x86
11/30/2013 09:46:55.031 package = HotFixSQL
11/30/2013 09:46:55.031 packagetype = GDR
11/30/2013 09:46:55.031 productname = SQL9
11/30/2013 09:46:55.047 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.047 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.047 splevel = 4
11/30/2013 09:46:55.047 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.047 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.047 version = 9
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 File Group Details: MSP
11/30/2013 09:46:55.047 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.047 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.047 File Details: sqlrun_sql.msp
11/30/2013 09:46:55.047
11/30/2013 09:46:55.047 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.047 agentservicename = SQLSERVERAGENT
11/30/2013 09:46:55.047 associatedhotfixbuild = 5292
11/30/2013 09:46:55.047 clustername =
11/30/2013 09:46:55.047 default = TRUE
11/30/2013 09:46:55.047 ftsservicename = MSFTESQL
11/30/2013 09:46:55.047 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.047 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.1
11/30/2013 09:46:55.047 id = MSSQL.1
11/30/2013 09:46:55.062 installsqldatadir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL
11/30/2013 09:46:55.062 lcid = 1033
11/30/2013 09:46:55.062 name = MSSQLSERVER
11/30/2013 09:46:55.062 productcode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}
11/30/2013 09:46:55.062 qfelevel = 5057
11/30/2013 09:46:55.062 servicename = MSSQLServer
11/30/2013 09:46:55.062 sku = STANDARD
11/30/2013 09:46:55.062 sp = 4
11/30/2013 09:46:55.094 type = SQL Server Standalone Product
11/30/2013 09:46:55.094 vermajbld = 5000
11/30/2013 09:46:55.094 version = 9
11/30/2013 09:46:55.109
11/30/2013 09:46:55.125 Product Enumeration Results:
11/30/2013 09:46:55.140 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS.inf
11/30/2013 09:46:55.140 arpfolder = OLAP9_KB2716429_ENU
11/30/2013 09:46:55.140 associatedhotfixbuild = 5320
11/30/2013 09:46:55.140 baselinebuild = 5000
11/30/2013 09:46:55.140 baselinebuildmax = 5069
11/30/2013 09:46:55.140 build = 5069
11/30/2013 09:46:55.140 description = SQL Server Analysis Services 2005
11/30/2013 09:46:55.140 details = Patch for Analysis Services 2005
11/30/2013 09:46:55.140 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.140 kbarticle = KB2716429
11/30/2013 09:46:55.140 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.140 legalproductname = SQL Server Analysis Services 2005
11/30/2013 09:46:55.156 machinetype = x86
11/30/2013 09:46:55.156 package = HotFixAS
11/30/2013 09:46:55.156 packagetype = GDR
11/30/2013 09:46:55.156 productname = OLAP9
11/30/2013 09:46:55.156 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.156 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.156 splevel = 4
11/30/2013 09:46:55.156 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.156 validateauthentication = true
11/30/2013 09:46:55.156 version = 9
11/30/2013 09:46:55.156
11/30/2013 09:46:55.156 File Group Details: MSP
11/30/2013 09:46:55.156 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.156 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.172 File Details: sqlrun_as.msp
11/30/2013 09:46:55.172
11/30/2013 09:46:55.172 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.172 associatedhotfixbuild = 1520
11/30/2013 09:46:55.172 clustername =
11/30/2013 09:46:55.187 default = TRUE
11/30/2013 09:46:55.203 fullversion = 2005.090.5057.00
11/30/2013 09:46:55.219 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.2
11/30/2013 09:46:55.219 id = MSSQL.2
11/30/2013 09:46:55.219 installsqldatadir = C:\Program Files\Microsoft SQL Server\
11/30/2013 09:46:55.234 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\
11/30/2013 09:46:55.250 lcid = 1033
11/30/2013 09:46:55.265 name = MSSQLSERVER
11/30/2013 09:46:55.297 olapservicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 productcode = {8ABF8FEB-ABB0-40DC-9945-85AF36EF30A9}
11/30/2013 09:46:55.297 qfelevel = 5057
11/30/2013 09:46:55.297 servicename = MSSQLServerOLAPService
11/30/2013 09:46:55.297 sku = STANDARD
11/30/2013 09:46:55.297 sp = 4
11/30/2013 09:46:55.297 type = Olap Standalone Product
11/30/2013 09:46:55.297 vermajbld = 5000
11/30/2013 09:46:55.297 version = 9
11/30/2013 09:46:55.297
11/30/2013 09:46:55.297 Product Enumeration Results:
11/30/2013 09:46:55.297 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS.inf
11/30/2013 09:46:55.297 arpfolder = NS9_KB2716429_ENU
11/30/2013 09:46:55.297 associatedhotfixbuild = 5320
11/30/2013 09:46:55.297 baselinebuild = 5000
11/30/2013 09:46:55.297 baselinebuildmax = 5069
11/30/2013 09:46:55.297 build = 5069
11/30/2013 09:46:55.297 description = SQL Server Notification Services 2005
11/30/2013 09:46:55.297 details = Patch for SQL Server Notification Services 2005
11/30/2013 09:46:55.297 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.312 kbarticle = KB2716429
11/30/2013 09:46:55.312 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.312 legalproductname = SQL Server Notification Services 2005 instances
11/30/2013 09:46:55.312 machinetype = x86
11/30/2013 09:46:55.312 package = HotFixNS
11/30/2013 09:46:55.312 packagetype = GDR
11/30/2013 09:46:55.312 productname = NS9
11/30/2013 09:46:55.312 recommendinstall = 1
11/30/2013 09:46:55.312 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.312 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.312 splevel = 4
11/30/2013 09:46:55.312 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.312 validateauthentication = true
11/30/2013 09:46:55.312 version = 9
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 File Group Details: MSP
11/30/2013 09:46:55.312 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.312 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.312 File Details: sqlrun_ns.msp
11/30/2013 09:46:55.312
11/30/2013 09:46:55.312 Instance Details: NS
11/30/2013 09:46:55.312 associatedhotfixbuild = 5292
11/30/2013 09:46:55.328 clustername =
11/30/2013 09:46:55.328 fullversion = 9.00.5057.00
11/30/2013 09:46:55.328 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\NS
11/30/2013 09:46:55.328 id =
11/30/2013 09:46:55.328 installsqldatadir =
11/30/2013 09:46:55.328 installsqldir = C:\Program Files\Microsoft SQL Server\90\NotificationServices\9.0.242\
11/30/2013 09:46:55.328 lcid = 1033
11/30/2013 09:46:55.328 name =
11/30/2013 09:46:55.375 productcode = {37E9AD9F-3217-4229-B5A5-7A0C82364C6C}
11/30/2013 09:46:55.390 qfelevel = 5057
11/30/2013 09:46:55.406 sku = STANDARD
11/30/2013 09:46:55.406 sp = 4
11/30/2013 09:46:55.406 type = Tools Only
11/30/2013 09:46:55.406 vermajbld = 5000
11/30/2013 09:46:55.422 version = 9
11/30/2013 09:46:55.422
11/30/2013 09:46:55.422 Product Enumeration Results:
11/30/2013 09:46:55.422 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS.inf
11/30/2013 09:46:55.422 arpfolder = RS9_KB2716429_ENU
11/30/2013 09:46:55.422 associatedhotfixbuild = 5320
11/30/2013 09:46:55.422 baselinebuild = 5000
11/30/2013 09:46:55.422 baselinebuildmax = 5069
11/30/2013 09:46:55.422 build = 5069
11/30/2013 09:46:55.453 description = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 details = Patch for SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.453 kbarticle = KB2716429
11/30/2013 09:46:55.453 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.453 legalproductname = SQL Server Reporting Services 2005
11/30/2013 09:46:55.453 machinetype = x86
11/30/2013 09:46:55.453 package = HotFixRS
11/30/2013 09:46:55.453 packagetype = GDR
11/30/2013 09:46:55.453 productname = RS9
11/30/2013 09:46:55.469 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.469 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.469 splevel = 4
11/30/2013 09:46:55.469 sqlutility = sqlcmd.exe
11/30/2013 09:46:55.469 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.469 validateauthentication = true
11/30/2013 09:46:55.469 version = 9
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 File Group Details: MSP
11/30/2013 09:46:55.469 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.469 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.469 File Details: sqlrun_rs.msp
11/30/2013 09:46:55.469
11/30/2013 09:46:55.469 Instance Details: MSSQLSERVER
11/30/2013 09:46:55.469 associatedhotfixbuild = 5292
11/30/2013 09:46:55.469 clustername =
11/30/2013 09:46:55.469 default = TRUE
11/30/2013 09:46:55.469 fullversion = 9.00.5057.00
11/30/2013 09:46:55.469 hiveregpath = Software\Microsoft\Microsoft SQL Server\MSSQL.3
11/30/2013 09:46:55.469 id = MSSQL.3
11/30/2013 09:46:55.469 installsqldatadir =
11/30/2013 09:46:55.469 installsqldir = C:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\
11/30/2013 09:46:55.484 lcid = 1033
11/30/2013 09:46:55.484 name = MSSQLSERVER
11/30/2013 09:46:55.484 productcode = {E930E839-998E-42F9-97E2-71FC960DB1B7}
11/30/2013 09:46:55.484 qfelevel = 5057
11/30/2013 09:46:55.484 rsservicename = ReportServer
11/30/2013 09:46:55.484 servicename =
11/30/2013 09:46:55.484 sku = STANDARD
11/30/2013 09:46:55.484 sp = 4
11/30/2013 09:46:55.484 type = Report Server Standalone Product
11/30/2013 09:46:55.484 vermajbld = 5000
11/30/2013 09:46:55.484 version = 9
11/30/2013 09:46:55.484
11/30/2013 09:46:55.484 Product Enumeration Results:
11/30/2013 09:46:55.484 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS.inf
11/30/2013 09:46:55.500 arpfolder = DTS9_KB2716429_ENU
11/30/2013 09:46:55.625 associatedhotfixbuild = 5320
11/30/2013 09:46:55.625 baselinebuild = 5000
11/30/2013 09:46:55.625 baselinebuildmax = 5069
11/30/2013 09:46:55.625 build = 5069
11/30/2013 09:46:55.625 description = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 details = Patch for SQL Server Integration Services 2005
11/30/2013 09:46:55.625 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.625 kbarticle = KB2716429
11/30/2013 09:46:55.625 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.625 legalproductname = SQL Server Integration Services 2005
11/30/2013 09:46:55.625 machinetype = x86
11/30/2013 09:46:55.640 package = HotFixDTS
11/30/2013 09:46:55.640 packagetype = GDR
11/30/2013 09:46:55.640 productname = DTS9
11/30/2013 09:46:55.640 recommendinstall = 1
11/30/2013 09:46:55.640 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.640 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.640 splevel = 4
11/30/2013 09:46:55.640 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.640 version = 9
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 File Group Details: MSP
11/30/2013 09:46:55.640 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.640 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.640 File Details: sqlrun_dts.msp
11/30/2013 09:46:55.640
11/30/2013 09:46:55.640 Instance Details: Integration Services
11/30/2013 09:46:55.640 associatedhotfixbuild = 5292
11/30/2013 09:46:55.640 clustername =
11/30/2013 09:46:55.640 dtsservicename = MsDtsServer
11/30/2013 09:46:55.640 fullversion = 9.00.5057.00
11/30/2013 09:46:55.656 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\DTS
11/30/2013 09:46:55.656 id =
11/30/2013 09:46:55.656 installsqldatadir =
11/30/2013 09:46:55.656 installsqldir = C:\Program Files\Microsoft SQL Server\90\DTS\
11/30/2013 09:46:55.656 lcid = 1033
11/30/2013 09:46:55.656 name =
11/30/2013 09:46:55.656 productcode = {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
11/30/2013 09:46:55.656 qfelevel = 5057
11/30/2013 09:46:55.656 servicename = MsDtsServer
11/30/2013 09:46:55.656 sku = STANDARD
11/30/2013 09:46:55.656 sp = 4
11/30/2013 09:46:55.656 type = Tools Only
11/30/2013 09:46:55.656 vermajbld = 5000
11/30/2013 09:46:55.656 version = 9
11/30/2013 09:46:55.656
11/30/2013 09:46:55.656 Product Enumeration Results:
11/30/2013 09:46:55.672 INF File Name: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools.inf
11/30/2013 09:46:55.672 arpfolder = SQLTools9_KB2716429_ENU
11/30/2013 09:46:55.672 associatedhotfixbuild = 5320
11/30/2013 09:46:55.672 baselinebuild = 5000
11/30/2013 09:46:55.672 baselinebuildmax = 5069
11/30/2013 09:46:55.672 build = 5069
11/30/2013 09:46:55.672 description = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 details = Patch for SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 installerlogpath = <PROGRAMFILESDIR>\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
11/30/2013 09:46:55.672 kbarticle = KB2716429
11/30/2013 09:46:55.672 kbarticlehyperlink =
http://support.microsoft.com/?kbid=2716429
11/30/2013 09:46:55.672 legalproductname = SQL Server Tools and Workstation Components 2005
11/30/2013 09:46:55.672 machinetype = x86
11/30/2013 09:46:55.672 package = HotFixTools
11/30/2013 09:46:55.672 packagetype = GDR
11/30/2013 09:46:55.672 productname = SQLTools9
11/30/2013 09:46:55.672 recommendinstall = 1
11/30/2013 09:46:55.672 relatedlinks = <LCIDSUPPORTDIR>\FinalSQL2005Information.rtf
11/30/2013 09:46:55.672 servicepackname = Microsoft SQL Server 2005 Service Pack 4 Cumulative Hotfix 5069
11/30/2013 09:46:55.672 splevel = 4
11/30/2013 09:46:55.672 supportdir = e:\6ce33de16cc8ba67b3e41388bb
11/30/2013 09:46:55.687 version = 9
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 File Group Details: MSP
11/30/2013 09:46:55.687 parameters = SQLBUILD=5069 KBNUMBER=KB2716429 REBOOT=ReallySuppress
11/30/2013 09:46:55.687 sourcepath = <SUPPORTDIR>\<PACKAGE>\Files
11/30/2013 09:46:55.687 File Details: sqlrun_tools.msp
11/30/2013 09:46:55.687
11/30/2013 09:46:55.687 Instance Details: SQL Tools
11/30/2013 09:46:55.687 associatedhotfixbuild = 5292
11/30/2013 09:46:55.687 clustername =
11/30/2013 09:46:55.687 fullversion = 9.4.5057
11/30/2013 09:46:55.687 hiveregpath = Software\Microsoft\Microsoft SQL Server\90\Tools
11/30/2013 09:46:55.687 id =
11/30/2013 09:46:55.687 installsqldatadir =
11/30/2013 09:46:55.687 installsqldir = C:\Program Files\Microsoft SQL Server\90\Tools\
11/30/2013 09:46:55.687 lcid = 1033
11/30/2013 09:46:55.687 name =
11/30/2013 09:46:55.687 productcode = {1DD463C0-A50A-4394-B7E4-5895C02F9E0D}
11/30/2013 09:46:55.687 qfelevel = 5057
11/30/2013 09:46:55.687 sku = STANDARD
11/30/2013 09:46:55.687 sp = 4
11/30/2013 09:46:55.687 type = Tools Only
11/30/2013 09:46:55.703 vermajbld = 5000
11/30/2013 09:46:55.703 version = 9
11/30/2013 09:46:55.703
11/30/2013 09:47:00.781 Registry: Opened registry key "System\CurrentControlSet\Control\Session Manager"
11/30/2013 09:47:00.781 Registry: Cannot read registry key value "PendingFileRenameOperations", error 0
11/30/2013 09:47:00.812 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:00.828 Registry: Read registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "EnableErrorReporting", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.703 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.719 Registry: Set registry key value "CustomerFeedBack", DWORD value = 0
11/30/2013 09:47:01.734 Locked file: Checking for locked files
11/30/2013 09:47:04.328 Attempting to pause the 32 bit ngen queue
11/30/2013 09:47:04.968 Installing product: SQL9
11/30/2013 09:47:05.781 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:05.781 Installing instance: MSSQLSERVER
11/30/2013 09:47:05.812 Installing target: SV53704
11/30/2013 09:47:05.828 Installing file: sqlrun_sql.msp
11/30/2013 09:47:05.828 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716429_sqlrun_sql.msp.log
11/30/2013 09:47:05.828 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:05.828 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.203 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:06.203 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:06.203 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:06.218 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixSQL\Files\sqlrun_sql.msp
11/30/2013 09:47:06.218 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:06.218 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:06.640 Watson: Param1 = Unknown
11/30/2013 09:47:06.640 Watson: Param2 = 0x66e
11/30/2013 09:47:06.640 Watson: Param3 = Unknown
11/30/2013 09:47:06.640 Watson: Param4 = 0x66e
11/30/2013 09:47:06.656 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:06.656 Watson: Param6 = Unknown
11/30/2013 09:47:06.656 Watson: Param7 = SQL9
11/30/2013 09:47:06.656 Watson: Param8 = @
11/30/2013 09:47:06.656 Watson: Param9 = x86
11/30/2013 09:47:06.656 Watson: Param10 = 5069
11/30/2013 09:47:06.656 Installed product: SQL9
11/30/2013 09:47:06.656 Installing product: OLAP9
11/30/2013 09:47:07.468 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:07.484 Installing instance: MSSQLSERVER
11/30/2013 09:47:07.484 Installing target: SV53704
11/30/2013 09:47:07.500 Installing file: sqlrun_as.msp
11/30/2013 09:47:07.500 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\OLAP9_Hotfix_KB2716429_sqlrun_as.msp.log
11/30/2013 09:47:07.515 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.515 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.640 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:07.640 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:07.640 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:07.656 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixAS\Files\sqlrun_as.msp
11/30/2013 09:47:07.656 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:07.656 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:08.078 Watson: Param1 = Unknown
11/30/2013 09:47:08.078 Watson: Param2 = 0x66e
11/30/2013 09:47:08.078 Watson: Param3 = Unknown
11/30/2013 09:47:08.078 Watson: Param4 = 0x66e
11/30/2013 09:47:08.078 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:08.078 Watson: Param6 = Unknown
11/30/2013 09:47:08.078 Watson: Param7 = OLAP9
11/30/2013 09:47:08.078 Watson: Param8 = @
11/30/2013 09:47:08.078 Watson: Param9 = x86
11/30/2013 09:47:08.078 Watson: Param10 = 5069
11/30/2013 09:47:08.078 Installed product: OLAP9
11/30/2013 09:47:08.078 Installing product: RS9
11/30/2013 09:47:08.875 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:08.875 Installing instance: MSSQLSERVER
11/30/2013 09:47:08.890 Installing target: SV53704
11/30/2013 09:47:08.890 Installing file: sqlrun_rs.msp
11/30/2013 09:47:08.890 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\RS9_Hotfix_KB2716429_sqlrun_rs.msp.log
11/30/2013 09:47:08.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:08.890 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.015 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:09.015 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:09.015 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:09.031 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixRS\Files\sqlrun_rs.msp
11/30/2013 09:47:09.047 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:09.047 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:09.593 Watson: Param1 = Unknown
11/30/2013 09:47:09.593 Watson: Param2 = 0x66e
11/30/2013 09:47:09.593 Watson: Param3 = Unknown
11/30/2013 09:47:09.609 Watson: Param4 = 0x66e
11/30/2013 09:47:09.609 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:09.609 Watson: Param6 = Unknown
11/30/2013 09:47:09.609 Watson: Param7 = RS9
11/30/2013 09:47:09.609 Watson: Param8 = @
11/30/2013 09:47:09.609 Watson: Param9 = x86
11/30/2013 09:47:09.609 Watson: Param10 = 5069
11/30/2013 09:47:09.625 Installed product: RS9
11/30/2013 09:47:09.625 Installing product: NS9
11/30/2013 09:47:10.406 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:10.406 Installing instance: NS
11/30/2013 09:47:10.422 Installing target: SV53704
11/30/2013 09:47:10.422 Installing file: sqlrun_ns.msp
11/30/2013 09:47:10.422 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB2716429_sqlrun_ns.msp.log
11/30/2013 09:47:10.422 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.422 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.531 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:10.531 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:10.531 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:10.547 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixNS\Files\sqlrun_ns.msp
11/30/2013 09:47:10.547 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:10.547 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:10.890 Watson: Param1 = Unknown
11/30/2013 09:47:10.890 Watson: Param2 = 0x66e
11/30/2013 09:47:10.890 Watson: Param3 = Unknown
11/30/2013 09:47:10.890 Watson: Param4 = 0x66e
11/30/2013 09:47:10.890 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:10.890 Watson: Param6 = Unknown
11/30/2013 09:47:10.890 Watson: Param7 = NS9
11/30/2013 09:47:10.890 Watson: Param8 = @
11/30/2013 09:47:10.890 Watson: Param9 = x86
11/30/2013 09:47:10.890 Watson: Param10 = 5069
11/30/2013 09:47:10.890 Installed product: NS9
11/30/2013 09:47:10.890 Installing product: DTS9
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:11.703 Installing instance: Integration Services
11/30/2013 09:47:11.703 Installing target: SV53704
11/30/2013 09:47:11.703 Installing file: sqlrun_dts.msp
11/30/2013 09:47:11.703 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log
11/30/2013 09:47:11.703 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.718 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.890 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:11.890 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:11.906 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:11.906 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixDTS\Files\sqlrun_dts.msp
11/30/2013 09:47:11.922 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:11.922 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:12.328 Watson: Param1 = Unknown
11/30/2013 09:47:12.328 Watson: Param2 = 0x66e
11/30/2013 09:47:12.328 Watson: Param3 = Unknown
11/30/2013 09:47:12.328 Watson: Param4 = 0x66e
11/30/2013 09:47:12.328 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:12.328 Watson: Param6 = Unknown
11/30/2013 09:47:12.328 Watson: Param7 = DTS9
11/30/2013 09:47:12.328 Watson: Param8 = @
11/30/2013 09:47:12.328 Watson: Param9 = x86
11/30/2013 09:47:12.328 Watson: Param10 = 5069
11/30/2013 09:47:12.343 Installed product: DTS9
11/30/2013 09:47:12.343 Installing product: SQLTools9
11/30/2013 09:47:13.125 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
11/30/2013 09:47:13.140 Installing instance: SQL Tools
11/30/2013 09:47:13.140 Installing target: SV53704
11/30/2013 09:47:13.156 Installing file: sqlrun_tools.msp
11/30/2013 09:47:13.172 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQLTools9_Hotfix_KB2716429_sqlrun_tools.msp.log
11/30/2013 09:47:13.172 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.172 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.484 MSP returned 1646: The patch package is not a removable patch package. Available beginning with Windows Installer version 3.0.
11/30/2013 09:47:13.484 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
11/30/2013 09:47:13.484 Registry: Cannot read registry key value "Debug", error 0
11/30/2013 09:47:13.500 Copy Engine: Error, unable to install MSP file: e:\6ce33de16cc8ba67b3e41388bb\HotFixTools\Files\sqlrun_tools.msp
11/30/2013 09:47:13.500 The following exception occurred: Unable to install Windows Installer MSP file Date: 11/30/2013 09:47:13.500 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 807
11/30/2013 09:47:13.828 Watson: Param1 = Unknown
11/30/2013 09:47:13.828 Watson: Param2 = 0x66e
11/30/2013 09:47:13.843 Watson: Param3 = Unknown
11/30/2013 09:47:13.843 Watson: Param4 = 0x66e
11/30/2013 09:47:13.843 Watson: Param5 = copyengine.cpp@807
11/30/2013 09:47:13.843 Watson: Param6 = Unknown
11/30/2013 09:47:13.843 Watson: Param7 = SQLTools9
11/30/2013 09:47:13.843 Watson: Param8 = @
11/30/2013 09:47:13.843 Watson: Param9 = x86
11/30/2013 09:47:13.843 Watson: Param10 = 5069
11/30/2013 09:47:13.843 Installed product: SQLTools9
11/30/2013 09:47:13.843 Hotfix package completed
11/30/2013 09:47:13.859 Attempting to continue the 32 bit ngen queueHi ~ any idea on this case ? here is the one MSP installation log:
=== Verbose logging started: 11/30/2013 21:28:15 Build type: SHIP UNICODE 4.05.6001.00 Calling process: e:\de60d5388bc787220900e629b152c9\hotfix.exe ===
MSI (c) (D4:28) [21:28:15:681]: Resetting cached policy values
MSI (c) (D4:28) [21:28:15:681]: Machine policy value 'Debug' is 0
MSI (c) (D4:28) [21:28:15:681]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (c) (D4:28) [21:28:15:681]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (D4:28) [21:28:15:681]: Grabbed execution mutex.
MSI (c) (D4:28) [21:28:15:697]: Cloaking enabled.
MSI (c) (D4:28) [21:28:15:697]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (D4:28) [21:28:15:697]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:15:697]: Running installation inside multi-package transaction {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
MSI (s) (A8:C0) [21:28:15:697]: Grabbed execution mutex.
MSI (s) (A8:04) [21:28:15:697]: Resetting cached policy values
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'Debug' is 0
MSI (s) (A8:04) [21:28:15:697]: ******* RunEngine:
******* Product: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}
******* Action:
******* CommandLine: **********
MSI (s) (A8:04) [21:28:15:697]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (A8:04) [21:28:15:931]: End dialog not enabled
MSI (s) (A8:04) [21:28:15:931]: Original package ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:931]: Package we're running from ==> C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: looking for appcompat database entry with ProductCode '{EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}'.
MSI (s) (A8:04) [21:28:15:994]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (A8:04) [21:28:15:994]: Opening existing patch 'C:\WINDOWS\Installer\e9ff36e.msp'.
MSI (s) (A8:04) [21:28:16:010]: Opening existing patch 'C:\WINDOWS\Installer\239697ae.msp'.
MSI (s) (A8:04) [21:28:16:056]: File will have security applied from OpCode.
MSI (s) (A8:04) [21:28:16:056]: Original patch ==> e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:056]: Patch we're running from ==> C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp' against software restriction policy
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not digitally signed
MSI (s) (A8:04) [21:28:16:072]: SOFTWARE RESTRICTION POLICY: e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is permitted to run at the 'unrestricted' authorization level.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches starts. Product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, Product version: 9.00.1399.06, Upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}, Product language 1033
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Tables 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 2262 2: _Columns 3: -2147287038
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: verifying the applicability of QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp against product code: {EE8CFFD9-6E29-4DC3-A967-7348D5F41F44}, product version: 9.00.1399.06, product language
1033 and upgrade code: {2B33A057-4470-45CD-8E63-863CB78FC626}
MSI (s) (A8:04) [21:28:16:072]: PATCH SEQUENCER: QFE patch e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp is not applicable.
MSI (s) (A8:04) [21:28:16:072]: SequencePatches returns success.
MSI (s) (A8:04) [21:28:16:072]: Final Patch Application Order:
MSI (s) (A8:04) [21:28:16:072]: Other Patches:
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C} - e:\de60d5388bc787220900e629b152c9\HotFixDTS\Files\sqlrun_dts.msp
MSI (s) (A8:04) [21:28:16:072]: Superseded: {5E9ADA2D-3132-42CF-8628-D2ADA0F335EE} -
MSI (s) (A8:04) [21:28:16:072]: Superseded: {32BCE9F2-8686-487A-80A9-A401C0F7DCBD} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {D23D25E7-0AB4-41EE-81B5-F0CF34D1BA2B} -
MSI (s) (A8:04) [21:28:16:072]: Unknown\Absent: {CF321155-04AA-4CF8-BB9A-DA3144835E3E} -
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisablePatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (A8:04) [21:28:16:072]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (A8:04) [21:28:16:072]: Disallowing uninstallation of patch {CF321155-04AA-4CF8-BB9A-DA3144835E3E} because the patch is marked as not uninstallable
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'Service Pack 4 for SQL Server Integration Services 2005 ENU (KB2463332)' could not be removed. Error code 1646. Additional information is available in the log
file C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: Service Pack 4 for SQL Server Integration Services 2005 ENU
(KB2463332). Removal success or error status: 0.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update '{4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}' could not be installed. Error code 1646. Additional information is available in the log file C:\Program Files\Microsoft
SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: {4C3BC5C8-67A5-40F1-85B7-D9341A5F7B6C}. Installation success
or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services - Update 'GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120)' could not be removed. Error code 1646. Additional information is available in the log file C:\Program
Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\DTS9_Hotfix_KB2716429_sqlrun_dts.msp.log.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer removed an update. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Update Name: GDR 5057 for SQL Server Integration Services 2005 ENU (KB2494120).
Removal success or error status: 1646.
MSI (s) (A8:04) [21:28:16:072]: Note: 1: 1708
MSI (s) (A8:04) [21:28:16:072]: Product: Microsoft SQL Server 2005 Integration Services -- Installation failed.
MSI (s) (A8:04) [21:28:16:072]: Windows Installer installed the product. Product Name: Microsoft SQL Server 2005 Integration Services. Product Version: 9.00.1399.06. Product Language: 1033. Installation success or error status: 1646.
MSI (s) (A8:04) [21:28:16:088]: Attempting to delete file C:\WINDOWS\Installer\1f80a9f.msp
MSI (s) (A8:04) [21:28:16:088]: MainEngineThread is returning 1646
MSI (s) (A8:C0) [21:28:16:088]: No System Restore sequence number for this installation.
Uninstallation of the patch package is not supported.
C:\WINDOWS\Installer\181c1.msi
MSI (s) (A8:C0) [21:28:16:088]: User policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Machine policy value 'DisableRollback' is 0
MSI (s) (A8:C0) [21:28:16:088]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (A8:C0) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (A8:C0) [21:28:16:088]: Restoring environment variables
MSI (c) (D4:28) [21:28:16:088]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (D4:28) [21:28:16:088]: MainEngineThread is returning 1646
=== Verbose logging stopped: 11/30/2013 21:28:16 === -
SQL 2005 Express will not start
Service just would not start after a reboot I have approximately 30 clients this has happened to basically out of the blue and they started happening approximately 6/17/2014. The SQL log and event log errrors are below. Uninstall reinstall only fails, switching
to local service account throws WMI Provider Error, Can't find object or property" [0x80092004]. The common issue seems to be a malware infection of Search Protect. Please advise before this gets worse. Thank you.
SQL 2005 wont start error logs
FallBack certificate initialization failed with error code: 1. 17190
TDSSNIClient initialization failed with error 0x80092004, status code 0x80. 17182
TDSSNIClient initialization failed with error 0x80092004, status code 0x1. 17182
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 17826
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. 17120
The SQL Server (VSDOTNET) service terminated with service-specific error %%-2146885628. 7024
FallBack certificate initialization failed with error code: 1. 17190
INFO-Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate. 26017
Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log. 17826
SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems. 17120
WMI Provider Error
"Can't find object or property" [0x80092004]
SQL Start up log
2014-06-26 09:18:54.83 Server Microsoft SQL Server 2005 - 9.00.5000.00 (Intel X86)
Dec 10 2010 10:56:29
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.1 (Build 7601: Service Pack 1)
2014-06-26 09:18:54.83 Server (c) 2005 Microsoft Corporation.
2014-06-26 09:18:54.83 Server All rights reserved.
2014-06-26 09:18:54.83 Server Server process ID is 2716.
2014-06-26 09:18:54.83 Server Authentication mode is MIXED.
2014-06-26 09:18:54.83 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2014-06-26 09:18:54.83 Server This instance of SQL Server last reported using a process ID of 4936 at 6/26/2014 9:13:53 AM (local) 6/26/2014 2:13:53 PM (UTC). This is an informational message only; no user action is required.
2014-06-26 09:18:54.83 Server Registry startup parameters:
2014-06-26 09:18:54.83 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2014-06-26 09:18:54.83 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2014-06-26 09:18:54.83 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2014-06-26 09:18:54.84 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-06-26 09:18:54.84 Server Detected 2 CPUs. This is an informational message; no user action is required.
2014-06-26 09:18:54.94 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-06-26 09:18:54.95 Server Database mirroring has been enabled on this instance of SQL Server.
2014-06-26 09:18:54.96 spid4s Starting up database 'master'.
2014-06-26 09:18:55.11 spid4s SQL Trace ID 1 was started by login "sa".
2014-06-26 09:18:55.13 spid4s Starting up database 'mssqlsystemresource'.
2014-06-26 09:18:55.15 spid4s The resource database build version is 9.00.5000. This is an informational message only. No user action is required.
2014-06-26 09:18:55.32 Server Error: 17190, Severity: 16, State: 1.
2014-06-26 09:18:55.32 Server FallBack certificate initialization failed with error code: 1.
2014-06-26 09:18:55.32 spid4s Server name is '2UA1371VFY\VSDOTNET'. This is an informational message only. No user action is required.
2014-06-26 09:18:55.32 spid8s Starting up database 'model'.
2014-06-26 09:18:55.32 Server Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2014-06-26 09:18:55.32 spid4s Starting up database 'msdb'.
2014-06-26 09:18:55.32 Server Error: 17182, Severity: 16, State: 1.
2014-06-26 09:18:55.32 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x80.
2014-06-26 09:18:55.32 Server Error: 17182, Severity: 16, State: 1.
2014-06-26 09:18:55.32 Server TDSSNIClient initialization failed with error 0x80092004, status code 0x1.
2014-06-26 09:18:55.32 Server Error: 17826, Severity: 18, State: 3.
2014-06-26 09:18:55.32 Server Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2014-06-26 09:18:55.33 Server Error: 17120, Severity: 16, State: 1.
2014-06-26 09:18:55.33 Server SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.
James BallThis is what I found by someone else;
I know it's probably too late to help with the original poster, but we had this same issue and nothing we tried resolved the problem. Finally, we opened a technical incident with Microsoft and this is the solution that we were provided:
Take backup of below registry key.
HKLM\SOFTWARE\Microsoft\Cryptography\MachineGuid This key should ideally have the GUID of the machine without curly braces, so {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} becomes xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
Then delete the braces.
Try to reboot and start the SQL service . If service don’t start then Uninstall and reinstall SQL.
The above solution worked on two separate machines exhibiting this problem.
Monday, June 30, 2014 3:03 PM
jawg
(Partner)
10 Point
James Ball -
Hi,
We have a problem when we are trying to install SQL SP3 on SQL 2005 cluster.
The problem is described bellow:
We installed a new Windows 2008 R2 x64 failover cluster with two nodes.
As a next step we installed SQL 2005 Enterprise edition x64 on this failover cluster. We have finished the installation without problems. After SQL installation we are trying to install SQL SP3 . We have logged on using a domain administrator account and
we start the installation of SP3 with that user. In authentication mode screen the test gives a success status using either domain administrator-windows authentication or sa-sql authentication. On remote user account screen, when we give the domain
administrator account we get the message "the account information could not be verified. Press ok to return to authentication mode screen to determine the reason for failure".
We have tried to give the SQL services startup user on remote user account screen but the error is the same.
the domain administrator account exists on security logins of SQL with sysadmin rights.
Can someone help?
Thanks.Hi StelioMavro,
According to your error message, when you install SQL Server 2005 SP3 in your failover cluster, we need to verify if there was other instance that had been removed and the installation did not pass the login check. I recommend you use windows authentication
instead of SQL Server authentication when applying SP3. And the windows account used to run the SP3 setup program must have administrator privileges on the computer where SP3 will be installed.
For more information about how to install SQL Server 2005 SP3 in failover cluster, you can review the following article.
http://www.sqlcoffee.com/Tips0007.htm
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
Bad Performance on SQL 2005 multiserver installation
We have upgraded our server environment from a single server solution with SQL 2000 and are now running on a multiserver solution with one DB server with SQL 2005 and two applictionservers.
And now we are experience a much slower performance in our new environment on all EVDRE reports. Is there anyone who know about any issue with a multiserver environment or SQL 2005 that makes the reports slower?
In our more advanced report with "expand by sheet" that took about 1 minute to expand on our old environment can take up to 10 minutes to expand in our new environment.
Both servers are running BPC 5.1 SP5 patch 1The SQL Server version is very good and the performance problems should not come from there.
Please make sure you check the document from sd regarding
SAP_BPC_Performance_Tuning_Guide.doc to be sure you have the right configuration for OLAP and SQL and also application server.
Can you please provide an information regarding what kind of configuration do you have into this multiserver environment?
It is important also nr. of processors and memory for each server.
Do you have a maintenance plan for your SQL server database?
If you don't have that can cause again a big problem regarding performances.
Please run into management studio exec sp_updatestats for you database to be sure that you have at least update statistics.
So all these things mentioned before should be managed carefully to be sure that you have good performances into system.
From application point of view make sure that you schedule lite optimize to be sure that you don't have more than 40000 rows into wb table.
Regards
Sorin Radulescu -
SQL 2005 Express on WE POSReady 7
Hi all
We have an issue spwaning with a SQL Express 2005 SP3 on POS machines running WE POSReady7
After running smoothly for over 1 year x4 units over the last 2 months have developed an issue where the SQL engine stops running and wont restart - gives a timeout error when trying to start the service.
I have tried to start sql via cmd line with various traceflags to stop the tempdb being cleared etc.. out but the service will still not start.
this is the issue in SQL logs:
2014-03-11 09:51:38.41 spid5s Starting up database 'mssqlsystemresource'.
2014-03-11 09:51:38.48 spid5s The resource database build version is 9.00.4035. This is an informational message only. No user action is required.
2014-03-11 09:51:39.76 spid8s Starting up database 'model'.
2014-03-11 09:51:39.76 spid5s Server name is 'MORPOS02'. This is an informational message only. No user action is required.
2014-03-11 09:51:39.78 spid5s Starting up database 'msdb'.
2014-03-11 09:51:39.88 spid8s Clearing tempdb database.
2014-03-11 09:51:40.53 spid8s Starting up database 'tempdb'.
2014-03-11 09:51:40.75 spid8s Fatal error encountered. To recover tempdb, tempdb log optimization must be turned off (-T1102) in the last server run.
2014-03-11 09:51:40.79 spid8s Using 'dbghelp.dll' version '4.0.5'
2014-03-11 09:51:40.80 spid8s **Dump thread - spid = 8, PSS = 0x048647D8, EC = 0x048647E0
2014-03-11 09:51:40.80 spid8s ***Stack Dump being sent to c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\SQLDump0001.txt
Anyhoo that is the main issue, but i am really asking here is when i try untinstall SQL it uninstalls OK but then re-installs itself after a short period! :S ! is there anything with this version of the OS that could be causing this?????
I removed all components from the Programs & Features > within 5min its back in there, start menu folders back, SQL mgmt console is back etc....I noticed after the uninstall is finished it i see the MSIEXEC process still running.
Ive tried to end the msiexec.exe process after uninstalling finishes and install SQL Express 2005 SP4 it gets part way through and then errors out.
rebooting has made no difference, have tried a number of things. I have ruled out a GPO and login script reinstalling SQL
thoughts?Is the database file you are access corrupted ?
Have you tried any of the latest edition of SQL Express?
www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET -
Replacing a SQL Server 2005 Express Database with a SQL CE 3.5 database
I am just googling for the past few days to find out the answer to this problem..
I have an app developed over few man-years of effort - with vb.net and SQL 2005 Express Db. Now we use VS 2010 sp1 with .net 3.5 sp1. We have used plain T-SQL commands and the app was performing admirably well. The DB has about forty tables. The data
volume is about 200 to 300 mb max - but mainly it stays about 50 to 60 mb in many places. We are also using XML data transfers to backup the data.
Now we want to shift to SQL CE 3.5 or 4.0 - just to avoid the pain of SQL Express download and installation by the users. We have successfully created a 3.5 and 4.0 sdf files. But when we change the connection from a mdf file to the sdf file in the VS2010 settings
area, it just goes fine - the connection string is accepted and the app starts. But we get the usual error no 26 - unable to locate the database file - and a five line message that it is not able to connect to the sql server.
Are we missing something ? We have included the sqlce dll in the references.. but just not able to make the app connect to the sdf file..
All the codes, datasets, adapters, queries are just intact in the app - but just we are not able to connect to the sdf database.
We would appreciate help in this regard and also in doing a build with SQL Ce with Inno Setup which we have been using so long.
Finally there is too much of SQL CEs around - but 3.5, 3.5 sp2 and now CE 4.0 seems to be ones to go in for. Which one is really the best for our app - 3.5 or 4.0 ?
Thanks in advance.we change the connection from a mdf file to the sdf file ... All the codes, datasets, adapters, queries are just intact in the app...
Agree with Erik, just changing the connection string don't work, you have to use data access components from
System.Data.SqlServerCe Namespace instead of
System.Data.SqlClient Namespace
Olaf Helper
[ Blog] [ Xing] [ MVP]
Maybe you are looking for
-
Changing logo image in search page
Hi Mr Roger Ford, Would you please to help me. I'm using SES 11.1.2 on SuSE Linux SLES 10. I would like to change the logo image in search page. I have followed step by step in: http://download.oracle.com/docs/cd/E14507_01/apirefs.1112/e14133/objects
-
Copy text from PDF and paste to imessage
Before iOS7 I would be able to copy text from a PDF file and paste it normally into a text message or imessage. Now when doing the same thing it doesn't paste the actual text I copied, but it pastes as an html attachment. Have I changed a setting o
-
[Microsoft Intune] Deployed software not showing up in web portal
I am testing microsoft intune in a testlab. I have downloaded the trial and installed it on the server and I synced my AD users with intune. After that i added a windows 8.1 device. I can reboot the machine remotely with the admin console and i can s
-
I just hooked up the Apple TV and after a bit have it working with everything except sound through my Bose sound system. It plays audio through the TV speakers but I cannot get audio out of the Bose. I can play movies, music, podcasts, etc but no aud
-
First page prints fine but subsequent pages expand beyond page border
When I print a web page or selection that extends beyond one page, the first page prints fine, but the type size on subsequent pages is expanded so that the content extends beyond the right edge of the page. This never happened before I upgraded to F