KB972455 WSUS 3.0 SP2
Eric Kosh
I try to install Windows Server Update Services 3.0 SP2 for x64-based
Systems (KB972455) but i have failed status with error code 80040E4D
In the WSUSSetup.log i have this:
2009-11-16 15:40:38 Success MWUSSetup Validating
pre-requisites...
2009-11-16 15:40:40 Error MWUSSetup CSqlConnection::Open:
Failed to open SQL connection to instance WSUS01 (Error 0x80040E4D)
2009-11-16 15:40:40 Error MWUSSetup
CUpgradeDriver::PerformPreSetupActions: Failed to open connection to SQL
instance %computername% (Error 0x80040E4D)
2009-11-16 15:40:40 Error MWUSSetup
CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error
0x80040E4D)
2009-11-16 15:40:40 Error MWUSSetup
CProgressManager::EnableCancel: GetDlgItem returning error (Error
0x80070578: Invalid window handle.)
my wsus are working correctly, i understand the problem with SQL
I there any body to help me to install this update for wsus,
i'm running on:
Windows 2008 64Bits
Sql 2008
WSUS 3.0 SP1
Thanks a lot
Eric
Lawrence Garvin [MVP]
news:%23bIHt2s...@TK2MSFTNGP05.phx.gbl...
> Hi
> I try to install Windows Server Update Services 3.0 SP2 for x64-based
> Systems (KB972455) but i have failed status with error code 80040E4D
> In the WSUSSetup.log i have this:
>
> 2009-11-16 15:40:38 Success MWUSSetup Validating
> pre-requisites...
>
> 2009-11-16 15:40:40 Error MWUSSetup CSqlConnection::Open:
> Failed to open SQL connection to instance WSUS01 (Error 0x80040E4D)
The natural conclusion is that this server does not have a SQL Server
instance by the name of "WSUS01".
Assuming WSUS01 is the server name, then the question revolves around
identifying the instance name of the database service that is supporting
WSUS.
> I there any body to help me to install this update for wsus,
>
> i'm running on:
> Windows 2008 64Bits
> Sql 2008
> WSUS 3.0 SP1
Determine the *correct* name for your database installation.
--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
My Blog: http://onsitechsolutions.spaces.live.com
Microsoft WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
Eric Kosh
> "Eric Kosh" <eric...@hotmail.com.del> wrote in message
> news:%23bIHt2s...@TK2MSFTNGP05.phx.gbl...
>
>> Hi
>> I try to install Windows Server Update Services 3.0 SP2 for x64-based
>> Systems (KB972455) but i have failed status with error code 80040E4D
>
>> In the WSUSSetup.log i have this:
>>
>> 2009-11-16 15:40:38 Success MWUSSetup Validating
>> pre-requisites...
>>
>> 2009-11-16 15:40:40 Error MWUSSetup
>> CSqlConnection::Open: Failed to open SQL connection to instance WSUS01
>> (Error 0x80040E4D)
>
> The natural conclusion is that this server does not have a SQL Server
> instance by the name of "WSUS01".
>
> Assuming WSUS01 is the server name, then the question revolves around
> identifying the instance name of the database service that is supporting
> WSUS.
>
>
>> I there any body to help me to install this update for wsus,
>>
>> i'm running on:
>> Windows 2008 64Bits
>> Sql 2008
>> WSUS 3.0 SP1
>
> Determine the *correct* name for your database installation.
>
>
>
how can i determine the CORRECT name of my instance? and how i can to
fix this error (i need to reinstall, i can change the instance name, ...
Lawrence Garvin [MVP]
> how can i determine the CORRECT name of my instance?
Describe for me your WSUS installation.
Eric Kosh
> news:ujtIoz2Z...@TK2MSFTNGP05.phx.gbl...
>
>> how can i determine the CORRECT name of my instance?
>
> Describe for me your WSUS installation.
>
>
wsus and sql are on the same machine. (Install first sql server 2008
then wsus)
I have not problem with my wsus, everything is ok. just only this
upgrade are not working (i test the sp2 from wsus, microsoft updates and
downloading the KB)
Lawrence Garvin [MVP]
>> Describe for me your WSUS installation.
> I'm not sure to understand
>
> wsus and sql are on the same machine. (Install first sql server 2008 then
> wsus)
That's a good start. Now, since this is SQL2008 I'll assume this install
wasn't done so long ago, so can you tell me exactly who/what/how SQL 2008
was installed, what edition of SQL2008 is installed, and *why* SQL2008 was
chosen to support WSUS (instead of the Windows Internal Database).
> I have not problem with my wsus, everything is ok. just only this upgrade
> are not working
The fact that the upgrade is not working wholly contradicts your believe
that you have no problem with WSUS.
Among other things, you appear to be unfamiliar with how the application
installation is configured, and since you also seem to be the primary
administrator for the service, I'd say that's a Critical Defect in the
installation!
Not to mention that the failure of the upgrade to complete successfully also
indicates the presence of one or more *technical* defects in the
installation. Since uninstalling and reinstalling (with knowledge) certainly
looks like it will take much less time and effort than trying to figure out
how the server actually is configured -- that was my suggestion.
Al Williams
ALCs are shown in Appendix D of the WSUS Operations Guide:
Appendix D: Permissions on WSUS Directories and Registry Keys
--
Allan Williams
Al Williams
http://technet.microsoft.com/en-us/library/dd939790(WS.10).aspx
In particular check that the NETWORK SERVICE has permissions to the WSUS
install (usually c:\program files\update servces) and database folders.
--
Allan Williams
Al Williams wrote:
> This is usually a permissions issue on your WSUS folders. The
> correct NTFS ALCs are shown in Appendix D of the WSUS Operations
> Guide:
> Appendix D: Permissions on WSUS Directories and Registry Keys
>
>
Eric Kosh
> news:u7Kf1aEa...@TK2MSFTNGP05.phx.gbl...
>
>>> Describe for me your WSUS installation.
>
>> I'm not sure to understand
>>
>> wsus and sql are on the same machine. (Install first sql server 2008
>> then wsus)
>
> That's a good start. Now, since this is SQL2008 I'll assume this install
> wasn't done so long ago, so can you tell me exactly who/what/how SQL
> 2008 was installed, what edition of SQL2008 is installed, and *why*
> SQL2008 was chosen to support WSUS (instead of the Windows Internal
> Database).
I chose SQL2008 for reason that i have a lot of computers (more than
3000 computers in the wsus). i think that it's better for performance.
may bye make a error?
>
>
>> I have not problem with my wsus, everything is ok. just only this
>> upgrade are not working
>
> The fact that the upgrade is not working wholly contradicts your believe
> that you have no problem with WSUS.
yes, i go say with a another formulation ;-)
i don't see any problem, all the computer are reporting correctly,
upgrade correctly. The wsus server download and apply correctly the
patch to all computers. Reports are correctly ...
>
> Among other things, you appear to be unfamiliar with how the application
> installation is configured, and since you also seem to be the primary
> administrator for the service, I'd say that's a Critical Defect in the
> installation!
>
> Not to mention that the failure of the upgrade to complete successfully
> also indicates the presence of one or more *technical* defects in the
> installation. Since uninstalling and reinstalling (with knowledge)
> certainly looks like it will take much less time and effort than trying
> to figure out how the server actually is configured -- that was my
> suggestion.
>
>
The for you , it's better to reinstall sql server and wsus, i go loss
less time ? (i need to reinstall windows ??? )
thank
Eric
Eric Kosh
Al Williams a �crit :
> Link didn't post, try:
>
> http://technet.microsoft.com/en-us/library/dd939790(WS.10).aspx
>
> In particular check that the NETWORK SERVICE has permissions to the WSUS
> install (usually c:\program files\update servces) and database folders.
>
thanks
Eric
Eric Kosh
> Link didn't post, try:
>
> http://technet.microsoft.com/en-us/library/dd939790(WS.10).aspx
>
> In particular check that the NETWORK SERVICE has permissions to the WSUS
> install (usually c:\program files\update servces) and database folders.
>
For NTFS i don't see the correct acl for WSUSInstallDir\Inventory
i corrected, reboot and it's not better
thanks
Eric
Lawrence Garvin [MVP]
>> That's a good start. Now, since this is SQL2008 I'll assume this install
>> wasn't done so long ago, so can you tell me exactly who/what/how SQL 2008
>> was installed, what edition of SQL2008 is installed, and *why* SQL2008
>> was chosen to support WSUS (instead of the Windows Internal Database).
>
> I chose SQL2008 for reason that i have a lot of computers (more than 3000
> computers in the wsus). i think that it's better for performance.
I think that for 3,000 computers, that probably wasn't a significant
justification.
However, that leaves all of my other, more important questions, still
unanswered, like
* What edition?
* Who installed it (you?)
* How was it installed?
* What instance name was it installed to?
>>> I have not problem with my wsus, everything is ok. just only this
>>> upgrade are not working
>>
>> The fact that the upgrade is not working wholly contradicts your believe
>> that you have no problem with WSUS.
>
> yes, i go say with a another formulation ;-)
> i don't see any problem, all the computer are reporting correctly, upgrade
> correctly. The wsus server download and apply correctly the patch to all
> computers. Reports are correctly ...
Okay.. fine.. you don't have a problem with your server then. Upgrade it! :)
A perfectly operational server *will* upgrade without error.. I've done it,
personally, a dozen times or more in recent years.
>> Not to mention that the failure of the upgrade to complete successfully
>> also indicates the presence of one or more *technical* defects in the
>> installation. Since uninstalling and reinstalling (with knowledge)
>> certainly looks like it will take much less time and effort than trying
>> to figure out how the server actually is configured -- that was my
>> suggestion.
>>
> The for you , it's better to reinstall sql server and wsus, i go loss less
> time ? (i need to reinstall windows ??? )
I do think that if you're unable to describe the exact installation and
configuration scenario from personal memory, and it's not documented
anywhere that you can copy and paste, starting from scratch may be your best
option.