SQL 2005

Hi,
Can you please help me to find SQL 2005 installation guide for SAP B1.
Thanks,
Olga

Have you got this part:
Procedure
1. Put the SAP Business One Product DVD into the DVD drive.
The installation program appears automatically. If the DVD does not launch the installation
program, navigate to the DVD root folder and double-click Autorun.exe.
2. Install Microsoft SQL Server 2005:
a) From the installation program Welcome page, choose Install Server .
> If SQL Server 2005 is not installed on your computer, the SQL Server 2005 installation page appears.
> Choose Install to begin installing SQL Server 2005. This process does not require inputfrom you and may take some time. Or,
> Choose Skip to perform the installation yourself.
>Note
>If you install SQL Server 2005 yourself, make sure you select Latin1_General and AS in theCollation Settings window.
> If you already have SQL Server 2005 installed, the installation proceeds to the Server Installation page. Continue with Step 4.
b) Put the SQL Server 2005 DVD and specify the installation directory.
To change the default installation directory, choose Browse.
Choose Install.
The setup begins a silent installation of SQL Server 2005 components. The silent installation
uses the following default values:
c) Wait until the installation program confirms that you can remove SQL Server 2005 DVD.

Similar Messages

Browse Data & Parameter flds no longer fully populated after upgd SQL 2005

I upgrade our SQL 2000 Server last weekend to SQL 2005 (sp2).
Now our Crystal reports that access SQL data are not working correctly. Parameter Fields are showing little to no data, where before the upgrade we were seeing many more rows in the list.
Digging further, I looked at the fields used for the dynamic LOV. If I use Browse Data on those fields I am seeing the same lack of data. One "Browse Data" that would typically return 80 items now returns 3 items. In that report the data field is DateTime. In another report, the field is string.
I am also seeing an extra check for User Name and password before getting to the Enter values screen for the parameter.
I am using Crystal Developer 11.0.0.1994. It is happening on multiple PCs. I tried with both the original SQL ODBC Driver and the newer SQL Native Client ODBC driver, with the same result.
I've looked at this for 3 days with no luck. Any ideas?

Full SysAdmin rights.
I use a dedicated ODBC connection and have tried both "SQL Server" odbc driver and "SQL NativeClient" (2005) odbc driver.
If I go to Crystal, to the Field Explorer, to the one of the fields, right-click and "Browse Data..." I get two results (I expect 82 results and have seen that in the past.) If I paste the query from Crystal, Database, "Show SQL Query.." to SQL Server Management Studio, I see the full, correct results.
In one example the field browsed is called "PeriodEndDate" (DateTime). A dynamic Parameter Field was created accessing this field. Here is the security curiosity...refreshing now asks for the user login each time "Prompt for new parameter values" is selected. It used to ask only the first time. The Crystal: Data Explorer" shows the current connection logged in ok.
The two issues may or may not be related. Certainly if #1 were fixed, dynamic parameters would return the correct results. Even if it asked for the password each time.
1.) "Browse Data" returning a smaller result than normal.
2.) "Parameter Prompt" asks for Server Name, Database Name, User Name, and Password on
each refresh selecting "Prompt for new parameter values".

Dsml and SQL 2005 reporting services?

I usually post over in the IDM forum so be nice to the newbie here :)
I have a Sun Directory server that I've enabled DSML on. On that side everything is good. However, ideally I want to pull this data into a MS SQL 2005 reporting services report. They have support for XML and web services, but the DSML front end doesn't accept GET requests and I don't know how to send the request as post in reporting services.
Has anyone else be able to get something like this working?
Thanks!

No idea about MS SQL, but is your reporting service able to use files on disk? If so I guess your problem is easily solved by using an app to fetch data from directory server to disk. If you're more adventerous, you write a script in perl/python which acts as a proxy and translates GET requests to POST and relays data back in real time. Not sure if these help or not, just my thoughts.

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 thanks

This may be hard disk problem, some file not able to write on HDD.
Regards
Rajnish

Xp_logininfo "Installation problem on windows 2003 with Sql 2005"

Hi every one
I am facing a problem during the installation of Solution Manager 4.0 on Windows 2003 server with Ms Sql 2005, I received the following error
Msg 15404, Level 16, State 19, Procedure xp_logininfo, Line 60.
Its some how look likes that the user "SID"ADM
Can any one give me a clue
thanks
Kind Regards
Sohail

Hi All,
This would solve your problem
First of all this error is <b>MSSQL error</b>.
When you perform an action on an instance of SQL Server that requires SQL Server to resolve the credentials of a Microsoft Windows NT domain user account, you may receive an error message that is similar
Server: Msg 8198, Level 16, State XX, Procedure <Stored Procedure Name>, Line <line Number>
Could not obtain information about Windows NT group/user '<Domain\Account Name>'.
To resolve the credentials of a Windows NT domain user account, SQL Server uses the xp_logininfo system stored procedure. Here is a list of the common scenarios where you may notice that the xp_logininfo system stored procedure fails and causes the 8198 error.
When you use an xp_sendmail extended stored procedure.
When you set up replication.
When you run a SQL Server Agent job.
SQL Server may run the xp_logininfo system stored procedure to retrieve information about the Windows domains and the user accounts, even if the user does not do so explicitly. Therefore, if you receive an 8198 error message and the error message mentions the xp_logininfo system stored procedure as the procedure, you must use <b>SQL Profiler</b> to trace and to troubleshoot the exact point of failure.
You can go through this link for more info...
http://support.microsoft.com/?kbid=834124
Feel Free to Revert back...
--Thanks and Regards,
Ragu
ERP,
Suzlon Energy Limted, Pune
Extn: 2638
+919370675797
I have no limits for others sky is only a reason

SQL 2005 will not connect in SQL 2012 profiler

We have a few SQL 2005 databases that we manage. I went to do a trace on them(recently upgraded to 2012) and it gives me the error, "SQL Server Native Client 11.0 does not support connections to SQL Server 2000 and earlier versions".
According to MSDN it does. https://msdn.microsoft.com/en-us/library/cc280356(v=SQL.110).aspx
"SQL Server Native Client 11.0 supports connections to SQL Server 2005, SQL Server 2008, SQL Server 2008
R2, SQL Server 2012, and Windows Azure SQL Database."
Any clue why it wouldn't let me connect?

Can you specify the following parameter in the "connect to server" dialog when you load the Profiler --> click on "options" button and go to "Additional Connection Parameters" tab and paste the following?
DataTypeCompatibility=80
Satish Kartan www.sqlfood.com

Database connection to MS SQL 2005 (URGENT Help Needed)

