September 16, 2010 at 8:08 am
Always it fails when it hits the SSIS component. I don't understand why.
This KB is in regards to the error:
"The task is configured to pre-compile the script, but binary code is not found. Please visit the IDE in Script Task Editor by clicking Design Script button to cause binary code to be generated."
It's driving me nuts because I need to get a Script Task working, but it keeps failing on my machine. So I keep trying to install the KB and the KB install fails.
Maybe it's because I'm using SP3? (Microsoft SQL Server 2005 - 9.00.2221.00 (Intel X86) Feb 9 2007 17:30:38 Copyright (c) 1988-2005 Microsoft Corporation Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 3) )
Any suggestions?
September 16, 2010 at 8:55 am
Do you get an error in the log for the failure?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
September 16, 2010 at 8:56 am
Try installing SQL Server cumulative service pack 3. You may be suffering from a different, or additional problem. then what 931593 specifically fixes.
September 16, 2010 at 10:08 am
I second Jason. What is the error message with which the KB installation is failing? You can find the details in SetupBootStrap\Logs folder.
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
September 16, 2010 at 10:36 am
My worry about installing cumulative SP3 is that our actual Dev / Test / QC boxes are still on SP1 (we've been having problems installing later SPs) and they need to be able to read my SSIS packages.
I'd read a few years back that SP1 SSIS could not read SP2 SSIS packages because of changes MS had made..
I forgot about checking the log file. Here's a snippet (the first error I found) of what it says:
09/16/2010 10:00:36.463 MSP Error: 29554 Perfmon Counter(MSSQLServerOLAPService) not Replaced in file d:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\perf-SQL2K5msmdctr.ini
09/16/2010 10:00:51.586 MSP returned 1603: A fatal error occurred during installation.
09/16/2010 10:00:51.649 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
09/16/2010 10:00:51.649 Registry: Cannot read registry key value "Debug"
09/16/2010 10:00:52.383 Copy Engine: Error, unable to install MSP file: d:\5e4540dced78168342f3cd2136f4c4\HotFixAS\Files\sqlrun_as.msp
09/16/2010 10:00:52.383 The following exception occurred: Unable to install Windows Installer MSP file Date: 09/16/2010 10:00:52.383 File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp Line: 800
09/16/2010 10:00:52.695 Watson: Param1 = Do_sqlPerfmon2
09/16/2010 10:00:52.711 Watson: Param2 = 0x7372
09/16/2010 10:00:52.711 Watson: Param3 = sqlLodctr2
09/16/2010 10:00:52.711 Watson: Param4 = 0x7372
09/16/2010 10:00:52.727 Watson: Param5 = utillib\sqlperfmon.cpp@325
09/16/2010 10:00:52.727 Watson: Param6 = Unknown
09/16/2010 10:00:52.727 Watson: Param7 = OLAP9
09/16/2010 10:00:52.727 Watson: Param8 = @
09/16/2010 10:00:52.742 Watson: Param9 = x86
09/16/2010 10:00:52.742 Watson: Param10 = 2221
09/16/2010 10:00:52.742 Installed product: OLAP9
09/16/2010 10:00:52.742 Installing product: NS9
09/16/2010 10:00:54.148 Registry: Opened registry key "Software\Microsoft\Windows\CurrentVersion\Uninstall"
09/16/2010 10:00:54.148 Installing instance: NS
09/16/2010 10:00:54.148 Installing target: MyBox
09/16/2010 10:00:54.148 Installing file: sqlrun_ns.msp
09/16/2010 10:00:54.164 Copy Engine: Creating MSP install log file at: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\NS9_Hotfix_KB931593_sqlrun_ns.msp.log
09/16/2010 10:00:54.164 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
09/16/2010 10:00:54.164 Registry: Cannot read registry key value "Debug"
09/16/2010 10:01:14.755 MSP returned 0: The action completed successfully.
09/16/2010 10:01:14.833 Registry: Opened registry key "Software\Policies\Microsoft\Windows\Installer"
09/16/2010 10:01:14.833 Registry: Cannot read registry key value "Debug"
09/16/2010 10:01:14.833 Copy Engine: Installed file: d:\5e4540dced78168342f3cd2136f4c4\HotFixNS\Files\sqlrun_ns.msp
Looks like I have some googling to do.
September 16, 2010 at 10:39 am
Brandie Tarvin (9/16/2010)
My worry about installing cumulative SP3 is that our actual Dev / Test / QC boxes are still on SP1 (we've been having problems installing later SPs) and they need to be able to read my SSIS packages.I'd read a few years back that SP1 SSIS could not read SP2 SSIS packages because of changes MS had made..
I had run into these issues of different sp levels causing ssis packages to not be read.
Is there any chance you could have an SSIS server separate from the database servers?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply