Welcome to ISAserver.org

[EE] SP2 Installation Problems

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Installation >> [EE] SP2 Installation Problems

Page: [1]

Message

<< Older Topic Newer Topic >>

[EE] SP2 Installation Problems - 6.Feb.2006 8:34:28 PM

tubespac

Posts: 11
Joined: 9.Feb.2005
From: Philadelphia, PA
Status: offline

Whenever I attempt to install Service Pack 2 on any of my three front-end servers (ISA 2004 Enterprise Edition) I receive the following error:

"Setup failed while setting the Configuration Storage Server name."

Upon receiving this error the installation fails and begins to rollback. I did a logged installation of the service pack and this is what I return:

12:13:34 ISA setup CA INFO : Setting ADAM server in registry to servername (Computer specifed in property)
12:13:34 ISA setup CA ERROR : SetPropertyADAMServerToWorkWith: SetADAMStorageServer failed, hr=0x80070005
MSI (c) (44:C8) [12:13:34:351]: Transforming table Binary.
MSI (c) (44:C8) [12:13:34:351]: Transforming table Binary.
MSI (c) (44:C8) [12:13:34:351]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (c) (44:C8) [12:13:34:351]: Transforming table Binary.
MSI (c) (44:C8) [12:13:34:351]: Transforming table Binary.
MSI (c) (44:C8) [12:13:34:351]: Note: 1: 2262 2: Binary 3: -2147287038
MSI (s) (88!88) [12:13:36:914]: Transforming table Error.
MSI (s) (88!88) [12:13:36:914]: Transforming table Error.
MSI (s) (88!88) [12:13:36:914]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (88!88) [12:13:36:914]: Product: Microsoft ISA Server 2004 -- Setup failed while setting the Configuration Storage server name.
12:13:36 ISA setup CA ERROR : Setup failed while setting the Configuration Storage server name.
12:13:36 ISA setup CA ERROR : (Error 36050) Setup failed while setting the Configuration Storage server name.
12:13:36 ISA setup CA ERROR : EXIT: SetPropertyADAMServerToWorkWith, Custom Action failed (0x643)

I have replaced the actual server name with servername above; however, the log does display the correct server name of the CSS, and none of the front-end servers have any difficulty communicating with the CSS on TCP port 2171. All three front-end servers and the CSS server are members of the same domain, so Windows Authentication is being used.

Does anyone have any information on this error?

Regards,
Christopher