SQL 2005 Baclup restore procedure
Due to some virus problem I crashed my Development server .Before to do so I had taken SQL Full backup & copied the Datafiles & translog to someother location.
Now I installed a new system with diffrent SID .How can I restore the taken backup (sql full & copy of datafile ,translog)
Could you please tell me the procedure from SQL management studio or whatever the way is possible.
Awaiting for all your valuable steps.
Hi
Do u installed the sap again or not. if you taken full windows system backup at anypoint of them then restore the windows system with sap.
if not please install it from scratch as u previously done it (ie in the same name for database and the users)
then u can restore the database using sql enterprise manager or from sap it self using db13c tcode
please let me know how it helped to u
because the database username and passwords are created at the time of sap installation process install sap and or restore sap using full windows system backup of NT Backup or other backup.
N.Rameshkarthik
Similar Messages
-
Can't restore SQL 2005 BAK to SQL 2008 R2 running on Server 2012
Hi there,
Preparing to switch from SQL 2005/Server 2003 to SQL 2008 R2 / Server 2012. Took a backup of the SQL database on 2005 (stored at a cloud backup provider nightly) and copied to the new machine. Unable to restore the .BAK file, with the error:
The media family on device <backup path> is incorrectly formed. SQL Server cannot process this media family.
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)
Tried it with two different backup files from two different nights, same error. I understand that this error can show up when restoring to a lower version of SQL, but that's not the case here.
Also, I know this can occur if the BAK file is corrupt, and I can't verify that yet, but two in a row failed. I'm hoping our cloud solution isn't part of the problem somehow.
BAK file is 15 Gb in size, so don't have the ability to attempt the restore on the 2005 production server. Just not enough room, and can't afford to cause performance issues on that box anyway.
Anyone know of any way to get a better handle on what's going on, or, even better, how to resolve it?
Thanks
RobinHello,
Since you are using a cloud solution, maybe the following article applies in your scenario.
http://www.sqlcoffee.com/Troubleshooting047.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Database restore from SQL 2000 to SQL 2005 for SBO 2005B
Hi Everyone,
I am facing some problems in regards to the restore of SBO Database from SQL 2000 to SQL 2005.
Let me explain you the problem.
See I am using SAP B1 2005B with patch level 38 in my laptop with SQL 2000. I have made an company in this and done work in it as a production company and now I want to restore this company in the server which has SQL 2005. How to do it.
I have taken a backup in my laptop from SAP B1 Server Suite Manager which has SQL 2000 and sucessfully backed up but when I am trying to restore in the server which has SQL 2005 I am getting the following error in SQL 2005 in server :-
Restore failed for Server 'DXBAP001'. (Microsoft.SqlServer.Smo)
System.Data.SqlClient.SqlError: Directory lookup for the file "C:\Program Files\Microsoft SQL Server\MSSQL\data\SBO_DCHAR.mdf" failed with the operating system error 3(The system cannot find the path specified.). (Microsoft.SqlServer.Smo)
Please let me know the solution for it.
Thanks in Advance.
Regards,
Kawish Junaid MazhariHi,
In SQL 2005 create a database and name as the 200 one was (though any name would do). when you create the database note the location of the .mdb and .ldf file.
once this had created right click on your new database > tasks > restore database
in the new window select from device and point it to your .bak file created from your 2000 system, ensure you put a tick in the restore box on the new line.
in the options tab tick overwrite database, and, change the file locations in the restore as directory to the file locations of the new database. the file names must be the same too.
you can change the original file names after the restore.
that should do the trick.
thanks,
mike -
Restoration at sql 2005 from sql 2000 backup.
Hi experts,
Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
And how about attaching datafiles of sql2000 into sql 2005 server?
Thanks and Regards,
Amit Jana.> Is it possible to restore a backup taken from sql 2000 database to sql 2005 database?
Yes its possible.
> And how about attaching datafiles of sql2000 into sql 2005 server?
Same method of attach/deattach.
But recommanded you first install 2000 instance restore database and do inplace sql 2005 upgrade.
Why you can't follow recommanded mothed ?
Regards,
Nikunj Thaker -
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. -
Upgrade Process from SQL 2005 to SQL 2012
Hi All,
I have gone thru multiple threads and would like to understand some steps in detail for me to upgrade SQL 2005 to SQL 2012.
Below is my understanding and questions around it, I would be setting up a new environment with OS 2007/2008 with SQL 2012:
Environment Readiness - Ensure new environment is ready with Win 2007/2008 with SQL 2012 Server
Run Upgrade Advisor on the new environment and point to SQL 2005 instance
Find the breaking/discontinued changes to be done before or After Upgrade
<Question>: Over here I would like to know what should be our approach to make the required changes
<Question>: Obviously I should not be making changes directly on the Production SQL 2005 server, then in that case should I take a backup/restore on the new SQL Server 2012 and then make the required changes to the database objects
like (Table schema(changing column names/datatypes etc.), Stored Procedure, Functions & Views)
<Question>: When I do a backup/restore I would also get the data along with it, so is this a recommended approach or should we only run/use the table schema creation scripts, fix the issues identified by UA and then do an Table to Table import,
any thoughts on this ?
<Question>: If I have to do a table to table Import then I should ensure there's a downtime during the Import or would I have any other better approach
So, basically my questions are around the approach of fixing the issues identified by UA and moving the database to SQL Server 2012 environment, I have around 300 databased to me upgraded.
Please do let me know what should be a good/proven approach ? Pl. do let me know if you would need any more details from me.
---UmeshThanks all for the replies.
I am trying summarize what I have understood here:
Document SQL Server 2005 environment details, Is there any tool which could give us all relevant details
I would take the backup from the SQL Server 2005 Production environment and then restore the same in a test environment which again has SQL Server 2005 and Run Upgrade Advisor on that
Probbaly run SQL Profiler as well to find out the deprecated changes to be done
I should fix all the breaking, discontinued changes on the Test system identified by UA
I should fix all the deprecated changes on the Test system identified by SQL Profiler
Steps 3 & 4 should give me the changed scripts for all database objects (i.e. Table Schema, Stored Procedures, Functions & Views)
<Question> Perform test, I understand this acitivity test can be captured by having SQL profiler running in the background on the SQL Server 2005 production environment where we can identify some days in a week or a month where maximum activity is
expected to ensure we cover most the scenarios, let me know is this approach looks fine or is there a better approach
Now, with regards to acutal upgrade I need to identify a time window where in less activity is done during which I could have a downtime for the actual SQL Server 2005 production environment
Post downtine, I should do a BackUp for all databases from SQL Server 2005 production environment
Test on environment readiness of SQL Server 2012 can be compared against the documentation done as part of the first Step
<Question> Ideally I should a restore first in the new environment which has SQL Server 2012
<Question> Then run the Scripted changes where we fixed all the breaking, discontinued & deprecated changes
<Question> Does above sequence of Step 9 & 10 make sense or is there a better approach of doing it
<Question> Post Upgrade and running of changed scripts, I should run the Upgrade Advisor again and see if everything looks fine
<Question> Perform test again which we ran on SQL Server 2005 Test environment
<Question> These steps should complete the Upgrade process.
Please do let me know if the above sequence look ok to all of you and does it really work in a practical scenario, do let me know your feedback or any change in sequence/process or any other tools that can be used here.
Thanks Again ... -
Using MAS/MAR with SQL 2005 / MSA clients with SQL2000 ?
Hello,
for the upgrade to MAS/MAR 5.0 SP15, SQL2005 is only supported.
AT the moment we use 5.0 SP11 with SQL2000.
Is it possible to install the sql2005 only on the MAR/MAS and create an upgrade
package (MUP) for MAS clients (with SQL2000), which should also be upgraded to 5.0 SP15 ?
Or must I upgrade the msa-clients to sql2005 too ?
Or can I upgrade the MAR/MAS with SQL2000 and forget the SQL-upgrade to 2005 ?
WHat do you think is the best way ?
Thanks,
GerdThere are two possible scenarios for this issue.
If all the clients are connected in network :
1 You can take the IDES DB Backup in one machine copy it to all client laptops and restore it. you can also achive this using SQL server inbuilt stored procedures. i.e this can be automated with simple SQL script.
If the client laptops are not in the network
1. One way is, you have to upgrade one client laptop machine to SQL Server 2005 and make sure that every thing works fine. take the image of the machine, pack it in MUP and roll out to all client laptops. This is the preferred way of doing.
2. Secnd way is, You just need to automate the entire of task of taking the IDES DB backup in each user laptop, install the SQL server 2005 and then attaching the backup DB. It is not tested by us and not sure of the results.
Best Regards
Shankar -
OCS 2007 R2 with SQL 2005 database mirroring failover?
We have OCS 2007 Enterprise Edition installed fine and with the databases mirrored to a backup server/location. I'm testing our environment for a potential disaster, including losing our primary SQL server (SQL 2005). I fail the databases over and update the backend pool to the backup SQL server name, but we cannot connect via Office Communicator and I see this error on the OCS server:
OCS User Services, error category 1006, event id 30962:
Connection to back-end database succeeded, but failed to execute registration stored procedure on the back-end. This error should not occur under normal operating conditions. Contact product support.
Back-end Server: databkp Database: rtc Sql native error: 515 Connection string of:
driver={SQL Native Client};Trusted_Connection=yes;AutoTranslate=no;server=databkp;database=rtc;
Cause: Possible issues with back-end database.
Resolution:
Ensure the back-end is functioning correctly.
Can anyone shed some light on this SQL 515 error? Thanks in advance!
-ErikWe're having a similar issue but with error number 601. I've tried a million different things aside from restoring the database, which may be next. I tried editing the procedure and I *think* I edited the right lines 77 and 105 for me. Changed:
delete dbo.DbConfigDateTime
from @DbTime as t
where dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtc'
and t.Value is null
to:
delete dbo.DbConfigDateTime
from @DbTime as t
where dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtc'
and t.Value is not null
and
delete rtcdyn.dbo.DbConfigDateTime
from @DbTime as t
where rtcdyn.dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtcdyn'
and t.Value is null
to:
delete rtcdyn.dbo.DbConfigDateTime
from @DbTime as t
where rtcdyn.dbo.DbConfigDateTime.Name = t.ValueName
and t.StoredDbName = N'rtcdyn'
and t.Value is not null
Not sure if that's where the modification is supposed to go. Any clarity here? Anyone else get a 601 error? -
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
SohailHi 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 -
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. -
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,
SSHi 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. -
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 === -
Crystal 8.5 connection with Sql 2005
Post Author: sgtpep
CA Forum: Semantic Layer and Data Connectivity
Hello all,I'm not sure this is the right forum group to post in, but here it goes:I have a problem when trying to print my crystal 8.5 reports through a sql 2005 native client.Some of them work just fine, but i get this error: "print job failed cannot open sql server" for others.I've been doing a little research, but i can't seem to find a definitive answer on this topic: Can/Does crystal 8.5 work with sql 2005 databases.I did find something about upgrading my drivers, but i'm not sure where to find them and what i should be looking for.Thanks in advance for your help,EricI see - the field notice does mention ICM 7.2(7)ES139.
Multiple occurrences of this issue have been observed since October 14, 2010
and on all Unified ICM/CCE releases. This is not a regression defect. The issue
occurs when a Microsoft SQL Server query operation is performed to compare the
'lastUpdateKeys' on AW and Central Controller/Logger, during the incremental
copying of configuration changes to the local AW. In addition, using the ICMDBA
tool to backup and restore the database with "Truncate Config Message Log"
option checked can lead to a similar issue that causes the ICM/CCE Router to
reject configuration updates. No UpdateAW restart is observed in this
situation.
I mistakenly thought it was caused by the SQL upgrade from 2000 to 2005.
By the way, regarding defect CSCtj65060, I NEVER check that "Truncate Config Message Log" option when exporting the config.
Regards,
Geoff -
Microsoft SQL 2005 preload problem
Hi Guys,
First post! I took receipt of my W520 a few weeks ago. It is great, very pleased with it on the whole.
There is one problem, however. I play a fair amount of recreational card games over the internet. This requires a program which converts the text file “hand histories” into postgreSQL server data to make it quickly readable and provide tracking for win/loss among a whole host of other statistical things.
Unfortunately after going through their troubleshooting numerous times, going through factory restore and repeating the process, I still cannot get my SQL server to automatically start. Believe me, I have tried everything. Running them all as admin, editing the startup in the windows “services” dialog etc etc. The server does start manually and the program works fine, but every time I start it I have to do it manually and it is irritating. It should just start up in the background but it doesn’t.
I believe it is the Microsoft SQL 2005 express that is somehow blocking the auto start. Basically, I want my Lenovo as it is, just without the preloaded SQL server. Using the factory restore just reloads it back on and when I manually uninstall the SQL server I still have the same problem. I believe it leaves a lot of little nuggets behind when you uninstall it through the standard W7 “uninstall a program” and the full uninstall looks a long and difficult process, with no guarantee of really removing everything.
So, the plan is to install a bare copy of W7 using a borrowed disk, install my own personal SQL program and test to see if that works. I am almost certain it will. From there, I plan to build back my programs on top so I essentially have my PC now, bar the bundled SQL 2005 express or whatever it is. Following this I will make a system image and store it away safely to avoid all this mess and only reinstall using the factory disks if absolutely necessary.
I have my W7 OEM serial, found using a serial grabber. Obviously I didn’t pay all this money to scrap all the useful thinkvantage tools like “airbag” and basic fingerprint/camera drivers etc. I also like the realtime warranty countdown timer. How should I go about this task? Is all I need is the PC serial underneath to reload thinkvantage at a later date with full functionality? Is there anything I should consider before starting?
If there is a better subforum to post this question in, please let me know.
Many thanks,
NickWhat is service dependency?
Yes I tried to make a batch file. Not in startup folder, but one on the desktop that had the right path. This returned an error from the statistical program and not the SQL server. It initially looked hopeful as I had it start up the "start server" option for the right SQL server. This opened up the dos window and said it had correctly started. However, when the stats program launched it hung up on loadscreen and returned an error message. Not sure why this was, but it didn't seem to like being loaded through a .bat.
This seems like a work around more than a solution anyway. I just want to get it to work properly.
Here is the thread in the database analaysis program forum for your reference.
http://forums.holdemmanager.com/general-support/197501-hem-crashing.html
Thanks,
Nick -
Hi ,
I have SAP 47X200 on SQL2005 64-bit installed on Windows enterprise edition X64.
I have installed database software using SQL4SAP.vbs as decrived in the installation guide : all OK , all work fine.
But , I want to use SQL 2005 with fixed memory as descrived in the article http://msdn.microsoft.com/en-us/library/ms191144.aspx
but in the server page proprierties box Memory i don't have the flag box Dynamic memory configuration but only Minimum server memory and Maximum server memory : if I set this two last value the same , the minimum server memory real is under this parameter.
So anyone know whi ? How to set fixed server memory ? Whi I don't have this flag?
thks Antonio Voce
Reward point for you.Hi ,
I set as you tell and now in database server proprierties under memory box i have this value :
Minimum server memory : 12000
Maximum server memory : 12000
Index creation memory : 12000
I have rebooted the server , starded SAP but in st04 I still see that the database memory is dynamically assigned :
Microsoft SQL Server 2005 - 9.00.3054.00 (X64) ##M Enterprise Edition
Windows NT 5.2 (Build 3790: Service Pack 2)
Database R3A Schema r3a Time of analysis 13.06.2008 16:38:46
DB Server SAPPONE DB startup 06/13/2008 16:35:38
CPUs available for SQL Server 16 of 16 Physical memory MB 32.765
Trace flag SAP release 620
Memory Usage
Current memory KB 600.320 Total SQL connections 61
Maximum memory KB 12.288.000 R/3 connections 60
Memory setting RANGE Free pages 675
Procedure cache KB 58.163 Data cache size KB 534.274
hit ratio % 87 hit ratio % 93
Maybe you are looking for
-
Windows Vista with Windows 7 Upgrade on Boot Camp 4.0.1. Is it possible??
Hello everyone, I own a genuine full installation Windows Vista and a genuine upgrade to Windows 7. I'd like to install these ( i.e. install Vista and then upgrade to 7) on a MacBookPro running on OSX Lion 10.7.2 with Boot Camp 4.0.1. Is It possible?
-
Does anyone have experience selling or giving away their Nano?
I'm considering selling my Nano and hope to replace it with a Touch. My question is, what do I need to do before selling the Nano to a buyer? Do I need to do any preparation? What does a buyer need to do to make a used Nano his? Can I just give him t
-
Unable to activate domains on solaris 10
Hi all, I have installed guardian 1.1 on my local machine (Win XP). I am using java 1.5_06. I was able to activate 9.2.1 domains on my machine, but not the domains running on Solaris 10. It keeps saying "The agent is not properly deployed to all runn
-
Apache serving bin files instead of default index
I was trying to set up Postfix and Mailman today, and I seem to have broken Apache in the process. I installed Postfix and Mailman as in the wiki, but after configuration of Mailman I tried accessing the web server, and the server gave me a bin file
-
I've just posted this question in the wrong section! (did say I was new to all this ) I'm trying to install PSE6 and keep getting the message "java script alert" critical errors were found in set up. incompatible payloads already installed. see set u