RE: SQL Server 2005 SP3 fails on cluster environmnet



Hi Surendra,

I had the same issue by reinstalling the SP3.

Here below is what I found on the MSDN social.

CAUSE:
By default the setup creates the Temp_MS_AgentSigningCertificate_database
Database
on specified default database location,
If the location doesn't exist, it fails to create the database and the setup
fails.


RESOLUTION:

1. In SSMS, go to Server Properties > Database Settings > Database Default
Locations ,check default location for Data and Log .
2. Try to access locations specified at Data and Log, Make sure files are
available
there.
3. If any of the files missing from above location , we hit the above error.
4. In that case, change the path to point to reall location of mdf/ldf files .
5. Setup should now succeed.

Also, another nice blog explaining the same issue...
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

Regards,

Pluto

"Surendra Kavali" wrote:

Hi

My server environment - Windows Server 2003 SP2 and SQL Server 2005
Standard Editon with SP2

while installing the SQL Server 2005 SP3 the setup fails and i am getting
the A recently applied update, KB955706, failed to install.

In Hotfix log i found the following the error message.

08/08/2009 11:45:19.136 Installing instance: QA
08/08/2009 11:45:19.167 Enumerating passive cluster nodes
08/08/2009 11:45:19.183 Patching available passive node: BLRFOCDB2
08/08/2009 11:45:19.199 Patching passive node: BLRFOCDB2
08/08/2009 11:45:19.214 Waiting for first completed passive node
08/08/2009 11:45:19.261 Task Scheduler: Created remote folder for product
instance target \\BLRFOCDB2
08/08/2009 11:45:19.386 Task Scheduler: Error, cannot copy file
\\BLRFOCDB2\C$\UpdateTemp_9\batchparser90.dll, error 5
08/08/2009 11:45:19.402 Task Scheduler: Error, cannot copy file
\\BLRFOCDB2\C$\UpdateTemp_9\batchparser90.dll
08/08/2009 11:45:19.417 Task Scheduler: Error, cannot transfer payload to
remote product instance target \\BLRFOCDB2
08/08/2009 11:45:19.433 Task Scheduler: Error, cannot transfer payload to
remote product instance target \\BLRFOCDB2
08/08/2009 11:45:19.464 Error, remote process failed for product instance
target
08/08/2009 11:45:19.480 Exit code for passive node: BLRFOCDB2 = 1603

Please help me on this issue, how to resolve this issue.

Thanks
Surendra
.



Relevant Pages

  • Re: SP3 for MSDE 2000
    ... > When I ran setup from the gui, it just quit complaining about strong ... then it just created a new default instance w/ the SP3 ... >> installation on my machine using a previous network name for my machine ... >> old database is listed, nothing can connect to it since it doesn't ...
    (microsoft.public.sqlserver.security)
  • Re: SP3 for MSDE 2000
    ... > When I ran setup from the gui, it just quit complaining about strong ... then it just created a new default instance w/ the SP3 ... >> installation on my machine using a previous network name for my machine ... >> old database is listed, nothing can connect to it since it doesn't ...
    (microsoft.public.security)
  • Re: SP3 for MSDE 2000
    ... Better than that - I just found out that the default new instance that SP3 ... > When I ran setup from the gui, it just quit complaining about strong ... >> installation on my machine using a previous network name for my machine ... >> old database is listed, nothing can connect to it since it doesn't ...
    (microsoft.public.security)
  • Re: SP3 for MSDE 2000
    ... Better than that - I just found out that the default new instance that SP3 ... > When I ran setup from the gui, it just quit complaining about strong ... >> installation on my machine using a previous network name for my machine ... >> old database is listed, nothing can connect to it since it doesn't ...
    (microsoft.public.sqlserver.security)
  • Re: SetUp functions for multiple test cases
    ... couldn't find out how to implement a setup function, ... new database in-memory and fill it with example data for every single ... The True Unit Test Zealots will argue that all tests should be 100% ... SUnit from Smalltalk to Python: SUnit takes full advantage of ...
    (comp.lang.python)

Loading