Hi all,
Does anyone know how to connect my adobe form to MS SQL 2005?
I have this code:
try {
     InitialContext initialContext = new InitialContext ();
     DataSource dataSource = (DataSource) initialContext.lookup ("jdbc/MyAlias");
      java.sql.Connection connection = dataSource.getConnection ();
} catch (SQLException e) {
     // handle exception
} catch (NamingException e) {
// handle exception
Other than these, what else do i need to do inorder to get my database connection up?
And after my database connection is up, how do i test to check if my database connection is up or not?
How do i extract the information from the database and put them onto the textfields/dropdownlists on my form?
Thanks In Advance

Hi Mel,
After implementing the codes and modifying them, some of them are underlined, why is this so? =X
Or are u willing to exchange msn so i could send u the screenshot instead?
Thanks In Advance
(Sorry im not that good in this)
(I shall underline the areas which represents the red underline in my web dynpro)
     //Code for database connection.
       InitialContext ctx = new InitialContext();
       DataSource ds = (DataSource)_ctx.lookup("jdbc/JXDataSource");_
       Connection conn = ds.getConnection();
       Statement st = null;
       ResultSet rs = null;
       IPrivateDetailed_Claims_FormView.IFillDataElement dataEle = null;
       st = conn.createStatement();
     //     Execute the appropriate SQL query
       rs = st.executeQuery("SELECT NAME WHERE VENDORCODE='9000116L' ");_
       while (rs.next())       {
     //     Code that will populate your VN based on the data obtained in the ResultSet.
       dataEle = wdContext.createFillDataElement();
       dataEle.setName(_rs.getString(1)_);
      // dataEle.setAge(rs.getInt(2));
      // dataEle.setAddress(rs.getString(3));
       //wdContext.nodeFillData.addElement(dataEle);
       // Close the connections
       rs.close();
       st.close();
                  conn.close();
Edited by: JingXuan Lim on Jan 25, 2008 4:59 AM
Edited by: JingXuan Lim on Jan 25, 2008 5:00 AM

ERP 6.0 on MS SQL 2005 not start

Hello.
System ERP 6.0
OS: Win2003
DB: MS SQL 2005
Try startup SAP System, but dispatcher stopped.
Work process are died...
In wp00 log next:
M Wed Dec 10 15:42:32 2008
M calling db_connect ...
C Thread ID:1860
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'E:\usr\sap\E01\DVEBMGS00\exe\dbmssslib.dll'
C dbmssslib.dll patch info
C    patchlevel   0
C    patchno      144
C    patchcomment MSSQL: ODBC fastload on separate connection (1131805)
C np:(local) connection used on STG-PTP-R3
C CopyLocalParameters: dbuser is 'e01'
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C Provider Release:9.00.2047.00
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C OpenOledbConnection: line 23715. hr: 0x8000ffff Communication link failure
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Communication link failure
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Named Pipes Provider: РЎ РѕРu00B1РѕРёСu2026 РєРѕРЅСu2020РѕРІ РєРu00B0РЅРu00B0Рu00BBРu00B0 РѕСu201AСЃСѓСu201AСЃСu201AРІСѓСЋСu201A РїСЂРѕСu2020Рu00B5СЃСЃСu2039.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C OpenOledbConnection: line 23715. hr: 0x8000ffff Communication link failure
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Communication link failure
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Named Pipes Provider: РЎ РѕРu00B1РѕРёСu2026 РєРѕРЅСu2020РѕРІ РєРu00B0РЅРu00B0Рu00BBРu00B0 РѕСu201AСЃСѓСu201AСЃСu201AРІСѓСЋСu201A РїСЂРѕСu2020Рu00B5СЃСЃСu2039.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C OpenOledbConnection: line 23715. hr: 0x8000ffff Communication link failure
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Communication link failure
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 233, sev 0), Named Pipes Provider: РЎ РѕРu00B1РѕРёСu2026 РєРѕРЅСu2020РѕРІ РєРu00B0РЅРu00B0Рu00BBРu00B0 РѕСu201AСЃСѓСu201AСЃСu201AРІСѓСЋСu201A РїСЂРѕСu2020Рu00B5СЃСЃСu2039.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23715]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn. 1
B ***LOG BY2=> sql error -1     performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY0=> Communication link failure [dbsh#2 @ 1204] [dbsh    1204 ]
B ***LOG BY2=> sql error -1     performing CON [dblink#5 @ 431] [dblink 0431 ]
B ***LOG BY0=> Communication link failure [dblink#5 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1440]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10468]
What's it mean?
I have a little experience with SQL Server...

Hi,
Is this a new installation, if so is it started all fresh or from upgrade.
If this is not new installation what are the activities executed that has affected the database, i feel no process on other end of pipe which was something related to non-existence of shadow process at database level for the process from SAP.
See also the amount of free space available and what was the LOG file size since this grow enormously in MSS.
Go thru the links
[http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3940600&SiteID=17]
[http://blogs.msdn.com/sql_protocols/archive/2006/07/26/678596.aspx]
have you installed the MSSQL supportpacks provided by SAP along with MSSQL database, i feel problem in database installation, this DB is not tuned in accordance to SAP.
Regards....
Edited by: Sita Rr Uppalapati on Dec 11, 2008 8:31 PM

Unable to install SQL 2005 Service Pack 3 (Unable to install Windows Installer MSI file)

I'm unable to install SQL 2005 Service Pack 3. This results in the following error message: Unable to install Windows Installer MSI file.
Could someone please help me. Thanks in advance!
=== Verbose logging started: 3-4-2009 9:33:00 Build type: SHIP UNICODE 4.05.6001.00 Calling process: d:\5ddfa356349ddf2e676c336d95c5\hotfix.exe ===
MSI (c) (E0:88) [09:33:00:404]: Resetting cached policy values
MSI (c) (E0:88) [09:33:00:404]: Machine policy value 'Debug' is 0
MSI (c) (E0:88) [09:33:00:404]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (E0:88) [09:33:00:404]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E0:88) [09:33:00:404]: Grabbed execution mutex.
MSI (c) (E0:88) [09:33:00:419]: Cloaking enabled.
MSI (c) (E0:88) [09:33:00:419]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E0:88) [09:33:00:419]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:01:747]: Running installation inside multi-package transaction C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:01:747]: Grabbed execution mutex.
MSI (s) (28:CC) [09:33:02:029]: Resetting cached policy values
MSI (s) (28:CC) [09:33:02:029]: Machine policy value 'Debug' is 0
MSI (s) (28:CC) [09:33:02:029]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (28:CC) [09:33:02:685]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (28:CC) [09:33:03:450]: File will have security applied from OpCode.
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi' against software restriction policy
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi has a digital signature
MSI (s) (28:CC) [09:33:04:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (28:CC) [09:33:04:888]: End dialog not enabled
MSI (s) (28:CC) [09:33:04:888]: Original package ==> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:CC) [09:33:04:888]: Package we're running from ==> C:\WINDOWS\Installer\3d3a713.msi
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (28:CC) [09:33:05:685]: MSCOREE not loaded loading copy from system32
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\2f1994e.msi 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Opening existing patch 'C:\WINDOWS\Installer\e6ba0.msp'.
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\e6ba0.msp 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Couldn't find local patch 'C:\WINDOWS\Installer\e6ba0.msp'. Looking for it at its source.
MSI (s) (28:CC) [09:33:05:825]: Resolving Patch source.
MSI (s) (28:CC) [09:33:05:825]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (28:CC) [09:33:05:825]: User policy value 'DisableMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media is enabled for product.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Trying source \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 2203 2: \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\SqlSupport.msp 3: -2147287037
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing net source list.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing media source list.
MSI (s) (28:CC) [09:33:07:654]: SOURCEMGMT: Resolved source to: 'SqlSupport.msp'
MSI (s) (28:CC) [09:33:37:732]: Note: 1: 1314 2: SqlSupport.msp
MSI (s) (28:CC) [09:33:37:732]: Unable to create a temp copy of patch 'SqlSupport.msp'.
MSI (s) (28:CC) [09:33:37:732]: Searching provided command line patches for patch code {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:37:763]: Note: 1: 1708
MSI (s) (28:CC) [09:33:37:763]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.
MSI (s) (28:CC) [09:33:37:763]: Windows Installer installed the product. Product Name: Microsoft SQL Server Setup Support Files (English). Product Version: 9.00.4035.00. Product Language: 1033. Installation success or error status: 1635.
MSI (s) (28:CC) [09:33:37:779]: MainEngineThread is returning 1635
MSI (s) (28:28) [09:33:37:888]: No System Restore sequence number for this installation.
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:37:888]: User policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Machine policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:37:904]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (28:28) [09:33:37:919]: Restoring environment variables
MSI (c) (E0:88) [09:33:37:935]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (E0:88) [09:33:37:935]: MainEngineThread is returning 1635
=== Verbose logging stopped: 3-4-2009 9:33:37 ===

This post should definitely help you
http://blogs.msdn.com/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?CommentPosted=true
Feroz
Mark as Answer if it helps. This posting is provided "AS IS" with no warranties and confers no rights.

I downloaded Mozilla 4 and tried to use it then, I had to delete it and go back to 3.6 vs now I am having problems with my MS SQL 2005 why? What was changed to enable Mozilla 4 to sync with MS SQL and how do I get it corrected?

After, trying Mozilla 4 beta and then having to go back to a previous vs of Mozilla 3.6.11 my MS OLE DB Provider for SQL 2005 Server has this error message '80040E57' I am using Windows 7 which was pre-installed on my new computer. I do not know how to fix it?

The latest flash player release is 11,0,1,152.
Can you upgrade to this version and see whether the crash stil exists?
Go to get.adobe.com/flashplayer to download and install flash player.
In case you need direct link to installer/uninstaller, please go to http://forums.adobe.com/message/3952360#3952360 to find them.
saranlee wrote:
My computer crashes repeatedly and I get the message pages are not responding do you want to stop, and/or shockwave is not responding do you want to stop. I have Windows XP Service Pack 3, I am having the same issues whether I use Internet Explorer, Google Chrome, or Mozilla Firefox. My HP Pavilion Desktop has 504 MB of Ram and I am using high speed internet connection. Because it was crashing so much, I used the uninstall program for Flash player to uninstall Flash, I checked my registry and removed anything I saw that was Flash. I then uninstalled Google Chrome and Mozilla Firefox, then I reinstalled the most recent versions from their websites. I did the same for FlashPlayer and Shockwave Flash. I went to the Adobe website and had them check to see if it was working and it shows I have FlashPlayer 10.3.181.36. The page that shows which version of flash player goes with Windows XP states that I should have 10.3.181.34 (This is what I thought I had before I updated, I was having the same problems). When I went into my computer to see what version I have, it shows 11.5.9.620 Activex and both Flash Player and Flash Player Object is listed as 10.3.181.34. My firewall for Windows is set to medium. I also am running Norton Internet Security. It takes anywhere from 3-6minutes for some of my games to load, and I have to refresh at least 3-4 times in order to play. When I do start to play it freezes frequently and I use escape to free it up. This has been going on for a month. I have no idea what to do. I am not very computer savy and I have been learning as I go.

SQL 2005 SAP R/3 4.6C - DBSL error RC=99 on import of Basis 4.6C SP 39

Hi,
I have just built a R/3 4.6C system on SQL 2005 with 4.6D_EXT kernel. The build was done using R3load to export from the 4.6C/SQL 2000/32bit system and import to 4.6C/SQL 2005/64bit system. The source 4.6C system only had Basis support package 37 applied, and I am trying to apply Basis 4.6C 38-57 on the 4.6C/SQL 2005/64bit system (in preparation for an ECC6 upgrade) and I get the following error:
EXEC SQL: SELECT ID,OBJECT,LANGU,TYP,VERSION FROM DOKIL WHERE (LANGU IN (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,
[developertra,00000] ExecuteAndFlush return code: 0x80040e10 Stmt: [CREATE PROCEDURE ##Y8IBASAPDEIBD00000025600000000006164133 @P
                                                                          99972 0.099972
[developertra,00000] MapHr:80040E10 DB_E_PARAMNOTOPTIONAL                  43 0.100015
[developertra,00000] HandleOledbError [ExecuteAndFlush,line 33423]: Error/Message: (err 0, sev 0), No value given for one or more
                                                                             96 0.100111
[developertra,00000] DbSlPrepare - Error 99 (dbcode -2147217904) on proc. creation
56 0.100167
[developertra,00000] DbSlPrepare - <CREATE PROCEDURE ##Y8IBASAPDEIBD00000025600000000006164133 @P000 varchar(3072) = ' ', @P001 v
                                                                            105 0.100272
[developertra,00000] 1 times error (0,0) in sequence                       30 0.100302
[developertra,00000] dbdsmss: DBSL99 SQL0                                  27 0.100329
[developertra,00000] No value given for one or more required parameters.
62 0.100391
[dbds        ,00589] ***LOG BY2=>sql error 0          performing FET
66 0.100457
[dbds        ,00589] ***LOG BY0=>No value given for one or more required parameters.
I have checked the collation setting in SQL 2005 and it is:
select serverproperty('collation')
SQL_Latin1_General_CP850_BIN2
There are 97000 odd entries in DOKIL, so I don't think that is the problem.
Would appreciate any assistance.
Kind regards,
Sheryl.

Hi ,
Instead of doing the build with export import, you can try to do the same with backup restore,,
But remember your sql2000 should be on bin2... then you can take backup and restore.
Since it is from 2000 to 2005 the restore would happen and it will work fine.
Try this and check out, since the error you have pasted is not clearly giving any picture...
Regards,
Ravi.

SAP R/3 Data Import to MS SQL 2005

Hi
I am trying to import SAP R/3 Data to MS SQL 2005 with SQL Server Import and Export Wizard (.net framework Data Provider for mySAP Business Suite. )
for ie i have to import data from mara table.
but i am getting error at the time i am making connect from MS SQL 2005 to SAP R/3 ...
Following is the error
The operation could not be completed
Additional information
--> Missing SYSNR = ... in connect_param in RFcOpenEx(Microsoft.Adapter.SAP.SAPProvider)
|--> Missing SYSNR = ... in connect_param in RFCOpenEx ( GInvoker)
Can any one explain me where i am going wrong?

I have downloaded SAP provider for SSIS, but it just a add-on and didn't find readme which will provide which right i should have for my SAP account.
Can you please send the location of the readme file.
I will furture request you, if possible send me what right i will required on SAP box to login using .Net Framework Data Provider for mySAP Business Suite from MS SQL Server Import and Export Wizard.

Upgrade R/3 4.7 110 from SQL 2000 to ECC 6.0 /SQL 2005

Dear Experts,
We are currently running R/3 4.7 110 with kernel 640 32 Bit Non Unicode on Windows Server 2000/ MS SQL 2000 Platform. We are planning to Upgrade the same to ECC 6.0 on Windows 2003/ SQL 2005 on New x64 Bit Hardware.
I was earlier planning to Upgrade the OS/DB in first Phase moving the same R/3 4.7 on Windows 2003 Server /MS SQL 2005 and then Upgrade it to ECC 6.0 in second phase. But to my surprise when I checked PAM, I found that R/3 4.7 110 is not at all supported on SQL 2005 ( though R/3 4.6 C is)
Now shall I upgrade it to ECC6.0 First with Windows 2003/SQL 2000 ( Because ECC6.0 is supported with MS SQL 2000)and then move to MS SQL 2005 ?
Thanks
Jitendra Tayal

We had the same issue.
So I checked with SAP.
This was their reply.
'SAP R/3 4.7 Ext 110 is supported on SQL 2005. Please refer to the following notes for further information:'
Note 905634 - Release planning for Microsoft SQL Server 2005
Note 799058 - Setting Up Microsoft SQL Server 2005
Note 899111 - Installing R3 4.7SR1 (47X110) on x64 Windows Platform
Note 151603 - Copying an SQL Server database
So feel free to go ahead.
Thanks.
Carl.

SQL Upgrade 2000 to SQL 2005

We are upgrading to new server and installing SQL 2005. Using Crystal Server 10. Where can I find a step by step? Can I just backup Business Objects Database, install the app on the new server, restore the database to SQL 2005?
Thanks,
SS

Hi Samuel
You can refer the below link for more information on SQL Server 2005 upgrade.
[http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx#top]
Regards
Girish.

Microsoft SQL 2005, Terminal Services and Tiger

We found a great application we need to use at work. Unfortunately, it runs only on Windows. We will need to run it on a Windows server, running SQL Server 2005, and Macs interacting with it using MS Terminal Server. At least that is what someone at Dell said. This ends up being a huge and complicated purchase for us.
All this is totally foreign to me. I set up our Mac network, using OSX Server 10.2, migrating up to 10.4. We have 16 computers on the network, and it runs reasonably well. I did not need months of training to set it up. There are many things I do not understand and features that I have zero idea about...but for email, web, ftp and application serving, it works well.
We have 13 Macs, 2 Windows boxes and one UNIX box on the network.
Has anyone used SQL 2005? Has anyone had to connect thru Terminal Services to a Windows Server?

Hi John!
Using Terminal Services on a Windows server is common in corporate environments and solves a lot of issues where Macs can't run Windows-only software.
Since the Windows server will be the only Windows machine on your network and you only need it for a specialized purpose, you can probably get by with purchasing Windows Small Business Server Premium, which comes with a SQL Server. You'll have to ask the vendor if this version will work with their product. See this link on Microsoft's website http://www.microsoft.com/windowsserver2003/sbs/default.mspx.
Many third party database applications will facilitate the setup of the datbase with the SQL server, but they won't support the SQL software and its security. I'd advise hiring a contractor to help with the installation and setting up a backup (preferably someone that can become familiar with your environment and provide ongoing support).
Hope this helps! bill
1 GHz Powerbook G4 Mac OS X (10.4.3)

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 queue

Hi ~ 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

Similar Messages

Maybe you are looking for